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

go_download_sdk: work around Bazel .tar.gz extraction bug #2836

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

jayconrod
Copy link
Contributor

@jayconrod jayconrod commented Mar 5, 2021

Use 'tar' installed on the system to extract .tar.gz archives instead
of Bazel's download_and_extract. Go has at least one test with an
invalid unicode file name, and on some configurations (macOS with Docker
and some particular file system binding?), this causes an error.

Fixes #2771

@jayconrod jayconrod requested a review from a team March 5, 2021 18:58
@google-cla google-cla bot added the cla: yes label Mar 5, 2021
Use 'tar' installed on the system to extract .tar.gz archives instead
of Bazel's download_and_extract. Go has at least one test with an
invalid unicode file name, and on some configurations (macOS + Docker
+ some particular file system binding?), this causes an error.

Fixes bazelbuild#2771
# BUG(#2771): Use a system tool to extract the archive instead of
# Bazel's implementation. With some configurations (macOS + Docker +
# some particular file system binding), Bazel's implementation rejects
# files with invalid unicode names. Go has at least one test case with a
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a bazel bug to track this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not at the moment. It seemed like a pretty intricate configuration, so I didn't try to reproduce it. I'd rather not report it upstream though without detailed instructions, since it's very unlikely to get fixed.

(Sorry I realize this sounds lazy; it's a consequence of not being able to spend adequate time on this).

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the Bazel bug is bazelbuild/bazel#12986

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot successfully extract go_sdk because of unicode filename
3 participants