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
max recursion depth exceeded error
This happens when attempting to send an alert to the hive.
Steps to Reproduce
Create alert, have the description encoded like so: description.encode('UTF-8')
send alert to hive, api.create_alert(alert)
profit
Possible Solutions
I created a pull request with the code that fixed the issue for me: #80
The crux of the issue is when it doesn't know how to get a serializable obejct from something it is supposed to raise an exception, instead the current code recalls the same method that was just called, in an attempt to encode the object, causing an endless recursion.
My pull request instead falls back to the base implementation causing an exception to be raised when it doesn't know how to return a serializable object, this is the technique the docs suggest you use.
From the docs:
Implement this method in a subclass such that it returns
a serializable object for o, or calls the base implementation
(to raise a TypeError).
This was somewhat difficult to track down, once I found this error and fixed it I was able to discover my problem, I was passing bytes in the description field. Without an exception being raised it was impossible to find out what was happening.
The text was updated successfully, but these errors were encountered:
Bug
Work Environment
Problem Description
max recursion depth exceeded error
This happens when attempting to send an alert to the hive.
Steps to Reproduce
Possible Solutions
I created a pull request with the code that fixed the issue for me:
#80
The crux of the issue is when it doesn't know how to get a serializable obejct from something it is supposed to raise an exception, instead the current code recalls the same method that was just called, in an attempt to encode the object, causing an endless recursion.
My pull request instead falls back to the base implementation causing an exception to be raised when it doesn't know how to return a serializable object, this is the technique the docs suggest you use.
From the docs:
Implement this method in a subclass such that it returns
a serializable object for
o
, or calls the base implementation(to raise a
TypeError
).This was somewhat difficult to track down, once I found this error and fixed it I was able to discover my problem, I was passing bytes in the description field. Without an exception being raised it was impossible to find out what was happening.
The text was updated successfully, but these errors were encountered: