-
Notifications
You must be signed in to change notification settings - Fork 648
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
fix lint #1680
fix lint #1680
Conversation
Codecov ReportBase: 50.70% // Head: 50.70% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #1680 +/- ##
========================================
Coverage 50.70% 50.70%
========================================
Files 324 324
Lines 12255 12255
Branches 1817 1817
========================================
Hits 6214 6214
Misses 5607 5607
Partials 434 434
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
You may also make a new pr to fix master branch |
link #1685 |
May refer to open-mmlab/mmeval#86 to resolve isort lint issue |
2069f0d
to
6b7b602
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.
LGTM
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist