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
Minor issue, but the log of stanek.js automatically starts up despite having manually closed, since the information it provides isn't always useful, I think it should be made so that its log doesn't start up automatically.
The text was updated successfully, but these errors were encountered:
Agreed that the output isn't useful. The reason Stanek keeps its tail window open is because while it is running, daemon.js is crippled (home RAM is reserved entirely for charging stanek) so it needs to be made obvious (and easily killable) for anyone who is otherwise left wondering why daemon.js isn't running any batching scripts on home.
If I ever get around to implementing #362 , then I will certainly stop this behaviour, since stanek.js will no longer be doing anything that impacts other scripts.
There are two options for dealing with this today:
Run autopilot.js with --no-tail-logs to manage what gets tailed yourself (affects all scripts)
Create a file "stanek.js.config.txt" and permanently set the --no-tail argument as an override to never tail this script again. The contents of the txt file would look like this: { 'no-tail': true }
Minor issue, but the log of stanek.js automatically starts up despite having manually closed, since the information it provides isn't always useful, I think it should be made so that its log doesn't start up automatically.
The text was updated successfully, but these errors were encountered: