Opened 11 months ago

Last modified 11 days ago

#24586 new enhancement

Audit all state for stuff we need to reset on exit to make tor restartable.

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-mobile, s8-api, 034-triage-20180328, 034-included-20180405, 034-roadmap-subtask, 035-roadmap-subtask, 035-triaged-in-20180711
Cc: darkk, brade, mcs, ahf, nickm, mike@…, arthuredelstein Actual Points:
Parent ID: #25510 Points:
Reviewer: Sponsor: Sponsor8


We should, as a last step in making tor restartable, go through all of our state to see whether there are any flags we need to clear or things we need to free.

Child Tickets

Change History (8)

comment:1 Changed 8 months ago by nickm

Keywords: 034-triage-20180328 added

comment:2 Changed 8 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:3 Changed 8 months ago by nickm

Keywords: 034-included-20180405 034-roadmap-subtask added; 034-removed-20180328 removed
Parent ID: #23847#25510

comment:4 Changed 6 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: 0.3.5.x-final
Type: defectenhancement

These are still worth doing, but I don't see them as likely to happen before our freeze in 4 days, and nobody is currently assigned to them. Deferring them to 0.3.5

comment:5 Changed 5 months ago by nickm

Keywords: 035-roadmap-subtask added

comment:6 Changed 4 months ago by nickm

Keywords: 035-triaged-in-20180711 added

comment:7 Changed 2 months ago by nickm

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

Deferring various feature-y things to 0.3.6. If one of these is actually happening in 0.3.5, please let me know!

comment:8 Changed 11 days 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.

Note: See TracTickets for help on using tickets.