psychedelicious b2ea749c72 fix(mm): handle any error during installation ... Previously we only handled expected error types. If a different error was raised, the install job would end up in an unexpected state where it has failed and isn't doing anything, but its status is still running. This indirectly prevents the installer threads from exiting - they are waiting for all jobs to be completed, including the failed-but-still-running job. We need to handle any error here to prevent this.		2024-03-27 08:34:00 +11:00
..
api	feat(mm): revised list of starter models	2024-03-22 14:59:33 +11:00
assets/images	tweaks in response to psychedelicious review of PR	2023-07-24 09:23:51 -04:00
invocations	fix(nodes): esrgan model name typo	2024-03-22 02:22:19 -07:00
services	fix(mm): handle any error during installation	2024-03-27 08:34:00 +11:00
shared	tidy(nodes): move all field things to fields.py	2024-03-01 10:42:33 +11:00
util	feat(mm): move HF token helper to route	2024-03-20 15:05:25 +11:00
__init__.py	fix: make invocation_context.py accessible to mkdocs	2024-03-01 10:42:33 +11:00
api_app.py	feat: move all config-related initialization to app	2024-03-20 15:05:25 +11:00
run_app.py	feat: single app entrypoint with CLI arg parsing	2024-03-19 09:24:28 +11:00