Skip to content
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

Closed
SenorSmartyPants opened this issue May 13, 2020 · 5 comments
Closed

API getWanted returns 500 error #282

SenorSmartyPants opened this issue May 13, 2020 · 5 comments
Assignees
Labels
bug Something isn't working feedback needed

Comments

@SenorSmartyPants
Copy link

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):

  • OS: ARM Docker
  • Branch / commit: build 26c9d78

Additional information
getUpcoming works

@evilhero
Copy link
Collaborator

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 b'this is the issue title.' - have to track down the culprit and then run a db conversion on the bytes column....

@evilhero evilhero self-assigned this May 15, 2020
@evilhero evilhero added the bug Something isn't working label May 15, 2020
evilhero added a commit that referenced this issue May 25, 2020
… db conversion is still required to be completed), better check of comlocation being set prior to attempting to create a series directory.
@SenorSmartyPants
Copy link
Author

pulled from python3-dev today and API is working again.

@SenorSmartyPants
Copy link
Author

And the problem is back again.
carepackage.zip

@evilhero
Copy link
Collaborator

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).

@evilhero evilhero reopened this May 27, 2020
@mylar3 mylar3 reopened this Jun 1, 2020
@evilhero evilhero reopened this Aug 13, 2020
@barbequesauce
Copy link
Collaborator

Still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working feedback needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants