Skip to content

185: Fix unsupported value type msg in log #192

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

banuchka
Copy link

@banuchka banuchka commented Oct 4, 2024

It is a useful thing to have correct information in log messages.
This PR is to fix an Issue 185

@bwplotka
Copy link
Member

bwplotka commented May 23, 2025

Thanks! Amazing -- do you mind rebasing and fixing DCO (signing commit)?

@@ -334,7 +334,12 @@ func (r *Receiver) search(projects []string, issueLabel string) (*jira.Issue, bo

issue := issues[0]
if len(issues) > 1 {
level.Warn(r.logger).Log("msg", "more than one issue matched, picking most recently resolved", "query", query, "issues", issues, "picked", issue)
keys := make([]string, len(issues))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mind adding a quick small function for this?

Copy link
Member

@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, DCO is blocking.

Signed-off-by: banuchka <tyrchenok@gmail.com>
@banuchka banuchka force-pushed the GH_jiralert_issue_185 branch from db71d89 to 2ccd9bd Compare May 23, 2025 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants