You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment if you fail to connect to the database, you'll get something like this:
✖ Connecting to database
Error: Post connection error
at /Users/stunjiturner/Downloads/Code/keystone-5/demo-projects/blog/node_modules/@keystone-alpha/utils/dist/utils.cjs.dev.js:72:21
at async executeDefaultServer (/Users/stunjiturner/Downloads/Code/keystone-5/demo-projects/blog/node_modules/@keystone-alpha/keystone/bin/utils.js:108:3) {
errors: {
MongooseAdapter: Error: Post connection error
at MongooseAdapter.connect (/Users/stunjiturner/Downloads/Code/keystone-5/demo-projects/blog/node_modules/@keystone-alpha/keystone/lib/adapters/index.js:31:23)
at processTicksAndRejections (internal/process/task_queues.js:89:5)
at async pReflect (/Users/stunjiturner/Downloads/Code/keystone-5/demo-projects/blog/node_modules/p-reflect/index.js:5:17)
at async Promise.all (index 0)
at async executeDefaultServer (/Users/stunjiturner/Downloads/Code/keystone-5/demo-projects/blog/node_modules/@keystone-alpha/keystone/bin/utils.js:108:3) {
errors: [Array]
}
}
}
error Command failed with exit code 1.
The actual error message which caused the failure is hidden within the line errors: [Array]. We need to improve the way we report these errors so that the vital info is not lost.
It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :)
At the moment if you fail to connect to the database, you'll get something like this:
The actual error message which caused the failure is hidden within the line
errors: [Array]
. We need to improve the way we report these errors so that the vital info is not lost.See #1231
The text was updated successfully, but these errors were encountered: