Fix time problems on Windows 10 #41
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
Due to Windows 10[1], Robot Interfaces did produce timestamps that were before epoch and thus failed when Robot tried to convert them into results. Now, if we try to put a timestamp that is before epoch, it is just reset to epoch. Also, RF3 interface did not have parity with the RF4 interface -- now it does [1] https://stackoverflow.com/a/58203399
Tattoo
force-pushed
the
fix_win10
branch
10 times, most recently
from
28f0305 to
8d5671f
Compare
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.
Due to Windows 10, Robot Interfaces did produce timestamps that were before epoch and thus failed when Robot tried to convert them into results.
Now, if we try to put a timestamp that is before epoch, it is just reset to epoch.
Also, RF3 interface did not have parity with the RF4 interface -- now it does