Skip to content

fix: Track latencies greater than 1 second #133

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

Merged
merged 3 commits into from
Jun 9, 2025

Conversation

jsonbailey
Copy link
Contributor

fixes #132

@jsonbailey jsonbailey requested a review from a team as a code owner June 9, 2025 13:46
The cast from TotalMilliseconds (double) to long has the potential to throw an exception. Currently the Timespan.MaxValue is not large enough, but lets ensure it stays that way in the future with a test.
@jsonbailey jsonbailey merged commit 4416c86 into main Jun 9, 2025
12 checks passed
@jsonbailey jsonbailey deleted the jb/sdk-1313/track-total-milliseconds branch June 9, 2025 14:32
jsonbailey pushed a commit that referenced this pull request Jun 9, 2025
🤖 I have created a release *beep* *boop*
---


##
[8.9.1](LaunchDarkly.ServerSdk-v8.9.0...LaunchDarkly.ServerSdk-v8.9.1)
(2025-06-09)


### Bug Fixes

* Track latencies greater than 1 second
([#133](#133))
([4416c86](4416c86))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

MigrationOpTracker incorrectly reports latency values greater than 999 ms
3 participants