-
Notifications
You must be signed in to change notification settings - Fork 115
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
API getWanted returns 500 error #282
Comments
Looks like there's some bytes objects being returned in the dict response and then it can't convert it to json because of the bytes. It's the Issue Name field that's causing problems, and I've seen this in the db where it's even displayed as |
… db conversion is still required to be completed), better check of comlocation being set prior to attempting to create a series directory.
pulled from python3-dev today and API is working again. |
And the problem is back again. |
Yep, was never meant to be totally fixed in PR #305 - was a partial attempt to stop the Issue Name field in the issues table from being written in the incorrect format going forward. In order to completely address this issue, everyone's DB has to have the Issue Name field converted properly so that the API can properly return the json response (amongst other things). Should be in the python3-dev branch by the end of week barring any unforseen problems with the testing aspect (code is done, just testing variations now). |
Still an issue? |
Describe the bug
http://host:8090/mylar/api?apikey=XXX&cmd=getWanted returns a 500 error.
CarePackage
carepackage.zip
Environment (please complete the following information):
Additional information
getUpcoming works
The text was updated successfully, but these errors were encountered: