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
Problem
When diagnosing pantsd issues, it's really hard to get accurate pantsd logs, because the first thing the user tries is ./pants clean-all, which removes anything of utility.
Solution
Store a pid-indexed copy of the pantsd logs either:
Whenever the daemon restarts, so on PantsDaemon.terminate().
Whenever we run a goal that would kill pantsd (./pants clean-all and ./pants kill-pantsd).
Result
Whenever we shutdown pantsd, a file like .pants.d/pantsd/pantsd.1234.log should be there after everything is said and done.
The text was updated successfully, but these errors were encountered:
Problem
When diagnosing pantsd issues, it's really hard to get accurate pantsd logs, because the first thing the user tries is
./pants clean-all
, which removes anything of utility.Solution
Store a pid-indexed copy of the pantsd logs either:
PantsDaemon.terminate()
../pants clean-all
and./pants kill-pantsd
).Result
Whenever we shutdown pantsd, a file like
.pants.d/pantsd/pantsd.1234.log
should be there after everything is said and done.The text was updated successfully, but these errors were encountered: