Fit positive timestamped TDD occurrence inputs within the canonical size gate
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start by reading the parent issue #1984 and the occurrence runner’s input-resolution and timestamp-validation paths; the issue does not name source files or tests. The prior candidate exceeded the canonical size ceiling, so first investigate a maintainable reduction and measure the frozen integrated tree with the unchanged canonical profile. Done requires passing that size gate, the configured build, 37 normal checks and six sanitizer checks, then independent review and architecture approval.
Written by the indexing model from the issue text.
Description
Parent: #1984. This is an urgent enabling step for replacing K-fusion with occurrence-specific TDD.
Discovery context
Ordinary positive TDD worker snapshots carry timestamp metadata, while the bound occurrence runner currently rejects timestamped relations. A bounded extension accepting row-presence multiplicities 0/+1 was implemented against private parent 242a07f8253cb6cf2abf903edbca63ac68ea392d. Its canonical Ubuntu 24.04 GCC 13 release/LTO profile matched fingerprint e998de7827ab8b2c665e9f895e4e2e6e0f17b29450ae468c39efe41464aa97a7, but the complete library measured 414120 .text bytes versus the unchanged 414109 ceiling (baseline 408989 + allowance 5120). Parent measures 414059; the 61-byte growth appears in the retained input resolver. Candidate tree: e6ae005b27096df157c801ef90635fab89e1faae.
The size-first stop was honored: evidence was preserved and source restored. Functional qualification and review were not completed. Architect and Critic discussed this discovery and agreed it merits a distinct child; #1995 and #2009 cover earlier consumer/K1 increments, not this timestamp capability. An open-issue duplicate search found no focused duplicate.
Scope
Find and implement a maintainable, semantically equivalent reduction allowing positive timestamped occurrence inputs within the existing size policy. One hypothesis is to retain timestamp-shape validation before and after reader acquisition, while per-operator resolution retains exact pointer/capacity, schema and generation attestation. Omitting repeated shape checks requires proving held source/descriptor leases prevent authorized mutation. No savings are assumed; a separate approved plan and fresh measurement are required.
Acceptance criteria
- Preserve exact timestamp pointer/capacity attestation, pointer/nonzero-capacity equivalence even for empty relations, capacity >= live rows, schema/generation checks, reader ordering and duplicate-source lease ownership.
- Accept only ordinary row-presence weights 0/+1 under the source reader; reject signed or weighted metadata with ENOTSUP and malformed/stale descriptors with EINVAL. Preserve phase refusals, allocation/admission failure cleanup, retained cleanup and retry.
- Preserve operator-specific metadata: detached VARIABLE passthrough keeps metadata; ordinary materializing MAP/JOIN/SEMIJOIN outputs keep their existing semantics.
- Freeze the complete integrated candidate and pass the unchanged canonical size ceiling with a matching profile. Do not change baseline, allowance, toolchain or measurement policy.
- After size passes, complete the configured build, the established 37 normal TDD/semantics checks and six ASan/UBSan checks, including timestamped versus untagged exact row-bag/fixed-point comparisons at W1/W2/W8, malformed/weighted input refusals, source immutability, reader contention and failure/retry balance.
- Obtain independent raw-diff review and final architecture/risk approval on the same immutable tree. Publication and hosted CI prerequisites remain required.
This child does not complete production scheduling, SCC barriers, signed/retraction algebra, worker transactions (#1963–#1965), or the full #1984/#1982 correctness/performance scope.
- Dominant language
- C
- Stars
- 18
- Forks
- 2
- Avg merge
- 8h
- Merged PRs (30d)
- 287
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 semantic-reasoning/wirelog
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
semantic-reasoning/wirelog#2163 ·
Maintainers usually reply within 1 day
-
Doc: insert executor and incremental consolidation leave sorted runs, not globally sorted headsOpen
Difficulty 1/5 Under an hour Newbie friendliness 83/100
semantic-reasoning/wirelog#2133 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
semantic-reasoning/wirelog#2042 ·
Maintainers usually reply within 1 day
-
p2-medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
semantic-reasoning/wirelog#1914 ·
Maintainers usually reply within 1 day
-
delta consolidate reports a governor refusal as ENOMEM without the session denial flagPossibly taken @justinjoy claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
semantic-reasoning/wirelog#2161 · 1 comment ·
Maintainers usually reply within 1 day
All issues in semantic-reasoning/wirelog
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
FujiNetWIFI/fujinet-lib#122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 12 days
-
bug format I/O medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day