This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Capture uaid Item error in webpush #811
Comments
bbangert
added a commit
that referenced
this issue
Mar 1, 2017
There's no need to log exceptions failing to save a message for a user that has been deleted. Now a metric will be emitted instead. This also tweaks the tox runner to no longer include object memory tracking by default. Closes #811
bbangert
added a commit
that referenced
this issue
Mar 1, 2017
There's no need to log exceptions failing to save a message for a user that has been deleted. Now a metric will be emitted instead. This also tweaks the tox runner to no longer include object memory tracking by default. Closes #811
bbangert
added a commit
that referenced
this issue
Mar 2, 2017
There's no need to log exceptions failing to save a message for a user that has been deleted. Now a metric will be emitted instead. This also tweaks the tox runner to no longer include object memory tracking by default. Closes #811
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When calling lookup_node in websocket.py, an invalid uaid goes to log_failure and is not caught or handled appropriately. This is logged hundreds of thousands of times in sentry and should be handled.
The text was updated successfully, but these errors were encountered: