Channel recovery #416
Open
Channel recovery #416
Conversation
This file contains 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
|
While this showcase the feature working, it's not ready yet as we currently don't reinitialise state such as delivery tag, and we don't recreate consumers (yet). |
Keruspe
force-pushed
the
channel-recovery
branch
2 times, most recently
from
799e115
to
8a00c90
Compare
|
Publisher confirms is now properly supported |
Keruspe
force-pushed
the
channel-recovery
branch
from
8a00c90
to
0c2ae49
Compare
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Signed-off-by: Marc-Antoine Perennou <[email protected]>
Keruspe
force-pushed
the
channel-recovery
branch
from
6d309ea
to
ab38c3d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
One more step towards #312
The test example in
examples/t.rsworks fine. We publish one message, make the channel get closed by declaring a non existing queue passively, then manage to publish a new message with no further action inbetween.