CCI report: dfa7cd5e-fed2-45cd-a100-15becb029b49

Request message

{
  "request": "trigger",
  "version": 1,
  "event_type": "patch",
  "repository": {
    "id": "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5",
    "name": "heartwood",
    "description": "Radicle Heartwood Protocol & Stack",
    "private": false,
    "default_branch": "master",
    "delegates": [
      "did:key:z6MksFqXN3Yhqk8pTJdUGLwATkRfQvwZXPqR2qMEhbS9wzpT",
      "did:key:z6MkireRatUThvd3qzfKht1S44wpm4FEWSSa4PRMTSQZ3voM",
      "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz"
    ]
  },
  "action": "Created",
  "patch": {
    "id": "cd1f40e147b25083c08dae7275175a8515e2bd0a",
    "author": {
      "id": "did:key:z6MkiaGEHcXc9v3ou5ZvfnRC8xBrGoEFWqvPQPTLEU8bUt8C",
      "alias": "nolan"
    },
    "title": "node: Probe and remove stale control socket before binding",
    "state": {
      "status": "open",
      "conflicts": []
    },
    "before": "6ba619f9a636fecfe5f30b36ebb6b8c06774d5cb",
    "after": "f9d4ce787e31331f1c961ef80f8746490f3aba47",
    "commits": [
      "f9d4ce787e31331f1c961ef80f8746490f3aba47"
    ],
    "target": "919d5c780c4da0b5b9f18f1549bc59dffd7125af",
    "labels": [],
    "assignees": [],
    "revisions": [
      {
        "id": "cd1f40e147b25083c08dae7275175a8515e2bd0a",
        "author": {
          "id": "did:key:z6MkiaGEHcXc9v3ou5ZvfnRC8xBrGoEFWqvPQPTLEU8bUt8C",
          "alias": "nolan"
        },
        "description": "First-time patch contributor, hope I got the workflow right.\n\nI noticed my node refusing to come back up after a laptop hard-crash. Removing the lingering control socket brought it back up.\n\nThis patch removes a stale control socket, but probes it with a connection attempt before doing so. If the connection attempt succeeds, the start attempt aborts, otherwise the socket is removed and the node is started again.\n\nUnit tests added as well, though I haven't yet tested with a power failure. I've actually switched my node to socket activation as a temporary workaround so I can stay on 1.10, but see no reason this wouldn't fix the issue. If it's generally safe to run heartwood main and you'd rather I do a live test, let me know and I'll revert my systemd changes and try killing the node to see if it comes back.",
        "base": "6ba619f9a636fecfe5f30b36ebb6b8c06774d5cb",
        "oid": "f9d4ce787e31331f1c961ef80f8746490f3aba47",
        "timestamp": 1786565245
      }
    ]
  }
}

Send response

{
  "response": "triggered",
  "run_id": {
    "id": "dfa7cd5e-fed2-45cd-a100-15becb029b49"
  },
  "info_url": "https://cci.rad.levitte.org//dfa7cd5e-fed2-45cd-a100-15becb029b49.html"
}

Checkout the source (in /opt/radcis/ci.rad.levitte.org/cci/state/dfa7cd5e-fed2-45cd-a100-15becb029b49/w)

Started at: 2026-09-07 17:55:33.418113+02:00

Commands:

Read the repo configuration (.radicle/native.yaml in /opt/radcis/ci.rad.levitte.org/cci/state/dfa7cd5e-fed2-45cd-a100-15becb029b49/w)

shell: 'export RUSTDOCFLAGS=''-D warnings''


  cargo --version

  rustc --version


  cargo fmt --check

  cargo clippy --all-targets --workspace -- --deny warnings

  cargo build --all-targets --workspace

  cargo doc --workspace --no-deps --all-features

  cargo test --workspace --no-fail-fast

  '

Run the script

Commands:

Send result

{
  "response": "finished",
  "result": "success"
}