jason810496 opened a new issue, #70077: URL: https://github.com/apache/airflow/issues/70077
Follow-up to #69302 (see [discussion](https://github.com/apache/airflow/pull/69302#discussion_r3608363125)). #69302 sends TS SDK logs to stderr when the log socket disconnects after a fatal error, but there's a separate gap in the subprocess startup lifecycle: 1. TS subprocess started (via `popen` on the coordinator side) 2. TS logger can still emit records here, before it has connected to the coordinator's `--log` socket 3. TS subprocess connects to the coordinator 4. All logger output is forwarded over the `--log` socket Stage 2 output currently has nowhere reliable to go, since a `LogChannel` only exists post-connect. Java and Go SDKs already buffer logs emitted in this window and flush them to the log socket once connected — TS SDK should do the same instead of dropping them. Reference: diagram in #70076 may help clarify the lifecycle. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
