-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
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
plugin initialization error unclear #880
Comments
cstepanian
added a commit
that referenced
this issue
Feb 8, 2025
Resolves #880 - Print plugin errors with full context, like which file could not be opened. - Clarify wording of some error messages. - Add miette dependency to print helpful KDL parsing errors. Signed-off-by: Cal Stepanian <[email protected]>
cstepanian
added a commit
that referenced
this issue
Feb 8, 2025
Relates to #880 - Print plugin errors with full context, like which file could not be opened. - Clarify wording of some error messages. - Add miette dependency to print helpful KDL parsing errors. Signed-off-by: Cal Stepanian <[email protected]>
cstepanian
added a commit
that referenced
this issue
Feb 9, 2025
Resolves #880 Add plugin version to the `Plugin` struct so that it's available when starting plugins. Also add logging when Hipcheck retrieves and starts plugins. Signed-off-by: Cal Stepanian <[email protected]>
cstepanian
added a commit
that referenced
this issue
Feb 10, 2025
Resolves #880 Add plugin version to the `Plugin` struct so that it's available when starting plugins. Also add logging when Hipcheck retrieves and starts plugins. Signed-off-by: Cal Stepanian <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This output does not make it clear which plugin had an error being initialized. Also as a small nitpick, there should be a space or some delimiter between string and configuration
The text was updated successfully, but these errors were encountered: