Skip to content
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] Work around pyarrow>=13 issue on MacOS, release-1.12 branch #2739

Closed
wants to merge 1 commit into from

Conversation

johnkerl
Copy link
Member

@johnkerl johnkerl commented Jun 14, 2024

Issue and/or context: Apply #2734 to release-1.12 for #2692, hoping to isolate the segfault from #2734.

Copy link

codecov bot commented Jun 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.03%. Comparing base (f8a2c9d) to head (ced152f).

Additional details and impacted files
@@              Coverage Diff              @@
##           release-1.12    #2739   +/-   ##
=============================================
  Coverage         90.03%   90.03%           
=============================================
  Files                37       37           
  Lines              4016     4016           
=============================================
  Hits               3616     3616           
  Misses              400      400           
Flag Coverage Δ
python 90.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
python_api 90.03% <ø> (ø)
libtiledbsoma ∅ <ø> (∅)

@johnkerl johnkerl changed the title [python] Work around pyarrow>=13 issue on MacOS, 1.12 branch [python] Work around pyarrow>=13 issue on MacOS, release-1.12 branch Jun 14, 2024
@johnkerl
Copy link
Member Author

johnkerl commented Jun 14, 2024

Segfaults like main on #2734 ✅ . This was just an experiment.

@johnkerl johnkerl closed this Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant