AlejandroMorgante opened a new issue, #68482:
URL: https://github.com/apache/airflow/issues/68482
I have a PR (#68479) failing on the **Compat 2.11.1** CI job on tests that
have nothing to do with Azure. Looking at the logs, the actual failures are all
in `test_wasb.py`:
```
FAILED
providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_wasb.py::TestWasbHook::test_sas_token_connection[sas_conn_id-sas_token]
FAILED
providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_wasb.py::TestWasbHook::test_sas_token_connection[extra__wasb__sas_conn_id-extra__wasb__sas_token]
FAILED
providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_wasb.py::TestWasbHook::test_sas_token_connection[http_sas_conn_id-sas_token]
FAILED
providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_wasb.py::TestWasbHook::test_sas_token_connection[extra__wasb__http_sas_conn_id-extra__wasb__sas_token]
```
Error:
```
AssertionError: assert False
where False = 'https://login.blob.core.windows.net/'.endswith('token/')
where 'https://login.blob.core.windows.net/' = BlobServiceClient(...).url
```
The test asserts `conn.url.endswith(sas_token + "/")` but
`BlobServiceClient.url` now returns `https://login.blob.core.windows.net/`
instead of the URL with the SAS token appended.
Digging into it, this seems to be caused by `azure-storage-blob` being
bumped from **12.29.0 → 12.30.0** in the constraints update `e3ed4035ee`
(2026-06-12). The Compat test runs with `--providers-skip-constraints` so it
picks up 12.30.0 from PyPI, and in that version `BlobServiceClient.url` appears
to no longer reflect the SAS token in the URL.
This is blocking unrelated PRs. Can someone take a look?
--
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]
