Skip to content

Next tukanos missing seconds#48

Merged
svenvc merged 4 commits into
svenvc:masterfrom
nextTukanos:nextTukanos-missingSeconds-1
Jun 23, 2026
Merged

Next tukanos missing seconds#48
svenvc merged 4 commits into
svenvc:masterfrom
nextTukanos:nextTukanos-missingSeconds-1

Conversation

@nextTukanos

Copy link
Copy Markdown
Contributor

Fixing dates for GemStone

GemStone is using seconds in Duration and if they are missing in a Date then error is thrown.

I don't see any reason for seconds to have "special" treatment.  It is also easier to read
GemStone uses microseconds to find out if Time is equal.  If we set Time asSeconds the test will pass.
@nextTukanos nextTukanos changed the title Next tukanos missing seconds 1 Next tukanos missing seconds Jun 22, 2026
Testing Time not seconds!
Missing seconds in writer
@svenvc

svenvc commented Jun 22, 2026

Copy link
Copy Markdown
Owner

This one is different: you are changing Date's STON representation.

The Time now change is a rounding operation I guess ?

@nextTukanos

Copy link
Copy Markdown
Contributor Author

This one is different: you are changing Date's STON representation.

Yes, this is different. I'm changing it only partially. The code that adds seconds was already there. That would also mean that all the changed tests would start failing if there would be a self offset seconds ~= 0. I'm exposing the seconds to have a consistent results for every case.

The Time now change is a rounding operation I guess ?

Your guess is on point. I have discovered that GemStone compares times based on microseconds so if I don't do that the test will fail due to rounding.

@svenvc svenvc merged commit 6bde065 into svenvc:master Jun 23, 2026
7 checks passed
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.

2 participants