Redis: Module Update and a Timing-Sensitive Test Fix
Redis bumped the bundled RedisBloom module to version 8.11.80, and the team flagged a flaky test caused by a race between blocked-client timeouts and module timers. Both changes are small in scope but touch release and CI reliability.
Duration: PT2M4S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-09-03T13:13:57Z
- Audio duration: PT2M4S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
It's September 3rd, 2026, and here's what moved in the Redis codebase.
Today's activity centers on reliability at two different layers: what ships in the release, and what passes in CI.
First, the release layer. PR 15742, from Aviv David, updates the module manifest to pin RedisBloom to version 8.11.80, up from 8.10.1. This manifest drives module updates, Docker bundled installs, and release tarballs, so this single pin means every one of those build paths now pulls and compiles the newer…
Second, the CI layer. PR 15743, opened by vitahlin, digs into a flaky test tied to blocked-client timeouts and module timers. The test assumed that unblocking by timer with matching values would reliably return OK. The actual issue: blocked-client timeouts and module timers are checked at different stages of the…
Both items are small and self-contained; there's no evidence they're related beyond both being part of ongoing maintenance hygiene — one keeping bundled modules current, the other keeping the test suite trustworthy.
What's next: watch for the fix to the blocked-client timer test to land and confirm the daily CI job stops flaking. And if you're touching module timer code, keep the…
Nearby episodes from Redis
- Stability Under Pressure
- Faster RDB Loads, Steadier Tests
- Cleaning Up Data Integrity Gaps
- Weekly Recap - Closing Correctness Gaps in Clustering and Access Control
- Cleaning Up Hash Field Expiration
- Cluster Bus Security and a Flaky Test Fix
- Quietly Failing Configs Get a Voice
- Chasing Timing Bugs Across the Stack