Skip to content

Conversation

@naughtyGitCat
Copy link
Contributor


Below we provide a basic checklist of things that would make it a good PR:

  • Make sure to sign the CLA (Contributor License Agreement).
  • Make sure all tests pass.
  • Keep current with the target branch and fix conflicts if necessary.
  • Update jira ticket description if necessary.
  • Attach screenshots and/or console output to the jira ticket to confirm new behavior, if applicable.
  • Leave notes to the reviewers if you need to focus their attention on something specific.

Once all checks pass and the code is ready for review, please add pmm-review-exporters team as the reviewer. That would assign people from the review team automatically. Report any issues on our Forum.

…, add arg in `TestShardsCollector` to fit ctor args change
…ame/configReplSetName}_{childKey}_{grandChildKey} raise error with '...was collected before with the same name and label values...'
@naughtyGitCat naughtyGitCat requested a review from a team as a code owner August 4, 2025 07:27
@naughtyGitCat naughtyGitCat requested review from BupycHuk and JiriCtvrtka and removed request for a team August 4, 2025 07:27
@idoqo
Copy link
Contributor

idoqo commented Aug 4, 2025

Hi, btw I see that the changes here are similar to https://github.com/percona/mongodb_exporter/pull/1122/files

@naughtyGitCat
Copy link
Contributor Author

sorry branch checkout mixed, I will checkout an clean branch, and pr again

@naughtyGitCat naughtyGitCat deleted the fix_duplicate_connPoolStats_replicaSets branch August 5, 2025 03:14
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