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
As discussed on Slack, there seems to be an issue around buffering or back pressure support when logging output from Citadel.
I'm running a task as follows:
letstream=tryawaitexecuteCommandStream("script.sh", inShell: true)
for tryawaitoutput in stream {
switch output {caselet.stdout(buffer):print(String(buffer: buffer), terminator:"")caselet.stderr(buffer):print(String(buffer: buffer), terminator:"")}}
where "script.sh" is a simple
echo"❌ this must fail"exit 1
but the echo isn't showing up in the logs.
An ugly fix for this is to introduce a delay before exiting:
echo"❌ this must fail"
sleep 0.1
exit 1
Best I can tell, there's no way on the consumer side of the AsyncThorwingStream to ensure all messages have been delivered before the stream terminates.
The text was updated successfully, but these errors were encountered:
As discussed on Slack, there seems to be an issue around buffering or back pressure support when logging output from Citadel.
I'm running a task as follows:
where "script.sh" is a simple
but the echo isn't showing up in the logs.
An ugly fix for this is to introduce a delay before exiting:
Best I can tell, there's no way on the consumer side of the
AsyncThorwingStream
to ensure all messages have been delivered before the stream terminates.The text was updated successfully, but these errors were encountered: