benoit74

Detect failing workers

2

We should not let a failing worker (considering that all its tasks are failing early) to continue to get new tasks

https://github.com/openzim/zimfarm/issues/797 is not completely fixed. We forgot to fix the "Workers" screen to use `original_schedule_name` when `schedule_name` is missing  And we forgot to fix the individual "Task" screen as...

Scheduling logic is not handling nicely the case where multiple web APIs are requested by a single worker

2

- Location: API ## Problem In the logs of youzim.it, we have found multiple "we have no preventing tasks. oops" errors. Root cause/fix is not yet identified but: - this...

Create documentation for content editors about zimit offliner

2

Just like we have done recently for [Youtube offliner](https://github.com/openzim/zimfarm/wiki/Youtube-scraper-configuration-and-debug), we need to create a documentation for Zimit offliner. Current documentation about [Zimit Ticket Lifecycle](https://github.com/openzim/zimfarm/wiki/Ticket-Lifecycle-(Zimit)) is mostly useless since it only...

For now, the only purge of tasks is done at the schedule level, where we keep only the 10 most recent tasks for every schedule. Should we (especially for youzim.it)...

Validate schedule configurations for minLength/maxLength and pattern

1

In the `/offliners` API, return minLength, maxLength and pattern. Adapt offliner definitions (new field type to create) so that these values can be sourced from the definitions and automatically provided...

Operations performed on Wasabi (typically updating the S3 policy when a worker IP changes) have no timeout. This means that DB locks arise when Wasabi is not responding because all...

Detect duplicate schedule names when cloning a schedule

7

- Location: API / UI ## Problem When cloning a schedule, if the new chosen name is already in used, this is only detected at the DB level, raising a...

HTTP HEAD verb is raising 500 errors

3

It looks like all HTTP HEAD operations on implemented endpoints are returning an HTTP 500 error. This is returning an HTTP 500: ``` curl -I 'http://localhost:8000/v1/schedules/?skip=0&limit=10' curl -I 'http://localhost:8000/v1/tasks/?skip=0&limit=10' curl...

"Actual content hidden" is always displayed on secret flags

2

- Location: UI The "Actual content hidden" is displayed on recipe / task flags even when the content is not hidden because the user is logged in, see below.