Repository navigation
gremlin, qt5_graphics: a stopped parse now raises KeyboardInterrupt - #4760
Merged
Merged
Conversation
Since LinuxCNC#4636 the gcodemodule lets the callback's own exception propagate instead of masking it as RuntimeError. An (AXIS,stop) program raises KeyboardInterrupt, which escaped these Exception-only handlers on file load. AXIS already catches it. Refs LinuxCNC#2492.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #2492, follow-up to #4636.
With the real exception now propagating, an (AXIS,stop) program raises KeyboardInterrupt out of gcode.parse. The file-load handlers in gremlin.py (gmoccapy) and qt5_graphics.py (qtvcp) caught only Exception, so a stopped preview escaped and aborted the load. Catch KeyboardInterrupt as well, same handling as before. AXIS already caught it (axis.py:1292).