-
Notifications
You must be signed in to change notification settings - Fork 328
Closed
Description
While trying to send a request, something happens (still investigating the source of the problem, it might be the server dropping the connection), resulting in a EPIPE
error.
Would I be correct in assuming that this best be caught in the request writer? If so, I can prepare a PR to that effect.
Of course I'm open to other suggestions :)
(main)> err.backtrace
=> [
[ 0] "<internal:prelude>:134:in `__write_nonblock'",
[ 1] "<internal:prelude>:134:in `write_nonblock'",
[ 2] "/app/vendor/bundle/ruby/2.3.0/gems/http-2.2.2/lib/http/timeout/per_operation.rb:77:in `block in write'",
[ 3] "/app/vendor/bundle/ruby/2.3.0/gems/http-2.2.2/lib/http/timeout/per_operation.rb:76:in `loop'",
[ 4] "/app/vendor/bundle/ruby/2.3.0/gems/http-2.2.2/lib/http/timeout/per_operation.rb:76:in `write'",
[ 5] "/app/vendor/bundle/ruby/2.3.0/gems/http-2.2.2/lib/http/request/writer.rb:99:in `write'",
[ 6] "/app/vendor/bundle/ruby/2.3.0/gems/http-2.2.2/lib/http/request/writer.rb:87:in `block in send_request'",
Metadata
Metadata
Assignees
Labels
No labels