{"action":"created","issue":{"url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/43","repository_url":"https://api.github.com/repos/testcontainers/testcontainers-node","labels_url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/43/comments","events_url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/43/events","html_url":"https://github.com/testcontainers/testcontainers-node/issues/43","id":532275293,"node_id":"MDU6SXNzdWU1MzIyNzUyOTM=","number":43,"title":"Testcontainers should not run multiple disk checks at the same time","user":{"login":"jeantil","id":22979,"node_id":"MDQ6VXNlcjIyOTc5","avatar_url":"https://avatars3.githubusercontent.com/u/22979?v=4","gravatar_id":"","url":"https://api.github.com/users/jeantil","html_url":"https://github.com/jeantil","followers_url":"https://api.github.com/users/jeantil/followers","following_url":"https://api.github.com/users/jeantil/following{/other_user}","gists_url":"https://api.github.com/users/jeantil/gists{/gist_id}","starred_url":"https://api.github.com/users/jeantil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeantil/subscriptions","organizations_url":"https://api.github.com/users/jeantil/orgs","repos_url":"https://api.github.com/users/jeantil/repos","events_url":"https://api.github.com/users/jeantil/events{/privacy}","received_events_url":"https://api.github.com/users/jeantil/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2019-12-03T21:23:33Z","updated_at":"2019-12-04T17:16:42Z","closed_at":null,"author_association":"NONE","body":"Hi, \r\n\r\nI recently opened apocas/docker-modem#112 because I kept getting seemingly innocuous stack traces in my tests logs: \r\n```\r\n console.error node_modules/jest-jasmine2/build/jasmine/Env.js:289\r\n    Unhandled error\r\n\r\n  console.error node_modules/jest-jasmine2/build/jasmine/Env.js:290\r\n    Error: (HTTP code 500) server error - a disk usage operation is already running \r\n        at /home/jean/dev/startups/yupwego/src/yupwego/node_modules/docker-modem/lib/modem.js:257:17\r\n        at getCause (/home/jean/dev/startups/yupwego/src/yupwego/node_modules/docker-modem/lib/modem.js:287:7)\r\n        at Modem.Object.<anonymous>.Modem.buildPayload (/home/jean/dev/startups/yupwego/src/yupwego/node_modules/docker-modem/lib/modem.js:256:5)\r\n        at IncomingMessage.<anonymous> (/home/jean/dev/startups/yupwego/src/yupwego/node_modules/docker-modem/lib/modem.js:232:14)\r\n        at IncomingMessage.emit (events.js:187:15)\r\n        at endReadableNT (_stream_readable.js:1094:12)\r\n        at process._tickCallback (internal/process/next_tick.js:63:19)\r\n``` \r\n\r\n@ehossack recently commented that he started observing these messages after upgrading from testcontainers 2.0.0 to testcontainers 2.1.0 and suggests it may be related to the changes in #42 \r\n\r\nIt seems testcontainers is attempting to run multiple disk free checks. It's a bit surprising because I can reproduce it with a single jest test which starts the container in a `beforeAll` and stops it in an `afterAll`"},"comment":{"url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/comments/561743427","html_url":"https://github.com/testcontainers/testcontainers-node/issues/43#issuecomment-561743427","issue_url":"https://api.github.com/repos/testcontainers/testcontainers-node/issues/43","id":561743427,"node_id":"MDEyOklzc3VlQ29tbWVudDU2MTc0MzQyNw==","user":{"login":"cristianrgreco","id":10348798,"node_id":"MDQ6VXNlcjEwMzQ4Nzk4","avatar_url":"https://avatars2.githubusercontent.com/u/10348798?v=4","gravatar_id":"","url":"https://api.github.com/users/cristianrgreco","html_url":"https://github.com/cristianrgreco","followers_url":"https://api.github.com/users/cristianrgreco/followers","following_url":"https://api.github.com/users/cristianrgreco/following{/other_user}","gists_url":"https://api.github.com/users/cristianrgreco/gists{/gist_id}","starred_url":"https://api.github.com/users/cristianrgreco/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cristianrgreco/subscriptions","organizations_url":"https://api.github.com/users/cristianrgreco/orgs","repos_url":"https://api.github.com/users/cristianrgreco/repos","events_url":"https://api.github.com/users/cristianrgreco/events{/privacy}","received_events_url":"https://api.github.com/users/cristianrgreco/received_events","type":"User","site_admin":false},"created_at":"2019-12-04T17:16:42Z","updated_at":"2019-12-04T17:16:42Z","author_association":"COLLABORATOR","body":"My understanding is as follows:\r\n\r\n1. If other libraries perform a disk usage operation, testcontainers fails.\r\n2. If we perform a disk usage operation, other libraries are failing. \r\n\r\nCatching the error would fix the first point, but we still have the second issue. \r\n\r\nIs my understanding correct? If it is then I think the only solution is to get rid of it altogether."}}
{"actor":{"display_login":"cristianrgreco"}}