Server failed to start on Ubuntu22.04

Type: Bug
The server used to be 18.04 and no longer supported because of the GLIBC version requirement. So we first upgraded the OS to 20.04, everything worked fine.
However, when the OS is upgraded again to 22.04, VSCode v1.86 just cannot connect to it and output nothing in the server log. We have tried v1.85, it still work.
How can I get more diagnostic infomation?
VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:28:19.990Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Connection to 'ssh-remote+2080' could not be established
Connection to 'SSH: 2080' could not be established  VS Code 服务器启动失败
Remote OS version: Linux x64 6.2.0-37-generic
Remote OS version: Linux x64 5.4.0-170-generic

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
47.72GB (24.22GB free)

Process Argv
--crash-reporter-id a3cc8086-87cf-48ed-8693-b47327f41a50

Screen Reader
no

VM
0%

Connection to 'ssh-remote+2080' could not be established
Connection to 'SSH: 2080' could not be established  VS Code 服务器启动失败

Item
Value

Remote
SSH: 2080

OS
Linux x64 6.2.0-37-generic

CPUs
Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz (64 x 800)

Memory (System)
251.49GB (241.95GB free)

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30951796
pythongtdpath:30769146
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019b:30953937
3ef8e399:30949928
e3gdj431:30956216

Please collect the "Remote - SSH" logs from the "Output" channel

I can confirm similar issue with below versions:
VS Code Version: 1.86.0
OS Version: Win Pro 11 23H2 Build 22631.3085
Remote SSH Host OS Version: Centos 7
Below is the "Remote - SSH" log output. I keep getting the error Waiting for server log... repeated until it fails and produces an error dialog with this message: Could not establish connection to "replacedSSHHostname": The VS Code Server failed to start.
I also see the warning dialog The remote host may not meet VS Code Server's prerequisites for glibc and libstdc++.
Upon further troubleshooting, The kernel version and glibc versions don't meet the minimum requirements from the vscode documentation site. Temporary fix is to revert to vscode version 1.85.2 which restores connectivity.
[09:13:50.816] Log Level: 2
[09:13:50.822] VS Code version: 1.86.0
[09:13:50.822] Remote-SSH version<EMAIL_ADDRESS>[09:13:50.822] win32 x64
[09:13:50.823] SSH Resolver called for "ssh-remote+replacedHOSTNAME", attempt 1
[09:13:50.823] "remote.SSH.useLocalServer": false
[09:13:50.823] "remote.SSH.useExecServer": false
[09:13:50.823] "remote.SSH.showLoginTerminal": false
[09:13:50.823] "remote.SSH.remotePlatform": {"replacedHOSTNAME":"linux","replacedHOSTNAME":"linux","cpp-ch-server":"linux"}
[09:13:50.824] "remote.SSH.path": undefined
[09:13:50.824] "remote.SSH.configFile": undefined
[09:13:50.824] "remote.SSH.useFlock": true
[09:13:50.824] "remote.SSH.lockfilesInTmp": false
[09:13:50.824] "remote.SSH.localServerDownload": auto
[09:13:50.824] "remote.SSH.remoteServerListenOnSocket": false
[09:13:50.824] "remote.SSH.showLoginTerminal": false
[09:13:50.824] "remote.SSH.defaultExtensions": []
[09:13:50.824] "remote.SSH.loglevel": 2
[09:13:50.824] "remote.SSH.enableDynamicForwarding": true
[09:13:50.824] "remote.SSH.enableRemoteCommand": false
[09:13:50.824] "remote.SSH.serverPickPortsFromRange": {}
[09:13:50.824] "remote.SSH.serverInstallPath": {}
[09:13:50.827] SSH Resolver called for host: replacedHOSTNAME
[09:13:50.827] Setting up SSH remote "replacedHOSTNAME"
[09:13:50.829] Using commit id "05047486b6df5eb8d44b2ecd70ea3bdf775fd937" and quality "stable" for server
[09:13:50.830] Install and start server if needed
[09:13:50.832] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[09:13:50.833] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[09:13:50.833] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[09:13:50.834] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[09:13:50.834] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[09:13:50.834] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[09:13:50.835] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[09:13:50.835] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[09:13:50.835] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[09:13:50.868] > OpenSSH_for_Windows_8.6p1
[09:13:50.868] > , LibreSSL 3.4.3

[09:13:50.872] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 63760 "replacedHOSTNAME" bash
[09:13:50.874] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[09:13:52.346] ><EMAIL_ADDRESS>password:]0;C:\WINDOWS\System32\cmd.exe
[09:13:52.346] Got some output, clearing connection timeout
[09:13:52.347] Showing password prompt
[09:13:56.493] Got password response
[09:13:56.493] "install" wrote data to terminal: "*******************"
[09:13:56.546] >
[09:13:57.711] > 8533d866f14e: running
[09:13:57.771] > Acquiring lock on /home/replacedUSERNAME/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/vscode-remote-lock.replacedUSERNAME.05047486b6df5eb8d44b2ecd70ea3bdf775fd937
> Found existing installation at /home/replacedUSERNAME/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937...
> Checking /home/replacedUSERNAME/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log and /home/replacedUSERNAME/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.pid for a running server
> Looking for server with pid: 6409
[09:13:57.780] > Running ssh connection command... /home/replacedUSERNAME/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/code-server --start-server --host=<IP_ADDRESS> --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --telemetry-level all   &> "/home/replacedUSERNAME/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log" < /dev/null
> printenv:
>     XDG_SESSION_ID=20
>     SELINUX_ROLE_REQUESTED=
>     SHELL=/bin/bash
>     SSH_CLIENT=replacedIPADDRESS 51267 22
>     SELINUX_USE_CURRENT_RANGE=
>     USER=replacedUSERNAME
>     SSH_AUTH_SOCK=/tmp/ssh-sH5X9uXo7d/agent.13492
>     VSCODE_AGENT_FOLDER=/home/replacedUSERNAME/.vscode-server
>     PATH=/usr/local/bin:/usr/bin
>     MAIL=/var/mail/replacedUSERNAME
>     PWD=/home/replacedUSERNAME
>     LANG=en_US.UTF-8
>     SELINUX_LEVEL_REQUESTED=
>     HOME=/home/replacedUSERNAME
>     SHLVL=2
>     LOGNAME=replacedUSERNAME
>     SSH_CONNECTION=replacedIPADDRESS 51267 replacedIPADDRESS 22
>     LESSOPEN=||/usr/bin/lesspipe.sh %s
>     XDG_RUNTIME_DIR=/run/user/20698
>     _=/usr/bin/printenv
> Removing old logfile at /home/replacedUSERNAME/.vscode-server/.05047486b6df5eb8d44b2ecd
> d70ea3bdf775fd937.log
> Spawned remote server: 13563
> Waiting for server log...
[09:13:57.796] >
[09:13:57.830] > Waiting for server log...
[09:13:57.846] >
[09:13:57.877] > Waiting for server log...
> Waiting for server log...
[09:13:57.911] >
[09:13:57.930] > Waiting for server log...
[09:13:57.945] >
[09:13:57.978] > Waiting for server log...
> Waiting for server log...
[09:13:58.012] >
[09:13:58.045] > Waiting for server log...
> Waiting for server log...
[09:13:58.079] >
[09:13:58.096] > Waiting for server log...

Your issue is unrelated https://github.com/microsoft/vscode/issues/203967#issuecomment-1923440629

same issue:
OS: Ubuntu 22.04.03
CPU: AMD EPYC 7702P 64-Core Processor
Virtualization features:
Virtualization:        AMD-V
Hypervisor vendor:     KVM
Virtualization type:   full
Version: 1.86.0 (user setup)
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
SSH Remote Log:
[11:53:15.972] Log Level: 2
[11:53:15.982] SSH Resolver called for "ssh-remote+XXX", attempt 1
[11:53:15.983] "remote.SSH.useLocalServer": false
[11:53:15.983] "remote.SSH.useExecServer": false
[11:53:15.983] "remote.SSH.showLoginTerminal": false
[11:53:15.983] "remote.SSH.remotePlatform": {"XXX":"linux","XXX":"linux","XXX":"linux"}
[11:53:15.983] "remote.SSH.path": undefined
[11:53:15.983] "remote.SSH.configFile": undefined
[11:53:15.984] "remote.SSH.useFlock": true
[11:53:15.984] "remote.SSH.lockfilesInTmp": false
[11:53:15.985] "remote.SSH.localServerDownload": auto
[11:53:15.985] "remote.SSH.remoteServerListenOnSocket": false
[11:53:15.985] "remote.SSH.showLoginTerminal": false
[11:53:15.985] "remote.SSH.defaultExtensions": []
[11:53:15.985] "remote.SSH.loglevel": 2
[11:53:15.985] "remote.SSH.enableDynamicForwarding": true
[11:53:15.985] "remote.SSH.enableRemoteCommand": false
[11:53:15.985] "remote.SSH.serverPickPortsFromRange": {}
[11:53:15.985] "remote.SSH.serverInstallPath": {}
[11:53:15.987] VS Code version: 1.86.0
[11:53:15.987] Remote-SSH version<EMAIL_ADDRESS>[11:53:15.987] win32 x64
[11:53:15.988] SSH Resolver called for host: XXX
[11:53:15.988] Setting up SSH remote "XXX"
[11:53:15.991] Using commit id "05047486b6df5eb8d44b2ecd70ea3bdf775fd937" and quality "stable" for server
[11:53:15.994] Install and start server if needed
[11:53:15.997] Checking ssh with "C:\Program Files\Common Files\Oracle\Java\javapath\ssh.exe -V"
[11:53:15.999] Got error from ssh: spawn C:\Program Files\Common Files\Oracle\Java\javapath\ssh.exe ENOENT
[11:53:15.999] Checking ssh with "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\bin\ssh.exe -V"
[11:53:16.000] Got error from ssh: spawn C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\bin\ssh.exe ENOENT
[11:53:16.000] Checking ssh with "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\libnvvp\ssh.exe -V"
[11:53:16.002] Got error from ssh: spawn C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\libnvvp\ssh.exe ENOENT
[11:53:16.002] Checking ssh with "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\ssh.exe -V"
[11:53:16.003] Got error from ssh: spawn C:\Program Files (x86)\Common Files\Oracle\Java\javapath\ssh.exe ENOENT
[11:53:16.003] Checking ssh with "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin\ssh.exe -V"
[11:53:16.004] Got error from ssh: spawn C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin\ssh.exe ENOENT
[11:53:16.004] Checking ssh with "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\libnvvp\ssh.exe -V"
[11:53:16.005] Got error from ssh: spawn C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\libnvvp\ssh.exe ENOENT
[11:53:16.005] Checking ssh with "C:\Program Files\Microsoft MPI\Bin\ssh.exe -V"
[11:53:16.006] Got error from ssh: spawn C:\Program Files\Microsoft MPI\Bin\ssh.exe ENOENT
[11:53:16.006] Checking ssh with "C:\ProgramData\Oracle\Java\javapath\ssh.exe -V"
[11:53:16.007] Got error from ssh: spawn C:\ProgramData\Oracle\Java\javapath\ssh.exe ENOENT
[11:53:16.007] Checking ssh with "C:\Windows\System32\ssh.exe -V"
[11:53:16.008] Got error from ssh: spawn C:\Windows\System32\ssh.exe ENOENT
[11:53:16.008] Checking ssh with "C:\Windows\ssh.exe -V"
[11:53:16.009] Got error from ssh: spawn C:\Windows\ssh.exe ENOENT
[11:53:16.009] Checking ssh with "C:\Windows\System32\wbem\ssh.exe -V"
[11:53:16.011] Got error from ssh: spawn C:\Windows\System32\wbem\ssh.exe ENOENT
[11:53:16.011] Checking ssh with "C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[11:53:16.012] Got error from ssh: spawn C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[11:53:16.012] Checking ssh with "C:\Program Files\PuTTY\ssh.exe -V"
[11:53:16.013] Got error from ssh: spawn C:\Program Files\PuTTY\ssh.exe ENOENT
[11:53:16.013] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V"
[11:53:16.043] > OpenSSH_for_Windows_8.6p1, LibreS
[11:53:16.043] > SL 3.4.3

[11:53:16.046] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 54435 "XXX" bash
[11:53:16.047] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[11:53:16.938] > 78f4bccdf1a0: running
> ]0;C:\WINDOWS\System32\cmd.exe
[11:53:16.938] Got some output, clearing connection timeout
[11:53:17.006] > Acquiring lock on /home/XXX/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/vscode-remote-lock.XXX.05047486b6df5eb8d44b2ecd70ea3bdf775fd937
> Found existing installation at /home/XXX/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937...
> Checking /home/XXX/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log and /home/XXX/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.pid for a running server
> Looking for server with pid: 19457
> Running ssh connection command... /home/XXX/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/code-server --start-server --host=<IP_ADDRESS> --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --telemetry-level all   &> "/home/XXX/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log" < /dev/null
> printenv:
>     SHELL=/bin/bash
>     PWD=/home/XXX
>     LOGNAME=XXX
>     XDG_SESSION_TYPE=tty
>     MOTD_SHOWN=pam
>     HOME=/home/XXX
>     LANG=C.UTF-8
>     VSCODE_AGENT_FOLDER=/home/XXX/.vscode-server
>     SSH_CONNECTION=XXX 54436 <IP_ADDRESS> 4620
>     XDG_SESSION_CLASS=user
>     USER=XXX
>     SHLVL=0
>     XDG_SESSION_ID=340
>     XDG_RUNTIME_DIR=/run/user/1000
>     SSH_CLIENT=XXX 54436 4620
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> s:/usr/local/games:/snap/bin
>     DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
>     _=/usr/bin/printenv
[11:53:17.030] >
> Removing old logfile at /home/XXX/.vscode-server/.05047486b6df5eb8d44b2ecd70e
> ea3bdf775fd937.log
> Spawned remote server: 26048
> Waiting for server log...
[11:53:17.060] > Waiting for server log...
[11:53:17.078] >
[11:53:17.092] > Waiting for server log...
[11:53:17.109] >
[11:53:17.117] > Waiting for server log...
[11:53:17.141] >
[11:53:17.156] > Waiting for server log...
[11:53:17.171] >
[11:53:17.187] > Waiting for server log...
[11:53:17.203] >
[11:53:17.219] > Waiting for server log...
[11:53:17.235] >
[11:53:17.250] > Waiting for server log...
[11:53:17.267] >
[11:53:17.282] > Waiting for server log...
[11:53:17.308] >
> Waiting for server log...
[11:53:17.328] >
[11:53:17.359] > Waiting for server log...
[11:53:17.373] >
[11:53:17.392] > Waiting for server log...
[11:53:17.423] > Waiting for server log...
[11:53:17.438] >
[11:53:17.454] > Waiting for server log...
[11:53:17.487] > Waiting for server log...
[11:53:17.503] >
[11:53:17.518] > Waiting for server log...
[11:53:17.533] >
[11:53:17.549] > Waiting for server log...
[11:53:17.565] >
[11:53:17.581] > Waiting for server log...
[11:53:17.597] >
[11:53:17.612] > Waiting for server log...
[11:53:17.628] >
[11:53:17.643] > Waiting for server log...
[11:53:17.659] >
[11:53:17.674] > Waiting for server log...
[11:53:17.699] >
[11:53:17.707] > Waiting for server log...
[11:53:17.721] >
[11:53:17.737] > Waiting for server log...
[11:53:17.765] >
[11:53:17.784] > Waiting for server log...
[11:53:17.817] > Waiting for server log...
[11:53:17.831] >
[11:53:17.847] > Waiting for server log...
[11:53:17.878] > Waiting for server log...
[11:53:17.893] >
[11:53:17.909] > Waiting for server log...
[11:53:17.925] >
[11:53:17.941] > Waiting for server log...
[11:53:17.957] >
[11:53:17.973] > Waiting for server log...
[11:53:17.988] >
[11:53:18.004] > Waiting for server log...
[11:53:18.037] >
> Waiting for server log...
[11:53:18.051] >
[11:53:18.068] > Waiting for server log...
[11:53:18.092] >
[11:53:18.098] > Waiting for server log...
[11:53:18.113] >
[11:53:18.144] > Waiting for server log...
[11:53:18.158] >
[11:53:18.177] > Waiting for server log...
[11:53:18.207] > Waiting for server log...
[11:53:18.253] >
> Waiting for server log...
[11:53:18.259] >
[11:53:18.268] > Waiting for server log...
[11:53:18.283] >
[11:53:18.299] > Waiting for server log...
[11:53:18.315] >
[11:53:18.330] > Waiting for server log...
[11:53:18.347] >
[11:53:18.365] > Waiting for server log...
[11:53:18.378] >
[11:53:18.395] > Waiting for server log...
[11:53:18.419] >
> Waiting for server log...
[11:53:18.441] >
[11:53:18.457] > Waiting for server log...
[11:53:18.485] >
[11:53:18.504] > Waiting for server log...
[11:53:18.535] > Waiting for server log...
[11:53:18.550] >
[11:53:18.567] > Waiting for server log...
[11:53:18.597] > Waiting for server log...
[11:53:18.634] >
> Waiting for server log...
[11:53:18.679] >
> Waiting for server log...
[11:53:18.748] >
> Waiting for server log...
[11:53:18.775] > Waiting for server log...
> Waiting for server log...
[11:53:18.795] >
> Waiting for server log...
[11:53:18.802] >
[11:53:18.875] > Waiting for server log...
> Waiting for server log...
[11:53:18.909] > Waiting for server log...
[11:53:18.925] > Waiting for server log...
[11:53:18.957] > Waiting for server log...
[11:53:18.971] >
[11:53:18.988] > Waiting for server log...
[11:53:19.003] >
[11:53:19.019] > Waiting for server log...
[11:53:19.035] >
[11:53:19.050] > Waiting for server log...
[11:53:19.067] >
[11:53:19.082] > Waiting for server log...
[11:53:19.098] >
[11:53:19.113] > Waiting for server log...
[11:53:19.138] >
[11:53:19.145] > Waiting for server log...
[11:53:19.160] >
[11:53:19.177] > Waiting for server log...
[11:53:19.204] >
[11:53:19.223] > Waiting for server log...
[11:53:19.253] > Waiting for server log...
[11:53:19.269] >
[11:53:19.284] > Waiting for server log...
[11:53:19.300] >
[11:53:19.316] > Waiting for server log...
[11:53:19.331] >
[11:53:19.348] > Waiting for server log...
[11:53:19.363] >
[11:53:19.378] > Waiting for server log...
[11:53:19.394] >
[11:53:19.409] > Waiting for server log...
[11:53:19.427] >
[11:53:19.442] > Waiting for server log...
[11:53:19.456] >
[11:53:19.472] > Waiting for server log...
[11:53:19.499] >
[11:53:19.518] > Waiting for server log...
[11:53:19.549] > Waiting for server log...
[11:53:19.563] >
[11:53:19.580] > Waiting for server log...
[11:53:19.613] > Waiting for server log...
[11:53:19.628] >
[11:53:19.643] > Waiting for server log...
[11:53:19.659] >
[11:53:19.676] > Waiting for server log...
[11:53:19.692] >
[11:53:19.707] > Waiting for server log...
[11:53:19.721] >
[11:53:19.737] > Waiting for server log...
[11:53:19.753] >
[11:53:19.769] > Waiting for server log...
[11:53:19.785] >
[11:53:19.801] > Waiting for server log...
[11:53:19.817] >
[11:53:19.832] > Waiting for server log...
[11:53:19.858] >
> Waiting for server log...
[11:53:19.881] >
[11:53:19.911] > Waiting for server log...
[11:53:19.924] >
[11:53:19.942] > Waiting for server log...
[11:53:19.974] > Waiting for server log...
[11:53:19.989] >
[11:53:20.007] > Waiting for server log...
[11:53:20.038] > Waiting for server log...
[11:53:20.053] >
[11:53:20.068] > Waiting for server log...
[11:53:20.083] >
[11:53:20.099] > Waiting for server log...
[11:53:20.115] >
[11:53:20.130] > Waiting for server log...
[11:53:20.146] >
[11:53:20.161] > Waiting for server log...
[11:53:20.178] >
[11:53:20.202] > Waiting for server log...
[11:53:20.209] >
[11:53:20.225] > Waiting for server log...
[11:53:20.251] >
[11:53:20.258] > Waiting for server log...
[11:53:20.272] >
[11:53:20.303] > Waiting for server log...
[11:53:20.319] >
[11:53:20.333] > Waiting for server log...
[11:53:20.365] > Waiting for server log...
[11:53:20.382] >
[11:53:20.396] > Waiting for server log...
[11:53:20.411] >
[11:53:20.427] > Waiting for server log...
[11:53:20.443] >
[11:53:20.459] > Waiting for server log...
[11:53:20.474] >
[11:53:20.490] > Waiting for server log...
[11:53:20.506] >
[11:53:20.522] > Waiting for server log...
[11:53:20.539] >
[11:53:20.552] > Waiting for server log...
[11:53:20.578] >
[11:53:20.583] > Waiting for server log...
[11:53:20.599] >
[11:53:20.631] > Waiting for server log...
[11:53:20.644] >
[11:53:20.661] > Waiting for server log...
[11:53:20.692] > Waiting for server log...
[11:53:20.707] >
[11:53:20.722] > Waiting for server log...
[11:53:20.736] >
[11:53:20.752] > Waiting for server log...
[11:53:20.768] >
[11:53:20.783] > Waiting for server log...
[11:53:20.799] >
[11:53:20.815] > Waiting for server log...
[11:53:20.831] >
[11:53:20.847] > Waiting for server log...
[11:53:20.872] >
[11:53:20.878] > Waiting for server log...
[11:53:20.893] >
[11:53:20.909] > Waiting for server log...
[11:53:20.936] >
[11:53:20.958] > Waiting for server log...
[11:53:20.989] > Waiting for server log...
[11:53:21.002] >
[11:53:21.019] > Waiting for server log...
[11:53:21.050] > Waiting for server log...
[11:53:21.068] >
[11:53:21.082] > Waiting for server log...
[11:53:21.098] >
[11:53:21.113] > Waiting for server log...
[11:53:21.128] >
[11:53:21.144] > Waiting for server log...
[11:53:21.159] >
[11:53:21.175] > Waiting for server log...
[11:53:21.195] >
[11:53:21.207] > Waiting for server log...
[11:53:21.223] >
[11:53:21.238] > Waiting for server log...
[11:53:21.253] >
[11:53:21.270] > Waiting for server log...
[11:53:21.295] >
[11:53:21.301] > Waiting for server log...
[11:53:21.318] >
[11:53:21.349] > Waiting for server log...
[11:53:21.361] >
[11:53:21.380] > Waiting for server log...
[11:53:21.413] > Waiting for server log...
[11:53:21.427] >
[11:53:21.442] > Waiting for server log...
[11:53:21.475] > Waiting for server log...
[11:53:21.490] >
[11:53:21.505] > Waiting for server log...
[11:53:21.521] >
[11:53:21.536] > Waiting for server log...
[11:53:21.551] >
[11:53:21.567] > Waiting for server log...
[11:53:21.582] >
[11:53:21.598] > Waiting for server log...
[11:53:21.623] >
[11:53:21.629] > Waiting for server log...
[11:53:21.643] >
[11:53:21.675] > Waiting for server log...
[11:53:21.688] >
[11:53:21.706] > Waiting for server log...
[11:53:21.739] > Waiting for server log...
[11:53:21.753] >
[11:53:21.769] > Waiting for server log...
[11:53:21.783] >
[11:53:21.799] > Waiting for server log...
[11:53:21.815] >
[11:53:21.830] > Waiting for server log...
[11:53:21.847] >
[11:53:21.862] > Waiting for server log...
[11:53:21.878] >
[11:53:21.894] > Waiting for server log...
[11:53:21.909] >
[11:53:21.925] > Waiting for server log...
[11:53:21.940] >
[11:53:21.957] > Waiting for server log...
[11:53:21.983] >
[11:53:21.988] > Waiting for server log...
[11:53:22.003] >
[11:53:22.034] > Waiting for server log...
[11:53:22.048] >
[11:53:22.067] > Waiting for server log...
[11:53:22.098] > Waiting for server log...
[11:53:22.113] >
[11:53:22.131] > Waiting for server log...
[11:53:22.162] > Waiting for server log...
[11:53:22.178] >
[11:53:22.194] > Waiting for server log...
[11:53:22.210] >
[11:53:22.225] > Waiting for server log...
[11:53:22.241] >
[11:53:22.257] > Waiting for server log...
[11:53:22.272] >
[11:53:22.288] > Waiting for server log...
[11:53:22.304] >
[11:53:22.320] > Waiting for server log...
[11:53:22.335] >
[11:53:22.350] > Waiting for server log...
[11:53:22.367] >
[11:53:22.383] > Waiting for server log...
[11:53:22.408] >
[11:53:22.413] > Waiting for server log...
[11:53:22.429] >
[11:53:22.459] > Waiting for server log...
[11:53:22.473] >
[11:53:22.491] > Waiting for server log...
[11:53:22.522] > Waiting for server log...
[11:53:22.539] >
[11:53:22.554] > Waiting for server log...
[11:53:22.585] > Waiting for server log...
[11:53:22.601] >
[11:53:22.617] > Waiting for server log...
[11:53:22.632] >
[11:53:22.649] > Waiting for server log...
[11:53:22.664] >
[11:53:22.680] > Waiting for server log...
[11:53:22.696] >
[11:53:22.712] > Waiting for server log...
[11:53:22.728] >
[11:53:22.743] > Waiting for server log...
[11:53:22.759] >
[11:53:22.775] > Waiting for server log...
[11:53:22.799] >
[11:53:22.807] > Waiting for server log...
[11:53:22.821] >
[11:53:22.839] > Waiting for server log...
[11:53:22.865] >
[11:53:22.885] > Waiting for server log...
[11:53:22.917] > Waiting for server log...
[11:53:22.931] >
[11:53:22.945] > Waiting for server log...
[11:53:22.981] > Waiting for server log...
[11:53:22.996] >
[11:53:23.012] > Waiting for server log...
[11:53:23.043] > Waiting for server log...
[11:53:23.059] >
[11:53:23.075] > Waiting for server log...
[11:53:23.091] >
[11:53:23.108] > Waiting for server log...
[11:53:23.122] >
[11:53:23.138] > Waiting for server log...
[11:53:23.154] >
[11:53:23.169] > Waiting for server log...
[11:53:23.185] >
[11:53:23.200] > Waiting for server log...
[11:53:23.217] >
[11:53:23.232] > Waiting for server log...
[11:53:23.249] >
[11:53:23.264] > Waiting for server log...
[11:53:23.289] >
[11:53:23.294] > Waiting for server log...
[11:53:23.311] >
[11:53:23.327] > Waiting for server log...
[11:53:23.355] >
[11:53:23.374] > Waiting for server log...
[11:53:23.406] > Waiting for server log...
[11:53:23.419] >
[11:53:23.437] > Waiting for server log...
[11:53:23.469] > Waiting for server log...
[11:53:23.484] >
[11:53:23.499] > Waiting for server log...
[11:53:23.515] >
[11:53:23.531] > Waiting for server log...
[11:53:23.547] >
[11:53:23.562] > Waiting for server log...
[11:53:23.579] >
[11:53:23.594] > Waiting for server log...
[11:53:23.609] >
[11:53:23.627] > Waiting for server log...
[11:53:23.641] >
[11:53:23.659] > Waiting for server log...
[11:53:23.673] >
[11:53:23.689] > Waiting for server log...
[11:53:23.714] >
[11:53:23.721] > Waiting for server log...
[11:53:23.737] >
[11:53:23.752] > Waiting for server log...
[11:53:23.779] >
> Waiting for server log...
[11:53:23.800] >
[11:53:23.832] > Waiting for server log...
[11:53:23.845] >
[11:53:23.863] > Waiting for server log...
[11:53:23.894] > Waiting for server log...
[11:53:23.909] >
[11:53:23.925] > Waiting for server log...
[11:53:23.942] >
[11:53:23.957] > Waiting for server log...
[11:53:23.972] >
[11:53:23.989] > Waiting for server log...
[11:53:24.006] >
[11:53:24.023] > Waiting for server log...
[11:53:24.039] >
[11:53:24.052] > Waiting for server log...
[11:53:24.069] >
[11:53:24.084] > Waiting for server log...
[11:53:24.100] >
[11:53:24.116] > Waiting for server log...
[11:53:24.131] >
[11:53:24.147] > Waiting for server log...
[11:53:24.162] >
[11:53:24.179] > Waiting for server log...
[11:53:24.204] >
[11:53:24.210] > Waiting for server log...
[11:53:24.225] >
[11:53:24.242] > Waiting for server log...
[11:53:24.269] >
[11:53:24.289] > Waiting for server log...
[11:53:24.320] > Waiting for server log...
[11:53:24.334] >
[11:53:24.352] > Waiting for server log...
[11:53:24.383] > Waiting for server log...
[11:53:24.400] >
[11:53:24.416] > Waiting for server log...
[11:53:24.447] > Waiting for server log...
[11:53:24.461] >
[11:53:24.478] > Waiting for server log...
[11:53:24.495] >
[11:53:24.509] > Waiting for server log...
[11:53:24.524] >
[11:53:24.541] > Waiting for server log...
[11:53:24.556] >
[11:53:24.571] > Waiting for server log...
[11:53:24.589] >
[11:53:24.603] > Waiting for server log...
[11:53:24.629] >
> Waiting for server log...
[11:53:24.650] >
[11:53:24.681] > Waiting for server log...
[11:53:24.695] >
[11:53:24.713] > Waiting for server log...
[11:53:24.747] > Waiting for server log...
[11:53:24.760] >
[11:53:24.777] > Waiting for server log...
[11:53:24.809] > Waiting for server log...
[11:53:24.824] >
[11:53:24.839] > Waiting for server log...
[11:53:24.856] >
[11:53:24.870] > Waiting for server log...
[11:53:24.886] >
[11:53:24.902] > Waiting for server log...
[11:53:24.918] >
[11:53:24.933] > Waiting for server log...
[11:53:24.949] >
[11:53:24.965] > Waiting for server log...
[11:53:24.980] >
[11:53:24.996] > Waiting for server log...
[11:53:25.012] >
[11:53:25.029] > Waiting for server log...
[11:53:25.053] >
[11:53:25.061] > Waiting for server log...
[11:53:25.075] >
[11:53:25.106] > Waiting for server log...
[11:53:25.119] >
[11:53:25.139] > Waiting for server log...
[11:53:25.169] > Waiting for server log...
[11:53:25.185] >
[11:53:25.201] > Waiting for server log...
[11:53:25.232] > Waiting for server log...
[11:53:25.248] >
[11:53:25.263] > Waiting for server log...
[11:53:25.279] >
[11:53:25.295] > Waiting for server log...
[11:53:25.310] >
[11:53:25.327] > Waiting for server log...
[11:53:25.342] >
[11:53:25.358] > Waiting for server log...
[11:53:25.373] >
[11:53:25.389] > Waiting for server log...
[11:53:25.406] >
[11:53:25.420] > Waiting for server log...
[11:53:25.446] >
[11:53:25.452] > Waiting for server log...
[11:53:25.468] >
[11:53:25.499] > Waiting for server log...
[11:53:25.511] >
[11:53:25.530] > Waiting for server log...
[11:53:25.562] > Waiting for server log...
[11:53:25.577] >
[11:53:25.594] > Waiting for server log...
[11:53:25.625] > Waiting for server log...
[11:53:25.641] >
[11:53:25.658] > Waiting for server log...
[11:53:25.672] >
[11:53:25.689] > Waiting for server log...
[11:53:25.706] >
[11:53:25.720] > Waiting for server log...
[11:53:25.737] >
[11:53:25.752] > Waiting for server log...
[11:53:25.768] >
[11:53:25.783] > Waiting for server log...
[11:53:25.798] >
[11:53:25.813] > Waiting for server log...
[11:53:25.829] >
[11:53:25.845] > Waiting for server log...
[11:53:25.871] >
[11:53:25.876] > Waiting for server log...
[11:53:25.891] >
[11:53:25.922] > Waiting for server log...
[11:53:25.937] >
[11:53:25.955] > Waiting for server log...
[11:53:25.987] > Waiting for server log...
[11:53:26.001] >
[11:53:26.017] > Waiting for server log...
[11:53:26.032] >
[11:53:26.048] > Waiting for server log...
[11:53:26.063] >
[11:53:26.079] > Waiting for server log...
[11:53:26.095] >
[11:53:26.111] > Waiting for server log...
[11:53:26.127] >
[11:53:26.142] > Waiting for server log...
[11:53:26.159] >
[11:53:26.174] > Waiting for server log...
[11:53:26.191] >
[11:53:26.206] > Waiting for server log...
[11:53:26.221] >
[11:53:26.239] > Waiting for server log...
[11:53:26.253] >
[11:53:26.268] > Waiting for server log...
[11:53:26.294] >
[11:53:26.300] > Waiting for server log...
[11:53:26.315] >
[11:53:26.347] > Waiting for server log...
[11:53:26.359] >
[11:53:26.379] > Waiting for server log...
[11:53:26.409] > Waiting for server log...
[11:53:26.425] >
[11:53:26.441] > Waiting for server log...
[11:53:26.472] > Waiting for server log...
[11:53:26.489] >
[11:53:26.504] > Waiting for server log...
[11:53:26.519] >
[11:53:26.535] > Waiting for server log...
[11:53:26.551] >
[11:53:26.567] > Waiting for server log...
[11:53:26.582] >
[11:53:26.598] > Waiting for server log...
[11:53:26.615] >
[11:53:26.630] > Waiting for server log...
[11:53:26.647] >
[11:53:26.662] > Waiting for server log...
[11:53:26.678] >
[11:53:26.693] > Waiting for server log...
[11:53:26.719] >
[11:53:26.725] > Waiting for server log...
[11:53:26.741] >
[11:53:26.757] > Waiting for server log...
[11:53:26.784] >
[11:53:26.802] > Waiting for server log...
[11:53:26.834] > Waiting for server log...
[11:53:26.850] >
[11:53:26.867] > Waiting for server log...
[11:53:26.897] > Waiting for server log...
[11:53:26.912] >
[11:53:26.927] > Waiting for server log...
[11:53:26.942] >
[11:53:26.959] > Waiting for server log...
[11:53:26.974] >
[11:53:26.990] > Waiting for server log...
[11:53:27.006] >
[11:53:27.021] > Waiting for server log...
[11:53:27.039] >
[11:53:27.053] > Waiting for server log...
[11:53:27.080] >
[11:53:27.085] > Waiting for server log...
[11:53:27.100] >
[11:53:27.131] > Waiting for server log...
[11:53:27.143] >
[11:53:27.162] > Waiting for server log...
[11:53:27.192] > Waiting for server log...
[11:53:27.209] >
[11:53:27.224] > Waiting for server log...
[11:53:27.241] >
[11:53:27.256] > Waiting for server log...
[11:53:27.271] >
[11:53:27.287] > Waiting for server log...
[11:53:27.302] >
[11:53:27.318] > Waiting for server log...
[11:53:27.333] >
[11:53:27.349] > Waiting for server log...
[11:53:27.365] >
[11:53:27.381] > Waiting for server log...
[11:53:27.397] >
[11:53:27.412] > Waiting for server log...
[11:53:27.439] >
> Waiting for server log...
[11:53:27.460] >
[11:53:27.476] > Waiting for server log...
[11:53:27.503] >
[11:53:27.522] > Waiting for server log...
[11:53:27.555] > Waiting for server log...
[11:53:27.569] >
[11:53:27.587] > Waiting for server log...
[11:53:27.618] > Waiting for server log...
[11:53:27.633] >
[11:53:27.649] > Waiting for server log...
[11:53:27.664] >
[11:53:27.680] > Waiting for server log...
[11:53:27.697] >
[11:53:27.711] > Waiting for server log...
[11:53:27.729] >
[11:53:27.743] > Waiting for server log...
[11:53:27.759] >
[11:53:27.775] > Waiting for server log...
[11:53:27.790] >
[11:53:27.808] > Waiting for server log...
[11:53:27.822] >
[11:53:27.839] > Waiting for server log...
[11:53:27.863] >
[11:53:27.869] > Waiting for server log...
[11:53:27.884] >
[11:53:27.916] > Waiting for server log...
[11:53:27.929] >
[11:53:27.943] > Waiting for server log...
[11:53:27.978] > Waiting for server log...
[11:53:27.993] >
[11:53:28.010] > Waiting for server log...
[11:53:28.025] >
[11:53:28.041] > Waiting for server log...
[11:53:28.057] >
[11:53:28.071] > Waiting for server log...
[11:53:28.087] >
[11:53:28.103] > Waiting for server log...
[11:53:28.118] >
[11:53:28.133] > Waiting for server log...
[11:53:28.149] >
[11:53:28.165] > Waiting for server log...
[11:53:28.190] >
[11:53:28.197] > Waiting for server log...
[11:53:28.212] >
[11:53:28.229] > Waiting for server log...
[11:53:28.256] >
[11:53:28.275] > Waiting for server log...
[11:53:28.307] > Waiting for server log...
[11:53:28.322] >
[11:53:28.339] > Waiting for server log...
[11:53:28.369] > Waiting for server log...
[11:53:28.384] >
[11:53:28.400] > Waiting for server log...
[11:53:28.416] >
[11:53:28.431] > Waiting for server log...
[11:53:28.448] >
[11:53:28.463] > Waiting for server log...
[11:53:28.479] >
[11:53:28.495] > Waiting for server log...
[11:53:28.510] >
[11:53:28.527] > Waiting for server log...
[11:53:28.542] >
[11:53:28.559] > Waiting for server log...
[11:53:28.583] >
[11:53:28.591] > Waiting for server log...
[11:53:28.606] >
[11:53:28.622] > Waiting for server log...
[11:53:28.649] >
> Waiting for server log...
[11:53:28.669] >
[11:53:28.700] > Waiting for server log...
[11:53:28.715] >
[11:53:28.731] > Waiting for server log...
[11:53:28.762] > Waiting for server log...
[11:53:28.779] >
[11:53:28.794] > Waiting for server log...
[11:53:28.809] >
[11:53:28.825] > Waiting for server log...
[11:53:28.841] >
[11:53:28.857] > Waiting for server log...
[11:53:28.872] >
[11:53:28.889] > Waiting for server log...
[11:53:28.905] >
[11:53:28.919] > Waiting for server log...
[11:53:28.936] >
[11:53:28.951] > Waiting for server log...
[11:53:28.967] >
[11:53:28.982] > Waiting for server log...
[11:53:29.008] >
> Waiting for server log...
[11:53:29.029] >
[11:53:29.047] > Waiting for server log...
[11:53:29.075] >
[11:53:29.093] > Waiting for server log...
[11:53:29.124] > Waiting for server log...
[11:53:29.139] >
[11:53:29.156] > Waiting for server log...
[11:53:29.189] > Waiting for server log...
[11:53:29.203] >
[11:53:29.219] > Waiting for server log...
[11:53:29.234] >
[11:53:29.250] > Waiting for server log...
[11:53:29.266] >
[11:53:29.281] > Waiting for server log...
[11:53:29.298] >
[11:53:29.313] > Waiting for server log...
[11:53:29.330] >
[11:53:29.347] > Waiting for server log...
[11:53:29.362] >
[11:53:29.377] > Waiting for server log...
[11:53:29.392] >
[11:53:29.409] > Waiting for server log...
[11:53:29.424] >
[11:53:29.441] > Waiting for server log...
[11:53:29.466] >
> Waiting for server log...
[11:53:29.488] >
[11:53:29.503] > Waiting for server log...
[11:53:29.531] >
[11:53:29.550] > Waiting for server log...
[11:53:29.580] > Waiting for server log...
[11:53:29.597] >
[11:53:29.612] > Waiting for server log...
[11:53:29.644] > Waiting for server log...
[11:53:29.660] >
[11:53:29.676] > Waiting for server log...
[11:53:29.691] >
[11:53:29.709] > Waiting for server log...
[11:53:29.723] >
[11:53:29.739] > Waiting for server log...
[11:53:29.757] >
[11:53:29.771] > Waiting for server log...
[11:53:29.787] >
[11:53:29.802] > Waiting for server log...
[11:53:29.819] >
[11:53:29.834] > Waiting for server log...
[11:53:29.851] >
[11:53:29.866] > Waiting for server log...
[11:53:29.881] >
[11:53:29.898] > Waiting for server log...
[11:53:29.923] >
[11:53:29.929] > Waiting for server log...
[11:53:29.945] >
[11:53:29.961] > Waiting for server log...
[11:53:29.988] >
[11:53:30.008] > Waiting for server log...
[11:53:30.041] > Waiting for server log...
[11:53:30.054] >
[11:53:30.072] > Waiting for server log...
[11:53:30.104] > Waiting for server log...
[11:53:30.119] >
[11:53:30.134] > Waiting for server log...
[11:53:30.167] > Waiting for server log...
[11:53:30.181] >
[11:53:30.212] > Waiting for server log...
[11:53:30.229] > Waiting for server log...
[11:53:30.244] >
[11:53:30.260] > Waiting for server log...
[11:53:30.277] >
[11:53:30.292] > Waiting for server log...
[11:53:30.307] >
[11:53:30.323] > Waiting for server log...
[11:53:30.339] >
[11:53:30.356] > Waiting for server log...
[11:53:30.380] >
[11:53:30.387] > Waiting for server log...
[11:53:30.402] >
[11:53:30.433] > Waiting for server log...
[11:53:30.447] >
[11:53:30.465] > Waiting for server log...
[11:53:30.496] > Waiting for server log...
[11:53:30.511] >
[11:53:30.528] > Waiting for server log...
[11:53:30.559] > Waiting for server log...
[11:53:30.573] >
[11:53:30.589] > Waiting for server log...
[11:53:30.604] >
[11:53:30.619] > Waiting for server log...
[11:53:30.635] >
[11:53:30.652] > Waiting for server log...
[11:53:30.668] >
[11:53:30.682] > Waiting for server log...
[11:53:30.708] >
[11:53:30.713] > Waiting for server log...
[11:53:30.729] >
[11:53:30.745] > Waiting for server log...
[11:53:30.774] >
[11:53:30.793] > Waiting for server log...
[11:53:30.823] > Waiting for server log...
[11:53:30.839] >
[11:53:30.856] > Waiting for server log...
[11:53:30.886] > Waiting for server log...
[11:53:30.901] >
[11:53:30.917] > Waiting for server log...
[11:53:30.932] >
[11:53:30.948] > Waiting for server log...
[11:53:30.963] >
[11:53:30.979] > Waiting for server log...
[11:53:30.995] >
[11:53:31.010] > Waiting for server log...
[11:53:31.027] >
[11:53:31.042] > Waiting for server log...
[11:53:31.068] >
[11:53:31.074] > Waiting for server log...
[11:53:31.090] >
[11:53:31.105] >
> *
> * Visual Studio Code Server
> *
> * By using the software, you agree to
> * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-lice
> ense) and
> * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacyst
> tatement).
> *
>
> Server did not start successfully. Full server log at /home/XXX/.vscode-serve
> er/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log >>>
[11:53:31.114] >
> <<< End of server log
> 78f4bccdf1a0: start
> exitCode==32==
> listeningOn====
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/run/user/1000==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> extInstallTime====
> serverStartTime==14092==
> 78f4bccdf1a0: end
[11:53:31.114] Received install output:
exitCode==32==
listeningOn====
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime==14092==

[11:53:31.116] Resolver error: Error: The VS Code Server failed to start
	at g.ServerInstallError (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:642637)
	at d (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:636024)
	at t.handleInstallOutput (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:638294)
	at t.tryInstall (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:761983)
	at async c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:722522
	at async t.withShowDetailsEvent (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:725828)
	at async I (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:719493)
	at async t.resolve (c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:723199)
	at async c:\Users\XXX\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:907003
[11:53:31.122] ------

[11:53:31.564] >
[11:53:32.384] "install" terminal command done
[11:53:32.384] Install terminal quit with output:

@MoonShiesty your issue is also unrelated, see my previous comment.

@MoonShiesty your issue is also unrelated, see my previous comment.

unrelated to what? i believe the issue was caused by the 1.86.0 release - i've been using ubuntu 22.04 + vscode remote ssh on this box for months, and the latest update broke the ssh remote extension

Please collect the "Remote - SSH" logs from the "Output" channel

Here is the log where I deleted hundreds of Waiting for server log...
[14:19:36.403] Log Level: 2
[14:19:36.425] SSH Resolver called for "ssh-remote+2080", attempt 1
[14:19:36.426] "remote.SSH.useLocalServer": false
[14:19:36.426] "remote.SSH.useExecServer": false
[14:19:36.427] "remote.SSH.showLoginTerminal": false
[14:19:36.427] "remote.SSH.remotePlatform": {"2080":"linux"}
[14:19:36.428] "remote.SSH.path": undefined
[14:19:36.429] "remote.SSH.configFile": undefined
[14:19:36.430] "remote.SSH.useFlock": true
[14:19:36.430] "remote.SSH.lockfilesInTmp": false
[14:19:36.430] "remote.SSH.localServerDownload": auto
[14:19:36.430] "remote.SSH.remoteServerListenOnSocket": false
[14:19:36.430] "remote.SSH.showLoginTerminal": false
[14:19:36.431] "remote.SSH.defaultExtensions": []
[14:19:36.431] "remote.SSH.loglevel": 2
[14:19:36.431] "remote.SSH.enableDynamicForwarding": true
[14:19:36.431] "remote.SSH.enableRemoteCommand": false
[14:19:36.431] "remote.SSH.serverPickPortsFromRange": {}
[14:19:36.431] "remote.SSH.serverInstallPath": {}
[14:19:36.435] VS Code version: 1.86.0
[14:19:36.435] Remote-SSH version<EMAIL_ADDRESS>[14:19:36.435] win32 x64
[14:19:36.441] SSH Resolver called for host: 2080
[14:19:36.441] Setting up SSH remote "2080"
[14:19:36.446] Using commit id "05047486b6df5eb8d44b2ecd70ea3bdf775fd937" and quality "stable" for server
[14:19:36.451] Install and start server if needed
[14:19:36.458] Checking ssh with "C:\Windows\system32\ssh.exe -V"
[14:19:36.460] Got error from ssh: spawn C:\Windows\system32\ssh.exe ENOENT
[14:19:36.460] Checking ssh with "C:\Windows\ssh.exe -V"
[14:19:36.461] Got error from ssh: spawn C:\Windows\ssh.exe ENOENT
[14:19:36.461] Checking ssh with "C:\Windows\System32\Wbem\ssh.exe -V"
[14:19:36.462] Got error from ssh: spawn C:\Windows\System32\Wbem\ssh.exe ENOENT
[14:19:36.463] Checking ssh with "C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[14:19:36.464] Got error from ssh: spawn C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[14:19:36.464] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V"
[14:19:36.535] > OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

