-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
Fix sub-second negative Duration serialization. #692
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #692 +/- ##
=======================================
- Coverage 97.8% 97.7% -0.1%
=======================================
Files 81 83 +2
Lines 9378 8984 -394
=======================================
- Hits 9169 8777 -392
+ Misses 209 207 -2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL
PTAL? :) |
This is still waiting on resolution to the changed comment. |
OK. But I replied there a while ago. I can just remove the comment change
from the PR if you still disagree with me.
…On Sun, 22 Sep 2024 at 00:47, Jacob Pratt ***@***.***> wrote:
This is still waiting on resolution to the changed comment.
—
Reply to this email directly, view it on GitHub
<#692 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABYQ56TNCSZ3CNVFOCYALETZXXZQ5AVCNFSM6AAAAABKPHZQTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGM2DKNZVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
That is what I had initially requested, yes. |
Done, PTAL. |
Sorry, I did not mean to close this! It happened automatically (somehow) when force-pushing a rebase. Due to a quirk of GitHub, any PR that is force-pushed after being closed cannot be re-opened. As such I'll be merging it manually, so as to avoid making you open a new PR. You're still credited as the author 🙂 |
This addresses the problem that the Duration's sign will "disappear" both during serialization and deserialization of sub-second Durations.