Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

Benchmarks: build_images.sh refuses a wheel without the chunked insert_many - #468

Merged
tae898 merged 1 commit into
mainfrom
benchmarks-wheel-guard-chunked-insert-many
Oct 22, 2026
Merged

tae898 merged 1 commit into
mainfrom
benchmarks-wheel-guard-chunked-insert-many

Conversation

@tae898

@tae898 tae898 commented Oct 22, 2026

Copy link
Copy Markdown

Adds wheel_guard.py and calls it from build_images.sh right after the wheel-is-a-file check, so no benchmark image (the arcadedb image, or the generic ones that carry the wheel) can be built with a bindings wheel whose insert_many materialises the whole input. The guard opens the wheel as a zip and refuses it unless arcadedb_embedded/core.py contains _INSERT_MANY_CHUNK, printing the reason and the fix (use a 26.10.2 or newer wheel). Every generated stage runs build_images.sh, so the stage drafts need no change and their sha256 list is untouched. It changes no existing row. Tests: two tiny fake wheels (with and without the marker) through the guard and through build_images.sh, plus the existing build_images tests now using a real fake wheel instead of a placeholder byte. CAMPAIGN.md and PROTOCOL.md document the guard. Closes #467.

🤖 Generated with Claude Code

…t_many (#467)

wheel_guard.py opens the wheel and requires _INSERT_MANY_CHUNK in arcadedb_embedded/core.py; a pre-26.10.2 wheel is refused with the fix. Existing rows are untouched. CAMPAIGN.md and PROTOCOL.md document the guard.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Benchmarks: refuse an ArcadeDB wheel whose insert_many materialises the whole input

1 participant