-
Notifications
You must be signed in to change notification settings - Fork 638
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
bugfix: walk function exit incorrectly #229
Conversation
BTW, maybe the ci test is some insufficient. We had better to improve the ci test (maybe circleci is nice) , to make sure being able to check the main functionalities. |
case nil: | ||
return nil, fmt.Errorf("%s: config not found", cpath) | ||
case errEOW: | ||
// found, continue below |
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.
remove this comment
two small comments then lgtm |
@jonboulle modified. PTAL, thanks. |
Signed-off-by: xiekeyang <xiekeyang@huawei.com>
On Wed, Aug 31, 2016 at 04:21:21AM -0700, xiekeyang wrote:
Some thoughts on testing here 1. I'm happy to write up integration |
Sorry it is my previous fault by #201 .
That patch leads the walk function exit incorrectly.
it is because that function
filepatch.Walk()
must not return error when meeting path mismatch error. Instead it should return nil. And the checking should be done in the end of walk.Here I fix the bug in this patch. I retrieve old assertion block. I've run
create
,validate
andunpack
command according to the command manual successfully.I will improve the mechanism gracefully.
PTAL, Thanks lots!
Signed-off-by: xiekeyang xiekeyang@huawei.com