fix: fix the column types for the software value language_stats db table [CM-718]#3521
Merged
borfast merged 1 commit intoOct 16, 2025
Conversation
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on November 12. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
mbani01
approved these changes
Oct 16, 2025
borfast
deleted the
fix/CM-718-fix-column-types-for-software-value-language-stats-table
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.
Obtaining the software value language statistics for a specific repository was failing due to one of the values (the bytes) being too large for the database column type.
The
scctool was reporting over 4 GB of HTML files, which seemed odd, but we confirmed it and it is correct, so we modified the column types from INT to BIGINT to accommodate larger values. We did the same for some other columns as well, as a preventative measure to avoid similar issues in the future.Jira ticket