[INFO] fetching crate elif-http-derive 0.2.11...
[INFO] testing elif-http-derive-0.2.11 against try#b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b for pr-145330-1
[INFO] extracting crate elif-http-derive 0.2.11 into /workspace/builds/worker-4-tc2/source
[INFO] started tweaking crates.io crate elif-http-derive 0.2.11
[INFO] removed 0 missing examples
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate elif-http-derive 0.2.11
[INFO] tweaked toml for crates.io crate elif-http-derive 0.2.11 written to /workspace/builds/worker-4-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate elif-http-derive 0.2.11 on toolchain b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate elif-http-derive 0.2.11 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 98123966b66549fc54f1b2cac9ff3ba8778dac5caf7028d0f74cf8c210d47216
[INFO] running `Command { std: "docker" "start" "-a" "98123966b66549fc54f1b2cac9ff3ba8778dac5caf7028d0f74cf8c210d47216", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "98123966b66549fc54f1b2cac9ff3ba8778dac5caf7028d0f74cf8c210d47216", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "98123966b66549fc54f1b2cac9ff3ba8778dac5caf7028d0f74cf8c210d47216", kill_on_drop: false }`
[INFO] [stdout] 98123966b66549fc54f1b2cac9ff3ba8778dac5caf7028d0f74cf8c210d47216
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 718f1e6c47391ba09baa5cc02a2d24aec6a15bbfffbe158211529861c1d0dda8
[INFO] running `Command { std: "docker" "start" "-a" "718f1e6c47391ba09baa5cc02a2d24aec6a15bbfffbe158211529861c1d0dda8", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v2.0.106
[INFO] [stderr]    Compiling async-trait v0.1.89
[INFO] [stderr]    Compiling elif-http-derive v0.2.11 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 7.94s
[INFO] running `Command { std: "docker" "inspect" "718f1e6c47391ba09baa5cc02a2d24aec6a15bbfffbe158211529861c1d0dda8", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "718f1e6c47391ba09baa5cc02a2d24aec6a15bbfffbe158211529861c1d0dda8", kill_on_drop: false }`
[INFO] [stdout] 718f1e6c47391ba09baa5cc02a2d24aec6a15bbfffbe158211529861c1d0dda8
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 2d236a139434d20562f4bf5c7c65692ea0a2dc580af488b97ee6b079f2480559
[INFO] running `Command { std: "docker" "start" "-a" "2d236a139434d20562f4bf5c7c65692ea0a2dc580af488b97ee6b079f2480559", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.101
[INFO] [stderr]    Compiling unicode-ident v1.0.18
[INFO] [stderr]    Compiling winnow v0.7.12
[INFO] [stderr]    Compiling target-triple v0.1.4
[INFO] [stderr]    Compiling toml_writer v1.0.2
[INFO] [stderr]    Compiling glob v0.3.3
[INFO] [stderr]    Compiling termcolor v1.4.1
[INFO] [stderr]    Compiling quote v1.0.40
[INFO] [stderr]    Compiling syn v2.0.106
[INFO] [stderr]    Compiling toml_parser v1.0.2
[INFO] [stderr]    Compiling serde_derive v1.0.219
[INFO] [stderr]    Compiling async-trait v0.1.89
[INFO] [stderr]    Compiling ctor v0.2.9
[INFO] [stderr]    Compiling elif-http-derive v0.2.11 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling serde v1.0.219
[INFO] [stderr]    Compiling toml_datetime v0.7.0
[INFO] [stderr]    Compiling serde_spanned v1.0.0
[INFO] [stderr]    Compiling serde_json v1.0.143
[INFO] [stderr]    Compiling toml v0.9.5
[INFO] [stderr]    Compiling trybuild v1.0.110
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]  --> tests/parameter_metadata_test.rs:1:5
[INFO] [stdout]   |
[INFO] [stdout] 1 | use elif_http::controller::{ControllerRoute, ElifController, RouteParam};
[INFO] [stdout]   |     ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]  --> tests/parameter_metadata_test.rs:2:5
[INFO] [stdout]   |
[INFO] [stdout] 2 | use elif_http::routing::{params::ParamType, HttpMethod};
[INFO] [stdout]   |     ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `elif_http`
[INFO] [stdout]  --> tests/parameter_metadata_test.rs:3:5
[INFO] [stdout]   |
[INFO] [stdout] 3 | use elif_http::{ElifRequest, ElifResponse, HttpResult};
[INFO] [stdout]   |     ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/parameter_metadata_test.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | #[controller("/api/test")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter '_req' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{_req}' and annotate with #[param(_req: type)], annotate with #[body(_req: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> tests/controller_impl_test.rs:21:30
[INFO] [stdout]    |
[INFO] [stdout] 21 |     pub async fn list(&self, _req: String) -> Result<String, String> {
[INFO] [stdout]    |                              ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/test_optional_with_attributes.rs:59:9
[INFO] [stdout]    |
[INFO] [stdout] 59 |     use elif_core::container::{IocContainer, ServiceBinder};
[INFO] [stdout]    |         ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter '_req' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{_req}' and annotate with #[param(_req: type)], annotate with #[body(_req: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> tests/controller_impl_test.rs:26:30
[INFO] [stdout]    |
[INFO] [stdout] 26 |     pub async fn show(&self, _req: String) -> Result<String, String> {
[INFO] [stdout]    |                              ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter '_req' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{_req}' and annotate with #[param(_req: type)], annotate with #[body(_req: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> tests/controller_impl_test.rs:32:32
[INFO] [stdout]    |
[INFO] [stdout] 32 |     pub async fn create(&self, _req: String) -> Result<String, String> {
[INFO] [stdout]    |                                ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter '_req' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{_req}' and annotate with #[param(_req: type)], annotate with #[body(_req: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> tests/controller_impl_test.rs:54:35
[INFO] [stdout]    |
[INFO] [stdout] 54 |     pub async fn dashboard(&self, _req: String) -> Result<String, String> {
[INFO] [stdout]    |                                   ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter '_req' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{_req}' and annotate with #[param(_req: type)], annotate with #[body(_req: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> tests/controller_impl_test.rs:60:41
[INFO] [stdout]    |
[INFO] [stdout] 60 |     pub async fn update_settings(&self, _req: String) -> Result<String, String> {
[INFO] [stdout]    |                                         ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/controller_impl_test.rs:38:1
[INFO] [stdout]    |
[INFO] [stdout] 38 | #[controller("/api/legacy")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/controller_impl_test.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[controller("/empty")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `elif_http`
[INFO] [stdout]  --> tests/comprehensive_body_test.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use elif_http::{ElifRequest, ElifResponse, HttpResult, HttpError};
[INFO] [stdout]   |     ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/body_injection_core_test.rs:70:5
[INFO] [stdout]    |
[INFO] [stdout] 70 |     #[post("")]
[INFO] [stdout]    |     ^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/test_optional_with_attributes.rs:32:6
[INFO] [stdout]    |
[INFO] [stdout] 32 | impl elif_core::foundation::traits::FrameworkComponent for MockCacheService {}
[INFO] [stdout]    |      ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/test_optional_with_attributes.rs:33:6
[INFO] [stdout]    |
[INFO] [stdout] 33 | impl elif_core::foundation::traits::Service for MockCacheService {}
[INFO] [stdout]    |      ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/test_optional_with_attributes.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout] 42 | / #[inject(
[INFO] [stdout] 43 | |     cache: Option<MockCacheService> = "redis_cache"
[INFO] [stdout] 44 | | )]
[INFO] [stdout]    | |__^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the attribute macro `inject` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module` is defined multiple times
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:58:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | / #[module(
[INFO] [stdout] 47 | |     providers: [
[INFO] [stdout] 48 | |         TestUserService,
[INFO] [stdout] 49 | |         TestSqlRepository
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout] 54 | | )]
[INFO] [stdout]    | |__- previous definition of the value `__register_module` here
[INFO] [stdout] ...
[INFO] [stdout] 58 | / #[module(
[INFO] [stdout] 59 | |     providers: [TestSqlRepository],
[INFO] [stdout] 60 | |     controllers: [],
[INFO] [stdout] 61 | |     imports: [],
[INFO] [stdout] 62 | |     exports: [TestSqlRepository]
[INFO] [stdout] 63 | | )]
[INFO] [stdout]    | |__^ `__register_module` redefined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `__register_module` must be defined only once in the value namespace of this module
[INFO] [stdout]    = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module___rust_ctor___ctor` is defined multiple times
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:58:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | / #[module(
[INFO] [stdout] 47 | |     providers: [
[INFO] [stdout] 48 | |         TestUserService,
[INFO] [stdout] 49 | |         TestSqlRepository
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout] 54 | | )]
[INFO] [stdout]    | |__- previous definition of the value `__register_module___rust_ctor___ctor` here
[INFO] [stdout] ...
[INFO] [stdout] 58 | / #[module(
[INFO] [stdout] 59 | |     providers: [TestSqlRepository],
[INFO] [stdout] 60 | |     controllers: [],
[INFO] [stdout] 61 | |     imports: [],
[INFO] [stdout] 62 | |     exports: [TestSqlRepository]
[INFO] [stdout] 63 | | )]
[INFO] [stdout]    | |__^ `__register_module___rust_ctor___ctor` redefined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `__register_module___rust_ctor___ctor` must be defined only once in the value namespace of this module
[INFO] [stdout]    = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module` is defined multiple times
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:67:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | / #[module(
[INFO] [stdout] 47 | |     providers: [
[INFO] [stdout] 48 | |         TestUserService,
[INFO] [stdout] 49 | |         TestSqlRepository
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout] 54 | | )]
[INFO] [stdout]    | |__- previous definition of the value `__register_module` here
[INFO] [stdout] ...
[INFO] [stdout] 67 | / #[module(
[INFO] [stdout] 68 | |     providers: [TestUserService],
[INFO] [stdout] 69 | |     controllers: [TestUserController],
[INFO] [stdout] 70 | |     imports: [DatabaseModule],
[INFO] [stdout] 71 | |     exports: [TestUserService]
[INFO] [stdout] 72 | | )]
[INFO] [stdout]    | |__^ `__register_module` redefined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `__register_module` must be defined only once in the value namespace of this module
[INFO] [stdout]    = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module___rust_ctor___ctor` is defined multiple times
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:67:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | / #[module(
[INFO] [stdout] 47 | |     providers: [
[INFO] [stdout] 48 | |         TestUserService,
[INFO] [stdout] 49 | |         TestSqlRepository
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout] 54 | | )]
[INFO] [stdout]    | |__- previous definition of the value `__register_module___rust_ctor___ctor` here
[INFO] [stdout] ...
[INFO] [stdout] 67 | / #[module(
[INFO] [stdout] 68 | |     providers: [TestUserService],
[INFO] [stdout] 69 | |     controllers: [TestUserController],
[INFO] [stdout] 70 | |     imports: [DatabaseModule],
[INFO] [stdout] 71 | |     exports: [TestUserService]
[INFO] [stdout] 72 | | )]
[INFO] [stdout]    | |__^ `__register_module___rust_ctor___ctor` redefined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `__register_module___rust_ctor___ctor` must be defined only once in the value namespace of this module
[INFO] [stdout]    = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module` is defined multiple times
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:335:1
[INFO] [stdout]     |
[INFO] [stdout]  46 | / #[module(
[INFO] [stdout]  47 | |     providers: [
[INFO] [stdout]  48 | |         TestUserService,
[INFO] [stdout]  49 | |         TestSqlRepository
[INFO] [stdout] ...   |
[INFO] [stdout]  53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout]  54 | | )]
[INFO] [stdout]     | |__- previous definition of the value `__register_module` here
[INFO] [stdout] ...
[INFO] [stdout] 335 | / #[module(
[INFO] [stdout] 336 | |     providers: [],
[INFO] [stdout] 337 | |     controllers: [],
[INFO] [stdout] 338 | |     imports: [],
[INFO] [stdout] 339 | |     exports: []
[INFO] [stdout] 340 | | )]
[INFO] [stdout]     | |__^ `__register_module` redefined here
[INFO] [stdout]     |
[INFO] [stdout]     = note: `__register_module` must be defined only once in the value namespace of this module
[INFO] [stdout]     = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0428]: the name `__register_module___rust_ctor___ctor` is defined multiple times
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:335:1
[INFO] [stdout]     |
[INFO] [stdout]  46 | / #[module(
[INFO] [stdout]  47 | |     providers: [
[INFO] [stdout]  48 | |         TestUserService,
[INFO] [stdout]  49 | |         TestSqlRepository
[INFO] [stdout] ...   |
[INFO] [stdout]  53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout]  54 | | )]
[INFO] [stdout]     | |__- previous definition of the value `__register_module___rust_ctor___ctor` here
[INFO] [stdout] ...
[INFO] [stdout] 335 | / #[module(
[INFO] [stdout] 336 | |     providers: [],
[INFO] [stdout] 337 | |     controllers: [],
[INFO] [stdout] 338 | |     imports: [],
[INFO] [stdout] 339 | |     exports: []
[INFO] [stdout] 340 | | )]
[INFO] [stdout]     | |__^ `__register_module___rust_ctor___ctor` redefined here
[INFO] [stdout]     |
[INFO] [stdout]     = note: `__register_module___rust_ctor___ctor` must be defined only once in the value namespace of this module
[INFO] [stdout]     = note: this error originates in the attribute macro `::ctor::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:10:5
[INFO] [stdout]    |
[INFO] [stdout] 10 | use elif_core::modules::{
[INFO] [stdout]    |     ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | / #[module(
[INFO] [stdout] 47 | |     providers: [
[INFO] [stdout] 48 | |         TestUserService,
[INFO] [stdout] 49 | |         TestSqlRepository
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     exports: [TestUserService, TestSqlRepository]
[INFO] [stdout] 54 | | )]
[INFO] [stdout]    | |__^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the attribute macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:58:1
[INFO] [stdout]    |
[INFO] [stdout] 58 | / #[module(
[INFO] [stdout] 59 | |     providers: [TestSqlRepository],
[INFO] [stdout] 60 | |     controllers: [],
[INFO] [stdout] 61 | |     imports: [],
[INFO] [stdout] 62 | |     exports: [TestSqlRepository]
[INFO] [stdout] 63 | | )]
[INFO] [stdout]    | |__^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the attribute macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]   --> tests/epic_3_integration_test.rs:67:1
[INFO] [stdout]    |
[INFO] [stdout] 67 | / #[module(
[INFO] [stdout] 68 | |     providers: [TestUserService],
[INFO] [stdout] 69 | |     controllers: [TestUserController],
[INFO] [stdout] 70 | |     imports: [DatabaseModule],
[INFO] [stdout] 71 | |     exports: [TestUserService]
[INFO] [stdout] 72 | | )]
[INFO] [stdout]    | |__^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the attribute macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:335:1
[INFO] [stdout]     |
[INFO] [stdout] 335 | / #[module(
[INFO] [stdout] 336 | |     providers: [],
[INFO] [stdout] 337 | |     controllers: [],
[INFO] [stdout] 338 | |     imports: [],
[INFO] [stdout] 339 | |     exports: []
[INFO] [stdout] 340 | | )]
[INFO] [stdout]     | |__^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the attribute macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/comprehensive_body_test.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     #[post("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/comprehensive_body_test.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/users/bulk")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/comprehensive_body_test.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 |     #[put("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/comprehensive_body_test.rs:47:5
[INFO] [stdout]    |
[INFO] [stdout] 47 |     #[post("/users/sync")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "parameter_metadata_test") due to 4 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: Unsupported parameter 'data' of type 'String'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{data}' and annotate with #[param(data: type)], annotate with #[body(data: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:44:33
[INFO] [stdout]    |
[INFO] [stdout] 44 |     pub fn update_item(id: u32, data: String) -> String {
[INFO] [stdout]    |                                 ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: Unsupported parameter 'file_data' of type 'Vec < u8 >'. Only path parameters (specified in route), body parameters (annotated with #[body]), and ElifRequest are supported. Hint: Remove this parameter, add it to the route path like '/users/{file_data}' and annotate with #[param(file_data: type)], annotate with #[body(file_data: Type)], or use #[request] to enable automatic request injection.
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:183:35
[INFO] [stdout]     |
[INFO] [stdout] 183 |     pub fn upload_avatar(id: u32, file_data: Vec<u8>) -> String {
[INFO] [stdout]     |                                   ^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `middleware`
[INFO] [stdout]  --> tests/controller_impl_test.rs:9:41
[INFO] [stdout]   |
[INFO] [stdout] 9 | use elif_http_derive::{controller, get, middleware, post};
[INFO] [stdout]   |                                         ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:182:17
[INFO] [stdout]     |
[INFO] [stdout] 182 |                 elif_core::modules::ModuleValidationError::CircularImport { .. }
[INFO] [stdout]     |                 ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "controller_impl_test") due to 7 previous errors; 1 warning emitted
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:205:17
[INFO] [stdout]     |
[INFO] [stdout] 205 |                 elif_core::modules::ModuleValidationError::MissingExport { .. }
[INFO] [stdout]     |                 ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:49:1
[INFO] [stdout]    |
[INFO] [stdout] 49 | #[controller("/api/test")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:285:17
[INFO] [stdout]     |
[INFO] [stdout] 285 |                 elif_core::modules::ModuleValidationError::SelfImport { .. }
[INFO] [stdout]     |                 ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]    --> tests/epic_3_integration_test.rs:310:17
[INFO] [stdout]     |
[INFO] [stdout] 310 |                 elif_core::modules::ModuleValidationError::DuplicateExport { .. }
[INFO] [stdout]     |                 ^^^^^^^^^ use of unresolved module or unlinked crate `elif_core`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `elif_core`, use `cargo add elif_core` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/async_body_test.rs:70:5
[INFO] [stdout]    |
[INFO] [stdout] 70 |     #[post("")]
[INFO] [stdout]    |     ^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "test_optional_with_attributes") due to 4 previous errors
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:37:5
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0119]: conflicting implementations of trait `From<HttpError>` for type `HttpError`
[INFO] [stdout]   --> tests/body_injection_core_test.rs:32:1
[INFO] [stdout]    |
[INFO] [stdout] 32 | impl From<ElifError> for HttpError {
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: conflicting implementation in crate `core`:
[INFO] [stdout]            - impl<T> From<T> for T;
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/simple_body_test.rs:59:5
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[post("")]
[INFO] [stdout]    |     ^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/debug_macro_test.rs:42:5
[INFO] [stdout]    |
[INFO] [stdout] 42 |     #[get("/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]  --> tests/integration_test.rs:9:1
[INFO] [stdout]   |
[INFO] [stdout] 9 | #[controller("/api/test")]
[INFO] [stdout]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]   |
[INFO] [stdout]   = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:49:5
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[delete("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `delete` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:54:5
[INFO] [stdout]    |
[INFO] [stdout] 54 |     #[get("/{id}/http-result")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     #[get("/{id}/elif-response")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     #[get("/{id}/result")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/{id}/unit")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/return_type_handling_test.rs:87:5
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[get("/{id}/string")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/uuid_parameter_test.rs:48:1
[INFO] [stdout]    |
[INFO] [stdout] 48 | #[controller("/api/users")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `controller` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "debug_macro_test") due to 1 previous error
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/detailed_param_test.rs:47:5
[INFO] [stdout]    |
[INFO] [stdout] 47 |     #[get("/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "epic_3_integration_test") due to 15 previous errors
[INFO] [stdout] Some errors have detailed explanations: E0428, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0428`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "return_type_handling_test") due to 6 previous errors
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/detailed_param_test.rs:54:5
[INFO] [stdout]    |
[INFO] [stdout] 54 |     #[post("")]
[INFO] [stdout]    |     ^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0119, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0119`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:55:5
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[patch("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `patch` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "body_injection_core_test") due to 2 previous errors
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[get("/hello")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[get("/hello")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[get("/hello")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 12 | impl<ElifResponse> TestController {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("")] // Empty string for root route under controller
[INFO] [stdout]    |     ^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("")] // Empty string for root route under controller
[INFO] [stdout]    |     ^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("")] // Empty string for root route under controller
[INFO] [stdout]    |     ^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 12 | impl<ElifResponse> TestController {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[post("/data")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[post("/data")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> tests/integration_test.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[post("/data")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 12 | impl<ElifResponse> TestController {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/detailed_param_test.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     #[put("/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   --> tests/async_body_test.rs:32:11
[INFO] [stdout]    |
[INFO] [stdout] 32 | impl From<elif_http::HttpError> for HttpError {
[INFO] [stdout]    |           ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]   --> tests/async_body_test.rs:33:16
[INFO] [stdout]    |
[INFO] [stdout] 33 |     fn from(_: elif_http::HttpError) -> Self {
[INFO] [stdout]    |                ^^^^^^^^^ use of unresolved module or unlinked crate `elif_http`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `elif_http`, use `cargo add elif_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> tests/integration_test.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[get("/hello")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> tests/integration_test.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("")] // Empty string for root route under controller
[INFO] [stdout]    |     ^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> tests/integration_test.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[post("/data")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0412, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0412`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "integration_test") due to 13 previous errors
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "async_body_test") due to 3 previous errors
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/uuid_parameter_test.rs:53:5
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[get("/{user_id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "simple_body_test") due to 1 previous error
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]   --> tests/uuid_parameter_test.rs:60:5
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[get("/{user_id}/posts/{post_id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "uuid_parameter_test") due to 3 previous errors
[INFO] [stdout] error[E0599]: no method named `map_err` found for opaque type `impl Future<Output = Result<_, String>>` in the current scope
[INFO] [stdout]   --> tests/detailed_param_test.rs:54:5
[INFO] [stdout]    |
[INFO] [stdout] 54 |     #[post("")]
[INFO] [stdout]    |     ^^^^^^^^^^^ method not found in `impl Future<Output = Result<_, String>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: consider `await`ing on the `Future` and calling the method on its `Output`
[INFO] [stdout]    |
[INFO] [stdout] 54 |     await.#[post("")]
[INFO] [stdout]    |     ++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "comprehensive_body_test") due to 5 previous errors
[INFO] [stdout] error[E0599]: no method named `map_err` found for opaque type `impl Future<Output = Result<_, String>>` in the current scope
[INFO] [stdout]   --> tests/detailed_param_test.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     #[put("/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^ method not found in `impl Future<Output = Result<_, String>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: consider `await`ing on the `Future` and calling the method on its `Output`
[INFO] [stdout]    |
[INFO] [stdout] 61 |     await.#[put("/{id}")]
[INFO] [stdout]    |     ++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0433, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (test "detailed_param_test") due to 5 previous errors
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: could not find `elif_http` in the list of imported crates
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `elif_http` in the list of imported crates
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("/health")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("/health")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("/health")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:25:5
[INFO] [stdout]    |
[INFO] [stdout] 25 |     #[get("/api")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:25:5
[INFO] [stdout]    |
[INFO] [stdout] 25 |     #[get("/api")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:25:5
[INFO] [stdout]    |
[INFO] [stdout] 25 |     #[get("/api")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:37:5
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:37:5
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:37:5
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:49:5
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[delete("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `delete` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:49:5
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[delete("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `delete` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:49:5
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[delete("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `delete` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:55:5
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[patch("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `patch` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:55:5
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[patch("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `patch` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:55:5
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[patch("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `patch` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 17 | impl<ElifResponse> AppRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 77 | impl<ElifResponse> AdminRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:85:5
[INFO] [stdout]    |
[INFO] [stdout] 85 |     #[get("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:85:5
[INFO] [stdout]    |
[INFO] [stdout] 85 |     #[get("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:85:5
[INFO] [stdout]    |
[INFO] [stdout] 85 |     #[get("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 77 | impl<ElifResponse> AdminRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:91:5
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:91:5
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:91:5
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 77 | impl<ElifResponse> AdminRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:97:5
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:97:5
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:97:5
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]    |
[INFO] [stdout] 77 | impl<ElifResponse> AdminRoutes {
[INFO] [stdout]    |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:103:5
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:103:5
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:103:5
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout]  77 | impl<ElifResponse> AdminRoutes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:115:5
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[get("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:115:5
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[get("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:115:5
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[get("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 113 | impl<ElifResponse> ApiV1Routes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:121:5
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:121:5
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:121:5
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 113 | impl<ElifResponse> ApiV1Routes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:127:5
[INFO] [stdout]     |
[INFO] [stdout] 127 |     #[post("/logout")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:127:5
[INFO] [stdout]     |
[INFO] [stdout] 127 |     #[post("/logout")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:127:5
[INFO] [stdout]     |
[INFO] [stdout] 127 |     #[post("/logout")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 113 | impl<ElifResponse> ApiV1Routes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:133:5
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:133:5
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:133:5
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 113 | impl<ElifResponse> ApiV1Routes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 113 | impl<ElifResponse> ApiV1Routes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 165 | impl<ElifResponse> ComplexRoutes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifRequest` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `HttpResult` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `ElifResponse` in this scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a type parameter
[INFO] [stdout]     |
[INFO] [stdout] 165 | impl<ElifResponse> ComplexRoutes {
[INFO] [stdout]     |     ++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `health_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:20:12
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("/health")]
[INFO] [stdout]    |     ----------------- help: use associated function syntax instead: `AppRoutes::health_original()`
[INFO] [stdout] 20 |     pub fn health() -> String {
[INFO] [stdout]    |            ^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:20:5
[INFO] [stdout]    |
[INFO] [stdout] 20 |     pub fn health() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     #[get("/health")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `api_root_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:26:12
[INFO] [stdout]    |
[INFO] [stdout] 25 |     #[get("/api")]
[INFO] [stdout]    |     -------------- help: use associated function syntax instead: `AppRoutes::api_root_original()`
[INFO] [stdout] 26 |     pub fn api_root() -> String {
[INFO] [stdout]    |            ^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:26:5
[INFO] [stdout]    |
[INFO] [stdout] 26 |     pub fn api_root() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:25:5
[INFO] [stdout]    |
[INFO] [stdout] 25 |     #[get("/api")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `create_item_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:32:12
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ----------------- help: use associated function syntax instead: `AppRoutes::create_item_original()`
[INFO] [stdout] 32 |     pub fn create_item() -> String {
[INFO] [stdout]    |            ^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:32:5
[INFO] [stdout]    |
[INFO] [stdout] 32 |     pub fn create_item() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `create_item` with a similar name, but with different arguments
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:31:5
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[post("/items")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `get_item_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:38:12
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     --------------------- help: use associated function syntax instead: `AppRoutes::get_item_original(id)`
[INFO] [stdout] 38 |     pub fn get_item(id: u32) -> String {
[INFO] [stdout]    |            ^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:38:5
[INFO] [stdout]    |
[INFO] [stdout] 38 |     pub fn get_item(id: u32) -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:37:5
[INFO] [stdout]    |
[INFO] [stdout] 37 |     #[get("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `delete_item_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:50:12
[INFO] [stdout]    |
[INFO] [stdout] 50 |     pub fn delete_item(id: u32) -> String {
[INFO] [stdout]    |            ^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:50:5
[INFO] [stdout]    |
[INFO] [stdout] 50 |     pub fn delete_item(id: u32) -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: use associated function syntax instead
[INFO] [stdout]    |
[INFO] [stdout] 49 -     #[delete("/items/{id}")]
[INFO] [stdout] 49 +     AppRoutes::delete_item_original(id)
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:49:5
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[delete("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `delete` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `patch_item_original` found for reference `&AppRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:56:12
[INFO] [stdout]    |
[INFO] [stdout] 56 |     pub fn patch_item(id: u32) -> String {
[INFO] [stdout]    |            ^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AppRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:56:5
[INFO] [stdout]    |
[INFO] [stdout] 56 |     pub fn patch_item(id: u32) -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: use associated function syntax instead
[INFO] [stdout]    |
[INFO] [stdout] 55 -     #[patch("/items/{id}")]
[INFO] [stdout] 55 +     AppRoutes::patch_item_original(id)
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:55:5
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[patch("/items/{id}")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `patch` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `dashboard_original` found for reference `&AdminRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:80:12
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     -------------------- help: use associated function syntax instead: `AdminRoutes::dashboard_original()`
[INFO] [stdout] 80 |     pub fn dashboard() -> String {
[INFO] [stdout]    |            ^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AdminRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:80:5
[INFO] [stdout]    |
[INFO] [stdout] 80 |     pub fn dashboard() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `dashboard` with a similar name, but with different arguments
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:79:5
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[get("/dashboard")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `settings_original` found for reference `&AdminRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:86:12
[INFO] [stdout]    |
[INFO] [stdout] 85 |     #[get("/settings")]
[INFO] [stdout]    |     ------------------- help: use associated function syntax instead: `AdminRoutes::settings_original()`
[INFO] [stdout] 86 |     pub fn settings() -> String {
[INFO] [stdout]    |            ^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AdminRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:86:5
[INFO] [stdout]    |
[INFO] [stdout] 86 |     pub fn settings() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:85:5
[INFO] [stdout]    |
[INFO] [stdout] 85 |     #[get("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `update_settings_original` found for reference `&AdminRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:92:12
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     -------------------- help: use associated function syntax instead: `AdminRoutes::update_settings_original()`
[INFO] [stdout] 92 |     pub fn update_settings() -> String {
[INFO] [stdout]    |            ^^^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AdminRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:92:5
[INFO] [stdout]    |
[INFO] [stdout] 92 |     pub fn update_settings() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `update_settings` with a similar name, but with different arguments
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:91:5
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:91:5
[INFO] [stdout]    |
[INFO] [stdout] 91 |     #[post("/settings")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `manage_users_original` found for reference `&AdminRoutes` in the current scope
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:98:12
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ---------------- help: use associated function syntax instead: `AdminRoutes::manage_users_original()`
[INFO] [stdout] 98 |     pub fn manage_users() -> String {
[INFO] [stdout]    |            ^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]    |
[INFO] [stdout]    = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AdminRoutes`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:98:5
[INFO] [stdout]    |
[INFO] [stdout] 98 |     pub fn manage_users() -> String {
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `manage_users` with a similar name, but with different arguments
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:97:5
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]   --> examples/advanced_routing_demo.rs:97:5
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[get("/users")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `create_admin_user_original` found for reference `&AdminRoutes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:104:12
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ----------------- help: use associated function syntax instead: `AdminRoutes::create_admin_user_original()`
[INFO] [stdout] 104 |     pub fn create_admin_user() -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `AdminRoutes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 |     pub fn create_admin_user() -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `create_admin_user` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:103:5
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:103:5
[INFO] [stdout]     |
[INFO] [stdout] 103 |     #[post("/users")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `profile_original` found for reference `&ApiV1Routes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:116:12
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[get("/profile")]
[INFO] [stdout]     |     ------------------ help: use associated function syntax instead: `ApiV1Routes::profile_original()`
[INFO] [stdout] 116 |     pub fn profile() -> String {
[INFO] [stdout]     |            ^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ApiV1Routes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:116:5
[INFO] [stdout]     |
[INFO] [stdout] 116 |     pub fn profile() -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:115:5
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[get("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `update_profile_original` found for reference `&ApiV1Routes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:122:12
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ------------------ help: use associated function syntax instead: `ApiV1Routes::update_profile_original()`
[INFO] [stdout] 122 |     pub fn update_profile() -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ApiV1Routes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:122:5
[INFO] [stdout]     |
[INFO] [stdout] 122 |     pub fn update_profile() -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `update_profile` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:121:5
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:121:5
[INFO] [stdout]     |
[INFO] [stdout] 121 |     #[put("/profile")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `put` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `logout_original` found for reference `&ApiV1Routes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:128:12
[INFO] [stdout]     |
[INFO] [stdout] 127 |     #[post("/logout")]
[INFO] [stdout]     |     ------------------ help: use associated function syntax instead: `ApiV1Routes::logout_original()`
[INFO] [stdout] 128 |     pub fn logout() -> String {
[INFO] [stdout]     |            ^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ApiV1Routes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     pub fn logout() -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:127:5
[INFO] [stdout]     |
[INFO] [stdout] 127 |     #[post("/logout")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `post` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `notifications_original` found for reference `&ApiV1Routes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:134:12
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ------------------------ help: use associated function syntax instead: `ApiV1Routes::notifications_original()`
[INFO] [stdout] 134 |     pub fn notifications() -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ApiV1Routes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:134:5
[INFO] [stdout]     |
[INFO] [stdout] 134 |     pub fn notifications() -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `notifications` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:133:5
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:133:5
[INFO] [stdout]     |
[INFO] [stdout] 133 |     #[get("/notifications")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `get_org_member_original` found for reference `&ApiV1Routes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:140:12
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ----------------------------------------------------- help: use associated function syntax instead: `ApiV1Routes::get_org_member_original(org_id, member_id)`
[INFO] [stdout] 140 |     pub fn get_org_member(org_id: String, member_id: u64) -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ApiV1Routes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:140:5
[INFO] [stdout]     |
[INFO] [stdout] 140 |     pub fn get_org_member(org_id: String, member_id: u64) -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `get_org_member` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:139:5
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[get("/organizations/{org_id}/members/{member_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `get_comment_original` found for reference `&ComplexRoutes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:168:12
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ---------------------------------------------------------------- help: use associated function syntax instead: `ComplexRoutes::get_comment_original(user_id, post_id, comment_id)`
[INFO] [stdout] 168 |     pub fn get_comment(user_id: u32, post_id: u64, comment_id: u32) -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ComplexRoutes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:168:5
[INFO] [stdout]     |
[INFO] [stdout] 168 |     pub fn get_comment(user_id: u32, post_id: u64, comment_id: u32) -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `get_comment` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:167:5
[INFO] [stdout]     |
[INFO] [stdout] 167 |     #[get("/users/{user_id}/posts/{post_id}/comments/{comment_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `get_categorized_item_original` found for reference `&ComplexRoutes` in the current scope
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:177:12
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ------------------------------------------------ help: use associated function syntax instead: `ComplexRoutes::get_categorized_item_original(category, item_id)`
[INFO] [stdout] 177 |     pub fn get_categorized_item(category: String, item_id: u32) -> String {
[INFO] [stdout]     |            ^^^^^^^^^^^^^^^^^^^^ this is an associated function, not a method
[INFO] [stdout]     |
[INFO] [stdout]     = note: found the following associated functions; to be used as methods, functions must have a `self` parameter
[INFO] [stdout] note: the candidate is defined in an impl for the type `ComplexRoutes`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:177:5
[INFO] [stdout]     |
[INFO] [stdout] 177 |     pub fn get_categorized_item(category: String, item_id: u32) -> String {
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: there is a method `get_categorized_item` with a similar name, but with different arguments
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of undeclared type `ElifResponse`
[INFO] [stdout]    --> examples/advanced_routing_demo.rs:176:5
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[get("/categories/{category}/items/{item_id}")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ElifResponse`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0412, E0433, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0412`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `elif-http-derive` (example "advanced_routing_demo") due to 98 previous errors
[INFO] running `Command { std: "docker" "inspect" "2d236a139434d20562f4bf5c7c65692ea0a2dc580af488b97ee6b079f2480559", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "2d236a139434d20562f4bf5c7c65692ea0a2dc580af488b97ee6b079f2480559", kill_on_drop: false }`
[INFO] [stdout] 2d236a139434d20562f4bf5c7c65692ea0a2dc580af488b97ee6b079f2480559