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.

Sign up for GitHub

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

Jump to bottom

Bug: CustomDatetime Marshal() uses wrong nanoseconds #170

Closed
2 tasks done
TheRangiCrew opened this issue Oct 29, 2024 · 0 comments · Fixed by #171
Closed
2 tasks done

Bug: CustomDatetime Marshal() uses wrong nanoseconds #170

TheRangiCrew opened this issue Oct 29, 2024 · 0 comments · Fixed by #171
Labels
bug Something isn't working

Comments

@TheRangiCrew
Copy link
Contributor

Describe the bug

CustomDatetime{}.MarshalCBOR() uses t.Nanosecond() which almost always marshals to 0.

Steps to reproduce

Marshal CustomDatetime and it will equal zero

Expected behaviour

Should marshal t to seconds and nanoseconds as per the CBOR specification.

SurrealDB version

surreal 2.0.4

Contact Details

No response

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update datetime marshal to use UnixNano() TheRangiCrew/surrealdb.go
1 participant
@TheRangiCrew