debugging

About a week ago I got a new bug report on OctoPrint’s issue tracker: GCode Viewer Visualisation Problem The problem The visualisation in GCode viewer ist not correct. The print is OK. See gcode file (zip) on Layer 43 to 47 and 49 And screenshot You already saw the included screenshot, and it shows that there was a spike being visualized in the GCode Viewer that wasn’t actually there. My first attempt at reproduction failed spectacularly – the file looked exactly like it was supposed to....

The original version of this post was published as a Twitter thread on March 23rd 2020. I figured I should give it a more permanent home here since IMHO it was a quite fun story. Since everyone can use some entertainment right now, how about a battle story on how a year ago I spent almost two weeks trying to wrap my head around a really weird issue of a lagging GCODE viewer and overall print progress reporting in OctoPrint and finally figuring it out?...