Skip to content
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

Fix Mnemosyne importer chokes on due dates >= 2038 #3459

Merged
merged 2 commits into from
Oct 2, 2024

Conversation

bpnguyen107
Copy link
Contributor

@bpnguyen107 bpnguyen107 commented Sep 30, 2024

I believe this fixes #3428. It seems to be a well-known problem.

I haven't tested it yet though. Can you share the problematic .db with me so I can see if this fixes the problem @dae? Even if it doesn't, we probably want to keep this change thinking ahead towards 2038... It'd probably be a good idea to make sure anywhere else Unix time is used in the codebase is also at least 64 bits.

@bpnguyen107 bpnguyen107 changed the title Mnemosyne importer chokes on due dates >= 2038 Fix Mnemosyne importer chokes on due dates >= 2038 Sep 30, 2024
@dae
Copy link
Member

dae commented Oct 2, 2024

Thanks Ben! I've confirmed this fixed the issue.

The main outstanding issue I'm aware of is that card.mod is an i32. It's not a pressing issue, as we don't store 1+ day intervals in seconds, but we'll need to deal with it at one point.

@dae dae merged commit cc45db0 into ankitects:main Oct 2, 2024
1 check 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.

Mnemosyne importer chokes on due dates >= 2038
2 participants