Repository navigation
feat: Support R2 URLs with jurisdictions - #757
Conversation
|
I don't understand from the GitHub action logs which of my changes are triggering the pre-commit failure |
|
Thanks for the PR. In regards to the pre-commit error, I think the issue is probably that it's not pinned to a specific version of ruff, and that a new version of ruff added that lint. Separately, the code you're touching in this PR, So if you could make a PR to upstream |
|
Hi @kylebarron, this has been merged upstream: apache/arrow-rs-object-store#815 |
|
great thanks, if you could merge in main, that should fix the CI |
|
Yep, all green now |
…797) * chore(pyo3-object_store): Bump to pyo3 0.30 and prepare 0.13 release Also bumps pyo3-async-runtimes to 0.30, and adds the unreleased R2 jurisdiction support (#757) to the changelog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: Build obstore against pyo3-object_store 0.12 from main via git The in-repo pyo3-object_store now needs pyo3 0.30, but obstore is still on pyo3 0.29 (pyo3-arrow and pyo3-file have no 0.30 release yet), so the path dependency no longer resolves. Pin obstore to pyo3-object_store at the current main rev until obstore moves to 0.30. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Relevant upstream docs: https://developers.cloudflare.com/r2/reference/data-location/#jurisdictional-restrictions