-
Notifications
You must be signed in to change notification settings - Fork 97
Receiving a feed with no data points raises 404 RequestError #119
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
Comments
Not sure if this library is still maintained, but this is a core breaking bug that has been open for at least a year. Is there any plan to tackle it or will someone try and fork the library? |
Can confirm. I am experiencing the same bug.
|
the same issue. |
Just spotted this issue, I should have probably fixed it instead of fixing the example in #160 🤦 |
This error is happening when a feed has no data, yet. The API responds with 404 and a generic "not found" error, leaving the Python client to die without much info. Just now, the IO team has updated the error messages for some of these data messages. Specifically the method:
will say "This feed has not published any data, yet.", which more clearly explains what is happening to the user. I believe @tyeth may also want to update the client itself to notice such errors and improve the behavior. It could catch these, emit a warning message, and return |
Calling
client.receive
on a newly created feed with no data points raises a 404 if no data exists on the feed.Update the library to not error on that call with a 404, and instead return a
None
value or a Data type which sets thevalue
asNone
:Example code
Output
The text was updated successfully, but these errors were encountered: