Skip to content

Some vendored crates get absolute paths in MODULE.bazel.lock #3754

@rejuvenile

Description

@rejuvenile

In my Cargo.toml, I have:

[workspace.dependencies]
...
flatbuffers-tonic = { path = "third_party/flatbuffers-tonic/flatbuffers-tonic" }
flatbuffers-tonic-build = { path = "third_party/flatbuffers-tonic/flatbuffers-tonic-build" }
flatbuffers-util = { path = "third_party/flatbuffers-tonic/flatbuffers-util" }
...

When these crates find their way into MODULE.bazel.lock, they are prefixed with absolute paths. This brakes cross-machine and cross-platform builds of these crates.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions