Repository navigation
Release Python SDK 0.48.0 for VGI protocol v3 - #98
Merged
Merged
Conversation
Remove the proposed user/session pushdown controls. Reuse ATTACH offer/selection and per-query eligibility/preparation. Documentation only; EC2 inventory and all 11 manifest tests passed.
EC2 Linux ARM64 diagnostic configure passes at audited e1784fa42310. All107 native C++ sources attempted:53compile/54fail; generated describe.c also compiles. Runtime and final linking remain unqualified. Runner lint/isolation guards and11manifest tests pass. Existing1.5 engine and build remain unchanged.
The transactor's client and server speak over AF_UNIX, which the client already treats as POSIX-only. These tests opened an AF_UNIX listener directly and failed on the Windows CI legs (Python 3.13 and 3.14). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- check_duckdb2_manifest: hash LF-normalized audit bytes, so a CRLF checkout (or a fixture written with write_text on Windows) matches the manifest digest. LF files hash exactly as before. - test_demo_startup_rejects_an_occupied_port: skip on Windows. waitress sets SO_REUSEADDR, which on Windows lets a second listener bind an occupied port, so the child really does bind and become ready. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pytest copies the test id into PYTEST_CURRENT_TEST. With the 32 KiB+ token value as its id, setup and teardown raised 'the environment variable is longer than 32767 characters' on Windows, which also cut the CI log off at the ERRORS header. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Publishes the Python SDK for the successor VGI wire contract,
vgi.v3/3.0.0.vgi-rpc>=0.52.3for complete outer IPC framing. Includes the one-shot writable-scan continuation fix.Compatibility: requires a native VGI build that speaks
vgi.v3/3.0.0; oldervgi.v2extensions are incompatible. The protocol is qualified with the DuckDB 1.5 adapter and the DuckDB 2.0/Nanoarrow candidate. Automatic whole-query pushdown remains separate adapter work.Validation: Ruff, strict mypy for runtime and tests, package builds and metadata checks passed. The full Python suite qualified 4,609 passing tests with 192 expected/environment skips; four initial failures were resolved by one stub-only cast correction and an exact Rust checkout path, then targeted tests passed. Existing full native SDK language matrices and canonical HTTP qualification cover the runtime changes.
The core wheel continues to bundle import-only fixture modules. The separate vgi-fixtures wheel is built and checked, while its PyPI publication remains disabled because that project has not been provisioned.