Skip to content

Commit

Permalink
chore: minor fixes (#158)
Browse files Browse the repository at this point in the history
* fix cargo warning for resolver

warning: some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest

As a library, this isn't important as end-user application decides the resolver finally. Just remove the warning.

* bump log to 0.4.19

failed to compile on latest nightly due to value-bag

* fix build
  • Loading branch information
xxchan committed Jul 11, 2023
1 parent 0d6a86a commit 11e078a
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,4 @@ members = [
"madsim-rdkafka",
"tonic-example",
]
resolver = "2"
2 changes: 1 addition & 1 deletion madsim-rdkafka/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ futures-channel = "0.3.0"
futures-executor = { version = "0.3.0", optional = true }
futures-util = { version = "0.3.0", default-features = false }
libc = "0.2.0"
log = "0.4.8"
log = "0.4.19"
serde = { version = "1.0.0", features = ["derive"] }
serde_derive = "1.0.0"
serde_json = "1.0.0"
Expand Down
2 changes: 1 addition & 1 deletion madsim-tonic/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,4 @@ chrono = { version = "0.4", default-features = false, features = ["clock"] }
futures-util = "0.3"
madsim = { version = "0.2.20", path = "../madsim" }
tracing = "0.1"
tonic = { version = "0.8.3", default-features = false, features = ["codegen"] }
tonic = { version = "0.8.3", default-features = false, features = ["codegen", "transport"] }

0 comments on commit 11e078a

Please sign in to comment.