Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.

Conversation

@sboeuf
Copy link
Contributor

@sboeuf sboeuf commented Jun 27, 2017

In case the call to SendCtlMessage() was returning an error, the
response object was nil, but it was used anyway.
This patch makes sure we are not using the response handler in
case we got an error.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 74.696% when pulling 036fc97 on sboeuf/fix_segfault into cf19e79 on master.

@dlespiau
Copy link
Contributor

dlespiau commented Jun 27, 2017

lgtm

Approved with PullApprove Approved with PullApprove

@sboeuf
Copy link
Contributor Author

sboeuf commented Jun 27, 2017

@dlespiau Am I supposed to fix those issues ??? I don't think it is related to my PR. Have you already got such issues with gometalinter (megacheck) ?

@dlespiau
Copy link
Contributor

dlespiau commented Jun 27, 2017

gometalinter has added a checker and we fail on those new checks.

@sboeuf
Copy link
Contributor Author

sboeuf commented Jun 27, 2017

@dlespiau Ok thanks for the confirmation. What do you want to do about that ? Removing this checker ?

@sboeuf sboeuf force-pushed the sboeuf/fix_segfault branch from 036fc97 to dae0de3 Compare June 27, 2017 22:57
In case the call to SendCtlMessage() was returning an error, the
response object was nil, but it was used anyway.
This patch makes sure we are not using the response handler in
case we got an error.

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
@sboeuf sboeuf force-pushed the sboeuf/fix_segfault branch from dae0de3 to e24e09b Compare June 27, 2017 23:00
@coveralls
Copy link

coveralls commented Jun 27, 2017

Coverage Status

Coverage decreased (-0.1%) to 74.696% when pulling e24e09b on sboeuf/fix_segfault into cf19e79 on master.

@sboeuf
Copy link
Contributor Author

sboeuf commented Jun 27, 2017

@dlespiau I have disabled megacheck. It's all green. Let me know if you think we should fix megacheck issues instead, but personally I think this PR should not be affected by this issue. We can still re-enable + fix megacheck in a follow up PR.
Merge it if that's fine for you ;)

@dlespiau
Copy link
Contributor

yes, we should fix the few issues (dead code) found by megacheck, that can be a different PR though.

@dlespiau dlespiau merged commit 7cb0341 into master Jun 28, 2017
@sboeuf sboeuf deleted the sboeuf/fix_segfault branch July 19, 2017 19:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants