[FIXED] Remove expected headers when mirroring #6961
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
Signed-off-by: Maurice van Veen <[email protected]>
|
Thank you @neilalexander and @MauriceVanVeen for the fast fix! Wondering why are we planning for the new release? Thank you 🙏 |
|
Likely in the next week or two, should have release candidates ready for testing either tomorrow or Monday. |
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.
When publishing a message into a stream with an
Nats-Expected-Stream(or other) header, it prevents this message from being stored by a mirror. Previously this was also prevented when sourcing, but that was fixed since 2.10.14 in #5256.Resolves #5865
Signed-off-by: Maurice van Veen [email protected]