Running a Typescript script from within another Typescript script; runs forever, never returns

[ingoratsdorf]

I have two TS scripts.

One is a keystore script that has been extensively tested and runs will when run with test data.
It saves, retrieves or deletes keys. Just for background info.

I have written the following test script to see how and if I can call the keystore script from within my test script. I obviously can, but it never returns and runs forever and ever.

Test script:

import * as wmill from "windmill-client"

export async function main(){
  const mysqlRes = await wmill.getResource('u/ingo/n8n_keystore');
  const jobId = await wmill.runScriptAsync('u/ingo/keystore', null, {
    "mysqlResource": mysqlRes,
    "tableName": "keystore",
    "uuid": "test",
    "command": "put",
    "value": "test value"
  });
  console.log(`Got jobId = ${jobId}`);
  const result = await wmill.waitJob(jobId, true);
}

Result:

--- BUN INSTALL ---

bun install v1.2.4 (fd9a5ea6)
Saved lockfile
+ windmill-client@1.494.0
1 package installed [6.00ms]

--- BUN CODE EXECUTION ---

Got jobId = 01972e3f-eca8-f13e-4961-4402c6dba18c
job 01972e3f-eca8-f13e-4961-4402c6dba18c has not started yet
sleeping 0.5 seconds for jobId: 01972e3f-eca8-f13e-4961-4402c6dba18c
job 01972e3f-eca8-f13e-4961-4402c6dba18c has not started yet
sleeping 0.5 seconds for jobId: 01972e3f-eca8-f13e-4961-4402c6dba18c
job 01972e3f-eca8-f13e-4961-4402c6dba18c has not started yet
sleeping 0.5 seconds for jobId: 01972e3f-eca8-f13e-4961-4402c6dba18c
[..]

Has anybody any idea of what is happening here? Obviously the script has started, because I have an ID. If there was an issue with the passed parameters, surely the thing should error out? But it does not.
I have checked the mysqlRes object, it is retrieved and is correct.

Dunno what to do from here.

[ingoratsdorf]

So the obvious option to run other local scripts is as easy as in typescript itself. Doh!

As noted in https://www.windmill.dev/docs/advanced/sharing_common_logic

import { keystore } from './keystore.ts';

Still does not really explain why the API call runs forever, never returns and does not generate an error of sort.

[rubenfiszel]

how many workers do you have? If just one then that's why, you can only execute one job at a time so the script calling the other is preventing the other to start for lack of worker.
also you can go on the runs page, filter for all and get more info

[ingoratsdorf]

Interesting idea ;-)
I have resolved the issue differently now but added a few more workers for good measure.
Not that they take much memory anyway.

Thanks, @rubenfiszel for the advice.

[ingoratsdorf]

I can confirm that calling scripts works well when having an available worker, ie you need a minimum of 2 :-)
I had to mic deno and bun TS and it works like a charm. :-)