-
Notifications
You must be signed in to change notification settings - Fork 122
Fix runfiles access via file resolver and static fs
#10663
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
Conversation
75548fb to
9a8b7ca
Compare
|
This is a major pare-down of what ended up basically being a re-write of fileresolver that I did while trying to investigate/understand this problem, and it seems to be failing the integration tests that motivated a lot of the re-write, so I may have to do a more complicated fix, in which case I'll probably have to effectively close this PR and open a much larger one. |
|
We got it working, no re-write of fileresolver required, thank goodness. |
Co-authored-by: Fabian Meumertzheim <[email protected]>
This reverts commit c6a777d.
Reverts #10663 This makes the dev push fail because of ``` Error getting static FS from relPath: "../+_repo_rules+com_github_buildbuddy_io_buildbuddy/static/": sub +_repo_rules+com_github_buildbuddy_io_buildbuddy/../+_repo_rules+com_github_buildbuddy_io_buildbuddy/static/: invalid argument ```
|
FYI this wasn't working in dev because of this error: I reverted it for now to unblock the dev push, but feel free to roll forward with a fix! |
Since upgrading to
MODULE.bazel, the bazel runfiles have an additional intervening subdirectory_mainbetween the runfiles root and the paths we use.This also fixes the related test, which was previously embedding the file we were trying to access via the runfiles.