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

Error generated when changing episode quailty #6783

Closed
johnvick opened this issue Jun 6, 2019 · 2 comments
Closed

Error generated when changing episode quailty #6783

johnvick opened this issue Jun 6, 2019 · 2 comments

Comments

@johnvick
Copy link

johnvick commented Jun 6, 2019

Branch: master
Commit: 6a21a6001b10827d14d450135bae61729b01edf1
Version: 0.3.2
Database: 44.14
Python Version: | 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516]
SSL Version: | OpenSSL 1.1.0j 20 Nov 2018
OS: | Linux-4.14.66+-armv7l-with-debian-9.9
Locale: | en_GB.UTF-8

Change episode quality leads to white screen and this error in logs:

2019-06-06 15:22:55 ERROR    Thread-61 :: [6a21a60] Exception generated: invalid literal for int() with base 10: 'Change status to:'
Traceback (most recent call last):
  File "/home/john/medusa/medusa/server/web/core/base.py", line 261, in async_call
    result = function(**kwargs)
  File "/home/john/medusa/medusa/server/web/home/handler.py", line 1592, in setStatus
    status = int(status)
ValueError: invalid literal for int() with base 10: 'Change status to:'

The episode quality is changed OK.

John

@triage-new-issues triage-new-issues bot added the triage Untriaged issue label Jun 6, 2019
@sharkykh sharkykh added Bug Confirmed Frontend and removed triage Untriaged issue labels Jun 6, 2019
@sharkykh sharkykh self-assigned this Jun 6, 2019
@sharkykh
Copy link
Contributor

sharkykh commented Jun 6, 2019

Oops. My bad.
Everything still works as intended.
It just generates an error because the "Change status to:" option didn't have a value (and I assumed wrong).
Will be fixed with #6784

@medariox
Copy link
Contributor

medariox commented Jun 6, 2019

Fixed with #6784

@medariox medariox closed this as completed Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants