CCI report: 339ccae4-44f8-465f-8459-4f267287cbf4

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": "967f1eb736de5aabde36279ab9afc6210fc841dc",
    "author": {
      "id": "did:key:z6MkrnXJWPndzPBxpBUaE3L3BnMeWpaQdT1V1FvkoCPFSFS3",
      "alias": null
    },
    "title": "Expose staleConnectionTimeout in config.json",
    "state": {
      "status": "open",
      "conflicts": []
    },
    "before": "0e5a56f25f51d07290613a9363bd8c0c9fc8e0be",
    "after": "4cbdb270e07083e16233f6ede6ed1e42c125496a",
    "commits": [
      "4cbdb270e07083e16233f6ede6ed1e42c125496a"
    ],
    "target": "0e5a56f25f51d07290613a9363bd8c0c9fc8e0be",
    "labels": [],
    "assignees": [],
    "revisions": [
      {
        "id": "967f1eb736de5aabde36279ab9afc6210fc841dc",
        "author": {
          "id": "did:key:z6MkrnXJWPndzPBxpBUaE3L3BnMeWpaQdT1V1FvkoCPFSFS3",
          "alias": null
        },
        "description": "STALE_CONNECTION_TIMEOUT is a compile-time constant. When a node is\ndropping peers it should be keeping (e.g. large transfers over slow\nstorage, high-latency links) an operator's only option today is to rebuild\nfrom source to tune this, while other limits (fetchTimeout, fetchPackReceive,\nfetchConcurrency, the rate and connection limits) are already exposed\nin `limits`.\n\nAdd `limits.staleConnectionTimeout`, mirroring `FetchTimeout` exactly: a\ntransparent newtype over LocalDuration, serialised as whole seconds, with\na Default of 2 minutes. `Limits` already carries\n`#[serde(default, rename_all = \"camelCase\")]`, so a config.json that does\nnot mention the field keeps current behaviour.\n\nCAUTION: lowering this too much below the default is risky. `Service::clock` advances once per\nreactor iteration, so one long iteration - draining the gossip backlog\nat startup, for instance - stamps every message it handles with an\nalready-stale timestamp, and the next sweep reaps peers that are in fact\ntransmitting. This is pre-existing behaviour that the\n120s default hides, not something introduced here.",
        "base": "0e5a56f25f51d07290613a9363bd8c0c9fc8e0be",
        "oid": "4cbdb270e07083e16233f6ede6ed1e42c125496a",
        "timestamp": 1790697431
      }
    ]
  }
}

Send response

{
  "response": "triggered",
  "run_id": {
    "id": "339ccae4-44f8-465f-8459-4f267287cbf4"
  },
  "info_url": "https://cci.rad.levitte.org//339ccae4-44f8-465f-8459-4f267287cbf4.html"
}

Checkout the source (in /opt/radcis/ci.rad.levitte.org/cci/state/339ccae4-44f8-465f-8459-4f267287cbf4/w)

Started at: 2026-09-29 17:57:23.984549+02:00

Commands:

Read the repo configuration (.radicle/native.yaml in /opt/radcis/ci.rad.levitte.org/cci/state/339ccae4-44f8-465f-8459-4f267287cbf4/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": "failure"
}