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
{{ message }}
Repository navigation
Commit fef63c7
Browse filesBrowse the repository at this point in the historyBrowse files
ref(checkin): Measure check-in durations with Stopwatch (JAVA-576)
All four check-in paths kept a `long startTime = System.nanoTime()` and
subtracted it in a finally block: CheckInUtils and the SentryCheckInAdvice
in sentry-spring, sentry-spring-jakarta and sentry-spring-7.
The serialized duration is unchanged, to the bit. JavaUptimeClock.tickNanos()
is System.nanoTime(), and check-ins have no Android path where the two could
diverge, so this is the same arithmetic behind a name. That is the point of
naming the guarantee rather than the mechanism: it makes a conversion that
touches a customer-facing value provably inert, and therefore landable before
the major.
Each site carries a TODO [MAJOR] for the change that is not inert: on
elapsed-real-time, a cron job that spans device sleep would report the
duration a user would measure rather than the CPU time it had.
The clock is resolved as JavaUptimeClock.getInstance() rather than through
options, so an uninitialised SDK reaches a working clock without a scopes
lookup.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments