Rafał Pitoń

Output from lldb: ``` * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x00000001000e3aba dethrace`ControlBoundFunkGroovePlus + 122 dethrace`ControlBoundFunkGroovePlus: -> 0x1000e3aba : addss (%rbx), %xmm0 0x1000e3abe...

Exactly same thing happens when Sinthea starts in race.

Hey, I was considering using the pre-made workflow that publishes new release on git tag, basically [this](https://github.com/mirumee/ariadne/blob/main/.github/workflows/publish.yml). Main way Misago is deployed is with `misago-docker`, and starting with v4 Misago...

Let's actually factually do this.

I don't know if this is possible with how GraphQL's query executor is structured, as disconnection goes down and just removes async generators without telling them their job is done....

Marked it for docs - we glance over the `info` contents, but it may be worth it to mention somewhere how to introspect it to find out what fields are...

I am not a fan of shoving this logic into the `make_executable_schema`. Introducing separate utils providing inter-op would be much preferable here. I think that simplest (even if not top-performing)...

@Sergei-Rudenkov this is not possible currently. Ariadne is using graphql-core v3 while Graphene is still on v2, and both of those versions share same namespace.

@Sergei-Rudenkov Sorry but no. I'm not able to put time now to dive into Graphene internals to develop thing like that.

I have an idea for changes to `make_executable_schema` that Ariadne GraphQL Modules implements that would make Graphene's v3 types work. There would be either a mixin or pass-through function that...