Skip to content
Merged
Changes from 1 commit
Commits
Show all changes
75 commits
Select commit Hold shift + click to select a range
34df1fd
feat(node): add per-IP write-surface rate brake and apply to write_ro…
beardthelion Jul 13, 2026
74e05be
feat(node): extend the per-IP write brake to the remaining write sinks
beardthelion Jul 13, 2026
6fded6e
test(node): adversarial TrustedProxy verification through the write b…
beardthelion Jul 13, 2026
e6324d2
feat(node): purge-spam admin subcommand for the empty-burst cleanup
beardthelion Jul 13, 2026
285d7c7
fix(review): make purge-spam empty-check reject git-discovery reads
beardthelion Jul 13, 2026
090019d
fix(review): normalization-consistent purge, brake helper, CLI + cove…
beardthelion Jul 13, 2026
dfd4f6c
test(review): close the reasoned-not-run gaps by execution
beardthelion Jul 13, 2026
0135419
fix(node): reject path-traversal repo names in purge-spam before remo…
beardthelion Jul 15, 2026
a0fcbb0
fix(node): delete child rows transactionally in delete_repo_by_id
beardthelion Jul 15, 2026
fde9cfe
fix(node): reap write_rate_limiter in the periodic cleanup loop
beardthelion Jul 15, 2026
15522d5
fix(node): hold the per-repo advisory lock across purge recheck+delete
beardthelion Jul 15, 2026
1fcca0d
fix(node): count purge-spam disk-removal failures separately from del…
beardthelion Jul 15, 2026
d9eebd2
fix(node): warn on unparseable rate-limit env vars instead of silentl…
beardthelion Jul 15, 2026
6325402
docs(node): document GITLAWB_IPFS_API/TIGRIS_BUCKET/METRICS_ADDR/SHUT…
beardthelion Jul 15, 2026
bfbe502
test(node): exercise the dry-run guard with a real on-disk candidate …
beardthelion Jul 15, 2026
cdb102e
style(node): cargo fmt for the #196 fix set
beardthelion Jul 15, 2026
4df79f2
fix(node): pin the writer's advisory-lock connection in RepoWriteGuard
beardthelion Jul 15, 2026
68c1f5c
refactor(node): introduce ObjectStore trait seam over TigrisClient
beardthelion Jul 15, 2026
3c1ceb8
fix(node): make purge-spam Tigris-authoritative and archive-deleting
beardthelion Jul 15, 2026
cf669bb
fix(review): don't hold/leak the pool connection in acquire_write
beardthelion Jul 15, 2026
dde5ea9
fix(node): make advisory-lock guards drop-safe and reorder acquire_write
beardthelion Jul 16, 2026
b94d440
fix(node): complete a fully-received push after client disconnect
beardthelion Jul 16, 2026
e4c4161
fix(node): serialize archive uploads under the per-repo advisory lock
beardthelion Jul 16, 2026
6ba698c
fix(node): let purge-spam reach repos that exist only as archives
beardthelion Jul 16, 2026
9f7757c
refactor(node): dedup limiter setup + write-brake test driver; fix .e…
beardthelion Jul 16, 2026
2a78524
docs(node): drop the .env.example shutdown-grace entry #196 added (#196)
beardthelion Jul 19, 2026
c4b337b
fix(node): give advisory-lock guards a dedicated pool and bound the r…
beardthelion Jul 19, 2026
4934646
fix(node): advertise a window-derived Retry-After on rate-limit 429s …
beardthelion Jul 19, 2026
0c279c9
fix(node): skip slug-scoped purge cascade when a mirror row shares th…
beardthelion Jul 19, 2026
86a8228
fix(node): fail closed classifying the purge target directory (#196)
beardthelion Jul 20, 2026
bf2a54e
fix(node): run the push completion tail in the disconnect-surviving t…
beardthelion Jul 20, 2026
c24b541
fix(node): tombstone bounties when their repo is purged (#196)
beardthelion Jul 20, 2026
3baa9ed
fix(node): serialize create_repo against the purge advisory lock (#196)
beardthelion Jul 20, 2026
9916bca
test(node): prove purge deletes at MAX_CONNECTIONS=1 with the split p…
beardthelion Jul 20, 2026
8f3d643
fix(node): fail the push when the durable upload times out, don't 200…
beardthelion Jul 20, 2026
d1e596e
fix(node): tombstone bounties under both owner forms on purge (#196)
beardthelion Jul 20, 2026
ce5dcc3
fix(node): fail closed on a symlink at the purge target (#196)
beardthelion Jul 20, 2026
7dc7be2
fix(node): retry-after on the push-advert 429, and create_repo locks …
beardthelion Jul 20, 2026
d2ba14e
fix(node): correct the create-pool and bounty-tombstone remediations …
beardthelion Jul 20, 2026
5a46ef6
fix(node): close the durable-upload data-loss class on every write pa…
beardthelion Jul 20, 2026
2fa9fa3
chore: merge main (iCaptcha PoW + gl retry tests) into feat/write-sin…
beardthelion Jul 21, 2026
16517f8
refactor(node): route the per-DID 429 through the shared too_many_req…
beardthelion Jul 21, 2026
ba572b3
fix(node): init's background upload waits out the creator's advisory …
beardthelion Jul 21, 2026
859240b
fix(node): roll back the local issue ref before unlock when the durab…
beardthelion Jul 21, 2026
c07435d
fix(node): fork publishes only after a durable upload, serialized on …
beardthelion Jul 21, 2026
2ad1c79
fix(node): read-path downloads publish under the purge lock, without …
beardthelion Jul 21, 2026
b2ca5a7
fix(node): bound every under-lock object-store call and dedup the upl…
beardthelion Jul 21, 2026
fa4322c
fix(node): harden the read-path download against cancellation, stale …
beardthelion Jul 21, 2026
c3d6e73
fix(node): keep the fork's unbounded work out of the target-lock span…
beardthelion Jul 21, 2026
03ef9b5
refactor(node): move read-path download coordination into a repo_stor…
beardthelion Jul 21, 2026
4408d27
fix(node): bound acquire_write's download and free the download-map e…
beardthelion Jul 21, 2026
a12f21a
fix(node): roll back the fork mirror and archive on late clone/insert…
beardthelion Jul 21, 2026
556aa31
fix(node): serialize repo purge cascade with mirror ingest via adviso…
beardthelion Jul 22, 2026
1d8c281
fix(node): roll back local ref on failed durable upload (close/merge/…
beardthelion Jul 22, 2026
1d0d3d2
fix(node): tie cancelled cold-download cleanup to blocking extraction
beardthelion Jul 22, 2026
03cd81e
chore(node): fmt + clippy cleanup for the #196 fixes
beardthelion Jul 22, 2026
9152178
fix(node): never let a failed ref snapshot become a delete-all rollba…
beardthelion Jul 22, 2026
296704f
fix(node): slug-lock every peer-ingest writer and drive the real inge…
beardthelion Jul 22, 2026
1e79ae5
fix(node): own cold-download cleanup in a spawned task so handler can…
beardthelion Jul 22, 2026
ce25bba
refactor(node): delegate issue ref helpers to the store ref primitives
beardthelion Jul 22, 2026
4329b2a
Merge origin/main into feat/write-sink-brake-coverage (reintegrate cu…
beardthelion Jul 22, 2026
d755180
fix(node): slug-lock arweave anchor writes; fail closed when the pre-…
beardthelion Jul 22, 2026
e6f4b2f
fix(node): close review residuals: coalesce cold downloads to one in-…
beardthelion Jul 22, 2026
1459cf2
Merge remote-tracking branch 'origin/main' into feat/write-sink-brake…
beardthelion Nov 11, 2026
da876e8
fix(node): re-apply create/fork purge serialization and restore brake…
beardthelion Nov 11, 2026
edfa6bb
fix(node): close review gaps in purge, locks, and fork cleanup
beardthelion Nov 11, 2026
96ed2b2
fix(node): subscriptions-only ws schema and unsettled-work purge guard
beardthelion Nov 11, 2026
082a37f
Merge remote-tracking branch 'origin/main' into feat/write-sink-brake…
beardthelion Nov 11, 2026
e9e86a1
fix(node): wire close_issue rollback, close purge symlink gap, correc…
beardthelion Nov 11, 2026
1187dca
fix(node): close purge/upload lifecycle gaps from review
beardthelion Nov 11, 2026
261f7ab
fix(node): merge rollback, honest create rollback, purge row recheck
beardthelion Nov 12, 2026
662b9a3
fix(node): probe purge slug liveness, gate issue write brake behind t…
beardthelion Nov 12, 2026
43d4f59
fix(node): close-issue rollback uses resolved ref, drop router brake …
beardthelion Nov 12, 2026
4b483a3
fix(node): close_issue spends neither bucket when either cap refuses,…
beardthelion Nov 12, 2026
11cadb9
fix(node): refund the write slot when the close cap refuses, send Ret…
beardthelion Nov 12, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix(node): tombstone bounties when their repo is purged (#196)
Bounties are keyed only on (repo_owner, repo_name) with no repo id, and
purge left them intact, so recreating the same name re-attached the old
open bounty and claim_bounty succeeded against it. Purge now transitions
the repo's non-terminal bounties (open/claimed/submitted) to a dead
'purged' status on the delete's own transaction, preserving the
financial record. 'purged' is inert against every mutating bounty
endpoint, including dispute (which would otherwise reset claimed/
submitted back to open).
  • Loading branch information
beardthelion committed Jul 20, 2026
commit c24b5418a8807a2b280fea8c53555eb8bd730bbb
163 changes: 162 additions & 1 deletion crates/gitlawb-node/src/db/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -1398,6 +1398,27 @@ impl Db {
// (no issues table to map issue_id → repo) are deliberately NOT cascaded
// here — dropping money records or unmappable rows on a repo delete would
// be wrong. They are left intact by design.
//
// But bounties key on (repo_owner, repo_name), not an immutable repo id, so
// an untouched OPEN bounty would silently re-attach to a same-name repo the
// owner recreates and become claimable again (finding F). Tombstone the
// repo's non-terminal bounties to a dead `purged` status instead of deleting
// them: this preserves the financial record while making them unclaimable
// (claim/submit/approve/cancel/dispute all gate on specific non-`purged`
// source statuses, so `purged` is inert and no transition reopens it).
// Scope by (repo_owner, repo_name) as the surviving purge does; the already
// terminal `completed`/`cancelled` bounties are left as-is. (Residual: a
// tombstoned bounty stays readable/listable under the same owner/name after
// recreation — a view, not a claim/payout re-attach; see the plan's KTD8.)
sqlx::query(
"UPDATE bounties SET status = 'purged'
WHERE repo_owner = $1 AND repo_name = $2
AND status IN ('open', 'claimed', 'submitted')",
)
.bind(&owner_did)
.bind(&name)
.execute(&mut *tx)
.await?;

let result = sqlx::query("DELETE FROM repos WHERE id = $1")
Comment thread
beardthelion marked this conversation as resolved.
Resolved
.bind(id)
Expand Down Expand Up @@ -3646,7 +3667,7 @@ mod agent_discovery_tests {

#[cfg(test)]
mod dedup_db_tests {
use super::{Db, RepoRecord};
use super::{BountyRecord, Db, RepoRecord};
use chrono::{DateTime, Utc};
use sqlx::PgPool;

Expand Down Expand Up @@ -3863,6 +3884,146 @@ mod dedup_db_tests {
);
}

/// U8 (F): bounties key on (repo_owner, repo_name), not an immutable repo id,
/// and `delete_repo_by_id` deliberately does not delete them (financial record).
/// Without tombstoning, a purged repo's OPEN bounty stays claimable and silently
/// re-attaches to a same-name repo recreated by the (spam) owner. The purge must
/// transition the affected non-terminal bounties to the terminal `purged` status
/// (preserving amount/wallet/tx_hash) so no claim/dispute path can re-expose them.
/// A bounty on an unrelated surviving repo must be left untouched.
/// RED on base: the bounty stays `open` and `claim_bounty` succeeds after recreate.
#[sqlx::test]
async fn delete_repo_by_id_tombstones_bounties_against_recreation(pool: PgPool) {
let db = db(pool).await;
let owner = "did:key:z6MkBountyPurgeFixtureForTombstone";
let victim = rec(
"rid-bounty-victim",
owner,
"victim",
"spam repo",
"2026-01-01T00:00:00Z",
"2026-01-01T00:00:00Z",
);
db.create_repo(&victim).await.unwrap();

// An unrelated surviving repo with its own open bounty.
let survivor_owner = "did:key:z6MkBountySurvivorFixtureUntouched";
let survivor = rec(
"rid-bounty-survivor",
survivor_owner,
"keeper",
"legit repo",
"2026-01-01T00:00:00Z",
"2026-01-01T00:00:00Z",
);
db.create_repo(&survivor).await.unwrap();

let bounty = |id: &str, r_owner: &str, r_name: &str, status: &str| BountyRecord {
id: id.to_string(),
repo_owner: r_owner.to_string(),
repo_name: r_name.to_string(),
issue_id: None,
title: "fix the bug".to_string(),
amount: 5_000,
creator_did: "did:key:z6MkCreator".to_string(),
claimant_did: None,
claimant_wallet: None,
pr_id: None,
status: status.to_string(),
created_at: "2026-01-01T00:00:00Z".to_string(),
claimed_at: None,
submitted_at: None,
completed_at: None,
deadline_secs: 604_800,
tx_hash: None,
};
db.create_bounty(&bounty("bnt-victim", owner, "victim", "open"))
.await
.unwrap();
// A mid-flight `claimed` bounty must also be tombstoned: otherwise a later
// dispute (which resets `claimed`/`submitted` back to `open`) would re-expose
// it on the recreated repo.
db.create_bounty(&bounty("bnt-victim-claimed", owner, "victim", "claimed"))
.await
.unwrap();
// An already-terminal `completed` bounty is outside the tombstone set.
db.create_bounty(&bounty(
"bnt-victim-completed",
owner,
"victim",
"completed",
))
.await
.unwrap();
db.create_bounty(&bounty("bnt-survivor", survivor_owner, "keeper", "open"))
.await
.unwrap();

// Purge the spam repo, then let the owner recreate the same owner/name.
let removed = db.delete_repo_by_id("rid-bounty-victim").await.unwrap();
assert_eq!(removed, 1, "the purged repo row is deleted");
let recreated = rec(
"rid-bounty-recreated",
owner,
"victim",
"recreated repo",
"2026-03-01T00:00:00Z",
"2026-03-01T00:00:00Z",
);
db.create_repo(&recreated).await.unwrap();

// The purged repo's bounty is tombstoned, so a claim is a no-op: the
// `UPDATE ... WHERE status='open'` matches nothing and it stays `purged`.
db.claim_bounty(
"bnt-victim",
"did:key:z6MkAttacker",
Some("0xattacker"),
"2026-03-02T00:00:00Z",
)
.await
.unwrap();
let victim_bounty = db.get_bounty("bnt-victim").await.unwrap().unwrap();
assert_eq!(
victim_bounty.status, "purged",
"the purged repo's bounty must be tombstoned, not re-claimable"
);
assert!(
victim_bounty.claimant_did.is_none(),
"the tombstoned bounty must not accept a new claimant"
);
// The financial record is preserved (tombstoned, not deleted).
assert_eq!(victim_bounty.amount, 5_000, "amount preserved on tombstone");
assert_eq!(
victim_bounty.creator_did, "did:key:z6MkCreator",
"creator_did preserved on tombstone"
);

// A mid-flight claimed bounty on the same repo is tombstoned too (so a
// dispute cannot reopen it against the recreated repo).
let claimed_bounty = db.get_bounty("bnt-victim-claimed").await.unwrap().unwrap();
assert_eq!(
claimed_bounty.status, "purged",
"a claimed bounty on the purged repo must also be tombstoned"
);
// An already-terminal completed bounty is left as-is (not in the tombstone set).
let completed_bounty = db
.get_bounty("bnt-victim-completed")
.await
.unwrap()
.unwrap();
assert_eq!(
completed_bounty.status, "completed",
"a terminal completed bounty must be left untouched"
);

// The unrelated survivor's bounty is untouched and still claimable.
let survivor_bounty = db.get_bounty("bnt-survivor").await.unwrap().unwrap();
assert_eq!(
survivor_bounty.status, "open",
"an unrelated repo's bounty must stay open"
);
}

/// The canonical `did:key:` row and the short-owner mirror row of one logical
/// repo collapse to a single deduped entry: the canonical row wins and inherits
/// the group's most recent `updated_at`.
Expand Down