OctoPrint.orgNew release candidate: 1.3.5rc2
This second release candidate of the 1.3.5 release fixes a few regressions and bugs in new/improved functionality that were found and reported in 1.3.5rc1:
- #2033 - Temperature tab: Fix for legend in graph not updating with current values on mouse over.
- #2033 - Temperature tab: Fix for new temperature inputs not fitting on one line in Firefox.
- #2033 - Temperature tab & GCODE viewer: Fix for available tools (and offsets) not properly updating on change of printer profile.
- #2033 - Wizard: Fix sorting of required wizards not properly handling non-ASCII unicode.
- #2035 - Fix an issue of the server not starting up if there’s a file in the analysis backlog. The reason for this is that spawning a new process while the intermediary server is active causes the server port to be blocked (this is due to how subprocessing works by default), in turn leading to an error on startup since the port cannot be bound by the actual server. Since the GCODE analysis takes now place in its own subprocess and hence triggers this problem, it had to be moved until after the actual server has already started up to avoid this problem.
- Wizard: Fix
onWizardPreventSettingsRefreshDialogcallback invocation. - Corewizard plugin: Fix
firstrunonlywizards (e.g. for printer profile configuration) being displayed again if any of the sub wizards (e.g. for the online check opt-in and configuration) is active.
If you are tracking the “Maintenance RC” release channel, you should soon get an update notification just like you are used to from stable releases.
If you are not interested in helping to test release candidates, just ignore this post, 1.3.5 stable will hit your instance via the usual way once it’s ready :)
You can find the full changelog and release notes as usual on Github.
Please provide feedback on this RC. For general feedback you can use this ticket on the tracker. Note that the information that everything works fine for you is also valuable feedback :). For bug reports please follow “How to file a bug report”.
Depending on how the feedback for this release candidate turns out, I’ll either look into releasing 1.3.5 or fix any observed regressions and push out a second release candidate once I get back from some much needed time off.
