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
15:25:35 - INFO - Guard is now watching at '/tmp/test'
[1] guard(main)> Puma starting in single mode...
* Version 3.8.2 (ruby 2.4.0-p0), codename: Sassy Salamander
I checked the wiki under logging, but I couldn't see any obvious example of how sub-processes output should be handled. I'm sure this is simple, but perhaps we could also update the documentation.
This happens even without guard-puma, also just with rails and sidekiq. I have to open guard, and press enter for it all to run, before it shows up normally.
I'm currently trying to figure out a solution to jc00ke/guard-puma#24
By default,
guard-puma
spawnspuma
and it writes several lines of startup information, and then per-request log lines, tostdout
.The problem is this clobbers the guard shell.
What is the correct way to log lines of output when executing sub-processes via guard?
The text was updated successfully, but these errors were encountered: