CCI report: 514d45ff-32dc-4a46-b300-fbb2a03ba3f1

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:z6MktaNvN1KVFMkSRAiN4qK5yvX1zuEEaseeX5sffhzPZRZW",
      "did:key:z6MkireRatUThvd3qzfKht1S44wpm4FEWSSa4PRMTSQZ3voM",
      "did:key:z6MkgFq6z5fkF2hioLLSNu1zP2qEL1aHXHZzGH1FLFGAnBGz",
      "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz"
    ]
  },
  "action": "Created",
  "patch": {
    "id": "c34e0c1940da85c02228d7b20168403c2a98e9ac",
    "author": {
      "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
      "alias": "lorenz"
    },
    "title": "fetch: Rewrite `git::repository::direct`",
    "state": {
      "status": "open",
      "conflicts": []
    },
    "before": "4787b53b1e85d8052744fc77e4160e4d90e46d0f",
    "after": "149b06a6d1200b996a4441c8e4df4a2458628290",
    "commits": [
      "149b06a6d1200b996a4441c8e4df4a2458628290"
    ],
    "target": "4787b53b1e85d8052744fc77e4160e4d90e46d0f",
    "labels": [],
    "assignees": [],
    "revisions": [
      {
        "id": "c34e0c1940da85c02228d7b20168403c2a98e9ac",
        "author": {
          "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
          "alias": "lorenz"
        },
        "description": "This function (and the helpers `ancestry` and `find_and_peel`) are\neagerly peeling to commits, leading to updates of tags that target the\nsame commit to be missed.\n\nFor example, there could be tag two tag objects with *different* OIDs\nA and B, from *different* authors, using *different* tag names, signed\nwith *different* secret keys, and both pointing to *the same* commit C.\n\nThe implementation would consider A and B to be the same, just becuase\nA and B both peel to C, skipping the update.\n\nThis is counterintuitive, and when combined with canonical references\ncan be quite confusing.\n\nChange this to only reason about an ancestry if the two objects in\nquestion really both are commits directly. Otherwise, treat cases where\nno structure can be used as ancestry similarly to non-fast-forward\nupdates.",
        "base": "4787b53b1e85d8052744fc77e4160e4d90e46d0f",
        "oid": "149b06a6d1200b996a4441c8e4df4a2458628290",
        "timestamp": 1759252535
      }
    ]
  }
}

Send response

{
  "response": "triggered",
  "run_id": {
    "id": "514d45ff-32dc-4a46-b300-fbb2a03ba3f1"
  },
  "info_url": "https://cci.rad.levitte.org//514d45ff-32dc-4a46-b300-fbb2a03ba3f1.html"
}

Checkout the source (in /opt/radcis/ci.rad.levitte.org/cci/state/514d45ff-32dc-4a46-b300-fbb2a03ba3f1/w)

Started at: 2025-09-30 19:30:35.331403+02:00

Commands:

Read the repo configuration (.radicle/native.yaml in /opt/radcis/ci.rad.levitte.org/cci/state/514d45ff-32dc-4a46-b300-fbb2a03ba3f1/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

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

  '

Run the script

Commands:

Send result

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