[tor-bugs] #27167 [Core Tor/Tor]: track "first" OR_CONN
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Dec 21 15:51:24 UTC 2018
#27167: track "first" OR_CONN
-------------------------------------------------+-------------------------
Reporter: catalyst | Owner:
| catalyst
Type: enhancement | Status:
| merge_ready
Priority: Medium | Milestone: Tor:
| 0.4.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: usability, ux, ux-team, bootstrap, | Actual Points:
035-roadmap-subtask, 035-triaged-in-20180711, |
s8-bootstrap, 035-deferred-20180930, |
s8-errors |
Parent ID: #27103 | Points:
Reviewer: nickm | Sponsor:
| Sponsor8
-------------------------------------------------+-------------------------
Comment (by catalyst):
Replying to [comment:11 nickm]:
> This is looking solid; I don't have any must-change items. I have left
a couple of questions on the PR, to make sure I understand what's going
on.
Thanks! I've pushed a fixup commit to add the requested comment, and I'll
start working on the control-spec.txt changes.
>
> One more general question: Do you think that eventually all calls to
control_event_bootstrap() should come from the btrack subsystem, or do you
think that the ones that remain outside it are unproblematic?
I think eventually all calls to `control_event_bootstrap()` should come
from the btrack subsystem. The directory progress reporting in particular
could benefit a lot from that. Also that way we can add GETINFO handlers
to the btrack subsystem to allow applications to query detailed bootstrap
state information.
>
> Two requests:
>
> 1. Could you please open a ticket to deal with the PT issue?
Done: #28925
>
> 2. When I merge this later today, could you please close the tickets
that are fixed by it?
Will do.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27167#comment:12>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list