Repository navigation
chore(register): give the upstream-owned concerns their homes; C-58 joins Cluster M - #180
Merged
Merged
Conversation
…ve C-58 into Cluster M Answering "are the things in other repos tracked by gh issues there?" — mostly yes, two were not, and one turned out to be already fixed upstream. ALREADY TRACKED, verified rather than assumed: C-13, C-28 timeouts -> pipeline-core #248, #347 C-73 stale run -> pipeline-core #341 (closed) C-72 pyarrow CVE -> vpp #174, faoapi #348, comment on #280 C-62, C-44 dependency drag -> comment on pipeline-core #319 C-43 area math -> views-datafactory #387 GAPS, now filed: C-26 (Tier 1) -> pipeline-core #366. Our only Tier 1, open since 2026-06-12 with no home in the repo that owns the code. Filed carrying the question this seat cannot answer: does get_feature_frame inherit the unconditional fillna(0.0), or does the frame path propagate NaN? That decides whether C-26 is live — run-0 shipped 28.4M historical rows through the frame path — or historical. Entry stays Tier 1 until answered, not downgraded on a guess. C-27 -> pipeline-core #367, cross-referenced to their #168 as the same defect class on a different call path. C-24 -> cross-referenced on faoapi #222 (their output-schema epic) asking directly whether the Topic-C rename is in scope, with an offer to close our entry pointing there if so. Open fourteen months without a home in the repo that owns the fix. FOUND WHILE CHECKING: C-58's fix has already LANDED upstream. pipeline-core #322 (write-path raise-by-default), #331 (relocate the four create_* sites) and #332 (assert the delivery path does not import provisioning) are all closed — that is þing-02's D5 implemented. But all three are on their 3.0.0, and we resolve 2.3.0, so the defect is fixed upstream and LIVE here until the bump. Same shape as C-73. C-58 joins Cluster M, which is now six entries — two of them Tier 2 — resolving on one publish. The integrity guard caught me writing "C-166" unnamespaced, which is my own convention. Fixed before commit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Answering "are the things in other repos tracked by gh issues there?" — mostly yes, two were not, and one turned out to be already fixed upstream.
Already tracked — verified, not assumed
Gaps — now filed
views-pipeline-core #366 — C-26, our only Tier 1. Open since 2026-06-12 with no home in the repo that owns the code. Filed carrying the question this seat cannot answer: does
get_feature_frameinherit the unconditionalfillna(0.0), or does the frame path propagate NaN? That decides whether C-26 is live — run-0 shipped 28.4M historical rows through the frame path — or historical. The entry stays Tier 1 until answered; deliberately not downgraded on a guess.views-pipeline-core #367 — C-27. Cross-referenced to their #168 as the same defect class on a different call path: catch broadly, guess at the cause, discard the evidence. Worth deciding once rather than twice.
views-faoapi #222 — C-24, cross-referenced. Asked directly whether the Topic-C rename is in their output-schema epic's scope, with an offer to close our entry pointing there if so, or file it properly if not. Open fourteen months without a home in the repo that owns the fix.
Found while checking: C-58 is already fixed upstream
views-pipeline-core #322 (write-path raise-by-default), #331 (relocate the four
create_*sites) and #332 (assert the delivery path does not import provisioning) are all closed — that is þing-02's D5, implemented.But all three are on their 3.0.0, and we resolve 2.3.0. So the defect is fixed upstream and live here until the bump — the same shape as C-73.
C-58 joins Cluster M, which is now six entries — two of them Tier 2 — resolving on one publish.
Note
The integrity guard caught me writing
C-166unnamespaced, which is my own convention. Fixed before commit.🤖 Generated with Claude Code