VM scheduled actions via Sunstone 3/3: Unexpected behavior on VMs older than a month when clicked

Description
(bug 3/3)
Not sure how to name the blue "thing" next to the green "Add Action" button but it has a lot of troubles...
When you click on it two actions are defined without a warning or confirmation - just committed to the core...

To Reproduce
Perform the following on a VM that was instantiated more than a month ago:

Select VM -> Actions tab
Click the blue clock-like thing
two actions are created one with wrong name "suspense", but the second one is entirely valid "terminate" action.
Check the VM state after max 30 seconds... And the VM is Terminated

Expected behavior
Not sure what I expect here:

There should be a warning/confirmation dialog before committing the scheduled actions?
The time should be 2w/4w from the moment when the action is applied, not now?
What is the purpose of this button anyway? Should it exists at all?

Details

Affected Component: [Sunstone/Scheduler]
Hypervisor: [KVM]
Version: [5.12.6]

Additional context
Missing a warning even every operator could click there and terminate a production VM in a glipse...
Please note that I totally agree that this case is hard to catch with common CI/automated testing because usually the testing VMs are not older enough to catch this. I had the chance to play with a staging environment where i have older VMs.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@rsmontero, @tinova, I think this is very important if not critical...

Hello @atodorov-storpool,
Just FYI, we call charters to "the blue thing". You can find the docs here: http://docs.opennebula.io/5.12/operation/vm_management/vm_instances.html?highlight=charters#vm-charter
Regarding the bugs you mentioned:

The suspense instead of suspend typo will be fixed in master.
We agree with you, that a warning message requiring a confirmation for the user before creating the actions will be more than useful.
The VM shouldn't be terminated after 30s. Could you send us the XML of the VM to take a look at the schedule actions defined. Also it would be useful to know the aprox time when you clicked the button.

Sure @christian7007. here it is
Clicked on the charters in ~17:38:25
refreshed few seconds later (it is seen from the screenshot that the VM has been triggered 17:38:27 (just 2-3 seconds  @later...)

[root@one512 ~]# cat vm-7-1608133136.xml
<VM>
  <ID>7</ID>
  <UID>0</UID>
  <GID>0</GID>
  <UNAME>oneadmin</UNAME>
  <GNAME>oneadmin</GNAME>
  <NAME>Ubuntu 20.04-7</NAME>
  <PERMISSIONS>
    <OWNER_U>1</OWNER_U>
    <OWNER_M>1</OWNER_M>
    <OWNER_A>0</OWNER_A>
    <GROUP_U>0</GROUP_U>
    <GROUP_M>0</GROUP_M>
    <GROUP_A>0</GROUP_A>
    <OTHER_U>0</OTHER_U>
    <OTHER_M>0</OTHER_M>
    <OTHER_A>0</OTHER_A>
  </PERMISSIONS>
  <LAST_POLL>1608133104</LAST_POLL>
  <STATE>6</STATE>
  <LCM_STATE>0</LCM_STATE>
  <PREV_STATE>6</PREV_STATE>
  <PREV_LCM_STATE>0</PREV_LCM_STATE>
  <RESCHED>0</RESCHED>
  <STIME>1603121479</STIME>
  <ETIME>1608133118</ETIME>
  <DEPLOY_ID>d574b352-5e26-4fa9-874e-461827423330</DEPLOY_ID>
  <MONITORING>
    <CPU><![CDATA[1.0]]></CPU>
    <DISKRDBYTES><![CDATA[141615508]]></DISKRDBYTES>
    <DISKRDIOPS><![CDATA[6415]]></DISKRDIOPS>
    <DISKWRBYTES><![CDATA[4637696]]></DISKWRBYTES>
    <DISKWRIOPS><![CDATA[242]]></DISKWRIOPS>
    <DISK_SIZE>
      <ID><![CDATA[0]]></ID>
      <SIZE><![CDATA[1085]]></SIZE>
    </DISK_SIZE>
    <ID><![CDATA[7]]></ID>
    <MEMORY><![CDATA[417392]]></MEMORY>
    <NETRX><![CDATA[0]]></NETRX>
    <NETTX><![CDATA[0]]></NETTX>
    <TIMESTAMP><![CDATA[1608133104]]></TIMESTAMP>
  </MONITORING>
  <TEMPLATE>
    <AUTOMATIC_DS_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 0) & (TM_MAD = "storpool")]]></AUTOMATIC_DS_REQUIREMENTS>
    <AUTOMATIC_NIC_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 0)]]></AUTOMATIC_NIC_REQUIREMENTS>
    <AUTOMATIC_REQUIREMENTS><![CDATA[(CLUSTER_ID = 0) & !(PUBLIC_CLOUD = YES) & !(PIN_POLICY = PINNED)]]></AUTOMATIC_REQUIREMENTS>
    <CONTEXT>
      <DISK_ID><![CDATA[1]]></DISK_ID>
      <NETWORK><![CDATA[YES]]></NETWORK>
      <SSH_PUBLIC_KEY><![CDATA[]]></SSH_PUBLIC_KEY>
      <TARGET><![CDATA[hda]]></TARGET>
    </CONTEXT>
    <CPU><![CDATA[1]]></CPU>
    <DISK>
      <ALLOW_ORPHANS><![CDATA[yes]]></ALLOW_ORPHANS>
      <CLONE><![CDATA[YES]]></CLONE>
      <CLONE_TARGET><![CDATA[SELF]]></CLONE_TARGET>
      <CLUSTER_ID><![CDATA[0]]></CLUSTER_ID>
      <DATASTORE><![CDATA[default]]></DATASTORE>
      <DATASTORE_ID><![CDATA[1]]></DATASTORE_ID>
      <DEV_PREFIX><![CDATA[vd]]></DEV_PREFIX>
      <DISK_ID><![CDATA[0]]></DISK_ID>
      <DISK_SNAPSHOT_TOTAL_SIZE><![CDATA[0]]></DISK_SNAPSHOT_TOTAL_SIZE>
      <DISK_TYPE><![CDATA[BLOCK]]></DISK_TYPE>
      <DRIVER><![CDATA[raw]]></DRIVER>
      <IMAGE><![CDATA[Ubuntu 20.04]]></IMAGE>
      <IMAGE_ID><![CDATA[0]]></IMAGE_ID>
      <IMAGE_STATE><![CDATA[2]]></IMAGE_STATE>
      <LN_TARGET><![CDATA[NONE]]></LN_TARGET>
      <ORIGINAL_SIZE><![CDATA[2252]]></ORIGINAL_SIZE>
      <READONLY><![CDATA[NO]]></READONLY>
      <SAVE><![CDATA[NO]]></SAVE>
      <SIZE><![CDATA[2252]]></SIZE>
      <SOURCE><![CDATA[ans-ds-1/ans-img-0]]></SOURCE>
      <TARGET><![CDATA[vda]]></TARGET>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <TYPE><![CDATA[BLOCK]]></TYPE>
    </DISK>
    <GRAPHICS>
      <LISTEN><![CDATA[<IP_ADDRESS>]]></LISTEN>
      <TYPE><![CDATA[vnc]]></TYPE>
    </GRAPHICS>
    <MEMORY><![CDATA[768]]></MEMORY>
    <OS>
      <ARCH><![CDATA[x86_64]]></ARCH>
    </OS>
    <TEMPLATE_ID><![CDATA[0]]></TEMPLATE_ID>
    <TM_MAD_SYSTEM><![CDATA[storpool]]></TM_MAD_SYSTEM>
    <VMID><![CDATA[7]]></VMID>
  </TEMPLATE>
  <USER_TEMPLATE>
    <INFO><![CDATA[Please do not use this VM Template for vCenter VMs. Refer to the documentation https://bit.ly/37NcJ0Y]]></INFO>
    <LOGO><![CDATA[images/logos/ubuntu.png]]></LOGO>
    <LXD_SECURITY_PRIVILEGED><![CDATA[true]]></LXD_SECURITY_PRIVILEGED>
    <SCHED_ACTION>
      <ACTION><![CDATA[suspense]]></ACTION>
      <ID><![CDATA[0]]></ID>
      <MESSAGE><![CDATA[Wed Dec 16 17:38:27 2020 : This action is not supported.]]></MESSAGE>
      <TIME><![CDATA[+1209600]]></TIME>
    </SCHED_ACTION>
    <SCHED_ACTION>
      <ACTION><![CDATA[terminate]]></ACTION>
      <DONE><![CDATA[1608133107]]></DONE>
      <ID><![CDATA[1]]></ID>
      <TIME><![CDATA[+2419200]]></TIME>
    </SCHED_ACTION>
    <SCHED_REQUIREMENTS><![CDATA[HYPERVISOR!="vcenter"]]></SCHED_REQUIREMENTS>
  </USER_TEMPLATE>
  <HISTORY_RECORDS>
    <HISTORY>
      <OID>7</OID>
      <SEQ>0</SEQ>
      <HOSTNAME>one512kvm1</HOSTNAME>
      <HID>0</HID>
      <CID>0</CID>
      <STIME>1608121489</STIME>
      <ETIME>1608132782</ETIME>
      <VM_MAD><![CDATA[kvm]]></VM_MAD>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <DS_ID>0</DS_ID>
      <PSTIME>1608121489</PSTIME>
      <PETIME>1608121492</PETIME>
      <RSTIME>1608121492</RSTIME>
      <RETIME>1608132779</RETIME>
      <ESTIME>1608132779</ESTIME>
      <EETIME>1608132782</EETIME>
      <ACTION>6</ACTION>
      <UID>0</UID>
      <GID>0</GID>
      <REQUEST_ID>8544</REQUEST_ID>
    </HISTORY>
    <HISTORY>
      <OID>7</OID>
      <SEQ>1</SEQ>
      <HOSTNAME>one512kvm2</HOSTNAME>
      <HID>1</HID>
      <CID>0</CID>
      <STIME>1608132987</STIME>
      <ETIME>1608133118</ETIME>
      <VM_MAD><![CDATA[kvm]]></VM_MAD>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <DS_ID>0</DS_ID>
      <PSTIME>1608132987</PSTIME>
      <PETIME>1608132991</PETIME>
      <RSTIME>1608132991</RSTIME>
      <RETIME>1608133113</RETIME>
      <ESTIME>1608133113</ESTIME>
      <EETIME>1608133118</EETIME>
      <ACTION>27</ACTION>
      <UID>0</UID>
      <GID>0</GID>
      <REQUEST_ID>6816</REQUEST_ID>
    </HISTORY>
  </HISTORY_RECORDS>
</VM>

[root@one512 ~]# onevm show 7
VIRTUAL MACHINE 7 INFORMATION
ID                  : 7
NAME                : Ubuntu 20.04-7
USER                : oneadmin
GROUP               : oneadmin
STATE               : DONE
LCM_STATE           : LCM_INIT
LOCK                : None
RESCHED             : No
START TIME          : 10/19 18:31:19
END TIME            : 12/16 17:38:38
DEPLOY ID           : d574b352-5e26-4fa9-874e-461827423330

VIRTUAL MACHINE MONITORING
CPU                 : 1.0
MEMORY              : 407.6M
NETTX               : 0K
NETRX               : 0K
DISKRDBYTES         : 141615508
DISKRDIOPS          : 6415
DISKWRBYTES         : 4637696
DISKWRIOPS          : 242
ID                  : 7
TIMESTAMP           :<PHONE_NUMBER>

PERMISSIONS
OWNER               : um-
GROUP               : ---
OTHER               : ---

VM DISKS
 ID DATASTORE  TARGET IMAGE                               SIZE      TYPE SAVE
  0 default    vda    Ubuntu 20.04                        1.1G/2.2G bloc   NO
  1 -          hda    CONTEXT                             -/-       -       -

VIRTUAL MACHINE HISTORY
SEQ UID  REQ   HOST         ACTION       DS           START        TIME     PROLOG
  0 0    8544  one512kvm1   undeploy-h    0  12/16 14:24:49   0d 03h08m   0h00m03s
  1 0    6816  one512kvm2   terminate     0  12/16 17:36:27   0d 00h02m   0h00m04s

SCHEDULED ACTIONS
   ID    ACTION  ARGS   SCHEDULED REPEAT   END        DONE                             MESSAGE CHARTER
    0  suspense     - 01/15 02:00                       - Wed Dec 16 17:38:27 2020 : This act Already done *
    1 terminate     - 01/29 02:00             12/16 17:38                                   - Already done *

Ammm it looks like the scheduler become crazy after first try with VM 6 (when reproduced the problem for reporting)...
sched.log
root@one512 one]# cat sched.log
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: Init Scheduler Log system
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: Starting Scheduler Daemon
----------------------------------------
     Scheduler Configuration File
----------------------------------------
DEFAULT_DS_SCHED=POLICY=1
DEFAULT_NIC_SCHED=POLICY=1
DEFAULT_SCHED=POLICY=1
DIFFERENT_VNETS=YES
LIVE_RESCHEDS=1
LOG=DEBUG_LEVEL=3,SYSTEM=file
MAX_DISPATCH=30
MAX_HOST=1
MAX_VM=5000
MEMORY_SYSTEM_DS_SCALE=0
MESSAGE_SIZE=1073741824
ONE_XMLRPC=http://localhost:2633/RPC2
SCHED_INTERVAL=30
TIMEOUT=60
----------------------------------------
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: XML-RPC client using<PHONE_NUMBER> bytes for response buffer.

Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: oned successfully contacted.
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: Configuring scheduler for Zone ID: 0
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: Starting scheduler loop...
Wed Dec 16 12:24:15 2020 [Z0][SCHED][I]: Scheduler loop started.
Wed Dec 16 12:49:16 2020 [Z0][VM][D]: Found 1 pending/rescheduling VMs.
Wed Dec 16 12:49:16 2020 [Z0][HOST][D]: Discovered 2 enabled hosts.
Wed Dec 16 12:49:16 2020 [Z0][VM][D]: VMs in VMGroups:

Wed Dec 16 12:49:16 2020 [Z0][VNET][D]: Discovered 2 vnets.
Wed Dec 16 12:49:16 2020 [Z0][SCHED][D]: Dispatching VMs to hosts:
	VMID	Priority	Host	System DS
	--------------------------------------------------------------
	5	0		1	0

Wed Dec 16 14:24:19 2020 [Z0][VM][D]: Found 1 pending/rescheduling VMs.
Wed Dec 16 14:24:19 2020 [Z0][HOST][D]: Discovered 2 enabled hosts.
Wed Dec 16 14:24:19 2020 [Z0][VM][D]: VMs in VMGroups:

Wed Dec 16 14:24:19 2020 [Z0][VNET][D]: Discovered 2 vnets.
Wed Dec 16 14:24:19 2020 [Z0][SCHED][D]: Dispatching VMs to hosts:
	VMID	Priority	Host	System DS
	--------------------------------------------------------------
	6	0		1	0

Wed Dec 16 14:24:49 2020 [Z0][VM][D]: Found 3 pending/rescheduling VMs.
Wed Dec 16 14:24:49 2020 [Z0][HOST][D]: Discovered 2 enabled hosts.
Wed Dec 16 14:24:49 2020 [Z0][VM][D]: VMs in VMGroups:

Wed Dec 16 14:24:49 2020 [Z0][VNET][D]: Discovered 2 vnets.
Wed Dec 16 14:24:49 2020 [Z0][SCHED][D]: Dispatching VMs to hosts:
	VMID	Priority	Host	System DS
	--------------------------------------------------------------
	7	0		0	0
	8	0		1	0

Wed Dec 16 14:25:19 2020 [Z0][VM][D]: Found 1 pending/rescheduling VMs.
Wed Dec 16 14:25:19 2020 [Z0][HOST][D]: Discovered 2 enabled hosts.
Wed Dec 16 14:25:19 2020 [Z0][VM][D]: VMs in VMGroups:

Wed Dec 16 14:25:19 2020 [Z0][VNET][D]: Discovered 2 vnets.
Wed Dec 16 14:25:19 2020 [Z0][SCHED][D]: Dispatching VMs to hosts:
	VMID	Priority	Host	System DS
	--------------------------------------------------------------
	9	0		0	0

Wed Dec 16 14:25:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:26:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:26:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:27:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:27:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:28:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:28:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:29:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:29:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:30:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:30:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:31:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:31:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:32:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:32:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:33:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:33:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:34:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:34:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:35:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:35:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:36:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:36:49 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:37:19 2020 [Z0][VM][D]: VMs with scheduled actions:
 6
Wed Dec 16 14:37:19 2020 [Z0][VM][I]: Executing action 'terminate' for VM 6 : Success.
Wed Dec 16 14:51:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:51:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:52:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:52:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:53:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:53:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:54:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:54:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:55:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:55:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:56:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:56:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:57:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:57:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:58:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:58:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:59:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 14:59:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:00:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:00:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:01:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:01:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:02:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:02:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:03:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:03:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:04:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:04:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:05:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:05:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:06:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:06:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:07:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:07:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:08:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:08:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:09:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:09:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:10:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:10:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:11:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:11:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:12:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:12:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:13:20 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:13:50 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:14:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:14:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:15:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:15:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:16:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:16:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:17:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:17:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:18:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:18:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:19:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:19:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:20:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:20:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:21:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:21:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:22:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:22:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:23:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:23:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:24:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:24:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:25:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:25:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:26:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:26:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:27:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:27:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:28:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:28:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:29:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:29:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:30:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:30:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:31:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:31:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:32:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:32:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:33:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:33:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:34:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:34:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:35:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:35:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:36:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:36:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:37:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:37:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:38:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:38:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:39:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:39:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:40:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:40:51 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:41:21 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:41:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:42:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:42:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:43:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:43:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:44:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:44:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:45:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:45:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:46:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:46:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:47:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:47:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:48:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:48:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:49:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:49:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:50:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:50:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:51:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:51:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:52:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:52:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:53:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:53:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:54:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:54:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:55:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:55:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:56:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:56:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:57:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:57:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:58:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:58:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:59:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 15:59:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:00:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:00:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:01:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:01:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:02:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:02:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:03:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:03:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:04:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:04:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:05:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:05:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:06:22 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:06:52 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:07:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:07:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:08:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:08:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:09:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:09:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:10:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:10:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:11:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:11:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:12:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:12:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:13:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:13:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:14:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:14:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:15:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:15:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:16:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:16:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:17:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:17:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:18:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:18:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:19:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:19:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:20:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:20:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:21:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:21:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:22:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:22:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:23:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:23:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:24:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:24:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:25:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:25:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:26:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:26:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:27:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:27:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:28:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:28:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:29:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:29:53 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:30:23 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:30:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:31:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:31:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:32:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:32:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:33:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:33:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:34:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:34:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:35:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:35:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:36:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:36:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:37:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:37:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:38:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:38:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:39:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:39:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:40:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:40:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:41:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:41:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:42:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:42:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:43:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:43:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:44:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:44:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:45:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:45:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:46:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:46:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:47:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:47:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:48:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:48:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:49:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:49:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:50:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:50:54 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:51:24 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:51:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:52:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:52:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:53:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:53:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:54:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:54:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:55:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:55:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:56:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:56:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:57:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:57:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:58:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:58:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:59:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 16:59:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:00:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:00:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:01:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:01:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:02:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:02:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:03:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:03:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:04:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:04:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:05:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:05:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:06:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:06:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:07:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:07:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:08:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:08:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:09:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:09:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:10:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:10:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:11:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:11:55 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:12:25 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:12:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:13:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:13:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:14:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:14:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:15:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:15:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:16:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:16:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:17:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:17:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:18:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:18:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:19:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:19:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:20:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:20:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:21:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:21:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:22:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:22:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:23:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:23:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:24:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:24:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:25:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:25:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:26:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:26:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:27:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:27:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:28:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:28:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:29:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:29:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:30:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:30:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:31:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:31:56 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:32:26 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:36:26 2020 [Z0][VM][D]: Found 1 pending/rescheduling VMs.
Wed Dec 16 17:36:26 2020 [Z0][HOST][D]: Discovered 2 enabled hosts.
Wed Dec 16 17:36:26 2020 [Z0][VM][D]: VMs in VMGroups:

Wed Dec 16 17:36:26 2020 [Z0][VNET][D]: Discovered 2 vnets.
Wed Dec 16 17:36:27 2020 [Z0][SCHED][D]: Dispatching VMs to hosts:
	VMID	Priority	Host	System DS
	--------------------------------------------------------------
	7	0		1	0

Wed Dec 16 17:38:27 2020 [Z0][VM][D]: VMs with scheduled actions:
 7
Wed Dec 16 17:38:27 2020 [Z0][VM][I]: Executing action 'suspense' for VM 7 : Failure. This action is not supported.
Wed Dec 16 17:38:27 2020 [Z0][VM][I]: Executing action 'terminate' for VM 7 : Success.

for faster reproduction I'am instantiating a VM, undeploy, then editing /VM/STIME to make the VM older, then resume the VM, and click on the charter
Same reproduced and in a customer installation too - I had a testing VM left from the initial tests. just resumed the VM to become in running state, clicked on the charter and the VM was almost immediately in state6 (DONE)

And The VM XML in question before clicking on the charter:
[root@one512 ~]# cat vm-7-1608133057.xml
<VM>
  <ID>7</ID>
  <UID>0</UID>
  <GID>0</GID>
  <UNAME>oneadmin</UNAME>
  <GNAME>oneadmin</GNAME>
  <NAME>Ubuntu 20.04-7</NAME>
  <PERMISSIONS>
    <OWNER_U>1</OWNER_U>
    <OWNER_M>1</OWNER_M>
    <OWNER_A>0</OWNER_A>
    <GROUP_U>0</GROUP_U>
    <GROUP_M>0</GROUP_M>
    <GROUP_A>0</GROUP_A>
    <OTHER_U>0</OTHER_U>
    <OTHER_M>0</OTHER_M>
    <OTHER_A>0</OTHER_A>
  </PERMISSIONS>
  <LAST_POLL>1608133043</LAST_POLL>
  <STATE>3</STATE>
  <LCM_STATE>3</LCM_STATE>
  <PREV_STATE>3</PREV_STATE>
  <PREV_LCM_STATE>3</PREV_LCM_STATE>
  <RESCHED>0</RESCHED>
  <STIME>1603121479</STIME>
  <ETIME>0</ETIME>
  <DEPLOY_ID>d574b352-5e26-4fa9-874e-461827423330</DEPLOY_ID>
  <MONITORING>
    <CPU><![CDATA[1.0]]></CPU>
    <DISKRDBYTES><![CDATA[141351256]]></DISKRDBYTES>
    <DISKRDIOPS><![CDATA[6345]]></DISKRDIOPS>
    <DISKWRBYTES><![CDATA[4555776]]></DISKWRBYTES>
    <DISKWRIOPS><![CDATA[233]]></DISKWRIOPS>
    <DISK_SIZE>
      <ID><![CDATA[0]]></ID>
      <SIZE><![CDATA[1085]]></SIZE>
    </DISK_SIZE>
    <ID><![CDATA[7]]></ID>
    <MEMORY><![CDATA[417392]]></MEMORY>
    <NETRX><![CDATA[0]]></NETRX>
    <NETTX><![CDATA[0]]></NETTX>
    <TIMESTAMP><![CDATA[1608133043]]></TIMESTAMP>
  </MONITORING>
  <TEMPLATE>
    <AUTOMATIC_DS_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 0) & (TM_MAD = "storpool")]]></AUTOMATIC_DS_REQUIREMENTS>
    <AUTOMATIC_NIC_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 0)]]></AUTOMATIC_NIC_REQUIREMENTS>
    <AUTOMATIC_REQUIREMENTS><![CDATA[(CLUSTER_ID = 0) & !(PUBLIC_CLOUD = YES) & !(PIN_POLICY = PINNED)]]></AUTOMATIC_REQUIREMENTS>
    <CONTEXT>
      <DISK_ID><![CDATA[1]]></DISK_ID>
      <NETWORK><![CDATA[YES]]></NETWORK>
      <SSH_PUBLIC_KEY><![CDATA[]]></SSH_PUBLIC_KEY>
      <TARGET><![CDATA[hda]]></TARGET>
    </CONTEXT>
    <CPU><![CDATA[1]]></CPU>
    <DISK>
      <ALLOW_ORPHANS><![CDATA[yes]]></ALLOW_ORPHANS>
      <CLONE><![CDATA[YES]]></CLONE>
      <CLONE_TARGET><![CDATA[SELF]]></CLONE_TARGET>
      <CLUSTER_ID><![CDATA[0]]></CLUSTER_ID>
      <DATASTORE><![CDATA[default]]></DATASTORE>
      <DATASTORE_ID><![CDATA[1]]></DATASTORE_ID>
      <DEV_PREFIX><![CDATA[vd]]></DEV_PREFIX>
      <DISK_ID><![CDATA[0]]></DISK_ID>
      <DISK_SNAPSHOT_TOTAL_SIZE><![CDATA[0]]></DISK_SNAPSHOT_TOTAL_SIZE>
      <DISK_TYPE><![CDATA[BLOCK]]></DISK_TYPE>
      <DRIVER><![CDATA[raw]]></DRIVER>
      <IMAGE><![CDATA[Ubuntu 20.04]]></IMAGE>
      <IMAGE_ID><![CDATA[0]]></IMAGE_ID>
      <IMAGE_STATE><![CDATA[2]]></IMAGE_STATE>
      <LN_TARGET><![CDATA[NONE]]></LN_TARGET>
      <ORIGINAL_SIZE><![CDATA[2252]]></ORIGINAL_SIZE>
      <READONLY><![CDATA[NO]]></READONLY>
      <SAVE><![CDATA[NO]]></SAVE>
      <SIZE><![CDATA[2252]]></SIZE>
      <SOURCE><![CDATA[ans-ds-1/ans-img-0]]></SOURCE>
      <TARGET><![CDATA[vda]]></TARGET>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <TYPE><![CDATA[BLOCK]]></TYPE>
    </DISK>
    <GRAPHICS>
      <LISTEN><![CDATA[<IP_ADDRESS>]]></LISTEN>
      <PORT><![CDATA[5907]]></PORT>
      <TYPE><![CDATA[vnc]]></TYPE>
    </GRAPHICS>
    <MEMORY><![CDATA[768]]></MEMORY>
    <OS>
      <ARCH><![CDATA[x86_64]]></ARCH>
    </OS>
    <TEMPLATE_ID><![CDATA[0]]></TEMPLATE_ID>
    <TM_MAD_SYSTEM><![CDATA[storpool]]></TM_MAD_SYSTEM>
    <VMID><![CDATA[7]]></VMID>
  </TEMPLATE>
  <USER_TEMPLATE>
    <INFO><![CDATA[Please do not use this VM Template for vCenter VMs. Refer to the documentation https://bit.ly/37NcJ0Y]]></INFO>
    <LOGO><![CDATA[images/logos/ubuntu.png]]></LOGO>
    <LXD_SECURITY_PRIVILEGED><![CDATA[true]]></LXD_SECURITY_PRIVILEGED>
    <SCHED_REQUIREMENTS><![CDATA[HYPERVISOR!="vcenter"]]></SCHED_REQUIREMENTS>
  </USER_TEMPLATE>
  <HISTORY_RECORDS>
    <HISTORY>
      <OID>7</OID>
      <SEQ>0</SEQ>
      <HOSTNAME>one512kvm1</HOSTNAME>
      <HID>0</HID>
      <CID>0</CID>
      <STIME>1608121489</STIME>
      <ETIME>1608132782</ETIME>
      <VM_MAD><![CDATA[kvm]]></VM_MAD>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <DS_ID>0</DS_ID>
      <PSTIME>1608121489</PSTIME>
      <PETIME>1608121492</PETIME>
      <RSTIME>1608121492</RSTIME>
      <RETIME>1608132779</RETIME>
      <ESTIME>1608132779</ESTIME>
      <EETIME>1608132782</EETIME>
      <ACTION>6</ACTION>
      <UID>0</UID>
      <GID>0</GID>
      <REQUEST_ID>8544</REQUEST_ID>
    </HISTORY>
    <HISTORY>
      <OID>7</OID>
      <SEQ>1</SEQ>
      <HOSTNAME>one512kvm2</HOSTNAME>
      <HID>1</HID>
      <CID>0</CID>
      <STIME>1608132987</STIME>
      <ETIME>0</ETIME>
      <VM_MAD><![CDATA[kvm]]></VM_MAD>
      <TM_MAD><![CDATA[storpool]]></TM_MAD>
      <DS_ID>0</DS_ID>
      <PSTIME>1608132987</PSTIME>
      <PETIME>1608132991</PETIME>
      <RSTIME>1608132991</RSTIME>
      <RETIME>0</RETIME>
      <ESTIME>0</ESTIME>
      <EETIME>0</EETIME>
      <ACTION>0</ACTION>
      <UID>-1</UID>
      <GID>-1</GID>
      <REQUEST_ID>-1</REQUEST_ID>
    </HISTORY>
  </HISTORY_RECORDS>
</VM>

Just FYI, we call charters to "the blue thing". You can find the docs here: http://docs.opennebula.io/5.12/operation/vm_management/vm_instances.html?highlight=charters#vm-charter

Thanks! Will disable them in the customer installations until this is resolved.

I've been looking into it and it seems that the root cause is that the scheduled actions used are relative actions (which are relatives to the VM creation time).
I've discussed this with the team and we thing that the following improvements should be added:

Add the warning message previously mentioned, explaining that charters can have impact on the VM.
Fail when trying to create an schedule action scheduled for a past time.

Also, thank you very much for the feedback! Really nice catch!

Hi @christian7007,
I want to clarify the other issues discovered in one place here:

The API accepts any string for action name, and this is discoverable only when the action is triggerred - IMO there should be validation on the API level, and an error returned for unknown actions. The reason for this is because the action could be registered via the API without sunstone,  and the mistake will be detected only when the action is expected to be triggered.
The API registers same actions multiple times(with same parameters) - IMO the name+time+etc should be unique to be accepted. The API should return an error for the duplicated actions.
The scheduler's log is too noisy. IMO the log message Wed Dec 16 17:27:26 2020 [Z0][VM][D]: VMs with scheduled actions: should be with higher debug level (4?) instead of the default. There is no point having this logged every 30 seconds in a production system.

Hello @atodorov-storpool, thanks again for the feedback. We'll take this into account when fixing this issue.

PRs to merge in master:

code
docs

test pendings


next release?

We are currently using <IP_ADDRESS>-develop to get the windows support and Linux docker support in the TopShelf but we also get a lot of warnings about about using a beta version in stable builds. I was just wondering if their will likely be a new release build soon since the last one was 5 months ago.

Sure, I can kick one out with what's in develop.

@seertenedos  what do you mean 'linux docker support',  run under linux?

https://github.com/Topshelf/Topshelf/pull/531
basically there were checks in the code that can only run on windows and if you try to do it on linux it would error. I submitted a fix so it will be able to run as a console app on linux. We mostly use this to run dotnet core as windows services on windows or as a console app in a linux docker container. This lets us get the best of both worlds and do a slow migration

that's just what I needed. thanks.

Hi, any update on a new release? We'd love to run a stable version with #529 in it

can this please happen soon? Still waiting on #531 to ideally be in a release to meet internal requirements for production release of our apps as they are only meant to reference non pre-release nugets.

Done.


Spelling test multifile

This fixes some misspellings in Swift test/multifile, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

@swift-ci smoke test and merge


Adding 1 day on 2011-12-29 while in Pacific/Apia yields the same day

Description of the Issue and Steps to Reproduce:
On 2011-12-29 23:59:59, Samoa changed its time zone from UTC-11 to UTC+13, thus completely skipping 2011-12-30.
However, when executing the following (relevant JSFiddle):
var t = moment.tz("2011-12-29 00:00:00", "YYYY-MM-DD HH:mm:ss", true, "Pacific/Apia");

console.log(t.format());
console.log(t.clone().add(1, "day").format());
console.log(t.clone().add(2, "days").format());

The following is outputted on the console:
2011-12-29T00:00:00-10:00
2011-12-29T00:00:00-10:00
2011-12-31T00:00:00+14:00

Environment:
Reproduced on Firefox 49 and Chromium 52 on Ubuntu 14.04 (although it's highly unlikely this issue is browser-specific).

This should go in the moment-timezone repo. I don't know its rules on historic zone changes so I'd just be guessing.


Retry does not seem active on read timeout

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.12.23. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.12.23

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Report
I am currently on holiday in a place with debatable and variable internet quality: nominally 1024k (~120kB/s effective) with ~50ms ping best case
However the ping can randomly shoot up to the second range, and packet loss can reach 10% in these situations (when the connection doesn't go down entirely) with effective bandwidth being similarly affected.
A more typical scenario is ~80kB/s effective with lag spikes into the 300ms range (connection is currently as perfect as I usually see it  and running ping for 150 packets yields min 45.604, avg 55.589, max 330.341, stdev 37.513)
As a result watching videos online is an impossibility and I rely on youtube-dl to get the videos offline and watch uninterrupted.
However the "retry" option does not seem to affect Read Timeout errors, which happen any time the ping shoots up a bit too high or the connection falls down entirely (even if it reconnects by the time the timeout actually triggers, the original read will never complete).
Verbose Log
These are two runs (back to back):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-R', u'infinite', u'https://www.youtube.com/watch?v=bAVS6IlujZE']
[debug] Encodings: locale utf-8, fs utf-8, out utf-8, pref utf-8
[debug] youtube-dl version 2017.12.23
[debug] Python version 2.7.14 - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.4.1, ffprobe 3.4.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] bAVS6IlujZE: Downloading webpage
[youtube] bAVS6IlujZE: Downloading video info webpage
[youtube] bAVS6IlujZE: Extracting video information
[youtube] bAVS6IlujZE: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
WARNING: Requested formats are incompatible for merge and will be merged into mkv.
[debug] Invoking downloader on u'https://r4---sn-4g5ednsk.googlevideo.com/videoplayback?id=6c0552e8896e8d91&itag=298&source=youtube&requiressl=yes&pl=16&mm=31&ei=3OBCWvinHYS9VImqvpgP&initcwndbps=392500&mn=sn-4g5ednsk&ms=au&mv=m&ratebypass=yes&mime=video/mp4&gir=yes&clen=6156947069&lmt=1513885734203450&dur=32046.048&mt=1514332278&key=dg_yt0&signature=7CC8C5B6640B3BB3BE9DE36255423EA1D7B224AD.6DC7F6A546407547833CB9F1E11FE3E34391197C&ip=<IP_ADDRESS>&ipbits=0&expire=1514353980&sparams=ip,ipbits,expire,id,itag,source,requiressl,pl,mm,ei,initcwndbps,mn,ms,mv,ratebypass,mime,gir,clen,lmt,dur'
[download] Resuming download at byte 143191710
[download] Destination: Tastosis, iNcontroL, & Day[9] host Day 1 of the Twitch StarCraft Holiday Bash-bAVS6IlujZE.f298.mp4
[download]   2.8% of 5.73GiB at 97.32KiB/s ETA 16:41:18ERROR: unable to download video data: ('The read operation timed out',)
Traceback (most recent call last):
  File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1889, in process_info
    partial_success = dl(fname, new_info)
  File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1834, in dl
    return fd.download(name, info)
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 361, in download
    return self.real_download(filename, info_dict)
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 287, in real_download
    return download()
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 180, in download
    data_block = ctx.data.read(block_size if not is_test else min(block_size, data_len - byte_counter))
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 384, in read
    data = self._sock.recv(left)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 597, in read
    s = self.fp.read(amt)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 384, in read
    data = self._sock.recv(left)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 766, in recv
    return self.read(buflen)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 653, in read
    v = self._sslobj.read(len)
SSLError: ('The read operation timed out',)

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-R', u'infinite', u'https://www.youtube.com/watch?v=bAVS6IlujZE']
[debug] Encodings: locale utf-8, fs utf-8, out utf-8, pref utf-8
[debug] youtube-dl version 2017.12.23
[debug] Python version 2.7.14 - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.4.1, ffprobe 3.4.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] bAVS6IlujZE: Downloading webpage
[youtube] bAVS6IlujZE: Downloading video info webpage
[youtube] bAVS6IlujZE: Extracting video information
[youtube] bAVS6IlujZE: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
WARNING: Requested formats are incompatible for merge and will be merged into mkv.
[debug] Invoking downloader on u'https://r4---sn-4g5ednsk.googlevideo.com/videoplayback?id=6c0552e8896e8d91&itag=298&source=youtube&requiressl=yes&mv=m&mn=sn-4g5ednsk&mm=31&initcwndbps=398750&ms=au&ei=UuRCWsyUAoiwctPhuugD&pl=16&ratebypass=yes&mime=video/mp4&gir=yes&clen=6156947069&lmt=1513885734203450&dur=32046.048&key=dg_yt0&signature=1314D2559FCF006A2C124D277BAC2B067ED8A643.51E83F8C277A34C4237096EE6D9F3163E89F029E&mt=1514333185&ip=<IP_ADDRESS>&ipbits=0&expire=1514354866&sparams=ip,ipbits,expire,id,itag,source,requiressl,mv,mn,mm,initcwndbps,ms,ei,pl,ratebypass,mime,gir,clen,lmt,dur'
[download] Resuming download at byte 169922912
[download] Destination: Tastosis, iNcontroL, & Day[9] host Day 1 of the Twitch StarCraft Holiday Bash-bAVS6IlujZE.f298.mp4
[download]   3.6% of 5.73GiB at 39.71KiB/s ETA 40:34:00ERROR: unable to download video data: ('The read operation timed out',)
Traceback (most recent call last):
  File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1889, in process_info
    partial_success = dl(fname, new_info)
  File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1834, in dl
    return fd.download(name, info)
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 361, in download
    return self.real_download(filename, info_dict)
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 287, in real_download
    return download()
  File "/opt/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 180, in download
    data_block = ctx.data.read(block_size if not is_test else min(block_size, data_len - byte_counter))
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 384, in read
    data = self._sock.recv(left)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 597, in read
    s = self.fp.read(amt)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 384, in read
    data = self._sock.recv(left)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 766, in recv
    return self.read(buflen)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 653, in read
    v = self._sslobj.read(len)
SSLError: ('The read operation timed out',)

Mitigation
I currently have a small script just running ydl in a loop until it succeeds, but a working Retry option would definitely be superior.

I'm facing the same issue. It's insanely annoying.


SerialRTU Anomaly

When sending data manually to query a coil, I get the expected result, but from NModbus4 I get a 0x3F result:
Using serial port monitor:
[22/12/2015 12:11:33] - Open port COM5 (C:\Program Files\Eltima Software\Serial Port Monitor\SerialMonitor.exe)

[22/12/2015 12:11:41] Written data (COM5)
    03 01 00 00 00 01 fc 28                           ......ü(
[22/12/2015 12:11:41] Read data (COM5)
    03 01 01 01 91 f0                                 ....‘ð
[22/12/2015 12:14:21] - Close port COM5

Using NModbus4
[22/12/2015 12:14:25] - Open port COM5 (C:\Users\gavin\Source\Repos\HSPI_MODBUS\Modbus Plugin\ConsoleApplication1\bin\Debug\ModbusConsole.vshost.exe)

[22/12/2015 12:14:25] Written data (COM5)
    03 01 00 00 00 01 fc 28                           ......ü(
[22/12/2015 12:14:25] Read data (COM5)
    00 3f                                             .?
[22/12/2015 12:14:28] - Close port COM5

Code:
Dim port = New SerialPort("COM5", 19200, Parity.Even, 8, StopBits.One)
port.Open()
Dim master As ModbusSerialMaster = ModbusSerialMaster.CreateRtu(port)
master.Transport.Retries = 0
master.Transport.ReadTimeout = 3000
Dim coils() = master.ReadCoils(3, 0, 1)

COM port parameters identical.  Any ideas?

Are you still hitting this issue?

Resolved the issue by removing a terminating resistor on the bus that seemed to be causing random CRC errors.
Sent from my iPhone

On 04 Jan 2016, at 11:38 AM, Dmitry Turin<EMAIL_ADDRESS>wrote:
Are you still hitting this issue?
—
Reply to this email directly or view it on GitHub.


Add support for a toKey symbol?

In ES6, the canonical use case for symbols is so that objects can implement special methods for use by other data structures. It seems like an ideal situation for this library to add support for a toKey method that could be used throughout this library. I implemented the concept in this data structure for identity map, but I think it could be generalized.
Unfortunately, there's not currently a way to create a typescript interface around a custom symbol. I suspect TS will add this soon enough, they've indicated they want to handle it on the issue tracker.
https://gist.github.com/chriseppstein/11ae09e2d96f72af036645a481d879e3

I this this is a good change but I'm not up-to-date with current TypeScript features. Can you tell if this can break support in browser/node?

We can feature detect whether Symbol() is supported. In those versions, users would have to provide a string function.

Closing this because of old age. If the issue persists, discuss it here and/or open a Pull Request please.


Frontend: Re-enable stubbing unavailable decls

This reverts commit ad604f2803fcdf73e34a575ab90b20d5a338d637.

@swift-ci please test


Pinning of the AUR's TLS public key

This is WIP towards implementing #185.

[x] Patch aursync
[ ] Patch aursearch
[ ] Patch aurgrep
[ ] Document

Should I start documenting this, or are you waiting for something? :)

It's more that I'm hesitant knowing there's no upstream support for actual HPKP, even when client-side pinning works fine. If you could do --cert-status in a separate commit, I'd merge that one directly, though.

I could do that, but it's not really worth a PR. You can add that to the two calls two curl if you want :)
Do you have a specific reason to hesitate? :)
I actually prefer client-side pinning because it's an out-of-band trust model, whereas everything is sent along with HPKP.

Cool, github kept the comments after a rebase and force-push :)

My concern for client-side pinning when HPKP is not supported by the site is, how do you make sure you don't have a fake, MITM certificate at the time you set the public key in your configuration? (I suppose you have a similar issue with HPKP, but only on the very first connection to the website)

how do you make sure you don't have a fake MITM certificate at the time you set the public key in your configuration?

By thinking and being careful. For example, you could

check several times during the week, and/or
check from within different networks, e.g. uni, and/or
use different DNS servers, and/or
also check through a VPN, and/or
check after SSHing somewhere else.

Maybe the admin of the machine the AUR runs on would even GPG-sign a hash generated directly from the file and/or post it to aur-general if you ask nicely :)
I don't find this inherently less secure than HPKP, but rather a trade-off. HPKP is nice because it requires no user-interaction, but a MITM on first connection negates it completely.
Whereas this makes out-of-channel checks much easier, and even allows you to secure a new machine before ever connecting to the internet, simply by copying a trusted hash over from another one.
Or, for that matter, pass a hash on to close friends, or compare against theirs.

