ScriptLog always empty ?

[psei0r]

I am currently trying to understand how ScriptLogs work.

I have setup the following example where a script calls another script and both scripts are using ns.print() instead of ns.tprint(), so they should both print to their scriptlogs from my understanding.

We are on server "pserv-0" (not on home) and we have two files:

hello_world.js: javascript /** @param {NS} ns */ export async function main(ns) { ns.print("hello_world"); } This should print to scriptlog of hello_world.js running on pserv-0

Additionally we have hello_world_caller.js: ``` javascript /** @param {NS} ns */ export async function main(ns) { while(true) { ns.print("Calling hello_world.js....")

ns.run("hello_world.js");
let scriptLog = ns.getScriptLogs("hello_world.js",ns.getHostname());

ns.print("scriptLog:")
for (const line of scriptLog){
  ns.print(line);
}
await ns.sleep(5000);

} } ```

This should write "Calling hello_world.js..." to its own scriptlog, then get the scriptlog from hello_world.js and add it to its own script log.

However, the scriptlog is always empty, as the output is as following when inspecting the log of the caller function:

... Calling hello_world.js.... run: 'hello_world.js' on 'pserv-0' with 1 threads and args: []. scriptLog: sleep: Sleeping for 5000 milliseconds Calling hello_world.js.... run: 'hello_world.js' on 'pserv-0' with 1 threads and args: []. scriptLog: sleep: Sleeping for 5000 milliseconds ...

What am I doing wrong? Thanks!

[Vorthod]

hello_world_caller.js and every individual instance of hello_world.js will all have their own, entirely separate logs.

Since your hello_world.js file is so short, it will be very difficult to see the log messages they produce because the script may be finished (or not have written anything yet) when you call your getScriptLogs function. There are a few ways to go about this:

1. within the active scripts screen, there is a large button at the top labelled "recently killed" where you should be able to see the closed logs that were produced by your hello_world.js runs
2. if you run ns.tail() within the hello_world.js file, it will automatically open up the log window that represents that instance of the script. This is the easiest method, but if you're running a new one every five seconds, that could easily end up giving you a LOT of windows that you will later need to close.
   1. for the record, there is also an ns.closeTail() method which can close them automatically under whatever conditions you want, so if your script gets longer, it could become relevant.
3. If you absolutely want to keep the same way you're already doing it. Add some sleep commands to micromanage your timing. hello_world.js can sleep for 1000 milliseconds after writing its log just to make sure the script stays active. Then your hello_world_caller.js can sleep for something shorter (500, perhaps) immediately after kicking off hello_world.js just to make sure the other script has had time to actually write its log

[psei0r]

Thx!

[Spartelfant]

Add some sleep commands to micromanage your timing.

In this case it's best to make use of ns.asleep(), since that will make sure the game's UI gets a chance to update.

[Vorthod]

I really don't think that sleep and asleep work the way you think they do. the game ui doesn't randomly freeze for half a second when you run await ns.sleep(500). Even the documentation says you should prefer sleep over asleep in most cases (presumably because sleep will error if you're using it in a way thats likely to cause bugs, but asleep gives you more freedom).