Skip to content
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

fix(compose): container locking #2722

Merged

Conversation

stevenh
Copy link
Collaborator

@stevenh stevenh commented Aug 8, 2024

Fix container locking which was duplicated and held for the duration of the concurrent operation so preventing any concurrency.

@stevenh stevenh requested a review from a team as a code owner August 8, 2024 19:06
Copy link

netlify bot commented Aug 8, 2024

Deploy Preview for testcontainers-go ready!

Name Link
🔨 Latest commit 6f359f0
🔍 Latest deploy log https://app.netlify.com/sites/testcontainers-go/deploys/66ba1973f338270008c4ee2e
😎 Deploy Preview https://deploy-preview-2722--testcontainers-go.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@stevenh stevenh changed the title chore: remove unused parameters chore: remove unused ctx Aug 9, 2024
@stevenh stevenh force-pushed the fix/compose-container-locking branch from e791f97 to f0e4665 Compare August 9, 2024 11:41
@stevenh stevenh changed the title chore: remove unused ctx fix(compose): container locking Aug 9, 2024
Copy link
Member

@mdelapenya mdelapenya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

Copy link
Member

@mdelapenya mdelapenya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, could you take a look at the test errors? they seem narrowed to the compose module, so they seem legit

Fix container locking which was duplicated and held for the duration of
the concurrent operation so preventing any concurrency.
@stevenh stevenh force-pushed the fix/compose-container-locking branch from f0e4665 to 6f359f0 Compare August 12, 2024 14:17
@stevenh
Copy link
Collaborator Author

stevenh commented Aug 12, 2024

BTW, could you take a look at the test errors? they seem narrowed to the compose module, so they seem legit

Yep, there was other fixes in later versions which were key for this one. I've back ported those, and will check the tests once they complete.

Copy link
Member

@mdelapenya mdelapenya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@mdelapenya mdelapenya self-assigned this Aug 12, 2024
@mdelapenya mdelapenya added the bug An issue with the library label Aug 12, 2024
@mdelapenya mdelapenya merged commit cf3db62 into testcontainers:main Aug 12, 2024
112 checks passed
@stevenh stevenh deleted the fix/compose-container-locking branch August 12, 2024 15:20
mdelapenya added a commit that referenced this pull request Aug 16, 2024
* main:
  fix: config via environment (#2725)
  fix(redpanda): race condition on port check (#2692)
  fix: logging restart (#2697)
  fix!: docker authentication setup (#2727)
  chore: improve error wrapping (#2720)
  chore: run make tests in verbose mode (#2734)
  chore(deps): bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible (#2733)
  fix(kafka): port race on start (#2696)
  docs: fix broken doc tags (#2732)
  fix: nginx request failures (#2723)
  fix(compose): container locking (#2722)
  fix(wait): log test timeout (#2716)
  chore: increase timeout values (#2719)
  chore: remove unused parameters (#2721)
  chore(mockserver): silence warning about internal port (#2730)
  feat(wait): skip internal host port check (#2691)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue with the library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants