Hotfix: redeploy difficulty tier skull hash fix - #135
Merged
Conversation
Pass bigint[] query params and add regression tests for skull values above int32 max. Production was still serving pre-#134 code after deploy. Co-authored-by: Cursor <cursoragent@cursor.com>
Barecheck - Code coverage reportTotal: 91.11%Your code coverage diff: 0.12% ▴ ✅ All code changes are covered |
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
1 participant
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
Production Sentry still shows the old query (
skull_hash::int) after #134 merged — the API process from the 03:24 Pantheon deploy was not restarted when #134 deployed at 03:30 (app_start_timeunchanged).This PR:
::intcast,convertUInt32Valuetransformer)bigint[]bind params for skull hash lookups3975235718)Merging triggers a fresh prod deploy.
Test plan
bun test src/services/difficulty-tier/Made with Cursor