Skip to content

Go: Properly escape dash in tracing-config.lua #9617

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

Merged
merged 1 commit into from
Jun 21, 2022

Conversation

criemen
Copy link
Collaborator

@criemen criemen commented Jun 20, 2022

Previously, the pattern didn't match what it was intended to match.

Previously, the pattern didn't match what it was intended to match.
@criemen criemen requested a review from a team as a code owner June 20, 2022 12:29
@criemen criemen requested a review from cklin June 20, 2022 12:30
@github-actions github-actions bot added the Go label Jun 20, 2022
Copy link
Contributor

@edoardopirovano edoardopirovano left a comment

Choose a reason for hiding this comment

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

Good find!

@AlexDenisov
Copy link
Contributor

Given the amount of time I spent debugging exactly the same issue, would it make sense to add a check to the tracer to issue a warning for such cases?

Copy link
Contributor

@smowton smowton left a comment

Choose a reason for hiding this comment

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

I'll take your word for it :)

@criemen
Copy link
Collaborator Author

criemen commented Jun 20, 2022

@AlexDenisov That would be great, but I don't think it's easy - to issue a correct warning, we'd need to parse Lua regexes, and I don't really want to get into the business of that 😬

@criemen criemen merged commit 0912996 into main Jun 21, 2022
@criemen criemen deleted the criemen/fix-go-pattern-lua-config branch June 21, 2022 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants