Frank Laub

My reading of this is that the context leak is just warning, and the panic is a separate issue. I think we should have two tickets.

The version differences won't matter if you use `-F metal` because that depends on `-F prove`, which embeds the prover into the binary (so it won't use the server).

It would be best if we could isolate the symptoms to a single execution, the smaller the reproduction case the better.

Could you describe the use case here on what problem we're trying to solve? Ideally we'd have example code that users would write that would expose the issue and then...

I think this is resolved with 1.0, we no longer use git to clone the template.

``` No space left on device ``` Did you run out of disk space? Are you using a read-only filesystem?

Also interested in any update to this feature.

I've attempted to merge the changes upstream. I think there are two issues: 1. License changes (openssl-net uses modified-BSD, this work was under Apache2) 2. Tests. The whole SSL portion...

I'm not sure we have any good recommendations for this just yet

It'd be really nice for it to handle multiple versions like other *up tools.