Error fetching gpodder data: Could not update data for device 'home-assistant-jh' - list index out of range

[jurgenhaas]

Version of the gpodder

2.0.0

Describe the bug

This problem already started with the latest 1.x version of gpodder and I was hoping that 2.x would fix it, but I still get this error in the logs:

2020-07-08 08:12:13 ERROR (MainThread) [custom_components.gpodder] Error fetching gpodder data: Could not update data for device 'home-assistant-jh' - list index out of range

There is no entity or content available inside of my home assistant instance. The problem started when I made some changes to my gpodder subscriptions and removed some of the urls in my account. So maybe the plugin is trying to fetch something that's no longer there?

gpodder configuration

It's now configured through the UI and as you can see from the log below, the credentials are ok.

Debug log

2020-07-08 09:00:06 INFO (MainThread) [custom_components.gpodder] 
-------------------------------------------------------------------
gpodder
Version: 2.0.0
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/gpodder/issues
-------------------------------------------------------------------

2020-07-08 09:00:08 DEBUG (MainThread) [custom_components.gpodder] 21 urls for device 'home-assistant-jh'
2020-07-08 09:00:17 ERROR (MainThread) [custom_components.gpodder] Error fetching gpodder data: Could not update data for device 'home-assistant-jh' - list index out of range
2020-07-08 09:00:17 DEBUG (MainThread) [custom_components.gpodder] Finished fetching gpodder data in 11.007 seconds
2020-07-08 09:00:38 DEBUG (MainThread) [custom_components.gpodder] 21 urls for device 'home-assistant-jh'

The last 3 lines repeat themselves every 30 seconds.

Please let me know if you need any additional information and BIG THANKS for maintaining this plugin.

[iantrich]

Do you have 21 subscriptions on the site?

[jurgenhaas]

Yes, it's 21 subscriptions.

[ludeeus]

It should not try anything that is no longer there.
The error is from the podcastparser which does not have an issue tracker so there is not really much to do.
And it's probably a result of an issue with one (more more) of the sources.

As a workaround:

1. Create a new device in gPodder
2. Add that device to this integration instead of the current one you are using.
3. Add one source to the device, until it breaks again.
4. Remove the one that breaks it, and add back the rest or remove that source from the home-assistant-jh device and you can use that again.

[jurgenhaas]

OK, found the feed which is causing the import to crash: https://gpodder.net/podcast/blick-uber-den-tellerrand-mit-dem-podpimp

I've then found another URL and tried with that: https://gpodder.net/podcast/blick-uber-den-tellerrand-4 but this feed also crashes the import. Maybe you can find out what's wrong?

Regardless of this specific feed, shouldn't it be the case that such an list index out of range error should be caught and handled by the plugin? I mean, if one feed is broken, just ignore it, maybe report it, but do not cause ALL the feeds from being unaccessible.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jurgenhaas]

Bump

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jurgenhaas]

Bump

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jurgenhaas]

@iantrich @ludeeus are you not planning to deal with this?

[ludeeus]

The issue is with podcastparser, the index error is handled and treated properly (if it was not you would have seen a stacktrace of the error) by this integration.

[jurgenhaas]

Well, if one of the subscribed urls is invalid, it doesn't have to kill everything, does it?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jurgenhaas]

Again, catching the error and processing the other feed would be expected.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.