Schema check/publish could fail due to GitHub errors/outages

[sentry]

Sentry Issue: GRAPHQL-HIVE-4KQ

HttpError: We couldn't respond to your request in time. Sorry about that. Please try resubmitting your request and contact us if the problem persists.
  File "../../../../node_modules/.pnpm/@octokit+request@8.3.1/node_modules/@octokit/request/dist-src/fetch-wrapper.js", line 71, in <anonymous>
    if (status >= 400) {
  File "node:internal/process/task_queues", line 105, in process.processTicksAndRejections
  File "../../../../node_modules/.pnpm/@octokit+auth-app@6.0.1/node_modules/@octokit/auth-app/dist-src/hook.js", line 69, in sendRequestWithRetries
    const timeSinceTokenCreationInMs = +/* @__PURE__ */ new Date() - +new Date(createdAt);
  File "../../../../node_modules/.pnpm/@octokit+plugin-retry@6.1.0_@octokit+core@5.2.0/node_modules/@octokit/plugin-retry/dist-src/wrap-request.js", line 4, in requestWithGraphqlErrorHandling
    async function wrapRequest(state, octokit, request, options) {
  File "../../../../node_modules/.pnpm/bottleneck@2.19.5/node_modules/bottleneck/light.js", line 403, in {Job#2}.doExecute
    this.Events.trigger("executing", eventInfo);

In this scenario, actors using the CLI will receive an "Unexpected error". We should probably instead give them more context, so they are not confused. E.g. "Failed to create GitHub status check. GitHub API is unresponsive.

In addition to that, this could lead to a schema check/schema publish succeeding on our end, but then failing due to the request to GitHub failing. We should think if that is okay or whether we want to handle this scenario differently.

Main questions:

• What information should we share with CLI users if a third-party request (e.g. to GitHub) fails after retries?
• How should we deal with GitHub check run creation failing after the schema version has been published? We still have partial success in that scenario; however, we tell the user that we are having an unexpected error

[dotansimha]

@n1ru4l bringing some focus on this one: it might be worth just showing the user that something is wrong with the GitHub call, it can help to figure out that something is wrong before reaching to support team.

[divomen]

I have the same issue now, it worked two days ago, but stopped working today.
How can I get any additional information about this error?

There are logs from github action:
$ hive schema:check --service ai ./src/schema.gql --registry.accessToken *** --github --debug
ℹ POST https://app.graphql-hive.com/graphql (x-request-id=439a23d4-1d16-461a-9c81-f4632faa4ee7) Attempt (1/6)
ℹ POST https://app.graphql-hive.com/graphql (x-request-id=439a23d4-1d16-461a-9c81-f4632faa4ee7) succeeded with status 200 (452ms).
✖ [
{
message: 'Unexpected error.',
locations: [ [Object] ],
path: [ 'schemaCheck' ],
extensions: { code: 'INTERNAL_SERVER_ERROR' }
}
]
› Error: Unexpected error. (Request ID:
› "439a23d4-1d16-961a-9c81-f4632faa4ee7") [115]
› > See https://the-guild.dev/graphql/hive/docs/api-reference/cli#errors for
› a complete list of error codes and recommended fixes.
› To disable this message set HIVE_NO_ERROR_TIP=1
› Reference: 439a23d4-1d16-961a-9c81-f4632faa4ee7
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: command finished with error: command (/home/runner/work/intail-mono/intail-mono/packages/ai) /tmp/yarn--1759328258119-0.06932716408673478/yarn run schema:check --registry.accessToken *** --github --debug exited (1)