One unreachable invalidation URL stops purges to the others
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start at API Platform's SurrogateKeysPurger::purge() and trace the bundle purger entry point, focusing on the per-chunk and per-URL loop described in the issue. Done means a failed invalidation URL does not prevent later chunks or other URLs from being attempted, while failures remain handled consistently with #311.
Written by the indexing model from the issue text.
Description
Found under #311. API Platform's SurrogateKeysPurger::purge() sends one request per chunk per invalidation URL in a loop. The first failure throws out of purge(), and after #311 it is logged and swallowed. That abandons the rest of the loop, so later header chunks and any other invalidation URLs are never sent for that flush.
With a single cache (the CWA template) this makes no difference. With several caches, one of them being down leaves the others stale for up to s-maxage.
The loop is in API Platform, so a fix is either upstream, or a bundle purger that sends to each URL independently and collects failures.
- Dominant language
- PHP
- Stars
- 32
- Forks
- 8
- Avg merge
- 58m
- Merged PRs (30d)
- 147
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from components-web-app/api-components-bundle
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
components-web-app/api-components-bundle#333 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
components-web-app/api-components-bundle#259 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
components-web-app/api-components-bundle#186 ·
Maintainers usually reply within 1 day
All issues in components-web-app/api-components-bundle
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
PHP workflow streaming requests buffer the full SSE responsePossibly taken @Winoren claimed this today. Openreview: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langgenius/dify#44270 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug customer-reported
Difficulty 1/5 Under an hour Newbie friendliness 90/100
MagnaCapax/PMSS#1085 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
nunomaduro/collision#375 ·