Log CLI invocation error as is without UnhandledPromiseException - #277
Merged
Sebastian-Webster merged 1 commit intoAug 9, 2026
Conversation
Sebastian-Webster
deleted the
276-log-error-from-cli-execution-as-is-without-unhandledpromiseexception
branch
August 9, 2026 08:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request closes #276
If an error occurred during database creation from the CLI, the error would be inside of an UnhandledPromiseException.
For example:
UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "Option logLevel must be either undefined or "LOG", "WARN", or "ERROR". | Received value: notaloglevel (type: string)".By adding a catch to the database creation, any errors will now show up in the console as is, without the UnhandledPromiseException. For example:
ERROR: Option logLevel must be either undefined or "LOG", "WARN", or "ERROR". | Received value: notaloglevel (type: string)This makes the error a lot easier to read.