Issue taxonomy: the last run did NOT pass (preflight=success, check=failure)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
Research direction
Read Doc/Architecture/IssueTaxonomy and inspect the run log linked in the issue to identify which open issue, severity label, or access problem caused the check to fail. Then trace the relevant check in .github/workflows/issue-taxonomy.yml; done when a subsequent run passes and closes this automatically maintained issue.
Written by the indexing model from the issue text.
Description
State: not passing — last run 2026-10-12T07:24:53Z (run).
job results: preflight=success check=failure
The run log names every open issue that has broken the taxonomy for more than 24 hours, every repository missing a severity label, or why the run could not read (a missing credential, a missing Issues: read grant, an unreadable page). An issue the release gate cannot classify is invisible to it — see Doc/Architecture/IssueTaxonomy.
Maintained automatically by .github/workflows/issue-taxonomy.yml; closed automatically when a run passes again.
- Dominant language
- C#
- Stars
- 12
- Forks
- 5
- Avg merge
- 4h 24m
- Merged PRs (30d)
- 961
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Systemorph/MeshWeaver
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Systemorph/MeshWeaver#6548 · 1 comment ·
Maintainers usually reply within 1 day
-
Module containers: a root singleton reaching a module service while a module singleton needs a root singleton deadlocks (lock order root/module inverted)Possibly taken @rbuergi claimed this today. Openbug sev:M
Difficulty 5/5 Over a week Newbie friendliness 25/100
Systemorph/MeshWeaver#6542 · 1 comment ·
Maintainers usually reply within 1 day
-
Release availability advisories are persisted and rendered as English sentences (Updates tab, de viewers)Possibly taken @rbuergi claimed this today. Openbug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Systemorph/MeshWeaver#6540 ·
Maintainers usually reply within 1 day
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Systemorph/MeshWeaver#6527 ·
Maintainers usually reply within 1 day
-
Update watcher: bind an unattended update to the repository the install came from, not the package idPossibly taken @rbuergi claimed this today. Openarea:security bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Systemorph/MeshWeaver#6526 ·
Maintainers usually reply within 1 day
All issues in Systemorph/MeshWeaver
Similar issues
-
A numeric literal is parsed in the host's culture, so 1.5 is 15 in a made EXE on a comma-decimal OSOpenbug interpreter silently-wrong small
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
reactiveui/ReactiveUI.Binding.SourceGenerators#176 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
dotnet/csharpstandard#1830 ·
Maintainers usually reply within 1 day
-
c:docs p:high size:S t:docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day