We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
klog still uses kong v0.7.1, although the latest version is v0.8.0 (at time of this writing).
After v0.7.1, there was a change in how kong handles errors from bindings. Errors, which are returned from bound objects, are now rewritten / reformatted, so the original error object is lost.
klog relies on the kong binding functionality in order to prettify AppError’s when something went wrong when executing a command. With the change in kong, the AppError object cannot be restored anymore.
AppError
I’m not sure yet how this can be fixed – options:
The text was updated successfully, but these errors were encountered:
Downgrade kong, to restore error handling/printing
80a8608
Due to #271, kong has to be downgraded again to v0.7.1. This PR also adds tests that would uncover the problem.
alecthomas/kong#383
Sorry, something went wrong.
A fix has landed. Waiting for next kong release to bump dependency.
0b9d589
No branches or pull requests
klog still uses kong v0.7.1, although the latest version is v0.8.0 (at time of this writing).
After v0.7.1, there was a change in how kong handles errors from bindings. Errors, which are returned from bound objects, are now rewritten / reformatted, so the original error object is lost.
klog relies on the kong binding functionality in order to prettify
AppError
’s when something went wrong when executing a command. With the change in kong, theAppError
object cannot be restored anymore.I’m not sure yet how this can be fixed – options:
The text was updated successfully, but these errors were encountered: