Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: StackExchange/StackExchange.Redis
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2.7.20
Choose a base ref
...
head repository: StackExchange/StackExchange.Redis
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2.7.23
Choose a head ref
  • 3 commits
  • 10 files changed
  • 4 contributors

Commits on Feb 20, 2024

  1. Release notes for 2.7.20

    NickCraver committed Feb 20, 2024
    Configuration menu
    Copy the full SHA
    e4cdd90 View commit details
    Browse the repository at this point in the history

Commits on Feb 24, 2024

  1. Sanitize client setinfo metadata (#2654)

    * fix #2653
    
    * Update src/StackExchange.Redis/ServerEndPoint.cs
    
    Co-authored-by: Philo <philon@microsoft.com>
    
    * release notes
    
    * merge fail
    
    ---------
    
    Co-authored-by: Philo <philon@microsoft.com>
    mgravell and philon-msft authored Feb 24, 2024
    Configuration menu
    Copy the full SHA
    6392871 View commit details
    Browse the repository at this point in the history

Commits on Feb 26, 2024

  1. Feature: Add HeartbeatConsistencyChecks (#2656)

    This is a new feature for allowing keepalive commands to be sent every heartbeat regardless of if they're needed for actual keepalives. I've gotten a ping about a network drop that went undetected for ~8 minutes because of usage only in strings. We see this use case not uncommonly, and because of that string type being the only thing used, we don't detect a protocol fault from subsequent string commands.
    
    The symptoms here are partial/unexpected string payloads but ultimately the wrong answers to the wrong query. Given we don't know at what layer this drop happens (this appears to be extremely rare, 1 in quadrillions as far as we know), the best we can currently do is react to it ASAP.
    
    There may be a better way to accomplish what this is after - discussing with Marc soon as we're both online but prepping this PR in case it's best path.
    NickCraver authored Feb 26, 2024
    Configuration menu
    Copy the full SHA
    54a633f View commit details
    Browse the repository at this point in the history
Loading