3D-printing/klipper
1
0
Fork 0
mirror of https://github.com/Klipper3d/klipper.git synced 2025-07-07 23:17:37 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

gcode: Don't dump the message log directly from set_printer_ready()

Browse source 
The set_printer_ready() method can be called from a background thread.
Have the main Printer class call a new dump_debug() method in the main
thread on a shutdown event.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2016-11-30 19:05:25 -05:00
parent 17dcb42752
commit 5ebe8ce025
2 changed files with 12 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

11
klippy/gcode.py
View file

@ -72,12 +72,11 @@ class GCodeParser:
self.build_handlers()
if is_ready and self.is_fileinput and self.fd_handle is None:
self.fd_handle = self.reactor.register_fd(self.fd, self.process_data)
if not is_ready:
logging.info("Dumping gcode input %d blocks" % (
len(self.input_log),))
# XXX - read from self.input_log is not thread safe
for eventtime, data in self.input_log:
logging.info("Read %f: %s" % (eventtime, repr(data)))
def dump_debug(self):
logging.info("Dumping gcode input %d blocks" % (
len(self.input_log),))
for eventtime, data in self.input_log:
logging.info("Read %f: %s" % (eventtime, repr(data)))
# Parse input into commands
args_r = re.compile('([a-zA-Z*])')
def process_commands(self, eventtime):