hash_pepper setup #70
push.yml
on: push
Matrix: Testing Application
Check Schema
32s
Deploying Application to Cloud VPS
0s
Annotations
11 errors
Check Schema
Failed to load 'schema.graphql' (ref: refs/pull/2627/merge)
|
Unhandled error:
tests/helpers/db.ts#L33
MongoPoolClosedError: Attempted to check out a connection from closed connection pool
❯ ConnectionPool.processWaitQueue node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:755:37
❯ ConnectionPool.close node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:521:10
❯ Server.destroy node_modules/mongoose/node_modules/mongodb/src/sdam/server.ts:249:15
❯ destroyServer node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:774:10
❯ Topology.close node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:505:7
❯ MongoClient.close node_modules/mongoose/node_modules/mongodb/src/mongo_client.ts:617:14
❯ processTicksAndRejections node:internal/process/task_queues:95:5
❯ NativeConnection.doClose node_modules/mongoose/lib/drivers/node-mongodb-native/connection.js:190:3
❯ NativeConnection._close node_modules/mongoose/lib/connection.js:966:7
❯ Module.disconnect tests/helpers/db.ts:33:3
❯ tests/resolvers/Mutation/updatePluginStatus.spec.ts:34:3
❯ callSuiteHook node_modules/@vitest/runner/dist/index.js:896:22
❯ runSuite node_modules/@vitest/runner/dist/index.js:1153:7
❯ runFiles node_modules/@vitest/runner/dist/index.js:1201:5
❯ startTests node_modules/@vitest/runner/dist/index.js:1210:3
❯ node_modules/vitest/dist/chunks/runBaseTests.Cx4wXyTR.js:130:11
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { address: 'localhost:27017', errmsg: 'Attempted to check out a connection from closed connection pool', hasErrorLabel: 'Function<hasErrorLabel>', addErrorLabel: 'Function<addErrorLabel>', errorLabels: [] }
This error originated in "tests/resolvers/Mutation/updatePluginStatus.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 "tests/resolvers/Mutation/updatePluginStatus.spec.ts". 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:
tests/helpers/db.ts#L33
MongoPoolClosedError: Attempted to check out a connection from closed connection pool
❯ ConnectionPool.processWaitQueue node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:755:37
❯ ConnectionPool.close node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:521:10
❯ Server.destroy node_modules/mongoose/node_modules/mongodb/src/sdam/server.ts:249:15
❯ destroyServer node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:774:10
❯ Topology.close node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:505:7
❯ MongoClient.close node_modules/mongoose/node_modules/mongodb/src/mongo_client.ts:617:14
❯ processTicksAndRejections node:internal/process/task_queues:95:5
❯ NativeConnection.doClose node_modules/mongoose/lib/drivers/node-mongodb-native/connection.js:190:3
❯ NativeConnection._close node_modules/mongoose/lib/connection.js:966:7
❯ Module.disconnect tests/helpers/db.ts:33:3
❯ tests/resolvers/Mutation/updatePluginStatus.spec.ts:34:3
❯ callSuiteHook node_modules/@vitest/runner/dist/index.js:896:22
❯ runSuite node_modules/@vitest/runner/dist/index.js:1153:7
❯ runFiles node_modules/@vitest/runner/dist/index.js:1201:5
❯ startTests node_modules/@vitest/runner/dist/index.js:1210:3
❯ node_modules/vitest/dist/chunks/runBaseTests.Cx4wXyTR.js:130:11
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { address: 'localhost:27017', errmsg: 'Attempted to check out a connection from closed connection pool', hasErrorLabel: 'Function<hasErrorLabel>', addErrorLabel: 'Function<addErrorLabel>', errorLabels: [] }
This error originated in "tests/resolvers/Mutation/updatePluginStatus.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 "tests/resolvers/Mutation/updatePluginStatus.spec.ts". 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:
tests/helpers/db.ts#L33
MongoPoolClosedError: Attempted to check out a connection from closed connection pool
❯ ConnectionPool.processWaitQueue node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:755:37
❯ ConnectionPool.close node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:521:10
❯ Server.destroy node_modules/mongoose/node_modules/mongodb/src/sdam/server.ts:249:15
❯ destroyServer node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:774:10
❯ Topology.close node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:505:7
❯ MongoClient.close node_modules/mongoose/node_modules/mongodb/src/mongo_client.ts:617:14
❯ processTicksAndRejections node:internal/process/task_queues:95:5
❯ NativeConnection.doClose node_modules/mongoose/lib/drivers/node-mongodb-native/connection.js:190:3
❯ NativeConnection._close node_modules/mongoose/lib/connection.js:966:7
❯ Module.disconnect tests/helpers/db.ts:33:3
❯ tests/resolvers/Mutation/updatePluginStatus.spec.ts:34:3
❯ callSuiteHook node_modules/@vitest/runner/dist/index.js:896:22
❯ runSuite node_modules/@vitest/runner/dist/index.js:1153:7
❯ runFiles node_modules/@vitest/runner/dist/index.js:1201:5
❯ startTests node_modules/@vitest/runner/dist/index.js:1210:3
❯ node_modules/vitest/dist/chunks/runBaseTests.Cx4wXyTR.js:130:11
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { address: 'localhost:27017', errmsg: 'Attempted to check out a connection from closed connection pool', hasErrorLabel: 'Function<hasErrorLabel>', addErrorLabel: 'Function<addErrorLabel>', errorLabels: [] }
This error originated in "tests/resolvers/Mutation/updatePluginStatus.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 "tests/resolvers/Mutation/updatePluginStatus.spec.ts". 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:
tests/helpers/db.ts#L33
MongoPoolClosedError: Attempted to check out a connection from closed connection pool
❯ ConnectionPool.processWaitQueue node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:755:37
❯ ConnectionPool.close node_modules/mongoose/node_modules/mongodb/src/cmap/connection_pool.ts:521:10
❯ Server.destroy node_modules/mongoose/node_modules/mongodb/src/sdam/server.ts:249:15
❯ destroyServer node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:774:10
❯ Topology.close node_modules/mongoose/node_modules/mongodb/src/sdam/topology.ts:505:7
❯ MongoClient.close node_modules/mongoose/node_modules/mongodb/src/mongo_client.ts:617:14
❯ processTicksAndRejections node:internal/process/task_queues:95:5
❯ NativeConnection.doClose node_modules/mongoose/lib/drivers/node-mongodb-native/connection.js:190:3
❯ NativeConnection._close node_modules/mongoose/lib/connection.js:966:7
❯ Module.disconnect tests/helpers/db.ts:33:3
❯ tests/resolvers/Mutation/updatePluginStatus.spec.ts:34:3
❯ callSuiteHook node_modules/@vitest/runner/dist/index.js:896:22
❯ runSuite node_modules/@vitest/runner/dist/index.js:1153:7
❯ runFiles node_modules/@vitest/runner/dist/index.js:1201:5
❯ startTests node_modules/@vitest/runner/dist/index.js:1210:3
❯ node_modules/vitest/dist/chunks/runBaseTests.Cx4wXyTR.js:130:11
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { address: 'localhost:27017', errmsg: 'Attempted to check out a connection from closed connection pool', hasErrorLabel: 'Function<hasErrorLabel>', addErrorLabel: 'Function<addErrorLabel>', errorLabels: [] }
This error originated in "tests/resolvers/Mutation/updatePluginStatus.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 "tests/resolvers/Mutation/updatePluginStatus.spec.ts". 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.
|
tests/utilities/adminCheck.spec.ts:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ createTestUser tests/helpers/userAndOrg.ts:23:23
❯ Module.createTestUserAndOrganization tests/helpers/userAndOrg.ts:107:26
❯ tests/utilities/adminCheck.spec.ts:28:28
|
tests/utilities/auth.spec.ts:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ createTestUser tests/helpers/user.ts:13:23
❯ Module.createTestUserFunc tests/helpers/user.ts:38:26
❯ tests/utilities/auth.spec.ts:30:16
|
tests/utilities/checks.spec.ts:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ createTestUser tests/helpers/userAndOrg.ts:23:23
❯ Module.createTestUserAndOrganization tests/helpers/userAndOrg.ts:107:26
❯ Module.createVolunteerAndActions tests/helpers/volunteers.ts:120:46
❯ tests/utilities/checks.spec.ts:64:11
|
tests/utilities/createSampleOrganizationUtil.spec.ts > generateUserData function > should return correct properties given ADMIN userType and organization Id:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ Module.generateUserData src/utilities/createSampleOrganizationUtil.ts:48:23
❯ tests/utilities/createSampleOrganizationUtil.spec.ts:28:28
|
tests/utilities/createSampleOrganizationUtil.spec.ts > generateUserData function > should return User with correct properties:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ Module.generateUserData src/utilities/createSampleOrganizationUtil.ts:48:23
❯ tests/utilities/createSampleOrganizationUtil.spec.ts:49:28
|
tests/utilities/createSampleOrganizationUtil.spec.ts > generateUserData function > should return Event with correct properties:
src/utilities/hashEmail.ts#L27
Error: Missing HASH_PEPPER environment variable required for secure email hashing
❯ Module.hashEmail src/utilities/hashEmail.ts:27:11
❯ Module.generateUserData src/utilities/createSampleOrganizationUtil.ts:48:23
❯ tests/utilities/createSampleOrganizationUtil.spec.ts:70:13
|