Argument of type '{ document: DocumentNode; schema: GraphQLSchema; rootValue?: unknown; contextValue?: unknown; variableValues?: Maybe<{ readonly [variable: string]: unknown; }>; operationName?: Maybe<string>; fieldResolver?: Maybe<GraphQLFieldResolver<any, any>>; typeResolver?: Maybe<GraphQLTypeResolver<any, any>>; subscribeFieldRes...' is not assignable to parameter of type 'ExecutionArgs'.

Type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema' is not assignable to type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema'.

@graphql-hive/yoga#build: command (/home/runner/work/console/console/packages/libraries/yoga) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)

Process completed with exit code 1.

Error: Cannot use GraphQLObjectType "Query" from another module or realm. Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed. https://yarnpkg.com/en/docs/selective-version-resolutions Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results. ❯ instanceOf node_modules/.pnpm/[email protected]/node_modules/graphql/jsutils/instanceOf.js:48:19 ❯ isObjectType node_modules/.pnpm/[email protected]/node_modules/graphql/type/definition.js:131:37 ❯ TypeInfo.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:165:40 ❯ Object.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:387:16 ❯ Proxy.visit node_modules/.pnpm/[email protected]/node_modules/graphql/language/visitor.js:197:21 ❯ Module.collectSchemaCoordinates packages/libraries/core/src/client/collect-schema-coordinates.ts:155:3 ❯ collect packages/libraries/core/src/client/usage.ts:345:21 ❯ packages/libraries/core/src/client/utils.ts:83:19 ❯ captureAsync packages/libraries/core/src/client/agent.ts:120:17 This error originated in "packages/libraries/yoga/tests/persisted-documents.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "usage reporting for persisted document". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Cannot use GraphQLObjectType "Subscription" from another module or realm. Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed. https://yarnpkg.com/en/docs/selective-version-resolutions Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results. ❯ instanceOf node_modules/.pnpm/[email protected]/node_modules/graphql/jsutils/instanceOf.js:48:19 ❯ isObjectType node_modules/.pnpm/[email protected]/node_modules/graphql/type/definition.js:131:37 ❯ TypeInfo.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:165:40 ❯ Object.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:387:16 ❯ Proxy.visit node_modules/.pnpm/[email protected]/node_modules/graphql/language/visitor.js:197:21 ❯ Module.collectSchemaCoordinates packages/libraries/core/src/client/collect-schema-coordinates.ts:155:3 ❯ collect packages/libraries/core/src/client/usage.ts:345:21 ❯ packages/libraries/core/src/client/utils.ts:83:19 ❯ captureAsync packages/libraries/core/src/client/agent.ts:120:17 This error originated in "packages/libraries/yoga/tests/persisted-documents.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "usage reporting for persisted document (subscription)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Cannot use GraphQLObjectType "Query" from another module or realm. Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed. https://yarnpkg.com/en/docs/selective-version-resolutions Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results. ❯ instanceOf node_modules/.pnpm/[email protected]/node_modules/graphql/jsutils/instanceOf.js:48:19 ❯ isObjectType node_modules/.pnpm/[email protected]/node_modules/graphql/type/definition.js:131:37 ❯ TypeInfo.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:165:40 ❯ Object.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:387:16 ❯ Proxy.visit node_modules/.pnpm/[email protected]/node_modules/graphql/language/visitor.js:197:21 ❯ Module.collectSchemaCoordinates packages/libraries/core/src/client/collect-schema-coordinates.ts:155:3 ❯ collect packages/libraries/core/src/client/usage.ts:345:21 ❯ packages/libraries/core/src/client/utils.ts:83:19 ❯ captureAsync packages/libraries/core/src/client/agent.ts:120:17 This error originated in "packages/libraries/yoga/tests/persisted-documents.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "usage reporting with batch execution and persisted documents". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Cannot use GraphQLObjectType "Query" from another module or realm. Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed. https://yarnpkg.com/en/docs/selective-version-resolutions Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results. ❯ instanceOf node_modules/.pnpm/[email protected]/node_modules/graphql/jsutils/instanceOf.js:48:19 ❯ isObjectType node_modules/.pnpm/[email protected]/node_modules/graphql/type/definition.js:131:37 ❯ TypeInfo.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:165:40 ❯ Object.enter node_modules/.pnpm/[email protected]/node_modules/graphql/utilities/TypeInfo.js:387:16 ❯ Proxy.visit node_modules/.pnpm/[email protected]/node_modules/graphql/language/visitor.js:197:21 ❯ Module.collectSchemaCoordinates packages/libraries/core/src/client/collect-schema-coordinates.ts:155:3 ❯ collect packages/libraries/core/src/client/usage.ts:345:21 ❯ packages/libraries/core/src/client/utils.ts:83:19 ❯ captureAsync packages/libraries/core/src/client/agent.ts:120:17 This error originated in "packages/libraries/yoga/tests/persisted-documents.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "usage reporting with batch execution and persisted documents". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:170:27

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:218:27

