-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
51 non standard rpc error response from hive rpc node #52
51 non standard rpc error response from hive rpc node #52
Conversation
Adding some logic to stop this response from Hive bringing down the hivewriter. ``` File "/home/podping/app/.venv/lib/pypy3.8/site-packages/lighthive/client.py", line 167, in validate_response raw_body=response, lighthive.exceptions.RPCNodeException: Internal Error During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/podping/app/src/podping_hivewriter/podping_hivewriter.py", line 495, in failure_retry ex.raw_body["error"]["data"]["name"] KeyError: 'name' ```
This reverts commit c6d11e1.
dealing with a non standard response from a Hive RPC node
Signed-off-by: Brian of London <[email protected]>
Signed-off-by: Brian of London <[email protected]>
This PR doesn't make any code changes, what am I missing? |
Oh. You already pushed the code change to |
I kinda messed up and tried to reverse that commit and then put my changes in a branch. |
Success... this is the only error I've had for days and the code dealt with it properly:
|
If the exception is being caught and handled gracefully, is there any way to clean that up and make it less of a huge log barf? |
I think we can stop logging known exception tracebacks now that we know what's working. |
@agates I monitor my logs and I think something I fixed before... needed more fixing.