erratic-pattern commented on PR #6518: URL: https://github.com/apache/arrow-rs/pull/6518#issuecomment-2400747715
> The reqwest maintainer states that users should walk the error chain if they want more detailed error information Yes I saw. I don't think "it's the application's responsibility to display error messages" is a valid excuse for a library to have crappy error messages out of the box, but they're free to do whatever they want. > I would recommend taking a step back and working out what it is we are wanting to expose beyond what we do currently, and getting consensus on the ticket. Presumably, someone would want to see the actual source of the error. For example: a `reqwest` error of kind `Request` could be a failure at any point during constructing the request object, sending the request, or (confusingly) receiving the response, but the error message does not elucidate anything beyond the opaque message "error sending request for url (...)". The documentation also does not explain what any of these error classifiers actually mean. As such, their error abstraction is entirely useless and more harmful than it is helpful. It would be better to simply display the `.source()` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
