-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix: Pin numpy<2 #85
fix: Pin numpy<2 #85
Conversation
You might wanna update |
I tested the main repo locally (without this PR) and I had no issues at all See https://github.com/MeltanoLabs/tap-universal-file/actions/runs/9761082046/job/26941341616 Can you give some steps to replicate what you're seeing @mjsqu ? Or @edgarrmondragon can you see it? My steps were
I checked because I looked for an issue on pyarrow for this and I didn't see anything. |
@visch how did you test the tap? |
Also, according to numpy/numpy#26191, pyarrow 16.0+ is required to support numpy 2.0 |
#87 should improve compatibility |
@edgarrmondragon I was running
I get the error
So the test must be wrong. I put in #88 to look at this |
@visch this worked for me on the HEAD of config:
file_type: parquet
file_regex: ^.*racing\.parquet$
file_path: tests/data
parquet_type_coercion_strategy: envelope
protocol: file |
@edgarrmondragon the version updates fixed us then, we're good to close then I think? @mjsqu are you good to go now? |
I think so. Let's wait for @mjsqu to confirm. |
Good to close, I can't reproduce this on my personal setup (py3.11, Debian Linux) - we've had a lot of this issue with numpy on my work environments, at various levels and we have pinned numpy |
Things should begin to stabilize as the ecosystem catches up 🤞. |
Patches:
#84