[cache] fix #38796 - fix inconsistent handling of empty byte[] #47491
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
…t to test "not null" (tests executed successfully locally)
mgravell
added
the
feature-caching
dotnet-issue-labeler
bot
added
the
needs-area-label
mgravell
added
area-runtime
and removed
needs-area-label
BrennanConroy
approved these changes
Mar 30, 2023
amcasey
added
area-middleware
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.
fix inconsistent handling of empty byte[]
As per #38796, handling of empty byte[] is inconsistent in redis cache, with
Getreturningnull; this PR fixes thisDescription
RedisValue.HasValueis effectively "not null or empty"; we just want to test "not null"; so: use thatFixes #38796
(tests executed successfully locally)