Ensure all github_id
columns are 8 bytes
#1386
Open
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.
We are currently getting
ActiveModel::RangeError (2159449066 is out of range for ActiveModel::Type::Integer with limit 4 bytes)
errors inShipit::CreateOnGithubJob
which suggests the ID being returned by GitHub is larger than the column we're trying to store it in.Sample backtrace
While the backtrace suggests we're hitting this issue with
CommitDeploy
, out of an abundance of precaution I went ahead and audited the entire schema to make sure allgithub_id
columns were eitherinteger(8)
orbigint
(which AFAIK are identical from an SQL standpoint). These were the outliers.