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: nanosecond precision for playground canister acquisition timestamps #3501

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

ericswanson-dfinity
Copy link
Member

Description

The playground backend returns acquisition timestamps with nanosecond precision, and uses nanosecond precision when looking up reserved canisters.

SystemDateTime has OS-specific precision. On Linux and OSX this is nanosecond precision, but on Windows it's 100ns precision. OffsetDateTime has nanosecond precision on all platforms.

The result was dfx deploy --playground on Windows would return a "Canister not found" error from the playground backend.

Part of https://dfinity.atlassian.net/browse/SDK-1343

How Has This Been Tested?

Covered by CI, and tested locally on OSX and Windows.

Checklist:

…econd precision

SystemDateTime has OS-specific precision (100ns on Windows)
@mergify mergify bot merged commit 4aa1c83 into master Jan 12, 2024
173 checks passed
@mergify mergify bot deleted the ens/canister-id-store-offsetdatetime branch January 12, 2024 20:04
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