Losing asgiref.Local value with async graphql resolvers

[ZipBrandon]

I am using https://strawberry.rocks/ as my GraphQL library. Everything works as expected with django-pgschemas when using it synchronously. get_current_schema() will return the schema I activated in my TenantProtocolRouter subclass. When I convert a query resolver to async (by introducing the async keyword to the function definition) then I receive a <django_pgschemas.schema.SchemaDescriptor object at 0xffff7114ecb0> when I call get_current_schema() and the tenant that I activated doesn't appear to be in the scope of the executing query resolver. I don't have a great understanding of asgiref.Local so I don't know if this would be expected. I migrated from django-tenants to circumvent the storing of the tenant on the connection and was hoping django-pgschemas's solution would help. Is there something that I could be conceptually missing?

[lorinkoz]

Hola @ZipBrandon. Can you give me more information so I can try to reproduce?

[lorinkoz]

Alright, my bad. This isn't trivial. Let me take a deeper look.

[lorinkoz]

I've been unable to trace the problem. Now, side question: because the tenant successfully arrives to your queries via info.context, would it be acceptable as a temporary workaround to activate the tenant right at the query?

[ZipBrandon]

@lorinkoz Exactly. You are correct and the ops that have to be async are being handled this way.

[lorinkoz]

My key takeaway: I need to add proper tests for django-channels both sync and async mode, so I can be sure whether this is a pgschemas thing or a strawberry thing. Let's see if I can allocate some time for that. In the meantime, if you or anyone from your team wants to take a shot at it, that would be highly appreciated.

[lorinkoz]

On a separate topic @ZipBrandon, we are using pgschemas in a single project that doesn't use the full set of features (namely async), therefore I don't have sufficient confidence that this package is production ready yet. Please use it with a grain of salt, as I know django-tenants is battle tested and way more mature than this one.