-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Linter and formatting fixes #2995
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2995 +/- ##
==========================================
+ Coverage 76.90% 76.99% +0.08%
==========================================
Files 228 228
Lines 17050 17050
==========================================
+ Hits 13113 13128 +15
+ Misses 3090 3079 -11
+ Partials 847 843 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 4 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
3c2733c
to
f577879
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This includes changes from the other PRs, so I ignored those, but the two top-most commits LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like that we are breaking the graphs in ramping_vus.go. But if you want you can:
- skip that file for now
- fix them in a separate PR - but open an issue for that.
I am approving this in case you go with 2
lib/executor/ramping_vus.go
Outdated
// 3| *************** | ||
// 2| ***************** | ||
// 1| ******************* | ||
// 0------------------------> time(s) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// 0------------------------> time(s) | |
// 0+-----------------------> time(s) |
Wouldn't that be better 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not really, it might confuse someone
The only exceptions were some `go generate`d code.
I got annoyed by some of the many linter errors we have unresolved. Some of them like the loopclosure ones might even hide other problems, so I decided it's time to fix them.
I'll try to do fixes for various unrelated issues commit by commit. To reduce merge conflicts, this is built on top of #2960.