zarqon
Well-known member
A while back, my routine scripts started hanging whenever they reached a point where another script was called using cli_execute("<script> <parameter>").
Using only the script name still works, but as soon as you also pass the first parameter (something I commonly did) mafia will hang. By hang, I mean consume full CPU but appear to do nothing. Further commands can be entered but they are queued.
Some ways to duplicate this error:
1) Call a nonexistent script, i.e. "call thisisnotascriptname".
2) Call a script and pass a parameter on the same line, i.e. "call bounty go" or "call getpipes 1".
Based on when this started happening, my guess is that it's related to the "Java is not ASH" change for strings.
It would be nice if I could continue passing parameters to scripts in the CLI, but regardless of whether or not that functionality is retained, the hanging is undesirable behavior.
Using only the script name still works, but as soon as you also pass the first parameter (something I commonly did) mafia will hang. By hang, I mean consume full CPU but appear to do nothing. Further commands can be entered but they are queued.
Some ways to duplicate this error:
1) Call a nonexistent script, i.e. "call thisisnotascriptname".
2) Call a script and pass a parameter on the same line, i.e. "call bounty go" or "call getpipes 1".
Based on when this started happening, my guess is that it's related to the "Java is not ASH" change for strings.
It would be nice if I could continue passing parameters to scripts in the CLI, but regardless of whether or not that functionality is retained, the hanging is undesirable behavior.