Fabian Meumertzheim
Fabian Meumertzheim
> Yes, that change includes the version bump for rules_js that @gregmagolan mentioned 4d ago Based on https://github.com/bazelbuild/bazel/issues/22073, I don't think that this can be worked around reliably on the...
As far as I know @joeleba is actively working on https://github.com/bazelbuild/bazel/issues/22073.
Looks like CI is failing due to missing build files, but the BCR setup looks good.
@wep21 How did you generate the patch? The Bazel implementation of patch can be a bit strict at times. I would recommend using `git diff` to generate the patch, those...
Maybe some targets are missing `-lpthread` linkopts?
@linzhp The current implementation of `go_repository` looks like it would cause a restart when applying patches: It calls `patch(ctx)` in the very end, but that ends up calling `ctx.path` on...
This is a problem with our naming scheme, but it rarely arises in practice. Out of the two modules you mention, one is archived and recommends using the other one...
You can use `go.mod`'s `replace` directive to replace the deprecated module with the maintained one anywhere in your dependency graph. `gazelle update-repos` should honor this directive. I don't know whether...
Thanks! Could you fix the failure: ``` ==================== Test output for //docs:check_extend.md: 56c56 < "@rules_python_gazelle_plugin//python", # Use gazelle from rules_python. --- > "@rules_python//gazelle", # Use gazelle from rules_python. FAIL: files...
@linzhp Could you test whether this reduces the runtime of the extension?