A new 6.3.1 maintenance release is now available for the QubeGUI v6.3. This is a recommended release for all customers running QubeGUI v6.3.
Below is a list of the fixes and enhancements.
================================================
6.3.1 FEATURES AND FIXES
-------------------------
=========================
New features
=========================
@NEW: modifying the subjob count will retry or retire subjobs to bring the
running subjob count up to the new subjob count; if the job has 10 subjobs, 6
of which are complete/failed/killed, and it's modified to 15 subjobs, the 6
done subjobs will be automatically retried. If the subjob count is modified to
be less than the number of running/pending/blocked subjobs, subjobs are
retired, pending/blocked before running.
@NEW: add in sanity check on upper limit for number of subjobs during
GUI-initiated job modification, eliminate user error which could overload the
supervisor. Upper limit is the lesser of (the agenda size + 10%) or (total
number of active slots in the farm)
=========================
Changes in behavior
=========================
@CHANGE: enable the "job log directory" context menu items on clients that can
access mounted job log dirs.
@CHANGE: modifying the GUI to run under "console" mode under Windows, so that
it's messages may be redirected and captured.
@CHANGE: use fixed-width font for stdout/stderr logpanes when locale is set to
en_US, to avoid errors when displaying Japanese and other double-byte
characters
@CHANGE: better sorting of subjob candidates for retire/retry. Desired
behavior is to keep the active and running subjobs near the top of the list
(lower subjob ID's), and the completed/retired ones at the bottom of the list.
Retry lower id's before higher id's, retire higher id's before lower ones.
=========================
Fixes
=========================
@FIX: added code to setup.py script to properly include the new AppUI files.
@FIX: fixed issue where the right-click menu item callbacks did not work in the
new Dependency Graph in many cases. Turns out that the callbacks were not
being registered in some cases because of the new, dynamic way that the
jobLayout.py was loading jobDependencyGraph
module.
@FIX: add missing qbColors.py module, wasn't being distributed with the python
source.
@FIX: Better error checking for Cinema4D in-app installer.
@FIX: added 'AESend Failed' to the regex_errors, will always mark the frame as
failed if found, even when aerender crashes and exits with code 0
