-
Notifications
You must be signed in to change notification settings - Fork 216
fix(l1,l2): stop removedb from faking success on the wrong datadir #7080
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
NikhilSharmaWe
wants to merge
2
commits into
lambdaclass:main
Choose a base branch
from
NikhilSharmaWe:fix/removedb-wrong-network-footgun
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tempfilelands in the rootCargo.lock, buttooling/is a second workspace with its own lockfile and this PR doesn't touch it. Itsethrexentry still carries the pre-PR dep set, soCheck Cargo.lockshould fail on:(
Makefile:269.) Cargo records dev-dependencies in the lockfile'sdependenciesarray alongside normal ones, so a dev-only dep still rotates both lockfiles - I checked, andtempfileis present in the rootethrexblock and absent from thetooling/one.Running
cargo metadata --manifest-path tooling/Cargo.tomlwithout--lockedregenerates it. #7067 hit exactly this and it cost a round-trip, so flagging it before CI finishes rather than after.The
.workspace = trueform itself is right, and the root lockfile entry is correct.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looked into it and I don't think we need to update
tooling/Cargo.lockfor this change.tempfileis only added under[dev-dependencies]onethrex. In the tooling workspace,ethrexis used as a path dependency, not as a workspace member, so Cargo does not include its[dev-dependencies]in that lockfile.I verified locally that
cargo metadata --locked --manifest-path tooling/Cargo.tomlpasses, and running it without--lockeddoes not change the lockfile. #7067 needed the tooling lock update because it added a normal dependency onethrex-dev, which is different from this case.Happy to take another look if I missed something.