The GitHub Actions job "Tests" on airflow.git/onikolas/cloudwatch_logging_remote_af3 has failed. Run started by GitHub user o-nikolas (triggered by o-nikolas).
Head commit for run: ad86d22b987202af9fc06354187d4a3ddd687b55 / Niko Oliveira <[email protected]> Fix Cloudwatch remote logging There were three main issues: 1) A circular loop that eventually fails due to call depth exceeded. This is because the handler was lazily initted during the first log emission. But when the handler is created some code down stream tries to log, and since there is no handler yet (because we're in the middle of creating it), it tries to create another one, and we were spinning ad infinitum. 2) The stream name is not set on read, because we don't call set_context anywhere in the SDK path, and the processor doesn't have access to the TI anyway (which is used for the stream name). So a 0 byte stream name was being used and was causing a failure in Watchtower. 3) read is also failing because it is using the relative_path as the stream name, which is almost right, but the name isn't sanitized (there are some characters that cloudwatch doesn't allow in a stream name). set_context used to sanitize the name and set it, but it isn't called in the SDK path. Report URL: https://github.com/apache/airflow/actions/runs/14254941286 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
