New release candidate: 1.4.0rc4

As this is the first blog post in 2020, first of all: Happy New Year to all of you! 🥳

This fourth RC of 1.4.0 fixes some regressions and issues in the new functionality observed with the prior RCs:

Improvements

  • #3400: Add ClientAuthed event to allow plugins to react to a client logging in on the socket
  • #3418: Add API endpoint /api/currentuser to retrieve permissions & groups of currently logged in user
  • #3425: Change method of prompting for log in for guests without permissions
  • Add documentation for /api/access endpoints and update existing documentation with permission information

Bug fixes

  • #3396: Fix timelapse listing not properly refreshing on rendering a new timelapse
  • #3398: Fix checking of needs not being picky enough
  • #3409: Fix timelapse rendering progress reporting under Python 3
  • #3419: Fix permission modelling for PRINT permission
  • #3425: Fix permissions for /api/settings
  • #3426: Fix “Remember me” checkbox on forced login screen
  • #3428: Fix plugin installation and other CLI interactions under Python 2 and 3 and Windows
  • #3431: Fix folder writability test under Python 3
  • Fix endless loading issue when page is cached by browser in a tab and the server is down

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, and also @CapnBry and @fieldOfView for their fixes!

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 “Maintenance RCs” release channel in this guide if not already done (also linked below). This is the first RC of the 1.4.0 series that is also available on the “Maintenance RCs” channel, the prior RCs were only pushed to the “Devel RCs” release channel. If you are tracking “Devel RCs” you will also get an update notification for this, since “Devel RCs” also tracks releases on the “Maintenance RCs” and “Stable” channels, so no need to switch.

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.

Thanks!

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.

Links


This is a companion discussion topic for the original entry at https://octoprint.org/blog/2020/01/28/new-release-candidate-1.4.0rc4/
3 Likes

I'm a new user of octoprint ...

Don't know much about linux,and it is a pain to write commands in command line,specialy with https or similar,which looks like a sausage ...

Would be nice to make a update script,and implement it in system ...

OctoPrint already has that:

2 Likes

Found it ...

Werry nice,thx you

If you have a huge aversion against the command line however I'd advice against using a Release Candidate. As posted, things can go wrong with candidates and worst case you then might have to resort to the command line to revert to a working state.