Today I opened a ticket regarding difficult to understand Torflow behavior. Subsequently I figured out the behavior, realizing it is a non-material bug that has no serious implication. However I can no longer revise the ticket, possibly due to
https://trac.torproject.org/projects/tor/ticket/26675#comment:2
or perhaps due to the next change which somehow reversed
Date: Sat, 07 Jul 2018 01:33:46 -0000 Changes (by cypherpunks):
- status: new => closed
- resolution: => fixed
I find this troubling.
On Sat, Jul 7, 2018 at 12:38 AM, starlight.2018q2@binnacle.cx wrote:
Today I opened a ticket regarding difficult to understand Torflow behavior. Subsequently I figured out the behavior, realizing it is a non-material bug that has no serious implication. However I can no longer revise the ticket, possibly due to
https://trac.torproject.org/projects/tor/ticket/26675#comment:2
or perhaps due to the next change which somehow reversed
Date: Sat, 07 Jul 2018 01:33:46 -0000 Changes (by cypherpunks):
- status: new => closed
- resolution: => fixed
I find this troubling.
Hi, Starlight!
Some part of trac are temporarily disabled, due to a bunch of vandalism last night. I hope somebody will re-enable soon, if they have time to keep an eye on it today. In the meantime, I've tried to get you back on to your ticket.
best wishes,
Thank you Nick! I was able to revise the ticket. Best to you too.
On Sat, Jul 7, 2018 at 13:49 UTC, <nickm at alum.mit.edu> wrote:
Hi, Starlight!
Some part of trac are temporarily disabled, due to a bunch of vandalism last night. I hope somebody will re-enable soon, if they have time to keep an eye on it today. In the meantime, I've tried to get you back on to your ticket.
best wishes,
Nick
-
Nick Mathewson -
starlight.2018q2＠binnacle.cx