CCI report: ed8606bd-6a52-4974-b83e-50dfeeb66a53

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": "01e2e755b4b6540f560993cef5483ecf6fffd2ff",
    "author": {
      "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
      "alias": null
    },
    "title": "cli/sync: Rewrite Announcement in Two Phases",
    "state": {
      "status": "archived",
      "conflicts": []
    },
    "before": "f30760d6bb86d2978a5ed4df8ee45b9aa97778b4",
    "after": "b1214b30b8a1e05130c8bfa65f4c15768a697341",
    "commits": [
      "b1214b30b8a1e05130c8bfa65f4c15768a697341"
    ],
    "target": "3fc92f83fe089263c470b328414d923227cf0e4a",
    "labels": [],
    "assignees": [],
    "revisions": [
      {
        "id": "01e2e755b4b6540f560993cef5483ecf6fffd2ff",
        "author": {
          "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
          "alias": null
        },
        "description": "The code for announcing changes is rewritten. It is now separated into\ntwo phases, such that first, announcements are made to preferred seeds,\nand only then, to other seeds, to meet desired replication target.\n\nThe primary reason is that in order for an announcement process to be\nconsidered successful, there are two conditions, and both have to be\nmet:\n 1. All preferred seeds must be in sync.\n 2. Replication target must be met.\n\nUp to now, the two conditions were correctly recognized, but it was hard\nto follow for the user, since they were both tracked in a pass.\n\nAlong the way I improved the messages quite a bit. It is now possible to\nobtain progress information, such as how many seeds are already in sync,\nas the process of announcement unfolds.\n\nI took care to use the terminology \"announce\", \"sync\" and \"seed\"\nprecisely.\n\nThis is motivated by\n\n  issue/022227e32a410d39118c35f7909d3512e980bc29\n\nbut since my understanding of the situation improved after working with\nthe code, I deviated from my original (much too verbose), proposal.\n\nWhat I originally wanted is more or less what one gets with `--debug`.",
        "base": "f30760d6bb86d2978a5ed4df8ee45b9aa97778b4",
        "oid": "d9969fe2c8aae55fdb836adf42444d35dd41748b",
        "timestamp": 1746482583
      }
    ]
  }
}

Send response

{
  "response": "triggered",
  "run_id": {
    "id": "ed8606bd-6a52-4974-b83e-50dfeeb66a53"
  },
  "info_url": "https://cci.rad.levitte.org//ed8606bd-6a52-4974-b83e-50dfeeb66a53.html"
}

Checkout the source (in /opt/radcis/ci.rad.levitte.org/cci/state/ed8606bd-6a52-4974-b83e-50dfeeb66a53/w)

Started at: 2026-09-08 06:43:17.833031+02:00

Commands:

Read the repo configuration (.radicle/native.yaml in /opt/radcis/ci.rad.levitte.org/cci/state/ed8606bd-6a52-4974-b83e-50dfeeb66a53/w)

shell: '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"
}