-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
feat: add debug logs to expressions #9533
feat: add debug logs to expressions #9533
Conversation
util/template/expression_template.go
Outdated
if (err != nil || result == nil) && allowUnresolved { // <nil> result is also un-resolved, and any error can be unresolved | ||
if (err != nil || result == nil) && allowUnresolved { | ||
// <nil> result is also un-resolved, and any error can be unresolved | ||
log.WithError(err).Debug("unresolved is allowed ") |
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.
how do we know if we hit this branch, not line 26? Mayb add more message?
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.
@alexec , Should I be adding a separate message for each debug pointer - Like on line: 26, 36 and 42? and in simple_template.go, on line 53?
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.
When I look at the logs, I should be able to know which line of code the logging came from. If each message was different, that would work.
@alexec , I have updated as per comments, Let me know if any further changes are required. |
Please sign off commits. |
4ecf2b1
to
1cc8e1e
Compare
@alexec , can we please close this PR. |
This was superseded by #10741 |
Fixes #TODO