zuse: fix time fix regression #4599
Merged
Conversation
This file contains hidden or 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
Fixes #4598. #4474 made the JSON time conversion no longer invertible, which caused problems for chat, which uses message timestamp in milliseconds as a key -- so chat would send a message with ms timestamp x, it would get encoded as @da x, but then when it went back through the conversion to milliseconds, it would often (not always) get encoded as x-1. I still do not fully understand why this is -- and why it doesn't seem to be a problem with seconds based on cursory testing -- but integer multiplication and division generally do not invert. And adding a half a millisecond to the input date before converting it resolves the issue and makes the functions invertible. I added a regression test, so hopefully the next courageous adventurer who winds up here after wondering why +unm looks funny will have a safeguard against some of the mistakes I made.
|
Do we want this on master or next-sys? |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4598.
#4474 made the JSON time conversion no longer invertible, which caused
problems for chat, which uses message timestamp in milliseconds as a key
— so chat would send a message with ms timestamp x, it would get
encoded as @da x, but then when it went back through the conversion to
milliseconds, it would often (not always) get encoded as x-1.
I still do not fully understand why this is — and why it doesn't seem
to be a problem with seconds based on cursory testing — but integer
multiplication and division generally do not invert. And adding a half a
millisecond to the input date before converting it resolves the issue
and makes the functions invertible.
I added a regression test, so hopefully the next courageous adventurer
who winds up here after wondering why
+unmlooks funny will have asafeguard against some of the mistakes I made.