Open DennohKim opened 3 months ago
Getting this too
me either
modify Cargo.toml
can fix this issue, but more errors are coming...ðŸ˜
[dependencies.diesel]
default-features = false
features = ["postgres", "r2d2", "chrono"]
version = "=2.1"
continue modify Cargo.toml, lock version of "dsync" to "0.0.16", then "cargo fullstack" is OK now.
Now runtime panik:
Starting frontend server @ http://localhost:21012/
thread 'tokio-runtime-worker' panicked at /Users/zhenpingzhao/.cargo/registry/src/index.crates.io-6f17d22bba15001f/create-rust-app-11.0.0/src/dev/frontend_dev_server.rs:29:10:
called Result::unwrap()
on an Err
value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
stack backtrace:
Need more config file?
I am also facing the issue. I also tried with dsync = "0.0.16" but did not work.
.cargo/registry/src/index.crates.io-6f17d22bba15001f/diesel_logger-0.3.0/src/lib.rs:80:1
|
80 | / implinstrumentation
, set_instrumentation
in implementation
Seems to be an issue with https://github.com/shssoichiro/diesel-logger, I'll see if I can dig into this a bit more
Thanks to the merged commit above, diesel_logger
seems to have been fixed. Unfortunately a new release has not been made yet so modifying Cargo.toml
to use the shssoichiro/diesel-logger
master
branch (or the commit branch) is necessary
edit: v0.4.0 released
[patch.crates-io]
diesel_logger = "0.4.0"
Unfortunately there seems to be a separate issue with dsync v0.1.0
delivering some breaking changes to the initial file in .cargo/bin/dsync.rs
😩. I don't believe that is linked to this issue but figured I would mention it here before creating a separate issue as dsync
was brought up earlier.
Since this error has been patched upstream we can upgrade diesel-logger to 0.4.0
and it should work as expected!
How can i resolve this error when boostrapping create-rust-app?