James Tucker
James Tucker
@evanphx Using middleware for chunking was a bad idea from the outset, it turns out. The problem being that it's consistently poorly defined for a server whether an app has...
As far as this ticket goes, I think the core problem in rack-streaming-proxy is that this class `https://github.com/zerowidth/rack-streaming-proxy/blob/master/lib/rack/streaming_proxy/response.rb` should be declaring `Transfer-Encoding:chunked`, given that it's outputting chunked encoding. It is...
http://github.com/raggi/hanna my fork supports 2.5, the bulk of the work for that feature was done by erikh
At runtime, you probably don't want to require anything, I'd recommend having `:require => nil`
Why prefer an arm image? That'll be slow on x86 machines? See https://github.com/tailscale/tailscale-android/pull/134/files for another method, this also explicitly picks a google apis image
It doesn't appear to be working with `--opengl` either
threads are webscale
I don't have a strong opininion either way. Certainly being able to identify it sounds nice, though I'd also quite like it if this actually worked: ``` % ~/.cache/tailscale-go/bin/go version...
i think we want to use stack.wait after stack.close to prevent this, or stack.destroy that does both
I'm happy to add additional test coverage, or provide examples of usage as you might like, but I wanted to send an in-principle patch first for feedback.