[14:19:36.543] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 34778 2080 bash
[14:19:36.547] Terminal shell path: C:\Windows\System32\cmd.exe
[14:19:37.541] ><EMAIL_ADDRESS>password:]0;C:\Windows\System32\cmd.exe
[14:19:37.541] Got some output, clearing connection timeout
[14:19:37.542] Showing password prompt
[14:19:40.894] Got password response
[14:19:40.894] "install" wrote data to terminal: "********"
[14:19:40.939] >
[14:19:41.528] > eea9bf829c27: running
[14:19:41.574] > Acquiring lock on /home/user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/vscode-remote-lock.user.05047486b6df5eb8d44b2ecd70ea3bdf775fd937
> Found existing installation at /home/user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937...
> Checking /home/user/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log and /home/user/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.pid for a running server
> Looking for server with pid: 46212
[14:19:41.596] > Starting VS Code Server... "/home/user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/code-server" --start-server --host=<IP_ADDRESS> --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --telemetry-level all   &> "/home/user/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log" < /dev/null
> The VS Code Server log file is /home/user/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log
> printenv:
>     SHELL=/bin/bash
>     LANGUAGE=zh_CN:zh
>     PWD=/home/user
>     LOGNAME=user
>     XDG_SESSION_TYPE=tty
>     MOTD_SHOWN=pam
>     HOME=/home/user
>     LANG=zh_CN.UTF-8
>     VSCODE_AGENT_FOLDER=/home/user/.vscode-server
>     SSH_CONNECTION=<IP_ADDRESS> 34782 <IP_ADDRESS> 22
>     XDG_SESSION_CLASS=user
>     USER=user
>     SHLVL=0
>     XDG_SESSION_ID=350
>     XDG_RUNTIME_DIR=/run/user/1009
>     SSH_CLIENT=<IP_ADDRESS> 34782 22
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> s:/usr/local/games:/snap/bin
>     DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1009/bus
>     _=/usr/bin/printenv
[14:19:41.603] >
> Removing old logfile at /home/user/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3b
> bdf775fd937.log
> Spawned remote server: 310881
[14:19:41.619] >
> Waiting for server log...
[14:19:41.649] > Waiting for server log...
[14:19:41.665] >
[14:19:41.680] > Waiting for server log...
[14:19:46.203] >
> Waiting for server log...
[14:19:46.212] >
[14:19:46.243] > Waiting for server log...
[14:19:46.258] >
> Waiting for server log...
[14:19:56.098] >
[14:19:56.112] > Waiting for server log...
[14:19:56.131] >
[14:19:56.158] > Waiting for server log...
[14:19:56.173] >
[14:19:56.190] > Waiting for server log...
[14:19:56.205] >
[14:19:56.221] > Waiting for server log...
[14:19:56.237] >
[14:19:56.252] >
> *
> * Visual Studio Code Server
> *
> * By using the software, you agree to
> * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-lice
> ense) and
> * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacyst
> tatement).
> *
>
[14:19:56.267] >
> Server did not start successfully. Full server log at /home/user/.vscode-server/.
> .05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log >>>
> <<< End of server log
> eea9bf829c27: start
> exitCode==32==
> listeningOn====
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
[14:19:56.282] >
[14:19:56.313] > bitness==64==
> tmpDir==/run/user/1009==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> extInstallTime====
> serverStartTime==14656==
> eea9bf829c27: end
[14:19:56.313] Received install output:
exitCode==32==
listeningOn====
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1009==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime==14656==

[14:19:56.315] Resolver error: Error: VS Code 服务器启动失败
	at g.ServerInstallError (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:460179)
	at d (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:453522)
	at t.handleInstallOutput (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:455792)
	at t.tryInstall (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:581100)
	at async c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:540958
	at async t.withShowDetailsEvent (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:544264)
	at async k (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:537923)
	at async t.resolve (c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:541635)
	at async c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-ssh-0.108.0\out\extension.js:2:807794
[14:19:56.322] ------

[14:19:56.582] >
[14:19:57.618] "install" terminal command done
[14:19:57.619] Install terminal quit with output:

@MoonShiesty your issue is also unrelated, see my previous comment.

if you read my comment, the linked issue is clearly unrelated. my issue is definitely not caused an out-of-date glibc (ubuntu 22 + no warning dialog like the linked issue)
i believe the issue was caused by the 1.86.0 release - i've been using ubuntu 22.04 + vscode remote ssh on this box for months - zero issues: the latest update clearly broke my ssh remote extension, and the linked workaround is unrelated to my issue (although downgrading does fix the issue)

Yes I think you are suffering the same issue as I do.
However I have another server running 22.04, and 1.86.0 works well on it. The main difference between the two servers is that the first one was newly upgraded which ran into this issue, and the latter one has 22.04 installed originally for months. So this issue might be caused by a specific version of a lib or something like that.

I am seeing this on Raspberry Pi OS Desktop (PC) exactly the same remote SSH log entries with the same waiting for log messages(lots of them), Resolver error, nothing in the .log file on the server side. Worked fine for months until recently. Not sure how to downgrade the "server" side, tried replacing the most recent code-nnnnn file with an older one, but that doesn't help either. Not sure how to "downgrade" the server side the right way. Can post remote SSH log if it would help.

@DougWilkinson
I uninstalled the vscode from the remote box (i think rm -rf ~/.vscode) and then downgraded by desktop vs-code, then turned off auto-update, then reinstalled the remote extension and it worked again.
I don't see any support from vs-code, but its free software, what can you do except switch to jetbrains

@connor4312 can you take another look at this issue?

