Uh oh!
There was an error while loading. Please reload this page.
feat(node): use ioredis tracing channels - #21187
Conversation
size-limit report 📦
|
Uh oh!
There was an error while loading. Please reload this page.
JPeer264
commented
May 28, 2026
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3f5a18b. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
Co-Authored-By: GPT-5 Codex <codex@openai.com>
Co-Authored-By: GPT-5 Codex <codex@openai.com>
Co-Authored-By: GPT-5 Codex <codex@openai.com>
0f096bb to
f288f8aCompareisaacs
commented
May 28, 2026
I kind of disagree. It's not too hard to land this, and then rework 21087 to incorporate both. Then the next step will be a cleanup of the span attribute keys and channel constant names. Landing this now, and I'll have updates to the other PR by EOD us/west time. |
Uh oh!
There was an error while loading. Please reload this page.

ioredis5.11 released tracing channels so we can start using them in the integration, I followed the same strategy we established withredisclient by limiting the patching to older releases and subscribing anyways which will be inert except for newer releases.I added similar tests as well to ensure both dc and non-dc paths still work.
This is not to be confused with the
redisclient, there is two of them,redisandioredis, the latter being older but more popular.