Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #30105

Closed (moved)
Open
Opened Apr 09, 2019 by Iain Learmonth@irl

"pr" lines in consensus can have trailing whitespace

dir-spec specifies keyword lines as:

KeywordLine ::= Keyword NL | Keyword WS ArgumentChar+ NL

However, observed in the wild:

pr 

There is trailing whitespace on line 1840 of the [19:00:00 consensus]. It is at line 1840.

As the directory authorities all seem to agree that this trailing whitespace should be there we don't have an issue, but it's against the spec and has likely happened by accident.

If we accidentally remove the trailing whitespace, we don't have a consensus anymore.

Options for fixing this are:

  • require trailing whitespace for pr lines with no arguments
  • make a new consensus method that doesn't have trailing whitespace

Either way, this needs a spec change before we write any code.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#30105