Skip to content

Add global timeout option for remote invocation#2038

Merged
jeremydmiller merged 1 commit intoJasperFx:mainfrom
codingzerotohero:global-remote-invocation-timeout-option
Jan 19, 2026
Merged

Add global timeout option for remote invocation#2038
jeremydmiller merged 1 commit intoJasperFx:mainfrom
codingzerotohero:global-remote-invocation-timeout-option

Conversation

@codingzerotohero
Copy link
Copy Markdown

@codingzerotohero codingzerotohero commented Jan 15, 2026

Added an option to set global default timeout for remote invocation in WolverineOptions, as well as test in CoreTests.Acceptance.remote_invocation - to ensure that it's respected.

The global timeout option will be overriden when InvokeAsync is called with a timeout parameter, allowing per call overrides if desired.

@codingzerotohero
Copy link
Copy Markdown
Author

codingzerotohero commented Jan 19, 2026

@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 bus.InvokeAsync<T> calls they've got..

@jeremydmiller jeremydmiller mentioned this pull request Jan 19, 2026
5 tasks
@jeremydmiller
Copy link
Copy Markdown
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.

@jeremydmiller jeremydmiller merged commit 1a4466f into JasperFx:main Jan 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants