New posts from Percona Blog not reaching the aggregator.

[jfg956]

New post: https://www.percona.com/blog/is-oracle-finally-killing-mysql/

[jfg956]

The post is in Percona feed (https://www.percona.com/blog/feed/): percona_com_feed.xml.txt

But it is not in the siftrss feed (https://siftrss.com/f/Y9ajk6YJVo): siftrss_Y9ajk6YJVo.xml.txt

Percona feed has this:

<lastBuildDate>Mon, 10 Jun 2024 13:00:10 +0000</lastBuildDate>

But siftrss has this:

<lastBuildDate>Fri, 07 Jun 2024 13:46:32 +0000</lastBuildDate>

It looks like siftrss is not getting the most up-to-date Percona feed.

[jfg956]

Reported to siftrss on Twitter: https://x.com/jfg956/status/1800206419339481177

[jfg956]

It thought this might be a caching problem on Percona's side, and it might be. My HTTP-foo is not great, but from below (Expires), I gather that the feed might be cached for 24 hours. Maybe this will solve itself tomorrow.

$ wget -q -S https://www.percona.com/blog/feed/
  HTTP/1.1 200 OK
  Date: Mon, 10 Jun 2024 16:50:14 GMT
  Content-Type: application/rss+xml; charset=UTF-8
  Transfer-Encoding: chunked
  Connection: keep-alive
  CF-Ray: 891adbf79b0cab21-YYZ
  CF-Cache-Status: HIT
  Age: 13384
  Cache-Control: public, max-age=86247
  ETag: W/"f6d493b6a12fdf5de8d01e334beddd5f"
  Expires: Tue, 11 Jun 2024 13:04:37 GMT
  Last-Modified: Mon, 10 Jun 2024 13:04:37 GMT
  Link: <https://www.percona.com/blog/>; rel="canonical"
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
  Vary: Accept-Encoding,User-Agent
  cf-apo-via: origin,feed
  permissions-policy: geolocation=self
  pragma: public
  referrer-policy: no-referrer-when-downgrade
  x-content-type-options: nosniff
  x-frame-options: SAMEORIGIN
  Server: cloudflare

[jfg956]

I checked the log in more details...

Usually, I have this when the feed is unchanged:

$ grep -e 'fetching feed.*com_percona_database_blog_filtered' -A 1 pluto_2024-06-10_06-00-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] no change; md5 digests match; skipping parsing feed

This is what I have when there is a change:

$ grep -e 'fetching feed.*com_percona_database_blog_filtered' -A 1 pluto_2024-06-11_13-00-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] Before parsing feed >com_percona_database_blog_filtered<...

Doing some tests...

~/planet/log$ ls -t | grep "log$" | head -n 200 | while read f; do echo; echo "File:" $f; grep -e 'fetching feed.*com_percona_database_blog_filtered' -A 1 $f; done > t
$ grep File t | head -n 1
File: pluto_2024-06-11_16-20-01.log
$ grep File t | tail -n 1
File: pluto_2024-06-08_22-00-01.log
$ grep "Before parsing" t -B 2
File: pluto_2024-06-11_13-00-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] Before parsing feed >com_percona_database_blog_filtered<...
--
File: pluto_2024-06-11_00-20-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] Before parsing feed >com_percona_database_blog_filtered<...
--
File: pluto_2024-06-10_21-40-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] Before parsing feed >com_percona_database_blog_filtered<...
--
File: pluto_2024-06-10_18-40-01.log
[info] OK - fetching feed 'com_percona_database_blog_filtered' - HTTP status 200 OK
[info] Before parsing feed >com_percona_database_blog_filtered<...

So it looks like the change reached us at 2024-06-10_18-40-01.

[jfg956]

Maybe the cache is on the CloudFlare side: https://x.com/jfg956/status/1800568188255764720

Anyhow, closing.