Skip to content

Conversation

@shiftinv
Copy link
Contributor

see https://github.com/graphql-python/gql/releases/tag/v4.0.0.

Regarding specific changes, all the information is on the task all the info is in the commit messages.

It's worth mentioning that the documentation suggests[^1] setting `variable_values`
directly on the (in our case, global) query object, and doesn't really talk about race conditions,
but I would assume they can happen, especially in async code.
It might be fine if you call `gql.gql(<str>)` every time, which might be what the documentation suggests,
but that seems like a performance nightmare.
Therefore, we just construct a new `GraphQLRequest` from the existing globals,
which automatically copies over the parsed `Document` node, so it should have little to no overhead.

[^1]: https://gql.readthedocs.io/en/latest/usage/variables.html
transports now log with `DEBUG` instead of `INFO`,
so we can go back up to `INFO` without getting too spammy.
@sentry
Copy link

sentry bot commented Sep 25, 2025

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: monty/log.py

Function Unhandled Issue
setup OSError: [Errno 30] Read-only file system: 'logs' monty.log in setu...
Event Count: 3

@onerandomusername onerandomusername merged commit b24798d into onerandomusername:main Sep 26, 2025
4 checks passed
@shiftinv shiftinv deleted the deps/gql-v4 branch October 1, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants