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

CouchPotato cache scheduler not working #334

Closed
Drewster727 opened this issue Jun 21, 2016 · 17 comments
Closed

CouchPotato cache scheduler not working #334

Drewster727 opened this issue Jun 21, 2016 · 17 comments
Assignees

Comments

@Drewster727
Copy link
Contributor

Plex Requests.Net Version: 1.8.0

Operating System: Ubuntu 15.10

Mono Version: 4.2.3

Applicable Logs (from /logs/ directory or the Admin page):

Reproduction Steps:

Reset your database so there are no "Requests" anymore. Load up 1.8.0 and setup couchpotato. I have already got Independence Day: Resurgence requested in CP:
image

Give PR some time to do the caching, check the Scheduled Jobs page and verify it ran the cacher for CP. Then search for Independence Day. You'll see a "Request" button when it should show requested.

image

This may be happening with Sonarr/SickRage as well, not sure.

@tidusjar
Copy link
Member

Thats strange, as I didn't make any changes around those areas...

@tidusjar
Copy link
Member

i'll pull the release and investigate

@Drewster727
Copy link
Contributor Author

image

I'm seeing that when it tries to connect to CP. Are you seeing that as well?

@tidusjar
Copy link
Member

I have not seen that. I'll have to see what's going on when I get home from work.

@Drewster727
Copy link
Contributor Author

It appears to be successfully connecting to CP and obtaining the data, but it cannot deserialize the json array properly (using RestSharp)

@tidusjar
Copy link
Member

Either we have changed a type, or there is a new/changed type that we are not expecting...

@Drewster727
Copy link
Contributor Author

yea, I'm guessing the CP json changed?

@tidusjar
Copy link
Member

Unlikely if an older version works.
I do remember changing one of the types slightly as someone's CP json was structured a bit differently, but i'm pretty sure it still worked

Date: Tue, 21 Jun 2016 07:39:53 -0700
From: notifications@github.com
To: PlexRequests.Net@noreply.github.com
CC: jamierees@outlook.com; assign@noreply.github.com
Subject: Re: [tidusjar/PlexRequests.Net] CouchPotato cache scheduler not working (#334)

yea, I'm guessing the CP json changed?


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

@Drewster727
Copy link
Contributor Author

Drewster727 commented Jun 21, 2016

I narrowed it down to the "Info" class of our CP object, not sure which property, but commenting all of them but the tmdb_id fixes the issue:

image

@tidusjar
Copy link
Member

Can you send me the Json response you get?

Date: Tue, 21 Jun 2016 07:47:35 -0700
From: notifications@github.com
To: PlexRequests.Net@noreply.github.com
CC: jamierees@outlook.com; assign@noreply.github.com
Subject: Re: [tidusjar/PlexRequests.Net] CouchPotato cache scheduler not working (#334)

I narrowed it down to the "Info" property of our CP object, not sure which property, but commenting all of them but the tmdb_id fixes the issue:


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

@Drewster727
Copy link
Contributor Author

looks like the release_date property is the culprit

@Drewster727
Copy link
Contributor Author

Here's an interesting item I found in the JSON...

sometimes the release_date is: "release_date": []
and sometimes it is: "release_date": {"dvd": 0, "expires": 1468174162, "theater": 0, "bluray": false}

so it can be an array or an object...

@Drewster727
Copy link
Contributor Author

@tidusjar
Copy link
Member

Hmmm... The issue would be that we would then do that for everything... I am working on refactoring the Api stuff because it's horrible to work with.

It's either an empty array or an object... well this sounds fun...

@Drewster727
Copy link
Contributor Author

I'm going to add that as a temp workaround for CP in the meantime. check my latest commit, it works like a charm.

Drewster727 pushed a commit that referenced this issue Jun 21, 2016
@tidusjar
Copy link
Member

Oh it's done in the request and not the response. Yeah looks good!

@Drewster727
Copy link
Contributor Author

yea, and of course my git screwed up again and committed the entire file(s) instead of just my line changes... so weird.

tidusjar pushed a commit that referenced this issue Jun 21, 2016
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

2 participants