-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Log error when project cannot be created #36057
Conversation
a6c3946
to
fb0a965
Compare
fb0a965
to
995ad3b
Compare
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
@@ -139,6 +143,7 @@ public static Optional<Project> createProject(ApplicationInfoBuildItem app, | |||
buildInfo, project.getScmInfo())); | |||
|
|||
} catch (Exception e) { | |||
LOG.debugv(e, "Couldn't create project for {0} application", name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be debug or does it have value for the user?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I debated using info level… the problem is that the exception you usually get is not really actionable as-is since you get exceptions like the one seen in #36041. Maybe if dekorate was returning more informative exceptions, it would make more sense to use an info level here.
I will let @iocanel have the final say on this as some changes might be needed in Dekorate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.