NOTE:
I've found the SEGV issue with 13.1.1+dfsg-1 on armhf.
With patched abi=+time64 version 13.1.1+dfsg-1.2 in experimental, the
issue was resolved.
Before: 13.1.1+dfsg-1 on armhf
groonga db/test < load-last-modified.grn
[[0,1708379668.191548,0.02317619323730469],1]
root@debian:/home/debian/bug1062131# date --set="2038-01-19 12:14:00"
Tue Jan 19 12:14:00 UTC 2038
root@debian:/home/debian/bug1062131# date
Tue Jan 19 12:14:03 UTC 2038
root@debian:/home/debian/bug1062131# groonga db/test <
update-last-modified.grn Segmentation fault
After: 13.1.1+dfsg-1.2 on armhf
date --set="2038-01-19 12:13:50"
Tue Jan 19 12:13:50 UTC 2038
root@debian:/home/debian/bug1062131# groonga db/test <
load-last-modified.grn [[0,2147516032.44891,0.01663732528686523],1]
date
Tue Jan 19 12:14:18 UTC 2038
root@debian:/home/debian/bug1062131# groonga db/test <
update-last-modified.grn [[0,2147516064.584529,0.01893329620361328],1]
Here is the schema and data:
cat bug1062131.schema
table_create --name Logs --flags TABLE_NO_KEY
column_create --table Logs --name log --type ShortText
column_create --table Logs --name level --type UInt8
column_create --table Logs --name timestamp --type Time
root@debian:/home/debian/bug1062131# cat load-last-modified.grn
# cat load-last-modified.grn
# Time.parse("2024-01-01 00:00:00").to_i
# => 1704034800
load --table Logs
[
{"_id": 1, "level": 0, "log": "check last_modified in object header",
"timestamp": 1704034800} ]
root@debian:/home/debian/bug1062131# cat update-last-modified.grn
# Time.parse("2024-02-01 00:00:00").to_i
# => 1706713200
load --table Logs
[
{"_id": 1, "level": 1, "log": "check last_modified in object header",
"timestamp": 1706713200} ]
