-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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.8.24
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: StackExchange/StackExchange.Redis
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2.8.31
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 6 files changed
- 4 contributors
Commits on Dec 18, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1a4c66d - Browse repository at this point
Copy the full SHA 1a4c66dView commit details
Commits on Feb 18, 2025
-
Improve readme - what even is this? (#2837)
* Improve readme - what even is this? Propose words for #2836 * Update README.md --------- Co-authored-by: Nick Craver <nrcraver@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for fe04b9a - Browse repository at this point
Copy the full SHA fe04b9aView commit details
Commits on Mar 4, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 3bd3e66 - Browse repository at this point
Copy the full SHA 3bd3e66View commit details -
Fix: Respect IReconnectRetryPolicy in disconnect loops (#2853)
Fixes the case where we loop from `Connecting` -> `BeginConnectAsync` -> `OnDisconnected` and the next heartbeat triggers a reconnect again due to the backoff thresholds resetting. This ultimately causes the backoff to not be respected. Here, we're doing 2 things: - Upping the max exponential backoff window to 60 seconds which better handlers clients at scale and mass DDoS cases. - Only resets the reconnect counter on the first disconnect, not doing so again until we've successfully reconnected and heartbeated again, so backoffs are properly respected.
Configuration menu - View commit details
-
Copy full SHA for 437e1ff - Browse repository at this point
Copy the full SHA 437e1ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2a47eb5 - Browse repository at this point
Copy the full SHA 2a47eb5View commit details
Commits on Mar 6, 2025
-
Fix: Rexpect backoff in the disconnect -> resurrection case as well (#…
Configuration menu - View commit details
-
Copy full SHA for 50f2218 - Browse repository at this point
Copy the full SHA 50f2218View commit details -
Physical bridge: handle the reconnect count case
Without this, we don't increase the current count and don't escalate in the exponential retry case, so let's both do that and log that something is happening so we can diagnose from the logs.
Configuration menu - View commit details
-
Copy full SHA for cd7a3b2 - Browse repository at this point
Copy the full SHA cd7a3b2View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 2.8.24...2.8.31