Skip to content
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

Fix for #1967: Sanitizing message failures #1990

Merged
merged 2 commits into from
Feb 15, 2022
Merged

Fix for #1967: Sanitizing message failures #1990

merged 2 commits into from
Feb 15, 2022

Conversation

NickCraver
Copy link
Collaborator

There seems to be just 1 case not covered by the IncludeDetailsInExceptions option on ConnectionMultiplexer - this remedies that. The option is on by default so this shouldn't break people like I thought initially.

Overall, we should probably also move this option to ConfigurationOptions and defaults if we do that (#1987).

There seems to be just 1 case not covered by the IncludeDetailsInExceptions option on ConnectionMultiplexer - this remedies that. The option is on by default so this shouldn't break people like I thought initially.

Overall, we should probably also move this option to ConfigurationOptions and defaults if we do that (#1987).
@NickCraver NickCraver merged commit 34ba699 into main Feb 15, 2022
@NickCraver NickCraver deleted the craver/fix-1967 branch February 15, 2022 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ask to extend ConnectionMultiplexer.IncludeDetailInExceptions check to more places
2 participants