[python] Work around pyarrow>=13 issue on MacOS, release-1.11 branch#2738
Closed
johnkerl wants to merge 1 commit intorelease-1.11from
Closed
[python] Work around pyarrow>=13 issue on MacOS, release-1.11 branch#2738johnkerl wants to merge 1 commit intorelease-1.11from
release-1.11 branch#2738johnkerl wants to merge 1 commit intorelease-1.11from
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-1.11 #2738 +/- ##
=============================================
Coverage 90.19% 90.19%
=============================================
Files 37 37
Lines 4019 4019
=============================================
Hits 3625 3625
Misses 394 394
Flags with carried forward coverage won't be shown. Click here to find out more.
|
release-1.11 branch
Contributor
Author
|
Segfaults like |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue and/or context: Apply #2734 to
release-1.11for #2692, hoping to isolate the segfault from #2734.