-
Notifications
You must be signed in to change notification settings - Fork 388
Comparing changes
Open a pull request
base repository: bazel-contrib/bazel-gazelle
base: v0.36.0
head repository: bazel-contrib/bazel-gazelle
compare: v0.37.0
Commits on Apr 9, 2024
-
Apply map_kind to args as well as rule kinds (#1722)
* Apply map_kind to args as well as rule kinds #1310 added support for adding args from Gazelle, so you can express things like: ``` maybe( java_test, ... ) ``` But `map_kind` doesn't currently get applied to these args. This PR adds that application. * Panic -> Error * Sort imports in testdata
Configuration menu - View commit details
-
Copy full SHA for 1e0d875 - Browse repository at this point
Copy the full SHA 1e0d875View commit details
Commits on Apr 11, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 65b433f - Browse repository at this point
Copy the full SHA 65b433fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 26bb2ac - Browse repository at this point
Copy the full SHA 26bb2acView commit details
Commits on Apr 12, 2024
-
[cmd/fetch_repo] make cache corruption failures more clear (#1782)
This failure was confusing to our users. We should make more clear error messages in cases when a `GOMODCACHE` might be corrupt. Resolves #1774 Example failure: ``` ERROR: /home/user/go-code/WORKSPACE:69:26: fetching go_repository rule //external:com_github_bazelbuild_remote_apis: Traceback (most recent call last): File "/home/user/.cache/bazel/_bazel_tfrench/b97476d719d716accead0f2d5b93104f/external/bazel_gazelle/internal/go_repository.bzl", line 263, column 17, in _go_repository_impl fail("failed to fetch %s: %s" % (ctx.name, result.stderr)) Error in fail: failed to fetch com_github_bazelbuild_remote_apis: fetch_repo: resulting module with sum h1:xhO5v3Ac039HesaPqoVUwOy4WhRRJbmo9om245kp+AY=; expected sum h1:xhO5v3Ac039HesaPqoVUwOy4WhRRJbmo9om245kp+AY=, Please try clearing your module cache directory "/home/user/go-code/pkg/mod" ERROR: Error computing the main repository mapping: no such package '@@com_github_bazelbuild_remote_apis//': failed to fetch com_github_bazelbuild_remote_apis: fetch_repo: resulting module with sum h1:xhO5v3Ac039HesaPqoVUwOy4WhRRJbmo9om245kp+AY=; expected sum h1:xhO5v3Ac039HesaPqoVUwOy4WhRRJbmo9om245kp+AY=, Please try clearing your module cache directory "/home/user/go-code/pkg/mod" INFO: Build Event Protocol files produced successfully. Computing main repo mapping: WARNING:Bazel failed with exit code 1 ```
Configuration menu - View commit details
-
Copy full SHA for cc40a33 - Browse repository at this point
Copy the full SHA cc40a33View commit details
Commits on Apr 13, 2024
-
Nit: pass -modcacherw in exec.Command. (#1784)
In previous change it was passed conditionally so it was separate, now it's always added.
Configuration menu - View commit details
-
Copy full SHA for 942129d - Browse repository at this point
Copy the full SHA 942129dView commit details
Commits on Apr 16, 2024
-
Mention JS extension in Aspect CLI (#1646)
* Update README.rst * Update README.rst
Configuration menu - View commit details
-
Copy full SHA for 42b7781 - Browse repository at this point
Copy the full SHA 42b7781View commit details
Commits on Apr 18, 2024
-
[Feature] bzlmod & go.work (#1731)
* adds go_deps.from_file(go_work = "//:go.work") * adds ability to op-out of version conflict failures go_deps.from_file(go_work = "//:go.work, fail_on_version_conflict = False) * parses go.work files to discover used go modules and replace statements * generates repos for all deps specified in go.mod's referenced by the //:go.work * handle replace statements (both at the go.work and the go.mod level) * Errors with actionable error message if duplicate dependencies with differing versions arise (Question: can we do better?) * expand BCR test coverage to include both go.work and go.mod scenarios Caveats: * allows for dependency bleed between different go modules in the workspace - this is sorta by design for this stepping stone, but is ideal * doesn't support replace statements in go.work yet (but that shouldn't be to hard to add in a follow up)
Configuration menu - View commit details
-
Copy full SHA for 908ba74 - Browse repository at this point
Copy the full SHA 908ba74View commit details
Commits on Apr 25, 2024
-
Add GIT_CONFIG_* env vars to go_repository allow-list (#1791)
* Add GIT_CONFIG_* env vars to go_repository allow-list * Add '# keep sorted' comment
Configuration menu - View commit details
-
Copy full SHA for a0f2bb6 - Browse repository at this point
Copy the full SHA a0f2bb6View commit details -
Configuration menu - View commit details
-
Copy full SHA for c26571e - Browse repository at this point
Copy the full SHA c26571eView commit details
Commits on May 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 918a4c4 - Browse repository at this point
Copy the full SHA 918a4c4View commit details
Commits on May 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9e8ba4f - Browse repository at this point
Copy the full SHA 9e8ba4fView commit details
Commits on May 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 7c84c33 - Browse repository at this point
Copy the full SHA 7c84c33View commit details
Commits on May 8, 2024
-
Normalise newlines on Windows (#1798)
Otherwise assorted things go wrong when running tests using this infrastructure on Windows where \r\n line endings confuse things.
Configuration menu - View commit details
-
Copy full SHA for ba2ce36 - Browse repository at this point
Copy the full SHA ba2ce36View commit details
Commits on May 11, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 8643a9d - Browse repository at this point
Copy the full SHA 8643a9dView commit details
Commits on May 12, 2024
-
allow go_visibility directive to change command package's visibility (#…
…1794) Co-authored-by: Zhongpeng Lin <zplin@uber.com>
Configuration menu - View commit details
-
Copy full SHA for 1541133 - Browse repository at this point
Copy the full SHA 1541133View commit details
Commits on May 16, 2024
-
Ensure the Gazelle binary is built for the right platform (#1803)
Right now we pick Gazelle for the "exec" platform. This isn't correct, because we are not running Gazelle as part of a build action. Instead, we are emitting a shell script that *invokes* Gazelle. That's why we need to make sure it's built for the target platform. This addresses an issue where Bazel ends up invoking a copy of Gazelle for Linux on my Mac, if I invoke bazel with --extra_execution_platforms=//my_linux_platform,//my_mac_platform.
Configuration menu - View commit details
-
Copy full SHA for f93e45f - Browse repository at this point
Copy the full SHA f93e45fView commit details
Commits on May 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 47e9c2a - Browse repository at this point
Copy the full SHA 47e9c2aView commit details
Commits on May 20, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 61b277b - Browse repository at this point
Copy the full SHA 61b277bView commit details -
Configuration menu - View commit details
-
Copy full SHA for f43d5d0 - Browse repository at this point
Copy the full SHA f43d5d0View commit details -
Make
# gazelle:proto file
work without needing to set different `op……tion go_package` in .proto files (#1765) Co-authored-by: Shahms King <shahms@google.com> Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im> Co-authored-by: Zhongpeng Lin <zplin@uber.com>
Configuration menu - View commit details
-
Copy full SHA for 6a27127 - Browse repository at this point
Copy the full SHA 6a27127View commit details
Commits on May 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 75eade4 - Browse repository at this point
Copy the full SHA 75eade4View commit details
Commits on May 24, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4d0129d - Browse repository at this point
Copy the full SHA 4d0129dView commit details
There are no files selected for viewing