Fix the received_timestamp for client data. #305
Merged
Conversation
This file contains 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
These should be timestamped at the time they are received, not at the time that they are taken (that might be much later). Signed-off-by: Chris Lalancette <[email protected]>
ahcorde
approved these changes
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These should be timestamped at the time they are received, not at the time that they are taken (that might be much later).
I found this while debugging some of the problems in #293
@Yadunund This will cause merge conflicts with #293, but I thought it was important enough on its own that we should get it in now while I am still debugging that one. Assuming this is approved, I'll merge this and then rebase #293 on top of this one.