fix: add output schema merges to Django replay span#93
Merged
sohankshirsagar merged 1 commit intomainfrom Apr 14, 2026
Merged
Conversation
sohankshirsagar
added
the
Tusk - Pause For Current PR
Contributor
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
jy-tan
approved these changes
Apr 14, 2026
sohankshirsagar
deleted the
sohan/send-output-schema-during-replay-django
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Django middleware's replay code path (
_capture_replay_output) was missingOUTPUT_SCHEMA_MERGESon the span, causing the Tusk UI to display raw base64-encoded response bodies instead of the decoded value when viewing replay results.This is purely a UI display bug — CLI test results are unaffected and correctly report "no deviation." The CLI comparison flow never reads
outputSchemafrom the replay span. It decodes the recorded span's body using the recorded schema (which hasencoding: BASE64), then compares it against the raw HTTP response bytes from the actual replay request. Both sides resolve to the decoded value, so the comparison passes.This issue is Django-specific. Flask/WSGI and FastAPI correctly set schema merges during replay
Changes
OUTPUT_SCHEMA_MERGESattribute to the replay span inDriftMiddleware._capture_replay_outputso the downstream schema generator correctly annotates the body field withencoding: BASE64