Octoprint: [RC Feedback] Feedback on the 1.3.12rc3 Release Candidate

[foosel]

Please provide general feedback on your experience with the 1.3.12rc3 Release Candidate here. An "All is working fine" is valuable feedback as well, because it tells me that people in fact are testing the RC and just not finding any problems. Thanks :)

If you run into any obvious bugs not yet listed below the following line, please open a new ticket and follow "How to file a bug report".

---

Currently known issues

Unreproduced issues

Unreproduced and information for further analysis missing

Unrelated third party plugin issues

• ❌ #3281 - WebCam Tab plugin (third party) is not working after installing 1.3.12rc2 - works fine on its own but breaks with current version of dashboard plugin, regardless of OctoPrint version (reproduced on 1.3.11 with current plugin versions, doesn't reproduce on 1.3.11 with Dashboard 1.1.0 w/o webcam support)

[b-morgan]

Updated from 1.3.12rc2 to 1.3.12rc3 (on OctoPi 16.0) successfully.

[JohnOCFII]

I recently wiped my OctoPi 0.13.0 and put down a fresh copy of OctoPi 0.16.0. (I made a backup, but forgot to upload it to my desktop -- doh!)

So - Clean OctoPi with just OctoSlack 1.9.1, Telegram Notifications 1.5.0 and M73 ETA Override 1.0.1 plugins on OctoPrint 1.3.12rc3 is working well. I tested: GCode Viewer, Terminal, Time-lapse, uploading and starting a print. This is connected to a Prusa MK3S with MMU2S. One of the prints I did was launch a single material MMU2S print. That also worked fine.

[schnello]

Update from RC2 to RC3 done, server is online and all (incl some prints) works fine.

[foosel]

Sounds very good all in all so far. Currently fighting off the flu, once I've succeeded in that I'll push out 1.3.12, unless something comes up in the meantime.

[rknobbe]

The Cura Octoprint Connection plugin (on the Cura side) seems to not work anymore. Not sure if the problem is on the Cura side or the Octoprint side. I get an "octoprint is busy, unable to start a new job" error from Cura. I'll keep researching.

[foosel]

The Cura Octoprint Connection plugin (on the Cura side) seems to not work anymore.

Can you be more specific, e.g. share logs? Also pinging @fieldOfView just in case...

[fieldOfView]

I likely won’t have time to look in to this until monday.

[fieldOfView]

@rknobbe, I cannot reproduce this issue. What version of Cura, and what version of the plugin are you using?

[foosel]

Another update on the plans for the stable release. I'm back on my feet but I'll leave for Berlin tomorrow to attend & participate in PyConDE - it doesn't feel like a good idea to push out a new stable release in a week I'm spending traveling, with no access to my usual zoo of test hardware, so I'll push that back until next week when I'm back in my home office.

[gcnix]

The Cura Octoprint Connection plugin (on the Cura side) seems to not work anymore.

Can you be more specific, e.g. share logs? Also pinging @fieldOfView just in case...

I have the same issue with 1.3.11. I found that once I connect Octoprint with printer ("verbinden"), it takes a few seconds for Cura to detect the printer being available. I then see an offer in Cura to queue the job, which I decline and with the next attempt it works. I believe it is only a timing issue.

[arhi]

works flawlessly for me, printed bunch of stuff on rc3 on 2 printers (one smoothieware based, other marlin based) no issues what so ever

[louispires]

This version was working great until this morning when I had my first ever error between Firmware and OctoPrint: https://github.com/foosel/OctoPrint/issues/3303

[foosel]

If you are wondering what's up here and why this is not yet rolled out as stable - conference epidemic got to me. I am beyond frustrated, I can tell you that.

[foosel]

1.3.12 has been released