-
Notifications
You must be signed in to change notification settings - Fork 9
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
Porting a know issues from the k6 repository #18
Comments
Thanks @olegbespalov (and hope you and the rest of the team are well!). Porting the issues to this repository makes sense to me. Would you concur @LeonAdato ? We'll be watching for grafana/k6#3849 to remove StatsD from k6. |
Ported and merged into the 0.2.0 version. |
Hi @javaducky @LeonAdato ! Thanks a lot for taking care! @javaducky, we're good! Hope everything is good too on your side @LeonAdato, out of curiosity, where were the issues ported? I can't see them https://github.com/LeonAdato/xk6-output-statsd/issues. I'm asking for details to mention the ported issue while I'm closing issues in k6's repository for better visibility. |
I mis-spoke. I just updated the repo based on the latest K6 which fixed a bunch of lingering issues. I'll get those open issues ported over in the next few days. |
@LeonAdato, I see that you've commented on each individual issue; I believe you intended to ask issues' authors to port them (unfortunately, there is no way to transfer issues between GH organizations). But since we're not sure if all the authors track the issues, and if that's fine by you, I could open them and link by myself. Does that sound good? |
Sounds great! |
What?
There are a couple of opened issues in the k6 repository related to the StatsD output:
check
metrics in StatsD output configurable grafana/k6#2470Since we likely won't work on them, keeping in mind the grafana/k6#2982 it's good to port (not sure of transfer could work) to this repository since currently this is the primarily recommended repository for the k6's statsd output.
@LeonAdato, do you think that makes sense? If so, I could port the mentioned issues to the repo and close them in the k6 reposory
The text was updated successfully, but these errors were encountered: