Opened 12 months ago

Last modified 2 months ago

#27104 new enhancement

report intermediate status when building application circuits

Reported by: catalyst Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: usability, ux, ux-team, bootstrap, network-team-roadmap-2019-Q1Q2, ex-sponsor19, ex-28018-child, ex-catalyst-20190619
Cc: brade, mcs, linda, isabela, iry, intrigeri, catalyst Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

During bootstrap, some minimum number of application circuits must be established before bootstrapping will complete. Right now, the user will receive no feedback of intermediate progress as a bootstrap circuit is being built. We should make this more granular, probably with intermediate progress at each EXTEND, to make visible when Tor is being slow to build circuits.

Child Tickets

Change History (15)

comment:1 Changed 12 months ago by catalyst

Keywords: s8-bootstrap added
Sponsor: Sponsor8

comment:2 Changed 12 months ago by intrigeri

Cc: intrigeri added

comment:3 Changed 12 months ago by catalyst

Sponsor: Sponsor8Sponsor8-can

This might happen as a side effect of some of the #22266 work, but isn't an essential part of it.

comment:4 Changed 11 months ago by catalyst

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

Move my post-freeze 0.3.5 items to 0.3.6.

comment:5 Changed 10 months ago by nickm

Parent ID: #22266#28018

comment:6 Changed 10 months ago by catalyst

Type: defectenhancement

comment:7 Changed 10 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:8 Changed 8 months ago by catalyst

#27167 makes this easier by adding the bootstrap tracker subsystem. Right now we don't quite have all the right data in the origin circuit events to make this incremental application circuit progress reporting work. Some approaches include adding more status events, or reporting the count of established circuit hops with each EXTEND event.

comment:9 Changed 7 months ago by catalyst

Sponsor: Sponsor8-canSponsor19-can

comment:10 Changed 6 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:11 Changed 4 months ago by gaba

Keywords: network-team-roadmap-2019-Q1Q2 added; 035-roadmap-subtask 035-triaged-in-20180711 s8-bootstrap 040-deferred-20190220 removed

comment:12 Changed 2 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Moving all new, assigned, accepted, reopened, need_information tickets from sponsor 19 into the unsponsor land. Added keyword ex-sponsor19 to track and check later if we had something that can be added to new sponsors.

comment:13 Changed 2 months ago by catalyst

Keywords: ex-28018-child added
Parent ID: #28018

Unparent remaining open children of #28018.

comment:14 Changed 2 months ago by catalyst

Cc: catalyst added
Keywords: ex-catalyst-20190619 added
Owner: catalyst deleted

Remove myself from tickets I'm not actively working on.

comment:15 Changed 2 months ago by catalyst

Status: assignednew
Note: See TracTickets for help on using tickets.