control-first failed on main: run 41408805357

Closed
  • Is something wrong?
#7,824 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, github-actions
Domain
ci-cd

Research direction

The issue links to a failed run of the control-first workflow, but the payload does not name the failing step or the workflow file. Start by opening the linked run and finding the first failed step, then check whether memex-control was tagged with 3.1.12411. Done means the step that failed is identified and the control tag is applied, or the job re-runs cleanly.

Written by the indexing model from the issue text.

Description

bug control-image sev:M

control-first failed on main: run 41408805357 — memex-control was not tagged 3.1.12411, so the control instance is NOT being given this platform build and the fleet will not be offered it (control first). Read the failed step; a re-run of this job re-decides idempotently.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 10m
Merged PRs (30d)
979

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.