-
Notifications
You must be signed in to change notification settings - Fork 2.2k
more debug info on BlockGasLimitReached exception log #5514
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
What kind of error does this return in the end? In general, I think error messages of RPC methods should be more user-friendly, without messy internals like boost.exception dumps |
then perhaps it could be extended by verbosity level of debug? |
I don't think log verbosity should control RPC output. |
Maybe output your message to log - and then look into aleth's log when you want to see debug info related to RPC call. |
Good point I agree with this since these errors will be displayed in response to functionally directly invoked by the end user. |
that is the issue. the log contain not enough info. the full message looks like:
|
I'm saying add a message to the log, but not to the RPC output |
Codecov Report
@@ Coverage Diff @@
## master #5514 +/- ##
==========================================
- Coverage 61.89% 61.89% -0.01%
==========================================
Files 345 345
Lines 28734 28716 -18
Branches 3265 3265
==========================================
- Hits 17786 17774 -12
+ Misses 9778 9777 -1
+ Partials 1170 1165 -5 |
when reading block gas limit reached log its unclear what are the expected values and why it is reached.
more debug info should help with debugging such exceptions