-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
[BUG] Ombi null childRequest output #119
Comments
This may not be a bug but broken data in the API calls...Can you make these calls manually and post the data in a gist? It is erroring on that line because that is the first time we evaluate the data. Has nothing to do with denied requests.
|
@samwiseg0 its most certainly broken data as usual. we could do a .get(key, False) tho to account for it though |
Sorry I didn't respond sooner. See below gist. Looks like the denied key for TV shows is returning null, which would definitely error that if call out. |
This gets even more fun. Several of the requested TV shows doesn't have any content in childRequests somehow. If these are skipped over (or empty data is put in place of the empty request) then it works fine. API changes are fun...
|
Neither of these issues are API changes but rather a broken state the app has created. You might find that removing the broken data and adding it back might rectify the issue. There has to be child objects in TV shows. Edit: All we will do/can do is workaround this by dropping invalid data. There is no "fix" on our side. Ombi is broken and issues will have to be opened with that project. |
Describe the bug
When there are no denied requests in Ombi, the function get_all_requests errors out with the following error:
This used to work in the past. The function doesn't check to see if the index actually exists before checking the value.
Varken/varken/ombi.py
Line 105 in 8877b7b
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ombi data is added to InfluxDB and the thread stays running.
Environment (please complete the following information):
Additional context
I do recall this working in the past. This seems to kill the thread preventing anything else from being written to InfluxDB.
The text was updated successfully, but these errors were encountered: