fix: serialize psycopg2 params in replay mode for consistent InputValueHash matching #55
Conversation
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
sohankshirsagar
approved these changes
Jan 30, 2026
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Fixes a bug where psycopg2 query parameters were not serialized in replay mode, causing
InputValueHashmismatches between record and replay. This resulted in exact hash matching failing and falling back to similarity matching, which could return incorrect mocks.Changes
serialize_value(params)in_try_get_mockto ensure parameters are serialized identically to record modeRoot Cause
During recording, parameters were serialized:
During replay (in
_try_get_mock), parameters were passed raw:This caused different hash values, breaking exact matching for queries containing UUIDs, datetimes, Decimals, and other non-JSON-native types.