Author Topic: Qube! 6.7-1c WranglerView patch release is available  (Read 1210 times)

jburk

  • Administrator
  • *****
  • Posts: 485
Qube! 6.7-1c WranglerView patch release is available
« on: September 06, 2015, 09:58:00 PM »
A 6.7-1c patch release is now available for the Qube 6.7-x WranglerView.  This is a recommended patch release for all customers running any version of Qube v6.7, and can be installed directly on top of 6.7-0 and 6.7-1.

This patch is available for all supported operating systems, and contains an optimization which delays the loading of the job logs when a job is selected.

For those using the Qube Installer utility, the 6.7-1 manifest file has been updated.  If you are using version 2.1-0 or later of the QubeInstaller installer utility, it, will auto-detect if a manifest has a newer version and offer to download it.

Or you can download the patched version directly at: http://repo.pipelinefx.com/downloads/pub/qubegui/current/

Full release notes are available on our documentation site: http://docs.pipelinefx.com/display/QUBE/WranglerView+6.7-1+Release+Notes

-------------------------------------------------------------------------------
6.7-1c FEATURES AND FIXES
-------------------------------------------------------------------------------
WranglerView 6.7-1c contains an optimization that delays the loading of the job
logs when a job is selected unless the stdout/stderr log pane is showing. This
allows the user to scroll through the job listing much quicker, and only when
the log's panel is displayed in the right-hand pane are the job's logs loaded.

It also provides for better functionality for the (new since 6.7-0) "Log Size"
column in the job and instance listings; when you select a job the log sizes
for the job are calculated and displayed. If the log's panel is not visible,
this allows the user to decide whether they wish to actually attempt to load
the logs by displaying the log panel.

=========================
Fixes
=========================

==== CL 14482 ====
@FIX: modifying a job can result in the job's environment being cleared out entirely

==== CL 14454 ====
@FIX: performance tweak: don't fetch the job logs when selecting the job if the
log pane is not shown