ci: reproduce Python 3.14 Windows setup failure - #1
Draft
KDB-Wind wants to merge 570 commits into
Draft
Conversation
… special characters
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
20 participants
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.
Purpose
Temporary fork-only validation for upstream PR HKUDS#5412. This Draft PR is intended to reproduce the
Python (Windows, 3.14)GitHub Actions check for the background child-output buffering fix.Scope
The source branch contains the same two code/test files as the upstream candidate:
nanobot/process_runtime.pytests/gateway/test_runtime.pyThis PR is for CI diagnosis only and is not intended for merging or submission upstream. The fork's
mainbranch is older than the source branch, so GitHub may display historical upstream commits in the comparison.Expected check
Observe whether the Windows Python 3.14 job can download
astral-sh/setup-uv@v4and proceed past job setup, independently of the upstream run's transient HTTP 429 failure.