Add global timeout option for remote invocation #2038
Merged
Conversation
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
Author
|
@jeremydmiller Hey! Any chance of this getting added to upcoming release? I'm currently integrating Wolverine to replace MassTransit for a client and I'd love to NOT have to add a timeout on each of the hundreds of remote |
Member
|
@codingzerotohero Yes. I'm working on Wolverine today. Still needing some client input for a potential change, but they're being slow so maybe that has to wait for 5.12. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Added an option to set global default timeout for remote invocation in
WolverineOptions, as well as test inCoreTests.Acceptance.remote_invocation- to ensure that it's respected.The global timeout option will be overriden when
InvokeAsyncis called with a timeout parameter, allowing per call overrides if desired.