-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update xorm.io/xorm to fix a interpreting db column sizes issue on 32bit systems #20371
Merged
Conversation
This file contains 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
wxiaoguang
approved these changes
Jul 14, 2022
GiteaBot
added
the
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
label
Jul 14, 2022
6543
added a commit
to 6543-forks/gitea
that referenced
this pull request
Jul 14, 2022
-> #20372 |
a1012112796
approved these changes
Jul 14, 2022
GiteaBot
added
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
and removed
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
labels
Jul 14, 2022
6543
added a commit
that referenced
this pull request
Jul 14, 2022
…0372) Backport #20371 Xorm 1.3.2-0.20220714055524 contains a fix for interpreting db column sizes. Prior to this fix xorm would assume that the size of a column was within the range of an `int`. This is correct on 64bit machines where `int` is typical equivalent to `int64` however, on 32bit machines `int` tends to be `int32`. Unfortunately the size of a LONGTEXT field is actually `max_uint32`, thus using `strconv.Atoi` on these fields will fail and thus #20161 occurs on 32 bit arm. Xorm 1.3.2-0.20220714055524 changes this field to use int64 instead. Fix #20161
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Jul 15, 2022
* upstream/main: Fix commit status icon when in subdirectory (go-gitea#20285) Fix eslint parsing errors, remove eslint-plugin-html (go-gitea#20323) Include login_name in adminCreateUser response (go-gitea#20283) Add allow_rebase_update, default_delete_branch_after_merge to repository api response (go-gitea#20079) Allow to specify colors for text in markup (go-gitea#20363) [skip ci] Updated translations via Crowdin update xorm.io/xorm v1.3.2-0.20220714055524-c3bce556200f (go-gitea#20371) Add order by for assignee no sort issue (go-gitea#20053) Make sure `repo_dir` is an empty directory or doesn't exist before 'dump-repo' (go-gitea#20205) Fix English mistakes in some Markdown documents (go-gitea#20274) Fix versions check for busybox `sh` (go-gitea#20358)
6543
changed the title
update xorm.io/xorm v1.3.2-0.20220714055524-c3bce556200f
Update xorm.io/xorm to fix a interpreting db column sizes issue on 32bit systems
Jul 15, 2022
vsysoev
pushed a commit
to IntegraSDL/gitea
that referenced
this pull request
Aug 10, 2022
) Xorm 1.3.2-0.20220714055524 contains a fix for interpreting db column sizes. Prior to this fix xorm would assume that the size of a column was within the range of an `int`. This is correct on 64bit machines where `int` is typical equivalent to `int64` however, on 32bit machines `int` tends to be `int32`. Unfortunately the size of a LONGTEXT field is actually `max_uint32`, thus using `strconv.Atoi` on these fields will fail and thus go-gitea#20161 occurs on 32 bit arm. Xorm 1.3.2-0.20220714055524 changes this field to use int64 instead. Fix go-gitea#20161
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
backport/done
All backports for this PR have been created
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
type/bug
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.
Xorm 1.3.2-0.20220714055524 contains a fix for interpreting db column sizes. Prior to this fix xorm would assume that the size of a column was within the range of an
int
. This is correct on 64bit machines whereint
is typical equivalent toint64
however, on 32bit machinesint
tends to beint32
.Unfortunately the size of a LONGTEXT field is actually
max_uint32
, thus usingstrconv.Atoi
on these fields will fail and thus #20161 occurs on 32 bit arm. Xorm 1.3.2-0.20220714055524 changes this field to use int64 instead.Fix #20161