wiki:org/teams/NetworkTeam/BugTriage

Minimal Checks

Tickets Without A Component

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

Tickets Without A Milestone

Tor

Ticket Summary Status Owner Reviewer Priority Severity Modified
#31179 Eliminate non tor_queue.h linked lists. new Medium Normal 6 hours ago
#31103 Support ORPort picking a random port that persists across restarts new Medium Normal 7 hours ago
#31190 List all valid DirPort urls new Medium Normal 25 hours ago
#31189 potential docs update needed for GuardLifetime? new Medium Normal 25 hours ago
#31188 make[1]: don't know how to make ./src/rust/target/release/libtor_rust.a new Medium Normal 26 hours ago
#31163 A flag to use hostname than IP as relay new Medium Normal 34 hours ago
#31112 remove specified target_hopnum from relay-side machines merge_ready Medium Normal 8 days ago
#31056 Hidden service sometimes unable to create circuit new High Normal 2 weeks ago

sbws

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

Complex Checks

Recently Modified Tickets

Tor

Results (1 - 10 of 1908)

1 2 3 4 5 6 7 8 9 10 11

Milestone: Tor: unspecified (10 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#31011 Make the bridge authority reject private PT addresses when DirAllowPrivateAddresses is 0 new Medium Normal 5 hours ago
#31074 Use tor_queue.h macros in config_line_t new Low Normal 6 hours ago
#29656 describe global initialization in our tinytest-based unit tests new Medium Normal 6 hours ago
#30349 Document member-hiding conventions for structs new Medium Normal 6 hours ago
#31121 Use publish-subscribe system in more places new Medium Normal 7 hours ago
#29245 Tor 0.4 eventually hits "Delaying directory fetches: No running bridges" after some period of inactivity with bridges new Medium Normal 7 hours ago
#28208 Run bridges+hs-v23 for make test-network in 0.4.2 and later assigned Medium Normal 7 hours ago
#23493 IPv6 v3 Onion Services support new Medium Normal 8 hours ago
#23507 Handle unreachable addresses on v3 single onion services by using a 3 hop path assigned Medium Normal 8 hours ago
#15516 Consider rate-limiting INTRODUCE2 cells when under load needs_revision dgoulet asn Medium Normal 8 hours ago
(more results for this group on next page)
1 2 3 4 5 6 7 8 9 10 11

sbws

Results (1 - 10 of 105)

1 2 3 4 5 6 7 8 9 10 11

Milestone: sbws: unspecified (10 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#29710 sbws reports fewer relays than torflow new Medium Normal 4 days ago
#4708 Implement bwauth cap for latency new Medium Normal 3 weeks ago
#4709 Implement bwauth cap for TCP socket exhaustion new Medium Normal 3 weeks ago
#2888 Testing framework/dataset for bw auths assigned Medium Normal 3 weeks ago
#2550 bwauth should reschedule quicker bandwidth test when bandwidthrate changes? assigned Medium Normal 3 weeks ago
#4359 Minimize time between new relay appearing and having some bw vote for it assigned Medium Normal 3 weeks ago
#10791 Detect overtuned exit relays new Medium Normal 3 weeks ago
#5457 Bw auths don't count circuit failures in descriptor mode assigned Medium Normal 3 weeks ago
#30902 Stop comparing file_created key in test new Medium Normal 4 weeks ago
#28667 Obtain the new descriptors and network status documents by signals instead of every 5min new Medium Normal 5 weeks ago
(more results for this group on next page)
1 2 3 4 5 6 7 8 9 10 11

Or timeline for the last 4 days

Bug triage: How Nick does it

  1. EVERY DAY, ONCE OR TWICE
  1. Look at the messages on the tor-bugs mailing list, or the bug changes on the timeline. You can skip over the ones that aren't "Core Tor/Tor" or "Please select a component".

1.5. Delete it?

If the ticket is spam, ping qbi on IRC or via mail. Send him the user name of the spammer plus the ticket number or wiki page. He'll check it and then disable the user and delete all its edits (tickets, wiki pages etc.). Everyone who is in the tracadm group can execute the script. Log in to troodi, sudo to tracadm and execute delete-user USERNAME.

  1. For the "please select a component" ones, try to set a component if you can.
  1. Make sure all the fields are right, if you can:
    • points
    • version
    • severity
    • priority
    • Status (put it in needs_review if it has a patch. Put it in needs_information if it's too vague to figure out).
    • type
    • component
    • Keywords including (See: org/process/TorOnTrac#Keywords):
      • regression
      • 02x-backport
      • (what part of tor it's in?)
      • 02x-proposed, if you think it should go in some frozen release series.
      • needs-proposal
      • easy
      • intro
    • Cc the subsystem maintainers, if you know who they are and you can identify the subsystem.
    • Sponsor, if it's totally obvious.
    • Summary, if the original summary wasn't informative.
  1. Milestone:

If the ticket has no milestone:

  • If it's a regression, put it in the current development milestone, with appropriate 02x-backport tickets.
  • If it's a bug, put it in the current development milestone, with appropriate 02x-backport tickets.
  • If it has a patch, put it in whatever development milestone is taking patches of this type.
  • Otherwise you can leave it with no milestone for now put it in Tor: unspecified.
  1. Close it?

If the ticket is something that we will never do, or a request for tech support, or a duplicate, then please close it as such. For duplicates, mention each ticket on the other ticket's comments. For tech support requests, tell people where to get tech support as you close.

  1. Fast fixes first!

Here, let X be some number of minutes between 1 and 5, depending how you feel.

If you can fix the bug in X minutes, do so!

Alternatively, if you can explain how to fix the bug in X minutes, do so!

Alternatively, if you are sure you'll want to figure it out and fix it, assign it to yourself (assign monthly keywords as appropriate.)

Alternatively, if the bug is from somebody you don't know, make sure at least to thank them for reporting the bug, and say at least something to help advance the state of it. New bug reporters should be made to feel welcome!

  1. EVERY WEEK OR TWO

(Nick / Isabela Gaba should do)

  1. Make sure everything in the current dev and stable milestones belongs there.
  1. Try to make sure that there are no tickets without a component.
  1. Make sure every Core Tor/Tor ticket has a milestone.
  1. Try to make sure everything has points.
  1. Look at needs_review/etc tickets.
Last modified 3 weeks ago Last modified on Jun 24, 2019, 12:59:32 PM