-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[python] Update pyarrow dependency #1926
Comments
Here are the issues:
Here is my proposal:
|
sounds good. there also is no rush to remove the hotfix; if pyarrow is already secure it does nothing, so in the worst case it’s an extra import and some light processing. |
Proposal works for me. Alt, which you are free to ignore: given what I've read about the actual fix (i.e., in code we don't use), it would also be OK to:
|
+1 from me |
Additional non-joy: we found on #1936 that with
on MacOS either This should be followed up on. Stack trace: https://gist.github.com/johnkerl/eb5874e94d0cc4768114faadcb989e83 |
Here is the follow-up:
|
Given the above, namely:
I conclude that we'll need to simply stick with All relevant PRs on this repo have been implemented and merged. |
Update: there is a mitigation in
so we can handle this, but, only after a core bump. |
No longer blocks 1.6 |
Nvm it's dependent on import order. So importing In light of that, could upper version bound here get removed? There are no wheel available for pyarrow versions this old for python 3.12, which is giving some CI grief over on cellxgene_census: https://github.com/chanzuckerberg/cellxgene-census/actions/runs/9405819588/job/25907864054?pr=1189 |
Please keep this issue open until these are resolved: |
This is for the
pyarrow
CVE. @bkmartinjr has verified we don't use the vulnerable code path, but, it's good optics for us to update.The text was updated successfully, but these errors were encountered: