aglinxinyuan commented on PR #6182: URL: https://github.com/apache/texera/pull/6182#issuecomment-4888251453
## Test results CI is fully green after the fix — every check that was failing now passes. | check | before | after | |---|---|---| | build / pyamber (3.10) | ❌ fail (31s) | ✅ pass (1m22s) | | build / pyamber (3.11) | ❌ fail | ✅ pass (1m44s) | | build / pyamber (3.12) — LICENSE-binary drift check | ❌ fail | ✅ pass (2m58s) | | build / pyamber (3.13) | ❌ fail | ✅ pass (4m38s) | | build / amber-integration (ubuntu-latest, 17) | ❌ fail | ✅ pass (6m02s) | | build / amber-integration (macos-latest, 17) | ❌ fail | ✅ pass (6m52s) | | Bench | ❌ fail | ✅ pass (5m14s) | | Required Checks | ❌ fail | ✅ pass | All were failing on the same `uv` error — `× No solution found … aiobotocore==2.25.1 depends on botocore>=1.40.46,<1.40.62 … you require botocore==1.43.40` — so the dependency-install step never completed. ### Local verification before pushing - **Resolution** — `uv pip compile` (0.11.26, same as CI) of `amber/requirements.txt` + `amber/operator-requirements.txt` resolves cleanly on py **3.10 / 3.11 / 3.12 / 3.13**. The resolved tree differs from `main` by exactly four packages: botocore, boto3, aiobotocore, s3transfer. - **LICENSE-binary drift** — ran `bin/licensing/check_binary_deps.py --ignore-transitive-version python` against the resolved manifest: no direct-dep drift, and the added/stale/transitive-drift sets are byte-identical to `main` (i.e. nothing new introduced). - **Functional smoke test** — installed the upgraded stack and constructed `botocore`/`boto3`/`aiobotocore`/`s3fs` clients plus pyiceberg's `FsspecFileIO` (the #4272 S3 FileIO path) — all import and initialize on the new versions. The `amber-integration` legs (which spin up Python workers and exercise the Iceberg/S3 path end-to-end) passing is the strongest confirmation the bump is safe. -- 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]
