Skip to content

fix: add actionable warning for background requests during replay #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sohil-kshirsagar merged 2 commits into from
Mar 16, 2026
Merged

fix: add actionable warning for background requests during replay #76

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47158a6
fix: add actionable warning for background requests during replay
sohil-kshirsagar Mar 16, 2026
6aa2aab
Merge branch 'main' into fix/replay-background-request-warning
sohil-kshirsagar Mar 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion drift/core/mode_utils.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,9 @@ def handle_replay_mode(

# Background request: App is ready + not within a trace (no parent span) + not a server request
if is_app_ready and not current_span_info and not is_server_request:
logger.debug("[ModeUtils] Handling no-op request")
logger.warning(
"[ModeUtils] Background request detected during replay (no active trace context). This typically means a background job, scheduled task, or middleware (e.g., rate limiters, message consumers) is running outside of a test trace. To avoid errors, disable these services when TUSK_DRIFT_MODE=REPLAY."
)
return no_op_request_handler()

return replay_mode_handler()
Expand Down
Loading