hugo/bDS2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Close TD-18 Oban Lite evaluation

Browse Source
This commit is contained in:
Chili Palmer
2026-06-12 13:54:59 +02:00
parent abbcef594a
commit 28e08451e4
1 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
TECHDEBTS.md
View File

@@ -691,7 +691,19 @@ to `@stemmer_algorithms` keys; default `"en"` unchanged. Delete
**Acceptance.** Misclassification fixtures (umlaut-free German, accented-free **Acceptance.** Misclassification fixtures (umlaut-free German, accented-free
French) detect correctly; stemmer selection unchanged for English. French) detect correctly; stemmer selection unchanged for English.
### TD-18: Evaluate Oban (Lite engine) for durable jobs ### TD-18: Evaluate Oban (Lite engine) for durable jobs ✅ DONE (2026-06-12)
**Status: evaluated; no-go for now.** `BDS.Publishing` already persists
`PublishJob` rows and the suite proves those rows survive a
`BDS.Publishing` restart; what it does **not** provide is durable mid-upload
resume/retry, and the current desktop spec does not require that behavior.
Moving publishing to Oban Lite now would add another coordination layer on top
of `BDS.Tasks`, force a redesign of the in-memory SCP mtime cache in
`BDS.Publishing`, and complicate the existing Ecto sandbox/release split for a
benefit that is not yet part of the product contract. `BDS.Scripting.JobStore`
and `BDS.Tasks` remain intentionally in-memory: they provide UI/runtime job
tracking, not durable work queues. Re-open this only if real crash-recovery
requirements emerge and a spike shows acceptable desktop binary/startup impact.
**Context.** Three overlapping job systems exist: in-memory UI tasks **Context.** Three overlapping job systems exist: in-memory UI tasks
(`BDS.Tasks`), DB-persisted publish jobs (`Publishing` + `PublishJob` rows), (`BDS.Tasks`), DB-persisted publish jobs (`Publishing` + `PublishJob` rows),
@@ -712,8 +724,9 @@ check interplay with the test sandbox and with the `bds_mcp` release. Write
up a go/no-go with the spike branch. If no-go, document why in this file and up a go/no-go with the spike branch. If no-go, document why in this file and
close. close.
**Acceptance.** Decision documented; if go: publishing migrated first, with **Acceptance.** Decision documented. Outcome: no-go for now; publishing keeps
crash-recovery test (kill app mid-upload, job resumes/retries on restart). its current persisted-status model and the task closes without an Oban
migration.
### TD-19: Add credo, mix_audit (and consider sobelow) to the quality gates ### TD-19: Add credo, mix_audit (and consider sobelow) to the quality gates