Skip to content

Preserve fbuild daemon environment overrides#1170

Merged
zackees merged 1 commit into
mainfrom
fix/preserve-fbuild-daemon-env
Jul 24, 2026
Merged

Preserve fbuild daemon environment overrides#1170
zackees merged 1 commit into
mainfrom
fix/preserve-fbuild-daemon-env

Conversation

@zackees

@zackees zackees commented Jul 24, 2026

Copy link
Copy Markdown
Member

Summary

This addresses the review finding on #1169, including FBUILD_DAEMON_PORT, after that PR auto-merged before the follow-up commit landed.

Validation

  • soldr cargo check -p fbuild-cli on current main plus this one-file diff
  • git diff --check

@zackees
zackees marked this pull request as ready for review July 24, 2026 01:09
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@zackees, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c791fc6a-9b44-440d-a630-08b1fb795a9b

📥 Commits

Reviewing files that changed from the base of the PR and between f896b7e and fb8cbf2.

📒 Files selected for processing (1)
  • crates/fbuild-cli/src/daemon_client.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/preserve-fbuild-daemon-env

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@zackees
zackees merged commit 0c457eb into main Jul 24, 2026
88 of 93 checks passed
@zackees
zackees deleted the fix/preserve-fbuild-daemon-env branch July 24, 2026 01:12
@fastled-project-sync fastled-project-sync Bot moved this to Triage in FastLED Tracker Jul 24, 2026
zackees added a commit to zackees/soldr that referenced this pull request Jul 24, 2026
running-process 4.6.1 changed user_baseline_environment() on Unix from a
snapshot of the current process environment to a scrubbed login baseline
(USER/LOGNAME/HOME/SHELL/default PATH + locale/TZ/TMPDIR only). The daemon
spawn sites do env_clear().envs(baseline), so SOLDR_CACHE_DIR stopped
reaching the daemon: it bound its socket under the default ~/.soldr root
while wrappers polled $SOLDR_CACHE_DIR/cache/soldr-daemon/sock, burned the
full 30s spawn-retry budget on NotRunning, wrote the daemon-unavailable
marker, and every compile fell back to direct uncached rustc (soldr#1657
degradation firing on all Linux CI lanes; 400 fallback lines in the
cancelled 0.8.23 release run).

Overlay the whole SOLDR_* namespace (case-insensitive, matching the
FBUILD_* passthrough in FastLED/fbuild#1170) on top of the baseline at all
three spawn sites: both Unix Command spawns and the Windows
CreateProcessW environment block, which has always been scrubbed via
CreateEnvironmentBlock and silently relied on the default root.

Verified in the Linux docker runner: before, a hello-world build stalled
30s and built uncached with the daemon socket in ~/.soldr-dev; after, the
daemon binds under $SOLDR_CACHE_DIR and the build completes in ~1s with
no fallback lines.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

1 participant