Skip to content

Catch name clashes in the OM parser.#577

Merged
brian-brazil merged 4 commits intomasterfrom
name-clash
Nov 13, 2020
Merged

Catch name clashes in the OM parser.#577
brian-brazil merged 4 commits intomasterfrom
name-clash

Conversation

@brian-brazil
Copy link
Copy Markdown
Contributor

Make sure we're catching all the cases in the client too.
This means you can't have a foo counter and a foo_created gauge.

@SuperQ Per the most recent discussions.

@brian-brazil brian-brazil force-pushed the name-clash branch 2 times, most recently from 17fb31c to 2e26e2f Compare September 15, 2020 13:18
@brian-brazil
Copy link
Copy Markdown
Contributor Author

@SuperQ Updated as per the meeting just there.

@SuperQ
Copy link
Copy Markdown
Member

SuperQ commented Nov 3, 2020

Looks like this needs a rebase.

@SuperQ SuperQ self-requested a review November 3, 2020 18:23
Make sure we're catching all the cases in the client too.
This means you can't have a foo counter and a foo_created gauge.

Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
This is so the average can be calculated.

Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
@brian-brazil
Copy link
Copy Markdown
Contributor Author

Rebased.

Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
Copy link
Copy Markdown
Contributor

@robskillington robskillington left a comment

Choose a reason for hiding this comment

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

LGTM

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.

3 participants