Description
This is not an issue in our repo, this ticket is for tracking.
It seems there is a problem with the flatbuffers package. I have recreated it in https://github.com/MaciejKaszynski/fbs_problem.
google/flatbuffers#9064
Just pulling the flatbuffers dependency causes
module extension @@grpc+//bazel:grpc_deps.bzl%grpc_repo_deps_ext does not generate repository "com_envoyproxy_protoc_gen_validate", yet it is imported as "com_envoyproxy_protoc_gen_validate" in the usage at https://bcr.bazel.build/modules/grpc-java/1.66.0/MODULE.bazel:68:35
Workaround
Running bazel mod deps --lockfile_mode=update creates the error but it still generates a correct lock file.
So just create the lock and commit normally.
Analysis results
No response
Solution
Need to wait for opensource Flatbuffers to fix.
Error Occurrence Rate
When updating lock file.
How to reproduce
bazel mod deps --lockfile_mode=update
Supporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category
Description
This is not an issue in our repo, this ticket is for tracking.
It seems there is a problem with the flatbuffers package. I have recreated it in https://github.com/MaciejKaszynski/fbs_problem.
google/flatbuffers#9064
Just pulling the flatbuffers dependency causes
Workaround
Running
bazel mod deps --lockfile_mode=updatecreates the error but it still generates a correct lock file.So just create the lock and commit normally.
Analysis results
No response
Solution
Need to wait for opensource Flatbuffers to fix.
Error Occurrence Rate
When updating lock file.
How to reproduce
bazel mod deps --lockfile_mode=updateSupporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category