Klaas van Schelven 1eb65a7790 Release worker_semaphore when failing to create worker ...

exposed when playing around with arbitrary Tasks in a shell; this created
workers I could not run, which would put the foreman in a 'waiting for available threads'
mode.

I briefly looked at the rest of that loop to see whether more exception handling
is necessary, but TBH I don't think we can reasonably recover from e.g. task.delete()
failing (or at least I don't want to think about it now)

2024-07-05 15:58:15 +02:00

..

management

Add checksnappea command

2024-05-17 12:03:40 +02:00

migrations

Pea -> Task

2024-04-19 21:29:04 +02:00

__init__.py

Explicit error message for malformed task name

2024-07-05 15:54:55 +02:00

admin.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

apps.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

datastructures.py

Convert snappea 'wakeup' signal to inotify-based

2024-04-22 15:34:33 +02:00

decorators.py

Performance logging of Snappea task create/delete

2024-05-22 17:45:28 +02:00

example_tasks.py

Snappea: logging

2024-04-23 11:28:07 +02:00

foreman.py

Release worker_semaphore when failing to create worker

2024-07-05 15:58:15 +02:00

models.py

Fix typo

2024-05-17 15:52:43 +02:00

settings.py

Add missing file

2024-04-24 12:30:25 +02:00

tests.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

views.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00