Electron 11 update breaks VScode window display!

Issue Type: Bug

Download vscode insider version (tar.gz file) and install it (untar the file).
Launch the installed vscode and enlarge the vscode window and then exit vscode.
Launch the installed vscode again and you'll see something like the attched screenshot.
If I shrink the launched vscode window to a smaller size then the display come back to normal.

There is not such an issue with the stable version v1.52.1 and the insider version using Electron 9.x. Start option "--no-xshm" and "--disable-gpu" don't help.
For more details please refer the closed issue report: https://github.com/microsoft/vscode/issues/112335
VS Code version: Code - Insiders 1.53.0-insider (01089c0a5052432594a177f90ad9f3148ec2a6a2, 2021-01-07T05:22:33.976Z)
OS version: Linux x64 3.10.0-693.17.1.el7.x86_64

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz (32 x 2100)

GPU Status
2d_canvas: enabledgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabled_readbackwebgl2: enabled_readback

Load (avg)
0, 0, 0

Memory (System)
187.41GB (113.61GB free)

Process Argv
--no-sandbox --crash-reporter-id 60a11865-2fb4-47a7-b42d-fad3e3fd65d3

Screen Reader
no

VM
0%

DESKTOP_SESSION
undefined

XDG_CURRENT_DESKTOP
undefined

XDG_SESSION_DESKTOP
undefined

XDG_SESSION_TYPE
undefined

Extensions: none
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221882
python383:30185418
pythonvspyt617cf:30237717
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30208930
wsl2promptcf:30219163
vstry244:30230484
pythonvsdeb440:30224570
unusedpromptcf:30219165
folderexplorercf:30219167
openfilemenucf:30219169
pythonvsded773:30223139
core-portspanel:30233467

This bug seems has something to do with remote connection. Say, I have two Linux machines: A (Red Hat Enterprise Linux Workstation release 7.9 (Maipo)) and B (CentOS Linux release 7.4.1708 (Core)). I installed on both A and B the same latest insider version. I don't have such a problem if I run the local Vscode on A. However, if I "ssh -X" to B (from A) and run VScode installed on B then I have the described problem.
If I use the stable version v1.52.1 or any older insider version (built on Electron 9.x) then I don't have any problem (except I have to launch vscode with "--no-xshm") no matter I run VScode on A or on B.
Hope this info helps.

This bug seems has something to do with remote connection. Say, I have two Linux machines: A (Red Hat Enterprise Linux Workstation release 7.9 (Maipo)) and B (CentOS Linux release 7.4.1708 (Core)). I installed on both A and B the same latest insider version. I don't have such a problem if I run the local Vscode on A. However, if I "ssh -X" to B (from A) and run VScode installed on B then I have the described problem.
If I use the stable version v1.52.1 or any older insider version (built on Electron 9.x) then I don't have any problem (except I have to launch vscode with "--no-xshm") no matter I run VScode on A or on B.
Hope this info helps.

Sorry for the late response, can you provide the --verbose --disable-gpu --no-xshm output for launching vscode in B from A

Sorry for the late response, can you provide the --verbose --disable-gpu --no-xshm output for launching vscode in B from A

Version: 1.53.0-insider
Commit: 1a4b35c2023a41efae1af2661026d57cea90ef5c
Date: 2021-01-21T05:13:53.220Z
Electron: 11.2.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 3.10.0-693.17.1.el7.x86_64

Version: 1.53.0-insider
Commit: 1a4b35c2023a41efae1af2661026d57cea90ef5c
Date: 2021-01-21T05:13:53.220Z
Electron: 11.2.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 3.10.0-693.17.1.el7.x86_64

[pzha@h050018 bin]$ ./code-insiders --verbose --disable-gpu --no-xshm
Warning: 'xshm' is not in the list of known options, but still passed to Electron/Chromium.
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[main 2021-01-21T17:24:16.213Z] Starting VS Code
[main 2021-01-21T17:24:16.213Z] from: /NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app
[main 2021-01-21T17:24:16.213Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'c33216d5-63a5-44b2-a782-c35bebf7cbeb',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416'
}
[main 2021-01-21T17:24:16.219Z] Resolving machine identifier...
[main 2021-01-21T17:24:16.220Z] Resolved machine identifier: 88f5d257145bfc502f1b17cd2a243848fb184879e6f6ea5ff918797f3e12411a
[main 2021-01-21T17:24:16.220Z] Main->SharedProcess#connect
[main 2021-01-21T17:24:16.230Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2021-01-21T17:24:16.233Z] lifecycle (main): phase changed (value: 2)
[main 2021-01-21T17:24:16.234Z] windowsManager#open
[main 2021-01-21T17:24:16.234Z] windowsManager#open pathsToOpen [
{
backupPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/Backups/1611249651704',
remoteAuthority: undefined
}
]
[main 2021-01-21T17:24:16.235Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 59, y: 19, width: 1674, height: 1017 }
[main 2021-01-21T17:24:16.235Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1993, height: 1102 }
[main 2021-01-21T17:24:16.235Z] window#ctor: using window state { mode: 1, x: 59, y: 19, width: 1674, height: 1017 }
[60724:0121/112416.304593:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2021-01-21T17:24:16.354Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing ''
[main 2021-01-21T17:24:16.394Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-01-21T17:24:16.395Z] lifecycle (main): phase changed (value: 3)
[main 2021-01-21T17:24:16.395Z] update#setState idle
[main 2021-01-21T17:24:16.395Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60724:0121/112416.403227:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(node:60724) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[main 2021-01-21T17:24:16.440Z] [storage state.vscdb] Trace (event): PRAGMA user_version = 1;
[main 2021-01-21T17:24:16.445Z] [storage state.vscdb] Trace (event): CREATE TABLE IF NOT EXISTS ItemTable (key TEXT UNIQUE ON CONFLICT REPLACE, value BLOB)
[main 2021-01-21T17:24:16.448Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2021-01-21T17:24:16.451Z] [storage state.vscdb] getItems(): 52 rows
[main 2021-01-21T17:24:16.509Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60749:0121/112416.533277:ERROR:xproto_internal.cc(110)] Cannot send request of length 25354132
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 7fbe7a1c-f3e4-4841-b952-11b3f61a537d, telemetry.lastSessionDate => Thu, 21 Jan 2021 17:23:09 GMT, telemetry.currentSessionDate => Thu, 21 Jan 2021 17:24:16 GMT}), delete(Set(0) {})
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','7fbe7a1c-f3e4-4841-b952-11b3f61a537d'),('telemetry.lastSessionDate','Thu, 21 Jan 2021 17:23:09 GMT'),('telemetry.currentSessionDate','Thu, 21 Jan 2021 17:24:16 GMT')
[main 2021-01-21T17:24:16.556Z] [storage state.vscdb] Trace (event): END TRANSACTION
[60749:0121/112416.571299:ERROR:xproto_internal.cc(110)] Cannot send request of length 24734164
[60724:0121/112416.749337:INFO:CONSOLE(618)] "%cTRACE color: #888 [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/workspaceStorage/1611249651704/state.vscdb, retryOnBusy: true)", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
(node:60777) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.    See https://github.com/electron/electron/issues/23506 for more information
[60724:0121/112419.423149:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/main.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[main 2021-01-21T17:24:19.581Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60724:0121/112419.612852:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] >> normalized [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/renderer1.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[60724:0121/112419.612887:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] >> normalized [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/main.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[main 2021-01-21T17:24:19.634Z] SharedProcess: IPC ready
[main 2021-01-21T17:24:19.646Z] Main->SharedProcess#connect: connection established
(node:60860) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node'.
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[main 2021-01-21T17:24:16.213Z] Starting VS Code
[main 2021-01-21T17:24:16.213Z] from: /NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app
[main 2021-01-21T17:24:16.213Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'c33216d5-63a5-44b2-a782-c35bebf7cbeb',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416'
}
[main 2021-01-21T17:24:16.219Z] Resolving machine identifier...
[main 2021-01-21T17:24:16.220Z] Resolved machine identifier: 88f5d257145bfc502f1b17cd2a243848fb184879e6f6ea5ff918797f3e12411a
[main 2021-01-21T17:24:16.220Z] Main->SharedProcess#connect
[main 2021-01-21T17:24:16.230Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2021-01-21T17:24:16.233Z] lifecycle (main): phase changed (value: 2)
[main 2021-01-21T17:24:16.234Z] windowsManager#open
[main 2021-01-21T17:24:16.234Z] windowsManager#open pathsToOpen [
{
backupPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/Backups/1611249651704',
remoteAuthority: undefined
}
]
[main 2021-01-21T17:24:16.235Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 59, y: 19, width: 1674, height: 1017 }
[main 2021-01-21T17:24:16.235Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1993, height: 1102 }
[main 2021-01-21T17:24:16.235Z] window#ctor: using window state { mode: 1, x: 59, y: 19, width: 1674, height: 1017 }
[60724:0121/112416.304593:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2021-01-21T17:24:16.354Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing ''
[main 2021-01-21T17:24:16.394Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-01-21T17:24:16.395Z] lifecycle (main): phase changed (value: 3)
[main 2021-01-21T17:24:16.395Z] update#setState idle
[main 2021-01-21T17:24:16.395Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60724:0121/112416.403227:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(node:60724) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[main 2021-01-21T17:24:16.440Z] [storage state.vscdb] Trace (event): PRAGMA user_version = 1;
[main 2021-01-21T17:24:16.445Z] [storage state.vscdb] Trace (event): CREATE TABLE IF NOT EXISTS ItemTable (key TEXT UNIQUE ON CONFLICT REPLACE, value BLOB)
[main 2021-01-21T17:24:16.448Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2021-01-21T17:24:16.451Z] [storage state.vscdb] getItems(): 52 rows
[main 2021-01-21T17:24:16.509Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60749:0121/112416.533277:ERROR:xproto_internal.cc(110)] Cannot send request of length 25354132
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 7fbe7a1c-f3e4-4841-b952-11b3f61a537d, telemetry.lastSessionDate => Thu, 21 Jan 2021 17:23:09 GMT, telemetry.currentSessionDate => Thu, 21 Jan 2021 17:24:16 GMT}), delete(Set(0) {})
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2021-01-21T17:24:16.552Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','7fbe7a1c-f3e4-4841-b952-11b3f61a537d'),('telemetry.lastSessionDate','Thu, 21 Jan 2021 17:23:09 GMT'),('telemetry.currentSessionDate','Thu, 21 Jan 2021 17:24:16 GMT')
[main 2021-01-21T17:24:16.556Z] [storage state.vscdb] Trace (event): END TRANSACTION
[60749:0121/112416.571299:ERROR:xproto_internal.cc(110)] Cannot send request of length 24734164
[60724:0121/112416.749337:INFO:CONSOLE(618)] "%cTRACE color: #888 [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/workspaceStorage/1611249651704/state.vscdb, retryOnBusy: true)", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
(node:60777) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.    See https://github.com/electron/electron/issues/23506 for more information
[60724:0121/112419.423149:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/main.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[main 2021-01-21T17:24:19.581Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[60724:0121/112419.612852:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] >> normalized [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/renderer1.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[60724:0121/112419.612887:INFO:CONSOLE(618)] "%cTRACE color: #888 [File Watcher (node.js)] >> normalized [CHANGED] /NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T112416/main.log", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
[main 2021-01-21T17:24:19.634Z] SharedProcess: IPC ready
[main 2021-01-21T17:24:19.646Z] Main->SharedProcess#connect: connection established
(node:60860) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node'.

It is interesting that if make the initial VScode window smaller (I resize the window of VScode,  and then quite VScode,  and launch VScode again), then the display would go back to normal. The following is the output (there are some difference to what I potsed above):
[pzha@h050018 bin]$ ./code-insiders --verbose --disable-gpu --no-xshm
Warning: 'xshm' is not in the list of known options, but still passed to Electron/Chromium.
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[main 2021-01-21T17:32:21.420Z] Starting VS Code
[main 2021-01-21T17:32:21.421Z] from: /NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app
[main 2021-01-21T17:32:21.421Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'c33216d5-63a5-44b2-a782-c35bebf7cbeb',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T113221'
}
[main 2021-01-21T17:32:21.427Z] Resolving machine identifier...
[main 2021-01-21T17:32:21.427Z] Resolved machine identifier: 88f5d257145bfc502f1b17cd2a243848fb184879e6f6ea5ff918797f3e12411a
[main 2021-01-21T17:32:21.428Z] Main->SharedProcess#connect
[main 2021-01-21T17:32:21.436Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2021-01-21T17:32:21.439Z] lifecycle (main): phase changed (value: 2)
[main 2021-01-21T17:32:21.439Z] windowsManager#open
[main 2021-01-21T17:32:21.439Z] windowsManager#open pathsToOpen [
{
backupPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/Backups/1611249651704',
remoteAuthority: undefined
}
]
[main 2021-01-21T17:32:21.440Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 494, y: 333, width: 1251, height: 767 }
[main 2021-01-21T17:32:21.440Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1993, height: 1102 }
[main 2021-01-21T17:32:21.440Z] window#ctor: using window state { mode: 1, x: 494, y: 333, width: 1251, height: 767 }
[62804:0121/113221.483633:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2021-01-21T17:32:21.579Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing ''
[main 2021-01-21T17:32:21.613Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-01-21T17:32:21.614Z] lifecycle (main): phase changed (value: 3)
[main 2021-01-21T17:32:21.614Z] update#setState idle
[main 2021-01-21T17:32:21.614Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[62804:0121/113221.622687:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(node:62804) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[main 2021-01-21T17:32:21.670Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2021-01-21T17:32:21.673Z] [storage state.vscdb] getItems(): 52 rows
[main 2021-01-21T17:32:21.745Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2021-01-21T17:32:21.775Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 7fbe7a1c-f3e4-4841-b952-11b3f61a537d, telemetry.lastSessionDate => Thu, 21 Jan 2021 17:31:59 GMT, telemetry.currentSessionDate => Thu, 21 Jan 2021 17:32:21 GMT}), delete(Set(0) {})
[main 2021-01-21T17:32:21.775Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2021-01-21T17:32:21.776Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','7fbe7a1c-f3e4-4841-b952-11b3f61a537d'),('telemetry.lastSessionDate','Thu, 21 Jan 2021 17:31:59 GMT'),('telemetry.currentSessionDate','Thu, 21 Jan 2021 17:32:21 GMT')
[main 2021-01-21T17:32:22.298Z] [storage state.vscdb] Trace (event): END TRANSACTION
[62804:0121/113222.546840:INFO:CONSOLE(618)] "%cTRACE color: #888 [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/workspaceStorage/1611249651704/state.vscdb, retryOnBusy: true)", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
(node:62856) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.      The following is the output (there are some difference to what I potsed above):
[pzha@h050018 bin]$ ./code-insiders --verbose --disable-gpu --no-xshm
Warning: 'xshm' is not in the list of known options, but still passed to Electron/Chromium.
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[main 2021-01-21T17:32:21.420Z] Starting VS Code
[main 2021-01-21T17:32:21.421Z] from: /NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app
[main 2021-01-21T17:32:21.421Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'c33216d5-63a5-44b2-a782-c35bebf7cbeb',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/logs/20210121T113221'
}
[main 2021-01-21T17:32:21.427Z] Resolving machine identifier...
[main 2021-01-21T17:32:21.427Z] Resolved machine identifier: 88f5d257145bfc502f1b17cd2a243848fb184879e6f6ea5ff918797f3e12411a
[main 2021-01-21T17:32:21.428Z] Main->SharedProcess#connect
[main 2021-01-21T17:32:21.436Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2021-01-21T17:32:21.439Z] lifecycle (main): phase changed (value: 2)
[main 2021-01-21T17:32:21.439Z] windowsManager#open
[main 2021-01-21T17:32:21.439Z] windowsManager#open pathsToOpen [
{
backupPath: '/NFS/ud1/home1/pzha/.config/Code - Insiders/Backups/1611249651704',
remoteAuthority: undefined
}
]
[main 2021-01-21T17:32:21.440Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 494, y: 333, width: 1251, height: 767 }
[main 2021-01-21T17:32:21.440Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1993, height: 1102 }
[main 2021-01-21T17:32:21.440Z] window#ctor: using window state { mode: 1, x: 494, y: 333, width: 1251, height: 767 }
[62804:0121/113221.483633:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2021-01-21T17:32:21.579Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing ''
[main 2021-01-21T17:32:21.613Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-01-21T17:32:21.614Z] lifecycle (main): phase changed (value: 3)
[main 2021-01-21T17:32:21.614Z] update#setState idle
[main 2021-01-21T17:32:21.614Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[62804:0121/113221.622687:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(node:62804) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[main 2021-01-21T17:32:21.670Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2021-01-21T17:32:21.673Z] [storage state.vscdb] getItems(): 52 rows
[main 2021-01-21T17:32:21.745Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2021-01-21T17:32:21.775Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 7fbe7a1c-f3e4-4841-b952-11b3f61a537d, telemetry.lastSessionDate => Thu, 21 Jan 2021 17:31:59 GMT, telemetry.currentSessionDate => Thu, 21 Jan 2021 17:32:21 GMT}), delete(Set(0) {})
[main 2021-01-21T17:32:21.775Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2021-01-21T17:32:21.776Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','7fbe7a1c-f3e4-4841-b952-11b3f61a537d'),('telemetry.lastSessionDate','Thu, 21 Jan 2021 17:31:59 GMT'),('telemetry.currentSessionDate','Thu, 21 Jan 2021 17:32:21 GMT')
[main 2021-01-21T17:32:22.298Z] [storage state.vscdb] Trace (event): END TRANSACTION
[62804:0121/113222.546840:INFO:CONSOLE(618)] "%cTRACE color: #888 [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/workspaceStorage/1611249651704/state.vscdb, retryOnBusy: true)", source: file:///NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (618)
(node:62856) Electron: Loading non-context-aware native module in renderer: '/NFS/ud1/home1/pzha/Downloads/VSCode-linux-x64/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.      In the case for a larger window we having failing requests to the XServer
ERROR:xproto_internal.cc(110)] Cannot send request of length 25354132
With Electron 11 and higher there is a refactor in chromium that switches to use xcb instead of xlib for the communication layer and this failure definitely can be related to it. Since CentOS 7 is no longer on the supported distro in upstream, I don't think its worth spending time to narrow down a minimal repro.
You can use our remote development flow https://code.visualstudio.com/docs/remote/remote-overview and continue to use CentOS 7 if thats a necessity. Closing as no further action can be taken here for the said distro, sorry about that.

Thanks for both the logs, it was helpful to spot the difference. In the case for a larger window we having failing requests to the XServer
ERROR:xproto_internal.cc(110)] Cannot send request of length 25354132
With Electron 11 and higher there is a refactor in chromium that switches to use xcb instead of xlib for the communication layer and this failure definitely can be related to it. Since CentOS 7 is no longer on the supported distro in upstream, I don't think its worth spending time to narrow down a minimal repro.
You can use our remote development flow https://code.visualstudio.com/docs/remote/remote-overview and continue to use CentOS 7 if thats a necessity. Closing as no further action can be taken here for the said distro, sorry about that.


IMAPClientHandler breaks when inbound buffer splits between CR and LF

Expected behavior
Reading well-formatted responses from a server should succeed regardless of how frames are split
Actual behavior
An exception is thrown IMAPDecoderError(parserError: NIOIMAPCore.ParserError(...) if a response is split between two buffers between a \r and \n.
This can happen when a server sends a very large response back which ends up being split between 8K buffers and the split just happens to land right after a carriage return. The next buffer will then start with a line-feed which the parser will blow up on.
Steps to reproduce
This is a bit hard to reproduce in the wild

Issue a command to a server with a very large response, where the 8192th byte of a response buffer is a \r
Parse the responses with IMAPClientHandler()

If possible, minimal yet complete reproducer code (or URL to code)
Add this test case to Tests/NIOIMAPTests/Coders/IMAPClientHandlerTests.swift:
class IMAPClientHandlerTests: XCTestCase {
    // ....

    func testSplitCRLF() {
        self.writeOutbound(.tagged(.init(tag: "a", command: .uidFetch(messages: .all, attributes: [.uid], modifiers: [])!)))
        self.assertOutboundString("a UID FETCH 1:* (UID)\r\n")

        self.writeInbound("* 38001 FETCH (UID 114597)\r")
        self.writeInbound("\n* 38045 FETCH (UID 114662)\r\n")
    }

This will give an error:
IMAPDecoderError(parserError: NIOIMAPCore.ParserError(hint: "none of the options match", file: "NIOIMAPCore/ParserLibrary.swift", line: 221), buffer: ByteBuffer { readerIndex: 0, writerIndex: 29, readableBytes: 29, capacity: 32, storageCapacity: 32, slice: _ByteBufferSlice { 0..<32 }, storage: 0x00006000032f1480 (32 bytes) }
readable bytes (max 1k): [ 0a 2a 20 33 38 30 34 35 20 46 45 54 43 48 20 28 55 49 44 20 31 31 34 36 36 32 29 0d 0a ])"
SwiftNIO version/commit hash
7d0f2cf79902c73d7bb1564e625e0de39d669045
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Darwin redacted.local 24.0.0 Darwin Kernel Version 24.0.0: Mon Aug 12 20:49:48 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T8103 arm64

I think I see the problem here.
For the IMAPServerHandler, there is a FramingParser which has logic which will properly ignore a buffer that starts with a \n  if the previous buffer ended in a \r. To that end, #670 was commited to make the newline parsing in the ParserLibrary.parseNewline to be more lenient than the protocol allows by accepting a single \r as the termination of the response if it existed at the end of a buffer.
Unfortunately, IMAPClientHandler does not use the FramingParser, so the leniency ends up causing a parsing error.


chore Fix link errors of librdkafka

Exclude coverage symbol from librdkafka's version script generator to avoid compatibility issues with recent linkers such as lld-17.

run buildall

run p0


Rename ParseJson to ParseJSON

Rename ParseJson to ParseJSON to be consistent with the existing JSON function.

For resource files, to avoid noisy commits, we only change the /en-us/ file. All the others are updated by the loc pipeline


Add Bangiales chloroplast genomes to data set

The current set of chloroplast genomes doesn't have red algal representatives. I propose to include the chloroplast genomes of the following species to the current data set:

Porphyra purpurea (NC000925)
Porphyra yezoensis (NC007932)
Pyropia haitanensis (NC021189)
Pyropia perforata (NC024050)
Wildemania schizophylla (NC029576)
Bangia fuscopurpurea (KP714733)

I updated the README file to adjust for incorporation of Bangiales species I added as well as Alismatales and Bromeliaceae, which appear to have been missed in previous commits.

Will accept.  Bromeliaceae is not an order. Will remove from list if added.

My mistake! Thank you for catching it.


Leddevice refactoring the next part

1. Tell us something about your changes.
just another monkey job. I want to save some code lines and remove dups.
led devices:

move switchoff() into base class, where possible. (default switchoff means, set al leds to black)
_ledCount is set automaticly before write is called.
use _ledCount where possible
some code style fixes
cleanup includes

=> now every leddevice including upcomming devices have a working switchOff
2. If this changes affect the .conf file. Please provide the changed section
no
3. Reference an issue (optional)
#194

cool! Let the tests begin :)

I just see I didn't cleaned the includes ... in some drivers are unused includes
e.g. ws2801:
currrent:

// STL includes
#include <cstring>
#include <cstdio>
#include <iostream>

// Linux includes
#include <fcntl.h>
#include <sys/ioctl.h>

// hyperion local includes
#include "LedDeviceWs2801.h"

neccessary
// hyperion local includes
#include "LedDeviceWs2801.h"

... I'll have a look

ok, now also includes are cleaned ... and lots of code line removed ;-)

spicy!

Great work - I love the sea of red!
I did laugh at  the 10 different implementations of switch off tho !

you are awesome red!!!

Thx, I'm actualy on the next leddevice iteration. I will seperate init code from write function as @penfold42 suggested. The base is already finished, but now comes the monkey part for every device.
Currently if you look into some devices it's somehow frightend that it contains only a few lines of code

I guess most of them have very little to do - frame up the led data and get the provider to send it!


projectCategory client

New client that retrieves list of project categories.
I use that for filtering issues based on project categories, not only project. Maybe helpful for others

Looks great, thanks!

Merged and published as v1.6.0
Thanks for also updating the existing docs, by the way :smile:


Poor Alignment of images in codeBuddy landing page

Description:
Issue: I came across an alignment issue in the codeBuddy landing page. The Image is not aligned correctly, which affects the user experience.
Expected Behavior:
The image should be properly aligned with the flow of the landing page, creating a visually pleasing and user-friendly appearance.

I had understood the requirement, and will be able to fix the issue, PLEASE assign this to me @0silverback0

good attention to detail! Go for it!


feat(auth): adding user endpoint to auth against oauth (AEROGEAR-9033)

Motivation
JIRA: https://issues.jboss.org/browse/AEROGEAR-9033
What
Add a endpoint to GET the user which can be used to validate if the user has authenticated with oauth in the UI
How
Added endpoint to swagger
Added a http_handler for the user resource
Added a service layer for the user resource
Added a model for the user resource
Added the route to the router
Verification Steps

Run make serve
Send a GET request to the user endpoint with the following headers
2.a X-Forwarded-User
2.b X-Forwarded-Email
The returned request should be in the following format but with the values you passed

Checklist:

[x] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

Progress

[x] Functionality
[ ] Tests
[ ] Verify against the UI pr

Coverage decreased (-1.5%) to 92.3% when pulling 89c3b39995c61db0910a1365bac68f08be5db557 on laurafitzgerald:AEROGEAR-9033 into da63cf7ec6a611754af2c8aae6d53530b85855c1 on aerogear:master.

@davidffrench @craicoverflow thanks for the reviews. I will address the comments in a follow on commit. I intentionally didn't add tests initially in order to wait for the review. I will add those now. :)

@davidffrench @craicoverflow changes made as requested. Tests are passing locally. Could you take a look at this again when you have some time. Thanks :)


fix: Allow connection with schema=information_schema

With snowflake, it's sometimes (particularly with alembic) convenient to connect with schema='information_schema', so that all other schemas are required explicitly (since there's no public schema, and the weird way snowflake scoping works).
As-is without this PR, the duckdb information_schema is lowercased, and the auto-use-schema code in fakesnow would unconditionally .upper() the given schema, search for INFORMATION_SCHEMA, not find it, and then you'd get This session does not have a current schema. Call 'USE SCHEMA' when you wouldn't in real life.
It might perhaps be more ideal to somehow fully recreate the snowflake information_schema and replace it, because there are some differences with the duckdb version that i suspect will end up being irreconcilable, but it's not obvious to me how to do this, nor how much additional work it'd be so...just a thought.

PS: yes having a fully recreated snowflake info schema makes sense to improve fidelity.


Misaligned tooltips in votes list

this seems like causing because of truncate

@mktcode I've created a PR here https://github.com/snapshot-labs/snapshot/pull/1633


sep: change reasoning behind setup checks

What
Change the reasoning behind setup checks to more generally focus on participants needing to verify the other participants escrow account state after formation.
Why
The statements made in the SEP already about these checks are focused on clawback state, but that is one of many states that could change. There are much worse things that can change, such as additional signers could be added by the other participant.

@acharb I adopted one of your changes, and then in the process of applying the other I realized we need to keep this requirement but for different reasons. I've rewritten the text in the security section to discuss the broader reason.


How to not set nonce

Getting an error message:
Receiver Requirement for no nonce has not been met, Received token has a nonce specified
Is there any way to not set a nonce?

There is now way currently to not set the nonce property. I keep this feature opened then.

I added a PR for this: https://github.com/WsdlToPhp/WsSecurity/pull/4

Sorry! Weirdly, I was not watching my own project so I did no see any activity since.... the beginning!
I'll review it very soon.

merged, tested and released!


Authentication Parameters

Just getting started with this api today. Unfortunatly i have encountered a 403 response error. When i follow the link it says that the authentication parameters are missing. I know that means my user key and an accept header with value application/json. Do i need to input these somewhere manually or is there an issue?
E/Volley: [208] BasicNetwork.performRequest: Unexpected response code 403 for https://api-2445582011268.apicast.io/games/?search=Zelda?fields=*

These are set automatically by the wrapper.
Are you sure you have set the api key correctly?

I have my key in my strings file and create the wrapper like so:
APIWrapper wrapper = new APIWrapper(getApplicationContext(),String.valueOf(R.string.Apikey));

The problem lies in your code: String.valueOf(R.string.Apikey)
Using String.ValueOf does not return the api key but the int that R.string.Apikey is represented by.
Try using getResources().getString(R.string.api_key), this will return the string you are looking for.

That did the trick. Not sure why i didn't think it would return the int now i think about it.
Thanks


README Rewrite

The readme had a lot of outdated information and was becoming fairly schizophrenic, so in an effort to force myself to clean it up I just started and committed the beginnings of a rewrite. I need to go back in and add documentation about redux-cli ( /cc @SpencerCDixon , just letting you know it's only temporary, needs to coincide with blueprint fixes) and pull as much else as possible into wiki pages (/cc @justingreenberg ).
Todo

[ ] redux-cli
[ ] https://github.com/davezuko/react-redux-starter-kit/issues/730

https://github.com/davezuko/react-redux-starter-kit/wiki/Fractal-Project-Structure /cc @justingreenberg -- highlighted it in README but can probably do an even better job of it.

Sounds good, finally back from job orientation/traveling.  Let me know if you'd like me to do

Nice, congrats and welcome back @SpencerCDixon .

Thanks!  Really sorry for being super MIA, crazy couple of weeks to say the least.  Going to create a new project with the Fractal Structure so I can get up to speed and be able to contribute.

Todo: https://github.com/davezuko/react-redux-starter-kit/issues/763

The Deployment Section of your README wisely steers clear of enterprise/production/youknowwhatImsayin servers, an area that would be very difficult for you to maintain.  However, we recently had a developer start out with your kit creating all of his work leveraging Koa with port 80 open on his box to demo.  Prior to doing what it takes to deploy on one of our real servers, he departed.
Since it turned out to be a challenge understand putting a server into 'HTML5 mode', much more to set up a nginx, Apache, etc. server into HTML5 mode, I was wondering if adding a reference to react-router's Configure Your Server  section or a reference to a document that I gather information on the subject might be helpful to those starting out with your kit.

@gkedge Woah, this got lost in the depths of the second issues page. That "Configure Your Server" post would definitely be helpful, so I will definitely do that.

This has been added, and I'll link to your post in the FAQ.

@davezuko the immutable.js guide got missed in this task.


Update vite to fix client pinging behind a proxy on WS disconnect

WHY are these changes introduced?
Fixes #0000
The current version of Vite in this project has a bug where when changes occur in the API behind a proxy (as in our case here), Vite pings the dev server to check the connection which is momentarily not running and throws an uncaught exception.  This requires a manual refresh of the page which looks like this in the Shopify Admin:

This was making it difficult to extend the API in the app.  I was constantly manually reloading the page.

WHAT is this pull request doing?
This updates Vite from 2.8.6 to 2.9.1 to incorporate these changes: https://github.com/vitejs/vite/pull/5466 which address this issue.  The API still reloads and goes through the auth process, but the manual refresh is no longer needed. :)
This doesn't violate any peer dependencies

Thanks @JaKXz I just pushed it :)

@jsullivan5 could you also try committing the result of npx yarn-deduplicate yarn.lock?


Go indexer: Add hooks to emit linkage edges. [phab:D1611]

Created by fromberger at 2017-05-04 04:05:45:
The main force of this change is to enable linkage metadata to be handled by
the Go extractor. The rest of the change is adding tests for the latter.
Included here are:

Add -extra_files flag to the command-line Go extractor.
This flag permits additional files to be included in each compilation
extracted by the tool, a useful property for testing.

Add an optional "data" attribute to the Go verifier test.
When this attribute is set, any files referenced are included in the
compilation unit generated by the extractor.

Extractor: Ensure required inputs have a vname set.

Add a -meta flag to the go_indexer tool.
This permits the indexer to scan for metadata files among required inputs.
If a nonempty suffix is given, a file matching the suffix is loaded as JSON
format linkage metadata. The name of the associated file is derived by
stripping the suffix to get the base name. This mechanism is not fully
general, but will serve for the common case of path-based meta files.

Add a metadata_suffix attribute to the Go verifier test rule.

Add a unit test for metadata linkage.

fromberger wrote at 2017-05-04 04:09:24:

Add a TODO to make linkage faster.

fromberger wrote at 2017-05-04 04:10:03:

Nicely format the metadata test file.

zarko commented inline (context lost during migration) at 2017-05-04 17:47:26:
Should this be "meta" or ".meta"?

zarko accepted this revision at 2017-05-04 17:47:26

fromberger commented inline (context lost during migration) at 2017-05-04 17:49:39:
I'm not sure what you mean—the flag name?

fromberger closed via commit 146c67b238a777e7087f107c2f3327531e126339 at 2017-05-04 17:52:10

zarko commented inline (context lost during migration) at 2017-05-04 17:59:48:
Ah, sorry, the values of this flag. It looks like you check for exact suffixes, not .suffixes.


FUDGE freezes in infinite loop when trying to modify graph instance

Freeze in this case means: electron is clearly still working and interactable (both the top menu and console, though the console doesn't react to sending commands), but nothing else will react to anything.
Steps to reproduce:

create two graphs
to second graph, add a transform component
add second graph as node to first graph
modify transform component, e.g. changing translation x value
FUDGE freezes

Alternative path to reproduce:

create two graphs
to second graph, add a transform component
to first graph, add a node, then the second graph as a child of the node. No problem so far
add a second instance of the graph as a child of the node. The same issue occurs.

Once i got a quickly repeating error message in the console reading Sync aborted, target already synced, but so far in only 1/8 tries. In the other 7/8 the console, while still interactable, doesn't show anything of note.

Please try again now

I can't reproduce the issue in either of the mentioned ways anymore. Let's hope it doesn't show up again in some other way.

I am having a similar issue with FUDGE freezing when interacting with the rigidbody component. Here are the steps to reproduce my error in a fresh project:

Create two graphs
To second graph, add a transform and a rigidbody component
Add second graph as node to first graph
Modify rigidbody component, e.g. changing typeBody, etc.
FUDGE freezes

Note: line 61 in Project.ts keeps firing

please test again

The issue is no longer reproduceable!


Modified metadrive

Hi, the main readme mentions the modified Metadrive. I was wondering if that is specified somewhere? Thank you!

Hello.
The modified files are (i) metadrive/manager/scenario_traffic_manager.py, in which we can specify the oppent vehicle and set its adversarial trajectory and (ii) metadrive/obs/top_down_renderer.py, in which the ego car, the opponent car and the other cars are rendered in red, blue and gray in the top-down view, respectively.
You can access the modified version of MetaDrive through the download link . Unzip metadrive.zip and place the metadrive folder into your project workspace. So that (i) it will not conflict with the official version of metadrive you have installed in other projects and (ii) it will avoid incompatibility with cat code caused by frequent metadrive updates.


implement runner-initiated split path

closes #22

Tests are passing for me locally, not sure why they fail in CI. I'll investigate!

Does anything more have to be done to merge this? @pabloem @pdames


FilePipe writeLineSeparator writes newline in separate write action allowing other threads to write between output and newline

Describe the bug
Using writeLineSeparator in a multithreading adapter gave a invalid result
result:
line1<Newline>
line2line3<Newline>
<Newline>
line4<Newline>

expected result
line1<Newline>
line2<Newline>
line3<Newline>
line4<Newline>

Category

Frank Framework

To Reproduce
Steps to reproduce the behavior:

create an adapter writing in bulk to a file using multiple threads
apply load

Expected behavior
By adding the newline to the string to write and write in 1 go this problem will no longer occur
Environment:

websphere
IAF 7.5-20200124.165603

Additional context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

Although we could try to send the line separator in some way 'closer' to the body of the file, there is and will be no guarantuee that the files sent from multiple threads will be in strictly consecutive order. I think the correct pattern would be make the multiple threads each write their files to a common directory, and have a single thread combine those files into a single file, via a DirectoryListener.

Hi Gerrit
I think doing a single write action with the newline added to the string before writing it to file will solve this issue. I understand the order of the rows cannot be guaranteed.
The option of writing to different files and merging them will still not guaranty order only solve this issue and be quite complex.
please try to add the newline in after the string and then write to file

@gvanbrakel Was this fix pickedup? as I remember it it was just adding the EOL to the string before writing it

Possible fix will be applied with the PR #1290.


feat(OCPADVISOR-143): Connect workloads to mocked API

OCPADVISOR-143
How to setup mock api:

Clone insights-results-aggregator-mock
make build (takes a few minutes for me, coffee time ☕)
2.1. can speed it up with make build -j 4 to run multiple jobs at once
make run
Test the mocked api curl localhost:8080/api/insights-results-aggregator/v2/namespaces/dvo
Run the app MOCK=true npm run start:proxy:beta
Workloads should load mocked data

Severities are missing, so they're still hardcoded.
Highest Severity is set to 5, but such level doesn't exist?
Workload details route has to be changed, because the api needs both cluster_uuid and namespace_uuid

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/Services/SmartProxy.js
44.44% <0.00%> (-5.56%)
:arrow_down:

:loudspeaker: Thoughts on this report? Let us know!.

:tada: This PR is included in version 1.23.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Automate CNAME records in cloudflare for new Ingress resources

Details
Due to not having a wildcard CNAME currently, all CNAMEs are manually created in the cloudflare console, ideally though whenever either an ingress or equivalent object is created the CNAMEs should be updated to include the new object automatically and likewise once an object is removed it should no longer persist as a CNAME in cloudflare.
EDIT** Wildcard CNAME records were available previously within cloudflares initial offering, however, it has since become an enterprise function which cost is unjustifiable for a homelab.

Testing out using the following: https://github.com/hotio/docker-cloudflare-ddns

Some other useful resources to investigate:

https://particule.io/en/blog/k8s-no-cloud/
https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md

external-dns doesn't currently support arm64 - currently, a PR in progress to add support with the current latest version and future versions until the upstream providers maintain a supported arm64 image https://github.com/raspbernetes/multi-arch-images/pull/126

https://github.com/helm/charts/tree/master/stable/nginx-ingress#externaldns-service-configuration


Observable.scan fails to pickup object from startWith

RxJS version:
"rxjs": "^5.0.3",
Code to reproduce:
import { Component } from '@angular/core';
import { Observable } from 'rxjs/Observable';
import { Subject } from 'rxjs/Subject';
import 'rxjs/Rx';

@Component({
  selector: 'app-root',
  template: `
    <button (click)='click$.next()'>Update</button>
    <h1>{{clock$ | async | date:'y MMM d jms'}}</h1>
  `,
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  click$ = new Subject();
  clock$;

  constructor() {
    this.clock$ = Observable.merge(
      this.click$,
      Observable.interval(1000)
    )
    .startWith(new Date())
    .scan((acc, curr)=> {
      const date = new Date(acc.getTime());
      date.setSeconds(date.getSeconds() + 1);
      return date;
    });
  }
}

Expected behavior:
Actual behavior:
ngrx-app: master$ ng s
** NG Live Development Server is running on http://localhost:4200. **
Hash: 4b06c933b6a34917c731
Time: 10139ms
chunk    {0} main.bundle.js, main.bundle.map (main) 3.42 kB {2} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.map (styles) 9.96 kB {3} [initial] [rendered]
chunk    {2} vendor.bundle.js, vendor.bundle.map (vendor) 2.84 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry] [rendered]

ERROR in ./src/app/app.component.ts
Module build failed: Error: /tmp/ngrx-app/src/app/app.component.ts (28,33): Property 'getTime' does not exist on type 'number | {}'.)
    at _checkDiagnostics (/tmp/ngrx-app/node_modules/@ngtools/webpack/src/loader.js:145:15)
    at /tmp/ngrx-app/node_modules/@ngtools/webpack/src/loader.js:172:17
 @ ./src/app/app.module.ts 14:0-47
 @ ./src/main.ts
 @ multi main
webpack: bundle is now VALID.

Additional information:
Angular app create using angular-cli

Would you share details of problem in Rx here? Error  Property 'getTime' does not exist on type 'number | {}'. is TypeScript Compiler error message by type inference and other than those I don't see specific failure.

I realize after I posted this error, it seem to be a problem with angular-cli doing something wonky and typescript. I wrote the same code with pure JS and Rxjs with now issue. Let me try coding this in TypeScript tonight and taking another look at it.

There is no starting value for the accumulator so the first run you get
undefined. If you use curr instead of acc it should work.
On Fri, Jan 20, 2017 at 3:55 PM Rajinder Yadav<EMAIL_ADDRESS>wrote:

I realize after I posted this error, it seem to be a problem with
angular-cli doing something wonky and typescript. I wrote the same code
with pure JS and Rxjs with now issue. Let me try coding this in TypeScript
tonight and taking another look at it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactiveX/rxjs/issues/2302#issuecomment-274177556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNdpQINpjDMM-9_FlJBa15fow1sIXqmks5rUR89gaJpZM4LpMNv
.

--
Thanks,
David

Shouldn't the startWith after the scan?
    this.clock$ = Observable.merge(
      this.click$,
      Observable.interval(1000)
    )
    .scan((acc, curr)=> {
      const date = new Date(acc.getTime());
      date.setSeconds(date.getSeconds() + 1);
      return date;
    })
    .startWith(new Date())

I've coded something similar using Rxjs with TS and it throws these same error, however the generated JS file runs fine.
@mattpodwysocki @david-driscoll I don't believe either those are the problem, if you code in ES2016 the code works fine.
Unfortunately in Angular CLI project when the error is thrown the app will not run, even though as @kwonoj has pointed out this is a TS error. I'll move this error to the Angular team.


Please make the open_epaper_link entities to be part of the devices, and give them an unique ID

Is your feature request related to a problem? Please describe.
At this moment, the created open_epaper_link.* entities, the ones used in the service, doesn't belong to any Home Assistant device. According to the interface, they don't have an unique ID, so they cannot be moved into a room, or can be renamed.
Describe the solution you'd like
It would be great if the entities are given an unique ID, so they can be renamed.
Also, IMHO they should be configured as part of the corresponding devices.

I second this, not being able to rename or associate entities properly with devices forces us to keep track of the MAC for identification. Will get annoying rather quickly when racking up dozens of devices

I would like to see this as well. Same for the cam-entitiy. All of them should be part of the corresponding devices.

Is this part of 0.4.4? I tried renaming one of my tags. All the named entities that were previously named with the device names are still correct, e.g. sensor.name_batter, sensor.name_rssi, etc. But the camera entity is still not named using the device name. It's named like camera.0000021edf9a3b15_cam which doesn't tell me which device it's part of. Is renaming the device (including renaming all entities) supposed to rename the camera?

Is this part of 0.4.4? I tried renaming one of my tags. All the named entities that were previously named with the device names are still correct, e.g. sensor.name_batter, sensor.name_rssi, etc. But the camera entity is still not named using the device name. It's named like camera.0000021edf9a3b15_cam which doesn't tell me which device it's part of. Is renaming the device (including renaming all entities) supposed to rename the camera?

I think that the rename feature of home assistant performs a 'search and replace'. That being said and if that is the case, if your camera does not contain the same name in the entity name as the device name prior to doing a name change it wont follow.
I wager you'd have to rename it manually this time to match your other entities containing _battery _rssi etc

The names of the Tags is now taken from the AP


⚠ Bofrost.be has degraded performance

In 85d84f6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 880 ms

Resolved: Bofrost.be performance has improved in 193a448 after 8 minutes.


Docker ignores DOCKER_OPTS when started through systemd

Description of problem:
When I setup the DOCKER_OPTS environment variable through a 'Environment' declaration in the systemd configuration file
'/etc/systemd/system/multi-user.target.wants/docker.service'
or in a dedicated custom file
'/etc/systemd/system/docker.service.d/enableRestRemoteApi.conf'
and starts docker as a service by
'systemctl start docker.service'
docker ignores/doesn't pick up the content of DOCKER_OPTS.
I am running Ubuntu 15.10 wily werewolf
Systemd is version 225
docker version:
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:20:08 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:20:08 UTC 2015
OS/Arch:      linux/amd64
docker info:
Containers: 19
Images: 130
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 168
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.0-19-generic
Operating System: Ubuntu 15.10
CPUs: 4
Total Memory: 3.558 GiB
Name: esben-ThinkPad-T440s
ID: ACN6:P7N7:Z53I:RJAZ:4XDU:2RKK:4XEO:Y2CH:UGWS:RXEG:GSW3:X3E3
WARNING: No swap limit support
uname -a:
Linux esben-ThinkPad-T440s 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
physical laptop
How reproducible:
Every time
Steps to Reproduce:

Stop docker service doing 'systemctl stop docker'
2.Add the line
Environment="DOCKER_OPTS=-H tcp://<IP_ADDRESS>:2375 -H unix:///var/run/docker.sock"
in
'/etc/systemd/system/multi-user.target.wants/docker.service'
in the [Service] section of the file
Reload the systemd configuration doing 'systemctl daemon-reload'
Start the service again doing 'systemctl start docker'
Do a
curl -X GET http://<IP_ADDRESS>:2375/images/json
to verify that the remote API doesn't run and you get a 'connection refused'

Actual Results:
Connection refused
Expected Results:
json-data

The DOCKER_OPTS env var is only used by upstart, see https://github.com/docker/docker/blob/6417c53c5ac4a066a0743c595e53c599a21c1e7e/contrib/init/upstart/docker.conf#L42
If you want to customize this, look in this section, that describes the use of an environment-file, and how to override the default ExecStart in a drop-in; https://docs.docker.com/engine/articles/systemd/#custom-docker-daemon-options
Hope this will help you further. I'm closing this issue, because I don't think this is a bug, but feel free to comment here if you think I closed this by mistake :+1:


Document vs Key/Value

I'm new at ArangoDB, so please allow the following newbie question:
How does the JSON differ between a document and a key/value pair? The document contains multiple attributes, a key/value pair has only 2 attributes?
The reason why I'm asking: In Web Interface I only find "Add a document", I'm missing "Add a key/value pair".
Best thanks in advance for help!

Another year later and it's still the same. No clear mention of how to create a key-value collection vs a normal document collection and/or what requirements must be met for a document collection to reap the performance benefits of a kv collection.

From the website:

Key/Value Store
ArangoDB implements the Key/Value store as a document collection that always has a primary key attribute. Absent secondary indexes, the collection always behaves as a simple key/value store. It is the easiest data model to scale.
The only sensible operations in this context are single key lookups and key/value pair insertions and updates. If the key attribute is the only sharding attribute, then sharding is done with the primary key and all operations scale linearly. If sharding is done using different shard keys, then a lookup of a single key involves asking all the shards and thus does not scale linearly.

@Simran-B That's probably the most technical explanation and it's not even in the docs! No wonder why I missed that. Your examples would be a good starting basis for a documentation page on this.
Still have some questions though. Is there a performance difference between RETURN DOCUMENT("<id>") and FOR doc IN coll FILTER doc._key == "<key>" LIMIT 1 RETURN doc? Which is the recommended way of querying for K/V? Is there special sharding setup to ensure linear scaling? etc

Played around with this more and I'm even more confused.
Let's say I want to have a collection that is 100% K/V with indexes on the key.
In arangojs, would this be db.collection('kvtest').save({_key: 'foo', value: 'bar'})?
Querying that with return DOCUMENT("kvtest/foo") seems to work, however explain says there's no indexes on it. Do I have to manually create them? I thought _key indexes were already created for me.
Also, what if i don't want the value: key in the document but just the actual value of 'bar' as the document's value? Is there somewhere else to put the value? There's no examples of this anywhere.
I tried going into aadvark and creating a new document with key 'foo' and no value, it creates an empty {} object. I then try editing the document by changing the value from {} to "bar" and hit save. It says it successfully saves but when I reload it's back to {} as the value. So I'm guessing you can't have plain literal values as the document's value?
Again, it's just really the lack of documentation on this aspect. Arangodb claims to be a multi-model with Key/Value store... but I'm at a loss at how this core feature is at all implemented, even after several hours of research.

We have plans for a key-value section in the docs, but it will be a project together with something else and certainly be after the 3.4 release. Will have to check with development about some technical details like performance.
You can compare both styles of read queries in your own setup of course. I remember difference in performance in older versions and DOCUMENT() being faster, but there were a few optimizations done to get them more on par.
Regarding index utilization and the query explain:

certain AQL functions such as WITHIN() or FULLTEXT() do utilize indexes internally, but their use is not mentioned in the query explanation for functions in general.

DOCUMENT() counts to that too. It does utilize the primary index internally, but this is not stated in the query explain because this is difficult to implement in the optimizer. The only exception that comes to mind is DISTANCE() in the 3.3 together with a geo index, which is transformed and handled differently from normal function calls. Index use should be in the query explain of such queries.
The _key attribute is always part of the document from a user perspective. It doesn't mean that it is in memory and persisted to disc like that however.
Your data has to have the form of a JSON document. If "bar" is your entire payload for key "foo", then
{ "value": "bar" } would be the minimal solution. ArangoDB is a JSON-document store from the usage standpoint, which can be used in a key-value fashion by not adding/using secondary indexes but only primary key lookups, no joins, leaving the default shard key to _key for linear scalability etc. Hope that makes sense.
I'll create a bug report for the Web UI, because it shouldn't confirm the saving for primitives.

Just as the commentors above, I was looking through the documentation about the key-value functionality but didn't find anything regarding how to use it. I came to the conclusion that you probably have to create a document with a single value and without secondary indexes, similar to when using MongoDB, and then googling the question I found this issue to confirm that.
For this comment I wanted to collect the documentation pages where I expected to read info about key-value pairs, and in the process of doing so, I finally found the following page in the "advanced topics" section:
https://docs.arangodb.com/3.4/Manual/Architecture/DeploymentModes/Cluster/DataModels.html#keyvalue-pairs
But that should really be more visible in the non-advanced sections of the docs, because just as the other commenters are saying, if ArangoDB mentions three models, but the overview pages in the documentation always only mentions two, this definitely leads to confused potential users.
This is the GitHub repo description:

ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values.

Then you go to the docs:

https://docs.arangodb.com/3.4/Manual/DataModeling/Concepts.html#data-model: Mentions documents and the way how graphs are handled, but zero mention of key-value.
https://docs.arangodb.com/3.4/Manual/DataModeling/: There's are specific sub-pages named "Documents" and "Graphs, Vertices & Edges", but again zero mention of key-value.

So I would suggest to mention key-values at least on the above two pages, maybe with a link to the "advanced topics" page regarding key-values.

Gotta admit I'm a little confused. Arango is "multi model" but from what I can tell it's just a document store with some sugar.
It seems like the "key-value store" model really means "don't store a JSON object as your document value, just store a single value."
Graph store appears to be store a pointer/vector as a JSON object as your document value.
Now, granted, I am only 24 hours in but this is my first impression. I could be wrong!

Three years later and it seems to be in the same state.
What I don't understand is in what way this is considered key/value and not a document

If "bar" is your entire payload for key "foo", then
{ "value": "bar" } would be the minimal solution

If you're already querying documents anyway, why would you limit yourself to a single key/value pair inside those documents.

I also recommend to document key/value support at least (as it is mentioned as a product feature) or better add some native functionality in the API and drivers. In principle you can as I did (in a very simple/naive way) using the spring data integration:
/**
 * A simple persistent key/value pair.
 * @see KeyValueArangoRepository
 */
@Document(collection = "KeyValues")
@PersistentIndex(fields = "key", unique = true)
@Data
public class KeyValue {

    @Id
    private String id;

    private String key;

    private Object value;
}

public interface KeyValueArangoRepository extends Repository<KeyValue, String> {

    /**
     * Increment the current numeric value and return the new one.
     * If the pair not exists, create it with the initial value and return this.
     */
    @Query("""
        WITH #collection
        UPSERT { key: @key }
        INSERT { key: @key, value: @init }
        UPDATE { value: OLD.value + 1 }
        IN #collection
        RETURN NEW.value
    """)
    long incrementAndGet(@Param("key") String key, @Param("init") long initialValue);
}

My Turn :)  I agree that if Arango is to support kv specific stores, then it should be a key value store, not a json document store.  All it needs is the ability to store primitives rather than a json document, and it turns into kv.
What if i need to store a lot of kv data points alongside graphs for instance?  The docs state:

Very large numbers of very small documents may have an unexpectedly big overhead: Each document needs has a certain amount extra storage space, depending on the storage engine and the indexes you added to the collection. The overhead may become significant if your store a large amount of very small documents.

So, while you can use it as a kv store, it doesn't actually have any performance benefits? and in-fact has performance penalties as a result.  So, in my opinion, it should either implement a kv store collection, or not advertise it as supporting kv.  A single attributed json document does not make it a kv.


MacOs catalina is not supported

Hello Team,
I upgraded my MacOS to Catalina and az aks stopped working. I do not see aks option anymore.
Does azure-cli supports this new version of MacOS or is there any plan to release its support?
Best regards,
Swapnil

@fengzhou-msft  please take a look.

@swapnild2111 can you tell me more about how you installed azure-cli, what is the version you use(are you able to run az --version)?

I have installed az with homebrew on mac.
`$az --version
azure-cli (2.0.17)
acr (2.0.11)
acs (2.0.15)
appservice (0.1.16)
batch (3.1.3)
billing (0.1.4)
cdn (0.0.8)
cloud (2.0.7)
cognitiveservices (0.1.7)
command-modules-nspkg (2.0.1)
component (2.0.7)
configure (2.0.10)
consumption (0.1.4)
container (0.1.10)
core (2.0.16)
cosmosdb (0.1.12)
dla (0.0.11)
dls (0.0.13)
eventgrid (0.1.3)
extension (0.0.2)
feedback (2.0.6)
find (0.2.6)
interactive (0.3.9)
iot (0.1.11)
keyvault (2.0.10)
lab (0.0.10)
monitor (0.0.9)
network (2.0.14)
nspkg (3.0.1)
profile (2.0.12)
rdbms (0.0.6)
redis (0.2.8)
resource (2.0.14)
role (2.0.11)
servicefabric (0.0.3)
sf (1.0.8)
sql (2.0.11)
storage (2.0.15)
vm (2.0.14)
Python location '/Users/swapnil/lib/azure-cli/bin/python'
Extensions directory '/Users/swapnil/.azure/cliextensions'
Python (Darwin) 2.7.16 (default, Aug 24 2019, 18:37:03)
[GCC 4.2.1 Compatible Apple LLVM 11.0.0 (clang-1<IP_ADDRESS>) (-macos10.15-objc-s
Legal docs and information: aka.ms/AzureCliLegal`

2.0.17 is quite old now. Please run brew upgrade azure-cli to upgrade to the latest version.

Thank you :)


Support for Curve25519

New API Proposal: Curve25519
Motivation:
I know CryptoKit provides Curve25519, but to export the public key as a pem string is not possible, as the raw representation of the key is compressed 32 bytes. For pem, we require uncompressed bytes along with ASN1 encoding and other stuff right?
Importance:
Saw in the source code the files like SubjectPublicKeyInfo.swift. This helps wrap the raw bytes and export them as pem. My current requirement is to export the curve25519 public key as a pem string. No libraries out there does this currently.

This is a good idea. I'll circulate the idea around and see how we feel about it.

I will add:

as the raw representation of the key is compressed 32 bytes. For pem, we require uncompressed bytes along with ASN1 encoding and other stuff right?

This is not true: Curve25519 public keys are not being emitted compressed, but they are always 32-bytes (Curve25519 keys only need the x coordinate). So the current output of the library is sufficient to produce a PEM format.

So the current output of the library is sufficient to produce a PEM format

Yes, I tried.
I'm currently achieving the same by prefixing a standard header that I got from Eskimo from Apple developer forums. But I'm sure everyone would be having this requirement, and nowhere is the prefix data for each curve type available as a list online.
Here's my question and the answer that I got for this. This is working 👍
https://developer.apple.com/forums/thread/679787

Just wanted to mention regarding:

and nowhere is the prefix data for each curve type available as a list online.

These values are available out on the internet in RFC8410 listed by the algorithm identifier OID.
They are buried in an ASN.1 structure for SubjectPublicKeyInfo so it's hard to identify the ones that count for the algorithm you are using.
It looks like Quinn was giving you a head start on defining this structure when the following was provided:
let prefix = Data([0x30, 0x2A, 0x30, 0x05, 0x06, 0x03, 0x2B, 0x65, 0x6E, 0x03, 0x21, 0x00])

Which roughly translates to:
0x30 = SEQUENCE (42 bytes length (0x2A))
0x30 = SEQUENCE (5 bytes length (0x05))
0x06 = OBJECT IDENTIFIER (3 bytes length (0x03))
0x2B = 43   (I believe this represents an OID formula for 140+3 or 1.3 (x40+Y))
0x65 = 101  {iso(1) org(3) thawte(101)} (https://oidref.com/1.3.101)
0x6E = 110  (OID id-X25519(110) for https://datatracker.ietf.org/doc/html/rfc8410)
0x03 = BIT STRING (33 bytes in length 0x00 + your key bytes)
And that is why appending your raw key bytes to your prefix worked out to generate your PEM.

Thank you @agnosticdev for that detailed description :)

Renaming the issue to better reflect what this is about. We'll take it in for consideration!


Voucher signup link

Need more iteration and do not have to be done before Swetugg Stockholm 2020.
A unique link (that can't be enumerated) that is created against a company name or optional string. When using that link the user gets an form similar to the one you get when signing up for a ticket. But there is a maximum number of signups you can do to every link, that is stated when creating the link. that correspond to the number of tickets the company have purchased on an invoice. Both we as organizer and the company can see how many ticket in total and how many that have signed up so far. All the data about the attendees needs to be encrypted and we need different export funktions to export meal/allergiers list and a list for the nametags.

Is solved through the external ticket-system instead.


Fix sandbox link in article

After conneting to github repo, sandbox link was changed, update it in article

@zerobias small fix in doc

👌 👌


react-scripts - CVE-2021-3803 - react-script module nth-check denial of service CVSS 7.5

Describe the bug
(Write your answer here.)
react-script inner dependency /embed module nth-check-1.0.2
https://nvd.nist.gov/vuln/detail/CVE-2021-3803
Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment
see above. kindly provide fixed in react-script update.

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)
Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Description of the Bug
The React app created using Create React App (CRA) has encountered a CSS issue after implementing React code splitting. When navigating to a code-split component for the first time, the CSS for that component is not applied. However, if the user navigates to another component and then returns, the CSS is correctly applied.
Additionally, there is an inner dependency issue with react-scripts related to the nth-check module, version 1.0.2, which has a vulnerability as described in CVE-2021-3803. This vulnerability involves inefficient regular expression complexity.
Did You Try Recovering Your Dependencies?
Yes, attempts to recover dependencies were made, but the issue persists.
Which Terms Did You Search for in User Guide?
Code splitting
CSS issues with code splitting
React Suspense CSS
CRA CSS not loading
CVE-2021-3803
React-scripts dependency update

Environment
Create React App version: 5.0.0 (example version)
React version: 18.0.0 (example version)
react-scripts version: 5.0.0 (example version)
Browser: Chrome 90, Firefox 88 (example versions)
Operating System: macOS 11.4, Windows 10 (example versions)

Steps to Reproduce
Create a React app using CRA.
Implement code splitting using React's lazy and Suspense.
Add CSS imports in the code-split component.
Navigate to the code-split component for the first time.
Observe that CSS is not applied.
Navigate to another component and return to the code-split component.
Observe that CSS is now correctly applied.

Expected Behavior
The CSS should be applied correctly the first time the code-split component is mounted.
Actual Behavior
The CSS is not applied the first time the code-split component is mounted. It only applies after navigating away and then returning to the component.
Reproducible Demo
Here is a simplified version of the project setup:
import React, { Suspense, lazy } from 'react';
import './styles.scss'; // Ensure global styles are loaded
const Search = lazy(() => import('./search/search'));
function Parent() {
return (
<Suspense fallback={Loading...}>

);
}
export default Parent;
import React from 'react';
import './search.scss';
function Search() {
return (

{/* Your search component code */}

);
}
export default Search;
Additional Notes
Vulnerability in nth-check
The react-scripts package includes an outdated version of the nth-check module, which is vulnerable to inefficient regular expression complexity as detailed in CVE-2021-3803. This issue needs to be addressed in an update to react-scripts to include a patched version of nth-check.

Has this issue been resolved? I am currently facing the same problem.

Any updates on this?

I resolved nth-check vulnerability issue by using overrides in package.json:
"overrides": {
"nth-check": ">=2.0.2",
},


Cannot create default exact Route component inside a Switch

Version
4.2.0
Test Case
https://codesandbox.io/s/kxk110lqy3
Steps to reproduce

Define an ExactRoute component:const ExactRoute = ({exact, ...rest}) => <Route exact={true} {...rest} />
Use a bunch of Route inside a Switch (this bug does not apply when no Switch are used)
Among those routes, define one using ExactRoute, for instance: <ExactRoute path="/about" component={About} />

Expected Behavior
I am trying to circumvent the fact that exact defaults to false (see #4958) by creating my own ExactRoute component. I would expect my ExactRoute component to match only if it is an exact match.
Actual Behavior
If you go to /about/me (a non-exact match), the About component will render
Alternatively, the matching will be exact only if exact is an argument of ExactRoute: <ExactRoute exact path="/about" component={About} />

Switch reads the props of its children directly. So, a dirty little secret is that you can actually put any component under it and it will work as long as the props are present.
So, you can't wrap a Route component and pass it to a Switch, unfortunately.

Should this be clarified in the docs?

@timdorr

So, you can't wrap a Route component and pass it to a Switch, unfortunately.

May I ask again why not? We are doing this in pretty much every project we have and seems to be working fine for us.
<Switch>
      <Route
        exact
        path="/login"
        render={props =>
          isAuthenticated() ? (
            <Redirect to={{ pathname: '/myfiles', from: props.location }} />
          ) : (
            <LoginPage {...props} />
          )
        }
      />
      <Route exact path="/logout" component={LogoutPage} />
      <PrivateRoute exact path="/myfiles" component={MyWCABFilesPage} />
      <PrivateRoute exact path="/search" component={SearchPage} />
</Switch>

The above behaves just like you'd expect. PrivateRoute is a Route wrapper that redirects users to /login if they are not authenticated.

Because you are using the same props as a vanilla Route. The OP is trying to avoid using the exact prop, but Switch reads that directly, so it wouldn't be available to read.

I see now, thanks for the clarification. But, IMO, your original answer might mislead some people and seems to imply something different.

I added a small clarification there.

@timdorr Many thanks 😄


Fix override of error message for 401 response

This PR fixes the override of the exception message for 401 error responses.  Previously the message was set unconditionally to a standard message in the SDK core.  Now that standard message is only used for 401 errors if no suitable error message is found in the response body.
Fixes #58.

:tada: This PR is included in version 1.7.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Danger is failing for valid PR

Danger failed on the PR #34 even though it was a valid PR stating that the PR was not all on the same line.
There seems to be some logic issue that requires some investigation and debugging.
Error Message:
Danger: ⅹ Failing the build, there is 1 fail.
## Failures
Please make sure all of your changes are on the same line and that you are only modifying one row.

Steps to reproduce:

Setup the project according to the Contributing Guide
Run npx danger pr https://github.com/twilio-labs/open-pixel-art/pull/34

You should see the error message outlined above. Instead it should pass as a valid submission.

Same thing happened in #33

This started showing up more regularly. I'll investigate myself to fix this.


Suggestion: Chunk loading idea (if possible)

Tthis may not impact the server performance, but may impact the client performance FPS and may be helpful against anti xray in some sort.
If the player in y 60 or higher load chunks from y 40 to y 255, and if the player in y 45 or lower load chunks from y 0 to y 128.
Now lets say a player dug down from y 65 to 43 check if the entire chunk details is sent to that player or not, if not update all the loaded chunks that doesn't have their full details sent to the player to have chunks details from y 0 to y 255. The same thing should be applied for a player that build or climb up from y 13 to y 67.

Im fairly certain the game already does this. If it doesn't, work though, this would be a good request for Tuinity, though.


[tests] Idea: Use a runtime test library for tests

@alexeygolev showed an interesting way of writing tests for the ramda libdef over in this pull request: https://github.com/flowtype/flow-typed/pull/95
Basically the idea is that we could have the test runner (a) typecheck the test code (contains type asserts just like we have today) and then (b) actually run the tests (using the actual npm library) to make sure they pass.
This could help bridge the uncertainty gap between a libdef and it's actual implementation.

So this is actually just running the flow-checking mechanism and then a [generic-test-framework] right after? looks nice, although I would definitely opt for tape instead of mocha, since it's much better isolated from the global environment...

So this is actually just running the flow-checking mechanism and then a [generic-test-framework] right after?

@ryyppy yea, that's right. The idea is to both confirm the validated types and give a means of confirming that the libdef matches the implementation as well.

I just made another thought about that... will this scale? When I imagine to run all tests and we need to install all npm dependencies for all libdefs just to run the tests, we will have first of all a huge install process and other than that a huge disk space waste just for developing some simple declarations...
Wouldn't it be better to tell lib-maintainers who commit stuff here to integrate the flow-tests process in their lib-tests themselves? Maybe  give them some best-practise guidance for adding libdef testing via npm test or so?

That's a good point with regard to the need to run all tests. We currently run all tests in travis on pull requests, but we really should only run tests for things that have changed. Once we're doing that, I think the speed will be manageable.
That said, running all tests is still useful sometimes (and is already slow), so perhaps the default behavior here should be that runtime tests only execute when a special flag is passed to run-tests? That way you can just do static-check types independent of the runtime tests.

Wouldn't it be better to tell lib-maintainers who commit stuff here to integrate the flow-tests process in their lib-tests themselves?

This is generally not a bad idea, but I don't know how practical it is on a wider scale. In order to verify that a libdef matches the implementation you really do need a statically-typed consumer of the library (like a statically-typed test). While I would always encourage lib maintainers to write tests, it's also common to write tests in ways that are hard (if not impossible) to statically verify. Meta-programming is pretty common and useful in testing (think about dynamic test harnesses and data-dependent conditionals, etc).
Overall I think you might've convinced me that we should at least make these kinds of runtime tests optional since they could pose a lot more burden for writing a simple test than is necessary in some cases. Perhaps they're only useful when someone as a reason to be extra thorough with their libdefs.


Help Creating a Custom Week View

Firstly, I'd like to thank the contributors to this project! It is awesome and greatly appreciated 👍.
I am looking for help creating a custom view for the week. I am trying to figure out what the best approach would be for creating the view in the attached image. In essence I want to create a view for the week that displays events on each day without putting them / displaying them in a timeslot. I just want a simple list of events to be rendered under each day. How would I go about doing this?
Thank you 😄

What do you think about having a calendar that only supports 'all day events' by hiding every other kind of event?
Taking the code from the examples page, I made a quick custom css as a proof of concept: https://codesandbox.io/s/react-big-calendar-example-lu1c0?file=/customStyle.css
You should be able to click and create more events on each day column! Let me know what you think

s

@FdelMazo This is perfect and is exactly what I needed, thank you! Very much appreciated 😄

You are welcome! Make sure to close the issue to avoid adding noise to this lib!

The solution provided by @FdelMazo works like a charm so closing the issue.


QOL: Transaction Search

Added a clear search button and moved the settings to the Accounts Page where it belongs :P

I've fixed issue #396 in this branch as well.

Thank you!


Refactor and improve the Camera Sensor and example

This is currently in progress: https://github.com/edbeeching/godot_rl_agents_examples/pull/14#issuecomment-1837311171
This should fix the sensor for Godot 4.2 so it works during training.
What's will still be left is to look into:

[ ] Onnx export / inference support (including considering preprocessing such as normalization, and potential frame stacking support in the sensor),
[ ] Potential grayscale feature (reduce the size where colors are not necessary)

As well as any other features that might be useful.

Hey @Ivan-267 are any items left to do on this?

Those were just some proposed options, none were implemented yet. I've tried the sensor a bit after writing those and I can confirm that we can't export onnx / run inference right now.


Regex replace not working

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.023Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-markdownlint
Dav
0.12.0

xml
Dot
1.9.2

latex-workshop
Jam
3.7.0

mysql-scratchpad
jbl
0.1.1

Go
luk
0.6.67

python
ms-
0.8.0

PowerShell
ms-
1.5.1

material-icon-theme
PKi
3.1.0

convert-markdown-to-html
sak
5.8.1

markdown-pdf
yza
0.1.7

(2 theme extensions excluded)

Steps to Reproduce:

Global scope search (ctrl + shift + f)
Type in regex, and replace
Regex not working

Reproduces without extensions: Yes

@zaynr Groups are working for me for example
Regex (extensionTreeItem)(:) with replace terms $1[]$2 replacing extensionTreeItem: with extensionTreeItem[]:

Can you please provide

regex
replace pattern
text to be replaced
replacement text

This will be helpful to reproduce it easily. Thanks


Zoom in data visualization

Would be great to allow a deeper zoom level with geohash size change.

Another project is holding me up but hoping to address this roughly first or second week of June

Going to archive this for now... will revisit after 2023 catch data are updated.


sonoff' accesses hass.helpers.system_info.  Deprecated in HA 2024.11

Hi
I get this messages:
Detected that custom integration 'sonoff' accesses hass.helpers.system_info. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from system_info directly at custom_components/sonoff/system_health.py, line 61: info = await hass.helpers.system_info.async_get_system_info(), please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
And if it helps, I create this issue!

duplicated: https://github.com/AlexxIT/SonoffLAN/issues/1434


Update README

The current README shows import Flow in the code examples, while Xcode wants me to use import FlowTables using the current version.

Thank you


Enables conv and sliding_window tests on vulkan.

These are both passing locally with swiftshader. Unsure of their status on an nvidia gpu, as issue #2659 doesn't say if it was an nvidia only issue (or one that affected swiftshader too).

Slide window is failing (https://github.com/google/iree/issues/2659). Not so sure about the conv. It's probably passing. Could you remove sliding window and trigger a build with kokoro manually?

Ran the tests on GPU and confirmed that conv_test passes on both GPU and SwiftShader, but sliding_window_test only passes on SwiftShader.


Suggestion- use statement with only

Hi @SnowHydrology and @GreyEvenson-NOAA,
Looking through the grid implementation (which looks great!), I noticed most of use statements do not have only,so just pointing to the module.  By explicitly specifying public entities (subroutine, function or variables etc.) with only, it is easier to tell where the entities are coming from, and easier to trace the code, and also allow to avoid name conflict (can rename referred entities.  As the codes get complex, this helps maintainability, code documentation without comments.
something to think about...
https://stackoverflow.com/questions/51686745/why-should-i-use-use-only-in-fortran

Hi @nmizukami,
Thanks for mentioning this and including the stackoverflow post. It's helpful/informative feedback! I'll add this to my to-do list.
@SnowHydrology has mentioned your expertise in this past. I hope to meet you at some point!


Use a SpinBox in the inspector array resize dialog

Replaces the LineEdit with a SpinBox.
Makes the dialog allow resizing to 0.
Increases the min width of the inspector array resize dialog so that the window title is visible.

Before
After

Out of curiosity, why is the new size using LineEdit and not SpinBox?

Out of curiosity, why is the new size field using LineEdit and not SpinBox?

That's a good question. I'm not sure why that was done. I've updated this PR to make it use a SpinBox instead.

Thanks!


Warning during backup : "The service wekan didn't fully started before the timeout."

Hi,
When backuping Wekan (yunohost backup creatte --apps wekan), I have almost every time a warning about  "The service wekan didn't fully started before the timeout." caused by a LDAP Background Sync error (regarding the log provided)
But the service still launches, despite this message.
Here is the full log :
https://paste.yunohost.org/hijiqinufe.vbs
# yunohost --version
yunohost:
  repo: stable
  version: <IP_ADDRESS>
yunohost-admin:
  repo: stable
  version: <IP_ADDRESS>
moulinette:
  repo: stable
  version: <IP_ADDRESS>
ssowat:
  repo: stable
  version: 3.6.4

#  yunohost app info wekan
description: Trello-like kanban
license: MIT
name: Wekan
version: 3.55~ynh1

I made some test to the version 3.55~ynh1 without encountering that issue.
Maybe you should upgrade first to actual wekan version => 3.79~ynh1

Hi, sorry for the delay in responding.
Despite upgrading wekan, I have still the same error (but not the same log), this time with every backup.
See the log here : https://paste.yunohost.org/ijoxaxeyup.vbs
It is the last user created on YNH that appears in the log (it changes to the last when creating a new one), no matter if the user has access to wekan or not, has already logged in wekan or not (I have tested these cases).
# yunohost --version
yunohost:
  repo: stable
  version: <IP_ADDRESS>
yunohost-admin:
  repo: now
  version: <IP_ADDRESS>
moulinette:
  repo: stable
  version: <IP_ADDRESS>
ssowat:
  repo: stable
  version: <IP_ADDRESS>

# yunohost app info wekan
description: Trello-like kanban
license: MIT
name: Wekan
version: 3.79~ynh1

When doing the backup, can you in another windows launch journalctl -feu wekan
at the beginning of the backup, wekan service is stopped, and started at the end of the backup. During the start part, you should see a line with Started Wekan, task board in the journactl windows let me know if the line is different.

Hi,
The line Started Wekan, task board is present in the journalctl. See here : https://paste.yunohost.org/xicisetaba.pl
I made 6 backups in a row, 4 with nothing to report, 2 with the same problem described in this issue (the second one and the last one). The journalctl output is the same in both cases.

Quick update : since my last message, all my backups (via a cronjob that runs every day) have the following issue.
I have tested on another YNH instance too and encountered the same issue.

Doing several backups, I also have the error sometimes...
And the error comes even if wekan service is started.
I've opened an issue at https://github.com/YunoHost/issues/issues/1573

Well, after some work on the issue, as even it says that the service is not started... it's started. We decided to not found a solution.


Ensure leader member sorted 1st

Pull Request Test Coverage Report for Build 963

9 of 10 (90.0%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 79.122%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/brod_cg_commits.erl
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

src/brod_consumer.erl
3
74.77%

Totals

Change from base Build 955:
-0.1%

Covered Lines:
2001

Relevant Lines:
2529

💛  - Coveralls


chore: Add tests for name and version config

While reviewing https://github.com/kaylareopelle/opentelemetry-ruby-contrib/pull/4, I decided to write some of the tests for the name and version config options. They're currently failing, but I think these are the scenarios we want to pass.

Closing, as this code has already been merged into the logger-instrumentation branch.