error: cannot check whether the hidden type of opaque type satisfies auto traits #401

Fantros · 2023-08-26T07:18:15Z

Fantros
Aug 26, 2023

error: cannot check whether the hidden type of opaque type satisfies auto traits
   --> src/main.rs:38:76
    |
38  |     let http = Server::bind(&SocketAddr::from(([127, 0, 0, 1], 80))).serve(Shared::new(service));
    |                                                                      ----- ^^^^^^^^^^^^^^^^^^^^
    |                                                                      |
    |                                                                      required by a bound introduced by this call
    |
note: opaque type is declared here
   --> src/main.rs:45:44
    |
45  | async fn handle(mut req: Request<Body>) -> Result<Response<Body>, Infallible> {
    |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: this item depends on auto traits of the hidden type, but may also be registering the hidden type. This is not supported right now. You can try moving the opaque type and the item that actually registers a hidden type into a new submodule
   --> src/main.rs:18:10
    |
18  | async fn main() {
    |          ^^^^
note: required because it appears within the type `ResponseFuture<impl Future<Output = Result<Response<Body>, Infallible>>, HeaderValue>`
   --> /home/codespace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tower-http-0.4.3/src/set_header/response.rs:275:16
    |
275 |     pub struct ResponseFuture<F, M> {
    |                ^^^^^^^^^^^^^^
note: required because it appears within the type `ResponseFuture<ResponseFuture<impl Future<Output = Result<Response<Body>, Infallible>>, HeaderValue>, HeaderValue>`
   --> /home/codespace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tower-http-0.4.3/src/set_header/response.rs:275:16
    |
275 |     pub struct ResponseFuture<F, M> {
    |                ^^^^^^^^^^^^^^
note: required because it appears within the type `H2StreamState<ResponseFuture<ResponseFuture<impl Future<Output = Result<Response<Body>, Infallible>>, HeaderValue>, HeaderValue>, Body>`
   --> /home/codespace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/proto/h2/server.rs:391:10
    |
391 |     enum H2StreamState<F, B>
    |          ^^^^^^^^^^^^^
note: required because it appears within the type `H2Stream<ResponseFuture<ResponseFuture<impl Future<Output = Result<Response<Body>, Infallible>>, HeaderValue>, HeaderValue>, Body>`
   --> /home/codespace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/proto/h2/server.rs:379:16
    |
379 |     pub struct H2Stream<F, B>
    |                ^^^^^^^^
    = note: required for `hyper::common::exec::Exec` to implement `hyper::common::exec::ConnStreamExec<tower_http::set_header::response::ResponseFuture<tower_http::set_header::response::ResponseFuture<impl std::future::Future<Output = Result<Response<Body>, Infallible>>, HeaderValue>, HeaderValue>, Body>`
note: required by a bound in `hyper::server::Builder::<I, E>::serve`
   --> /home/codespace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/server/server.rs:570:12
    |
560 |     pub fn serve<S, B>(self, make_service: S) -> Server<I, S, E>
    |            ----- required by a bound in this associated function
...
570 |         E: ConnStreamExec<<S::Service as HttpService<Body>>::Future, B>,
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `Builder::<I, E>::serve`

I am getting this error can you help me?

davidpdrsn · 2023-08-26T07:29:13Z

davidpdrsn
Aug 26, 2023
Maintainer

Please post the code that reproduces this. Can’t say much from the error alone.

7 replies

Fantros Aug 26, 2023
Author

async fn handle(mut req: Request<Body>) -> Result<Response<Body>, Infallible> {

}

davidpdrsn Aug 26, 2023
Maintainer

I think you’ll have to post a minimal reproduction example

Fantros Aug 26, 2023
Author

I found the problem, the errors in the handle affect there

davidpdrsn Aug 26, 2023
Maintainer

Would you mind posting a bit about what the problem/solution was? I’m case someone in the future finds their way to this question

Fantros Aug 26, 2023
Author

There was a data missing in the function, I added it and it was fixed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

error: cannot check whether the hidden type of opaque type satisfies auto traits #401

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 7 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

error: cannot check whether the hidden type of opaque type satisfies auto traits #401

Uh oh!

Fantros Aug 26, 2023

Replies: 1 comment · 7 replies

Uh oh!

davidpdrsn Aug 26, 2023 Maintainer

Uh oh!

Fantros Aug 26, 2023 Author

Uh oh!

davidpdrsn Aug 26, 2023 Maintainer

Uh oh!

Fantros Aug 26, 2023 Author

Uh oh!

davidpdrsn Aug 26, 2023 Maintainer

Uh oh!

Fantros Aug 26, 2023 Author

Fantros
Aug 26, 2023

Replies: 1 comment 7 replies

davidpdrsn
Aug 26, 2023
Maintainer

Fantros Aug 26, 2023
Author

davidpdrsn Aug 26, 2023
Maintainer

Fantros Aug 26, 2023
Author

davidpdrsn Aug 26, 2023
Maintainer

Fantros Aug 26, 2023
Author