Watchlist item only added upon Watchlistarr restart

[hstamas]

Got Watchlistarr up and running via Docker on an M1 Mac. If I add a movie to my Plex watchlist, Radarr will only pick it up if I stop and restart the Watchlistarr Docker container.

I am extremely new to Docker so maybe I dont have something set correctly?

[tiredjohn]

Same issue here, also running on docker – but the refresh has fallen back to every 19 minutes, or whenever I restart the container. Seems like REFRESH_INTERVAL_SECONDS isn't being respected. (I'm using Plex Pass)

[Redryan243]

Same issue here. My logs show it defaulting to a 60 second interval, even though my config specifies 10 seconds. It is working at the 60 second at least for me.
Edit: multiple settings from config do not seem to be used, even though I uncommented and updated them. The other ones seems to be tags and profile, but it is taking my baseurl

[hstamas]

Glad it not just me! I dont quite know how to set up the config file so I am just using what ever defaults. I do have a Plexpass and I see in the logs that it is recognized as such.

[tiredjohn]

I've looked into this and the issue seems to be that Plex has added server-side caching to their RSS feeds. The refresh interval is working as intended, but the server cache means that it keeps fetching the same data regardless of the update frequency.

I've made a change and submitted a PR to append a random 10 character parameter to the RSS URL each time it's used, which fixes it for me: #183

(Docker hub fork here, in case anyone doesn't want to wait: https://hub.docker.com/r/tiredjohn/watchlistarr/)

[strangedesign13]

@tiredjohn thanks for this! Totally solved my problem!

[hstamas]

@tiredjohn any idea why I am seeing this warning when I pull your image? Im on a Mac M1.

"AMD64 - Image may have poor performance if run via emulation"

UPDATE: Running your version results in the container exiting with an error in the logs saying that my CPU is "starved" etc.

[tiredjohn]

@tiredjohn any idea why I am seeing this warning when I pull your image? Im on a Mac M1.

I've added an arm64 build for you, try pulling it again.

[hstamas]

Perfect @tiredjohn , thank you!

Probably doesn't come as a surprise to anyone that I am a complete Docker noob but this is forcing me to learn the basics at least!

Question. If I ran the build command that nylonee has listed at the bottom of his Github page (docker build -t nylonee/watchlistarr:latest -f docker/Dockerfile ), would that have accomplished the same thing? Given me an image that was comparable with arm64 machines (my Mac M1)?

[tiredjohn]

@hstamas My version is tiredjohn/watchlistarr, so "docker pull tiredjohn/watchlistarr:latest" should do it for you.

[Abolfazl]

@tiredjohn I setup you version of watchlistarr and it fixed the sync issue. However I am having an issue where I keep getting an error that [WARNING] Your app's responsiveness to a new asynchronous event (such as a new connection, an upstream response, or a timer) was in excess of 100 milliseconds. Your CPU is probably starving. Consider increasing the granularity of your delays or adding more cedes. This may also be a sign that you are unintentionally running blocking I/O operations (such as File or InetAddress) without the blocking combinator.. I think the original nylonee/watchlistarr image was producing this error too.

Do you know what might be causing it?

[nylonee]

Thanks for your help @tiredjohn and for the debugging all, I've pushed a fix (#190) to beta and will release it to the main docker tag soon