PodFetch: panicked when Polling for new episodes

Describe the bug

I am getting different panicked errors like the below, both when Polling for new episodes or refreshing. After I get a panicked, it will not do Pollingnagain, and I have to restart the container.

thread ‘<unnamed>’ panicked at src/service/podcast_episode_service.rs:121:86: called Result::unwrap() on an Err value: Eof note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I have tried removing some podcasts that were the source for this, but it seems random. It do not happen all the time, so if I manually refresh, it might refresh fine.

Is there a way that I can identify what podcasts generate the issue?

I absolute love this Project, just wish I didn’t have to manually restart app container five times a day.

Thank you.

Reproduction

Random, but happens every day when pooling for episodes.

System Info

Docker Container behind nginx reverce proxy.

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

Now it’s working, Thank you !!! Log now shows this: 2024-02-23T05:00:37.147298526Z 2024-02-23T05:00:37 ℹ️ - Polling for new episodes successful 2024-02-23T06:00:00.517630201Z 2024-02-23T06:00:00 ℹ️ - Polling for new episodes 2024-02-23T06:00:23.906923407Z 2024-02-23T06:00:23 ℹ️ - Error parsing podcast “” with cause Eof 2024-02-23T06:00:23.908792474Z 2024-02-23T06:00:23 ❌ - Error polling for new episodes: Bad Request: Error parsing podcast Eof 2024-02-23T07:00:00.276985953Z 2024-02-23T07:00:00 ℹ️ - Polling for new episodes 2024-02-23T07:00:04.743714425Z 2024-02-23T07:00:04 ℹ️ - Error parsing podcast “” with cause Eof 2024-02-23T07:00:04.745260860Z 2024-02-23T07:00:04 ❌ - Error polling for new episodes: Bad Request: Error parsing podcast Eof 2024-02-23T08:00:00.117844670Z 2024-02-23T08:00:00 ℹ️ - Polling for new episodes 2024-02-23T08:00:07.893052045Z 2024-02-23T08:00:07 ℹ️ - Downloading podcast episode: Back at Base: Episode 3 - A Shot at Redemption 2024-02-23T08:00:38.960142100Z 2024-02-23T08:00:38 ℹ️ - Polling for new episodes successful 2024-02-23T09:00:00.335919427Z 2024-02-23T09:00:00 ℹ️ - Polling for new episodes 2024-02-23T09:00:13.184533504Z 2024-02-23T09:00:13 ℹ️ - Downloading podcast episode: Fredag 23. feb. 2024 2024-02-23T09:00:39.375255389Z 2024-02-23T09:00:39 ℹ️ - Polling for new episodes successful Is there a way to see what Podcast/Episode is failing?

I added the title

That is perfect.

I now noised this: 2024-03-04T13:00:00.677573923Z 2024-03-04T13:00:00 ℹ️ - Polling for new episodes 2024-03-04T13:00:04.723122874Z 2024-03-04T13:00:04 ℹ️ - Error parsing podcast Borgen unplugged “” with cause Eof 2024-03-04T13:00:04.724761283Z 2024-03-04T13:00:04 ❌ - Error polling for new episodes: Bad Request: Error parsing podcast Borgen unplugged with cause Eof 2024-03-04T14:00:00.094149944Z 2024-03-04T14:00:00 ℹ️ - Polling for new episodes 2024-03-04T14:00:34.452353765Z 2024-03-04T14:00:34 ℹ️ - Polling for new episodes successful

And the wired thing is that there is no new episode to download on that podcast, I’ll check if this one specifically fails randomly. Thank you.

Thank you. I have now updated, and will upload the logs for both DB and App container if the error persists.