You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For historical reasons Sentry CLI emits debug_id as a field in debug ID injection. As per spec it should actually be debugId, HOWEVER, we wanted to give ourselves and more importantly Sentry Self-Hosted versions to catch up to be able to process debugId fields before we change what Sentry CLI emits.
See this issue as a task to do a major version and emit debugId instead of debug_id.
Actual Time Capsule Content because it is funny
Donald Trump was just elected President a second time
It is 9°C in Vienna right now
People are moving to Bluesky and I have 119 followers
Cramer is on sabbatical
We are starting to work on v9 of the JS SDK
The JS SDK team is 7 people right now
Mobile team moved upstairs
We do not yet have span streaming
I do not yet have my own company
Debug ID proposal is at Stage 1
I am currently doing a masters degree
The text was updated successfully, but these errors were encountered:
For historical reasons Sentry CLI emits
debug_id
as a field in debug ID injection. As per spec it should actually bedebugId
, HOWEVER, we wanted to give ourselves and more importantly Sentry Self-Hosted versions to catch up to be able to processdebugId
fields before we change what Sentry CLI emits.See this issue as a task to do a major version and emit
debugId
instead ofdebug_id
.Actual Time Capsule Content because it is funny
The text was updated successfully, but these errors were encountered: