New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display build process messages to console #3739
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: