add preflight script graphiql plugin #16737
n1ru4lpr.yaml
on: pull_request
Matrix: build / build-and-dockerize
alpha
/
cli-artifacts
4m 54s
alpha
/
...
/
snapshot
53s
graphql-breaking-changes
/
search-token
0s
db-types
/
diff
1m 31s
test
/
db-migrations
1m 19s
test
/
unit
2m 1s
code-style
/
eslint-and-prettier
3m 36s
typescript
/
typecheck
4m 10s
website-preview
/
deployment
3m 47s
storybook-preview
/
deployment
3m 30s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
Matrix: alpha / cli-test
graphql-breaking-changes
/
check
8s
test
/
e2e
6m 53s
Matrix: test / integration
alpha
/
...
/
Build CLI Docker Image
Annotations
7 errors and 28 warnings
|
Unhandled error:
packages/libraries/yoga/tests/persisted-documents.spec.ts#L744
Error: Snapshot `usage reporting with batch execution and persisted documents 1` mismatched
- Expected
+ Received
@@ -4,13 +4,6 @@
Query.a,
],
operation: {a},
operationName: anonymous,
},
- e8571e61911eea36db5ef7a3ed222aacb0cd5ba1: {
- fields: [
- Query.b,
- ],
- operation: {b},
- operationName: anonymous,
- },
}
❯ createMismatchError node_modules/.pnpm/@vitest+snapshot@2.0.5/node_modules/@vitest/snapshot/dist/index.js:1647:17
❯ SnapshotClient.assert node_modules/.pnpm/@vitest+snapshot@2.0.5/node_modules/@vitest/snapshot/dist/index.js:1748:13
❯ Proxy.__INLINE_SNAPSHOT__ node_modules/.pnpm/vitest@2.0.5_@types+node@22.9.3_less@4.2.0_lightningcss@1.28.1_terser@5.36.0/node_modules/vitest/dist/chunks/vi.fiQ7lMRF.js:281:27
❯ Proxy.methodWrapper node_modules/.pnpm/chai@5.1.1/node_modules/chai/chai.js:1591:25
❯ Object.<anonymous> packages/libraries/yoga/tests/persisted-documents.spec.ts:744:24
❯ matchBody node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/match_body.js:42:17
❯ Interceptor.match node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/interceptor.js:359:17
❯ node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/intercepted_request_router.js:304:9
❯ InterceptedRequestRouter.startPlayback node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/intercepted_request_router.js:303:45
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.
|
|
Unhandled error:
packages/libraries/yoga/tests/persisted-documents.spec.ts#L744
Error: Snapshot `usage reporting with batch execution and persisted documents 2` mismatched
- Expected
+ Received
@@ -1,13 +1,6 @@
{
- 07188723c7bd37a812cb478cc980f83fe5b4026c: {
- fields: [
- Query.a,
- ],
- operation: {a},
- operationName: anonymous,
- },
e8571e61911eea36db5ef7a3ed222aacb0cd5ba1: {
fields: [
Query.b,
],
operation: {b},
❯ createMismatchError node_modules/.pnpm/@vitest+snapshot@2.0.5/node_modules/@vitest/snapshot/dist/index.js:1647:17
❯ SnapshotClient.assert node_modules/.pnpm/@vitest+snapshot@2.0.5/node_modules/@vitest/snapshot/dist/index.js:1748:13
❯ Proxy.__INLINE_SNAPSHOT__ node_modules/.pnpm/vitest@2.0.5_@types+node@22.9.3_less@4.2.0_lightningcss@1.28.1_terser@5.36.0/node_modules/vitest/dist/chunks/vi.fiQ7lMRF.js:281:27
❯ Proxy.methodWrapper node_modules/.pnpm/chai@5.1.1/node_modules/chai/chai.js:1591:25
❯ Object.<anonymous> packages/libraries/yoga/tests/persisted-documents.spec.ts:744:24
❯ matchBody node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/match_body.js:42:17
❯ Interceptor.match node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/interceptor.js:359:17
❯ node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/intercepted_request_router.js:304:9
❯ InterceptedRequestRouter.startPlayback node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/intercepted_request_router.js:303:45
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.
|
|
packages/libraries/yoga/tests/persisted-documents.spec.ts > usage reporting with batch execution and persisted documents:
packages/libraries/yoga/tests/persisted-documents.spec.ts#L826
AssertionError: Mocks not yet satisfied:
POST http://localhost:80/usage
- Expected
+ Received
- true
+ false
❯ Scope.done node_modules/.pnpm/nock@14.0.0-beta.7/node_modules/nock/lib/scope.js:205:12
❯ packages/libraries/yoga/tests/persisted-documents.spec.ts:826:23
|
|
test / unit
Process completed with exit code 1.
|
|
test / e2e
The process '/home/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 1
|
|
test / integration (1)
The run was canceled by @github-actions[bot].
|
|
test / integration (1)
The operation was canceled.
|
|
alpha / npm / snapshot
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/
|
|
alpha / npm / snapshot
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/
|
|
alpha / npm / snapshot
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/
|
|
static-analysis / analyze (typescript)
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.
|
|
static-analysis / analyze (typescript)
Unable to validate code scanning workflow: MissingPushHook
|
|
static-analysis / analyze (javascript)
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.
|
|
static-analysis / analyze (javascript)
Unable to validate code scanning workflow: MissingPushHook
|
|
alpha / cli-test (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L12
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L13
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L22
UndefinedVar: Usage of undefined variable '$PORT'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
cypress
|
7.01 MB |
|
|
graphql-hive~console~O72BRS+13.dockerbuild
|
1.49 MB |
|
|
graphql-hive~console~QINMYG+13.dockerbuild
|
1.75 MB |
|
|
hive-cli-darwin-arm64
|
41.3 MB |
|
|
hive-cli-darwin-x64
|
42 MB |
|
|
hive-cli-linux-arm
|
41.9 MB |
|
|
hive-cli-linux-x64
|
46.6 MB |
|
|
hive-cli-win-x64
|
36.9 MB |
|
|
hive-cli-win-x86
|
34.4 MB |
|