-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore: Flaky test in AuthenticationServiceTest
#35538
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How will this change be any different than the execution which is already present.
The mono from
.flatMap(this::validateRequiredFieldsForGenericOAuth2)was earlier being zipped with(Mono.zip(workspaceIdMono, trueEnvironmentIdCached, newPageMono))which would mean that both these Monos will be executing in parallel.With the new change
we are still doing the same thing.
Should we use something like:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nsarupr the error is popping up because
newPageMonois getting executed alongside ofdatasourceMonoCached. With the updated change we are making sure Monos will be executed within the flatMap which was not the case earlier.Earlier:
After changes:
Also
zipWhenalso works but thought, all the zipped entities should be within the sameflatMaphence opted for this approach.This also works:
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abhvsn should we use zipWhen() for a cleaner code and better readability here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As stated I would not prefer that considering we are not using the returned value in
zipWhen.