Parsa Shamaeezadeh

Commenting out this line: https://github.com/graphql-rust/juniper/blob/39d1e434204399357470c17c1f2a1b0b58fa6432/juniper_codegen/src/util/mod.rs#L1116 And then `cargo clean` and building again seems to have solved the issue. I think `#resolve_field_async` should be respecting the `noasync` attribute but it's not....

I didn't modify the `actix_web` example much, I don't see anything async here: ```rust ... pub struct Context { ///this could be a database connection users: HashMap, db: Rc }...

`into_enum_tokens` and `into_input_object_tokens` both have: ```rust if !self.no_async { body.extend(_async) } ``` in the end. ```into_tokens``` doesn't. I did the same there (changed `output` to mut, removed `#resolve_field_async` and added...

@tyranron Thank you for the explanation for !Sync in `juniper::execute`. However I think I'm missing something here: 1- I'm only using actix as a developing tool for now, later it'll...

@tyranron The problem can be reproduced with just this, the following doesn't compile: ```rust use rusqlite::{Connection}; use juniper::{GraphQLObject, graphql_object}; pub struct TestContext { conn: Connection, } impl juniper::Context for TestContext...

I'm on `juniper = "0.15.7"` Looking at the proc_macro code I don't see any mechanism to recognize whether the resolvers are async or not. I suspect the transition from manual...

@tyranron I see. So reading your first comment again, if I understand correctly you're saying that: If I'm not using async anywhere, and none of my of resolvers are async,...

I just ran into this issue earlier; Take a look at this: https://github.com/drizzle-team/drizzle-orm/blob/6adbd78748c8ecb687caa87b7cd775d86cdc0a2b/drizzle-orm/src/d1/session.ts#L68-L80 I'm really confused by the above code, it does not make sense to me. Regardless, I made...