wiki:org/teams/NetworkTeam/BugTriage

Version 11 (modified by teor, 3 months ago) (diff)

Add automatically updating queries

Minimal Checks

Tickets Without A Component

Ticket Summary Status Owner Reviewer Priority Severity Modified
#31708 Make the Tor website join the Digital Climate Strike on September 20 assigned teor Medium Normal 6 days ago
#31711 Spread the word about the Digital Climate Strike on Tor's social media assigned steph Medium Normal 6 days ago

Tickets Without A Milestone

Tor

Ticket Summary Status Owner Reviewer Priority Severity Modified
#31742 Write a script or makefile target to install git hooks new Medium Normal 42 hours ago
#31257 Tor Unexpectedly Exited. new Medium Normal 8 days ago
#31291 non-public relay health metrics for operators new Medium Normal 3 weeks ago
#31103 Support ORPort picking a random port that persists across restarts new Medium Normal 5 weeks ago
#31290 provide DNS health metrics for tor exit relay operators new Medium Normal 7 weeks ago
#31179 Eliminate non tor_queue.h linked lists. new Medium Normal 7 weeks ago
#31228 Support spawning multiple transport instances new Medium Normal 8 weeks ago
#31163 A flag to use hostname than IP as relay new Medium Normal 2 months ago
#31056 Hidden service sometimes unable to create circuit new High Normal 3 months ago

sbws

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

Complex Checks

Recently Modified Tickets

Tor

Results (1 - 10 of 1930)

1 2 3 4 5 6 7 8 9 10 11

Milestone: Tor: unspecified (10 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#22893 prop224: Make intro point per-service and not per-descriptor assigned teor Very High Normal 7 hours ago
#31576 Fix shellcheck errors in contrib/dist/rc.subr, and add to test-shellcheck new Low Minor 22 hours ago
#30797 Stop shipping an abandoned systemd script? new Medium Normal 22 hours ago
#31190 List all valid DirPort urls new Medium Normal 24 hours ago
#31756 Cover all configuration options with test_parseconf.sh new Medium Normal 35 hours ago
#31698 Reconsider HAVE_XXX_H usage in the Tor code new Low Normal 42 hours ago
#31737 Change handling of relative paths in %include directives? new Medium Normal 42 hours ago
#31713 Automatically rectify include paths before every commit new Medium Normal 5 days ago
#31636 Circuit padding: Add meta probability distribution type new Medium Normal 6 days ago
#30992 circpadding machines have shutdown sync issues (with intro circ NACKs and other cases) assigned Medium Normal 6 days 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
#31331 scanner integration test fails some times because the test Web server is not multi-threaded new Medium Normal 6 weeks ago
#29710 sbws reports fewer relays than torflow new Medium Normal 2 months ago
#4708 Implement bwauth cap for latency new Medium Normal 3 months ago
#4709 Implement bwauth cap for TCP socket exhaustion new Medium Normal 3 months ago
#2888 Testing framework/dataset for bw auths assigned Medium Normal 3 months ago
#2550 bwauth should reschedule quicker bandwidth test when bandwidthrate changes? assigned Medium Normal 3 months ago
#4359 Minimize time between new relay appearing and having some bw vote for it assigned Medium Normal 3 months ago
#10791 Detect overtuned exit relays new Medium Normal 3 months ago
#5457 Bw auths don't count circuit failures in descriptor mode assigned Medium Normal 3 months ago
#30902 Stop comparing file_created key in test new Medium Normal 3 months 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.