Skip to content

cflite_pr: gitbot-shared-context path-dep needs proper vendoring #67

Description

@hyperpolymath

Closing #66 marked the cflite_pr job continue-on-error: true as a placeholder while the real fix is figured out. The underlying issue:

Cargo.toml declares

gitbot-shared-context = { path = "../../shared-context" }

but .clusterfuzzlite/Dockerfile only COPY . /src/echidnabot — the sibling crate isn't in the build context, so cargo fuzz build errors with unable to update /shared-context.

Resolution options

  1. Vendor inline — cargo vendor the dep into vendor/shared-context and switch the manifest dep to { path = "vendor/shared-context" }. Simple but duplicates source.
  2. Git-dep — replace path dep with { git = "https://github.com/hyperpolymath/gitbot-shared-context", rev = "<sha>" } (or wherever shared-context lives). Cleanest. Requires the sibling repo to be publishable.
  3. Dockerfile context bump — change COPY . /src/echidnabot to COPY echidnabot /src/echidnabot + COPY shared-context /src/shared-context and adjust .clusterfuzzlite invocation to run from the parent directory. Hardest to wire through CI.

Recommend option 2 if the sibling repo exists publicly; otherwise option 1.

Once chosen + landed, REMOVE continue-on-error: true from cflite_pr.yml and CLOSE this issue.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    automationBots, schedulers, dispatch, self-healing, fan-outpackagingGuix, Nix, containers, distribution artefactspriority:p2Normal - queue itscope:repoConfined to this repositorystatus:readyFully specified and ready to be picked uptech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions