-
-
Notifications
You must be signed in to change notification settings - Fork 257
Pulsar support for retry and DLQ #1333
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
base: main
Are you sure you want to change the base?
Conversation
3.11 update
|
Hey @jeremydmiller |
…s sync with Pulsar RECONSUMETIMES header
…red endpoints, added first test for it
…on waiting for DLQ envelope
… MoveToRetryLetterQueueAsync from the lifecycle
|
@punxrok Couple things:
|
…be deleted in next commit) with ISupportNativeScheduling for Pulsar's native retry letter functionality.
…m the previously modified code
…viously modified code
…viously modified code - removed DotPulsar.Extensions.Resiliency (retry and delay message functionality was not working properly) and created "in-house" retry and DLQ functionalities
|
@jeremydmiller, I have tried to address your open concerns. Please check the comments (TODO:) where further clarification is required. |
|
@punxrok Man, I'm sorry, but would you mind rebasing this on main? And I will get this into a release very soon. |
# Conflicts: # src/Transports/Pulsar/Wolverine.Pulsar/PulsarEndpoint.cs # src/Transports/Pulsar/Wolverine.Pulsar/PulsarListener.cs # src/Transports/Pulsar/Wolverine.Pulsar/PulsarTransportExtensions.cs # src/Transports/Pulsar/Wolverine.Pulsar/Wolverine.Pulsar.csproj # src/Wolverine/Runtime/MessageContext.cs
Pulsar support for retry and DLQ