For reference, I have this in my ~/.zshrc:
function generate-tls-pubkey-hash() {
	openssl s_client -servername $1 -connect $1:443 |
	 openssl x509 -pubkey -noout |
	 tee /dev/stderr |
	 openssl rsa -pubin -outform der |
	 openssl dgst -sha256 -binary |
	 openssl enc -base64
}

The resulting hash can be used in curl by prepending sha256//.

Did you make up your mind on this? :)

Sorry, I don't have much time to look at aurutils atm

Okay, thanks for the reply, just wanted to get a lifesign :)

See https://github.com/AladW/aurutils/issues/185#issuecomment-326458202. If you want to implement this in a separate repo, let me know and I'll link it from the readme.


IRGen: Also list specialized generic class' objective c ro data in the dedicated linker section

List the emitted ro_data of specialized generic classes in the __objc_clsrolist section.
rdar://132354480

@swift-ci test


Add percentage in restoring state

add volume percentage
add backup percentage

depends on https://github.com/longhorn/longhorn/issues/2512


[Bug]: This action requires the clientId field. Enter a valid value for clientId

The problem
I installed yesterday on Home Assistant version 2024.10.1, Supervisor version 2024.10.0, Operating System 13.1.
The WhatsApp version is 1.4.1 and I can't send a single message and every time I try to send it, I get the error "This action requires the clientId field. Enter a valid value for clientId" and I don't know how to solve it.
I created another client and scanned the QR code and the same problem.

What version of Home Assistant Core has the issue?
2024.10.1
What version of the addon has the issue?
1.4.1
What type of installation are you running?
Home Assistant OS
Log information
2024-10-09 09:47:37.087 INFO (SyncWorker_5) [supervisor.docker.manager] Stopping addon_f4fdf59d_whatsapp_addon application
2024-10-09 09:47:44.334 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_f4fdf59d_whatsapp_addon application
2024-10-09 09:47:47.896 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on f4fdf59d/aarch64-addon-whatsapp_addon with version 1.4.1

s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[15:23:55] INFO: Installed custom component.
[2024-10-08T15:23:59.108] [INFO] default - Whatsapp Addon started.
[2024-10-08T15:24:03.608] [INFO] default - default client is ready.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[18:46:19] INFO: Installed custom component.
[2024-10-08T18:46:47.184] [INFO] default - Whatsapp Addon started.
[2024-10-08T18:46:49.988] [INFO] default - default client is ready.
/whatsapp.js:240
      throw new WhatsappError(err.output.payload.statusCode);
            ^

WhatsappError: Send message failed. Whatsapp error 428: Connection Closed
    at WhatsappClient.sendPresenceUpdate (/whatsapp.js:240:13)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processTimers (node:internal/timers:504:9) {
  code: 428
}

