backlog: user-facing ticket descriptions + drafts for pinned native container gaps - #11
Closed
ahrzb wants to merge 1 commit into
Closed
backlog: user-facing ticket descriptions + drafts for pinned native container gaps#11ahrzb wants to merge 1 commit into
ahrzb wants to merge 1 commit into
Conversation
…drafts for the pinned native container gaps
Owner
Author
|
Redundant — the entire contents of this branch (5f6bd0b) is already on master, having reached it via the merge of #10. A diff of this branch against master shows no backlog/ changes at all. Cause: I branched from a stale origin/master ref (git fetch was silently failing on SSH), not realising my board commit had already been carried to master. Closing rather than merging; nothing is lost. |
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
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.
Board-only change (
backlog/**). No code touched.Rewrote descriptions around what a user actually hits
Every open ticket and draft now opens with a concrete scenario — real column names, the SQL a user would write, the symptom they'd see — before any engine internals. Previously they were written engine-inward and read as implementation notes.
Covers: TASK-3, TASK-15, TASK-16, TASK-29, TASK-34 and DRAFT-7 through DRAFT-13.
New drafts for the pinned native gaps
Ritchie's TASK-29 container work left 4 strict
xfail_on_nativemarkers intests/test_diff_types.pywith no tickets tracking them. Per the standing native-bug process (xfail-strict + a ticket, never fix inline), the xfail half was done and the ticket half was missing. Filed as two drafts, split by severity:struct(...)/make_array(...). Fails loudly: works intransform(), breaks ininfer(). Bracket literal[a, b]still works, so lists have an alternative spelling; structs don't.SELECT [bedrooms, price_per_sqft]gives[3.0, 12.5]at training and[3, 12.5]at serving, no error. Silent cross-engine divergence on the default serving engine, hence the higher rating.Also DRAFT-11, recording Wren's measured finding that SQL named arguments are unreachable from Python (a per-function Rust
ScalarUDFcapability the bindings don't expose) — captured so nobody re-derives it.Both new drafts are pending AmirHossein's review of scope and priority.
🤖 Generated with Claude Code