background-task-tracing
Ensures background task code includes unique trace IDs for debugging.
Applies to: JavaScript, Python, TypeScript
Why this matters
Every background thread/task should have a trace_id that appears in all its log messages. This enables grep-based log correlation when debugging stuck or failing jobs.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, QUAL012 includedstablestack explain QUAL012False positive in your codebase? Suppress a single line with # noqa: QUAL012
More Code Quality checks
exception-swallowing
Silently swallowed exceptions hide bugs and make debugging hard
QUAL002unnamed-thread
Threads without names are hard to identify in debugging tools
QUAL003complex-tuple
Tuples with 3+ elements are hard to understand - use a dataclass instead
QUAL004mutable-default-argument
Mutable default arguments are shared between calls and cause bugs
QUAL005print-statement
Print statements are typically debugging code that shouldn't be committed
QUAL006todo-comment
TODO/FIXME comments indicate incomplete or problematic code
QUAL007broad-exception
Catching all exceptions hides bugs and makes debugging hard
QUAL008magic-number
Magic numbers make code hard to understand and maintain