-
Notifications
You must be signed in to change notification settings - Fork 24
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
Timestamps sent with year 2077 #211
Comments
My understanding was that tracing is not currently supported: |
Thank you. The runtime seems to support the Performance API nowadays https://community.cloudflare.com/t/2023-5-12-workers-runtime-release-notes/508952 with the limitation that time advances only when I/O is performed - which is better than nothing. |
I'll take a closer look at performance tracing, but to some extent, it will continue being limited due to how Workers runtime provides current time. However, I think measurements around IO boundaries can still be useful. |
The following repro will send timestamps with year 2077 in Self Hosted:
In Sentry.io the transaction is dropped (I assume because it is 53 years in the future!)
Passing
startTimestamp
andendTimestamp
explicitly viaperformance.now()/1000
it works as expected.I have raised this issue with sentry, but they asked me to follow up here.
I am sorry if this is not related to this repo, but it could be worth being aware.
The text was updated successfully, but these errors were encountered: