-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
controller check error #599
controller check error #599
Conversation
Squash commits please. |
e2c1348
to
ee0633b
Compare
/retest |
/lgtm leave approve to @sids-b @edisonxiang |
I didn't understand why the build failed. (Here is a success travis build on the same changes: https://travis-ci.org/subpathdev/kubeedge ) |
/retest |
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
@subpathdev , you need to make changes in the UT's as this err return would not be there in the code and it will continue to execute |
The overall change looks good to me though |
@@ -330,6 +330,24 @@ func TestDTController_distributeMsg(t *testing.T) { | |||
} | |||
}) | |||
} | |||
|
|||
//Sucess Case |
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.
nit: s/Sucess/Successful
LGTM Overall. Can merge this PR once @m1093782566 review comments fixed |
Please squash the commits. |
* create test case distributeMsg chan no found * create test case distributeMsg sucessfull
c4b1a00
to
336014d
Compare
/approve THANKS! |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
In this line we can see, that the CommTo return nil or an error. https://github.com/kubeedge/kubeedge/blob/master/edge/pkg/devicetwin/dtcontext/dtcontext.go#L71
In this PR I take this error and create an error in function distributeMsg (
kubeedge/edge/pkg/devicetwin/dtcontroller.go
Line 116 in 98c2762
kubeedge/edge/pkg/devicetwin/dtcontroller.go
Line 79 in 98c2762
In my opinion we should check if an error occur or not when it is possible. This will also increase the possibility to debug the program.
Which issue(s) this PR fixes:
Special notes for your reviewer: