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

Creating this item as an expansion/clarification of #22266 (moved), 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.

changed milestone to %Tor: unspecified

added bootstrap component::core tor/tor milestone::Tor: unspecified network-team-roadmap-2019-Q1Q2 owner::catalyst priority::high resolution::implemented severity::normal sponsor::19-can status::closed type::enhancement labels

Trac:
Cc: N/A to brade, mcs

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

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

For #27239 (moved), 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 (moved) (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).

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

Trac:
Keywords: N/A deleted, sponsor19-also added

Trac:
Cc: brade, mcs to brade, mcs, arma

Trac:
Keywords: sponsor19-also deleted, ex-sponsor8 added
Sponsor: Sponsor8-must to Sponsor19-must

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

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.

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: unspecified
Keywords: N/A deleted, 040-deferred-20190220 added

Trac:
Keywords: ex-sponsor8, 040-deferred-20190220 deleted, network-team-roadmap-2019-Q1Q2 added
Sponsor: Sponsor19-must to Sponsor19-can

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

Trac:
Keywords: N/A deleted, bootstrap added

Moving from Sponsor 19 to Sponsor 28.

Trac:
Sponsor: Sponsor19-can to Sponsor28-can

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.

Trac:
Status: assigned to closed
Resolution: N/A to implemented
Sponsor: Sponsor28-can to Sponsor19-can

thanks catalyst!

closed

mentioned in issue #28203 (moved)

mentioned in issue #28351 (moved)

mentioned in issue #28591 (moved)

mentioned in issue #28925 (moved)

mentioned in issue #28930 (moved)

mentioned in issue #28884 (moved)

mentioned in issue #28929 (moved)

mentioned in issue #28928 (moved)

moved to tpo/core/tor#28018 (closed)