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

Nightly Branch reports all collections as duplicate #1772

Closed
wellingssimon opened this issue Dec 13, 2023 · 12 comments
Closed

Nightly Branch reports all collections as duplicate #1772

wellingssimon opened this issue Dec 13, 2023 · 12 comments
Assignees
Labels
bug Bug is with Plex Meta Manager

Comments

@wellingssimon
Copy link

Version Number

1.19.1-nightly50

What branch are you on?

nightly

Describe the Bug

I switched to the nightly branch some time ago as it resolved some issues I was having at that point but from some time yesterday each scheduled run has failed:

|========================================= Warning Summary ==========================================|
| |
| Count | Message |
|=======|============================================================================================|
| 2 | Config Warning: Skipping duplicate collection: "Trending Now" |
| 2 | Config Warning: Skipping duplicate collection: "Most Watched This Week" |
| 2 | Config Warning: Skipping duplicate collection: "Most Watched This Year" |
| 1 | Config Warning: Skipping duplicate collection: "Netflix" |
| 1 | Config Warning: Skipping duplicate collection: "Marvel Cinematic Universe" |
| 1 | Config Warning: Skipping duplicate collection: "DC Extended Universe" |
| |
|========================================== Error Summary ===========================================|
| |
| Count | Message |
|=======|============================================================================================|
| 2 | YAML Error: metadata attribute is required |
| |
|====================================================================================================|
| Finished 11:25 Run |
| Version: 1.19.1-nightly50 |
| Finished: 11:25:33 2023-12-13 Run Time: 0:00:03 |
|====================================================================================================|

Every collection reports as a duplicate. I am certain I do not have duplicate collections configured.

The same setup running the develop branch works correctly.

Relevant Collection/Overlay/Playlist Definition

No response

Logs

No response

@wellingssimon wellingssimon added bug Bug is with Plex Meta Manager status:not-yet-viewed I haven't reviewed the Feature or Bug yet labels Dec 13, 2023
@hdemel
Copy link

hdemel commented Dec 13, 2023

Reporting the exact same behaviour. Rolling back to the main branch with the same configuration files yields no error so does seem to be something in the new nightly.

@YozoraXCII
Copy link
Contributor

YozoraXCII commented Dec 13, 2023

Can we have a log of this behaviour please?

As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

@wellingssimon
Copy link
Author

Can we have a log of this behaviour please?

As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

I can get a log later this evening. The standard meta.log?
I’ve already switched to the develop branch and it is working as expected but will switch back to nightly to get the log file for you. Thanks.

@YozoraXCII
Copy link
Contributor

YozoraXCII commented Dec 13, 2023

Can we have a log of this behaviour please?
As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

I can get a log later this evening. The standard meta.log? I’ve already switched to the develop branch and it is working as expected but will switch back to nightly to get the log file for you. Thanks.

If you've only done one run, then meta.log.1/meta.1.log would be the "n-1" log, you can check the log header which will tell you what branch was running.

@wellingssimon
Copy link
Author

Can we have a log of this behaviour please?
As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

I can get a log later this evening. The standard meta.log? I’ve already switched to the develop branch and it is working as expected but will switch back to nightly to get the log file for you. Thanks.

If you've only done one run, then meta.log.1/meta.1.log would be the "n-1" log, you can check the log header which will tell you what branch was running.

Meta log attached using nightly build

meta.log

@YozoraXCII
Copy link
Contributor

Can we have a log of this behaviour please?
As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

I can get a log later this evening. The standard meta.log? I’ve already switched to the develop branch and it is working as expected but will switch back to nightly to get the log file for you. Thanks.

If you've only done one run, then meta.log.1/meta.1.log would be the "n-1" log, you can check the log header which will tell you what branch was running.

Meta log attached using nightly build

meta.log

Thanks

Can you send me the contents of /config/TV Shows.yml

@wellingssimon
Copy link
Author

Can we have a log of this behaviour please?
As a side-note I would suggest using develop as we are reworking some things in nightly, but I would really appreciate those logs.

I can get a log later this evening. The standard meta.log? I’ve already switched to the develop branch and it is working as expected but will switch back to nightly to get the log file for you. Thanks.

If you've only done one run, then meta.log.1/meta.1.log would be the "n-1" log, you can check the log header which will tell you what branch was running.

Meta log attached using nightly build
meta.log

Thanks

Can you send me the contents of /config/TV Shows.yml

TV Shows and Movies config attached.

pmm.zip

If you spot any other obvious improvements I can make, hints would be appreciated ;)

@YozoraXCII
Copy link
Contributor

Thanks - we know why this is happening, just trying to break it down.

Are you on the Discord? Can chat easier there if you want.

@YozoraXCII
Copy link
Contributor

This should be fixed in nightly54

@wellingssimon
Copy link
Author

This should be fixed in nightly54

Really appreciate the efforts to get this fixed so quickly. You definitely deserve the sponsorship money for this kind of response. Off topic, I read that FlixPatrol has gone subscription based which has broke the integration. Have you considered (is it even possible) to charge PMM users a small fee to cover the costs of that?

@chazlarson
Copy link
Contributor

The subscription is insanely expensive, and chances are the sort of use PMM would put it to would not be allowed, anyways.

@JohnFawkes
Copy link
Contributor

This should be fixed in nightly54

Really appreciate the efforts to get this fixed so quickly. You definitely deserve the sponsorship money for this kind of response. Off topic, I read that FlixPatrol has gone subscription based which has broke the integration. Have you considered (is it even possible) to charge PMM users a small fee to cover the costs of that?

its like 50k a month for api access. Flixpatrol is in nightly and develop versions of pmm anyway

@meisnate12 meisnate12 removed the status:not-yet-viewed I haven't reviewed the Feature or Bug yet label Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug is with Plex Meta Manager
Projects
None yet
Development

No branches or pull requests

6 participants