Node.js v18.9.1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[23:05:22] INFO: Installed custom component.
[2024-10-08T23:05:27.624] [INFO] default - Whatsapp Addon started.
[2024-10-08T23:05:32.041] [INFO] default - default client is ready.
/whatsapp.js:240
      throw new WhatsappError(err.output.payload.statusCode);
            ^

WhatsappError: Send message failed. Whatsapp error 428: Connection Closed
    at WhatsappClient.sendPresenceUpdate (/whatsapp.js:240:13) {
  code: 428
}

Node.js v18.9.1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[00:08:03] INFO: Installed custom component.
[2024-10-09T00:08:10.111] [INFO] default - Whatsapp Addon started.
[2024-10-09T00:08:11.628] [INFO] default - default client is ready.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:47:48] INFO: Installed custom component.
[2024-10-09T09:47:54.772] [INFO] default - Whatsapp Addon started.
[2024-10-09T09:47:56.894] [INFO] default - casa require authentication over QRCode, please see your notifications...
[2024-10-09T09:47:57.573] [INFO] default - default client is ready.
[2024-10-09T09:48:25.517] [INFO] default - casa client is ready.

Additional information
This action requires the clientId field. Enter a valid value for clientId

Same here but if I use the action in an automation it works


Remove short pause after each slide

