JP Bochi

what if we assume there's interest in a PR for this, then go ahead and open one? How would you solve it?

> Always a good assumption to have, @jpbochi. I will check it out later this week and open the PR. Stay tuned. I couldn't wait, sorry. Here's my solution: https://github.com/visionmedia/supertest/pull/690

should I ping someone to review that PR?

http/3 and quic are picking up speed. - cURL has some implementations: https://github.com/curl/curl/blob/master/docs/HTTP3.md - NGINX has beta support: https://www.nginx.com/blog/our-roadmap-quic-http-3-support-nginx/ - AWS CloudFront just introduced support for it: https://aws.amazon.com/blogs/aws/new-http-3-support-for-amazon-cloudfront/ Could httpie...

FWIW, transcrypt supports that. See https://github.com/elasticdog/transcrypt#designate-a-file-to-be-encrypted. I'm posting it here as a possible source for inspiration, not as a promotion of it.

I managed to make `git diff` work by calling `gpg` directly. This is what I did: ``` echo "*.secret diff=gpg" > .gitattributes git config --local diff.gpg.textconv 'gpg --decrypt 2> /dev/null'...

> Would something like this fulfill your needs? > > #535 > > If not, how would you see the interface to git-secret changing? That could work, maybe. One thing...

@markstos yes, here's the pull request. You could try to get it merged. Or you could just use my version. :laughing: But to be honest, this code\* is far too...

same thing here. We need, at least, a workaround. What's the best known one? ``` 🜚 helm --debug list -A Error: list: failed to list: stream error when reading response...

was there any attempt to implement this in `jq`?