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: use Started instead of listening #167

Merged
merged 5 commits into from
Oct 10, 2024

Conversation

mdelapenya
Copy link
Member

@mdelapenya mdelapenya commented Oct 9, 2024

What does this PR do?

It uses Started instead of listening in the log to define that Ryuk properly initialised.

Why is this important?

To avoid breaking existing clients of Ryuk, which could be updating the Ryuk version in the properties file

Related issues

Follow-up questions

I wonder what are the different use cases to have a different ryuk version at the properties level and not use the one provided by the library.

I acknowledge that we introduced a breaking change when we updated the log format to a more structured one, which we are fixing in this PR, but if the user puts a wrong version in the properties, like a very outdated ryuk version, what can we do in that case?

To avoid breaking existing clients of Ryuk, using a custom Ryuk version with older testcontainers versions.
@mdelapenya mdelapenya requested a review from a team as a code owner October 9, 2024 17:47
@mdelapenya mdelapenya added the bug An issue with the project label Oct 9, 2024
@mdelapenya mdelapenya self-assigned this Oct 9, 2024
eddumelendez
eddumelendez previously approved these changes Oct 9, 2024
reaper.go Show resolved Hide resolved
reaper.go Outdated Show resolved Hide resolved
@mdelapenya mdelapenya merged commit 91122e2 into testcontainers:main Oct 10, 2024
9 checks passed
@mdelapenya mdelapenya deleted the fix-log branch October 10, 2024 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue with the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants