The Fix
pip install redis==7.1.0
Based on closed redis/redis-py issue #2667 · PR/commit linked
Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.
@@ -1,3 +1,4 @@
@@ -1,3 +1,4 @@
+ * Fix incorrect usage of once flag in async Sentinel
* asyncio: Fix memory leak caused by hiredis (#2693)
* Allow data to drain from async PythonParser when reading during a disconnect()
Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: Do not apply this fix if the logic of the 'once' argument is intended to remain inverted.\n\n
Why This Fix Works in Production
- Trigger: Usage of "once" argument is incorrect (inverted) in async Sentinel client
- Mechanism: The 'once' argument was used incorrectly in the async Sentinel client, causing inverted logic
- Why the fix works: Fixes the incorrect usage of the 'once' flag in the async Sentinel client by inverting the if and else bodies in the execute_command method. (first fixed release: 7.1.0).
- If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.
Why This Breaks in Prod
- The 'once' argument was used incorrectly in the async Sentinel client, causing inverted logic
- Production symptom (often without a traceback): Usage of "once" argument is incorrect (inverted) in async Sentinel client
Proof / Evidence
- GitHub issue: #2667
- Fix PR: https://github.com/redis/redis-py/pull/2718
- First fixed release: 7.1.0
- Reproduced locally: No (not executed)
- Last verified: 2026-02-07
- Confidence: 0.85
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.78
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“My PR was merged, so I'm closing this issue! Thanks @dvora-h !”
“@felipou Thanks for reporting this! We are always happy to receive PR's contributions, so go for it...”
“Ok! I've just created a PR for this: https://github.com/redis/redis-py/pull/2718”
Failure Signature (Search String)
- Usage of "once" argument is incorrect (inverted) in async Sentinel client
Copy-friendly signature
Failure Signature
-----------------
Usage of "once" argument is incorrect (inverted) in async Sentinel client
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Usage of "once" argument is incorrect (inverted) in async Sentinel client
What Broke
This led to unexpected behavior in command execution, potentially affecting application reliability.
Why It Broke
The 'once' argument was used incorrectly in the async Sentinel client, causing inverted logic
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install redis==7.1.0
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/redis/redis-py/pull/2718
First fixed release: 7.1.0
Last verified: 2026-02-07. Validate in your environment.
When NOT to Use This Fix
- Do not apply this fix if the logic of the 'once' argument is intended to remain inverted.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
- Pin production dependencies and upgrade only with a reproducible test that hits the failing path.
Version Compatibility Table
| Version | Status |
|---|---|
| 7.1.0 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.