Randomize the collection name to avoid collisions when search indexes are created or dropped asynchronously#2859
Merged
GromNaN merged 1 commit intodoctrine:2.13.xfrom Oct 17, 2025
Conversation
… are created or dropped asynchronously
jmikola
approved these changes
Oct 17, 2025
Member
jmikola
left a comment
jmikola
left a comment
There was a problem hiding this comment.
The WC addition seems unrelated to randomized collection names, but I do remember you adding a WC to data fixtures in a previous test. Was this just overlooked?
Member
Author
|
Yes, that was missing. The test was randomly failing with the new version of MongoDB Atlas Local without the WC. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Search indexes are created and dropped asynchronously. Sometimes the search index from a previous test still exists when the new test is run, even if the collection has been dropped.
By setting a random collection name, we prevent side effects.
I think the issue arises from the new version of MongoDB Atlas Local.