Wojtek Mach

OK, so about `%Req.DecodeError{exception: %Jason.DecodeError{}}`. I think it's definitely compelling to have an exception struct that I control so that I can grow it in the future. I kind of...

exactly, right? if someone was pattern matching on `%Req.DecodeError{exception: %Jason.DecodeError{}}` they would be screwed anyway. And if someone was pattern matching on just `%Req.DecodeError{}` what are they gonna do with...

Yeah, I'll go with returning `%Jason.DecodeError{}` for now, there's time before v1.0 to change things still. Thank you so much!

Done!

Before merging this, I think we should have a script ready that updates all existing builds.txt with the checksums. WDYT @ericmj? These are all the files we need to update:...

Thank you!

I'd be OK and I think Eric would be too to make a size exception in Hex for this particular package. So my question is how having or not having...

here's a POC for Elixir. :) ```elixir #!/usr/bin/env mix run Path.wildcard("#{Mix.Project.app_path()}/ebin/*.beam") |> Enum.each(fn path -> {:ok, _module, chunks} = :beam_lib.all_chunks(String.to_charlist(path)) {_, dbgi} = List.keyfind(chunks, ~c"Dbgi", 0) {:debug_info_v1, :elixir_erl, {:elixir_v1, code,...

Thank you for the report, we definitely need to improve the error message. The idea was you can only call `transport_error/1` with errors that can happen in production so your...

Thank you!