Commit Graph

9 Commits

Author SHA1 Message Date
Klaas van Schelven
32be257172 Fail to start when using non-sqlite for snappea
See #252

This is not backwards compatible (it will now hard-break), but given snappea's
rather particular design decisions this is probably for the best, and given
what else was just discovered on #252 I strongly doubt anyone was actually using
it in such setups anyway.
2025-10-23 22:11:57 +02:00
Klaas van Schelven
918b1ef54c Add ids to 2 system-checks 2025-02-18 12:10:32 +01:00
Klaas van Schelven
705cf43fc2 Remove doc-TODO 2025-01-24 11:43:28 +01:00
Klaas van Schelven
cf23ba707e Warn about top-level settings 2025-01-24 11:40:13 +01:00
Klaas van Schelven
259069f6e2 Explicit error message for malformed task name 2024-07-05 15:54:55 +02:00
Klaas van Schelven
08330dd274 Use proper thread-local for wakeup_file uuid part
Stackoverflow said "In Python, everything is shared, except for function-local
variables (because each function call gets its own set of locals, and threads
are always separate function calls.) "

whatever was meant exactly by that, it's not true for us, because our functions
are called on-import, and the vars-in-closure are shared between threads. i.e.:

>>> from threading import Thread
>>> def closure():
...   l = []
...   def inner():
...     l.append("x")
...     print(len(l))
...   return inner
...
>>> inner = closure()
>>> thread = Thread(target=inner)
>>> thread.start()
1
>>> thread = Thread(target=inner)
>>> thread.start()
2
2024-04-23 09:42:24 +02:00
Klaas van Schelven
1fc1da1ceb Implement the registry's 'autodiscover'
actually: not autodiscover on-bootup, but just try to import the tasks
when you actually need them. This makes it so that we can avoid the whole
of the Django app-loading magical machinery
2024-04-22 22:37:47 +02:00
Klaas van Schelven
3c106521bc snappea WIP commit 2024-04-19 16:21:42 +02:00
Klaas van Schelven
94d0fda6ab Midway checking to preserve state 2024-04-19 11:58:20 +02:00