Jim Newsome

Ah thanks - that gives me the first panic message and a backtrace. The first panic message tells me there's a deadlock, but seems to be missing the thread `Location`s......

FTR here's our ad-hoc way of applying the params from the recent consensus: ``` for param in CircuitPriorityHalflifeMsec=30000 DoSCircuitCreationEnabled=1 DoSConnectionEnabled=1 DoSConnectionMaxConcurrentCount=50 DoSRefuseSingleHopClientRendezvous=1 ExtendByEd25519ID=1 KISTSchedRunInterval=2 NumDirectoryGuards=3 NumEntryGuards=1 NumNTorsPerTAP=100 UseOptimisticData=1 bwauthpid=1 cbttestfreq=10...

> You're going to want to check that some of these options are not already listed in our existing torrc files (e.g., tor.common.torrc), because options in the torrc files will...

I took a closer look at these parameters from the recent consensus. 3 of them are overridden by a torrc setting of the same name: ``` tor.common.torrc:DoSCircuitCreationEnabled 0 tor.common.torrc:DoSConnectionEnabled 0...

> The value of `DoSConnectionMaxConcurrentCount` should have no effect (that part of the code is skipped) if `DoSConnectionEnabled` is set to 0. Ah, makes sense. Thanks!

Rob points out that the torrc's do override `CircuitPriorityHalflife`, which overrides the consensus parameter `CircuitPriorityHalflifeMsec`. In this case it doesn't matter since they're getting the same value (30s vs 30000...

We should really take a look at this. In particular we need to set `cc_alg=2` to enable congestion control

Another example where Miri may be missing UB. I was attempting to use Miri to remind myself of how to safely work with libc style socket unions, and mistakenly (?)...

Discussed this a bit with @robgjansen . I think we agree that guix and/or nix support are potentially nice, but we can't dedicate much effort to them right now. >...

I needed this feature as well. tbh's patch works for me (thanks!)