AssertionError: Mocks not yet satisfied: POST http://localhost:80/usage - Expected + Received - true + false ❯ Scope.done node_modules/.pnpm/[email protected]/node_modules/nock/lib/scope.js:205:12 ❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:527:14

AssertionError: Mocks not yet satisfied: POST http://localhost:80/usage - Expected + Received - true + false ❯ Scope.done node_modules/.pnpm/[email protected]/node_modules/nock/lib/scope.js:205:12 ❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:661:14

AssertionError: Mocks not yet satisfied: POST http://localhost:80/usage - Expected + Received - true + false ❯ Scope.done node_modules/.pnpm/[email protected]/node_modules/nock/lib/scope.js:205:12 ❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:826:23

Process completed with exit code 1.

Argument of type '{ document: DocumentNode; schema: GraphQLSchema; rootValue?: unknown; contextValue?: unknown; variableValues?: Maybe<{ readonly [variable: string]: unknown; }>; operationName?: Maybe<string>; fieldResolver?: Maybe<GraphQLFieldResolver<any, any>>; typeResolver?: Maybe<GraphQLTypeResolver<any, any>>; subscribeFieldRes...' is not assignable to parameter of type 'ExecutionArgs'.

Type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema' is not assignable to type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema'.

@graphql-hive/yoga#build: command (/home/runner/work/console/console/packages/libraries/yoga) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)

The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1

Argument of type '{ document: DocumentNode; schema: GraphQLSchema; rootValue?: unknown; contextValue?: unknown; variableValues?: Maybe<{ readonly [variable: string]: unknown; }>; operationName?: Maybe<string>; fieldResolver?: Maybe<GraphQLFieldResolver<any, any>>; typeResolver?: Maybe<GraphQLTypeResolver<any, any>>; subscribeFieldRes...' is not assignable to parameter of type 'ExecutionArgs'.

Type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema' is not assignable to type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema'.

Process completed with exit code 2.

Argument of type '{ document: DocumentNode; schema: GraphQLSchema; rootValue?: unknown; contextValue?: unknown; variableValues?: Maybe<{ readonly [variable: string]: unknown; }>; operationName?: Maybe<string>; fieldResolver?: Maybe<GraphQLFieldResolver<any, any>>; typeResolver?: Maybe<GraphQLTypeResolver<any, any>>; subscribeFieldRes...' is not assignable to parameter of type 'ExecutionArgs'.

Type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema' is not assignable to type 'import("/home/runner/work/console/console/node_modules/.pnpm/[email protected]/node_modules/graphql/type/schema").GraphQLSchema'.

@graphql-hive/yoga#build: command (/home/runner/work/console/console/packages/libraries/yoga) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)

Process completed with exit code 1.

The job was canceled because "hive-linux-arm64-ubuntu22" failed.

The operation was canceled.

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.

Unable to validate code scanning workflow: MissingPushHook

1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.