CHANGES: socket times also moved to nanoseconds since boot - #387
Merged
Conversation
The 0.8 BREAKING, SILENTLY entry missed quark_socket.established_time and quark_socket.close_time, which moved to nanoseconds since boot along with the process and event times.
stanek-michal
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out of #372, which mixed a changelog fix, manpages and Go bindings; this carries only the changelog fix.
The 0.8 BREAKING, SILENTLY entry missed quark_socket established_time and close_time, which also moved to nanoseconds since boot.