GH-41735: [CI][Archery] Update archery to be compatible with pygit2 1.15 API change#41739
Merged
kou merged 2 commits intoapache:mainfrom May 20, 2024
Merged
GH-41735: [CI][Archery] Update archery to be compatible with pygit2 1.15 API change#41739kou merged 2 commits intoapache:mainfrom
kou merged 2 commits intoapache:mainfrom
Conversation
…git2 1.15 API change
|
|
Member
Author
|
@github-actions crossbow submit -g python |
|
Member
Author
|
This will fail until it is merged on main. |
|
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 11decbc. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them. |
vibhatha
pushed a commit
to vibhatha/arrow
that referenced
this pull request
May 25, 2024
…git2 1.15 API change (apache#41739) ### Rationale for this change pygit2 updated how they expose some of the `GIT_OBJ` variables to use `GIT_OBJECT` prefix here: libgit2/pygit2@8b3861b ### What changes are included in this PR? Update code to make it compatible with both possible APIs. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41735 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
stevelorddremio
pushed a commit
to stevelorddremio/arrow
that referenced
this pull request
Jun 17, 2024
…git2 1.15 API change (apache#41739) ### Rationale for this change pygit2 updated how they expose some of the `GIT_OBJ` variables to use `GIT_OBJECT` prefix here: libgit2/pygit2@8b3861b ### What changes are included in this PR? Update code to make it compatible with both possible APIs. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41735 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
lriggs
pushed a commit
to lriggs/arrow
that referenced
this pull request
Jun 18, 2024
…git2 1.15 API change (apache#41739) ### Rationale for this change pygit2 updated how they expose some of the `GIT_OBJ` variables to use `GIT_OBJECT` prefix here: libgit2/pygit2@8b3861b ### What changes are included in this PR? Update code to make it compatible with both possible APIs. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41735 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
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
2 participants
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.
Rationale for this change
pygit2 updated how they expose some of the
GIT_OBJvariables to useGIT_OBJECTprefix here: libgit2/pygit2@8b3861bWhat changes are included in this PR?
Update code to make it compatible with both possible APIs.
Are these changes tested?
Via archery
Are there any user-facing changes?
No