rss-bridge: #51 was closed, and the cause was never identified
Small follow-up to #124, which merged at 12:25. You closed#51 one second later, on the strength of that round's green install-test — which is entirely your call, and this PR does not argue with it. It fixes the consequence: three statements merged with #124 are now stale, and stale in the direction that matters — they describe a failing test and an open issue.
File
Said
Now
rss-bridge/templates/rss-bridge.httproute.yaml
"its install-test fails on the Gitea runner (#51)"
went green in the converting PR; #51 closed; cause never identified
it was closed on exactly that round — said plainly
The emphasis moved to the part that outlives the colour
What stays true and useful after the issue is closed is not the green. It is this pair:
The chart was ruled out by a diff, not an argument. The render for the fixture values was byte-identical to main, so the pod spec that passed is the one that had been failing. The runner is the implicated layer.
The cause was never identified. Nobody established what changed on the runner, and #51's own diagnostic programme — docker info for userns and the dind configuration, the same image in a local k3d without remapping — was not executed.
So the overlay comment now says, where whoever next sees a red will be reading it: a recurrence is a fresh finding, not a known quirk. That is the one sentence that a closed issue cannot carry any more, and it is why it belongs in the file rather than only in the tracker.
Also folded in
The run-count wording from #124's tail. The count was pinned at "two consecutive runs" and a third green arrived with the next push, so each commit recording the number invalidated it. Phrased as "every run of that branch since" instead — stable, still establishes it is not a fluke, cannot go stale.
Version
Patch, 2.1.1+up2026.09.30. Comment-only changes, but a comment in a chart directory is still a change to that chart — the rule #40 was argued on — so it is a patch plus a publish. appVersion untouched.
Verified: helm lint --strict clean, ci/run-httproute-match-test.sh rss-bridge 2 assertions held, and the render for the fixture values is byte-identical to the pre-#124 main, so no template output moves.
The wiki carries the same correction in this round (rss-bridge, CI-CD, Lessons-Learned): #51 closed, cause unidentified, recurrence is a finding.
No Fixes keyword — #51, #114 and #40 are all closed already, and this PR finishes no further issue.
# `rss-bridge`: #51 was closed, and the cause was never identified
Small follow-up to #124, which merged at 12:25. You closed #51 one second later, on the strength of that round's green install-test — which is entirely your call, and this PR does not argue with it. It fixes the consequence: **three statements merged with #124 are now stale, and stale in the direction that matters** — they describe a failing test and an open issue.
| File | Said | Now |
|---|---|---|
| `rss-bridge/templates/rss-bridge.httproute.yaml` | "its install-test **fails** on the Gitea runner (#51)" | went green in the converting PR; #51 closed; cause never identified |
| `rss-bridge/values.yaml` | the same, plus "and that test **is still red**" | same correction |
| `ci/httproute/rss-bridge.yaml` | "#51 **is not closed** on the strength of a colour" | it was closed on exactly that round — said plainly |
## The emphasis moved to the part that outlives the colour
What stays true and useful after the issue is closed is not the green. It is this pair:
- **The chart was ruled out by a diff, not an argument.** The render for the fixture values was byte-identical to `main`, so the pod spec that passed is the one that had been failing. The runner is the implicated layer.
- **The cause was never identified.** Nobody established what changed on the runner, and #51's own diagnostic programme — `docker info` for `userns` and the dind configuration, the same image in a local k3d without remapping — was not executed.
So the overlay comment now says, where whoever next sees a red will be reading it: **a recurrence is a fresh finding, not a known quirk.** That is the one sentence that a closed issue cannot carry any more, and it is why it belongs in the file rather than only in the tracker.
## Also folded in
The run-count wording from #124's tail. The count was pinned at "two consecutive runs" and a third green arrived with the next push, so each commit recording the number invalidated it. Phrased as "every run of that branch since" instead — stable, still establishes it is not a fluke, cannot go stale.
## Version
**Patch, `2.1.1+up2026.09.30`.** Comment-only changes, but a comment in a chart directory is still a change to that chart — the rule #40 was argued on — so it is a patch plus a publish. `appVersion` untouched.
Verified: `helm lint --strict` clean, `ci/run-httproute-match-test.sh rss-bridge` 2 assertions held, and the render for the fixture values is **byte-identical to the pre-#124 `main`**, so no template output moves.
The wiki carries the same correction in this round (`rss-bridge`, `CI-CD`, `Lessons-Learned`): #51 closed, cause unidentified, recurrence is a finding.
No `Fixes` keyword — #51, #114 and #40 are all closed already, and this PR finishes no further issue.
The count was pinned at "two consecutive runs" and a third green arrived
with the next push, which is a regress: every commit that records the
number invalidates it. Phrased as "every run of that branch since"
instead, which is stable, still establishes that it is not a fluke, and
cannot go stale in main.
The caution it carries is unchanged and is the one that matters: it is a
colour, not a cause. Nobody has identified what changed on the runner, and
#51's diagnostic programme is still unexecuted.
PR #124 merged at 12:25 and the maintainer closed#51 one second later, on
the strength of that round's green install-test. Three statements that
merged with #124 are stale as a result, and they are stale in the
direction that matters - they describe a failing test and an open issue:
- rss-bridge/templates/rss-bridge.httproute.yaml and values.yaml said
the install-test "fails on the Gitea runner (#51)", in the present
tense, and values.yaml added "and that test is still red".
- ci/httproute/rss-bridge.yaml said "#51 is not closed on the strength
of a colour", which was true when written and is now the opposite of
what happened.
Replaced with what is actually known, and the emphasis moved to the part
that outlives the colour: the test went green on a render byte-identical
to main, which rules the chart out and leaves the runner - and THE CAUSE
WAS NEVER IDENTIFIED. The diagnostic programme in #51 (docker info for
userns and the dind configuration, the same image in a local k3d without
remapping) was not executed. So a recurrence is a fresh finding rather
than a known quirk, and the overlay comment now says so where whoever
sees the red will be reading.
Also carries the wording change that was already on this branch when
#124 merged: the reproduced green is phrased as "every run of that branch
since" rather than pinned to a count, because each commit recording the
count invalidated it - a third green arrived with the push after "two".
Patch bump, per the rule #40 was argued on: a comment in a chart
directory is still a change to that chart, so it is a patch plus a
publish. No template output changes - the render for the fixture values
is byte-identical to the pre-#124 main, which the tests re-confirm.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
jklein
rss-bridge: #51 was closed, and the cause was never identifiedSmall follow-up to #124, which merged at 12:25. You closed #51 one second later, on the strength of that round's green install-test — which is entirely your call, and this PR does not argue with it. It fixes the consequence: three statements merged with #124 are now stale, and stale in the direction that matters — they describe a failing test and an open issue.
rss-bridge/templates/rss-bridge.httproute.yamlrss-bridge/values.yamlci/httproute/rss-bridge.yamlThe emphasis moved to the part that outlives the colour
What stays true and useful after the issue is closed is not the green. It is this pair:
main, so the pod spec that passed is the one that had been failing. The runner is the implicated layer.docker infoforusernsand the dind configuration, the same image in a local k3d without remapping — was not executed.So the overlay comment now says, where whoever next sees a red will be reading it: a recurrence is a fresh finding, not a known quirk. That is the one sentence that a closed issue cannot carry any more, and it is why it belongs in the file rather than only in the tracker.
Also folded in
The run-count wording from #124's tail. The count was pinned at "two consecutive runs" and a third green arrived with the next push, so each commit recording the number invalidated it. Phrased as "every run of that branch since" instead — stable, still establishes it is not a fluke, cannot go stale.
Version
Patch,
2.1.1+up2026.09.30. Comment-only changes, but a comment in a chart directory is still a change to that chart — the rule #40 was argued on — so it is a patch plus a publish.appVersionuntouched.Verified:
helm lint --strictclean,ci/run-httproute-match-test.sh rss-bridge2 assertions held, and the render for the fixture values is byte-identical to the pre-#124main, so no template output moves.The wiki carries the same correction in this round (
rss-bridge,CI-CD,Lessons-Learned): #51 closed, cause unidentified, recurrence is a finding.No
Fixeskeyword — #51, #114 and #40 are all closed already, and this PR finishes no further issue.