M105 timer can cause an M105 cascade on long command-ok-cycles

[foosel]

Problem

If the user has configured a long comm timeout (> 5s) or a long running command, the M105 polling timer will enqueue multiple M105 commands that then will cascade through comms once the timeout gets resolved/the long running command ends.

The problem is that the polling timer doesn't write into the send queue (which is typed) but into the command queue which then in turn gets written into the send queue, but isn't typed itself.

Solution

Make the command queue a typed queue as well.

[foosel]

For testing:

• Make sure M800 is not configured as a long running command

• Connect to virtual printer

• Upload a file with the contents

  M117 M105 cascade test start
  M800
  M117 M105 cascade test end
  

• Send !!DEBUG:sleep_after_next M800 30 to printer

• Print file

Should log several times in octoprint.log that the temperature type was already in the command queue, will only send one additional M105 if a timeout is encountered.