-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
SickRage API fails #144
Comments
@shiitake this look like its to do with your changes. Any idea? |
Just confirming this one also, exactly the same problem here. |
I'll take a look when I get home. @shiitake if you have any ideas please let me know. |
@tidusjar I can test out the dev build. Just linkme and I'll let you know what On Thu, Apr 7, 2016, 8:28 AM Jamie notifications@github.com wrote:
|
@tidusjar That fixed it for me! |
@Codehhh Excellent. It settings the seasons wanted correctly in Sickrage? (If you selected First season or Latest)? |
Not sure what changed, but I'm getting "An error has occurred" First Season request - sets first season as wanted Logs are attached for further analysis |
Looking at the logs this is what we got back from SickRage:
But that should have appeared in the notification for you. Latest season will set the most recent season as 'Wanted' Can you delete the log file and repo it and then upload the logs? |
by repo it do you mean add it to git? |
@Codehhh Sorry, reproduce the error. |
The Bachelor: All Seasons |
I can't seem to find out what is going on. What timezone are you in? Can we do a remote session so I can take a look? |
I'm in EST. I will be free in roughly 3 hours, have class until then. Let me know when you're free and how we can communicate more privately. |
Ok I should be free around them. We can communicate privately on Gitter. |
Fixed. |
Plex Requests.Net Version:
v1.6.0
Operating System:
ReadyNASOS 6.4.2 (based on Debian 7)
Mono Version:
mono 4.2.3
SickRage Version:
SickRage 2016.03.28-2
Reproduction Steps:
Request TV. The show is still added, but "Something went wrong" popped up.
The text was updated successfully, but these errors were encountered: