-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Replace calls to verifyComplete() with expectComplete().verify(Duration) to avoid blocking indefinitely #35915
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
Conversation
@ThomazPassarelli Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
When we merge this we should also consider this comment from the original issue:
|
I've got one locally. We should also remove any calls to |
@ThomazPassarelli can you please sign the CLA when you have a moment? |
@ThomazPassarelli Thank you for signing the Contributor License Agreement! |
Thanks very much, @ThomazPassarelli. |
This pull request addresses the issue #35791, where it was required to replace
verifyComplete()
withexpectComplete().verify(Duration)
in test cases across multiple files.Changes made:
verifyComplete()
withexpectComplete().verify(Duration.ofSeconds(5))
in all the necessary places. The decision to useDuration.ofSeconds(5)
was influenced by its existing usage in another part of the project, ensuring consistency across the codebase.import java.time.Duration;
where it was not already imported.I have successfully made changes to 23 files and built the project without any errors. All the tests ran successfully after the changes.