Opened 22 months ago

Closed 14 months ago

Last modified 14 months ago

#28018 closed enhancement (implemented)

Improve accuracy and usefulness of information reported to controllers about bootstrap status

Reported by: nickm Owned by: catalyst
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: network-team-roadmap-2019-Q1Q2, bootstrap
Cc: brade, mcs, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor19-can


Creating this item as an expansion/clarification of #22266, to better match our roadmap.

The goal here is to improve what Tor reports to controllers about our bootstrapping status, so they can better inform the user -- especially for the purpose of troubleshooting what has gone wrong.

Child Tickets

#22266taskclosedcatalystgather info on jump-to-80% issues
#23605defectclosedcatalystexpired consensus causes guard selection to stall at BOOTSTRAP PROGRESS=80
#24661defectclosedteoraccept a reasonably live consensus for guard selection
#27100enhancementclosedcatalystreport connection to PT SOCKS proxy separately from OR connection
#27102taskclosedcatalystgather feedback re decoupling bootstrap progress numbers from BOOTSTRAP_STATUS enum values
#27103enhancementclosedcatalystreport initial OR_CONN as the earliest bootstrap phases
#27402enhancementclosedcatalyststop reporting "internal paths" during bootstrap
#28281taskclosedcatalystoutline of high-level bootstrap tracker abstractions
#28591defectclosedteorAccept a future consensus for bootstrap
#28731defectclosedcatalystlog bootstrap tag name for easier troubleshooting
#28813taskclosedcatalystconfirm hypothesis re PT jump-to-80%
#28884enhancementclosedcatalystPT users still have a jump-to-80% problem
#28925defectclosedcatalystdistinguish PT vs proxy for real in bootstrap tracker
#28928taskclosedcatalystupdate control-spec.txt for new bootstrap phases
#28929defectclosedcatalystfix typo/mispaste in BOOTSTRAP_STATUS_AP_CONN_PROXY summary text

Change History (13)

comment:1 Changed 22 months ago by mcs

Cc: brade mcs added

comment:2 Changed 21 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:3 Changed 21 months ago by mcs

For #27239, I reviewed the child tickets of this ticket and thought about how Tor Launcher / Tor Browser will be affected. I added a few comments in other tickets, in some cases asking for clarification about what is planned. I have a few general comments:

Overall, the direction the Network Team has taken should bring some nice improvements to Tor Browser users. Some of the tor changes seem to require a lot of work, and I appreciate the effort that is being put into all of this.

I already mentioned this briefly in ticket:22266#comment:26, but I want to also mention it here: tor itself should try to provide status and error information in a UI-agnostic way. What I mean by that is that tor should support many kinds of status and error reporting interfaces and not lock clients into a particular way of doing things. For example, for Tor Launcher we might implement what is proposed in #23971 (a multi-step progress bar that includes clearly delineated phases). Or we might build something that looks more like a series of checkmarks (one for each bootstrap phase) with some kind of intermediate progress display. But someone else might want to build something completely different.

Another issue that is related to improved bootstrap status reporting is improved error reporting. Do we have a ticket or set of tasks that cover that area? Maybe adding more phases will be enough, but there may be more that should be done. For example, being able to tell users exactly where a failure occurred would be very helpful; currently, it is difficult to distinguish local network problems from a PT problem from a wider Tor network problem.

We are looking forward to making whatever changes are needed in to Tor Launcher / Tor Browser to accommodate the improvements. As you proceed, please help us by being clear about what has changed (hopefully control spec updates will be sufficient to communicate the changes).

comment:4 Changed 21 months ago by arma

Keywords: sponsor19-also added

Adding a note: this is a critical-path ticket for Sponsor19 as well (e.g. for #23839)

Last edited 21 months ago by arma (previous) (diff)

comment:5 Changed 21 months ago by arma

Cc: arma added

comment:6 Changed 20 months ago by gaba

Keywords: ex-sponsor8 added; sponsor19-also removed
Sponsor: Sponsor8-mustSponsor19-must

comment:7 Changed 20 months ago by gaba

Moving it to sponsor19. Let's talk about which part of this can be done for s19.

comment:8 Changed 18 months ago by nickm

Keywords: 040-deferred-20190220 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.

comment:9 Changed 15 months ago by gaba

Keywords: network-team-roadmap-2019-Q1Q2 added; ex-sponsor8 040-deferred-20190220 removed
Sponsor: Sponsor19-mustSponsor19-can

comment:10 Changed 15 months ago by catalyst

Keywords: bootstrap added

Not sure why this didn't previously have the "bootstrap" keyword.

comment:11 Changed 14 months ago by phw

Sponsor: Sponsor19-canSponsor28-can

Moving from Sponsor 19 to Sponsor 28.

comment:12 Changed 14 months ago by catalyst

Resolution: implemented
Sponsor: Sponsor28-canSponsor19-can
Status: assignedclosed

I removed all of the remaining open children of this ticket and gave them the ex-28018-child tag. We can figure out what sponsor they best belong under. Closing this ticket as sponsor19, because the already-closed children are either sponsor8 or sponsor19.

comment:13 Changed 14 months ago by gaba

thanks catalyst!

Note: See TracTickets for help on using tickets.