After #2134 we have implemented a mechanism to block a Piwigo installation performing too many requests on piwigo.org to fetch the version list. By exploring the logs today, I realize we still have many blocked Piwigo. The requests looks like:
I can't be sure, but maybe it's a highly visited Piwigo. If 10 visitors open a page at the same time, as $conf['update_notify_last_check'] will be outdated for all of them, they will all perform the request to piwigo.org.
Let's add our unique_exec system (as for send_piwigo_infos.
After #2134 we have implemented a mechanism to block a Piwigo installation performing too many requests on piwigo.org to fetch the version list. By exploring the logs today, I realize we still have many blocked Piwigo. The requests looks like:
```
MariaDB [piwigo_site]> select * from all_versions_requests where origin='dc666919e8db219634c286a8497f68e188e10adf' order by occured_on desc;
+------------------------------------------+---------------------+
| origin | occured_on |
+------------------------------------------+---------------------+
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
| dc666919e8db219634c286a8497f68e188e10adf | 2026-01-04 20:35:16 |
+------------------------------------------+---------------------+
11 rows in set (0.001 sec)
```
As we can see, all requests in the same second.
I can't be sure, but maybe it's a highly visited Piwigo. If 10 visitors open a page at the same time, as `$conf['update_notify_last_check']` will be outdated for all of them, they will all perform the request to piwigo.org.
Let's add our unique_exec system (as for `send_piwigo_infos`.
<!-- github-sync-id:3779579334 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After #2134 we have implemented a mechanism to block a Piwigo installation performing too many requests on piwigo.org to fetch the version list. By exploring the logs today, I realize we still have many blocked Piwigo. The requests looks like:
As we can see, all requests in the same second.
I can't be sure, but maybe it's a highly visited Piwigo. If 10 visitors open a page at the same time, as
$conf['update_notify_last_check']will be outdated for all of them, they will all perform the request to piwigo.org.Let's add our unique_exec system (as for
send_piwigo_infos.