Re: [I] Opaque retry errors make debugging difficult [arrow-rs]

["tustvold (via GitHub)" <gi...@apache.org>]

tustvold commented on issue #5923:
URL: https://github.com/apache/arrow-rs/issues/5923#issuecomment-2184932676

   > Oh, uh, apologies. I'm not really sure what got interpreted as pejorative in there but it definitely wasn't intended!
   
   I was referring to "Users shouldn't have to fork and patch the repo to discover why their requests are failing".
   
   >  This is what I got out of printing e.source():
   
   Generally it is considered best practice to either include an error as a `source` or include it in the display implementation. In this case reqwest/hyper is choosing the former option. To display an error you should walk the source chain and print them. If you use something like anyhow it will automatically do this for you when you call the debug implementation.
   
   Now we blur this a little in some places for ergonomics reasons, but in general we want to leave it up to the caller to decide the level of verbosity they want.
   
   > The information I needed to troubleshoot was the fact that there was an invalid certificate
   
   Did you try enabling more verbose logging? Hyper is quite chatty at the debug and trace levels and I would have expected it to provide further context on this? Perhaps we just need to better document how to get more verbose logging information out of `tracing`?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org