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
A minor release of clap happened yesterday, which changes the behavior or argument matching and leads plugin writers to hit an error when they run:
ignition@ignition-apollo test % cargo r -- --supergraph ./local.graphql
Finished dev [unoptimized + debuginfo] target(s) in 0.42s
Running `target/debug/router --supergraph ./local.graphql`
thread 'main' panicked at 'Must use `_os` lookups with `Arg::allow_invalid_utf8` at `supergraph-path`', /Users/ignition/.cargo/git/checkouts/router-18de2f110854a520/dfbfea0/apollo-router/src/executable.rs:314:49
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
We are working around this by pinning the dependency to clap = "3.1.18" but we need to find the root cause and address it.
The text was updated successfully, but these errors were encountered:
Workaround against #1231
A minor release of Clap occured yesterday; which introduced a breaking change.
This might lead cargo scaffold users to hit a panic a runtime when the router tries to parse env variables and arguments.
This patch Pins the clap dependency to the version that was available before the release, until the root cause is found and fixed.
Workaround against #1231
A minor release of Clap occured yesterday; which introduced a breaking change.
This might lead cargo scaffold users to hit a panic a runtime when the router tries to parse env variables and arguments.
This patch Pins the clap dependency to the version that was available before the release, until the root cause is found and fixed.
A minor release of clap happened yesterday, which changes the behavior or argument matching and leads plugin writers to hit an error when they run:
We are working around this by pinning the dependency to
clap = "3.1.18"
but we need to find the root cause and address it.The text was updated successfully, but these errors were encountered: