CCI report: 2da0496f-0969-4dda-b9fd-9fc73bdf135c

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": "1eb6299cb1c4f7c8fd354a8e1f4f80bcbd8d6ee5",
    "author": {
      "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
      "alias": "lorenz"
    },
    "title": "node: Control via `uds_windows` not `winpipe`",
    "state": {
      "status": "open",
      "conflicts": []
    },
    "before": "90cf37c471ce531b90aabb048ceaca25996da2cf",
    "after": "ebf7d876b4d7fc41775febfe49cb0a702f266e53",
    "commits": [
      "ebf7d876b4d7fc41775febfe49cb0a702f266e53"
    ],
    "target": "90cf37c471ce531b90aabb048ceaca25996da2cf",
    "labels": [],
    "assignees": [],
    "revisions": [
      {
        "id": "1eb6299cb1c4f7c8fd354a8e1f4f80bcbd8d6ee5",
        "author": {
          "id": "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz",
          "alias": "lorenz"
        },
        "description": "Recent versions of Windows support Unix Domain Sockets natively, see\n<https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/>.\n\nBy using that feature instead of Windows named pipes, the difference\nfor handling communication via the control socket comparing Unix-like\nsystems and Windows becomes smaller:\n\n 1. No special paths like `\\.\\pipe\\\u2026` have to be handled.\n 2. Not two I/O mechanisms are abstracted (named pipe and UDS) but\n    just one.\n 3. `winpipe` relies on background threads while `uds_windows` does\n    not.\n\nOnce the feature `windows_unix_domain_sockets` (which is tracked at\nhttps://github.com/rust-lang/rust/issues/150487) stabilizes, it will\nlikely be possible to just drop the dependency `uds_windows` and use\nthe implementation in `std::os::windows::net` directly.",
        "base": "90cf37c471ce531b90aabb048ceaca25996da2cf",
        "oid": "ebf7d876b4d7fc41775febfe49cb0a702f266e53",
        "timestamp": 1770888008
      }
    ]
  }
}

Send response

{
  "response": "triggered",
  "run_id": {
    "id": "2da0496f-0969-4dda-b9fd-9fc73bdf135c"
  },
  "info_url": "https://cci.rad.levitte.org//2da0496f-0969-4dda-b9fd-9fc73bdf135c.html"
}

Checkout the source (in /opt/radcis/ci.rad.levitte.org/cci/state/2da0496f-0969-4dda-b9fd-9fc73bdf135c/w)

Started at: 2026-02-12 10:20:12.827881+01:00

Commands:

Read the repo configuration (.radicle/native.yaml in /opt/radcis/ci.rad.levitte.org/cci/state/2da0496f-0969-4dda-b9fd-9fc73bdf135c/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"
}