Use Client Timestamp for info/finish timetracking #4580
Merged
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.
If the client and server clock are not in sync, the timespans are not merged correctly. This does not lead to large differences (we’ve seen about 1 second per task) but it creates extra confusion in the time tracking view.
This PR uses the client clock for timetracking of info and finish requests.
URL of deployed dev instance (used for testing):
Steps to test:
Issues: