You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Retry FastLanes mixed-schema and numeric round trips #38
Retry pinned FastLanes evidence from #16 when the official Python writer supports mixed string/numeric tables without TypedCast failure or process exit -11. Require a 13-column round trip before any ranking.
Lab defect: the earlier numeric -11 observation used comma-separated input even though the official reader uses |. The corrected pipe-delimited contract is now encoded in the experimental target.
Format observation: the pinned FastLanes evidence still records partial-vector string failures at 1,023, 1,025, and 2,049 rows, while 1,024 and 2,048 were the documented successful boundaries.
Crash observation: malformed comma input is retained as MUST_NOT_CRASH evidence and isolated in a subprocess. It is not called an upstream bug until a minimal reproducer against the pinned official commit is confirmed.
The target is PARTIAL/EXPERIMENTAL and never gates Core CI.
Revalidation: official Python binding remains blocked
2026-07-17 JST, fixed source commit f0edc1020a538f1f8098640fce8347c9ac247a0d (remote HEAD) was checked out and built in the repository Nix environment.
src/table/stats.cpp:17:21: error: null passed to a callee that requires a non-null argument [-Werror,-Wnonnull]
... instantiation of member function TypedStats<std::string>::TypedStats
The source confirms the official Python API exists, the CSV reader uses |, and ReadCsv asserts that row count is a multiple of the 1,024-value vector size. The mixed-schema writer/reader itself was therefore not reclassified: this run is UNAVAILABLE for the requested round-trip because the pinned official binding does not build in this host/toolchain. It is not yet an upstream format bug. A Linux x86_64 retry or an upstream-supported warning/toolchain configuration is required before ranking.
comma-malformed: RuntimeError from invalid integer input, no process crash
This supersedes any general statement that pipe-delimited numeric input succeeds. The earlier corrected numeric success remains a separate host/workload observation. The result is still PARTIAL/FAILED evidence and is not an upstream bug claim until a minimal reproducer is confirmed against the pinned source.
The result remains PARTIAL/FAILED: the Linux numeric and string cases exited SIGSEGV, and the 13-column mixed case raised UNREACHABLE. It is excluded from rankings and is not, by itself, an upstream bug claim. The next retry requires a reproducible source/toolchain that completes the mixed-schema round trip without fatal termination on both supported hosts.
The parallel audit found no decision-changing retry basis for the pinned FastLanes experiment.
The lab's reproducible evidence remains tied to f0edc1020a538f1f8098640fce8347c9ac247a0d.
The macOS official Python binding build still stops in TypedStats<std::string> before a 13-column round trip.
The Linux evidence remains durable: numeric 1M x 8 and string boundary cases terminated with SIGSEGV, while the 13-column case raised UNREACHABLE; malformed comma input raised an ordinary runtime error without a process crash.
The official quick-fuzz target is still experimental evidence, not a general round-trip result.
Classification remains PARTIAL / FAILED, excluded from rankings, and this is not an upstream bug claim. We will retry only when an upstream-supported or reproducibly pinned toolchain completes the mixed-schema round trip without fatal termination on both supported hosts.
The official FastLanes HEAD still resolves to the recorded commit . Existing Linux and macOS evidence therefore remains the authoritative retry result; repeating the same full workflow would not add information. The next useful run is the smallest Linux x86_64 mixed-schema case at 1,024 rows, with the existing fresh-process artifact capture, before making any upstream bug claim.
The previous comment was shell-escaped incorrectly. The authoritative result is:
The official FastLanes HEAD still resolves to the recorded commit f0edc1020a538f1f8098640fce8347c9ac247a0d. Existing Linux and macOS evidence therefore remains the authoritative retry result; repeating the same full workflow would not add information. The next useful run is the smallest Linux x86_64 mixed-schema case at 1,024 rows, with the existing fresh-process artifact capture, before making any upstream bug claim.
This is a reproducible claim failure, not an upstream bug attribution. The issue remains open under the existing retry conditions: a successful mixed-schema round trip without the prior SIGSEGV/UNREACHABLE observations, independently reproduced on macOS and Linux.
The requested pinned FastLanes retry is complete as a reproducible research result. The official dev branch currently still resolves to f0edc1020a538f1f8098640fce8347c9ac247a0d, so there is no source change that justifies repeating the same workflow.
Linux x86_64: the full official Python retry preserved artifacts and reproduced SIGSEGV in numeric/string cases; the focused 1,024-row, 13-column pipe-delimited retry built the extension but raised RuntimeError: UNREACHABLE at wizard.cpp:1252.
macOS ARM64: the official Python binding build stopped in TypedStats<std::string> under the pinned Nix/Clang toolchain before a mixed-schema round trip.
The required 13-column successful round trip was therefore not established. FastLanes remains PARTIAL/FAILED, EXPERIMENTAL, and excluded from rankings.
This closes the lab-side retry/revalidation work; it does not claim an upstream FastLanes bug or a successful format round trip. Reopen only when a changed upstream source or supported toolchain enables a new independent Linux and macOS retry.
Activity
Anionix commentedon Jul 14, 2026
Evidence split for the robustness v1 follow-up:
-11observation used comma-separated input even though the official reader uses|. The corrected pipe-delimited contract is now encoded in the experimental target.MUST_NOT_CRASHevidence and isolated in a subprocess. It is not called an upstream bug until a minimal reproducer against the pinned official commit is confirmed.The target is
PARTIAL/EXPERIMENTALand never gates Core CI.Anionix commentedon Jul 16, 2026
Revalidation: official Python binding remains blocked
2026-07-17 JST, fixed source commit
f0edc1020a538f1f8098640fce8347c9ac247a0d(remoteHEAD) was checked out and built in the repository Nix environment.Environment:
Command shape:
Observed failure before any 13-column round trip:
The source confirms the official Python API exists, the CSV reader uses
|, andReadCsvasserts that row count is a multiple of the 1,024-value vector size. The mixed-schema writer/reader itself was therefore not reclassified: this run isUNAVAILABLEfor the requested round-trip because the pinned official binding does not build in this host/toolchain. It is not yet an upstream format bug. A Linux x86_64 retry or an upstream-supported warning/toolchain configuration is required before ranking.Anionix commentedon Jul 16, 2026
Linux revalidation: runner fixed, FastLanes remains experimental
Workflow run: https://github.com/Anionix/data-format-lab/actions/runs/29520329351
Source commit:
f0edc1020a538f1f8098640fce8347c9ac247a0dEnvironment: Ubuntu 24.04, x86_64, Python 3.12.13, Clang 21.1.8,
pyfastlanes==0.1.3.post9, runtime0.1.4.The dependency-isolated runner now completed and preserved per-case artifacts, logs, and SHA-256 hashes. Results:
numeric-8-columns, 1,000,000 rows:SIGSEGV(-11)string-{1023,1024,1025,2048,2049}: allSIGSEGV(-11)mixed-13-columns, 1,024 rows:RuntimeError: UNREACHABLEcomma-malformed:RuntimeErrorfrom invalid integer input, no process crashThis supersedes any general statement that pipe-delimited numeric input succeeds. The earlier corrected numeric success remains a separate host/workload observation. The result is still
PARTIAL/FAILEDevidence and is not an upstream bug claim until a minimal reproducer is confirmed against the pinned source.Anionix commentedon Jul 16, 2026
Durable Linux retry evidence
PR #174 is now merged on
main, preserving the exact host/toolchain record and the Release asset for workflow run 29520329351.f0edc1020a538f1f8098640fce8347c9ac247a0db9270a10d9cc0f5d81a81e67b8e22af591a06018e767720b9d9c6e4c3689227aThe result remains
PARTIAL/FAILED: the Linux numeric and string cases exitedSIGSEGV, and the 13-column mixed case raisedUNREACHABLE. It is excluded from rankings and is not, by itself, an upstream bug claim. The next retry requires a reproducible source/toolchain that completes the mixed-schema round trip without fatal termination on both supported hosts.Anionix commentedon Jul 16, 2026
Public-source audit (2026-07-17 JST)
The parallel audit found no decision-changing retry basis for the pinned FastLanes experiment.
f0edc1020a538f1f8098640fce8347c9ac247a0d.TypedStats<std::string>before a 13-column round trip.SIGSEGV, while the 13-column case raisedUNREACHABLE; malformed comma input raised an ordinary runtime error without a process crash.Classification remains
PARTIAL / FAILED, excluded from rankings, and this is not an upstream bug claim. We will retry only when an upstream-supported or reproducibly pinned toolchain completes the mixed-schema round trip without fatal termination on both supported hosts.Anionix commentedon Jul 16, 2026
Current retry boundary (2026-07-17 JST)
The official FastLanes HEAD still resolves to the recorded commit . Existing Linux and macOS evidence therefore remains the authoritative retry result; repeating the same full workflow would not add information. The next useful run is the smallest Linux x86_64 mixed-schema case at 1,024 rows, with the existing fresh-process artifact capture, before making any upstream bug claim.
Anionix commentedon Jul 16, 2026
Correction to the previous comment
The previous comment was shell-escaped incorrectly. The authoritative result is:
The official FastLanes HEAD still resolves to the recorded commit
f0edc1020a538f1f8098640fce8347c9ac247a0d. Existing Linux and macOS evidence therefore remains the authoritative retry result; repeating the same full workflow would not add information. The next useful run is the smallest Linux x86_64 mixed-schema case at 1,024 rows, with the existing fresh-process artifact capture, before making any upstream bug claim.Anionix commentedon Jul 16, 2026
Focused retry result from merged PR #189:
f0edc1020a538f1f8098640fce8347c9ac247a0dmixed, 1,024 rows, 13 pipe-delimited columns; other cases were intentionally skippedRuntimeError: UNREACHABLEatwizard.cpp:1252FAILED/HARNESS_FAILED; nodata.flsordecoded.csvwas produced324900b5c84492c70392c43f33c3324d02caece10171e386587f915fb7752ea2f89350885f783fdb6a24e771fa21d8a72a1a98761abf31ac77bc89e15ab479685f130b49cff7ccb564e804c50e8eb14399d9974b88967448955d1673bcd799b8This is a reproducible claim failure, not an upstream bug attribution. The issue remains open under the existing retry conditions: a successful mixed-schema round trip without the prior SIGSEGV/UNREACHABLE observations, independently reproduced on macOS and Linux.
Anionix commentedon Jul 17, 2026
Closure: retry scope complete (2026-07-17 JST)
The requested pinned FastLanes retry is complete as a reproducible research result. The official
devbranch currently still resolves tof0edc1020a538f1f8098640fce8347c9ac247a0d, so there is no source change that justifies repeating the same workflow.SIGSEGVin numeric/string cases; the focused 1,024-row, 13-column pipe-delimited retry built the extension but raisedRuntimeError: UNREACHABLEatwizard.cpp:1252.TypedStats<std::string>under the pinned Nix/Clang toolchain before a mixed-schema round trip.PARTIAL/FAILED,EXPERIMENTAL, and excluded from rankings.This closes the lab-side retry/revalidation work; it does not claim an upstream FastLanes bug or a successful format round trip. Reopen only when a changed upstream source or supported toolchain enables a new independent Linux and macOS retry.