benoit74

We have a task with more details about the error: https://farm.openzim.org/pipeline/73d37947-2501-4075-bddb-8b0ea4b8c504/debug Returned response was : ``` [2025-10-18 15:31:01,332: ERROR] unexpected error while decoding server response: 502 Bad Gateway 502 Bad...

Another issue which needs to be fixed at Zimfarm level this time: https://farm.openzim.org/pipeline/8ccd39b1-fa95-45a2-82c2-af50486f9c25/debug ``` [2025-10-21 15:40:30,776: ERROR] unexpected error while decoding server response: 413 Request Entity Too Large 413 Request...

Indeed, this means this is k8s ingress which blocked the "too big" zimcheck output. Let's open a dedicated issue.

Yet another issue of the `502 Bad Gateway` issue despite now having two containers to process the load: https://farm.openzim.org/pipeline/7a815556-53bd-46e1-99a6-c33e521a0c6f/debug I don't get why we suddenly get these errors which never...

@elfkuzco for the time being, let's do something simple. After some thought, retrying all API calls is risky because it could have adverse effects if the Zimfarm already processed the...

#1555 does not seem to produce expected effect, https://farm.openzim.org/pipeline/1e15becd-b7dc-4fd7-92ef-b2329204b3c1/debug still failed during a patch operation.

See for instance impact on `badger3`: ``` zim3 ~ # find /srv -name *.zim -exec ls -lh {} \; -rw-r--r-- 1 root root 236G Nov 20 22:36 /srv/zimfarm/data/f73049af-8d6e-474d-979a-3d4d16c6bd3c/gutenberg_mul_all_2025-11.zim -rw-r--r-- 1...

@Abhigyan-GG I'm quite sure we are not yet certain about what we want to implement. But the receiver part is indeed a mostly mandatory one. Big question is "how feasible...

This does not looks like modifications done at the `receiver` but modifications done in the `backend`. We might probably do that, but this is the easy part. What I'm searching...

In general, it is best to have everything in Github issues so that everyone can find it again in the future. And having discussions available helps to understand why we...