You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Source install restarts stale global fbuild-daemon binary #830
A local source/editable install can install a fresh venv fbuild.exe but still restart a stale global daemon binary from %USERPROFILE%\.local\bin\fbuild-daemon.exe.
Observed after installing merged PR #828 / commit ba50fc5 into FastLED's venv:
.venv\Scripts\fbuild.exe--version
.venv\Scripts\fbuild.exe daemon restart
.venv\Scripts\fbuild.exe daemon status
Get-Process-Id <status-pid>|Select-Object Path
Expected: the CLI installed from source should spawn a matching daemon build from the same install/version, or install/update the daemon binary it will restart. Otherwise local fbuild fixes in daemon/core code cannot be validated downstream, and users can think they are testing a fresh fbuild while the daemon is still old.
Activity
fix(cli): spawn sibling fbuild-daemon binary, not bare PATH lookup (#830