Repository navigation
Pin chdb-core v26.11.0-rc.2 - #65
Merged
wudidapaopao merged 5 commits intoNov 5, 2026
Merged
Conversation
Move the engine pin from v26.9.2-rc.2 to v26.11.0-rc.1 in the three places that carry it, as the release check's propose_bump step does: CHDB_ENGINE_PIN in update_libchdb.sh and build.rs, and engine under [package.metadata.chdb] in Cargo.toml. This is a release candidate, taken to validate the engine before the v26.11.1 release; the crate's release gate still applies, so it does not publish against this pin.
Since chdb-core#261 the Linux libchdb.a is one relocatable object, libchdb.o, made by ld -r with only the C API left global. It has no libcxx__/libcxxabi__/libunwind__ members, so bundled_runtime_hidden found nothing to check and failed by design against v26.11.0-rc.1. For that layout the test now reads the archive's whole symbol table. It requires one definition from each bundled runtime (libc++, libc++abi, libunwind), so a missing runtime or stripped symbol table cannot pass. It then asserts that no GLOBAL, WEAK or UNIQUE definition, at any visibility, has a C++ runtime name. The macOS archive keeps the member layout, so the member check is unchanged there and for older Linux engines. Measured on v26.11.0-rc.1: 68 global definitions on linux-x86_64 and linux-aarch64, all C API; the three anchors are present as LOCAL.
Move the engine pin from v26.11.0-rc.1 to v26.11.0-rc.2 in the three places that carry it, as the release check's propose_bump step does: CHDB_ENGINE_PIN in update_libchdb.sh and build.rs, and engine under [package.metadata.chdb] in Cargo.toml, plus the comment that names the pin. rc.2 is rc.1 plus chdb-core#312: chdb_shutdown() no longer refuses after MergeTree use, the one-shot API works more than once per process, a statement that follows a failed query no longer gets the failed query's leftover output, and exiting with a connection open no longer breaks the engine teardown after an engine restart or with the static library. Its chdb.h differs from rc.1 only in CHDB_VERSION. The static archives keep the rc.1 layout, measured the same way: one prelinked libchdb.o whose 68 global definitions are all C API on linux-x86_64 and linux-aarch64, and 0 visible definitions among 59 runtime members on macOS arm64. bundled_runtime_hidden's note on the measured engines now says so. This is still a release candidate: the crate's release gate applies, so it does not publish against this pin.
On v26.11.0-rc.1, chdb_shutdown() refused once a MergeTree table had been used: "chDB global pool shutdown refused: ... MergeTreeBackgroundExecutorThreads", then "global thread pool did not become idle", because the MergeTree background executors outlived the engine. chdb-core#312 destroys them on shutdown, and rc.2 carries it. The new runtime_faces case writes twenty parts to a MergeTree table in a session, drops the session while the background merges have work, calls runtime::shutdown() and lets the process exit. Like every case there it runs in a process of its own, since a shutdown is one-way. Against the rc.1 library it fails with EngineCallFailed from chdb_shutdown (exit status 101); against rc.2 it passed 15 of 15 runs.
runtime::shutdown and docs/examples.md said that a process that simply exits does not need it. The engine does not support that: exiting with a connection still open leaves its teardown to run inside exit(), and while MergeTree merges run in the background that teardown can crash the process. Against the rc.2 library on linux-x86_64, 5 of 5 such exits died with SIGSEGV or SIGABRT, while dropping the connection first, with or without runtime::shutdown() afterwards, exited cleanly 10 of 10 times. The rc.2 release notes say the same: close every connection, or call chdb_shutdown(), before the process exits. The docs now say to drop every connection before the process exits and to call shutdown after the last one, and name the two ways a Rust program keeps a connection open at exit: std::process::exit runs no destructors, and a connection held in a static is never dropped. A code comment in shutdown also cited chdb.h by line numbers (1078-1080) that no longer point at chdb_shutdown; it now names the function's documentation instead.
wudidapaopao
added a commit
that referenced
this pull request
Nov 5, 2026
2.1.0 adds QueryResult::data_str (#59) and moves the engine to chdb-core v26.11.0-rc.2 (#65), so it is a minor release. The release-gate note in Cargo.toml said the crate does not publish against a release candidate. This release does, so the note now names the candidate it is published against. The Quick Start and docs/examples.md still asked for 1.1.0 and 1.0.0, which resolve to 1.x and never reach 2.x.
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.
Summary
Moves the engine pin from chdb-core
v26.9.2-rc.2tov26.11.0-rc.2(ClickHouse baseline masterdef2fdf4caa, 26.11.1.1). This PR first pinnedv26.11.0-rc.1; rc.2 is rc.1 plus chdb-core#312, which fixeschdb_shutdownafter MergeTree use, the one-shot API, leftover output after a failed query and the exit teardown. Besides the pin, it adapts one static-linking test to the new Linux archive layout, adds a runtime case for shutting down after MergeTree merges, and corrects theruntime::shutdowndocs about a plain process exit.This is a release candidate, taken to validate the engine. It is not on PyPI, and the full release will be
v26.11.1. The crate's release gate inCargo.tomlstill holds: do not publish against this pin.Changes
Pin. The same three edits the release check's
propose_bumpstep makes:CHDB_ENGINE_PINinupdate_libchdb.shCHDB_ENGINE_PINinbuild.rsengineunder[package.metadata.chdb]inCargo.toml, plus the comment that names the pin.github/scripts/check-engine-pin.shpasses. The repo stores no checksums. I checked the downloaded rc.2 assets against the release'sSHA256SUMS, and all matched:linux-x86_64-libchdb.tar.gz,linux-x86_64-libchdb-static.tar.gz,linux-aarch64-libchdb-static.tar.gzandmacos-arm64-libchdb-static.tar.gz. rc.2'schdb.hdiffers from rc.1's only inCHDB_VERSION, and is ABI-identical to the previous pin's.tests/bundled_runtime_hidden.rs. Since chdb-core#261, the Linuxlibchdb.ais prelinked byld -rinto one object,libchdb.o, and only the C API stays global. That fixes Static linking breaks backtrace #53. The archive no longer haslibcxx__/libcxxabi__/libunwind__members, so the test failed as it was written to: "no runtime members" means it is checking nothing._ZNSt3__15mutex4lockEv,__cxa_throwand_Unwind_RaiseException. A missing runtime or a stripped symbol table therefore cannot pass.GLOBAL/WEAK/UNIQUEdefinition, at any visibility, has a C++ runtime name (reserved_-prefixed orunw_*).tests/runtime_faces.rs: new caseshutdown_after_mergetree_merges. It writes twenty parts to a MergeTree table in a session, drops the session while the background merges have work, callsruntime::shutdown()and exits. On rc.1,chdb_shutdownrefused here ("global thread pool did not become idle"); chdb-core#312 fixed that. The case fails against the rc.1 library (EngineCallFailed, exit status 101) and passes against rc.2.runtime::shutdowndocs (src/runtime.rs,docs/examples.md). They said a process that simply exits does not need it. It does: exiting with a connection still open while MergeTree merges run can crash the process at exit, which the rc.2 release notes also say. The docs now say to drop every connection before the process exits and to callshutdownafter the last one. They also name the two ways a Rust program keeps a connection open at exit:std::process::exitruns no destructors, and a connection held in astaticis never dropped. A stalechdb.hline reference in a code comment is replaced by the function it pointed at.No other binding code changes.
Verification (local, Linux x86_64, Rust 1.97.0, against rc.2)
Dynamic.
./update_libchdb.sh --localwas used (the tarball it downloaded matchesSHA256SUMS), thenLD_LIBRARY_PATHpointed at the repo root, instead of--global, which needs sudo:cargo fmt --check: passcargo clippy --all-targets -- --deny warnings: passcargo build --verbose: passcargo test -- --test-threads=1, run twice: all pass both times, including the 16runtime_facescases and the 64 doc testscargo test --features durable -- --test-threads=1: all pass except the known heartbeat flake (see Notes)cargo test --features durable-s3 --lib -- --test-threads=1 durable::backends: 20 passedcargo run --features durable --example <name>: exit 0, nothing on stderrtests/version.rspasses. That includesexpected_and_reported_engine_versions_agree, which compares the build's26.11.0-rc.2with what the loaded library reports.shutdown_after_mergetree_mergesagainst the rc.1 library fails as intended; against rc.2 it passed 15 of 15 runs.Static. These are the same steps as the CI
staticjob, with no libchdb installed; build.rs fetched the rc.2 archive, whoselibchdb.ais byte-identical to the checked asset:cargo clippy --all-targets --all-features -- --deny warnings: passcargo test --features static --no-run --tests: 17 binariescheck-static-link.sh: every binary carries the engine--test-threads=1 < /dev/null: all pass, including the 16runtime_facescasescargo test --features static --doc: 64 passedNot verified locally
durable_s3tests need credentials, so they were not run, same as in CI.Notes
durable_conformance::a_heartbeat_running_through_commits_does_not_disturb_themfailed withLeaseFencedin the rc.2 durable run, while the machine was under parallel load, and passed in 3 of 3 reruns of thedurable_conformancebinary. It also failed 2 of 7 runs against rc.1. The test usesFakeEnginewith a 300 ms lease, so it never touches libchdb. It looks like an engine-independent timing flake, not a regression from this bump.bindings.mdstill says to skipchdb_shutdown"if the process is simply exiting", which disagrees withchdb.hand with the rc.2 release notes. That file is in chdb-core, so it is not changed here.🤖 Generated with Claude Code
Note
Pin chdb-core engine to v26.11.0-rc.2 and validate shutdown after MergeTree merges
runtime::shutdown(src/runtime.rs, docs/examples.md)shutdown_after_mergetree_mergesintegration case that inserts 200,000 rows into a MergeTree table, drops the session, then shuts down (tests/runtime_faces.rs)Macroscope summarized b17cf1b.