fix(mongodb): Use wait strategy instead of deprecated wait_for_logs #943
+10
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix(mongodb): Use wait strategy instead of deprecated wait_for_logs
Summary
Replace the deprecated
wait_for_logsfunction withLogMessageWaitStrategyin the MongoDB container module.This is part of a fix for #874 and similar to:
Changes
LogMessageWaitStrategyinstead ofwait_for_logs_wait_strategy=LogMessageWaitStrategy(...)to parent constructor_connect()with empty implementation (DbContainer's base implementation uses SQLAlchemy which doesn't apply to MongoDB)Testing
All existing MongoDB tests pass:
No deprecation warnings from testcontainers after this change.