element-hq / element-integration-manager

Element Integration Manager related issues
6 stars 1 forks source link

RSS Feed started to skip entries again #108

Open bkil opened 11 months ago

bkil commented 11 months ago

A continuation of #99 as multiple users are impacted.

You can see for yourself in our case by comparing the RSS entries posted in the matrix rooms vs. the RSS XML changes (added lines) committed to the git repo being followed

The following xml files are hooked up to this single room (about 90% of the updates): changeset-discuss, gitlab-piclayer, mastodon-doudouosm, mastodon-openstreetmap, osm-notes, wiki.

bkil commented 11 months ago

A specific one that is missing for example is this one: https://github.com/bkil-bot/osm-rss-juggler/commit/df7af58e3d459b13c5cb84cd7c91474235a6816a

You can't find any recent RSS bot message by the bot mentioning any of the ids of 3708296, 3701551, 3701558.

There are possibly many more messages missing (I don't have a full list), but I just clicked on a recent one to give you an example. If I had to implement a monitoring bot side by side to see which entries are posted by the RSS bot and which ones are missing, I could mind as well implement our own RSS bot instead.

JokerGermany commented 9 months ago

Happened again in this room for the last two weeks Room: https://matrix.to/#/#messenger-de:matrix.org Feed URL: https://matrix.org/blog/feed

JokerGermany commented 9 months ago

Serveral rooms and feed urls are affected again...

vranki commented 5 months ago

Looks like feeds bot is also not reading Mastodon generated rss feeds. For example https://mementomori.social/@instanssi.rss does not provide any updates.

bkil commented 5 months ago

This issue is cloned to https://github.com/matrix-org/matrix-hookshot/issues/844 if the issue is related to the source code, not to operational reasons.

Half-Shot commented 5 months ago

So I think the situation will be fixed by changes to Hookshot (https://github.com/matrix-org/matrix-hookshot/issues/844), and we can close this issue when that issue is resolved. For now, let's keep this open.