-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
[thrift] Update thrift 0.20.0 git reference #39787
[thrift] Update thrift 0.20.0 git reference #39787
Conversation
I think we should not use a branch as reference at all because per definition it is not stable... Use a git tag or commit sha. |
a83c99d
to
850ada0
Compare
@@ -12,7 +12,7 @@ vcpkg_find_acquire_program(BISON) | |||
vcpkg_from_github( | |||
OUT_SOURCE_PATH SOURCE_PATH | |||
REPO apache/thrift | |||
REF "${VERSION}" | |||
REF "v${VERSION}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the Thrift repository is using a convention where the latest releases are all tagged vX.Y.Z
, so I think this minor change should work.
I suppose this could change in the future, but I think this is probably the cleanest solution for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thrift repository is using a convention where the latest releases are all tagged vX.Y.Z
I can confirm that. I would also recommend to reference the release tag as it never changes after the release. Sorry for any confusion, was not aware that a single commit may cause such a tail of problems.
@microsoft-github-policy-service agree |
Makes sense to me. I updated the PR to use the corresponding tag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is holding our Apache Arrow release, could this be merged?
Thanks @JavierMatosD ! |
…3208) ### Rationale for this change Currently our java-jars and some wheels jobs are failing due to downloading a wrong version of Apache Thrift based on the 0.20.0 branch instead of the tag. That branch contains a new commit that makes the sha validation to fail. ### What changes are included in this PR? Apply the Thrift patch that was applied on vcpkg here: microsoft/vcpkg#39787 ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #43204 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…3208) ### Rationale for this change Currently our java-jars and some wheels jobs are failing due to downloading a wrong version of Apache Thrift based on the 0.20.0 branch instead of the tag. That branch contains a new commit that makes the sha validation to fail. ### What changes are included in this PR? Apply the Thrift patch that was applied on vcpkg here: microsoft/vcpkg#39787 ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #43204 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
This is a candidate fix for the Thrift build failure identified in #39786.
The PR updates the port to reference the
v0.20.0
tag instead of the0.20.0
branch.Fixes #39786.
./vcpkg x-add-version --all
and committing the result.