This second RC of 1.3.12 fixes some regressions observed with the first one:
- #3348 (regression) - Fix an issue with the warning decorator trying to access non existing fields on instance methods, causing trouble with plugins still using deprecated settings methods.
- #3349 (regression) - Fix an issue with unset optional headers on file uploads, causing uploads to fail in case of a missing content type or file name, e.g. from Cura.
- #3350 (regression) - Appkeys: Fix wrong data type for newly generated keys under Python 3, causing the keys to not match and the plugin to not properly work.
- #3354 (regression - Fix timelapse start not triggering correctly due to using a no longer existing field in the PrintStarted payload.
- #3357 (regression) - Fix local autologin no longer working due to a logic change introduced by the new granular permission system.
- #3361 (regression) - Fix an exception raised when attempting to log out the single admin user if access control is disabled.
- #3362 (regression) - Fix escaping of placeholders in some error notifications.
- #3363 (regression) - Gracefully handle missing subfolders on file list nodes.
- #3364 (regression) - Make sure
datais actually set.
- Appkeys: Fix a deprecation warning. (regression)
The heads-up regarding Plugins and Python 3 from 1.4.0rc1 still applies.
You can find the full changelog and release notes as usual on Github.
Special thanks to everyone who contributed to this release candidate and provided full, analyzable bug reports!
As the past RCs have shown me that a lot of people appear to be unaware of this: Please do not install this RC if you expect a fully stable version. It is not a stable release, it is a release candidate, and of the next big release to boot: severe bugs may occur, and they might be bad enough that they make a manual downgrade to an earlier version necessary - maybe even from the command line.
You should feel comfortable with and capable of possibly having to do this before installing an RC.
If you want to and can help test this release candidate, you can find information on how to switch to the “Devel RCs” release channel in this guide if not already done (also linked below). Please note that contrary to maintenance releases this RC is not available on the “Maintenance RCs” release channel so if you are tracking that you’ll need to switch. The reason is that RCs of big releases might be more unstable at first than pure maintenance releases due to newly introduced features or very heavy refactorings, so I’m splitting these between two release channels. Note that when tracking “Devel RCs” you’ll get all releases from “Stable” and “Maintenance RCs” as well.
Please provide feedback on this RC. For general feedback you can use this ticket on the tracker. The information that everything works fine for you is also valuable feedback 😄. For bug reports please follow “How to file a bug report” - I need logs and reproduction steps to fix issues, not just the information that something doesn’t work so make sure to fill out all fields of the issue template.
Depending on the feedback regarding this version I’ll look into fixing any observed regressions and bugs and pushing out a follow-up version as soon as possible and necessary.
This is a companion discussion topic for the original entry at https://octoprint.org/blog/2019/12/02/new-release-candidate-1.4.0rc2/