New Release Discord notification links to GitHub Actions run instead of swamp changelog/release notes

Teamk1mo ago

#1147

/feed: filter and search by author, title/text, and topic

Teamk1mo ago

#1178

Unclear whether SWAMP_API_KEY auth claims a device's banked "ghost" reputation, or only swamp auth login does

Teams2mo ago

#1109

Vault: native secret-read access audit trail

Teams2mo ago

#1080

runModel(): options.arguments never reach the child's per-method arguments — merged into globalArgs, then dropped or rejected

Teams2mo ago

#1077

runModel(): nested outputs record triggeredBy "manual" with no parentOutputId — docs promise model-trigger lineage

Teams2mo ago

#1052

commitPush no-op verification fetches the full monolithic index instead of the v2 shard/commitSeq fast-path (follow-up to #1034)

Teams2mo ago

#1049

Catalog export re-uploads the full monolithic object every sync, even with zero changes (sibling to #1034)

Teams2mo ago

#1034

Shard-first v2 still re-uploads the full monolithic index + catalog export every commit; silent writeback failure above the 30s request timeout

Teams3mo ago

#1033

S3 datastore push walks the entire cache root — nested/foreign namespace dirs become doubled index keys (recurring)

Teams3mo ago

#1021

extension update/install reports new version while on-disk pulled files stay old

Teams3mo ago

#1009

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

Teamk3mo ago

#1008

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

Teams2mo ago

#913

datastore migrate-index ignores the repo's configured namespace (migrates bucket-root index instead)

Teams3mo ago

#829

Intra-namespace write concurrency: whole-index sync under the lock serializes fan-out workloads (split from shipped #666)

Teams3mo ago

#867

Pre-sync pull aborts the whole command when an index entry's S3 object is missing — no built-in way to recover

Teams3mo ago

#869

Local model source edit may not change the bundle cache key — rebuilt bundle shadowed by an older same-hash copy on a shared S3 datastore

Teams3mo ago

#851

autoGc emits auto_gc_completed event on --json stdout, breaking single-parse consumers

Teams3mo ago

#826

Batch / prefix delete for swamp data delete (single lock acquisition)

Teams3mo ago

#812

Same-namespace writers fully serialize on the per-namespace lock — could maintenance/append writes avoid holding it?

Teams2mo ago

#811

Could method-summary report artifacts get a default retention cap? They grow to dominate the datastore manifest

Teams3mo ago

#803

Datastore should fail fast on unresolvable credentials instead of stalling on the AWS provider chain

Teams3mo ago

#806

Optional scheduled / automatic datastore GC (retention-policy-driven pruning)

Team3mo ago

#805

Notify issue author/participants on ripples & status changes — with Discord bot DM as a delivery channel

Team3mo ago

#666

Single global datastore lock serializes unrelated writes across all repos/namespaces

Teams3mo ago

#788

swamp data gc prunes the catalog but never deletes objects from S3 datastores (markDirty hook not wired) — sync manifest never shrinks

Teams3mo ago

#665

data gc --dry-run ignores the flag and performs a destructive GC

Teams3mo ago

#669

Private / org-scoped collectives with member ACLs

Team3mo ago

#606

Resident/warm worker mode — `model method run` has ~6s fixed per-invocation overhead that rules out latency-sensitive use

Teams3mo ago

#580

swamp CLI commands fail silently or hang when invoked from git worktrees via SWAMP_REPO_DIR

Teams4mo ago

#382

Many CLI commands acquire global .datastore.lock unnecessarily, causing 60s LockTimeoutError under any concurrent writer

Teams4mo ago

← Back to list

01Issue

BugClosedSwamp CLIPublicTeam

AssigneesNone

Relationships

#579 Homepage install command: wrong domain and missing https:// protocol

Opened by mgreten · 6/6/2026

Description

The macOS install command shown on the swamp homepage uses the wrong domain and is missing the https:// protocol prefix, causing a 404 error.

Steps to Reproduce

Visit the swamp homepage
Copy the install command: curl -fsSL swamp-club.com/install.sh | sh
Run it in a terminal

Actual Behavior

curl: (22) The requested URL returned error: 404

Expected Behavior

The install command should work. The correct command is:

curl -fsSL https://swamp.club/install.sh | sh

Root Cause

Two issues with the homepage command:

Wrong domain: swamp-club.com instead of swamp.club
Missing protocol: https:// is required for curl to resolve the URL correctly

Environment

macOS (darwin-aarch64)

02Bog Flow

Closed

6/6/2026, 9:27:55 PM

No activity in this phase yet.

03Sludge Pulse

stack72 commented 6/6/2026, 9:28:01 PM

Dupe of #580

New Release Discord notification links to GitHub Actions run instead of swamp changelog/release notes

/feed: filter and search by author, title/text, and topic

Unclear whether SWAMP_API_KEY auth claims a device's banked "ghost" reputation, or only swamp auth login does

Vault: native secret-read access audit trail

runModel(): options.arguments never reach the child's per-method arguments — merged into globalArgs, then dropped or rejected

runModel(): nested outputs record triggeredBy "manual" with no parentOutputId — docs promise model-trigger lineage

commitPush no-op verification fetches the full monolithic index instead of the v2 shard/commitSeq fast-path (follow-up to #1034)

Catalog export re-uploads the full monolithic object every sync, even with zero changes (sibling to #1034)

Shard-first v2 still re-uploads the full monolithic index + catalog export every commit; silent writeback failure above the 30s request timeout

S3 datastore push walks the entire cache root — nested/foreign namespace dirs become doubled index keys (recurring)

extension update/install reports new version while on-disk pulled files stay old

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

datastore migrate-index ignores the repo's configured namespace (migrates bucket-root index instead)

Intra-namespace write concurrency: whole-index sync under the lock serializes fan-out workloads (split from shipped #666)

Pre-sync pull aborts the whole command when an index entry's S3 object is missing — no built-in way to recover

Local model source edit may not change the bundle cache key — rebuilt bundle shadowed by an older same-hash copy on a shared S3 datastore

autoGc emits auto_gc_completed event on --json stdout, breaking single-parse consumers

Batch / prefix delete for swamp data delete (single lock acquisition)

Same-namespace writers fully serialize on the per-namespace lock — could maintenance/append writes avoid holding it?

Could method-summary report artifacts get a default retention cap? They grow to dominate the datastore manifest

Datastore should fail fast on unresolvable credentials instead of stalling on the AWS provider chain

Optional scheduled / automatic datastore GC (retention-policy-driven pruning)

Notify issue author/participants on ripples & status changes — with Discord bot DM as a delivery channel

Single __global__ datastore lock serializes unrelated writes across all repos/namespaces

swamp data gc prunes the catalog but never deletes objects from S3 datastores (markDirty hook not wired) — sync manifest never shrinks

data gc --dry-run ignores the flag and performs a destructive GC

Private / org-scoped collectives with member ACLs

Resident/warm worker mode — `model method run` has ~6s fixed per-invocation overhead that rules out latency-sensitive use

Homepage install command: wrong domain and missing https:// protocol

Homepage install command: wrong domain and missing https:// protocol

Gator-approved feed post did not trigger Discord activity or profile points

swamp CLI commands fail silently or hang when invoked from git worktrees via SWAMP_REPO_DIR

Many CLI commands acquire global .datastore.lock unnecessarily, causing 60s LockTimeoutError under any concurrent writer

Relationships

#579 Homepage install command: wrong domain and missing https:// protocol

Description

Steps to Reproduce

Actual Behavior

Expected Behavior

Root Cause

Environment

Closed

Single global datastore lock serializes unrelated writes across all repos/namespaces