Cody Casterline

This seems to mostly work for me: ```typescript #!/usr/bin/env deno run --allow-net --allow-env --allow-read=. // Minor problem: Every time I run, Deno (re-)tries downloading // https://esm.sh/v115/@types/[email protected]/graphql~.d.ts // looking for types,...

@trevor-scheer Unfortunately, I don't have time to take that on. But hopefully the working demo above will at least let others see that it's not far off. (Anybody else want...

It seems like the bug here is that `pip-compile` should resolve *all* dependencies for all python versions, so that the `requirements.txt` that it generates with `--generate-hashes` will work on multiple...

Well, today I learned that the "bug" behavior I'm seeing is actually [defined in the GraphQL specification][1]: > If an error was raised during the execution that prevented a valid...

Oops, nevermind, the spec goes on to say: > If a field error is raised, execution attempts to continue and a partial result is produced (see [Handling Field Errors](https://spec.graphql.org/October2021/#sec-Handling-Field-Errors)). The...

I tried that as well, and got the same error. Maybe I'm on an older version. I'll update and try again.

Came back to test this. Created a repository where I can reproduce this issue: https://github.com/NfNitLoop/async-graphql-bug-1449/commit/5563f45e2ebed13b44d04bba6803a380796baafc But then I re-read @Miaxos's comment, suggesting `Option` and I tried that. Sure enough, it...

We started running into this just today. A few hours earlier, builds worked. Now they're failing, with no changes to our go code or workflow. ``` Run golangci/golangci-lint-action@v3 with: version:...

I'm getting this error too. But, I think the error in sscache is just a duplicate of an error that happens earlier in the build: ``` Run PyO3/maturin-action@v1 with: target:...

I'd recommend we rename this bug to "No module named pip for x86 manylinux_2_28".