Compile output no longer emitted continuously

[rishabkaushik]

This is not a big issue but with recent release the compile output is no longer emitted and just gets appended after the action is completed. Is this how it is going to be?

Again, I have no problem with it but earlier it looked cool with raining characters. 😀

Related commit I assume: d51fc60

[sebjulliand]

Yep; the spooled output from CL commands used to be written directly to the standard output by the system or cl commands.
Since the CL commands are now run through Mapepire, they produce actual spooled files that are read after the action is done. It can't be "streamed" anymore 😅

[rishabkaushik]

Thanks for all the good work you guys are doing! Really appreciate.

[sebjulliand]

Thanks a lot 🙏🏻

[rishabkaushik]

@sebjulliand I am having a related problem with compilation.

I have a local repo setup and based on it I have my custom actions.json to compile the programs after deployment. Although this works but sometimes it is taking a lot of time sometimes more than a minute to even start the action server side. I assume something is waiting for something. A full compile sometimes taking up to 6 minutes(4 min wait and 2 min compilation and fetching spools).

The terminal stays on this screen for quite sometime before starting the execution of it server-side.

I checked code for IBM i output and there is a lot happening there and in an infinite loop i guess? I am not sure what it is trying to do. Mostly it is Running CL through SQL statements. I can try an replicate this and maybe debug the extension but are you aware of any recently introduced mechanism for synchronous processing for anything that happens?

[rishabkaushik]

The program is not that big.

[sebjulliand]

Nothing related to the execution queue has been changed lately. The queue has been introduced in 3.0.0.
But I'm not sure that's related to the queue. I also had a similar issue when running CL commands from the Db2 extension using the cl: prefix. I'm not 100% positive, but that could be related and that would mean Mapepire itself is causing this ☹️