Andrushika commented on issue #70953:
URL: https://github.com/apache/airflow/issues/70953#issuecomment-5163611291
Thanks for preparing the release, Jarek!
A side note: Some mentions in the issue body did not take effect. The body
mentions many different users, but in the rendered body only the first 50 are
real mention links. I did not get the notification from GitHub, but found this
RC testing through the vote email instead. I think a follow-up comment that
mentions the remaining users may reach them.
Tested #70301 with `apache-airflow-providers-microsoft-azure==14.1.0rc1` on
released `Airflow 3.3.0`. Setup: `breeze --use-airflow-version 3.3.0`, RC wheel
from PyPI, Azurite as the blob backend.
- `ProvidersManager().remote_logging_handler_by_scheme("wasb")` returns
`WasbRemoteLogIO`. The scheme is registered on the released core.
- `resolve_remote_task_log` with `remote_base_log_folder =
wasb://rc-test/logs` builds `WasbRemoteLogIO` through provider dispatch. I
mocked the legacy discovery and it was not called.
- `WasbRemoteLogIO.from_config()` reads the `[logging]` section as expected.
The `wasb://` prefix is stripped and the container falls back to `airflow-logs`.
- Uploaded a log file with `io.upload()` and read it back with `io.read()`
against Azurite. The content matched and the log source URL points at the right
blob.
Works as expected.
Drafted-by: Claude Code (Fable 5); reviewed by @Andrushika before posting
--
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]
