openviking: Add versions 0.4.17, 0.4.17.1, 0.4.18, 0.4.19, 0.4.20, 0.4.21, 0.4.22 - #2391
Draft
riseproject-dev[bot] wants to merge 2 commits into
Draft
riseproject-dev[bot] wants to merge 2 commits into
riseproject-dev[bot] wants to merge 2 commits into
Conversation
Contributor
|
…4.21, 0.4.22 Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
riseproject-dev
Bot
force-pushed
the
github-actions/nightly-upgrade/openviking
branch
from
September 28, 2026 08:19
a59d227 to
cbc886b
Compare
riseproject-dev
Bot
changed the title
…e, cap rustc parallelism, relax 0.4.21/0.4.22's tree-sitter pin The nightly-upgrade bot regenerated this branch from main to add 0.4.22, force-pushing a fresh "Add versions ..." commit that dropped every prior fix commit on this branch (the perl/OpenSSL-licence fix, the thin-LTO fix, and the FindPython3 patches for 0.4.17-0.4.21) back to the pre-fix state, leaving only the 0.4.16 patch. Restore all of it: - CIBW_BEFORE_ALL_LINUX installs perl (openssl-src's Configure needs FindBin.pm, gotcha 46) and the vendored-licence step fetches OpenSSL's LICENSE.txt when Cargo.lock pins openssl-src (0.4.18+). - patches/openviking/<version>/0001-*.patch (FindPython3 Development.Module) carried forward to 0.4.17-0.4.22 -- verified each applies cleanly against its own upstream tag. On top of the restored state, apply this run's fixes: - CARGO_PROFILE_RELEASE_LTO=thin (already restored) mitigates but does not eliminate rustc's heap corruption compiling ragfs-python: 0.4.17.1 SIGABRT'd again with "malloc(): unsorted double linked list corrupted", and 0.4.19 hung silently until the 360-minute job timeout cancelled it. Both match gotcha 228 (rustc OOM/heap-corruption under concurrent codegen on the 4-core riscv64 runners); add CARGO_BUILD_JOBS=2, the fix gotcha 228 and several other Rust ports in this repo already use. - 0.4.21's test install failed: "Could not find a version that satisfies the requirement tree-sitter==0.25.2 (from openviking)". tree-sitter never published a riscv64 wheel for 0.25.2 (riscv64 wheels start at 0.26.0), so PIP_ONLY_BINARY=:all: in the test environment has nothing to install. 0.4.20 pins tree-sitter loosely (>=0.23.0); 0.4.21 tightened it to an exact pin, and the newly-added 0.4.22 keeps the same exact pin. Patch pyproject.toml in both to relax it back to a lower bound so the resolver can pick 0.26.0; this port's smoke test and pytest selection never touch tree-sitter's Python API directly.
This branch has not been deployed
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
1 participant
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.
Automatically generated by the nightly
check_versions.pyrun.openviking v0.4.16 -> v0.4.17, v0.4.17.1, v0.4.18, v0.4.19, v0.4.20, v0.4.21, v0.4.22
Every
- version:entry added todocs/packages/openviking.yamlis built by this PR's ownbuild-openviking.ymlrun; merging publishes the wheels.