-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Panic on cargo add with --offline flag #10814
Comments
Maybe the [package]
name = "cloudmqtt"
version = "0.1.0"
edition = "2021"
authors = ["Marcel Müller <neikos@neikos.email>"]
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[workspace]
members = ["mqtt-format"]
[[bin]]
name = "cloudmqtt-client"
required-features = ["bin"]
[features]
bin = ["clap", "tokio/rt-multi-thread", "tokio/macros"]
[dependencies]
bytes = "1.1.0"
clap = { version = "3.2.6", optional = true, features = ["derive"] }
dashmap = "5.3.4"
futures = "0.3.21"
mqtt-format = { version = "0.1.0", path = "mqtt-format" }
nom = { version = "7.1.1" }
nom-supreme = "0.8.0"
thiserror = "1.0.31"
tokio = { version = "1.19.2", default-features = false, features = [
"net",
"time",
"sync",
"macros"
] }
tokio-util = { version = "0.7.3", features = [
"futures-io",
"io",
"io-util",
"compat",
] }
[dev-dependencies]
static_assertions = "1.1.0" |
Thanks for reporting this! A fix is posted but in the mean time, |
bors
added a commit
that referenced
this issue
Jul 3, 2022
fix(add): Don't panic with `--offline` For some reason, I defined my own `--offline` flag and it didn't get updated with the global `--offline` flag, so it started failing. The new test previously paniced and now it doesn't. Fixes #10814
Great! Thanks for the quick fix |
Hezuikn
pushed a commit
to Hezuikn/cargo
that referenced
this issue
Sep 22, 2022
For some reason, I defined my own `--offline` flag and it didn't get updated with the global `--offline` flag, so it started failing. Fixes rust-lang#10814
Hezuikn
pushed a commit
to Hezuikn/cargo
that referenced
this issue
Sep 22, 2022
For some reason, I defined my own `--offline` flag and it didn't get updated with the global `--offline` flag, so it started failing. Fixes rust-lang#10814
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Running
cargo add nom-supreme --offline
causes cargo to panic with:Steps
Possible Solution(s)
Not running with
--offline
doesn't make the error occur.Notes
Running
cargo clean
doesn't fix the issueVersion
The text was updated successfully, but these errors were encountered: