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

Use a lookup key based on the container request to find containers to be reused #568

Open
mdelapenya opened this issue Oct 14, 2022 · 0 comments · May be fixed by #2768
Open

Use a lookup key based on the container request to find containers to be reused #568

mdelapenya opened this issue Oct 14, 2022 · 0 comments · May be fixed by #2768
Labels
chore Changes that do not impact the existing functionality

Comments

@mdelapenya
Copy link
Member

    > The fix makes sense from a technical perspective. However, regarding the `reuse` behavior itself, we decided in `testcontainers-java` that relying on the container name is not a stable indicator of equality(with the name itself potentially leading to conflicts) and we, therefore, use the hash of the container create command as the lookup key.

@kiview what do you think if we proceed with the merge, and create a discussion/issue to refactor how the reuse container feature works: if I understood correctly, a container should be reused if and only if the container request (Go abstraction) is exactly the same, identified by a unique hash of the struct representing the request.

Originally posted by @mdelapenya in #558 (comment)

@mdelapenya mdelapenya added the chore Changes that do not impact the existing functionality label Oct 14, 2022
@mdelapenya mdelapenya linked a pull request Sep 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Changes that do not impact the existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant