世事如棋

I confirm this issue. also using 20200818.0. speederv2.exe MD5 Checksum: 970253A0953585093C4F8B4C749B21EC SHA-1 Checksum: 252C9E36B9FEC7091B17954BA1082F8B451BF4EC SHA-256 Checksum: 18E2DA4FE88CDB7781F3AFCE4DC2421FBC8DA5E9B635996C638A215E7A249578 SHA-512 Checksum: 1CBD60E357FBF9F5F92E4A4B7E7B7304115FB6282716BE653274BD4EAAADB6DB76573750DCDDB634B2702D8283387ED0DC3A5DCD8412D880FF28A66AA948D278 See VirusTotal result: https://www.virustotal.com/gui/file/18e2da4fe88cdb7781f3afce4dc2421fbc8da5e9b635996c638a215e7a249578/detection Searching, there's a related question on...

Fyi, 4.1.3 and 4.1.4 was released and both are bug fix releases.

I believe this is just a one-line change in the `.spec` file so thought a maintainer can make a commit directly (otherwise he/she still has to review/approve a PR anyway)....

FYI I am now using the following scripts to deal with this issue (for stateful compute nodes). Feel free if you wish to add this into ohpc recipes. ``` [root@mgmt...

> So this problem only seen during discovery ? > Once the node definition is created, provisioning that node diskless or diskful is ok with those disks installed ? exactly....

I don't use IPMI/BMC so I tried `nodeset shell` instead, which should be the same thing. -- and yes, it's the same behavior. I tried going through both Legacy PXE...

we just found that when a dedicated GPU is installed and is used for video output, we can see there is a kernel panic related to nvme.

Hello. I am also seeing this and the workaround doesn't work. Can someone help? Below is the output of `openssl s_client -host vpn1.nsccwx.cn -port 4434` ``` CONNECTED(00000003) 140305714038080:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../ssl/statem/statem_lib.c:1941:...

I would prefer Windows native IME over ibus/fcitx. to be honest, despite their developers' hard work, which is very appreciated, IMEs on Linux have yet not reached the quality of...