Celery 5.6.3 removes deprecated redis get_connection args — verify Scout instrumentation

Open
#837 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python, redis
Domain
backend, observability, testing-qa

Research direction

Start by checking whether the Scout Celery instrumentation calls or wraps Redis get_connection, then compare its arguments with Celery 5.6.3 and inspect worker pool initialization. Run the Scout Python agent test suite with Redis and non-Redis backends, including worker startup. Done means no runtime TypeError, instrumentation attaches correctly, and compatible version constraints include Celery 5.6.3.

Written by the indexing model from the issue text.

Description

botwork

Background

Celery 5.6.3 was released on March 26, 2026. This substantial patch release includes 30+ changes, most notably:

  • Removed deprecated arguments from redis get_connection call (#10036) — previously deprecated keyword arguments have been removed.
  • Fixed Django worker recursion bug with defensive checks for pool_cls.__module__ (#10048).
  • Fixed worker reconnection after Redis failover (#10151).
  • Fixed O(K^2) message bloat in chain of chords (#10171) — performance improvement for complex task workflows.
  • Fixed warm shutdown RuntimeError with eventlet>=0.37.0 (#10123).

Impact

Scout's Celery instrumentation may be affected by:

  1. Removed deprecated redis get_connection args — If Scout's instrumentation touches Celery's redis connection handling (e.g., for result backend monitoring or broker interaction tracing), the removal of deprecated arguments could cause TypeError exceptions at runtime.
  2. Worker pool behavior changes — The Django worker recursion fix and pool module checks alter worker startup behavior, which could affect how Scout attaches instrumentation during worker initialization.

Suggested Action

  1. Check whether Scout's Celery instrumentation calls or wraps get_connection on redis backends. If so, verify the call signature is compatible with the updated code in #10036.
  2. Run the Scout Python agent test suite against Celery 5.6.3 with both redis and non-redis backends.
  3. Verify worker startup instrumentation works correctly with the updated pool initialization logic.
  4. Update version constraints to include Celery 5.6.3 if compatible.

References

Dominant language
Python
Stars
77
Forks
19
Avg merge
1d 9h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scoutapp/scout_apm_python

All issues in scoutapp/scout_apm_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.