Opened 4 weeks ago

Last modified 3 days ago

#30909 needs_review defect

sbws consensus timestamp updates incorrectly use the current time

Reported by: teor Owned by: teor
Priority: Medium Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version: sbws: 1.1.0
Severity: Normal Keywords: sbws-ci-fail-sometimes
Cc: juga Actual Points: 0.2
Parent ID: #30733 Points: 0.2
Reviewer: juga Sponsor:

Description

There is a race condition in the sbws relay consensus timestamp update code.

sbws uses the current timestamp (now) when the same consensus is retrieved twice. Instead, it should just keep the same (valid-after) timestamp.

Child Tickets

Change History (3)

comment:1 Changed 4 weeks ago by teor

Reviewer: juga
Status: assignedneeds_review

See my pull request:
https://github.com/torproject/sbws/pull/360

It checks the valid-after time and the timestamp in the same way, so this bug shouldn't happen any more. If it does, we should fix the test code.

comment:2 Changed 10 days ago by juga

Status: needs_reviewmerge_ready

lgtm, just added a comment regarding the commit.

comment:3 Changed 3 days ago by juga

Status: merge_readyneeds_review

I realized about other bug, fixed in https://github.com/juga0/sbws/commits/bug30909_11.
I'm not sure which the workflow should be here, so just changing this ticket to needs review, but not doing PR nor assigning reviewer.

Note: See TracTickets for help on using tickets.