-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[MXNET-1291] solve pylint errors in examples with issue no.12205 #13938
Conversation
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.
Branch has a merge conflict. Please resolve. Thanks a lot for this really big contribution! Great work!
@ChaiBapchya , |
Thanks a lot for your contribution. Could you find out why our sanity check did not catch this? Also, it seems like you are deleting a bunch of files |
Hi @marcoabreu Sorry, I don’t know what you want to tell me. Can you elaborate on that? Many thanks, |
@@ -1,100 +0,0 @@ | |||
# Urban Sounds Classification in MXNet Gluon |
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.
Why is this removed?
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.
Sorry, I don't know anything about this file, I just accept this change which made by communities before committing my branch.
@cchung100m - Thank you for your contributions and solving pylint issues in examples. I have left few comments. |
We don't test examples in CI :( |
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.
Please update out pylint pipeline to ensure all these points are caught in future
@cchung100m are the files in example/autoencoder being deleted? @marcoabreu we might have to wait for the fixes to all the lint errors (in examples folder) to be merged, before we enable the check in CI |
@cchung100m Could you please look into the comments above? |
@vandanavk @ankkhedia I will solve the conflict files and rebase this branch ASAP. |
d0bf224
to
61a70dc
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
@marcoabreu @ChaiBapchya @sandeep-krishnamurthy is this PR good to go? |
I will re-check the conflicting files ASAP. |
Unify the style of comments
Unify the style of comments
Correct the misuse of tenses from preprocessed to preprocesses
1. Add reference of the paper in comment. 2. Change the comments from "Run training to CapsNet" to "Perform CapsNet training"
Remove a redundant noun 'dataset'
Align the style of comment from single-line comment to multi-line comment
Correct the misdescription comment of LogSoftmax class from 'softmax loss function' to 'logarithm of softmax'
Remove the '#' symbol in the header comment
a3bcf9f
to
ce04d77
Compare
update out pylint pipeline to ensure all these points are caught
Hi @szha @marcoabreu @ChaiBapchya @sandeep-krishnamurthy I complete the rebase and re-test on this branch, I will appreciate if you can help to review/merge, again, thanks :) |
…che#13938) * Unify the style of comments Unify the style of comments * Unify the style of comments Unify the style of comments * Correct the misuse of tenses Correct the misuse of tenses from preprocessed to preprocesses * Enhance the comment for better description 1. Add reference of the paper in comment. 2. Change the comments from "Run training to CapsNet" to "Perform CapsNet training" * Remove a redundant noun Remove a redundant noun 'dataset' * Unify the style of comments Align the style of comment from single-line comment to multi-line comment * Correct the misdescription of LogSoftmax class Correct the misdescription comment of LogSoftmax class from 'softmax loss function' to 'logarithm of softmax' * Remove the '#' symbol in the header comment Remove the '#' symbol in the header comment * update the result of pylint pipeline update out pylint pipeline to ensure all these points are caught * retrigger the CI
) * Unify the style of comments Unify the style of comments * Unify the style of comments Unify the style of comments * Correct the misuse of tenses Correct the misuse of tenses from preprocessed to preprocesses * Enhance the comment for better description 1. Add reference of the paper in comment. 2. Change the comments from "Run training to CapsNet" to "Perform CapsNet training" * Remove a redundant noun Remove a redundant noun 'dataset' * Unify the style of comments Align the style of comment from single-line comment to multi-line comment * Correct the misdescription of LogSoftmax class Correct the misdescription comment of LogSoftmax class from 'softmax loss function' to 'logarithm of softmax' * Remove the '#' symbol in the header comment Remove the '#' symbol in the header comment * update the result of pylint pipeline update out pylint pipeline to ensure all these points are caught * retrigger the CI
…che#13938) * Unify the style of comments Unify the style of comments * Unify the style of comments Unify the style of comments * Correct the misuse of tenses Correct the misuse of tenses from preprocessed to preprocesses * Enhance the comment for better description 1. Add reference of the paper in comment. 2. Change the comments from "Run training to CapsNet" to "Perform CapsNet training" * Remove a redundant noun Remove a redundant noun 'dataset' * Unify the style of comments Align the style of comment from single-line comment to multi-line comment * Correct the misdescription of LogSoftmax class Correct the misdescription comment of LogSoftmax class from 'softmax loss function' to 'logarithm of softmax' * Remove the '#' symbol in the header comment Remove the '#' symbol in the header comment * update the result of pylint pipeline update out pylint pipeline to ensure all these points are caught * retrigger the CI
Description
this is the part 3 of the changes to solve pylint errors in examples with issue #12205
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.
Changes
Comments