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
Lately i've been working with rust a lot and one thing is driving me crazy a little during production deploy.
I dont know it it properly works for other (outside compiled) runtimes like c# and Java, but SST hides all output from async executions of cargo-lmabda.
It could be easilly solved by using callback from execAsync and piping it to console. Just how it works with workers just few lines above workers.stdout(input.workerID, data.toString());
Or i guess even directly calling console.log() since thats how internally works eslint implementation in node runtime (i guess).
I could try to implement it later this month if this makes sense.
The text was updated successfully, but these errors were encountered:
Anyways just from curiosity, is there a reason execAsync is used ? Using spawn just like in worker process would eliminate problem caused by combination of promisify and callbacks.
Hi,
Lately i've been working with rust a lot and one thing is driving me crazy a little during production deploy.
I dont know it it properly works for other (outside compiled) runtimes like c# and Java, but SST hides all output from async executions of cargo-lmabda.
It could be easilly solved by using callback from execAsync and piping it to console. Just how it works with workers just few lines above workers.stdout(input.workerID, data.toString());
Or i guess even directly calling console.log() since thats how internally works eslint implementation in node runtime (i guess).
I could try to implement it later this month if this makes sense.
The text was updated successfully, but these errors were encountered: