Half of my feeds show a wrong yellow triangle in beta 6

[neilt]

Describe the bug

Half of my feeds show yellow triangle with the release of beta 6. The error message is "An error occurred when this feed was last refreshed".

1. Quitting and restarting Vienna did not fix the problems

2. Going to each feed and manually "Refresh Selected Subscription" fixes it. As far as I can tell the feed refreshed, but show the yellow triangle erroneously.

3. In the screen shot below https://github.com/postgres/postgres/commits/master.atom had a yellow triangle until I manually refreshed it.

4. In the screen shot below, https://www.postgresql.org/news.rss shows the problem.

To Reproduce
Not sure

Screenshots

Please complete the following information:

• Vienna Version 3.10.0 Beta 6 :2be6cde9: (8710)

ProductName: macOS
ProductVersion: 15.6.1
BuildVersion: 24G90

[neilt]

Actually now that I have more time after updating from beta 5 to 6, I can see that all of the feeds marked in yellow are failing with a time out. So I have to go into each individual feed and manually refresh to see anything new.

[barijaona]

Could be related to #2006, but I don't see why
Does using "Refresh All Subscriptions" after failure improve things ?

[neilt]

Could be related to #2006, but I don't see why Does using "Refresh All Subscriptions" after failure improve things ?

No, the only thing that works is manually refreshing each feed individually.

[neilt]

It appears to me that some error is stopping all feeds from refreshing because some of the feeds at the top refresh automatically and the ones at the bottom always fail.

So I started at the bottom, selecting small batches of feeds to manually update and each batch updated fine all of the way to the top.

I also noticed that I have a bunch of feeds that normally do not work. I had not got around to deleting them. But am deleting then now.

Is it possible that having a bunch of feeds that are no longer accessible somehow messes up the queuing logic which worked fine in Beta 5?

[barijaona]

Are you fetching directly from websites or fetching from an OpenReader / GoogleReader server ?

[neilt]

Are you fetching directly from websites or fetching from an OpenReader / GoogleReader server ?

Directly from websites.

[neilt]

So deleting the 50+ feeds that no longer worked seems to have partially rectified the problem. The feeds appear to update now when Vienna is opened, but they don't all update. I still have to manually select a group of feeds and update them.

These feeds were largely in folders and since the yellow warning did not populate up to the parent folder, I did not realize how many feeds were bad.

My use case is not normal in that I only use Vienna to monitor feeds that are being downloaded, analyzed and saved by my custom code feed reader, which automatically marks feeds as unreachable. That is why I had so many bad feeds.

My guess is that a valid test case would be to create a bunch (50+) of bad feeds, then at the end a couple of good feeds and you'll see that the good feeds never get read for some reason.

[barijaona]

Can you send me an OPML with a bunch of bad feeds ? ("File" -> "Export subscriptions", then select "Export selected subscriptions")

[neilt]

Can you send me an OPML with a bunch of bad feeds ? ("File" -> "Export subscriptions", then select "Export selected subscriptions")

Not easily. I just wanted it to work, so I just deleted all of the bad ones. Afterwords I kicked myself because I should have exported before deleting. I'll see what I can do.