-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose.devcontainer.containerFeatures.TIMESTAMP.yml
race conditions
#801
Labels
bug
Something isn't working
Milestone
Comments
beejeebus
pushed a commit
to beejeebus/cli
that referenced
this issue
Apr 16, 2024
…ainers#801 This commit adds a UUID to the filename for `docker-compose.devcontainer.containerFeatures`. The current filename uses a timestamp to avoid collisions, which causes different invocations of the CLI to overwrite each others files.
beejeebus
pushed a commit
to beejeebus/cli
that referenced
this issue
Apr 18, 2024
…ainers#801 This commit adds a UUID to the filename for `docker-compose.devcontainer.containerFeatures`. The current filename uses a timestamp to avoid collisions, which causes different invocations of the CLI to overwrite each others files.
chrmarti
pushed a commit
that referenced
this issue
Apr 18, 2024
This commit adds a UUID to the filename for `docker-compose.devcontainer.containerFeatures`. The current filename uses a timestamp to avoid collisions, which causes different invocations of the CLI to overwrite each others files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
👋 we use the devcontainer CLI in a testing framework that runs tests in parallel.
we've found occasional failures in these tests, and tracked it down to tests overwriting each others
docker-compose.devcontainer.containerFeatures.TIMESTAMP.yml
file.we routinely run more than one of these in one second, so TIMESTAMP isn't enough to keep them from clobbering each other.
The text was updated successfully, but these errors were encountered: