-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes #20285; prevent oid time overflow at year 2038 #20338
Conversation
I reproduce the issue by setting the date on my computer to year 2038. |
Is it possible to add a test for this? |
I guess not too easy, at least we probably can get one at openSUSE :) |
Can we use the date command to test it? edit: lol, the last commit says it was made on Sep 12, 2038 |
I'm ok with either:
|
I say, please increase the underlying integer size to 64 bits. |
Sure |
Once again, I set the system date to 2038 and there is no problem. |
Thanks for your hard work on this PR! Hint: mm: orc; threads: on; opt: speed; options: -d:release |
…g#20338) * Revert "fixes nim-lang#20285; prevent oid time overflow at year 2038" This reverts commit dfcdb6e. * increase time to 64 bits and clean up * add testcase * inline consts * add a changelog * fixes nim-lang#20285; prevent oid time overflow at year 2038
fixes #20285
ref py-bson/bson#117