Resolve relative symlinks in bootstrap script
Currently, the bootstrap script only accepts absolute symlinks.
Implements a patch to resolve relative symlinks.
Adds an extra, take it if you want it, patch that adds an explicit error when a symlink is dangling.
Summary of Changes
Hello @mattyclarkson, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request enhances the robustness of the bootstrap script by improving its symlink resolution capabilities. It ensures that both absolute and relative symlinks are correctly followed, preventing issues that arose from relative paths. Additionally, it introduces a more informative error handling mechanism for broken or dangling symlinks, making the script more resilient and easier to debug.
Highlights
- Relative Symlink Resolution: The bootstrap script has been updated to correctly resolve relative symbolic links, addressing a previous limitation where it only handled absolute symlinks.
- Dangling Symlink Detection: An explicit check has been added to detect and report dangling symbolic links, providing a clear error message when a symlink points to a non-existent target.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.
Thanks for providing a patch! We are about to cut a release, so maybe we should wait until after the release branch is created.
Could you add some extra explanation as to what made you add this change? How do you manage python?
Could you add some extra explanation as to what made you add this change?
During an action, a tool symlinks to a py_binary target with a relative symlink path. This then results in a Unable to find runfiles error as the relative symlink is not resolved. The tool performs relative symlinks because outside of Bazel this will result in a relocatable set of symlinks.
How do you manage
python?
We let Bazel manage it with @rules_python//python/config_settings:bootstrap_impl=script.
It would be nice to add some integration tests which would make the change more explanatory and avoid us running into the problem later.