I use slick with autoplay option. I have a question: is there any way to remove short pause after each slide? I want to slider moved without any stops. Sorry for my bad english ;)

Do you have an example? What did you set autoplaySpeed to?

This issue looks like a support question and a stale conversation and therefore is being closed


ask

my device is android 11, can i use this library to my app?

Yes

Yes

ok i will learn it, if there is something i don't understand i will ask again

Yes

wait, so this library doesn't have a download and install mechanism within the application itself? only notifications? even from github

Yes

wait, so this library doesn't have a download and install mechanism within the application itself? only notifications? even from github

@MaserPlay bro

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns
```json
{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}
```

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns

{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}

nice, I see the last release of this library was a year ago, have you replaced the dialog with the latest material design 3?

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns

{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}

nice, I see the last release of this library was a year ago, have you replaced the dialog with the latest material design 3?

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns
{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}

nice, I see the last release of this library was a year ago, have you replaced the dialog with the latest material design 3?

No

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns
{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}

nice, I see the last release of this library was a year ago, have you replaced the dialog with the latest material design 3?

No

can you change it to material design 3?

Yes.
This is a updated version AppUpdater by javiersantos
I just update this lib to support new android versions, and change some old libs to with new ones.
On my web server, I created a dynamically modified json that returns
{
  "latestVersion": "10.11.23_BugFix2",
  "latestVersionCode": "17",
  "url": "https://github.com/MaserPlay/AppAi/releases/download/10.11.23_BugFix2/app-release.apk",
  "releaseNotes": [
    "- BugFix",
    "- Updated Versions of AppAi"
  ]
}

nice, I see the last release of this library was a year ago, have you replaced the dialog with the latest material design 3?

No

can you change it to material design 3? like this

No + I don't remember exactly, maybe I added it.


Godoc "Simplest Example" Incorrect

https://godoc.org/github.com/gizak/termui
"A simplest example:" code sample won't compile as g.Border.Label = "Gauge" (code line 14) is actually of type bool
Should be: g.BorderLabel = "Gauge"

Fixed by https://github.com/gizak/termui/pull/84


The SQL Extractor in Airflow fails to parse PosgreSQL's variants of TRUNCATE, ALTER and ANALYZE

I am using the SQLExecuteQueryOperator in Airflow to run SQL in a PostgreSQL database. The corresponding SQL Extractor from OpenLineage fails to parse these three statements:
ALTER SEQUENCE tablename RESTART WITH 1;
The error message is Expected one of TABLE or INDEX, found: SEQUENCE
ANALYZE tablename;
The error message indicates that ANALYZE needs to be followed by TABLE. That modification, however, would not be accepted by the database engine.
TRUNCATE tablename;
Again, the error message indicates that TRUNCATE needs to be followed by the TABLE keyword. That is not strictly necessary in PostgreSQL.

@alescervenka this generally should create error facet, but not prevent parsing of other SQL statements, or otherwise, in the case of first two statements, generate useful lineage information, right?
I think TRUNCATE tablename; should work though, and will look on that

TRUNCATE should be fixed in the next release https://github.com/sqlparser-rs/sqlparser-rs/pull/883

Thank you for fixing the TRUNCATE @mobuchowski .
I tried testing you hypothesis that the two issues might not prevent the extractor from generating a useful lineage. I did that in a DAG with operator:
update_table = SQLExecuteQueryOperator(
    task_id='update_table',
    conn_id = PG,
    autocommit = True,
    sql = """ANALYZE stage.source_table;
    update stage.source_table set cvalue = 'there' where ckey = 'where';
    """,
    split_statements = True,
    dag = dag
)

When I check the result of extraction in Marquez (at http://localhost:3000/lineage/job/default/sql_lineage_test.update_table), I can see the extraction facet in the resulting JSON but no lineage information in the graph above:

@alescervenka I believe this is a bug - but a different one, related to not properly handling split_statements, rather than parser. Parser does right thing when I pass it a list of statements instead of single one. I'll change title of this issue to reflect where the problem is.


fix(@angular-devkit/build-angular): move core-js out of dev-dependencies

The polyfills in build_angular/src/angular-cli-files/models use core-js in production mode. Therefore, it needs to be in the regular dependencies, not just dev-dependencies.
This allows NPM/Yarn to install the proper core-js version when the main project uses a newer one.
The problem occurred when our project moved to<EMAIL_ADDRESS>still using Angular 7 and therefore using<EMAIL_ADDRESS>

Thank you for the contribution.
However, Angular CLI 7.x only supports core-js 2.x.  Please upgrade to 8.x if core-js 3.x is required.  Also note that core-js is no longer a project dependency for 8.0+ generated projects.

@clydin
Hi,
yes, I am aware that Angular 7.x only supports core-js 2.x.
The non-angular part of our project moved to core-js 3.1.4 which broke build-angular, because it does not define its core-js version in its production dependencies. Therefore, I moved the<EMAIL_ADDRESS>from dev-dependencies to dependencies, allowing NPM to detect that it needs to install an independent core-js version for build-angular, avoiding the need of migrating to Angular 8 right now.
I did NOT change the core-js version of build-angular on the 7.x branch, just made sure it correctly broadcasts it to NPM

The project local version of core-js is used in 7.x.  This changed in 8.  This PR would be a breaking change as the version within  projects would no longer be used which could result in behavioral changes.

You can use a variation of the following if core-js 3.x is required within the local project for a 7.x project:
{
  "compilerOptions": {
    "paths": {
      "core-js/es7/reflect": ["./node_modules/core-js/proposals/reflect-metadata"],
      "core-js/es6/*": ["./node_modules/core-js/es/*"]
    }
  }
}

The node modules path may need to be adjusted based on its location within the project.

Okay, I'll setup the paths then. Thanks for your time and sorry for the inconvenience

No problem at all.  And thank you for taking the time to help contribute to the project.


SSL certificate for load balancer

Given that there's a login on the site, it seems like a good idea for it to use SSL. Amazon Certificate Manager is free, and on Elastic Beanstalk you should be able to just add the certificate to the load balancer without actually changing the nginx configuration (apparently communication between the load balancer and the app server is over HTTP).
More info here https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html, and I'm happy to help with this

@pjsier Yes, 100%. I tried this a few months ago and it works but our assets aren't working. Here's  our staging server where I tested. https://staging.coderdojochi.org/

Hmm, not sure why on the staging site it's referencing the static files over http because the settings look right, and on staging the STATIC_URL setting shows up as HTTPS. It could have to do with SITE_URL being HTTP?
That part seems fixable though, and you can add the S3 bucket to a Cloudfront distro with a certificate through ACM set up to get around that.


Fix yaml syntax in ci.yaml

Fixes https://github.com/litestar-org/litestar/pull/2090

Oups, fixed already :)


