Skip to content
This repository has been archived by the owner on Apr 22, 2021. It is now read-only.

v6.1763.0
Compare
Choose a tag to compare
@luguina luguina released this 21 Jun 10:45
· 123 commits to master since this release
v6.1763.0
2b2e5cc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

We have been working hard this week and this release is packed with fixes for some annoying app bugs as well as some new features.

Changelog since v6.1747.0:

Feat: if in the last release we fixed the messy download messages in text UI, now is the turn of the rendering process. This version shows the rendering process in a nice single-line progress bar in text UI mode.
Fix: to prevent the creation of zombie frames, when the renderer is killed it sends the allocated frame number back to the server to ensure that is reset and reassigned to another user.
Fix: the killing process sent by the server might create a kill-loop in the client if the job is not in the rendering phase but being downloaded.
Fix: the app was sending a null MimeType when sending a file to the server.
Fix: an error response from the server to the app request was not correctly sent to the server.
Fix: some calls to deprecated methods updated and some extra minor fixes.
Fix: when -compute-method is specified as an argument, it doesn't overwrite the value of the configuration file.
Fix: when an HTTP413 error occurs (that's the case when a rendered frame size if too large), the app keeps trying up to five times (but there is no way to circumvent the error unless the server configuration is updated).
Fix: the -renderbucket-size option is not applied if the app runs in an environment with no configuration file.
Fix: some old bugs and internal improvements in the logs and error management.

Assets 2
Loading