I'm seeing this behaviour. In my case it's Snap version of VSCode on Ubuntu 22.04.
Start up VSCode and get an error like Error: /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by /lib/x86_64-linux-gnu/libstdc++.so.6)`
I uninstall extensions C# Dev Kit and C#, restart VSCode, reinstall the extensions, restart VSCode again and all is well again. Any simpler workaround or fix for this?

Hey @roblourens @connor4312, this issue might need further attention.
@Sciroccogti, you can help us out by closing this issue if the problem no longer exists, or adding more information.

I am also having this issue. The latest version of VSCode and ubuntu 22.04 don't seem to be compatible. I had to downgrade to version 1.85.2 to get the remote extension to work again.

Issue has multiple scenarios reported and we have also had various fixes landed in the server since the original issue was made. Can users confirm if the issue is present with v1.91.1 and latest ssh extension, attach the relevant logs. Thanks!

Sure, it is working well now, thx a lot! Sorry for the late response.


Should Ruby files in bin/config dir be excluded?

Should Ruby files in bin config directory be excluded so that we can upgrade rails easily.

closed by https://github.com/toshimaru/rubocop-rails_config/pull/18


Uncaught SyntaxError: The requested module '/node_modules/.vite/accounting-js.js?v=ebd463f2' does not provide an export named 'default

I have added the following configuration,still
Uncaught SyntaxError: The requested module '/node_modules/.vite/accounting-js.js?v=ebd463f2' does not provide an export named 'default
let optimizeDeps = {
include: ['accounting-js']
};
this is my "vite": "^2.1.0",

commonjsOptions: {
exclude: ['accounting-js/*'],
},
is not used

let alias = {
'accounting-js': 'accounting-js/dist/accounting.es6.js' is not used

}

Closing this issue because the issue template was not respected. Please create a new one that includes a minimal reproduction so it is easier for others to debug the problem. Also please respect the Before submitting the issue, please make sure you do the following and tick the checkboxes so we know that you read the contribution guidelines and further documentation.

Hi,
same error message occurred in v2.4.0-beta.1:Uncaught SyntaxError: The requested module '/node_modules/.vite/vue.js?v=e5663ae3' does not provide an export named 'createBlock'

Please open a new issue with a proper reproduction

Hi,
tried v2.4.0-beta.2, It's ok now.

Hi,
tried v2.4.0-beta.2, It's ok now.

thanks,softboy


chore: update restart docs for protocol upgrade

To add some further detail for protocol upgrades to try and mitigate node operators using unsafe-reset-all during a protocol upgrade.
close #577 .
@karlem @daniel1302 - please can you review what has been added here? I have a few questions:

does this apply to ONLY users not running Visor (i.e. will Visor do all this for them if they are using it)
should we capture a final step that says "if you see X, Y, Z in the logs the nodes are running as expected" so node operators can validate all went swimmingly

From my point of view the steps looks correct. This is exactly what Visor does in automated way.

@candida-d @karlem - I have addressed the comments and think these are now OK but would appreciate a re-review

@gordsport  ok I have made the update

@karlem, is there an automated way of detecting if it is already time for an update?
Something better than looking/grepping logs.
If yes, maybe we can give a hit on how it can be done. Or at least a sentence about how visor does it.
Please note that some node operators can't use visor for different reasons.

@fkondej yes they could be calling the JSON RPC admin API on the core node to get the status as well.

I think it would be also good to know why validators cannot use Visor. Perhaps we could solve some of their problems by adding more features or something?

There is nothing we can do. They have their own infrastructure to manage running services. Others are using docker. Others just won't use it.
I see two major problems for someone not using a visor:

When running core + data-node, the core does not stop when data-node fails/stops. This is a major problem, cos the core advanced with blocks, leaving the data-node behind. There is no reason for the core to work in this situation.
Lack of guidance on how to automate/improve the Protocol Upgrade process.


Uri to display and send to server

Hi, how do i use the uri return from createPdf  to display it in react-native-pdf and use the path and send to server.
I try add "file://", is not working.
res i get from createPdf
"/tree/primary:Documents/document/primary:Documents/594w-842h-contain (9).pdf"

is this in android or ios?

Fixed with latest version.

Is on android


Subaddress support

Question description
Does mymonero support subaddresses? Should I add a feature request?

Currently we dont support subaddresses.
A large amount of work has been put in to support it in the future but at this time it still is in progress


border and background image

How to modify the background image？How to add borders？

Hi,
The control is a subclass of UIControl, so you should be able to set a background image or borders in the same way you would with a normal UIView. Let me know if that doesn't work!


All level files are 2MB

We're trying to use goleveldb for @perkeep but @mpl and I have noticed performance problems over time.
My index in goleveldb is 1.3GB, but every level has files that are about 2MB:
bard:leveldb-weird $ du -h .
1.3G    .

bard:leveldb-weird $ ls -l *.ldb | wc -l
767

bard:leveldb-weird $ ls -l | sort -k5 -n | tail -10
-rw-r--r-- 1 bradfitz bradfitz 2322555 Apr 21 20:58 069086.ldb
-rw-r--r-- 1 bradfitz bradfitz 2323338 Apr 21 20:58 069090.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324125 Apr 21 20:58 069089.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324145 Apr 21 20:58 069095.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324431 Apr 21 20:58 069093.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324465 Apr 21 20:58 069094.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324656 Apr 21 20:58 069088.ldb
-rw-r--r-- 1 bradfitz bradfitz 2324715 Apr 21 20:58 069091.ldb
-rw-r--r-- 1 bradfitz bradfitz 2325053 Apr 21 20:58 069092.ldb
-rw-r--r-- 1 bradfitz bradfitz 4619241 Apr 20 10:44 LOG.old

bard:leveldb-weird $ go run ~/leveldb.go .
2018/04/22 11:44:16.588499 start
2018/04/22 11:44:16.709327 opened = *leveldb.DB
2018/04/22 11:44:16.709348 files at level0 = 0
2018/04/22 11:44:16.709353 files at level1 = 70
2018/04/22 11:44:16.709358 files at level2 = 593
2018/04/22 11:44:16.709374 files at level3 = 104
2018/04/22 11:44:16.709378 files at level4 = 0
2018/04/22 11:44:16.709749 closed

If I compact it all, I get 617 2MB files at level3:
2018/04/22 11:43:12.808138 start
2018/04/22 11:43:12.820236 opened = *leveldb.DB
2018/04/22 11:43:12.820258 files at level0 = 0
2018/04/22 11:43:12.820266 files at level1 = 0
2018/04/22 11:43:12.820276 files at level2 = 0
2018/04/22 11:43:12.820288 files at level3 = 617
2018/04/22 11:43:12.820300 files at level4 = 0
2018/04/22 11:43:12.820592 closed

We are opening it with all the default Options. We specify no options values.
The docs at https://godoc.org/github.com/syndtr/goleveldb/leveldb/opt#Options.CompactionTableSize say:
    // CompactionTableSize limits size of 'sorted table' that compaction generates.
    // The limits for each level will be calculated as:
    //   CompactionTableSize * (CompactionTableSizeMultiplier ^ Level)
    // The multiplier for each level can also fine-tuned using CompactionTableSizeMultiplierPerLevel.
    //
    // The default value is 2MiB.
    CompactionTableSize int

That suggests that level0 should be 2MB, and subsequent levels should be bigger.
But we're seeing 2MB for all files, which isn't very performant and wastes a lot of file descriptors.
Are we using it wrong, or is this a bug?
Thanks!
/cc @rhysh

subsequent levels should be bigger.

The subsequent levels are bigger, but the files (with default settings) are the same size. Subsequent levels include more files.
CompactionTableSize * (CompactionTableSizeMultiplier ^ Level) for your example is 2 MiB * (1 ^ 2), so level2's files are 2 MiB each. The total size of level2 is CompactionTotalSize * (CompactionTotalSizeMultiplier ^ Level), 10 MiB * (10 ^ 2) = 1000 MiB.
It's been a couple of years since I've tried adjusting those knobs, but I recall it being fruitful. I don't know my way around the settings well, and the variable names (some with Table, some with  Total) all look similar to me.
To start off: The files are never modified once they're written. Data starts in low-numbered levels, and migrates to higher levels as new data comes in. The mechanism for that is to read one file from level K and to read N files (10, by default) from level K+1, writing out N+1 (11) files in level K+1. The database then deletes the previous files (once they're no longer referenced by iterators). When the files are 2 MB, that process involves reading 22 MB and writing 22 MB.
Because the compaction process discards the affected files, there's a benefit to keeping them somewhat small: Using larger files means the compaction process will require reading and writing more data, which could be disruptive for latency-sensitive applications. I think that's one of the primary tradeoffs you'll get with these settings.

But we're seeing 2MB for all files, which isn't very performant and wastes a lot of file descriptors.

To trade latency for fewer files, CompactionTableSizeMultiplier might help. If you need to conserve file descriptors (rather than inodes), OpenFilesCacheCapacity should limit the number of cached FDs.

What @rhysh said is spot on. @bradfitz Basically you need to set CompactionTableSizeMultiplier > 1 if you want subsequent table size to be bigger. The default value is 1 which means all level will have same size.


tf.nn.softmax_cross_entropy_with_logits_v2 loss function so big

Describe the problem
I am trying to build up a binary image classifcation project (2 classes are balanced) . There are 2 nodes in output layer. However, my loss function is starting from a high point(3000). Is my loss function okay? Should I change my loss function ? I want to use a metric similar to Sklearn's log-loss. At the end of 1st epoch, it reaches to 80% accuracy and after 10 epochs and its accuracy becomes 82 %. During 10 epochs, it decreases from 3000 to 20. The graph of my loss function is as following(1 epoch = 175 steps) .

The graph of accuracy for 10 epochs is below:

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Windows 10 Home
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below):1.6.0
Python version: 3.6.0(no anaconda)
CUDA/cuDNN version:9.0 - 7.0
GPU model and memory:GTX 1050
Bazel Version:N/A

Source code / logs
cross_entropy=tf.reduce_mean( tf.nn.softmax_cross_entropy_with_logits_v2(labels=y_true,logits=y_pred ))

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Bazel version
Exact command to reproduce

I updated bazel information.

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!

bro have you found solution of this ?


Fix some flaky tests and improve device plugin de-registration in virt-handler

What this PR does / why we need it:
Fixing the following flakes in the test suite:

Hook sidecar test assumed that the VMI pod exists immediately after the VMI creation
Migration policy cleanup was deleting all migrations in parallel runs instead of just the policies for the corresponding test namespace
Drain tests were evicting all pods (including system components) instead of just VMI pods, which caused unpredictable delays
Basic operator tests were not waiting for the operator to be back online wich made follow-up tests fails due to non-responsive webhooks
The migration network tests were only waiting for the virt-handler pods to be running, instead of waiting for them to be ready

One production code improvement was also needed:
The virt-handler device-plugins are now during shutdown sending an empty list of devices to the kubelet to "emulate" a deregistration process. Otherwise the devices are shown as still available for quite some time which leads to admission errors after scheduling, since the scheduler thinks that the resources are still available, but the kubelet then fails to request them.
Tests which should be fixed which were reported as failing:
[Serial][sig-compute]MediatedDevices with mediated devices configuration Should successfully passthrough a mediated device with a disabled display
[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext With selinuxLauncherType as container_t [test_id:2953]Ensure virt-launcher pod securityContext type is correctly set
 [Serial][rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute] VM Live Migration Starting a VirtualMachineInstance with migration policies migration policy should override cluster-wide policy if defined
[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext With selinuxLauncherType as container_t [test_id:2895]Make sure the virt-launcher pod is not priviledged
[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking VirtualMachineInstance with masquerade binding mechanism [Serial]with a dedicated migration network Should migrate over that network
[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component] VMI definition with SM BIOS hook sidecar should not start with hook sidecar annotation when the version is not provided

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Improve device plugin de-registration in virt-handler and some test stabilizations

/cc @dhiller
/cc @xpivarc
/cc @EdDev
Extracted the test fixes from #7119 since I need more time on that PR.

/retest

/retest

/cc @vladikr do you want to have a look at the device plugin changes?

/retest

/approve

/cherrypick release-0.49

/test pull-kubevirt-e2e-k8s-1.23-sig-compute


Get Public IPs (IPv6)

Exposed IPsV6 and AllIPs APIs. Added tests.

Why not leaving the IPs function as it is and just introducing a new function for retrieving the IPv6 addresses instead?

That's what I did. I think the diff in the PR may be adding to confusion, but it essentially leaves the original API as is, and exposes two new APIs (one for retrieving both sets, and one for the ipv6 set). See https://github.com/fastly/go-fastly/pull/189/files#diff-063a6e698147141c9ccad8e9632e0e13R22

@philippschulte
Is there an ETA on merges and releases?

@wbautistaEXPEDIA v1.14.0 has been released. Thanks again for your contribution!


My links edit screen 'freezes' when typing certain characters

Category

[ ] Question
[x] Bug
[ ] Enhancement

Expected or Desired Behavior
I would like to be able to add links with certain characters (for instance = or ?) in the URL. It seems like the screen freezes for a long time because of the regex check.
Observed Behavior
The edit link screen freezes for a while when you want to add a pretty long link with the characters = or ? in it.
Steps to Reproduce

Open footer
Click Edit
Edit or add a link
make sure the link is longer than 30 characters, add a = or ? at the end of it

Cleaning up. This should be fixed in latest releases.


Feature for controller of car with routs

@Hello team in this pull request I have  created :

Implement create, delete, and show controller actions for the car resource.
Add routes for each method.

hello, @SaeqaSultani  Thank you for reviewing my pull request,  Cheers and Happy!


Add -S/--skip-covered for skipping fully covered files

Does not affect the detailed output for now.
See #28

--omit-covered-files is available now.


Status/Future of this Repo

:wave: Hi all - I'd like to discuss the future of this repo. The last meaningful library (Go) commit was pre-2020, and the issues requesting istio version support are piling up. I've spent the last few days attempting to convert this project to Go modules (dep ensure hangs and is no longer supported), and the dependency situation is....messy to say the least; several package revisions no longer exist, and I still haven't found a working combination. Obviously, having an SMI adapter for Istio would be fantastic, but I'm curious as to the official status/support of this repository.

Thanks, @keithmattix! I've added this as a discussion item for the June 9th community meeting - https://docs.google.com/document/d/1NTBaJf6LhUBlF8_lfvBBt_MbyPvT-6CZNg6Ckpm_yCo/edit?usp=sharing - please edit as desired.

Was there an outcome to this? I'm not sure how SMI is going in general but to a casual observer the istio support seems basically stopped.

Development of Istio support has shifted to https://github.com/nicholasjackson/istio-smi-controller for the time being 😄

Closing due to project archival: https://www.cncf.io/blog/2023/10/03/cncf-archives-the-service-mesh-interface-smi-project/


Upgrade App Auth library ADAL dependency to 4.X

Is your feature request related to a problem? Please describe.
Couple of customers have requested this. ADAL 4.X GAed over 6 months back.
Describe the solution you'd like
Upgrade App Auth's ADAL dependency to 4.X.

There was already an issue for this right?
https://github.com/Azure/azure-sdk-for-net/issues/5006

I have multiple projects and one of them use ADAL 4.4.1, another one use Microsoft.Azure.Management.AppService.Fluent that used Microsoft.Rest.ClientRuntime.Azure.Authentication. As result in third project has:

NU1608: Detected package version outside of dependency constraint: Microsoft.Rest.ClientRuntime.Azure.Authentication 2.3.4 requires Microsoft.IdentityModel.Clients.ActiveDirectory (>= 3.14.0 && < 4.0.0) but version Microsoft.IdentityModel.Clients.ActiveDirectory 4.4.1 was resolved.

I vote for this issue with two hands.

@Alezis , this issue is for Microsoft.Azure.Services.AppAuthentication and not for Microsoft.Rest.ClientRuntime.Azure.Authentication Nuget. Can you please create a separate issue for that? Thanks!

Hey Folks,
I am facing this issue with my usage of 'Microsoft.Azure.Services.AppAuthentication'
I have these dependencies:
Microsoft.Bot.Builder >= 4.4.3
Microsoft.Extensions.Configuration.AzureKeyVault >= 2.2.0
Microsoft.Bot.Builder brings in Microsoft.Bot.Connector >= 4.4.3 which in turn brings in Microsoft.IdentityModel.Clients.ActiveDirectory >= 4.5.0.
Microsoft.Extensions.Configuration.AzureKeyVault brings in Microsoft.Azure.Services.AppAuthentication >= 1.0.1 which in turn brings in Microsoft.IdentityModel.Clients.ActiveDirectory >= 3.19.4
My solution ends up resolving Microsoft.IdentityModel.Clients.ActiveDirectory to 4.5.0 since it fulfils all the dependency requirements, however Microsoft.IdentityModel.Clients.ActiveDirectory had a change between 3.x and 4.x in that it no longer packages an additional DLL named Microsoft.IdentityModel.Clients.ActiveDirectory.Platform.
My application crashes when trying to configure KeyVault with this exception:
System.IO.FileNotFoundException   HResult=0x80070002   Message=Could not load file or assembly 'Microsoft.IdentityModel.Clients.ActiveDirectory.Platform, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.   Source=Microsoft.Extensions.Configuration.AzureKeyVault   StackTrace:    at Microsoft.Extensions.Configuration.AzureKeyVaultConfigurationExtensions.<GetTokenFromClientCertificate>d__5.MoveNext()    at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
I made this PR to fix this: https://github.com/Azure/azure-sdk-for-net/pull/6343 However I then stumbled upon this issue which shows that something similar has been merged in and reverted for some undocumented reason.

New PR: https://github.com/Azure/azure-sdk-for-net/pull/6734

Hi all, we have just released the newest version 1.3.0 of AppAuth that updates its ADAL dependency to 4.3. Please let us know if you have any issues

I have basically the same issue as @Matt:
Also stuck on this problem, anyone taking a look?
In my case I'm trying to use Microsoft.Cloud.Metrics.Client.Metrics.MetricReader (v 2.2018.1214.1056) in a Bot Framework v4 project. The MetricReader requires Microsoft.IdentityModel.Clients.ActiveDirectory.Platform; BFv4 requires Microsoft.IdentityModel.Clients.ActiveDirectory >= v 4.5.0. But the .Platform is deprecated on .ActiveDirectory as of v >= 4.0 (not the Bot Framework version, the ActiveDirectory version.)

@jbaek080 It sounds like your issue would be with the MetricReader package since it has a dependency on ADAL 3.x.

Closing since app auth has been upgraded to use 4.X


Does LCE support deployment on ARM32 Cortex-M7?

Hi all,
I am urgently seeking to deploy the TFLite models converted using Larq Compute Engine (LCE) on an ARM32 device, specifically a Cortex-M7 CPU, the STM32F7 series MCU.
I have seen some related issues, such as #647, #688.
I have also noticed the "arm32" keyword in the LCE source code, kernels_arm32.h.

Does LCE support deployment on ARM32 Cortex-M7 processors?
Is there some relevant documentation or sample code for me to reference, or are there any other solutions that would allow me to deploy BNN TFLite models on the Cortex-M7?

Hi @Oslomayor.
Plumerai (the company that created Larq Compute Engine) offers an inference engine for Cortex-M CPUs, but this is a paid product and not open source. You can contact Plumerai through this form https://plumerai.com/contact_us, and the documentation of the inference engine can be found at https://docs.plumerai.com/1.16/inference_engine/ .

Hi @Tombana
Thank you for the information you provided. Plumerai's inference engine seems to support int8 and int16 quantized models, just as it states in the documentation: "Plumerai's inference engine provides fast execution of INT8 quantized or INT16 quantized deep learning models in tiny memory spaces." However, what I need is to deploy int1 models on Cortex-M CPUs.

You're correct, support for 1-bit layers is not mentioned in the public documentation. However, 2D binary convolutions are supported with optimized implementations for Cortex-M4 and Cortex-M7.


BUG No module named 'gluonts.torch.model.i_transformer'

Description
(A clear and concise description of what the bug is.)
from gluonts.torch.model.i_transformer import ITransformerEstimator
ModuleNotFoundError: No module named 'gluonts.torch.model.i_transformer'
To Reproduce
(Please provide minimal example of code snippet that reproduces the error. For existing examples, please provide link.)
put code here

Error message or code output
(Paste the complete error message, including stack trace, or the undesired output that the above snippet produces.)
i have best  new  gluonts version , but  ModuleNotFoundError: No module named 'gluonts.torch.model.i_transformer'

Environment

Operating system: win11
Python version: py3.9
GluonTS version: dev
MXNet version:

(Add as much information about your environment as possible, e.g. dependencies versions.)

@MInYangP-OU this test module imports the estimator exactly as you say, and works fine. Are you sure you’re on the latest dev branch?


Remote Tree scrollbar gets wonky when some of the nodes are multiline

Godot version
Godot v4.1.dev4
System information
Ubuntu 22.04.2 LTS 22.04 - Vulkan (Forward+) - integrated Intel(R) HD Graphics 4400 (HSW GT2) () - Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (4 Threads)
Issue description
To be more precise, you can't scroll all the way to the bottom; if you do, the view goes back up shortly. Here's an example (I'm sorry for the wonky cropping, but should demonstrate it well-enough):
https://github.com/godotengine/godot/assets/85438892/0f1d8451-ad48-4b43-b540-3b7fd2fc9dcf
Nodes are probably not supposed to be multiline, but this issue likely goes deeper.
Steps to reproduce
Shown above pretty much
Minimal reproduction project
N/A

@MewPurPur  my private calming down innovation XY workaround in this case :P
--- a/scene/gui/tree.cpp
+++ b/scene/gui/tree.cpp
@@ -1948,7 +1948,7 @@ void Tree::update_item_cell(TreeItem *p_item, int p_col) {
                font_size = theme_cache.font_size;
        }
        p_item->cells.write[p_col].text_buf->add_string(valtext, font, font_size, p_item->cells[p_col].language);
-       p_item->cells.write[p_col].text_buf->set_break_flags(TextServer::BREAK_MANDATORY | TextServer::BREAK_WORD_BOUND | TextServer::BREAK_ADAPTIVE);
+       p_item->cells.write[p_col].text_buf->set_break_flags(TextServer::BREAK_NONE);
        TS->shaped_text_set_bidi_override(p_item->cells[p_col].text_buf->get_rid(), structured_text_parser(p_item->cells[p_col].st_parser, p_item->cells[p_col].st_args, valtext));
        p_item->cells.write[p_col].dirty = false;
 }

See #77802.

To my understanding, while this will fix the remote tree, scrollbars will still be bugged for other multiline trees?

I'll try not to forget to try to create a MRP since this has been addressed in the editor.

The text gets still inside the icons:

This is an older issue, I don't know if it's reported.

I believe it was also introduced by the tree multiline PR.
4.0.3.slable:


there are empty space underneath footer

branch: kickstarter
the empty space will be gone if resize the window.

solved by me accidentally lol


vimplugins: update.py supports GitHub Access tokens; add completion-nvim, completion-treesitter

Motivation for this change
Update vimplugins and add:

https://github.com/haorenW1025/completion-nvim
https://github.com/nvim-treesitter/completion-treesitter

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I've rebased this and also made ./update.py use GITHUB_API_TOKEN if defined. This makes updating considerably faster since you have use higher parallelism without 429s.
I think there are more than a few people using neovim 0.5, particularly for the features that these plugins revolve around. It certainly wouldn't be the first unstable thing packaged in nixpkgs, and at least one of them has a tagged release. Hopefully this can be merged. Thanks for considering/reviewing!

while at it would you mind packaging https://github.com/nvim-lua/lsp-status.nvim

@teto Sure, I've redone the PR with lsp-status.nvim included as well.
Also, I was able to use -p 16 to redo this, which was 16 times faster than can be achieved without GITHUB_API_TOKEN.

this iteration isn't ready for merging, btw.

Looks like I had missed another dependency of completion-treesitter.
@teto your requested plugin breaks my system config (it looks like maybe vimplugins tests that vim can startup properly?) When I point at this commit, it works. Maybe you can file an issue/pr on lsp-status.nvim for this? I don't quite have context, or time to test this outside of nixpkgs. https://github.com/colemickens/lsp-status.nvim/commit/3982991cdf72897ed047f5fd2197108751cb7dbe
I'm going to back out the lsp-status-nvim commit and push what works.

Thanks @Mic92. I responded to feedback and ran ./update.py again to validate and update.

Should the token be made a requirement? I mean without it, one does run into request limits quite fast, so it is not really usable.

@Mic92 I don't know. I didn't want to make a "breaking change" if i I didn't have to. It does update with -p 1, it's just slow. I'd rather leave it to another PR, to be frank. (I went ahead and did this next round of fixups and rebased/pushed.)

Any chance you can update coc-metals as part of this PR as well? The current version in Nixpkgs is super outdated. The new repository is https://github.com/scalameta/coc-metals
I tried to update a few plugins but I was also blocked by https://github.com/NixOS/nixpkgs/issues/91339

I don't think so, sorry. I've already churned this PR once for a change I wound up having to back out. I'd really like to see this merged so we can unblock everyone.

No problems, I'll try to put up a follow up PR.

Let's merge this :+1: Thanks for your work!

This still doesn't work for me. I have set up a GITHUB_API_TOKEN and some packages managed to be downloaded at first but then again Github doesn't seem to like the amount of requests.
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...
<urlopen error [Errno 113] No route to host>, Retrying in 3 seconds...

Unless I made some other coding error, "No route to host" is a very different error condition than an HTTP 429.

Agreed. Sounds like a local network issue.

I don't think I have any network issues, it would be nice if someone else could try and see if this works for them.

I just ran it https://asciinema.org/a/mFnijt0sBehQyxZWUeRKb2Iu2 (and rotated the access token).

Wow, that really works for you! Thanks for that. Any chance you could try and make the same changes I made to vim-plugin-names here and then run the script again?
It's really late in my timezone but I promise to post what happens on my end tomorrow first thing. I wish this worked for me too...

Sure, let's move the conversation over to your PR. Maybe a new issue would be best if you (or anyone) winds up finding something wrong with the update script.


Update vpn-gateway-about-vpn-devices.md

Good afternoon, I would like to publish this Azure VPN configuration document with BLOCKBIT UTM
Thank you

@marcoaderno : Thanks for your contribution! The author, @yushwang, has been notified to review your proposed change.

@marcoaderno Please reach out to me offline - we need to perform some validation before publishing VPN devices/models on this page. My email address: Yu-Shun.Wang (at Microsoft.com).
#please-close


Bump up changed-files GHA

The GHA was bumped up by infra to latest stable v43.0.0, and they removed the old pin, so action won't run in other PRs until this one gets merged.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

Let's see if it runs properly.


Sorting causes problems with import

Description / Beschreibung
When using different uri_prefixes for, e.g. a domain import, the sorting by uri destroys the order in the file, and parent Attributes are imported after their children (with a different uri_prefix earlier in the alphabet). This is the problematic line:
https://github.com/rdmorganiser/rdmo/blob/master/rdmo/core/xml.py#L52
Expected behaviour / Erwartetes Verhalten
I am not sure if we could get rid of the sorting, we could also sort by path (which would give the field some meaning in the xml again). Ideas? @triole @MyPyDavid

could you not find the different uri_prefixes first and loop over them to keep them separate?
Don't know if it applies here, would need to reproduce it to better see it..

Well to match the parents, the path is the important value. With the uri_prefixes it could also fail in the other direction, if the child is from rdmorganiser.github.io and the parent from somewhere else.


"Genelengths" in rnaseqdiffexpression pipeline

Creates a table of "Genelengths" from featurecounts output
Can be very helpful for downstream analysis - such as correcting for gene length in GO analysis etc

Thanks!


generate-changelog for postgres default value generates incorrectly

Search first

[X] I searched and no similar issues were found

Description
When generating a changelog for my existing database, the resulting postgresql code has a syntax error that prevents it from being used as-is.
Steps To Reproduce
in psql to the local database:
CREATE TABLE "wblink" ("schedulebatchlinkid" BIGINT GENERATED BY DEFAULT AS IDENTITY NOT NULL, "wid" VARCHAR(500) NOT NULL, "bid" VARCHAR(500) NOT NULL, "deleted" BIT(1) DEFAULT (0)::bit(1) NOT NULL);
liquibase.properties file point to the local db:
liquibase generate-changelog --changelog-file=sql/test.postgresql.sql
Actual Behavior
Result:
test.postgresql.sql.txt
Expected/Desired Behavior
Expected is the following result, instead:
expected.postgresql.sql.txt
Liquibase Version
version 4.19.1
Database Vendor & Version
PostgresSQL 14.7
Liquibase Integration
CLI
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
Ubuntu on Docker
Additional Context
On 'Pro' trial, to determine if I can use this in our company's project.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

I'd guess what's happening is that we sometimes get computed values back from the database metadata wrapped in ()'s for some database. Feels like sqlserver for sure, but maybe others? So we check for that and strip off surrounding ()s which works, until the default value is  (0)::bit(1)
Perhaps we can better limit that () stripping to only databases that use that style? Or at least stop doing it for postgresql if they don't support it


Can not reproduce the accuracy

Will you release your training config?

We included our training setting in Page 8, 2nd paragraph. We will consider releasing our training code after publication.


Release 1.19.0

Closes: #1476

@pankajkoti The regression tests work fine on both the celery executor and the k8s executor. Please feel free to merge it after you finish the testing on you part :)

@pankajkoti The regression tests work fine on both the celery executor and the k8s executor. Please feel free to merge it after you finish the testing on you part :)

I think we already tested the regression. I will test the released providers once for sanity later. I think we can proceed with merging and releasing.


uri is not escaped properly

GetBlob fails for "image - copy(1).png" with Error preparing HTTP request: invalid uri character.

I'm not sure but this could be a solution:
in rest_client.rs convert uri from url.
request.method(http_method.clone()).uri(url.to_string());

I can confirm the bug. I've been lazy with the escaping it seems :).

A solution could be replacing the uri code with something like this:
        let mut uri = format!(
            "https://{}.blob.core.windows.net/{}/{}",
            self.client().account(),
            utf8_percent_encode(&container_name, COMPLETE_ENCODE_SET),
            utf8_percent_encode(&blob_name, COMPLETE_ENCODE_SET)
        );

I do not remember right now if the container can have non valid HTTP characters so it's safest to escape it anyway.
I will have to modify every builder to call the utf8_percent_encode function. Another way is to write. I'll think about it in a bit.

If you have the time I could use an hand testing the solution. Right now I have only changed GET blob, you can find the code in this branch: issue/98.

I have removed "testing needed" here and added to the above PR (which should contain the fix for all the blob storage methods).


ymodem:set the transport retry as optional

Summary
The waiting duration of the rb/sb command can be determined based on the number of retransmissions, so that ymodem can restart to the normal system after running in the bootloader for a short period of time.
Impact
ymodem
Testing
use stm32 ymodem

[Experimental Bot, please feedback here]
NuttX PR Requirements Review
Verdict: The PR does not fully meet NuttX requirements.
Missing Information:

Summary:

Lacks clarity on why this change is necessary. What problem does it solve?
Needs specifics on how the waiting duration is calculated.
Should mention which functional part of the code is modified (e.g., ymodem driver).

Impact:

Unclear if this is a new feature or modification.
Does this change user interaction with ymodem?
Potential impact on compatibility (backward/forward) is not addressed.

Testing:

Insufficient detail.
Provide:

Specific build host details (OS, CPU, compiler version).
Target architecture, board, and configuration.
Actual testing logs before and after the change.

Recommendations:

Expand the Summary:  Clearly articulate the problem, the solution (including calculation details), and the affected code section.
Complete the Impact Section: Address all points, especially user impact and compatibility concerns.
Provide Detailed Testing Information:  Include specific host/target setups and relevant log snippets.


Update Composer dependencies (2021-02-02-00-13)

Visual regression test passed!
View the visual regression test report


Create test.md

Docs Build status updates of commit 0ad4c53:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/test.md
:bulb:Suggestion

Details

docset/windows/test.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Leaving the PR as it is for one week until assuming the tests could take some time.

Closing as a test PR.


Ros2 v0.8.0 fix packages2

Fixed the cause of /autoware/state becoming Emergency
How to check
$ros2 launch autoware_launch planning_simulator.launch.xml vehicle_model:=lexus vehicle_id:=default sensor_model:=aip_xx1 map_path:=[MAP_PATH]
Set initial pose and goal pose
$ros2 topic echo /autoware/state # check state

Could you resolve conflicts?

rebased on ros2-v0.8.0-beta


Came Across this unexpected bug and idk how to fix it

So i was just Exploring and experimenting with the layout and came across something Crazy, I had the 3 Column Setup and was messing with custom Css and came across this https://cdn.discordapp.com/attachments/453878883398189056/482737550394392586/unknown.png

press control + comma and disable BD's minimal mode


IFE integration docs processExits

From the tests in elixir-omg I think doing an IFE needs a processExits call as well, but this information was not available reading integration docs https://github.com/omisego/plasma-contracts/blob/master/plasma_framework/docs/integration-docs/integration-doc.md#processing-a-standard-exit
https://github.com/omisego/plasma-contracts/blob/master/plasma_framework/docs/integration-docs/integration-doc.md
Am I missing something or is this really missing? What is the link between IFE and exit processing?
Cheers

It's missing from the doc. After piggyback, one can processExits for the IFE.
The process is mostly same as SE, if you want to go ahead now, you can get the IFE exitId from this helper function of ExitGame contract:
https://github.com/omisego/plasma-contracts/blob/6429cb9feff9d90c9559ce30a279d1f0a332924b/plasma_framework/contracts/src/exits/payment/PaymentExitGame.sol#L61
Will leave this issue open until we add the doc.

you've said

one can processExits for the IFE (of that token).

does that mean he doesn't have to? what are the implications if one doesn't call process exit?
also, have we documented what the mechanics of these things are? for example... we know we need to do these things... but would integrators know why (purpose)?

You don't have to process your own exits - anyone can process anyone else's exits that are on the queue (i.e. ready to be processed).
Processing an exit just means transferring the money from the vault to the owner.
However, exits have to be processed in order - the exit at the top of the queue must be processed before the 2nd exit on the queue.
Which means that if you're not in a hurry to get your money, instead of spending the gas to process your exit you can just wait and hope that somebody more impatient behind you in the queue will do it for you.
To avoid these kinds of games of chicken, we (the network operator) will probably pay the gas to periodically process exits and empty the queue (at least initially).

Two questions in reverse order:
First:

To avoid these kinds of games of chicken, we (the network operator) will probably pay the gas to periodically process exits and empty the queue (at least initially).

Does this part of the system already exist? How are we planning to do this? Are we able to observe and metric the queues?
Second:
IFE first step is that I get my tokens back on OMG network, second step after processing the exit is that I get back on the ethereum network? So... IFE is basically revert transaction + standard exit? Sorry, this might be very basic.

Two questions in reverse order:
First:

To avoid these kinds of games of chicken, we (the network operator) will probably pay the gas to periodically process exits and empty the queue (at least initially).

Does this part of the system already exist? How are we planning to do this? Are we able to observe and metric the queues?

Observing the queues is pretty easy, but AFAIK whether and how we do this hasn't been set in stone yet.

Second:
IFE first step is that I get my tokens back on OMG network, second step after processing the exit is that I get back on the ethereum network? So... IFE is basically revert transaction + standard exit? Sorry, this might be very basic.

No, you don't get your tokens back on OMG network (child chain, right?) when you exit. Exiting means removing the tokens from the child chain and unlocking them on the root chain.
Not sure if I understand the question, but an IFE allows you to exit either the inputs or the outputs of a tx. If you start an IFE because you think a tx hasn't been included in a block, and piggyback an output, and later it's shown that the tx was actually put into a block; then that's almost exactly the same as a standard exit (but costs more gas because of the more complicated exit game).
Hmmm, maybe you're thinking about if the IFE is shown to be non-canonical because one of its inputs has been spent in another tx. In this case, the IFE tx is not so much reverted as it never happened. The spent input has been spent, so that can't be exited. However, if there is another input in the IFE tx that has not been spent in another tx, then it can be exited via piggybacking the IFE.
This is not the same as reverting and standard exiting though. The output that that input is spending can never be standard exited, because even if the IFE tx is 'invalid' and will never be put into a block, the owner of that output has signed a tx to spend it, and that can be used to challenge a standard exit.

Before I test the second part...

Observing the queues is pretty easy, but AFAIK whether and how we do this hasn't been set in stone yet.

Is this tracked somewhere? I presume it's a mainnet blocker, right?

Before I test the second part...

Observing the queues is pretty easy, but AFAIK whether and how we do this hasn't been set in stone yet.

Is this tracked somewhere? I presume it's a mainnet blocker, right?

I wouldn't say it's a blocker, because it's an extra service that can be added on at any time

Two details I've noticed:

the return value of getNextExit(uint256,address) is a composition, and it is not evident that you need to perform exit_id = queue_next_exit_id &&& (1 <<< 160) - 1 @boolafish helped me on that and it might be useful to mention what the result means

calling processExits and just looking at the transaction status being 0x1 is not enough. Meaning, it doesn't mean we've actually processed specified exits, but you need to observe if there were emitted events...


Remove breadcrumb block from the authoring doc

Refer issue - https://github.com/hlxsites/sunstar/pull/338

Also see this


Changing ActiveProfile: Collection changed during LateUpdate

Describe the bug
When swapping the MixedRealityToolkit.ActiveProfile, the following InvalidOperationException (collection changed) occurs during LateUpdate.
Create a new scene and configure for the MixedRealityToolkit
Add a button to the scene and apply / configure the included script
Enter play mode and expand the MixedRealityPlayspace object in the hierarchy
Click the button to toggle between profiles

To reproduce

Create a new scene and configure for the MixedRealityToolkit
Add a button to the scene and apply / configure the included script
Enter play mode and expand the MixedRealityPlayspace object in the hierarchy
Click the button to toggle between profiles

Expected behavior
The collection modification either does not occur, or the enumeration is aborted during [Late]Update when it is modified.
Your Setup (please complete the following information)

Unity Version 2018.4.9f1
MRTK Version 2.0.0 + fixes that will be in 2.1.0

SwapActiveProfile.cs
using Microsoft.MixedReality.Toolkit;
using UnityEngine;

public class SwapActiveProfile : MonoBehaviour
{
    public MixedRealityToolkitConfigurationProfile profile1;
    public MixedRealityToolkitConfigurationProfile profile2;

    void Start()
    { }

    public void Swap()
    {
        MixedRealityToolkit.Instance.ActiveProfile = (MixedRealityToolkit.Instance.ActiveProfile == profile1) ? profile2 : profile1;
    }
}

This may be related to a recent change to the MixedRealityServiceRegistry.GetAllServices(). Investigating...

Fixed in personal fork as part of #6043