This allows the user to only show logs from a specific date span.
For that two date picker and a 'Update' button were added to the
header bar.
For the until date we assume always 23:59:59 o'clock, as witouth
a specific time journalctl assumes 00:00 which would result in an
empty log if we only wanted to look at todays log.
As the LogView is shared with others (e.g. ceph log) use an boolean
variable to set if we want to show those date pickers)
Fixes timeout when the user has a long uptime and or persistent logs
allow the since/until parameters which journalctl understands
We use a really simple regex to check a valit date (time) stamp.
This can be done as this API call gets mainly used by the GUI where
we have full controll over what we send and additional journalctl
has already a good timestamp parser which can handle that.
fixes:
* update deprecated field
* move static configuration to class definition
* change applyIf to apply
* change system report handler to pass a function to
check_command (instead of the result of showReport)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
looks like ExtJS is not automatically flattening the array anymore
and items in a multidimensionnal array are not displayed with ExtJS6
lxc/Config.js is still commented because we haven't reached this part
in the upgrade, but fixing there too
This takes a bit of screensize, but is fine as long as the browser
horizontal screen size is at least 1280 px ( 92 % of desktop users in 2016
according to StatsCounter)
Still usable for the remaining small displays, but horizontal scrolling
is needed for grids with a lot of columns.
Moving the sub tabs to the top left provides a minor usability
improvement as all controls are now grouped together in the same
screen region.
we used an empty value for the Key-Value ComboBox for defaults.
With extjs6, if the idProperty of a model is empty, they generate
a name for it, which breaks our logic for submitting
(currently we checked if this is empty, and send a delete command
to our api)
instead, we use the value 'default' and check for it when we submit
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
includes the following fixes:
* remove all code related to the old java applet vnc client
(we do not use this anymore)
* move static configuration to class definition
* use Ext.ux.IFrame instead of widget.uxiframe (to be consistent)
* change listener from show to activate (for browser refresh)
* change deprecated autoScroll to scrollable
* remove novnc option from openVNCViewer function,
since we do not need this option anymore
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this fixes two problems:
* we were loading the store before the parent ComboGrid class could put
a listener on the load event
* displayField must now be set in class body, take opportunity to move out
what we can of the mega initComponent()
this two fixes allow the HA GroupEdit Window to properly display the
existing members of a HA Group when editing group membership
Tabpanel reload -> send 'show' event -> reload child panel store
do not work with ExtJS6
but
Tabpanel reload -> reload child panel -> child send 'show' event ->
reload a grid store in the panel still works
so we don't blindly replace the 'show' events everywhere but only
when the event was expected by a direct child of a tabpanel
this also fixes the problem that the method
Ext.ComponentQuery.query() was outputting a warning
since it did not know if it should perform a lookup
for a class name or a xtype
fixes the LogView (for Tasks and Syslog) including:
moving static configuration to class definition
changing deprecated bodyStyle: padding to bodyPadding
removing chrome scrolltop hack (does work properly now, and hack
did not work anymore)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
fixes include:
move static configuration to class declaration
use Ext.create instead of new for reload_task
use store.reload(), because store.filter() triggers no reload with
activated
remove store.guaranteeRange hack for infinite grid (works properly now)
since buffered: true is deprecated, use a BufferedStore instead
remove verticalScrollerType and invalidateScrollerOnRefresh
since this does not exist anymore in extjs6
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This reverts commit c8e0699d5d.
Without using an idProperty in the KeyValue model, the id of each
store item is autogenerated, and the DiffStore always recreate the whole
store content every second instead of updating the fields where values
have changed. Recreating the whole store content makes the
Node Summary View flicker, as the order of items in the store change
after each reload.
Testing shows that reversing this commit do not break anything else.
