-
Notifications
You must be signed in to change notification settings - Fork 208
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
Use common time comparison logic to enable better logging #5782
Conversation
40aa000
to
3653b43
Compare
I guess this was run before the last change, but somehow not updated afterwards. Hence re-triggering. |
There is a ticket: https://progress.opensuse.org/issues/164239 - we can force merge |
The |
rebased now, thanks. Wasn't there some fancy bot to rebase on my behalf? :) |
@Mergifyio rebase |
✅ Branch has been successfully rebased |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5782 +/- ##
=======================================
Coverage 98.49% 98.49%
=======================================
Files 394 394
Lines 38668 38671 +3
=======================================
+ Hits 38085 38088 +3
Misses 583 583 ☔ View full report in Codecov by Sentry. |
s/comparision/comparison/ |
All checks had been green except for docker-compose failing due to zypper repo refresh errors. nicksinger only fixed the typo in the git commit message subject line. Merging manually. |
check()
was previously using the current time._key_auth()
however used the time provided in a header (which is attached right as the transaction starts on the server side). This change makes use of the already existing subroutine_is_timestamp_valid
for both places and uses the current time instead of one attached in some hook earlier. It also adds a debug log output to print both plain timestamps in case of mismatches.Related ticket: https://progress.opensuse.org/issues/162038