[CANARY] jwt to v2.8.1 - testing PR #241 (fix-nsc-775) #7552
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
Updated jwt dependency to a pre-release version to test fixes from PR #241 addressing nsc issue #775. Adjusted go.mod replace directive accordingly. Signed-off-by: Alberto Ricart <[email protected]>
… set Weight of 0, to 100. Now the value is honored. Signed-off-by: Alberto Ricart <[email protected]>
Member
Author
|
@neilalexander we are going to need to come up with a strategy for this fix this innocuous bug is one of those where there's an omit empty and default value for the struct is zero, along with some unfortunate interpretation that 0 == 100. |
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.
Updated jwt dependency to a pre-release version to test fixes from PR nats-io/jwt#241 addressing nsc issue nats-io/nsc#775. Adjusted go.mod replace directive accordingly.
@neilalexander this is trying to honor a mapping - the reason for the issue has a workaround (remove the mapping) but the ability to have a mapping that removes all traffic is needed - the original work on this didn't include that functionality.
Signed-off-by: Your Name [email protected]