Visitar URL original
land_stage: --drop-unless drops the rows a repair stage replaced by tae898 · Pull Request #297 · humemai/arcadedb-embedded-python · GitHub
Skip to content

land_stage: --drop-unless drops the rows a repair stage replaced - #297

Merged
tae898 merged 1 commit into
mainfrom
issue/land-drop-unstamped
Oct 8, 2026
Merged

tae898 merged 1 commit into
mainfrom
issue/land-drop-unstamped

Conversation

@tae898

@tae898 tae898 commented Oct 8, 2026

Copy link
Copy Markdown

Adds --drop-unless BACKEND:LANE:WORKLOAD:FIELD=VALUE to land_stage.py: at landing, the rows of that cell whose FIELD is not VALUE are dropped, so the rows a repair stage replaced go and the repair's own rows, which carry the stamp, stay. Repeatable; absent counts as not VALUE; a malformed spec ends the run instead of silently dropping nothing.

The 26.10.1 campaign needs it once. Its first stage measured ArcadeDB's served graph OLTP at the engine's default bulk-load body limit, which broke the sf10 load; the repair stage re-ran the cell with the raise, stamped as server_http_body_max_bytes. With --drop-unless arcadedb_graph_server:l2:oltp:server_http_body_max_bytes=68719476736, the campaign's current rows give 8 dropped (six sf1 rows and the two failed sf10 rows) and 12 kept, and no row of another backend is touched.

PUBLISHING.md documents the flag next to the landing command, and the script's step list says what step 2 now drops. New test_land_stage_drop_unless.py (3 tests): parsing and refusal of malformed specs, which rows match, and the campaign shape.

🤖 Generated with Claude Code

…ed on the repair's stamp

qP01 measured ArcadeDB's served graph OLTP at the default bulk-load body limit; the repair stage re-ran it with the raise stamped as server_http_body_max_bytes (DECISIONS #172). --drop-unless arcadedb_graph_server:l2:oltp:server_http_body_max_bytes=68719476736 drops the eight old rows and keeps the twelve repaired ones (checked against the campaign's rows). A malformed spec ends the run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tae898
tae898 merged commit cbbe9f0 into main Oct 8, 2026
2 checks passed
@tae898
tae898 deleted the issue/land-drop-unstamped branch October 8, 2026 17:16
tae898 added a commit that referenced this pull request Nov 10, 2026
…the engine of its base version

The 2026-11-11 laptop smoke of the post2 rerun failed the native pair check: the native package's _build_info.ENGINE_VERSION is 26.11.1 while the
wheel is 26.11.1.post2, and the comparison stripped only a .devN suffix ("PAIR UNVERIFIED: ... native engine is '26.11.1', the wheel is
26.11.1.post2"). A wheels-only postN ships the engine of its base version (DECISIONS #297; engine_pin.jar_pin already says so for the jars).

engine_matches() drops .devN on both sides as before and .postN on the wheel side only, after the .devN step, so a different base version
(26.11.2 against 26.11.1.post2) and an engine that itself says .postN still fail. BENCH_PAIR_VERSION_CHECK="<engine> <wheel>" prints
MATCH or MISMATCH without docker, which test_pair_scripts.py uses (10 cases, plus a test that the check calls it).

No other place rejected a .postN wheel: build_images.sh's pre-release guard does not match it (the post2 jvm and native images built),
engine_pin.verify uses jar_pin, make_post1_rerun_stages and post1_rows already order and strip postN.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant