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

When a command returns no result, the next command may be popped and not sent #210

Closed
jathanism opened this Issue Apr 11, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@jathanism
Member

jathanism commented Apr 11, 2015

See:
https://gist.github.com/johnfzc/b36a99ba573f7f6670c0

In this problem, reload cancel is executed, returns a prompt immediately and show ver is popped off the stack before reload cancel is even sent.

This seems like a bug that may be caused by commands that return no data?

The command show ver should not be popped until reload cancel returns a prompt!

CC @johnfzc

@jathanism

This comment has been minimized.

Member

jathanism commented Apr 12, 2015

The device for this particular case is a Cisco ISR 819.

@jathanism jathanism added the bug label Apr 13, 2015

@jathanism jathanism closed this in e9d936a May 7, 2015

jathanism added a commit that referenced this issue May 7, 2015

Merge pull request #215 from jathanism/issue-210
Fix #210: Bugfix when buffered command results weren't properly cleared.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment