Wojtek Mach

Do you know where :badarg is coming from? btw I believe your :customize_hostname_check value is the default so I don’t think it needs to be set explicitly.

Btw can you update to Req 0.5.1 just in case? There was a bug related to picking http1/2 pool though I don’t think it is relevant here.

Oh because it’s using ssl options on :gen_tcp, right? Perhaps it’s a bug in starting custom finch pool (per custom :connect_options) could you create one finch pool for http and...

Thank you for all the help. I was able to reproduce this with a test: https://github.com/wojtekmach/req/compare/wm-ssl#diff-dc476e4c9226d38862002c18df4835a1d51d98448df84548cd4e144fae0ec2e9 The thing is the custom step was only applied on the first (to https://)...

I think this proposal or EEP-34 is a very welcome change. For anyone interested, here's a proof-of-concept for 3 byte little-endian packet headers using the `{packet, -N}` notation per https://www.erlang.org/eeps/eep-0034#new-packet-types....

I'm not! It's on my long term TODO list but if anyone would like to pick it up, by all means. I hope my proof of concept helps.

The eheap_alloc crash is described here: https://github.com/erlang/otp/issues/8238 The workaround is here: https://github.com/erlang/otp/issues/8238#issuecomment-1987173291 The fix is already merged in so should be out in the next patch release.

No idea, sorry.

Could you try a new project with the same mix.lock and if you can reproduce slowly cut down the lock to the minimal one?

@paulo-ferraz-oliveira is this issue up for grabs? If it is ready to be worked on, I think we should close https://github.com/asdf-vm/asdf-erlang/issues/165 in favor of this.