Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Cannot run website with serve-docs.sh on macOS #28

Open
steren opened this issue Jun 21, 2017 · 4 comments
Open

Cannot run website with serve-docs.sh on macOS #28

steren opened this issue Jun 21, 2017 · 4 comments
Assignees
Labels

Comments

@steren
Copy link
Contributor

steren commented Jun 21, 2017

I get this error:

steren:bazel-website steren$ ./scripts/serve-docs.sh
expr: syntax error
INFO: Found 1 target...
ERROR: /Users/steren/work/bazel-website/BUILD:84:1: Generating site tarball. failed: Process exited with status 1 [sandboxed].
Cannot create redirect file docs/skylark/lib/provider.html. File exists.
Use --strategy=SiteTar=standalone to disable sandboxing for the failing actions.
Target //:jekyll-tree.tar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3.448s, Critical Path: 1.76s
@davidzchen
Copy link
Member

+cc @laurentlb, @fweikert

Are you running on macOS? The problem is that when we generate the Skylark Library, there is both a provider.html and a Provider.html. Because HFS+ (and presumably the upcoming APFS) is by default case-insensitive, we get this error.

The script runs without any issues on Linux. IMO the ideal fix for this is to either improve the directory structure of the Skylark Library to separate modules and types or have a single page for both the provider module and the Provider type.

@steren
Copy link
Contributor Author

steren commented Jun 22, 2017

Yes I am on macOS.

It is a bad practice to have 2 web page URLs that only differ by a letters being upper case.

@davidzchen
Copy link
Member

Agreed. Let's open a bug on bazelbuild/bazel to fix this in the Skylark Library.

@steren steren changed the title Cannot run website with serve-docs.sh Cannot run website with serve-docs.sh on macOS Jun 22, 2017
@davidzchen davidzchen added the bug label Jun 23, 2017
@jin
Copy link
Member

jin commented May 12, 2020

This is unfortunately still an issue. For local development, I'd just comment out either page from redirects.bzl.

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

No branches or pull requests

3 participants