BrightFutures 2.0

Open questions:

[ ] Should Future<T, E>.succeeded(_: T) return a Future<T, NoError> or a Future<T, E>?
[ ] Do we need an Either (or EitherError)?

I've finished the first stab at getting rid of NSError in the framework and it has turned out quite nice, I think. One thing that I'm not so happy about yet is that I need EitherError where two types of errors could be returned, e.g. https://github.com/Thomvis/BrightFutures/blob/9335a5c169f7938bf160ffccc3e62fde8aeb0cec/BrightFutures/Future.swift#L485. It might not be a very big deal and I will think about it more. Feedback is welcome!

Thanks @robrix! I've replaced the EitherError with an External error case. I like it!


Create a safeguard for tempfile

Make sure that the file stream for tempfiles are closed successfully and files are written correctly before passing the files to a planner. Use the file only after closing it like this. Additional checks for the files might be helpful also. This issue is well known (https://github.com/python/cpython/issues/115113).
It is an expected behavior. Path.write_text() is not an atomic operation. First it open a file for writing (creating a new file if it did not exist and truncating and existing file), then write an encoded string (perhaps in several chunks if it is large enough, the closes the file). If you read a file between its opening and writing into it, you can see an empty file or a partial content.

If you want an atomic operation, write into another file (preferable in the same directory), and then replace the target file with it (using os.replace()). The success is platform and filesystem depending, but it should work on Posix platform in common cases.

See:
https://github.com/IBM/nl2flow/blob/main/nl2flow/plan/planners.py#L122

Done


Set/show rules for math symbols

Description
Hello, I'm totally new to typst and I really appreciate the way math is handled. However, I skimmed through the docs and issues and didn't find any way of manipulation of math symbols like the general typst idea of handling the styles. So, when I want to write very basic expression like integral from a to b with limits, I need to write
$ limits(integral)_a^b f(x) dx $

It is not that bad, but in general I want to use "limits" on all integrals I encounter, so that seems a bit of excess. However, if I try to use that approach "just use show/set rules" and try to write a rule that edits math.integral, it gives a message "expected function, label, string, regular expression, or selector, found symbol".
Of course, it is possible to use variables to create new integral with limits:
#let integral =  math.limits(math.integral)
$ integral_0^oo f(x) dx $

It is even possible to set it from templates if using import * (but not from constructor functions). But is seems to me than changing a way limits are placed or symbol is written (in fact replacing it with some other combination of commands and symbols) is the "style thing", so it seems more consistent to change them through styles rules.
Use Case
What is more, using styles instead of reassinging commands will allow changing rendering for some categories of symbols or symbols that meet certain conditions. In case of integrals, that would be adding limits for all types of integrals, not just one symbol. If rules for symbols work, that requires just adding selectors for symbol groups.
I suppose that this is a useful thing for maths that is just not implemented yet. I believe that developing rules for proper math editing will lead to much easier math typing. Of course, over- and misuse of such rules could make math less intuitive. E.g., users can reassign symbols with long names to shorter ones. Nevertheless, this is the problem that typst encounters in general, and it seems that it doesn't cause much fuss.
Again, I'm totally new to typst, so I could get it all wrong. In that case, I would be grateful to someone who can tell me how to properly deal with this problem.

Seems related to #305 and #262.
That having said, your choice of putting the limits above/below the integral is definitely a bit weird. (as in generally speaking the built-in behavior of Typst should be the typographically best and users should not deviate from that)
In this specific case though, I don't see much functional difference between show rule and redefining the symbol.

Well, in fact there are numerous math things that relate to symbols style. For example, in math community of my country sinh is usually written as sh, trigonometric functions like сsc (cosecant) are never used (1/sin is written instead) and so on. Placing limits that way is also that kind of thing. Sadly, sometimes it is impossible to make the things the best way for everybody. It is possible to add special symbols for such localizations, but it would become harder to share source between different communities. Changing some settings in the header is easier than replacing things in all the document.
Of course, its could be managed through several "localization" packages with "import *", but I don't think it is a good way. It would be great if I could call some functions from one package to set up my "localization", but as there are no global variables allowed, that would require some state management (and that seems too complicated).
Again, I think that rules could be used for some more complicated things, like reducing spacing if symbol stays in fraction (that will need some new math selectors to be added). I can't think of all the potential uses right now, but I think that that could  reduce boilerplate for non-trivial customization.
Probably, it is better to listen to someone more experienced in typing math as I haven't written large math doc in typst yet.

More thoughts in support of this feature:

Conceptually, it's like dependency injection in programming: the math formulas become generic over styling and the entities predefined by typst specification (e.g. integral in this case) implicitly become interfaces whereas the filters become their implementations. So, we can have a single way to represent, what is written, but different ways to show it.
This opens up a wide scope for imagination:

One can write an article once and then adopt it for different localizations just by changing filters
Imagine a person has realized that all the previously written code needs a slight but a systematic styling shift and from now on he or she would use other visual primitives to represent math entities. In that case, post-processing is the right choice because it would need less effort (that changing all formulas) and would maintain consistency within the document.

Сoncerning сonsistency, math-mode filters would be consistent with ones in non-math mode (their presence is generally what people expect) so it follows the major design goal of typst: Simplicity through Consistency

(Still, this arguments only show that such feature would be useful. However it's not obvious how important it is…)

In principle, I agree that styling is the right way to configure this as opposed to redefining the symbol. I'd have to think a bit more about the implementation implications though.


Allow the px-context-browser to be disabled

Is there a property that is in the works or streamlined in the backlog for disabling the context-browser?

Just to clarify, by "disabled" do you mean that you still want the context browser to be visible on the page, but have it grayed out or something and non-interactive?

@randyaskin yes that's exactly what I am asking for. Thank you!

@randyaskin I would love to build this enhancement, Let me know if you would like me to contribute to this?

@1mayur - let's run this by our designers first, and if they give the thumbs up, it's all yours :)

@runn-vermel Thanks. Will wait for the response

review requested from design team

To be in line with our other disabled buttons, I would expect:

A new property should be added for "disabled" (boolean, value false by default)
Asset and parent asset text color should be exposed as a new style variable (--px-cb-text-color--disabled), which should default to $gray4
The "fa-caret-down" icon on the right should be hidden
The cursor should change from pointer to "not-allowed"
The click event should be ignored so the modal is not invoked

@randyaskin Okay, Thanks

@randyaskin @runn-vermel Created the PR with the feature and also updated the index.html page for demo.


SBOM Report for Infor ( GRC Product )

Hi,
Aditya here from the Infor GRC automation team. We have been using these packages for our product, GRC (Governance Risk and Compliance), for a while now. Infor GRC has been generating SBOM reports for vulnerability scanning. Recently, we have been asked to obtain SBOM reports from third-party resources we have been using. Therefore, I request you to provide me with the SBOM reports for the packages mentioned below, along with their versions. The reports are required for these versions only and in CycloneDX JSON format.
netty-transport-native-epoll -	4.1.111.Final
netty-transport-classes-epoll -	4.1.111.Final
netty-buffer -	4.1.111.Final
netty-codec -	4.1.111.Final
netty-codec-http2 -	4.1.111.Final
netty-transport-native-unix-common -	4.1.111.Final
netty-resolver -	4.1.111.Final
netty-transport	 - 4.1.111.Final
netty-handler -	4.1.111.Final
netty-codec-http -	4.1.111.Final
netty-common  -	4.1.111.Final

Netty, as an open source project, has no obligation to provide you with such reports. You can check out the relevant tag, modify the pom files to add sbom plugins, and generate the reports yourselves. You could also take this opportunity to contribute sbom plugin configurations to our build, to make this less troublesome in the future.


[ST] Fade Visited Trades is broken / other UI broken

As title says, visited trades are not being rendered in a different shade.  This is an essential feature for me.
I tried to remove and re-add ESGST and re-enable Fade Visited Trades.  No joy.
This is as of the big site update a week ago at ST, which also moved the ESGST button out of location on the top bar.

does [ST] Mark trades as visited when visiting them. do anything?
has [ST] Fade Visited Trades been depreciated?
I still can't get this to work like it used to.

This is essential for me because I send a trade offer to anyone that has the game I want, (under a certain rep because I avoid for-profit traders).  Without faded visited trades, I accidentally send duplicate offers when I try to send out new offers a few days or weeks later when additional people have listed something I'm (still) looking for.


feat: implement observability hooks for all leapfrogai components

User Story: Implement Prometheus and Kubernetes Metrics
As a UDS cluster administrator
I want to have Prometheus metrics and Kubernetes metrics for observability of the LeapfrogAIservices
So that I can monitor the performance, health, and usage of the LeapfrogAI services
Applies to ALL LeapfrogAI services and components (pods, daemon sets, jobs, etc.).
Acceptance Criteria:
1. Identify Key Metrics

[ ] Identify the key metrics for the observability of the components and services:

Generation tokens per second
Total number of generated tokens
Latency of generation requests
Number of active generation requests
CPU and memory utilization (via Kubernetes Metrics Server)
Error rates and counts

[ ] Must ensure metrics remain relevant and actionable for continuous improvement
[ ] Setup logger profiles for all metrics in the development, staging and production environments

2. Implement Prometheus Metrics Endpoints

[ ] Implement Prometheus metric endpoints in the backend services to expose the identified metrics

Must format metrics following Prometheus conventions using the UDS Package CR

3. Integrate with Prometheus Monitoring Stack

[ ] Configure Prometheus to scrape the backend services’ metric endpoints at regular intervals

Prometheus: Must ensure it integrates with the services using proper intervals
Grafana: Must integrate with Grafana for real-time metric visualization

4. Kubernetes Metrics Integration

[ ] Leverage Kubernetes Metrics Server to collect and monitor cluster-level metrics, including:

CPU usage
Memory usage
Pod resource consumption
Node health

[ ] (OPTIONAL) Leverage these metrics for horizontal resource scaling

5. Log Aggregation

[ ] Implement log aggregation using Promtail to send logs to Loki for centralized log management.

Loki: Must aggregate and store logs related to backend services for analysis

6. Set Up Dashboards and Alerts

[ ] Set up Grafana dashboards to visualize the following backend and Kubernetes metrics in real-time:

Tokens per second
Latency and error rates
Resource utilization (CPU, memory)
Active requests
Pod and node health

[ ] Set up appropriate Prometheus recording and alerting rules based on collected metrics

Must configure alerts for significant threshold breaches (e.g., high latency, excessive errors, resource exhaustion)

7. Authentication and Authorization

[ ] Implement secure authentication and authorization mechanisms for accessing the Prometheus metrics endpoints

8. Optimize Performance Impact

[ ] Optimize the performance impact of metrics collection to minimize overhead on the backend services

Must regularly review and tune metrics collection to avoid resource strain

9. Document and Instruct

[ ] Document all available metrics, their descriptions, and instructions on how to interpret them
[ ] Provide clear instructions for setting up and configuring Prometheus and Grafana for backend services monitoring

10. Load Testing

[ ] Conduct load testing to ensure that the metrics collection can handle high-traffic scenarios

Must verify system stability under load (regular Locust testing)

Bump this issue with the following additions, on top of vLLM. Each one must have all of the criteria as listed for vLLM in the original issue description:

[ ] llama-cpp-python
[ ] supabase
[ ] leapfrogai-api
[ ] leapfrogai-ui
[ ] whisper
[ ] text-embeddings

Deprecated in favor of https://github.com/orgs/defenseunicorns/projects/75/views/7?pane=issue&itemId=79287868


(fix) Update for latest Ergo dev with dual engine

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 95.312% when pulling 516640e9437f8867f9ad2dfa3ba6c0ce34819a33 on jeromesimeon:js-dual-engine into d1363c0724393d57527ba3229adea2b3b272b7f6 on accordproject:master.


Ldap improvements

These are two commits that:

Adds the option for a connection timeout.
Removed the deprecated method option.

I planned to do more stuff (refactoring some parts), but I thought I'd over-complicate the PR :sweat_smile:

There's a single test failing. Fix it and it should be good to merge. It's probably related to the way you are fetching the values from the config since you've changed it in a lot of places.

@vitoravelino fixed!


Fixed docker issue with FLASK_APP value

CATEGORY
Choose one

[ X] Bug Fix

SUMMARY
Fixes #8620
TEST PLAN
Tested locally. I tested with docker-compose.yml env SUPERSET_ENV: development and SUPERSET_ENV: production.
git clone https://github.com/apache/incubator-superset/
cd incubator-superset/contrib/docker
docker-compose run --rm superset ./docker-init.sh
docker-compose up

ADDITIONAL INFORMATION

[ X] Has associated issue: Fixes #8620

REVIEWERS

Codecov Report

Merging #8621 into master will increase coverage by 0.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8621      +/-   ##
==========================================
+ Coverage   65.78%   66.42%   +0.64%
==========================================
  Files         482      482
  Lines       23798    24590     +792
  Branches     2589     2589
==========================================
+ Hits        15655    16334     +679
- Misses       7974     8087     +113
  Partials      169      169

Impacted Files
Coverage Δ

superset/db_engine_specs/postgres.py
55.55% <0%> (-27.78%)
:arrow_down:

superset/utils/core.py
89.23% <0%> (+1.21%)
:arrow_up:

superset/jinja_context.py
78.37% <0%> (+1.67%)
:arrow_up:

superset/views/core.py
76.3% <0%> (+4.5%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff6773d...a8ba2ea. Read the comment docs.


Fix permanent replacement of tasks with the wrong config

I'm closing this and will come back to it.  Not going to make it into GA and it's not super urgent.


Can't install on GTX 1660 Super

Hello!
I've been able to install GamerOS on my old i7-3770 with GTX 960 easily following the standard installer, but I tried doing the same with my new Ryzen 5 3600 and GTX 1660 Super (nvme drive) and all I get is an unreadable blurry screen and at some point it gets stuck on a half blue screen.
It stops being usable after the initial installer menu (Install GamerOS, uefi bootloader, Reboot to system settings...).
Any help would be awesome.
Thanks again.

The problem is not resolved, but I found a workaround:
Installing GamerOs with the GTX 960 in my Ryzen 5 3600 rig.
Nouveau problem? Could it be possible to include the Nvidia driver at install?
Thanks anyway. I really do like GamerOS.

Hi, can you try the new ISO installer here: https://github.com/gamer-os/install-media/releases/download/2020-03-12/gameros-2020.03.12-x86_64.iso
This sounds like a duplicate of https://github.com/gamer-os/install-media/issues/8


STAGA complex

another histone acetyltransferase complex (is_a GO:0000123)
Reported by: mah11
Original Ticket: "geneontology/ontology-requests/1603":https://sourceforge.net/p/geneontology/ontology-requests/1603

thanks www.movied.org


align repo with software project blueprint to comply with FINOS bylaws

Hi @martin-traverse,
Trying to send this PR to update the TRAC repo so that it complies with some FINOS requirements.
Is it possible to get this through? There's a lot of checks! Let me know if you have any questions.
-Juan

@TheJuanAndOnly99  - I had to approve as this was your first PR. Thanks for this, we've known for a while that we had these gaps!
We are currently running build, integration, packaging and compliance jobs before every merge to main, across all languages and a matrix of supported versions. I agree it's a lot of checks! It has the benefit of discovering issues early, but it does mean you have to solve e.g. new security vulnerabilities before committing even a very small fix.


Fix custom PageResource not being considered on Pages

Currently, if you define a custom Resource on filament-fabricator.php, this resource is not considered on the plugin Create, Edit, List, and View pages.
'page-resource' => \App\Models\PageResource::class,

This PR fixes this matter, adding the method below on every page:
public static function getResource(): string
{
    return config('filament-fabricator.page-resource') ?? static::$resource;
}

Thanks


Only trigger action on specific paths

This (Hopefully final) PR updates to action to only trigger if any of the following paths are altered in a PR:

Any files in docs/
Any files in overrides
mkdocs.yml
requirements.txt

Deploy Preview
Building preview of Pull request. Please wait...


z-index for location geometry layer

Currently the marker is drawn first with additional geometries as layer being drawn on top of the marker.
This isn't great.

Added to geometry docs.


problem with "data_dir" at starts...

I have download all images, and the directory created is "PetImages" with two subdirectorys called "Cat" and "Dog".
When I run this command: ..." datasets.ImageFolder(data_dir + '/train',..." , appear an error because don't found the path.
Can you help me, please?
Thanks.

The data has to be arranged this way:
root/dog/xxx.png
root/dog/xxy.png
root/dog/xxz.png
root/cat/123.png
root/cat/nsdf3.png
root/cat/asd932_.png
Check the documentation for torchvision.datasets.ImageFolder

The data has to be arranged this way
root/train/cats/cat0.jpg and so on (all your cat images)
root/train/dogs/ dog0.jpg and so on (all your dog images)
The same has to be done for test as well
check the documentation for torchvision.datasets.ImageFolder

Thanks for the answer @Adarshd19
Did that resolve your issue @Melendez95 ?