-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New issue when creating check runs. #203
Comments
The error message is pretty clear: we need to fix the request in the following way: - mutation newCheckRun($name: String!, $repoId: ID!, $headSha: String!,
+ mutation newCheckRun($name: String!, $repoId: ID!, $headSha: GitObjectID!,
$status: RequestableCheckStatusState!, $title: String!, $text: String, $summary: String!,
- $url: String!, $conclusion: CheckConclusionState, $externalId: String) {
+ $url: URI!, $conclusion: CheckConclusionState, $externalId: String) { Unfortunately, this means using a custom scalar, and it seems like this has not been implemented yet in graphql-ppx (teamwalnut/graphql-ppx#272). At the moment, the only workaround I can imagine is to intercept and patch the request before sending it (around this point): bot/bot-components/GitHub_mutations.ml Line 134 in 15a4b50
|
Use a manually edited copy of the query to use the right custom custom scalar.
The tested hackish workaround (d9c1d87) seems to work. |
I still don't understand the cause, has the GitHub API changed? |
From what I can tell, GitHub's API used to tolerate that we use the |
Use a manually edited copy of the query to use the right custom custom scalar.
Same technic (manually copied and patched query) than for coq#203.
Use a manually edited copy of the query to use the right custom custom scalar.
Same technic (manually copied and patched query) than for #203.
The explanation from GitHub is that they have upgraded their |
The creation of some check runs have failed in the last hours / days (?). An example failed query (that I could reproduce) is:
with variables:
leading to the following error:
The text was updated successfully, but these errors were encountered: