alpha
Login
or
Join now
tangled.org
/
core
Star
8
Fork
66
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Monorepo for Tangled
tangled.org
Star
8
Fork
66
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
14
Pulls
26
Pipelines
core
/
spindle
/
at
b2bef7385c516f2753b0e8cbc5a8f4cea271693e
8 folders
5 files
oppiliappan
spindle,docs: rename TANGLED_EVENT_NAME to TANGLED_PIPELINE_KIND
7w ago
bcb7237a
config
spindle,docs: rename TANGLED_EVENT_NAME to TANGLED_PIPELINE_KIND the PIPELINE prefix is to match TANGLED_PIPELINE_ID, and the `_KIND` is because we refer to this as trigger "kind" everywhere else. Signed-off-by: oppiliappan <me@oppi.li>
1 month ago
db
{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
engine
spindle: limit concurrent workflows to cap total memory usage Add a channel-based semaphore (SPINDLE_SERVER_MAX_CONCURRENT_WORKFLOWS, default 8) that blocks workflow goroutines from starting a container until a slot is free. Each workflow acquires a slot before SetupWorkflow and releases it on exit via defer. Combined with the 6 GiB per-container limit (MAX_JOB_MEMORY_MB), this bounds total container memory to ~48 GiB on the current 64 GiB host. MAX_JOB_COUNT still controls pipeline-level concurrency at the queue. Without this semaphore, max workflows were effectively unbounded and (wrongly) assumed to be capped at MAX_JOB_COUNT. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
1 month ago
engines
spindle/engines/nixery: limit max memory per job Default to 6GB. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
1 month ago
models
spindle,docs: rename TANGLED_EVENT_NAME to TANGLED_PIPELINE_KIND the PIPELINE prefix is to match TANGLED_PIPELINE_ID, and the `_KIND` is because we refer to this as trigger "kind" everywhere else. Signed-off-by: oppiliappan <me@oppi.li>
1 month ago
queue
spindle: rework db schema Signed-off-by: oppiliappan <me@oppi.li>
1 year ago
secrets
spindle: add repo DID support in ingester, secrets, and xrpc handlers Signed-off-by: Lewis <lewis@tangled.org>
3 months ago
xrpc
*: correct typos throughout codebase Fix various misspellings found by the typos tool: - Error messages: Forbiden -> Forbidden, insufficent -> insufficient - Comments and docs: recieve -> receive, acheive -> achieve, etc. - Variable names: Referencs -> References, intialize -> initialize - HTML templates: Unubscribe -> Unsubscribe, explictly -> explicitly - Function names: perferom -> perform Also remove backwards compat code for is_deafult JSON field. Add _typos.toml config for false positives (external APIs, etc.) Signed-off-by: eti <eti@eti.tf>
2 months ago
ingester.go
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
middleware.go
spindle: improve the logging situation Signed-off-by: oppiliappan <me@oppi.li>
8 months ago
motd
appview/docs/nix/spindle/readme.md: fix outdated documentation links Signed-off-by: pompydev <pompydev@proton.me>
6 months ago
server.go
spindle/config: fmt Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
1 month ago
stream.go
knotserver: add repo DID migration on startup Signed-off-by: Lewis <lewis@tangled.org>
3 months ago