summaryrefslogtreecommitdiffstats
path: root/modules/sitemap
diff options
context:
space:
mode:
author6543 <6543@obermui.de>2022-07-14 20:40:30 +0200
committerGitHub <noreply@github.com>2022-07-14 19:40:30 +0100
commit181814952779c92942d296647852a5a3aa394c79 (patch)
treed490ba99b1974f2f81158c68254662b3049bb209 /modules/sitemap
parent931c02d1521b7b990f70a590c691b066dbc27d4d (diff)
downloadgitea-181814952779c92942d296647852a5a3aa394c79.tar.gz
gitea-181814952779c92942d296647852a5a3aa394c79.zip
update xorm.io/xorm v1.3.2-0.20220714055524-c3bce556200f (#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
Diffstat (limited to 'modules/sitemap')
0 files changed, 0 insertions, 0 deletions