You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using rust-cache in a repository with a large number of Cargo.toml/Cargo.lock files due to including cargo and the rust book as submodules (see e.g. this subdirectory):
Post job cleanup.
Error: An error occurred trying to start process '/home/runner/runners/2.311.0/externals/node16/bin/node' with working directory '/home/runner/work/mdbook-pandoc/mdbook-pandoc'. Argument list too long
Possible fixes
Only consider lockfiles for workspace members instead of globbing for all lockfiles within a workspace. This would require parsing the workspace manifests to determine member crates
Keep globbing for all lockfiles but pass them to the cleanup script in a way that doesn't result in the argument list too long error
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. We already parse some of the toml files. So might as well also do that for the workspace definition.
I don’t have too much time to dedicate to maintenance right now though.
We already parse some of the toml files. So might as well also do that for the workspace definition.
Turns out there was already logic for calling out to cargo metadata, so all that was required was adding the --no-deps flag to determine workspace members. Opened #180
Problem
I'm using
rust-cache
in a repository with a large number ofCargo.toml
/Cargo.lock
files due to including cargo and the rust book as submodules (see e.g. this subdirectory):Cargo.toml and Cargo.lock files
These lockfiles aren't relevant to the compilation/caching of my project, since I only build the mdbook contained in each repository.
The number of lockfiles breaks the post-run cleanup step (it works fine without submodules cloned):
Possible fixes
The text was updated successfully, but these errors were encountered: