Opened 3 years ago

Last modified 5 weeks ago

#18321 assigned defect

Exclude our own vote from the consensus if we think our own vote is invalid

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dirauth reliability intro
Cc: Actual Points:
Parent ID: Points: small/medium
Reviewer: Sponsor:

Description

We're creating a vote that is invalid, but try to make a consensus anyway like nothing's wrong. Then we fail doing that as described above.

Child Tickets

Change History (16)

comment:1 Changed 3 years ago by teor

We probably shouldn't even submit our vote to the other authorities if we can't parse it ourselves.

comment:2 Changed 3 years ago by teor

Keywords: TorCoreTeam201602 added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.7.x-final

comment:3 Changed 3 years ago by teor

Milestone: Tor: 0.2.7.x-finalTor: 0.2.9.x-final

comment:4 Changed 3 years ago by arma

Agreed, I think ignoring our vote if we can't handle it, and still helping to make a consensus with the other valid votes, is a fine plan.

Unless it is a big mess of code to do it, in which case, maybe it is wise to use this opportunity to clean up the code, or maybe we should say that it's a rare case and isn't worth the extra code. Depends what you (or somebody) finds when they go to see about implementing the idea.

comment:5 Changed 3 years ago by nickm

"Ignoring our vote if we can't handle it..." wouldn't actually be too hard to do.

comment:6 Changed 3 years ago by isabela

Sponsor: SponsorU-can

comment:7 Changed 3 years ago by nickm

Parent ID: #17668
Points: small/medium

comment:8 Changed 3 years ago by nickm

Keywords: TorCoreTeam201602 removed

comment:9 Changed 3 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:10 Changed 3 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

tickets market to be removed from milestone 029

comment:11 Changed 3 years ago by nickm

Keywords: SponsorU-deferred added
Sponsor: SponsorU-can

Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.

comment:12 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:13 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:14 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 2 years ago by nickm

Keywords: tor-dirauth reliability intro added; SponsorU-deferred removed

comment:16 Changed 5 weeks ago by nickm

Owner: nickm deleted
Status: acceptedassigned

I am not actually working on these tickets, so they shouldn't be assigned to me.

Note: See TracTickets for help on using tickets.