Skip to content
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

"continue-on-error" has no effect #11

Closed
GoogleCodeExporter opened this issue Jun 11, 2015 · 2 comments
Closed

"continue-on-error" has no effect #11

GoogleCodeExporter opened this issue Jun 11, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Start the server and client
2. Send a edit-config operation with error-option set to "continue-on-error" 
and three configurations (that will call three callbacks) where the second 
callback return EXIT_FAILURE.

What is the expected output? What do you see instead?
I expected the three callbacks should be called but the behaviour is identical 
to "stop-on-error" error-option (just the first and second callbacks are 
called).

What version of the product are you using? On what operating system?
I am using the branch master commit 3f33930cd3a8 (Thu Sep 5 13:50:40 2013 
+0200) on a Gentoo Linux.

Original issue reported on code.google.com by paulo.zu...@asga.com.br on 6 Sep 2013 at 4:40

@GoogleCodeExporter
Copy link
Author

Original comment by rkre...@cesnet.cz on 10 Sep 2013 at 6:58

@GoogleCodeExporter
Copy link
Author

Original comment by mv6...@gmail.com on 11 Sep 2013 at 8:30

  • Changed state: Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant