Skip to content

Conversation

@tmr-g
Copy link
Contributor

@tmr-g tmr-g commented Dec 26, 2025

TODO: descr

Closes #12156, #10704

NO_DOC=bugfix
NO_CHANGELOG=fixme

TODO: tests

@tmr-g tmr-g force-pushed the i12156-2 branch 4 times, most recently from 0240d08 to 3b06138 Compare December 28, 2025 21:07
@coveralls
Copy link

coveralls commented Dec 28, 2025

Coverage Status

coverage: 87.653% (+0.02%) from 87.636%
when pulling c5f65e4 on tmr-g:i12156-2
into def2beb
on tarantool:master
.

- The epoch seconds value parsed with `'%s'`
  by `datetime.parse()` isn't ignored and used
  now as a timestamp value by `datetime.new()`.
- The zero value doesn't produce an error.

Closes tarantool#12143

NO_DOC=bugfix
Now `datetime.new()` and `datetime_object:set()`
check timestamp value to be in valid range.
Out of range timestamps produce an error instead of assertion failure.

Closes tarantool#12147

NO_DOC=bugfix
Constants `MIN_TZOFFSET` and `MAX_TZOFFSET` are introduced
in `datetime.lua` and in Lua test modules  for better evolvability.

NO_CHANGELOG=no visible changes
NO_TEST=no new behavior
NO_DOC=no new behavior
TODO: descr

Closes tarantool#12156

NO_DOC=bugfix
NO_CHANGELOG=fixme

TODO: tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] datetime: inprecisely defintion of epoch's [min,max] lead to year overflow during conversion to string

2 participants