rajamesandClaude Opus 5.5
c1bc1c8041
Acceptance / Acceptance (pull_request) Canceled after 0s
Build / Image RASPI (push) Successful in 4m35s
Build / Image PC (push) Successful in 4m30s
Build / Image MILKV (push) Successful in 4m33s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m7s
Issues follow the record's Found / Ruled / Built / Verified
(docs/fabric/FABRIC-3.md): the reporter writes what was found and its
evidence; Captain Bob rules; the commits build it; the acceptance logs
verify it. A finding is not a request to fix it (.claude/CLAUDE.md).
.gitea/ISSUE_TEMPLATE/
1-bug.yaml Found, where, system (v4/v3), seen on (ISA, stick,
hardware), evidence (the log lines), how found
2-work.yaml what, why (the ruling or design section), done when
(with the acceptance protocol and its logs), area,
priority
3-ruling.yaml the question, the options and their costs, a
recommendation, where the ruling will be recorded,
what waits on it
4-board.yaml board, the image booted (Nexus version or commit),
what happened, the serial log, the BRINGUP.md item
config.yaml blank issues still allowed; the XWiki linked for
design and discussion
.gitea/pull_request_template.md what and why, Closes #, acceptance
(the check runs itself; hand-run logs; hardware), the
record (FABRIC-3.md, CHANGELOG), no unrequested fixes
Gitea reads these from the default branch: they apply once on master.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
54 lines
1.8 KiB
YAML
54 lines
1.8 KiB
YAML
name: Bug
|
|
about: Something is wrong. Report it as found -- it is fixed only when Captain Bob says so.
|
|
title: "[bug] "
|
|
labels: ["kind/bug"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Write what was **found**, with its evidence. The rest of the issue follows the project's
|
|
record (`docs/fabric/FABRIC-3.md`): **Ruled** (Captain Bob decides whether and how it is
|
|
fixed), **Built** (the commits), **Verified** (the acceptance logs). A finding is not a
|
|
request to fix it (`.claude/CLAUDE.md`, Hard Rules).
|
|
- type: textarea
|
|
id: found
|
|
attributes:
|
|
label: Found
|
|
description: What is wrong, and what happens because of it. Concrete input and the wrong output, crash or hang.
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
id: where
|
|
attributes:
|
|
label: Where
|
|
description: File and line, or the word, capsule or board.
|
|
placeholder: "v4/src/exec.c:182"
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: system
|
|
attributes:
|
|
label: System
|
|
options: ["v4 (the default)", "v3 (system=v3)", "both", "the build or CI", "not specific"]
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: isa
|
|
attributes:
|
|
label: Seen on
|
|
multiple: true
|
|
options: ["amd64", "aarch64", "riscv64", "32-bit build (test-32)", "the PC stick", "hosted", "real hardware"]
|
|
- type: textarea
|
|
id: evidence
|
|
attributes:
|
|
label: Evidence
|
|
description: The serial log (`logs/<TS>/<arch>/...`), the failing test, or the steps that reproduce it. Logs are the evidence; paste the lines that matter.
|
|
render: text
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: how
|
|
attributes:
|
|
label: How it was found
|
|
description: A boot, a test, a review, real hardware.
|