-
Notifications
You must be signed in to change notification settings - Fork 34
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
Failure to parse manifest file #39
Comments
More specifically, my manifest is: [package]
name = "test-instruments-parse-issue"
version = "0.1.0"
authors = ["Colin Rofls <[email protected]>"]
edition = "2018"
cargo-features = ['named-profiles']
[workspace]
members = [
"inner",
] and my package structure is,
I would like to handle workspaces better, but I need more information in this particular case. |
Sorry for taking so long to get back to you. I reinstalled everything with a newer toolchain, and recompiled cargo-instruments and it worked this time - so I assume a newer Cargo dependency or similar fixed it? In general, for better support for workspaces, allowing the user to be in the root and run |
I agree that would be a nice improvement. |
Greetings! Could you please give some additional info about how you solved this? I'm facing the same problem now. |
Here is my demonstration.
The manifest is like: [package]
name = "cargo-instruments-workspace-issue"
version = "0.1.0"
edition = "2021"
# cargo-features = ['named-profiles']
[workspace]
members = ["foo", "bar"] Only comment out It could also applies to manifest with only [workspace]
members = ["foo", "bar"] |
Given:
I get the error:
It would be great if this tool could properly parse such manifest files.
The text was updated successfully, but these errors were encountered: