core/spindle/ at 0bfc1652e3179f7053ebfda93ed6850a3c3530af · tangled.org/core · Tangled

tangled.org / core

10

Monorepo for Tangled tangled.org

10

core / spindle /

at 0bfc1652e3179f7053ebfda93ed6850a3c3530af 8 folders 5 files

Evan Jarrett spindle: do not abort pipeline on InitWorkflow failure 2mo ago

spindle/engine: store workflow logs in s3

3 months ago

{appview,knot,spindle}/db: add busy-timeout on sqlite connection Based on: <32d9db7c74d4a98852e8e59bdd4bb8b56d16ea83> Authored-by: Lewis <lewis@tangled.org> Signed-off-by: Seongmin Lee <git@boltless.me>

3 months ago

spindle: do not abort pipeline on InitWorkflow failure A single workflow failing to initialize would abort the entire pipeline. Instead, mark the failed workflow and continue processing the rest, matching the existing behavior for unknown engines. Signed-off-by: Evan Jarrett <evan@evanjarrett.com>

2 months ago

spindle/nixery: update setup command docs Signed-off-by: moshyfawn <email@moshyfawn.dev>

4 months ago

spindle: add repo DID support in ingester, secrets, and xrpc handlers Signed-off-by: Lewis <lewis@tangled.org>

3 months ago

spindle: rework db schema Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

spindle: add repo DID support in ingester, secrets, and xrpc handlers Signed-off-by: Lewis <lewis@tangled.org>

3 months ago

spindle: add repo DID support in ingester, secrets, and xrpc handlers Signed-off-by: Lewis <lewis@tangled.org>

3 months ago

appview/ingester: harden event processing and cursor This is more of a practical proposal than solving a direct problem. We fire-and-forget our cursor updates even if an event fails. Instead, we should have it in the same thread as the record ingestion and not be silent about errors. Also for verification I think a little retry-backoff would be in order. Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

spindle: improve the logging situation Signed-off-by: oppiliappan <me@oppi.li>

8 months ago

appview/docs/nix/spindle/readme.md: fix outdated documentation links Signed-off-by: pompydev <pompydev@proton.me>

6 months ago

spindle: do not abort pipeline on InitWorkflow failure A single workflow failing to initialize would abort the entire pipeline. Instead, mark the failed workflow and continue processing the rest, matching the existing behavior for unknown engines. Signed-off-by: Evan Jarrett <evan@evanjarrett.com>

2 months ago

knotserver: add repo DID migration on startup Signed-off-by: Lewis <lewis@tangled.org>

3 months ago