You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2018. It is now read-only.
The various ServerProto traits can all return errors, but those errors are thrown away (e.g. here). It is really important for debugability to be able to have some nonzero amount of information about what's happening when your requests aren't getting through.
You can write a wrapping proto that intercepts the errors and e.g. logs them but it is over 100 lines of code for a single "kind" of proto, and regardless, silently throwing away errors is not a reasonable default. Here's one example of confusion caused by this: sfackler/rust-postgres#260
The text was updated successfully, but these errors were encountered:
The various
ServerProto
traits can all return errors, but those errors are thrown away (e.g. here). It is really important for debugability to be able to have some nonzero amount of information about what's happening when your requests aren't getting through.You can write a wrapping proto that intercepts the errors and e.g. logs them but it is over 100 lines of code for a single "kind" of proto, and regardless, silently throwing away errors is not a reasonable default. Here's one example of confusion caused by this: sfackler/rust-postgres#260
The text was updated successfully, but these errors were encountered: