vscode takes more than 30 seconds to start

Type: Bug
Starting earlier this week, vscode takes around 30 seconds or more to start on my linux machine, even with all extensions disabled and no workspace selected.
I get several messages that the window is not responding and need to click on "Continue waiting".
It does not even render the top-most menu (File, Edit, etc.) during this time, like I saw in some other recent issues.
After this long startup it works as usual.
I think this is the same or a similar issue to https://github.com/microsoft/vscode/issues/190360, but that one was closed and @deepak1556 asked another user, who was reporting similar behavior, to create a new issue.
Things I tried, which didn't show any improvements:

Deleting the GPU Cache in ~/.config/Code/GPUCache
Deleting the Code Cache in ~/.config/Code/Code Cache
code --disable-gpu
code --disable-features=CalculateNativeWinOcclusion
code --no-sandbox
Starting with an empty user dir
Uninstalling and reinstalling code
Installing code-insiders (same issue), uninstalling code-insiders
code --password-store="basic"

The redacted output of code --verbose --vmodule="*/components/os_crypt/*=1"
[136138:0915/110016.132362:VERBOSE1:key_storage_util_linux.cc(54)] Password storage detected desktop environment: GNOME
[136138:0915/110016.173525:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2023-09-15T09:00:16.219Z] [File Watcher (node.js)] Request to start watching: /home/user/.config/Code/User (excludes: <none>, includes: <all>),/home/user/.config/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2023-09-15T09:00:16.227Z] Starting VS Code
[main 2023-09-15T09:00:16.227Z] from: /usr/share/code/resources/app
[main 2023-09-15T09:00:16.227Z] args: {
  _: [],
  diff: false,
  merge: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  'pre-release': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  'disable-chromium-sandbox': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: false,
  'enable-smoke-test-driver': false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '7346e23b-af02-4155-a12b-7ce240bbf770',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  'disable-gpu-sandbox': false,
  '__enable-file-policy': false,
  'enable-coi': false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  vmodule: '*/components/os_crypt/*=1',
  'disable-dev-shm-usage': false,
  'profile-temp': false,
  logsPath: '/home/user/.config/Code/logs/20230915T110016'
}
[main 2023-09-15T09:00:16.228Z] Resolving machine identifier...
[main 2023-09-15T09:00:16.229Z] Resolved machine identifier: 35cf8fef0352205ea27a549b3225b163da5ac48caa8efa83497c7c7b95ab0b15
[main 2023-09-15T09:00:16.229Z] Main->SharedProcess#connect
[main 2023-09-15T09:00:16.231Z] [File Watcher (node.js)] Started watching: '/home/user/.config/Code/User'
[main 2023-09-15T09:00:16.231Z] StorageMainService: creating application storage
[main 2023-09-15T09:00:16.233Z] ElectronURLListener: waiting for window to be ready to handle URLs...
[main 2023-09-15T09:00:16.233Z] lifecycle (main): phase changed (value: 2)
[main 2023-09-15T09:00:16.233Z] windowsManager#open
[main 2023-09-15T09:00:16.233Z] windowsManager#open pathsToOpen [
  {
    backupPath: '/home/user/.config/Code/Backups/1694766829611',
    remoteAuthority: undefined
  }
]
[main 2023-09-15T09:00:16.233Z] windowsManager#doOpenEmpty {
  restore: true,
  remoteAuthority: undefined,
  filesToOpen: undefined,
  forceNewWindow: true
}
[main 2023-09-15T09:00:16.234Z] IPC Object URL: Registered new channel vscode:d3cff652-9b8d-4e14-8d65-c4f5d8c1e91c.
[main 2023-09-15T09:00:16.234Z] window#validateWindowState: validating window state on 2 display(s) { mode: 1, x: 3419, y: 7, width: 843, height: 1401 }
[main 2023-09-15T09:00:16.234Z] window#validateWindowState: multi-monitor working area { x: 2560, y: 0, width: 2560, height: 1440 }
[main 2023-09-15T09:00:16.234Z] window#ctor: using window state { mode: 1, x: 3419, y: 7, width: 843, height: 1401 }
[main 2023-09-15T09:00:16.262Z] window#load: attempt to load window (id: 1)
[main 2023-09-15T09:00:16.267Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2023-09-15T09:00:16.267Z] lifecycle (main): phase changed (value: 3)
[main 2023-09-15T09:00:16.267Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2023-09-15T09:00:16.267Z] update#setState idle
[main 2023-09-15T09:00:16.288Z] [File Watcher (node.js)] Started watching: '/home/user/.config/Code/User/settings.json'
[main 2023-09-15T09:00:18.772Z] lifecycle (main): phase changed (value: 4)

[NOTHING HAPPENS HERE]

[main 2023-09-15T09:00:46.268Z] update#checkForUpdates, state =  idle
[main 2023-09-15T09:00:46.268Z] update#setState checking for updates
[main 2023-09-15T09:00:46.268Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[136138:0915/110046.340184:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
[main 2023-09-15T09:00:46.343Z] CodeWindow: detected unresponsive
[main 2023-09-15T09:00:46.428Z] update#setState idle
[136178:0915/110052.086370:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2023-09-15T09:00:52.147Z] resolveShellEnv(): skipped (VSCODE_CLI is set)

Startup Performance
## System Info

Code: 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d)
OS: linux(6.2.0-32-generic)
CPUs: 12th Gen Intel(R) Core(TM) i7-1260P(16 x 1587)
Memory(System): 46.74 GB(40.95GB free)
Memory(Process): 195.75 MB working set(112.13MB private, 1.06MB shared)
VM(likelihood): 0%
Initial Startup: true
Has 0 other windows
Screen Reader Active: false
Empty Workspace: true

Performance Marks

What
Duration
Process
Info

start => app.isReady
83
[main]
initial startup: true

nls:start => nls:end
0
[main]
initial startup: true

require(main.bundle.js)
44
[main]
initial startup: true

start crash reporter
2
[main]
initial startup: true

serve main IPC handle
1
[main]
initial startup: true

create window
27
[main]
initial startup: true, state: 0ms, widget: 27ms, show: 0ms

app.isReady => window.loadUrl()
91
[main]
initial startup: true

window.loadUrl() => begin to require(workbench.desktop.main.js)
36084
[main->renderer]
NewWindow

require(workbench.desktop.main.js)
189
[renderer]
cached data: YES, node_modules took 0ms

wait for window config
1
[renderer]
-

init storage (global & workspace)
19
[renderer]
-

init workspace service
17
[renderer]
-

register extensions & spawn extension host
241
[renderer]
-

restore viewlet
16
[renderer]
workbench.view.explorer

restore panel
0
[renderer]
-

restore & resolve visible editors
91
[renderer]
1: PerfviewInput

overall workbench load
219
[renderer]
-

workbench ready
36706
[main->renderer]
-

renderer ready
451
[renderer]
-

shared process connection ready
0
[renderer->sharedprocess]
-

extensions registered
37050
[renderer]
-

Extension Activation Stats

Extension
Eager
Load Code
Call Activate
Finish Activate
Event
By

vscode.git
true
32
13
62
*
vscode.git

vscode.git-base
true
3
0
0
*
vscode.git

vscode.github
true
8
2
3
*
vscode.github

vscode.debug-auto-launch
false
2
1
0
onStartupFinished
vscode.debug-auto-launch

vscode.emmet
false
11
10
0
onLanguage
vscode.emmet

vscode.extension-editing
false
7
1
0
onLanguage:markdown
vscode.extension-editing

vscode.github-authentication
false
14
1
2
onStartupFinished
GitHub.vscode-pull-request-github

vscode.markdown-language-features
false
52
6
331
onLanguage:markdown
vscode.markdown-language-features

vscode.markdown-math
false
9
0
0
api
vscode.markdown-language-features

vscode.merge-conflict
false
10
3
2
onStartupFinished
vscode.merge-conflict

vscode.microsoft-authentication
false
15
1
9
onAuthenticationRequest:microsoft
vscode.microsoft-authentication

GitHub.vscode-pull-request-github
false
63
1
247
onStartupFinished
GitHub.vscode-pull-request-github

ms-vscode-remote.remote-containers
false
47
0
60
onStartupFinished
ms-vscode-remote.remote-containers

streetsidesoftware.code-spell-checker
false
47
0
646
onStartupFinished
streetsidesoftware.code-spell-checker

Terminal Stats

Name
Timestamp
Delta
Total

code/terminal/willGetTerminalBackend
1694768156403
0
0

code/terminal/didGetTerminalBackend
1694768156447
44
44

code/terminal/willReconnect
1694768156447
0
44

code/terminal/willGetTerminalLayoutInfo
1694768156447
0
44

code/terminal/didGetTerminalLayoutInfo
1694768156556
109
153

code/terminal/didReconnect
1694768156556
0
153

code/terminal/willReplay
1694768156556
0
153

code/terminal/didReplay
1694768156556
0
153

code/terminal/willGetPerformanceMarks
1694768156556
0
153

code/terminal/didGetPerformanceMarks
1694768156604
48
201

Raw Perf Marks: main
Name	Timestamp	Delta	Total
code/timeOrigin<PHONE_NUMBER>694.254	0	0
code/didStartMain<PHONE_NUMBER>768	73.74609375	73.74609375
code/willStartCrashReporter<PHONE_NUMBER>774	6	79.74609375
code/didStartCrashReporter<PHONE_NUMBER>776	2	81.74609375
code/mainAppReady<PHONE_NUMBER>851	75<PHONE_NUMBER>5
code/willGenerateNls<PHONE_NUMBER>852	1<PHONE_NUMBER>5
code/willLoadMainBundle<PHONE_NUMBER>856	4<PHONE_NUMBER>5
code/fork/willLoadCode<PHONE_NUMBER>865	9<PHONE_NUMBER>5
code/registerFilesystem/file<PHONE_NUMBER>896	31<PHONE_NUMBER>5
code/registerFilesystem/vscode-userdata<PHONE_NUMBER>896	0<PHONE_NUMBER>5
code/didLoadMainBundle<PHONE_NUMBER>900	4<PHONE_NUMBER>5
code/willStartMainServer<PHONE_NUMBER>906	6<PHONE_NUMBER>5
code/didStartMainServer<PHONE_NUMBER>907	1<PHONE_NUMBER>5
code/willCreateCodeWindow<PHONE_NUMBER>915	8<PHONE_NUMBER>5
code/willRestoreCodeWindowState<PHONE_NUMBER>915	0<PHONE_NUMBER>5
code/didRestoreCodeWindowState<PHONE_NUMBER>915	0<PHONE_NUMBER>5
code/willCreateCodeBrowserWindow<PHONE_NUMBER>915	0<PHONE_NUMBER>5
code/didCreateCodeBrowserWindow<PHONE_NUMBER>942	27<PHONE_NUMBER>5
code/didCreateCodeWindow<PHONE_NUMBER>942	0<PHONE_NUMBER>5
code/willOpenNewWindow<PHONE_NUMBER>942	0<PHONE_NUMBER>5

Raw Perf Marks: localPtyHost
Name	Timestamp	Delta	Total

Raw Perf Marks: renderer
Name	Timestamp	Delta	Total
code/timeOrigin<PHONE_NUMBER>943	0	0
code/didStartRenderer<PHONE_NUMBER>023	36080	36080
code/willWaitForWindowConfig<PHONE_NUMBER>023	0	36080
code/didWaitForWindowConfig<PHONE_NUMBER>024	1	36081
code/willShowPartsSplash<PHONE_NUMBER>024	0	36081
code/didShowPartsSplash<PHONE_NUMBER>025	1	36082
code/willLoadWorkbenchMain<PHONE_NUMBER>026	1	36083
code/didLoadWorkbenchMain<PHONE_NUMBER>215	189	36272
code/registerFilesystem/file<PHONE_NUMBER>231	16	36288
code/registerFilesystem/vscode-userdata<PHONE_NUMBER>231	0	36288
code/willInitWorkspaceService<PHONE_NUMBER>232	1	36289
code/willInitStorage<PHONE_NUMBER>232	0	36289
code/willInitUserConfiguration<PHONE_NUMBER>235	3	36292
code/didInitUserConfiguration<PHONE_NUMBER>247	12	36304
code/willInitWorkspaceConfiguration<PHONE_NUMBER>248	1	36305
code/didInitWorkspaceConfiguration<PHONE_NUMBER>249	1	36306
code/didInitWorkspaceService<PHONE_NUMBER>249	0	36306
code/didInitStorage<PHONE_NUMBER>251	2	36308
code/willStartWorkbench<PHONE_NUMBER>255	4	36312
code/LifecyclePhase/Ready<PHONE_NUMBER>257	2	36314
code/willCreateWorkbenchContributions/1<PHONE_NUMBER>300	43	36357
code/didCreateWorkbenchContributions/1<PHONE_NUMBER>308	8	36365
code/willCreateWorkbenchContributions/2<PHONE_NUMBER>308	0	36365
code/registerFilesystem/trustedDomains<PHONE_NUMBER>310	2	36367
code/registerFilesystem/vscode-local-history<PHONE_NUMBER>314	4	36371
code/didCreateWorkbenchContributions/2<PHONE_NUMBER>315	1	36372
code/willCreatePart/workbench.parts.titlebar<PHONE_NUMBER>317	2	36374
code/didCreatePart/workbench.parts.titlebar<PHONE_NUMBER>334	17	36391
code/willCreatePart/workbench.parts.banner<PHONE_NUMBER>334	0	36391
code/didCreatePart/workbench.parts.banner<PHONE_NUMBER>334	0	36391
code/willCreatePart/workbench.parts.activitybar<PHONE_NUMBER>334	0	36391
code/didCreatePart/workbench.parts.activitybar<PHONE_NUMBER>336	2	36393
code/willCreatePart/workbench.parts.sidebar<PHONE_NUMBER>336	0	36393
code/didCreatePart/workbench.parts.sidebar<PHONE_NUMBER>337	1	36394
code/willCreatePart/workbench.parts.editor<PHONE_NUMBER>337	0	36394
code/didCreatePart/workbench.parts.editor<PHONE_NUMBER>367	30	36424
code/willCreatePart/workbench.parts.panel<PHONE_NUMBER>367	0	36424
code/didCreatePart/workbench.parts.panel<PHONE_NUMBER>368	1	36425
code/willCreatePart/workbench.parts.auxiliarybar<PHONE_NUMBER>368	0	36425
code/didCreatePart/workbench.parts.auxiliarybar<PHONE_NUMBER>368	0	36425
code/willCreatePart/workbench.parts.statusbar<PHONE_NUMBER>368	0	36425
code/didCreatePart/workbench.parts.statusbar<PHONE_NUMBER>370	2	36427
code/didRemovePartsSplash<PHONE_NUMBER>383	13	36440
code/willRestoreEditors<PHONE_NUMBER>383	0	36440
code/restoreEditors/editorGroupsReady<PHONE_NUMBER>387	4	36444
code/willRestoreViewlet<PHONE_NUMBER>387	0	36444
code/terminal/willGetTerminalBackend<PHONE_NUMBER>403	16	36460
code/restoreEditors/editorsToOpenResolved<PHONE_NUMBER>403	0	36460
code/didRestoreViewlet<PHONE_NUMBER>403	0	36460
code/willRegisterExplorerViews<PHONE_NUMBER>404	1	36461
code/didRegisterExplorerViews<PHONE_NUMBER>447	43	36504
code/terminal/didGetTerminalBackend<PHONE_NUMBER>447	0	36504
code/terminal/willReconnect<PHONE_NUMBER>447	0	36504
code/terminal/willGetTerminalLayoutInfo<PHONE_NUMBER>447	0	36504
code/restoreEditors/editorGroupsRestored<PHONE_NUMBER>474	27	36531
code/didRestoreEditors<PHONE_NUMBER>474	0	36531
code/didStartWorkbench<PHONE_NUMBER>474	0	36531
code/LifecyclePhase/Restored<PHONE_NUMBER>474	0	36531
code/willCreateWorkbenchContributions/3<PHONE_NUMBER>474	0	36531
code/willConnectSharedProcess<PHONE_NUMBER>475	1	36532
code/terminal/didGetTerminalLayoutInfo<PHONE_NUMBER>556	81	36613
code/terminal/didReconnect<PHONE_NUMBER>556	0	36613
code/terminal/willReplay<PHONE_NUMBER>556	0	36613
code/terminal/didReplay<PHONE_NUMBER>556	0	36613
code/terminal/willGetPerformanceMarks<PHONE_NUMBER>556	0	36613
code/willLoadExtensions<PHONE_NUMBER>577	21	36634
code/terminal/didGetPerformanceMarks<PHONE_NUMBER>604	27	36661
code/willHandleExtensionPoints<PHONE_NUMBER>697	93	36754
code/willHandleExtensionPoint/configurationDefaults<PHONE_NUMBER>697	0	36754
code/didHandleExtensionPoint/configurationDefaults<PHONE_NUMBER>698	1	36755
code/willHandleExtensionPoint/configuration<PHONE_NUMBER>698	0	36755
code/didHandleExtensionPoint/configuration<PHONE_NUMBER>718	20	36775
code/willHandleExtensionPoint/jsonValidation<PHONE_NUMBER>718	0	36775
code/didHandleExtensionPoint/jsonValidation<PHONE_NUMBER>719	1	36776
code/willHandleExtensionPoint/debuggers<PHONE_NUMBER>719	0	36776
code/didHandleExtensionPoint/debuggers<PHONE_NUMBER>725	6	36782
code/willHandleExtensionPoint/breakpoints<PHONE_NUMBER>725	0	36782
code/didHandleExtensionPoint/breakpoints<PHONE_NUMBER>725	0	36782
code/willHandleExtensionPoint/notebooks<PHONE_NUMBER>725	0	36782
code/didHandleExtensionPoint/notebooks<PHONE_NUMBER>725	0	36782
code/willHandleExtensionPoint/notebookRenderer<PHONE_NUMBER>725	0	36782
code/didHandleExtensionPoint/notebookRenderer<PHONE_NUMBER>726	1	36783
code/willHandleExtensionPoint/problemPatterns<PHONE_NUMBER>726	0	36783
code/didHandleExtensionPoint/problemPatterns<PHONE_NUMBER>727	1	36784
code/willHandleExtensionPoint/problemMatchers<PHONE_NUMBER>727	0	36784
code/didHandleExtensionPoint/problemMatchers<PHONE_NUMBER>728	1	36785
code/willHandleExtensionPoint/taskDefinitions<PHONE_NUMBER>728	0	36785
code/didHandleExtensionPoint/taskDefinitions<PHONE_NUMBER>730	2	36787
code/willHandleExtensionPoint/terminal<PHONE_NUMBER>730	0	36787
code/didHandleExtensionPoint/terminal<PHONE_NUMBER>730	0	36787
code/willHandleExtensionPoint/terminalQuickFixes<PHONE_NUMBER>730	0	36787
code/didHandleExtensionPoint/terminalQuickFixes<PHONE_NUMBER>730	0	36787
code/willHandleExtensionPoint/walkthroughs<PHONE_NUMBER>730	0	36787
code/didHandleExtensionPoint/walkthroughs<PHONE_NUMBER>730	0	36787
code/willHandleExtensionPoint/commands<PHONE_NUMBER>730	0	36787
code/didHandleExtensionPoint/commands<PHONE_NUMBER>734	4	36791
code/willHandleExtensionPoint/submenus<PHONE_NUMBER>734	0	36791
code/didHandleExtensionPoint/submenus<PHONE_NUMBER>734	0	36791
code/willHandleExtensionPoint/menus<PHONE_NUMBER>734	0	36791
code/didHandleExtensionPoint/menus<PHONE_NUMBER>749	15	36806
code/willHandleExtensionPoint/authentication<PHONE_NUMBER>749	0	36806
code/didHandleExtensionPoint/authentication<PHONE_NUMBER>749	0	36806
code/willHandleExtensionPoint/languages<PHONE_NUMBER>749	0	36806
code/didHandleExtensionPoint/languages<PHONE_NUMBER>768	19	36825
code/willHandleExtensionPoint/customEditors<PHONE_NUMBER>768	0	36825
code/didHandleExtensionPoint/customEditors<PHONE_NUMBER>768	0	36825
code/willHandleExtensionPoint/codeActions<PHONE_NUMBER>768	0	36825
code/didHandleExtensionPoint/codeActions<PHONE_NUMBER>768	0	36825
code/willHandleExtensionPoint/viewsWelcome<PHONE_NUMBER>768	0	36825
code/didHandleExtensionPoint/viewsWelcome<PHONE_NUMBER>768	0	36825
code/willHandleExtensionPoint/resourceLabelFormatters<PHONE_NUMBER>768	0	36825
code/didHandleExtensionPoint/resourceLabelFormatters<PHONE_NUMBER>768	0	36825
code/willHandleExtensionPoint/grammars<PHONE_NUMBER>768	0	36825
code/didHandleExtensionPoint/grammars<PHONE_NUMBER>773	5	36830
code/willHandleExtensionPoint/colors<PHONE_NUMBER>773	0	36830
code/didHandleExtensionPoint/colors<PHONE_NUMBER>774	1	36831
code/willHandleExtensionPoint/semanticTokenTypes<PHONE_NUMBER>774	0	36831
code/didHandleExtensionPoint/semanticTokenTypes<PHONE_NUMBER>774	0	36831
code/willHandleExtensionPoint/semanticTokenModifiers<PHONE_NUMBER>774	0	36831
code/didHandleExtensionPoint/semanticTokenModifiers<PHONE_NUMBER>774	0	36831
code/willHandleExtensionPoint/semanticTokenScopes<PHONE_NUMBER>774	0	36831
code/didHandleExtensionPoint/semanticTokenScopes<PHONE_NUMBER>774	0	36831
code/willHandleExtensionPoint/themes<PHONE_NUMBER>774	0	36831
code/didHandleExtensionPoint/themes<PHONE_NUMBER>775	1	36832
code/willHandleExtensionPoint/iconThemes<PHONE_NUMBER>775	0	36832
code/didHandleExtensionPoint/iconThemes<PHONE_NUMBER>775	0	36832
code/willHandleExtensionPoint/snippets<PHONE_NUMBER>775	0	36832
code/didHandleExtensionPoint/snippets<PHONE_NUMBER>775	0	36832
code/willHandleExtensionPoint/keybindings<PHONE_NUMBER>775	0	36832
code/didHandleExtensionPoint/keybindings<PHONE_NUMBER>784	9	36841
code/willHandleExtensionPoint/viewsContainers<PHONE_NUMBER>784	0	36841
code/didHandleExtensionPoint/viewsContainers<PHONE_NUMBER>802	18	36859
code/willHandleExtensionPoint/views<PHONE_NUMBER>802	0	36859
code/didHandleExtensionPoint/views<PHONE_NUMBER>810	8	36867
code/willHandleExtensionPoint/remoteHelp<PHONE_NUMBER>810	0	36867
code/didHandleExtensionPoint/remoteHelp<PHONE_NUMBER>810	0	36867
code/willHandleExtensionPoint/continueEditSession<PHONE_NUMBER>810	0	36867
code/didHandleExtensionPoint/continueEditSession<PHONE_NUMBER>810	0	36867
code/didHandleExtensionPoints<PHONE_NUMBER>810	0	36867
code/didLoadExtensions<PHONE_NUMBER>818	8	36875

Raw Perf Marks: localExtHost
Name	Timestamp	Delta	Total
code/timeOrigin<PHONE_NUMBER>633.436	0	0
code/fork/start<PHONE_NUMBER>752<PHONE_NUMBER>4375<PHONE_NUMBER>4375
code/fork/willLoadCode<PHONE_NUMBER>774	22<PHONE_NUMBER>4375
code/extHost/willConnectToRenderer<PHONE_NUMBER>902	128<PHONE_NUMBER>4375
code/extHost/didConnectToRenderer<PHONE_NUMBER>903	1<PHONE_NUMBER>4375
code/extHost/didWaitForInitData<PHONE_NUMBER>961	58<PHONE_NUMBER>4375
code/extHost/didCreateServices<PHONE_NUMBER>962	1<PHONE_NUMBER>4375
code/extHost/willWaitForConfig<PHONE_NUMBER>990	28<PHONE_NUMBER>4375
code/extHost/didWaitForConfig<PHONE_NUMBER>012	22<PHONE_NUMBER>4375
code/extHost/didInitAPI<PHONE_NUMBER>025	13<PHONE_NUMBER>4375
code/extHost/didInitProxyResolver<PHONE_NUMBER>026	1<PHONE_NUMBER>4375
code/extHost/ready<PHONE_NUMBER>026	0<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.emmet<PHONE_NUMBER>051	25<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.emmet<PHONE_NUMBER>061	10<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.extension-editing<PHONE_NUMBER>062	1<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.extension-editing<PHONE_NUMBER>068	6<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.markdown-language-features<PHONE_NUMBER>069	1<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.markdown-language-features<PHONE_NUMBER>121	52<PHONE_NUMBER>4375
code/extHost/willActivateExtension/vscode.emmet<PHONE_NUMBER>121	0<PHONE_NUMBER>4375
code/extHost/didActivateExtension/vscode.emmet<PHONE_NUMBER>132	11<PHONE_NUMBER>4375
code/extHost/willActivateExtension/vscode.extension-editing<PHONE_NUMBER>132	0<PHONE_NUMBER>4375
code/extHost/didActivateExtension/vscode.extension-editing<PHONE_NUMBER>133	1<PHONE_NUMBER>4375
code/extHost/willActivateExtension/vscode.markdown-language-features<PHONE_NUMBER>133	0<PHONE_NUMBER>4375
code/extHost/didActivateExtension/vscode.markdown-language-features<PHONE_NUMBER>470	337<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.git-base<PHONE_NUMBER>542	72<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.git-base<PHONE_NUMBER>545	3<PHONE_NUMBER>4375
code/extHost/willActivateExtension/vscode.git-base<PHONE_NUMBER>548	3<PHONE_NUMBER>4375
code/extHost/didActivateExtension/vscode.git-base<PHONE_NUMBER>548	0<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.git<PHONE_NUMBER>581	33<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.git<PHONE_NUMBER>613	32<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.github<PHONE_NUMBER>614	1<PHONE_NUMBER>4375
code/extHost/didLoadExtensionCode/vscode.github<PHONE_NUMBER>621	7<PHONE_NUMBER>4375
code/extHost/willLoadExtensionCode/vscode.markdown-math<PHONE_NUMBER>842	221	1208.56396484375
code/extHost/didLoadExtensionCode/vscode.markdown-math<PHONE_NUMBER>850	8	1216.56396484375
code/extHost/willActivateExtension/vscode.git<PHONE_NUMBER>852	2	1218.56396484375
code/extHost/willActivateExtension/vscode.github<PHONE_NUMBER>877	25	1243.56396484375
code/extHost/didActivateExtension/vscode.github<PHONE_NUMBER>885	8	1251.56396484375
code/extHost/willActivateExtension/vscode.markdown-math<PHONE_NUMBER>886	1	1252.56396484375
code/extHost/didActivateExtension/vscode.markdown-math<PHONE_NUMBER>886	0	1252.56396484375
code/extHost/didActivateExtension/vscode.git<PHONE_NUMBER>927	41	1293.56396484375

Loader Stats
Load AMD-module

Module
Duration

vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js
208.70000000018626

vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.nls.js
26.100000000093132

vscode-file://vscode-app/usr/share/code/resources/app/out/../node_modules.asar/vscode-textmate/release/main.js
127.40000000037253

vscode-file://vscode-app/usr/share/code/resources/app/out/../node_modules.asar/vscode-oniguruma/release/main.js
180.60000000009313

Load commonjs-module

Module
Duration

Invoke AMD-module factory
[added as an attachment, because otherwise my comment is too long]
Invoke commonjs-module

Module
Duration

Node Cached Data Stats
cached data used
cached data missed
prof-OZlf1Dl9.renderer.cpuprofile.txt
cached data rejected
cached data created (lazy, might need refreshes)

invoke-amd-module factory.txt
prof-OZlf1Dl9.main.cpuprofile.txt
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:51:20.981Z)
OS version: Linux x64 6.2.0-32-generic
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1260P (16 x 2812)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 2, 2

Memory (System)
46.74GB (40.61GB free)

Process Argv
--unity-launch --crash-reporter-id 7346e23b-af02-4155-a12b-7ce240bbf770

Screen Reader
no

VM
0%

DESKTOP_SESSION
regolith

XDG_CURRENT_DESKTOP
Regolith:GNOME-Flashback:GNOME

XDG_SESSION_DESKTOP
regolith

XDG_SESSION_TYPE
x11

Extensions (11)

Extension
Author (truncated)
Version

vscode-pull-request-github
Git
0.72.0

latex-workshop
Jam
9.13.4

vscode-docker
ms-
1.26.0

isort
ms-
2023.10.1

python
ms-
2023.16.0

vscode-pylance
ms-
2023.9.10

remote-containers
ms-
0.309.0

autodocstring
njp
0.6.1

bib
phr
0.3.0

code-spell-checker
str
3.0.1

graphviz-interactive-preview
tin
0.3.5

prof-OZlf1Dl9.main.cpuprofile.txt
prof-OZlf1Dl9.renderer.cpuprofile.txt
invoke-amd-module factory.txt

Thanks for the logs, can you also provide the following trace

Closing all running instances of VSCode
Start a new instance with the following arguments code --trace --trace-category-filter="base,benchmark,browser,ipc,latency,mojom,content,startup,toplevel,v8,navigation,disabled-by-default-base,disabled-by-default-lifecycles,disabled-by-default-mojom,disabled-by-default-network"
Once the editor is fully loaded, open command palette  and run Developer: Stop Tracing, this will generate a trace and provide you the path at which the trace was saved. Attach it to this issue thread.

Thanks for your response - I attached the tracefile (compressed, because its 37MB vs githubs 25MB limit)
code-rZteGydY.trace.zip

ScheduledActionBeginLayerTreeFrameSinkCreation seems to block the renderer main thread for 25s once the navigation has started in the browser process, this very likely indicates a delay in establishing gpu channel.
@hjl-csis can you test the following commands separately, make sure close any running instances and report back which one resolves the issue.

code --enable-features="EstablishGpuChannelAsync"
code --disable-gpu-compositing
code --in-process-gpu

Unfortunately none of them seem to have any effect on the startup time.
They all come with a Warning: 'disable-gpu-compositing' is not in the list of known options, but still passed to Electron/Chromium., but I guess that is expected.

Thanks for checking, can you collect the traces using the same steps as https://github.com/microsoft/vscode/issues/193188#issuecomment-1724063833 but use the following launch arguments instead code --disable-gpu --disable-gpu-compositing --trace --trace-category-filter="benchmark,browser,cc,cc.debug,compositor,mojom,content,startup,toplevel,gpu,v8,navigation,disabled-by-default-cc,disabled-by-default-cc.debug,disabled-by-default-cc.debug.scheduler"

Sure - this time it took a bit longer for the vscode window to show up (before, it showed up basically instantly, but was empty), but then it stayed empty for around the same amount of time as before. It might have been an artifact of the tracing?
code-jkKOcmH9.trace.zip

There is still time spent on establishing GPU channel, can you try launching with code --disable-gpu --disable-software-rasterizer --disable-gpu-compositing

Uh, with those options it starts instantly! Thank you!
Do you have any idea whether this is more likely to be a individual problem with my setup, or something that needs fixing in vscode or Electron?

Thanks for confirming, I can't say for sure why this happens in your case, but I can say for sure this is not a bug from the application side. It might be a bug in the Chromium runtime for your particular hardware setup.
All I could see from the runtime trace was that the renderer main thread was blocked attempting to establish a communication channel to the gpu process. The flags I proposed will avoid using the gpu process for compositing and rasterization, which negates the need to establish a communication channel on renderer startup. The side effect would be that rendering might be slow.
We can perform event tracing to understand the problem a bit better, it will take sometime before I can get back to you with the commands for that.

Hi, I ran with the code --disable-gpu --disable-software-rasterizer --disable-gpu-compositing flags for quite some time and forgot about them. Today I remembered this issue and tried running without them, and it starts up just fine.
I assume a graphics driver update in the meantime helped, but can't say for sure which one.
Thank you for your help!

I started to experience the same issue as well on VS Code 1.86.2 on a Ubuntu Budgie 22.04.
GPU is an Nvidia 3050 Ti and I'm currently running it in Intel only mode via Optimus.
code --disable-gpu --disable-software-rasterizer --disable-gpu-compositing fixes the problem for me as well.
I assume the ticket was closed because of the workaround, but is there any more that can be done to help this being fixed in a different way? @deepak1556

In fact:
code --disable-gpu --disable-software-rasterizer already fixes the probkem, --disable-gpu-compositing doesn't seem to make a difference.

In fact:
code --disable-gpu --disable-software-rasterizer already fixes the problem, --disable-gpu-compositing doesn't seem to make a difference.

it works, but I also get a warning:
Warning: 'disable-software-rasterizer' is not in the list of known options, but still passed to Electron/Chromium.

In my case this workaround also helped.
Don't you think this issue should be fixed on the side of the vscode?

@pktiuk - it totally should.

@pktiuk - it totally should.

I asked about reopening https://github.com/microsoft/vscode/issues/204243


Use Reqwest backend for Appveyor, not Hyper which is deprecated

Since https://github.com/rust-lang-nursery/rustup.rs/pull/1222 Appveyor builds have been complaining, so should stop asking for the Hyper backend

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+

:pushpin: Commit 335841c484c1a6f592e7745789ec43f400b75973 has been approved by gnzlbg

:hourglass: Testing commit 335841c484c1a6f592e7745789ec43f400b75973 with merge 4d9a03e391a1f6626949e870e5c49e14d8944abb...

:sunny: Test successful - status-appveyor, status-travis
Approved by: gnzlbg
Pushing 4d9a03e391a1f6626949e870e5c49e14d8944abb to master...


Support for GithubEnterprise

The 3rd party module repo-path-parse only understands github.com URLs.
While trying to release to a github enterprise installation (github.com on-premises) that has another domain than github.com, repo-path-parse cannot understand it
By switching to parse-repo this is solved
Examples:
parse-repo: https://tonicdev.com/5788ea6e2a91251300f25bb0/5788ea6e2a91251300f25bb1
repo-path-parse: https://tonicdev.com/5788ea6e2a91251300f25bb0/5788eca636f3d6120002b014

Thanks @jmendiara! I've just released this as v2.4.2.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
SDR-Radio (latest 3.3 stable) installed using Winget does not get detected as a Winget package.
Maybe the package namespace is incorrect? The wingetcreate tool suggests SDR-Radio.comLtd.SDR-Radio.comV3(64-bit)created2024-02-05_0741 as a PackageIdentifier. So maybe something like SDR-Radio.comLtd.SDR-Radio.comV3 could work better? Also, the PackageName itself should probably be changed to SDR-Radio.com (V3).
Steps to reproduce

Run: winget install SimonG4ELI.SDR-Radio
Reboot the computer.
Run: winget list|Select-String sdr-radio
Run: winget uninstall SimonG4ELI.SDR-Radio

Actual behavior
> winget list|Select-String sdr-radio

SDR-Radio.com (V3)                            SDR-Radio.com (V3)                             Unknown

> winget uninstall SimonG4ELI.SDR-Radio
No installed package found matching input criteria.

Expected behavior
> winget list|Select-String sdr-radio

SDR-Radio.com (V3)                            SimonG4ELI.SDR-Radio                             3.3

Environment
winget --info
Windows Package Manager v1.6.3482
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.3930
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.3482.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Enabled

Screenshots and Logs
No response

SDR-Radio is now correctly detected as installed by Winget, however its version is still shown as Unknown and update is offered every time:
Name                                                       Id                                                  Version            Available      Source
SDR-Radio.com (V3)                                         SimonG4ELI.SDR-Radio                                Unknown            3.3            winget

This is probably because the installer does not seem to report installed version:

@Trenly Is there any way to workaround this? Thanks!

SDR-Radio is now correctly detected as installed by Winget, however its version is still shown as Unknown and update is offered every time:
Name                                                       Id                                                  Version            Available      Source
SDR-Radio.com (V3)                                         SimonG4ELI.SDR-Radio                                Unknown            3.3            winget

This is probably because the installer does not seem to report installed version:

@Trenly Is there any way to workaround this? Thanks!
By the way, SDR-Radio is not the only app that has this problem. For example, DG0JBJ.HDSDR is another.

Apps with version Unknown always show for upgrade because their version cannot be determined. However, they are skipped when using winget upgrade --all

That's what I thought. Thanks! I've created a ticket on the SDR-Radio.com support forum for the missing version info, so hopefully it will be added in a future release. :-)
Closing this issue since the other problem has been resolved.


why the content not include image link？

most of recipes contents include image link, but when I capture recipe use org-chef, I found images link always dropped , why can't include link in recipes?

Hi! I haven't included images in the past, mostly because you would have to store the images somewhere, which would involve setting up another directory or something. Plus having a plain text version can be nice too.
I'm completely open to a pull request for this if somebody wants to implement it, I think that would be great! I would suggest making this configurable, though.

Just a note on file storage, you can just give a url, e.g.
[[https://recipies.com/some/thing/preview-image.jpg][preview]]


1st layer transactions shouldn't be marked as anonymous

We all know how things work here and that you can make 1st layer transactions by being technically anonymous etc.
However to avoid misleading newcomers i think the comparison table shouldn't make it look as if they were anonymous by default, so i propose to replace the green check with something like a yellow dot and a note that says pseudo anonymous on the Bitcoin Network, while leaving the check on Bitcoin Lightning Network.
Also, i propose to move the Lightning Network column before the Bitcoin Network one so that it gives the visual cue that Lightning is a more convenient way to use Bitcoin, like an upgrade over bitcoin, that is not necessarily true, but makes things less confusing for someone that is approaching this for the first time.

This is how it would look like

(i don't know how to make the dot inside the yellow circle with this app, so i've just left it like that for now )


Paths in package.json don't exist

The project's package.json refers to lib/index.js and lib/index.d.ts, but these files don't exist in the package as published to NPM. It seems this is not a problem for Webpack and TypeScript, which will fall back to the default index.js and index.d.ts in the root of the project, where they do exist. However, other tools such as Snowpack, which appear to be more strict with this do struggle because of this.

Hello @arendjr, thanks for the contribution. I'm having a look

Ah yes ! you are right we publish the content of lib folder 😄 sorry for that I accept the PR, and I will release a 1.6.1 today.

1.6.1 released successfully, it should be available soon https://www.npmjs.com/package/monaco-promql

Thanks! 👍


added pt-br language and flag

Is that all it requires to add a new language? Thanks :)

Yes, that is all. :-)

Thanks!!!


Use getenv() to get CRAFT_ENVIRONMENT

I'm getting this error on PHP 8, Craft 4, and 2.0.0-beta.1 of this plugin:
Exception 'Error' with message 'Undefined constant "born05\sentry\CRAFT_ENVIRONMENT"'

in /Users/reinhard/Work - Client/Sendbird/craft-cms/vendor/born05/craft-sentry/src/Plugin.php:64

Stack trace:
#0 /craft-cms/vendor/yiisoft/yii2/base/BaseObject.php(109): born05\sentry\Plugin->init()
#1 /craft-cms/vendor/yiisoft/yii2/base/Module.php(161): yii\base\BaseObject->__construct(Array)
#2 /craft-cms/vendor/craftcms/cms/src/base/Plugin.php(122): yii\base\Module->__construct('sentry-sdk', Object(craft\console\Application), Array)
...

@weotch Not the plugin maintainer but that's strange as I believe the CRAFT_ENVIRONMENT constant is still valid and works in Craft CMS 4.
https://craftcms.com/docs/4.x/config/#craft-environment
However, I do know by the default Craft CMS 4 now looks for environment variables with the CRAFT_ prefix against config settings now, what might be the issue is in the web/index.php, there was always this line present which defined CRAFT_ENVIRONMENT to a value.
https://github.com/craftcms/craft/blob/309136a5abb3ba48018caf10ea03b61fa4a4b744/bootstrap.php#L20
In Craft CMS 4 this has been removed due to Craft 4 automatically using environment variable names with the CRAFT_ prefix. So I assume this is why it's undefined.

@weotch & @jamesmacwhite thanks for point this out. I've fixed it more accordingly, i think, to Craft's way of doing this in Craft 4. Please let me know if this doesn't work as expected.
See version: 2.0.0


All bank interest

Is your suggestion related to a problem? Please describe in detail.
A clear and concise description of what the problem is.
Ex. [...] doesn't work, [...] solves it.
Describe your suggestion
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Ex. [...] could be a problem, but [...]
Additional context
Add any other context or screenshots about the suggestion here.

how i can see all my bank interest

This isn't possible, bank history is limited to transactions from the past 7 days.


Add Maybe Maybe a -> Maybe a

maybe call it crush or flatten or something.

I think it makes sense to suggest this to http://package.elm-lang.org/packages/elm-community/maybe-extra/1.1.0/
The idea is that a bunch of stuff like this lives in *-extra modules and we'll do a pass to bring the good stuff into core.

is already in extra, called join


Pico Neo 3 stuttering

[+] I have read the FAQ.
[+] I have searched in existing issues.

Environment

OS: Windows
scrcpy version: 1.6 to 1.20
installation method: Windows release
device model: Pico Neo 3
Android version: 10

I've been using the Pico Neo 2 since Januarry 2021 and I used scrcpy to display the picture from Pico on PC (Windows). It worked all very fine.
In October I got two new Pico Neo 3 devices and no matter what I do and try, the performance is very poor. I get about 1 fps - so it's more a diashow than anything.
I've tried everything i could find on the internet and forums, like reducing the bit-rate, max-size, I tried older versions of scrcpy (every version from 1.6 to 1.20) there is always the same result on both Pico Neo 3 devices. (bitrates: 1M to 25M, there is no difference in the performance)
And no matter what I try, performance on Pico Neo 2 is always perfect and on the Pico Neo 3 always very stuttering.
I also just contacted the support from Pico Neo, but maybe you can help me with any new idea...
By the way: It has to run by USB-cable (and i also tried different cables - every cable worked with Pico Neo 2 - and none made a difference with the Pico Neo 3).
Here are my settings (although i tried many other versions):
scrcpy.exe --crop=1280:1776:400:60 --max-size=800 --bit-rate=1M --max-fps=30 --window-borderless --always-on-top --window-x=100 --window-y=100 --window-width=800 --window-height=600 --display-buffer=100
scrcpy.exe --bit-rate=8M --max-fps=60 --window-borderless --always-on-top --window-x=100 --window-y=100 --window-width=800 --window-height=600
scrcpy.exe --crop=1280:1776:400:60 --max-size=400 --bit-rate=1M --max-fps=30 --window-borderless --always-on-top --window-x=100 --window-y=100 --window-width=800 --window-height=600 --display-buffer=1000
I also added a short Video. The picture inside the Pico Neo 3 was always smooth and i was moving the head all the time. And that's how it's always looking on the Windows screen...
https://user-images.githubusercontent.com/78421427/142998795-0fb5cfea-5fd4-4c0b-a7f9-4a8ee749f469.mp4
Thanks in advance!
Mihael

This is a problem on the device, the encoder is not able to produce frames at the expected rate.
Did you try another encoder?

Ok thank you. I thought so too.
Yes I tried all possible encoders. One of them gave me a blackscreen. The others were all stuttering as well.

What if you record with screenrecord?
adb shell screenrecord /sdcard/file.mp4
adb pull /sdcard/file.mp4

That seemed to work a little better - at least in the main menu:
https://user-images.githubusercontent.com/78421427/143006701-adb4e6fb-6902-48d3-bb7e-2059ec0c6c7c.mp4

Tried another one where I switched back to 72 fps (inside the Pico settings) and its stuttering again:
https://user-images.githubusercontent.com/78421427/143007437-fe82a082-d20c-4bb9-b222-950d689436de.mp4

You could play with the encoder settings.
You could adapt any of the MediaFormat settings via the command line:
# example usage
scrcpy --codec-options=max-fps-to-encoder:float=5,bitrate:int=500000

This overwrites the existing ones (for example passed via --max-fps and --bit-rate), but also allows any other options.
The variables name and type are documented in the MediaFormat page.
For information, here are the options scrcpy configure by default:
https://github.com/Genymobile/scrcpy/blob/57fb08e443272a9d346b036fb421cdf0ccff3074/server/src/main/java/com/genymobile/scrcpy/ScreenEncoder.java#L199-L213

So I built scrcpy with different settings in ScreenEncoder.java and also added other setting i found in a different issue:
format.setInteger(MediaFormat.KEY_PROFILE, MediaCodecInfo.CodecProfileLevel.AVCProfileBaseline);
format.setInteger(MediaFormat.KEY_LEVEL, MediaCodecInfo.CodecProfileLevel.AVCLevel1);
But unfortunately nothing helped. The stuttering didn't stop.
Here are the logs from Pico Neo 2 (where it works fine) and the Pico Neo 3 (stuttering) with same settings. Maybe you see something I didn't see:
pico2.txt
pico3.txt
To me lines 31 to 33 look fishy (pico3.txt), compared to pico2.txt:
12-02 12:17:02.506  1177  2285 E OMXNodeInstance: setParameter(0xf583c304:qcom.encoder.avc, OMX.google.android.index.allocateNativeHandle(0x7f00005d): Input:0 en=0) ERROR: UnsupportedSetting(0x80001019)
12-02 12:17:02.506  1177  2285 I OMX-VENC: WARN: Enable/Disable allocate-native-handle allowed only in secure session
12-02 12:17:02.506  1177  2285 E OMXNodeInstance: setParameter(0xf583c304:qcom.encoder.avc, OMX.google.android.index.allocateNativeHandle(0x7f00005d): Output:1 en=0) ERROR: UnsupportedSetting(0x80001019)
By the way: Pico Support answered that they don't have any stuttering in their Pico Neo 3+scrcpy. They also sent me a video as proof. I tried it on 4 different PCs, 2x Pico Neo 3, one Pico Neo 2 and different cables. Always the same result.
Let me know if you have any other idea.
Thx!

OMX-VENC: Enable/Disable allocate-native-handle allowed only in secure session

Just to see if the error message is different, could you try with this change:
diff --git a/server/src/main/java/com/genymobile/scrcpy/ScreenEncoder.java b/server/src/main/java/com/genymobile/scrcpy/ScreenEncoder.java
index f98c53d0..ac1f9d87 100644
--- a/server/src/main/java/com/genymobile/scrcpy/ScreenEncoder.java
+++ b/server/src/main/java/com/genymobile/scrcpy/ScreenEncoder.java
@@ -226,6 +226,7 @@ public class ScreenEncoder implements Device.RotationListener {
         // On Android 12 preview, SDK_INT is still R (not S), but CODENAME is "S".
         boolean secure = Build.VERSION.SDK_INT < Build.VERSION_CODES.R || (Build.VERSION.SDK_INT == Build.VERSION_CODES.R && !"S"
                 .equals(Build.VERSION.CODENAME));
+        secure = false;
         return SurfaceControl.createDisplay("scrcpy", secure);
     }

(or you could try the old scrcpy v1.5, before 1fdde490fd2a0b89680a2b5da5e5274192398023 was merged)
You are not alone with this problem on Pico Neo 3: #2835

Ok here are the logs
pico2_secure.txt
pico3_secure.txt
I'm not sure what exactly changed compared to the first logs. By the way: I'm building with scrcpy v1.21
I just tried v1.5 and 1.5.1. They are behaving the same as the other versions (Pico Neo 3 is stuttering, Pico Neo 2 is working).

Sorry, I picked the wrong versions to test (1.15 and 1.15.1). Now i tried 1.5 and it's the same behaviour.

Here a little update on my current progress:
After wasting quite a lot of time trying to fix the problem i ordered a third PicoNeo3 because i speculated that the problem is on the hardware.
Immediately after i got the headset i tried it with scrcpy and it worked perfectly fine. At that point the Software/Firmware version was v4.2.78. Then I updated the headset to current version v4.3.34 and it's stuttering again.
So the problem seems to be the new Software/Firmware.
Unfortunately there is no way I could go back to v4.2.78. Factory reset only deletes all user-files but does not change SW/FW.
I'm in contact with PicoNeo-Devs and I'll give an update here if there is anything new.

I had similar issues and asked on the developer forum for a PUI archive.
"Dear developer,
The Neo 3 series do not support downgrade.
For screen casting solutions, the Neo 3 series no longer supports scrcpy screen casting, and you can try use Miracast for screen casting.
Please refer to the following links for details:
https://developer.pico-interactive.com/docs/en/12058/225664/
In addition, our own screen casting solution is expected to be released in Q2."
https://devanswers.pico-interactive.com/index.php?qa=3722&qa_1=is-there-a-pui-archive


Montage enh

addresses and closes pr #1704

besides LGTM if @christianbrodbeck is happy

Sorry for not responding earlier, just got back from a trip, besides the comment it looks good to me.

i think i've addressed everything now.

cool. all comments have been addressed.

Hmm, one more thought: for all builtin montages we supposedly know the unit, we should use that information. Do they all happen to be in m?

some of them don't look to be in either. maybe in cm.

are we all good here?

if @christianbrodbeck is happy I am happy

We could just guess based on the fact that a head is in the magnitude of 10 cm across... But then I also don't know how important it is to have the standardized montages in m?

@christianbrodbeck yeah, i guessed that they were probably cm too. I think it's unimportant if you haven't transformed the points. it's only important if you are going to do some source space computations with the sensors. I think most default case will be for sensor space analyses.

@teonlamont @christianbrodbeck I'm happy, looks clean!

Yes, it's good for merge unless you wanted to add a note to the extent that builtin montages are not properly scaled, I don't know if that would cause any trouble anywhere but if it would not then I guess we don't need the note.

Feel free to add the note!

On 17 Mar 2015, at 17:07, Christian Brodbeck<EMAIL_ADDRESS>wrote:
Yes, it's good for merge unless you wanted to add a note to the extent that builtin montages are not properly scaled, I don't know if that would cause any trouble anywhere but if it would not then I guess we don't need the note.
—
Reply to this email directly or view it on GitHub.

rebased, note added, and whats_new updated

+1 for merge when travis is happy

+1 too

Looks like another whats_new conflict, I'll merge by rebase since I caused the problem

Merged by rebase, thanks @teonlamont


Fix GridMap freeing edge connection debug mesh too early

Fixes GridMap freeing edge connection debug mesh too early.
Fixes https://github.com/godotengine/godot/issues/98821

Thanks!


Support for "answer" posts

Currently there is no support for answer posts. While answer posts cannot be created, they can be edited.
I tried adding the functionality myself, but ran into issues with pytumblr recognizing answer posts. Any ideas?

Do you mean creating answers to questions asked? If so, the way to do that through the tumblr API is to, through editing it, setting the "answer" tag to whatever you want to answer (which requires the changing of the valid parameters in the code), and setting the state from "submission" to "published"

The method _post_valid_options doesn't have any valid options for answer posts (see https://github.com/tumblr/pytumblr/blob/master/pytumblr/init.py#L469). Last time I tried working on this (which admittedly was a while ago), I thought it was more complicated than simply adding an if-statement to this one method... if I have time this weekend, I'll see if I can dig up what I did to get answer support. IIRC, though, it was fairly kludgey, which is why I opened an issue instead of making a pull request.

Sorry about not responding earlier, but I got that to work simply by changing
valid = ['type', 'state', 'tags', 'tweet', 'date', 'format', 'slug']
to
valid = ['type', 'state', 'tags', 'tweet', 'date', 'format', 'slug', 'answer', 'state']
then used
asklist = client.submission('[my blog's name]')

'for ask in asklist['posts']:'
    if ask['type'] == 'answer':
        if ask['state'] == 'submission':
            client.edit_post('[my blog's name]', id=ask['id'], answer=[whatever I want my bot to answer to any given ask], state='published');'

to answer every ask that hasn't yet been answered.
sorry if that was weirdly ambiguous with the brackets.

However, if you mean submitting answer posts to other blogs using pytumblr, I have no idea whether that is possible or how to do that if it is.

@Macman1234 I may have a slight improvement on your solution for answering questions: instead of adding 'answer' to the list of valid options for all post types, what about adding
elif post_type == 'answer': valid += ['answer']
near the bottom of _post_valid_options() where all the other if statements are, and then answer asks using
client.edit_post('[blog name]', id=[ask ID], type='answer', answer=[answer], state='published') (note the inclusion of a 'type' arg)?

@sintelligentdesign That looks great to me. Have you done any testing with that solution?

I've been using it in one of my projects and it's been working reliably. That said, I haven't written any tests for it. It's a minor change but that's still probably important (I'm just garbage at writing tests).

@sintelligentdesign That's almost certainly a better way of implementing that then the way that I've been using: a lot more sane to prevent using "answer" in editing other types of posts. Thanks for that, I'll probably switch over to using it that way.

For answering the ask, is there a way to use an image with it?

You can include an HTML <img> element in your answer field, which appears to work on desktop (but not mobile?), unless the post is set to a draft before being published, in which case the image seems to disappear (??). I'll try to see if I can figure out something better (read: reliable) sometime this week.

Cool

Any luck for images? I know that when i answer one it auto uploads it. I was hoping not to host the images and let tumbrl handle them like i have been with answers.

By "when I answer one it auto uploads it," are you talking about using the website and answering questions with images manually, or using the API? I assume the first but i just wanted to be sure.
According to the API docs, answer posts don't support the data field used in image posts, and when I gave editing an answer post by adding a data field a shot, it didn't return an error but it didn't work either.
One possibility, although you mentioned wanting to avoid hosting images outside of Tumblr, could be to use an image hosting service's API (I initially was going to suggest Imgur but when I looked the Imgur Python API was deprecated, bummer) and adding the link to the image in the answer field of the answer post. That still has the issue though of apparently not working on mobile (Maybe? Can anybody else test this? Maybe I'm just doing something wrong and dumb. I haven't tried Markdown as the post format but I can't imagine it would make a difference).


Create a Material Baker.

Currently we can use MaterialX only when installing multiple dependencies:

Substance designer install to output materialx
Upcoming Autodesk materialx tool
Python and MaterialX sdk
Opening MaterialXView and then clicking B button and then picking a location.

The ability to have a single command to bake would be helpful to automation and ease of production use.
Fixes: https://github.com/materialx/MaterialX/issues/650
For review.

One additional note, @fire, make sure you've filled out a Contributor License Agreement (either for yourself or your company), so that we can merge your contributions once they're ready to go:
https://github.com/materialx/MaterialX/blob/main/CONTRIBUTING.md
Thank you!

@jstone-lucasfilm I'll get back to you over the weekend.

The design for something that lets someone pick between 4 types of images and also hdr is too complicated for now. So I took it out.

@fire Just a reminder that you'll need to sign a CLA before we can move forward with this pull request:
https://github.com/materialx/MaterialX/blob/main/CONTRIBUTING.md

Please check your mail.

@jstone-lucasfilm Gentle reminder.

Thanks for the reminder, @fire, and I'll check in with our legal team.  They need to approve your CLA before I can proceed.


⚠ Bofrost.lu has degraded performance

In 387fc73, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1119 ms

Resolved: Bofrost.lu performance has improved in db23e25 after 6 minutes.