Bootstrap: environmental sanitisation, package install robustness - #26433
Merged
Conversation
Member
Author
|
Fixes at least one failure mode: https://discord.com/channels/440868230475677696/473506116718952450/1544263017632636969 |
drashna
approved these changes
Sep 2, 2026
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.
Description
Bootstrap script:
LC_ALL=C, drop out of any active Python venv, wipePYTHON*variables (keepingPYTHON_TARGET_VERSION), and clear conda/pip/uvoverrides that would affect dependency resolution or builds. Proxy, TLS, and index/mirror variables survive, since corporate networks need them.--no-projecttouv runwhen determiningQMK_DISTRIB_DIR, souvignores anypyproject.tomlin the invoking directory.brew install/brew upgradenow run per-formula and retry with--build-from-sourcewhen no bottle exists. Intel machines get a warning before the pre-install countdown that source builds can take a long time.CI workflow:
emaint sync -a || emerge --sync --quiet || emerge-webrsync -q, since rsync-based sync is unreliable from GitHub runners (no IPv6 routing, flaky mirrors) and webrsync has been solid.&&-chains each distro's metadata sync and package install, so a failed sync no longer counts as a successful attempt, and the step fails outright after 10 failed attempts.brew updateup to 10 times (withbrew update-resetbetween attempts) before running the bootstrap script, and stop at the first success.Types of Changes
Checklist