Showing Blank Terminal

Type: Bug
I am using windows 10 os
VS Code version: Code 1.75.0 (e2816fe719a4026ffa1ee0189dc89bdfdbafb164, 2023-02-01T15:23:45.584Z)
OS version: Windows_NT x64 6.1.7600
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz (4 x 2304)

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_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
3.92GB (0.59GB free)

Process Argv
--crash-reporter-id 83e87beb-6f10-4f46-9431-d9f21b965974

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

es7-react-js-snippets
dsz
4.4.3

mayukaithemevsc
Gul
3.2.4

material-icon-theme
PKi
4.23.1

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
pyind779cf:30657577
f6dab269:30613381
pythonsymbol12:30657548
vscsb:30628654

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/label info-needed terminal

I guess I am experiencing the same issue.
I'm using a DevContainer from this repository: ansible-playground
The container starts as expected without errors.
As soon as I want to open a terminal, I get a blank Terminal tab and after a few seconds, a popup appears in the lower ricght corner with the following error:

After about 2 minutes, the terminal could be spawned. But only, if I do NOT Restart pty host
2023-02-06 17:00:39.033 [trace] ptyService#getLayoutInfo {"workspaceId":"57e3b2211a8b9e91388c7e989b089339"}
2023-02-06 17:00:39.033 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":0,"terminals":[]}]
2023-02-06 17:00:44.148 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":0,"terminals":[]}]
2023-02-06 17:01:23.830 [trace] ptyService#setLayoutInfo []
2023-02-06 17:01:27.444 [trace] persistentTerminalProcess#ctor 1 [object Arguments]
2023-02-06 17:01:27.445 [debug] MutationLogger "Persistent process "1" interaction state" set to "None", reason: initialized
2023-02-06 17:01:27.459 [trace] ptyService#start 1
2023-02-06 17:01:27.459 [trace] persistentTerminalProcess#start 1 false
2023-02-06 17:01:27.461 [trace] IPty#spawn /bin/bash ["--init-file","/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh"] {"name":"xterm-256color","cwd":"/workspaces/ansible-playground","env":{"HOSTNAME":"ansible-control","HOME":"/home/vscode","PATH":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/remote-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/vscode/.local/bin","SHELL":"/bin/bash","PWD":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164","REMOTE_CONTAINERS_IPC":"/tmp/vscode-remote-containers-ipc-b4965da84f939eef5a05e19650e15323c77aa616.sock","REMOTE_CONTAINERS_SOCKETS":"[\"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock\",\"/tmp/.X11-unix/X0\",\"/home/vscode/.gnupg/S.gpg-agent\"]","USER":"vscode","SHLVL":"1","PROMPT_DIRTRIM":"4","_":"/bin/cat","SSH_AUTH_SOCK":"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock","DISPLAY":":0","REMOTE_CONTAINERS_DISPLAY_SOCK":"/tmp/.X11-unix/X0","REMOTE_CONTAINERS":"true","BROWSER":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/helpers/browser.sh","TERM_PROGRAM":"vscode","TERM_PROGRAM_VERSION":"1.75.0","LANG":"en_US.UTF-8","COLORTERM":"truecolor","GIT_ASKPASS":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass.sh","VSCODE_GIT_ASKPASS_NODE":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/node","VSCODE_GIT_ASKPASS_EXTRA_ARGS":"","VSCODE_GIT_ASKPASS_MAIN":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass-main.js","VSCODE_GIT_IPC_HANDLE":"/tmp/vscode-git-3b2c3540f1.sock","VSCODE_IPC_HOOK_CLI":"/tmp/vscode-ipc-d40bf28d-d692-49c9-a9cc-45eec1fb2fe9.sock","VSCODE_INJECTION":"1"},"cols":119,"rows":13,"useConpty":false,"conptyInheritCursor":false}
2023-02-06 17:03:27.039 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.039 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.040 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.040 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.040 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.040 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:27.047 [trace] IPty#onData ]633;C
2023-02-06 17:03:27.048 [trace] IPty#onData ]633;E;__vsc_original_prompt_command=$PROMPT_COMMAND
2023-02-06 17:03:27.048 [trace] IPty#onData ]633;D;0
2023-02-06 17:03:27.049 [trace] IPty#onData ]633;P;Cwd=/workspaces/ansible-playground
2023-02-06 17:03:27.051 [trace] IPty#resize 119 13
2023-02-06 17:03:27.052 [trace] IPty#resize 119 13
2023-02-06 17:03:27.052 [trace] IPty#resize 119 25
2023-02-06 17:03:27.054 [debug] CommandDetectionCapability#handleCommandExecuted 0 0
2023-02-06 17:03:27.055 [debug] CommandDetectionCapability#setCommandLine __vsc_original_prompt_command=$PROMPT_COMMAND
2023-02-06 17:03:27.055 [debug] CommandDetectionCapability#handleCommandFinished 0 0 __vsc_original_prompt_command=$PROMPT_COMMAND {"commandExecutedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":1,"_onDispose":{"_listeners":[null],"_disposed":false}},"commandExecutedX":0,"command":"__vsc_original_prompt_command=$PROMPT_COMMAND","commandFinishedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":2,"_onDispose":{"_listeners":[null],"_disposed":false}}}
2023-02-06 17:03:27.057 [trace] IPty#onData ]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:03:27.064 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:03:27.066 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:03:27.546 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:43.340 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-06 17:03:43.747 [debug] MutationLogger "Persistent process "1" interaction state" set to "Session", reason: input
2023-02-06 17:03:43.747 [trace] IPty#write d
2023-02-06 17:03:43.755 [trace] IPty#onData d
2023-02-06 17:03:47.717 [trace] IPty#write
2023-02-06 17:03:47.718 [trace] IPty#onData
2023-02-06 17:04:00.938 [trace] IPty#resize 106 25
2023-02-06 17:04:00.939 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:04:00.945 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:04:00.946 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:04:00.995 [trace] persistentTerminalProcess#ctor 2 [object Arguments]
2023-02-06 17:04:00.996 [debug] MutationLogger "Persistent process "2" interaction state" set to "None", reason: initialized
2023-02-06 17:04:01.003 [trace] ptyService#start 2
2023-02-06 17:04:01.003 [trace] persistentTerminalProcess#start 2 false
2023-02-06 17:04:01.003 [trace] IPty#spawn /bin/bash ["--init-file","/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh"] {"name":"xterm-256color","cwd":"/workspaces/ansible-playground","env":{"HOSTNAME":"ansible-control","HOME":"/home/vscode","PATH":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/remote-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/vscode/.local/bin","SHELL":"/bin/bash","PWD":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164","REMOTE_CONTAINERS_IPC":"/tmp/vscode-remote-containers-ipc-b4965da84f939eef5a05e19650e15323c77aa616.sock","REMOTE_CONTAINERS_SOCKETS":"[\"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock\",\"/tmp/.X11-unix/X0\",\"/home/vscode/.gnupg/S.gpg-agent\"]","USER":"vscode","SHLVL":"1","PROMPT_DIRTRIM":"4","_":"/bin/cat","SSH_AUTH_SOCK":"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock","DISPLAY":":0","REMOTE_CONTAINERS_DISPLAY_SOCK":"/tmp/.X11-unix/X0","REMOTE_CONTAINERS":"true","BROWSER":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/helpers/browser.sh","TERM_PROGRAM":"vscode","TERM_PROGRAM_VERSION":"1.75.0","LANG":"en_US.UTF-8","COLORTERM":"truecolor","GIT_ASKPASS":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass.sh","VSCODE_GIT_ASKPASS_NODE":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/node","VSCODE_GIT_ASKPASS_EXTRA_ARGS":"","VSCODE_GIT_ASKPASS_MAIN":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass-main.js","VSCODE_GIT_IPC_HANDLE":"/tmp/vscode-git-3b2c3540f1.sock","VSCODE_IPC_HOOK_CLI":"/tmp/vscode-ipc-14b55115-acb9-47df-9abd-3d60b1b8f6af.sock","VSCODE_INJECTION":"1"},"cols":101,"rows":24,"useConpty":false,"conptyInheritCursor":false}
2023-02-06 17:05:58.503 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:05:58.505 [trace] IPty#resize 262 25
2023-02-06 17:05:58.505 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:05:58.505 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:05:58.507 [trace] IPty#onData ]633;C
2023-02-06 17:05:58.508 [trace] IPty#onData ]633;E;__vsc_original_prompt_command=$PROMPT_COMMAND]633;D;0
2023-02-06 17:05:58.508 [trace] IPty#onData ]633;P;Cwd=/workspaces/ansible-playground
2023-02-06 17:05:58.511 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:05:58.512 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:05:58.514 [debug] CommandDetectionCapability#handleCommandExecuted 0 0
2023-02-06 17:05:58.514 [debug] CommandDetectionCapability#setCommandLine __vsc_original_prompt_command=$PROMPT_COMMAND
2023-02-06 17:05:58.514 [debug] CommandDetectionCapability#handleCommandFinished 0 0 __vsc_original_prompt_command=$PROMPT_COMMAND {"commandExecutedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":7,"_onDispose":{"_listeners":[null],"_disposed":false}},"commandExecutedX":0,"command":"__vsc_original_prompt_command=$PROMPT_COMMAND","commandFinishedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":8,"_onDispose":{"_listeners":[null],"_disposed":false}}}
2023-02-06 17:05:58.515 [trace] IPty#onData ]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:05:58.521 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:05:58.521 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:05:58.537 [trace] IPty#resize 106 25
2023-02-06 17:05:58.538 [trace] IPty#resize 262 25
2023-02-06 17:05:58.538 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:05:58.545 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:05:58.545 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:05:58.545 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:05:58.546 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:05:59.034 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:06:07.773 [trace] IPty#resize 262 20
2023-02-06 17:06:07.774 [trace] IPty#resize 262 20
2023-02-06 17:06:07.774 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:07.774 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:07.781 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:07.781 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:07.782 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:07.782 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:08.204 [trace] IPty#resize 262 19
2023-02-06 17:06:08.205 [trace] IPty#resize 262 19
2023-02-06 17:06:08.205 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:08.205 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:08.211 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:08.212 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:08.212 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:08.212 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:08.668 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:06:09.192 [trace] IPty#resize 262 20
2023-02-06 17:06:09.193 [trace] IPty#resize 262 20
2023-02-06 17:06:09.193 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:09.193 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:09.200 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:09.200 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:09.201 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:09.201 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:09.301 [trace] IPty#resize 262 20
2023-02-06 17:06:09.302 [trace] IPty#resize 262 20
2023-02-06 17:06:09.691 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:06:09.758 [trace] IPty#resize 262 21
2023-02-06 17:06:09.759 [trace] IPty#resize 262 21
2023-02-06 17:06:09.759 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:09.759 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:09.765 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:09.766 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:09.766 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:09.766 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:09.816 [trace] IPty#resize 262 21
2023-02-06 17:06:09.816 [trace] IPty#resize 262 21
2023-02-06 17:06:10.261 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:06:12.208 [trace] IPty#resize 262 23
2023-02-06 17:06:12.208 [trace] IPty#resize 262 23
2023-02-06 17:06:12.209 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:12.209 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:12.216 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:12.216 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:12.218 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:12.219 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:12.455 [trace] IPty#resize 262 23
2023-02-06 17:06:12.455 [trace] IPty#resize 262 23
2023-02-06 17:06:12.705 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:06:13.306 [trace] IPty#resize 262 17
2023-02-06 17:06:13.306 [trace] IPty#resize 262 17
2023-02-06 17:06:13.306 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:13.306 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:06:13.313 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:13.313 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:13.313 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:06:13.313 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:06:13.791 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":true,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]}]
2023-02-06 17:08:35.150 [trace] IPty#resize 262 17
2023-02-06 17:08:35.226 [trace] persistentTerminalProcess#ctor 3 [object Arguments]
2023-02-06 17:08:35.229 [debug] MutationLogger "Persistent process "3" interaction state" set to "None", reason: initialized
2023-02-06 17:08:35.282 [trace] ptyService#start 3
2023-02-06 17:08:35.282 [trace] persistentTerminalProcess#start 3 false
2023-02-06 17:08:35.284 [trace] IPty#spawn /bin/bash ["--init-file","/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh"] {"name":"xterm-256color","cwd":"/workspaces/ansible-playground","env":{"HOSTNAME":"ansible-control","HOME":"/home/vscode","PATH":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/remote-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/vscode/.local/bin","SHELL":"/bin/bash","PWD":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164","REMOTE_CONTAINERS_IPC":"/tmp/vscode-remote-containers-ipc-b4965da84f939eef5a05e19650e15323c77aa616.sock","REMOTE_CONTAINERS_SOCKETS":"[\"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock\",\"/tmp/.X11-unix/X0\",\"/home/vscode/.gnupg/S.gpg-agent\"]","USER":"vscode","SHLVL":"1","PROMPT_DIRTRIM":"4","_":"/bin/cat","SSH_AUTH_SOCK":"/tmp/vscode-ssh-auth-b4965da84f939eef5a05e19650e15323c77aa616.sock","DISPLAY":":0","REMOTE_CONTAINERS_DISPLAY_SOCK":"/tmp/.X11-unix/X0","REMOTE_CONTAINERS":"true","BROWSER":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/bin/helpers/browser.sh","TERM_PROGRAM":"vscode","TERM_PROGRAM_VERSION":"1.75.0","LANG":"en_US.UTF-8","COLORTERM":"truecolor","GIT_ASKPASS":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass.sh","VSCODE_GIT_ASKPASS_NODE":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/node","VSCODE_GIT_ASKPASS_EXTRA_ARGS":"","VSCODE_GIT_ASKPASS_MAIN":"/vscode/vscode-server/bin/linux-x64/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/extensions/git/dist/askpass-main.js","VSCODE_GIT_IPC_HANDLE":"/tmp/vscode-git-3b2c3540f1.sock","VSCODE_IPC_HOOK_CLI":"/tmp/vscode-ipc-103b0d30-3356-40fd-99c4-9689217f4cef.sock","VSCODE_INJECTION":"1"},"cols":250,"rows":17,"useConpty":false,"conptyInheritCursor":false}
2023-02-06 17:10:24.853 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":false,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]},{"isActive":true,"activePersistentProcessId":3,"terminals":[{"relativeSize":1,"terminal":3}]}]
2023-02-06 17:10:24.860 [trace] IPty#onData ]633;C
2023-02-06 17:10:24.861 [trace] IPty#onData ]633;E;__vsc_original_prompt_command=$PROMPT_COMMAND
2023-02-06 17:10:24.861 [trace] IPty#onData ]633;D;0
2023-02-06 17:10:24.861 [trace] IPty#onData ]633;P;Cwd=/workspaces/ansible-playground
2023-02-06 17:10:24.866 [debug] CommandDetectionCapability#handleCommandExecuted 0 0
2023-02-06 17:10:24.866 [debug] CommandDetectionCapability#setCommandLine __vsc_original_prompt_command=$PROMPT_COMMAND
2023-02-06 17:10:24.866 [debug] CommandDetectionCapability#handleCommandFinished 0 0 __vsc_original_prompt_command=$PROMPT_COMMAND {"commandExecutedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":25,"_onDispose":{"_listeners":[null],"_disposed":false}},"commandExecutedX":0,"command":"__vsc_original_prompt_command=$PROMPT_COMMAND","commandFinishedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":26,"_onDispose":{"_listeners":[null],"_disposed":false}}}
2023-02-06 17:10:24.868 [trace] IPty#onData ]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:10:24.874 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:10:24.874 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:10:24.899 [trace] IPty#resize 262 17
2023-02-06 17:10:24.899 [trace] IPty#onData
]633;Avscode ➜ /workspaces/ansible-playground (main) $ ]633;B
2023-02-06 17:10:24.904 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-06 17:10:24.904 [debug] CommandDetectionCapability#handleCommandStart 49 0
2023-02-06 17:10:25.382 [trace] ptyService#setLayoutInfo [{"isActive":false,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]},{"isActive":false,"activePersistentProcessId":2,"terminals":[{"relativeSize":1,"terminal":2}]},{"isActive":true,"activePersistentProcessId":3,"terminals":[{"relativeSize":1,"terminal":3}]}]

On my Windows machne using code version 1.74.3 (WSL on Ubuntu-22.04), this issue does not occur.
After upgrading to 1.75.0, it still works as expected.
Also upgrading the extension 'Dev Container' from v0.266 to v0.275.1 does not seem to reproduce the behavior I get on my Manjaro-KDE machine.

I have the same problem since 1.75.
I cannot use the terminal in any dev-containers. I tried an existing one, the Microsoft alpine container and several others.
I develop in containers exclusively so I am certain it worked before.
Always "The connection to the terminal's pty host process is unresponsive, the terminals may stop working."
I am on Fedora 36.

I'm experiencing the same thing. Terminals take an extremely long time (minutes) to open and only do so successfully if I ignore the prompt to restart the pty host. While this is going on, I can see this process is sat consuming 100% CPU:
/app -1 -1 1 /bin/bash --init-file /vscode/vscode-server/bin/linux-x64/441438abd1ac652551dbe4d408dfcec8a499b8bf/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh

A bit more context as this is still driving me mad. Here's the Remote Pty Host trace logs for this happening:
2023-02-21 17:39:17.668 [trace] ptyService#getLayoutInfo {"workspaceId":"9b99770236c84fb98061ab648a1c2e57"}
2023-02-21 17:39:39.540 [trace] persistentTerminalProcess#ctor 1 [object Arguments]
2023-02-21 17:39:39.541 [debug] MutationLogger "Persistent process "1" interaction state" set to "None", reason: initialized
2023-02-21 17:39:39.564 [trace] ptyService#start 1
2023-02-21 17:39:39.564 [trace] persistentTerminalProcess#start 1 false
2023-02-21 17:39:39.566 [trace] IPty#spawn /bin/bash ["--init-file","/home/dev/.vscode-server/bin/441438abd1ac652551dbe4d408dfcec8a499b8bf/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh"] {"name":"xterm-256color","cwd":"/app","env":{<redacted>},"cols":371,"rows":20,"useConpty":false,"conptyInheritCursor":false}
2023-02-21 17:41:22.599 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]
2023-02-21 17:41:22.605 [trace] IPty#onData ]633;C
2023-02-21 17:41:22.607 [trace] IPty#onData ]633;E;]633;D]633;P;Cwd=/app
2023-02-21 17:41:22.607 [trace] IPty#onData ]633;Adev@c5b9a3266bb2:/app$ ]633;B
2023-02-21 17:41:22.613 [debug] CommandDetectionCapability#handleCommandExecuted 0 0
2023-02-21 17:41:22.614 [debug] CommandDetectionCapability#setCommandLine
2023-02-21 17:41:22.614 [debug] CommandDetectionCapability#handleCommandFinished 0 0  {"commandExecutedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":1,"_onDispose":{"_listeners":[null],"_disposed":false}},"commandExecutedX":0,"command":"","commandFinishedMarker":{"line":0,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":2,"_onDispose":{"_listeners":[null],"_disposed":false}}}
2023-02-21 17:41:22.615 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-21 17:41:22.615 [debug] CommandDetectionCapability#handleCommandStart 29 0
2023-02-21 17:41:22.620 [trace] IPty#resize 372 20
2023-02-21 17:41:22.620 [trace] IPty#onData
]633;Adev@c5b9a3266bb2:/app$ ]633;B
2023-02-21 17:41:22.627 [debug] CommandDetectionCapability#handlePromptStart 0 0
2023-02-21 17:41:22.628 [debug] CommandDetectionCapability#handleCommandStart 29 0
2023-02-21 17:41:23.106 [trace] ptyService#setLayoutInfo [{"isActive":true,"activePersistentProcessId":1,"terminals":[{"relativeSize":1,"terminal":1}]}]

I've just tried this with VS Code Insiders (still using dev container v0.275.1) and it's not happening there:
$ code-insiders --version
1.76.0-insider
7b6b6869e8f5b71b5e9cdbd3f590b10964f89607
x64

So hopefully this is fixed in an upcoming release :crossed_fingers:

I can confirm that it seems to befixed in version >=1.76.0
❯ code --version
1.76.0
92da9481c0904c6adfe372c12da3b7748d74bdcb
x64


Create a homepage

User Stories:

As a user, I can view all news articles in a list.

As a user, I can see how many upvotes and comments each article has.

As a user, I can click on the comment count to route to a different page.

Closing issue, homepage with handlebars created, complete


[Bug] VoiceActivity in Modal and DM Profile

Addon Name and Version
VoiceActivity v1.5.4
Discord Version
Ptb 155131 (56cefd9) Host 1.0.1019 Windows 10 64-Bit (10.0.19045)
Describe the bug
Not display in activity like old versions ?
Screenshots

Its not popout when u clic on chat its the bigger one
Enhancement
Experiment profile add

For the modal section, I couldn't find a way to reliably patch it in the same way I did after Discord's compiler switch a while ago. It was in the patch notes for that update that it would be temporarily removed until I can find a solution. It's not at the top of my todo list, but when I get a good chunk of free time I'll try to fix it again.
As for the suggestion, it's a great idea, and I'll look into adding a section for the plugin there in the future.

Ok thx

The DM profile section was just added in v1.6.0. As for the profile modal section, it’s still a pain to add it back, and I will if I ever find a good way to do it.


Feature request: Add tags to feed items

I've been using feediverse to autopost to the Fediverse.  It

uses existing tags from the items
allows you to add tags to each item (useful for comments and untag items)

Any chance of doing this with autopost?

Thanks for the request @vexillia. Could you say a bit more about what you're expecting here?
Per the examples, we do support --tags to manually specify tags to add to each post. I believe that only works with autopost manual, though, so if you're interested in it for autopost atom we could consider adding that 🙂

OK.  With feediverse I can specify the template for the post to include tags from the item (if they exist) and add certain tags to every post as follows:
template: "{title} \n{link} \n{hashtags} #viaRSS\n"
template: "{title} \n{link} \n{hashtags} #BlogComment #viaRSS\n"
This produces:

So when autoposting (not manual), I'm interested in an  equivalent to the {hashtags} switch and an ability to add tags like #viaRSS to every post.
I'm not bothered about other formatting options (but they would be nice). :-)

Gotcha, thanks. Yeah, I think we could enable that by adding --tags to autopost atom, which would append any explicitly specified tags to the set pulled from the feed.

At the moment I'm not getting any tags if they exist within the item with just:
autopost atom feed
Is that right?

Is that right?

That sounds like a bug -- autopost atom should always pull the feed's tags. Could you share an example entry from the feed? It's possible that the tags aren't structured correctly (there's a lot of invalid Atom RSS in the wild).

Here's a snippet showing the tags:
<link rel='replies' type='application/atom+xml' href='https://blog.vexillia.me.uk/feeds/4282617702182468787/comments/default' title='Post Comments'/>
<link rel='replies' type='text/html' href='https://www.blogger.com/comment/fullpage/post/2202580486252841248/4282617702182468787' title='0 Comments'/>
<link rel='edit' type='application/atom+xml' href='https://www.blogger.com/feeds/2202580486252841248/posts/default/4282617702182468787'/>
<link rel='self' type='application/atom+xml' href='https://www.blogger.com/feeds/2202580486252841248/posts/default/4282617702182468787'/>
<link rel='alternate' type='text/html' href='https://blog.vexillia.me.uk/2024/09/basing-recipes.html' title='Basing Recipes'/>

<author>
<name>Vexillia</name>
<uri>https://www.blogger.com/profile/06568117694302239705</uri>
<email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTOHpPdy-qK7_7UGDXenKCbTQsWuPTwpBZ21uIqDj4_PxjlRJA08cW5aioGK5BT39Ku4EoQ0o0pfMq4MMhQGwLYn69_3ESQRkoSnXI93qnUuJmMJha-90aP9vuJY-K3xfeUcgyn_fvZzoejqFgao0kwYALZZmTDS2TWnwpTzQjfKgUAm4/s220/20220123%20-%20Be%20Pure.jpg'/>
</author>

<media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhXoeI0j_FxZAolS7rbW-CfC3ZQB28eUBkz4A7A2OoCLk3NGn1Vc_4RZ4Tg48LDGzHoIpibPoQ5e3IW0IA7zVakDlajPdGN8w9B1a25KKwcnwYig8or0Pn0qI1cRwaWkUmXSptyJ1dHUCwNfsFwZucqO3wb4oWJBBq1Gj6vqQbAI84M0AZirU7Ro8DU866n/s72-c/20220204%20-%20%20S8001954f.JPG' height='72' width='72'/><thr:total>0</thr:total></entry>

<entry>
<id>tag:blogger.com,1999:blog-2202580486252841248.post-4863971468292128007</id>
<published>2024-09-10T18:00:00.006+01:00</published>
<updated>2024-10-31T18:23:28.866Z</updated>
<category scheme='http://www.blogger.com/atom/ns#' term='Ancients'/>
<category scheme='http://www.blogger.com/atom/ns#' term='ADLG'/>
<category scheme='http://www.blogger.com/atom/ns#' term='On Tour'/>
<title type='text'>ADLG: Northern League Round 4 (Manchester, 08 September 2024) </title>
<content type='html'>

Here's the full feed:
view-source_https___www.blogger.com_feeds_2202580486252841248_posts_default.txt
Hope this helps.  BTW it's Blogger feed.

Thanks, that is indeed helpful -- the <category /> listings there look right, so I'll try and debug this some more later.

Any luck?

Any luck?

Sorry, but I can't reproduce any tagging issues here. Here's what I see when I use your RSS feed with a dummy backend:
$ autopost atom https://feeds.feedburner.com/TheWavingFlag
DUMMY (dummy): content='ADLG: King In The North (York, 19 - 20 Oct 2024)' url='http://blog.vexillia.me.uk/2024/10/adlg-king-in-north-york-14-15-oct-2023.html' tags=['ADLG', 'Ancients', 'On Tour']
🎉 dummy: http://blog.vexillia.me.uk/2024/10/adlg-king-in-north-york-14-15-oct-2023.html

Based on that output, the tags are present.
I also tried with the other feed URL, and it also works:
$ autopost atom https://www.blogger.com/feeds/2202580486252841248/posts/default/4282617702182468787
DUMMY (dummy): content='Basing Recipes' url='https://blog.vexillia.me.uk/2024/09/basing-recipes.html' tags=['Hobby', 'Tips']
🎉 dummy: https://blog.vexillia.me.uk/2024/09/basing-recipes.html

note tags=['Hobby', 'Tips'] in the output there.

I also tested this:
autopost --config-file /home/vexillia/.autopost.toml manual "test" --url https://www.blogger.com/feeds/2202580486252841248/posts/default --tags ADLG
again no tags:

Oh, looks like this is a bug specifically in the Bluesky backend -- we don't emit tags there at all. I'll see what can be done there.

Looks like I need to call tag() once per listed tag.

Morning!  Any luck unravelling the Bluesky API calls for tags?

Done with https://github.com/woodruffw/autopost/commit/73df7bdeced4a3487b6775c3eb1fdb4b551f2bec -- I'll make a release shortly.

Confirmed with v0.9 and thanks.


[3.3] Backport of 2 small fixes

Partial Backport of #24968 to stable branches.
3 changed lines.
Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Which branches do we want this on? It applies cleanly all the way back to 3.0, but the discussions in #24968 only talk about 3.3.

IMO should be applied all the way through to 3.0

ping @FdaSilvaYY to fix the whitespace error

Whitespace fixed !

This pull request is ready to merge

Merged to the 3.3, 3.2, 3.1 and 3.0 branches. Thank you for your contribution.


Update Site settings “info”

Automatically generated by Netlify CMS

:construction_worker: Deploy Preview for determined-goodall-4680a1 processing.
:hammer: Explore the source changes: f152dbf62c0ff1b2746ebf27db075329a70ac5f9
:mag: Inspect the deploy log: https://app.netlify.com/sites/determined-goodall-4680a1/deploys/60c91ceee849b100080194e7


Replace 'subscriptionKey' with 'key' in ruby.md

Hello 👋 I was following the guides at https://docs.microsoft.com/en-us/azure/cognitive-services/bing-spell-check/quickstarts/ruby and noticed that we mention subscriptionKey in the guide, but it doesn't exist in the code. It's called key instead, so fixing it.

@pizza : Thanks for your contribution! The author, @v-jaswel, has been notified to review your proposed change.

Thanks for finding this @pizza! Let's definitely merge this in. #sign-off
Feel free to reach out again if you find anything else in our docs!

@aahill: I'm sorry - only the author of this article, @v-jaswel, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


4-week average calculates incorrectly for recently added users

Expected behavior: New user that has participated in the auction for two weeks, gaining 300 and 400 points respectively, has a 4-week average of (200 + 400) / 2 = 300 points.
Actual behavior: New user that has participated in the auction for two weeks, gaining 300 and 400 points respectively, has a 4-week average of (200 + 400) / 4 = 150 points.

That is up to debate / matter of definition. As a matter of fact within the last 4 weeks that user has contributed an average of 150 points per week, since the contribution was 0 in the first two weeks.
This is related to the problem of total average which could be defined as (total_points / beginning_of_time) or ( total_points / time_since_first_participation) or (total_points / weeks_participated) or (total_points / weeks_contributed) etc... While the first option is not useful, most other options require a greater extent of data tracking that does not exist yet in the system since participation cannot be defined based on (lack of) bids or transaction.
It's also worth mentioning that there are many edge cases in which the statistic calculation will behave incorrect or fuzzy.

Possible solutions if someone has not participated in all of the last 4 weeks:

leave the 4 week average section blank
grey the average and put an tooltip/hover-over explaining the user hasn't been there all 4 last weeks.


Enabling all source inclusion with source link

This PR enables storing compressed source files inside PDB files, so they can later be accessed using System.Reflection.Metadata without the need for internet connection.

All sources are indeed packaged into pdb, as shown by dotPeek:


nixos/gtk: init

Motivation for this change
See #71079
Qt part #80866
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

One thing this is lacking is a test suite. Ideally a Matrix of gnome, gnome-xorg, i3 or something and sway.

@jtojnar

One thing this is lacking is a test suite. Ideally a Matrix of gnome, gnome-xorg, i3 or something and sway

What test should do? Just take screenshots? What gtk program should be used to demonstrate that settings do work? Sway will show nothing until there is a solution for #54150

I think having a simple script verifying that the setting apply in different environments (i3, Sway, Plasma, GNOME Shell) should be good.
Something like https://github.com/NixOS/nixpkgs/blob/ef34994d9a4407954c2207b3e72cb3a16fc9be56/nixos/tests/fontconfig-default-fonts.nix#L28-L31
Looking at https://lazka.github.io/pgi-docs/#Gtk-3.0/classes/Settings.html#Gtk.Settings.props.gtk_theme_name, I would expect something like this to work but it does not seem to:
nix-shell -p gobject-introspection -p gtk3 -p 'python3.withPackages (p: with p; [pygobject3])' --run "python3 -c \"import gi; gi.require_version('Gtk', '3.0'); from gi.repository import Gtk; s = Gtk.Settings.get_default(); print(s.props.gtk_theme_name)\""

I might try to pick this up and make a new pr could be useful. If anyone has any concerns to raise about a new pr lmk.

If we want this, we will probably want to not treat all GTK versions as monoliths and go more in the direction of RFC 42.


Repo sync for protected CLA branch

The pull request is created from master637576670767223596 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


problem when open a modal while some modal is already opening

while some modal is opening, open a new modal will not clear previous overlay.

Do you have a modal that opens a modal?
If this is still a problem, please provide a way to reproduce it.
Closed due inactivity but feel free to reopen it if it is still necessary.

Seems like a Duplicate of https://github.com/Dogfalo/materialize/issues/4044


build deprecation warnings

When building with current SCIP bugfix branch (v91-bugfix) on a Debian12 system, there are several warnings:
17:58:56 + cmake .. -DSCIP_DIR=/scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/build/scip
17:58:56 CMake Deprecation Warning at CMakeLists.txt:5 (cmake_minimum_required):
17:58:56   Compatibility with CMake < 2.8.12 will be removed from a future version of
17:58:56   CMake.
17:58:56
17:58:56   Update the VERSION argument <min> value or use a ...<max> suffix to tell
17:58:56   CMake that the project does not need compatibility with older versions.
17:58:56
17:58:56
17:58:56 -- The C compiler identification is GNU 12.2.0
17:58:56 -- The CXX compiler identification is GNU 12.2.0
17:58:56 -- Detecting C compiler ABI info
17:58:56 -- Detecting C compiler ABI info - done
17:58:56 -- Check for working C compiler: /usr/lib/ccache/cc - skipped
17:58:56 -- Detecting C compile features
17:58:56 -- Detecting C compile features - done
17:58:56 -- Detecting CXX compiler ABI info
17:58:57 -- Detecting CXX compiler ABI info - done
17:58:57 -- Check for working CXX compiler: /usr/lib/ccache/c++ - skipped
17:58:57 -- Detecting CXX compile features
17:58:57 -- Detecting CXX compile features - done
17:58:57 -- Found JNI: /usr/lib/jvm/default-java/include  found components: JVM
17:58:57 -- Found Java: /usr/bin/java (found version "17.0.11")
17:58:57 -- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
17:58:57 libscip is a SHARED_LIBRARY.
17:58:57 -- Configuring done
17:58:57 -- Generating done
17:58:57 -- Build files have been written to: /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/JSCIPOpt/build
17:58:57 + make -j4
17:58:57 [  9%] Building Java objects for scipjar.jar
17:58:57 [ 18%] Building CXX object CMakeFiles/jscip.dir/src/scipjni_wrap.cxx.o
17:58:59 [ 27%] Generating CMakeFiles/scipjar.dir/java_class_filelist
17:58:59 [ 36%] Creating Java archive scip.jar
17:58:59 [ 36%] Built target scipjar
17:58:59 [ 45%] Building Java objects for examples.jar
17:58:59 In file included from /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/scip/src/scip/scip.h:44,
17:58:59                  from /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/JSCIPOpt/src/scipjni_wrap.cxx:753:
17:58:59 /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/JSCIPOpt/src/scipjni_wrap.cxx: In function ‘SCIP_CONS* createConsBasicQuadratic(SCIP*, const char*, int, SCIP_VAR**, double*, int, SCIP_VAR**, SCIP_VAR**, double*, double, double)’:
17:58:59 /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/JSCIPOpt/src/scipjni_wrap.cxx:867:52: warning: ‘SCIP_RETCODE SCIPcreateConsBasicQuadratic(SCIP*, SCIP_CONS**, const char*, int, SCIP_VAR**, double*, int, SCIP_VAR**, SCIP_VAR**, double*, double, double)’ is deprecated [-Wdeprecated-declarations]
17:58:59   867 |       SCIP_CALL_ABORT( SCIPcreateConsBasicQuadratic(scip, &cons, name, nlinvars, linvars, lincoefs, nquadvars, quadvars1, quadvars2, quadcoefs, lhs, rhs) );
17:58:59       |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17:58:59 In file included from /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/JSCIPOpt/src/scipjni_wrap.cxx:755:
17:58:59 /scratch/opt/jenkins/workspace/SCIPOptSuite_test_interfaces/scipoptsuite-9.1.1/scip/src/scip/cons_quadratic.h:124:14: note: declared here
17:58:59   124 | SCIP_RETCODE SCIPcreateConsBasicQuadratic(
17:58:59       |              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

This deprecation is since SCIP 8.0.0 !

Well, JSCIP is released separately from SCIP and generally does not require you to use the latest version of SCIP. So I saw little point in applying this method rename, possibly with some #ifdef mess, when the old names are still working. But I guess I can do the change now, I doubt anyone still wants to use SCIP 7.x.x by now, so we can just use the new name and be done with it now. I will do that ~2 weeks from now after my paid time off, unless someone beats me to it.

Thanks. No hurry. The old function may just be removed at some point.

Makes sense.

Turns out the current JSCIPOpt does not build with SCIP < 8.0.0 anyway, so I might as well just switch to the non-deprecated functions here.

(See #50.)


Angular templates are not working (missing ng-app)

Steps to reproduce:

https://plnkr.co/ > Launch the Editor
New > AngularJS > 1.4.X

Current Behaviour:
The following html is generated:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <title>AngularJS Plunker</title>

    <link href="style.css" rel="stylesheet" />

Hello {{name}}!

The following html is rendered:
Hello {{name}}!

Adding  seems to fix the issue:
Hello World!

I would fix it but I don't know where the templates are stored :(

Update title sine its not specific to Angular 1.4, seems to occur with all Angular versions

This happens to me in Firefox only since forever. I asked @ggoodman about this when it first started, and I think he said it's a security thing in Firefox or something.


Installing mattermost-team-edition in a namespace that contains another pod is causing an error

Whenever i try to install mattermost-team-edition to a namespace that contains another pod, it is causing an error of CrashLoopBackOff to the mattermost-team-edition pod. Everything works perfectly though if I set it up on a brand new namespace.

Didn't run into this issue when I deployed it in a namespace where there was another pod. Maybe resolved?


Remove synthetic expected output tokens option

The synthetic expected output tokens option helped provide a way for users to recommend an output token length to GenAi-Perf via prompt engineering. However, it did not guarantee a set number of expected output tokens will be generated.
Now that we are adding a way to precisely set the output token count mean and standard deviation, a user can always just set the output token mean to be the number of output tokens they want and the standard deviation to 0 for the same effect. As a result, we can remove the expected output tokens option to remove overlap and provide an option with increased accuracy.

recommend an output token length to GenAi-Perf via prompt engineering
@nv-braf is that true?

tentatively seems good to go

output token count mean and standard deviation

the PR for this is still pending right?

recommend an output token length to GenAi-Perf via prompt engineering

@nv-braf is that true?

You can see it in these lines:
prompt = (             "Randomly stream lines from the following text "             f"with {expected_output_tokens} output tokens. "             "Don't generate eos tokens:\n\n"         )

tentatively seems good to go

output token count mean and standard deviation

the PR for this is still pending right?

That's right. Once I merge this into that PR's branch, that PR should be pretty much ready to review. Just going to add a few more tests there.


minor problem in W1D3 tutorial 6

The code in the first task of W1D3 has two extra indents where "return mse_all"

Thanks for flagging, we pushed a fix in #314; I'm sorry we weren't able to fix for the earlier timezones.


Compilation errrors

The error i have is this I cant explain it but i tried to compile the game and this happened
[C:/HaxeToolkit/haxe/lib/polymod/git/polymod/format/XMLMerge.hx:189: characters 10-23 : Warning : This typedef is deprecated in favor of haxe.xml.Access
C:/HaxeToolkit/haxe/lib/polymod/git/polymod/format/XMLMerge.hx:189: characters 30-43 : Warning : This typedef is deprecated in favor of haxe.xml.Access]: these two should be fix because of the ASIPSuff.hx file in sources but its not missing so I not sure whats wrong and the stuff below I dont know about**
source/LuaClass.hx:35: characters 46-58 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:1669: characters 42-54 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:1469: characters 42-54 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:1144: characters 42-54 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:855: characters 41-53 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:635: characters 40-52 : Type not found : StatePointer
source/Replay.hx:55: lines 55-145 : Defined in this class
source/LuaClass.hx:370: characters 42-54 : Type not found : StatePointer
Pls fix these issues I cant compile the game if their not fixed in the next update

You need the linc_luajit library

how do you install that

Ya so how do I get that exactly

haxelib git linc_luajit https://github.com/nebulazorua/linc_luajit.git

Thank You Very Much


Per-channel notification configuration

I would love to be able to configure my notification preferences on a per-channel basis. For instance, there's a channel directly related to a project (#project) I'm working on that I would like to be notified by each time a message is received in that channel. In contrast, there's a general channel (#general) for everyone that's very busy and almost never relevant to me.
So in the examples above, I would like to receive notifications for all messages in #project, while only receiving notifications in #general if I'm mentioned.

Just me?

This is planned for settings overhaul, see #85.


Websocket support

Hello !
Thanks a lot for your project, by curiosity, will you support the websocket client for surrealdb ?
Thanks a lot

@IDerr Hey, we're adding the support for websockets soon. It should be available in less than a week, from today. Sorry for the late answer, but we're having issues with notifications :sweat_smile:

@IDerr  Hey, we're adding the support for websockets soon. It should be available in less than a week, from today. Sorry for the late answer, but we're having issues with notifications sweat_smile

No worries! Thanks for the notification!

I added support in 9c9f1f7c7a8b8050ffa1eeab797b72041a4e463b.
Let me know how it works for you :smile:


Feat/100 mb files

fix #85

It turns out that this might not be the biggest file - so we'll postpone this.


[Feature]Allow PlaywrightAssertions to work with Response object

PlaywrightAssertions works with APIResponse object but I'd like to also be able to use it with the Response object.  The use-case is being able to ensure certain requests that are made as part of page events are successful.  Based on the result of those requests certain UI elements are enabled or disabled.

@yury-s your example is exactly what i'm doing today.  I was just hoping to use a more readable assertion but the if/else works just fine.  This is part of a smoke test to validate that a grid gets loaded with data if there is data in the response.
basically my test looks like this:
  @Test
  public void somePageTest(Page page) {
      var response = page.waitForResponse(SomePage.onLoadEndpoint, () -> dashboardPage.someStuff.click());
      var somePage = PageFactory.create(SomePage.class, page);

      // when this fails the error message would be "expected true got false" and i was hoping for consistent error messages.
      assertThat(response.ok()).isTrue();

      if(response.length > 0) {
          assertThat(somePage.someGrid).isVisible();
      }

      assertThat(somePage.someGridRows).isVisible();

    }

Related upstream issue: https://github.com/microsoft/playwright/issues/12171

Folding into the upstream issue, since this is not Java specific.


Neetcode Youtube video used Bellman Ford but solution on website is using Modified Dijkstra's

Leetcode Question 787. Cheapest Flights Within K Stops
Solution Provided: Github Solution
Neetcode video: YT Link

Has been fixed


The readonly attribute of TextArea break vscode.workspace.onDidChangeTextDocument API on browser version vscode

VS Code Version:
OS Version:

Steps to Reproduce:

open a browser version vscode
open a editor with readonly mode
any extension who use the vscode.workspace.onDidChangeTextDocument API would be invalid

This issue won't be occured on desktop version. Follow code show more details:
https://github.com/microsoft/vscode/blob/c57c05ea36/src/vs/editor/browser/controller/textAreaHandler.ts#L135-L137
the readonly attribute is used to disable keyboard popping in mobile devices, but it break the vscode.workspace.onDidChangeTextDocument event too.
Change the platform.isWeb to platform.isIOS may be better

Does this issue occur when all extensions are disabled?: Yes

@conwnet Can you please give an example of how vscode.workspace.onDidChangeTextDocument behaves differently?  I am not 100% convinced that there is a bug here. I would expect that vscode.workspace.onDidChangeTextDocument is never called, not in desktop and also not in web.

@conwnet Can you please give an example of how vscode.workspace.onDidChangeTextDocument behaves differently? I am not 100% convinced that there is a bug here. I would expect that vscode.workspace.onDidChangeTextDocument is never called, not in desktop and also not in web.

There is a bug that are relatively easy to reproduce, when someone use GitHub CodeSpaces (because the bug only occured in browser version):

Install the Vim extension and the GitLens Extension. (the VIM extension require the vscode.workspace.onDidChangeTextDocument API for basic hjkl cursor motion, and the GitLens extension will provide can readonly mode editor)
Open any file which has at least two commit, click Open Change with Previous Revision in the editor menu title.

then we will get a readonly editor, but VIM extension can not move cursor by pressing hjkl key here.

The readonly attribute was added in this commit: https://github.com/microsoft/vscode/commit/0040158a0d438bf9c1584edc9733bf8708e1360c As the message describe, it used to disable keyboard popping up on mobile devices, and there is no isWeb condition at the earliest time.
and then add the isWeb condition at this commit https://github.com/microsoft/vscode/commit/69ae6cdf2183dd8c7a7e845dec7f032ce9ff2af9 by you @alexdima 😂, I guess that's the readonly attribute cause some bug at desktop version?
Another thing, I think when we need consider the mobile devices, I think change the platform.isWeb to platform.isMobile may be better, but there is not a option named isMobile in platform.ts, so I just change it to platform.isIOS at #117758.

To verify, use vim in the browser in a readonly editor.


Allow X or Y axis ticks to start from any point on the axis line. (Non Uniform Ticks)

Is your feature request related to a problem? Please describe.
We currently have a graph in development where we need to display the Y2 Axis ticks from middle or somewhere else on the Y2 Axis line. Usually the ticks that we send to carbon is always uniform.
Describe the solution you'd like
I wanted to know if there is a way to have non uniform ticks or ticks starting from other point or then axis line. Or will carbon allow for non uniform ticks in the future?
Screenshot
UX reference on how it should look like:

Implementation that i could achieve using<EMAIL_ADDRESS>

Also is there any way to hide the data points on the left Y axis? This got introduced when i added the Y2 axis & I could find any exposed parameter/property from Carbon to hide it.

To add to this, I wanted to start my y axis from 18 & my Y2 axis from -1000.

But somehow the x axis moved upwards & the values didn't align as I wanted. Is this the normal behavior of carbon? Is there any way to hide that bold x axis line or move it downwards at the base line.
Code Snippet:

Hi,
We needed clarifications on the relationship between y & y2 axis.
So for our project, we have Gestation Age as x axis, Fundal height as y axis & Fetal Weight as y2 axis.
Currently we have a formula defining the relation between y & y2 axis i.e. Fundal Height & Fetal Weight respectively.
_ Relation:  Fundal Height(y) = (Fetal Weight + 5012)/226 _
Our Fundal height y axis ranges from 18 cm to 46 cm & Fetal weight y2 axis from 500g to 500g. We have a relationship using a formula we cannot align properly in the graph.
We wanted to achieve something like this:

As of now, this is what we have achieved:
https://github.com/cerner/carbon-graphs/issues/257#issuecomment-655959873
But our implementation is an just approximation, & it will not be accurate to each & every patient.
So the question is that
Can we have the ticks on y2 axis with a relation to y axis? OR Is there any way to establish a relation & plot points according to both y & y2 axis?
JS Project Link: https://github.cerner.com/aeon-womenshealth/fundal-height-js/blob/2fc55da15345255653473142c0ac77e98a56ddf3/src/fundal-height/utils/DataHelpers.js#L413

Hi @hackawesome , thanks for opening this issue.

I’m not sure if it’s possible to start ticks at any point in the axis out of scale. The only alternative I can think of is giving the option of non-linear scales. But we can continue investigating both possibilites int the future.

Can you elaborate? Do you mean that you would like to toggle visibility of Y-axis datapoints?

Making the 0 line bold is normal Carbon behavior.

Y and Y2 axes are independent. If you want any correlation between Y and Y2 ticks, you can calculate them using your formula and pass in an array of custom values.

Hope this answers your questions.

Hi @hackawesome , thanks for opening this issue.

I’m not sure if it’s possible to start ticks at any point in the axis out of scale. The only alternative I can think of is giving the option of non-linear scales. But we can continue investigating both possibilites in the future.

Can you elaborate? Do you mean that you would like to toggle visibility of Y-axis datapoints?

Making the 0 line bold is normal Carbon behavior.

Y and Y2 axes are independent. If you want any correlation between Y and Y2 ticks, you can calculate them using your formula and pass in an array of custom values.

Hope this answers your questions.

Closing due to no activity for 3 weeks.


add rookie post

@kyle-dorman @johncoghlan
Team rookie post by @merrittlosert @aninthios & I!

Looks great! Some of these images seem huge and potentially smaller ones could be used--for example, rather than loading the full resolution and resizing by tags.

@zcohn Thanks! For the second set of feedback, does this just mean to host a smaller resolution image on imgur?

Exactly.

Fixed the large images - thanks everyone! @johncoghlan

@zcohn @johncoghlan @jkenny do you all think this is good to go?

Couple of minor suggestions but other than that it looks great!

@jkenny thanks for taking a look. I updated based on your comments.

LGTM

Ok last chance for comments @here. If there aren't any, I will merge tomorrow morning.

👊

Woohoo! 👍 👍 👍


Validator allows duplicate operationId values in some cases

At least when two operations use a $ref to the same operation object, the validator doesn't seem to pick up on the consequentially shared operationId.

It does look for duplicated operation ids, but that's an interesting edge case that I guess it can't handle. That's worth looking into, thanks for the issue

Hey @danhudlow, finally getting around to looking at this. I'm wondering about this pattern that you're finding the problem with. It doesn't look like the spec supports referencing entire operations (based on the definition of a path object).
Are you storing operation objects under schemas (or definitions if using OpenAPI 2) and then referencing them at the path level like so? :
"/some/path": {
  "get": {
    "$ref": "#/components/schemas/Operation1"
  }
}

I guess I'm also a little confused why you would create a named schema for an operation since they shouldn't be used more than once.

The path item object itself can contain a reference, and I have seen two different paths offer the same behavior by referencing the same path item object.

Ah yes, you're correct. Thanks for setting me straight. That still seems like an odd pattern to me, since any path item shared between two paths would have the colliding operation ID problem you originally mentioned (if the shared path item has an operation defined). That said, I understand the use case so I'll add logic just to check the existence of duplicated IDs.

@dhudlow Have a look at the test case in #31 and let me know if that is a realistic and/or appropriate use case for what you were looking to fix.

Looks right to me!

:tada: This issue has been resolved in version 0.2.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove initial State configuration in tests with PseudoModel configuration

Description
A coordinate PR to ensure orca-jedi tests pass if this oops PR is merged. Leaving in draft for now since the oops one is.
Issue(s) addressed
None.
Dependencies
https://github.com/JCSDA-internal/oops/pull/2522
Impact
None.
Checklist

[x] I have updated the unit tests to cover the change
[ ] ~New functions are documented briefly via Doxygen comments in the code~
[ ] ~I have linted my code using cpplint~
[x] I have run the unit tests
[x] I have run mo-bundle to check integration with the rest of JEDI and run the unit tests under all environments

There is an associated sith ocean obs processing apps change for this that would have to be coordinated with this change too.

@tom-8822 Do you have a link to a mo-bundle build (containing this and the parent change) so that I can test this change against sith? We would need to coordinate the change with sith when it comes down to it, as our operational configs currently have this issue.

The below all look OK to me, however be aware that we have had an anomalous test failure that started appearing overnight for oceansound_multi that is nothing to do with this change.
Testing

[ ] ostia configuration on spice
[ ] ocnd configuration on spice
[ ] gl_ocn configuration on spice
[ ] ostia configuration on xc
[ ] ocnd configuration on xc
[ ] gl_ocn configuration on xc


od predict correct boundingbox.

fix https://github.com/apple/turicreate/issues/2707

Oh now the format of the predict() only match the bounding box definition for turicreate only (top_left for origin, center for position).
@nickjong should we return different format according to the model state:
state['annotation_origin'], state['annotation_position'] ?
(I actually don't know why we allow user to define the bounding box coordinate for annotation at the c++ level,
but I guess it is for createml).

good!

Pass on gitlab. Will merge it.


Provide ability to handle output binding failures in JavaScript

If you're writing a function that is using a trigger type that has no built-in retry such as a HTTP or Event Hubs there is no way to handle errors that occur when executing output bindings. This can result in the loss of data. The same is not true in C#, because types such as IAsyncCollector can be used and flushed while in user code e.g.
        public static async Task Run(
            EventData sensorEvent,
            IAsyncCollector<EventData> outputWeatherData,
            TraceWriter log)
        {
            var message = new WeatherData
            {
                SensorId = $"Sensor_1",
                Humidity = 12,
                Precipitation = 12,
                Temperature = 80
            };

            try
            {
                await outputWeatherData.AddAsync(new EventData(JsonSerializerHelper.ToByteArray(message)));
                await outputWeatherData.FlushAsync();
            }
            catch(Exception e)
            {
                // handle error
            }
        }

A good JavaScript experience might look something like this:
module.exports = function (context, myQueueItem) {
    context.log('JavaScript queue trigger function processed work item', myQueueItem);
    context.done(null, { myOutput: { text: 'hello there, world', noNumber: true }}, function(err) {
        // handle output binding errors
    });
};

I'll work on a design for this. We should try to get to this in 2.x

I think @mathewc 's error filter work would provide a solution for this.

Yes - for https://github.com/Azure/azure-webjobs-sdk/issues/980 we're enabling exception filters that can handle ALL execution errors.

Closing as the fix for  Azure/azure-webjobs-sdk#980 is now available


Installation documentation

In the installation documentation, it is possible to click on "Copy", to copy the installation command to clipboard:
npm install -g @sap-cloud-sdk/cli@latest
The copied command does not work because also the leading dollar sign is copied:
$ npm install -g @sap-cloud-sdk/cli@latest
zsh: command not found: $

The documentation shall be fixed: https://sap.github.io/cloud-sdk/docs/js/getting-started#installation

This repository is deprecated.
As replacement, we provide extensive setup guides for your projects: https://github.com/SAP-samples/cloud-sdk-js.


Remove-Item should provide -File parameter

Summary of the new feature / enhancement
Current Situation
Currently, trying to recursively delete files with a particular file extension also deletes all sub directories in a call like this:
Remove-Item * -Recurse -Filter '*.java'

Example
PS C:\Temp\Test> Get-ChildItem * -Recurse -Name -Filter '*.java'
trunk\MyProject\File1.java
trunk\MyProject\File2.java
trunk\MyProject\MyFolder\File1.java
trunk\MyProject\MyFolder\File2.java

PS C:\Temp\Test> Remove-Item * -Recurse -Verbose -Filter '*.java'
VERBOSE: Performing the operation "Remove Directory" on target "C:\Temp\Test\Something".
VERBOSE: Performing the operation "Remove Directory" on target "C:\Temp\Test\Something\trunk".
VERBOSE: Performing the operation "Remove Directory" on target "C:\Temp\Test\Something\trunk\MyProject".
VERBOSE: Performing the operation "Remove Directory" on target "C:\Temp\Test\Something\trunk\MyProject\MyFolder".
VERBOSE: Performing the operation "Remove File" on target "C:\Temp\Test\Something\trunk\MyProject\MyFolder\File1.java".
VERBOSE: Performing the operation "Remove File" on target "C:\Temp\Test\Something\trunk\MyProject\MyFolder\File2.java".
VERBOSE: Performing the operation "Remove File" on target "C:\Temp\Test\Something\trunk\MyProject\File1.java".
VERBOSE: Performing the operation "Remove File" on target "C:\Temp\Test\Something\trunk\MyProject\File2.java".

PS C:\Temp\Test> Get-ChildItem
PS C:\Temp\Test>

Desired Situation
(a) Directories not matching the filter should not be deleted.
(b) Add a -File parameter, providing the same functionality as the Get-ChildItem -File parameter.
Version
PS C:\Temp\Test> $psversiontable

Name                           Value
----                           -----
PSVersion                      7.3.9
PSEdition                      Core
GitCommitId                    7.3.9
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Proposed technical implementation details (optional)
See above.

While I understand the desire to enhance Remove-Item, I think what @SteveL-MSFT  is proposing is more than just a workaround:
Given that all provider cmdlets (Get-Command *-Item*)  other than Get-ChildItem (as well as Select-String) lack advanced filtering capabilities, it makes sense to confine those to the Get-ChildItem, and require use of the latter to provide the list of input objects via the pipeline.

I comprehend the tendency for not touching a running system. Yet, the current implementation adds serious hazard by deleting more items than stated in the command as unwanted side effect, and there is no way of avoiding that other than having another command do the job.

My fundamental concern is that adding additional switches to only one other provider cmdlet introduces an awkward inconsistency - why don't the others have them?

By contrast, clearly documenting that Get-ChildItem is the provider cmdlet to use for advanced filtering capabilities, and using its output as pipeline input to the others, if needed, is a conceptually straightforward solution that avoids either inconsistencies or a lot of duplication of functionality.

I hear you re the risks of inadvertent deletion of items with Remove-Item, but the problem goes deeper - see below.

Just as a general tip (you may already know this): Adding -WhatIf previews what items would be targeted for deletion by a given call.

Taking a closer look at your specific Remove-Item command:

A conceptual problem is that -Recurse mostly does not work the way it does in Get-ChildItem; its purpose is to be an opt-in to quietly remove any directories among the targeted items.

To me, this semantic difference is problematic, and -Recurse never made much sense as an override-a-confirmation-prompt switch (there is -Force, but it already combines two behaviors: including hidden items and, on Windows, overriding a ReadOnly attribute).

A bug is that that adding -Recurse causes the -Filter argument to be ignored.

In other words: your command targets all items - both files and subdirs. - in the current directory, and quietly removes them.

This is obviously a serious problem: see #20651

Curiously:

If you use -Include rather than -Filter, -Recurse does also recurse into subdirs. and the filtering works as intended (but still wouldn't protect you from matching subdirs. too).

As an aside:

If Remove-Item worked like Get-ChildItem, Remove-Item *.java -Recurse -WhatIf should work the same, but doesn't: -Recurse then again only acts as the confirmation-prompt override switch.
That said, Get-ChildItem behavior in this case is itself highly problematic, especially if the -Path argument doesn't contain wildcard characters: it is still treated as a name to search for in the entire subtree - see #5699

The above isn't the only problem; there's a number of open Remove-Item bugs as of this writing:

https://github.com/PowerShell/PowerShell/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+remove-item

@SetTrend, to me the tl;dr  is (keep in mind that I'm just a fellow user):

I don't think what you're suggesting should be added to Remove-Item.

Remove-Item does need changing, however:

The aforementioned bugs need fixing.
For the sake of usability and to avoid conceptual confusion - without breaking backward compatibility [too much] - it is worth hiding the current -Recurse switch (primarily from the documentation), in one of two ways:

Either: By making it an (effective) alias of -Force (while exceptionally tolerating the presence of both -Force and -Recurse), meaning that the existing semantics of -Force would be overloaded (technically, a breaking change, though arguably one that falls into bucket 3).
Or: By introducing a new switch with an unambiguous name and make -Recurse an  alias of it; however, it's hard to come up with a good name; -WithContent?

The WG has reviewed this and considers this to be more of a documentation issue. The PowerShell paradigm is to get a group of things and then perform some action. The get cmdlet provides the filtering which is what is asked for here. The Remove-Item cmdlet is working as designed.


Navigation between slides on small resolutions

Hello,
I have an issue - three dots at the bottom of the slider, I mean navigation between the sliders, it doesn't work at small resolutions unless the page has been refreshed.
Not sure if it's my page's problem or script's, but I've tried changing z-indexes, deleting/replacing svg's - nothing helps.
Btw had the same problem with Owl Carousel...

My bad, the problem was with other block's height covering slider...


novoalign step: Did not find non-empty output file

Running bcbio_nextgen.py config/test.yaml -t ipython -n 24 -s sge -q comp2.q I get the following error after aligning a chunk of a fastq:
Did not find non-empty output file .../align/C6736ANXX_5_1_chastity_passed/split/tx/tmpqVdxNE/1_2015-07-07_test-sort-1_20000000.bam
[2015-07-19T05:55Z] compute-2-1.local: Uncaught exception occurred

The file 1_2015-07-07_test-sort-1_20000000.bam exists in .../align/split/ and was never present in the tmp directory as far as I could tell.

Tyler;
Sorry about the issues. bcbio is failing a sanity check and not finding the output BAM file it expects from alignment. It's tough to tell from this snippet what failed since the errors are typically upstream in the log file. Can you reproduce if you run in non-distributed mode with -n 1? If so, it might be easier to identify the underlying issue with the alignment and suggest a fix. Hope this helps.

I'll give it a try. This is a little unrelated, but for the purpose of speeding up debugging this issue I'll bring it up anyway. At the very top of my config file I'd put test_run: True. However it seems as though the input file is not being downsampled, judging by the output files so far:
-rw-r--r-- 1 tfunnell users 498M Jul 18 22:55 1_2015-07-07_test-sort-1_20000000.bam
-rw-r--r-- 1 tfunnell users 344M Jul 20 14:03 1_2015-07-07_test-sort-20000001_40000000.bam

Am I missing something? Is there another way to ask bcbio to only run with a small sample of reads?
Also, despite specifying -n 48 originally, each of these alignments seemed like they were being performed serially.

Anyways, I just changed the split size to something small and re-ran. Here is a gist:
https://gist.github.com/funnell/a27fc91196e75fdb6beb

This seems to be related to #936. In novoalign.py, the tobam_cl part of
cmd = cmd.format(**locals()) + tobam_cl

contains {out_file}. However, the checking that is giving me the error is looking for tx_out_file. I suppose one possible fix would be to replace {out_file} with {tx_out_file} in the output from tobam_cl. But I'm not sure if this should be done in tobam_cl, or as a string replacement in the novoalign file, or maybe the tx_out_file checking should be changed to out_file checking... I hope you can give some guidance.

From this commit, it looks like the command string should contain {tx_out_file}
https://github.com/chapmanb/bcbio-nextgen/commit/0358f5fe2b6bbd5450ac520cae540d951e4c7db1

Tyler;
Thanks for the detailed report and the fixes. I pushed some additional changes which clean up the header as well, so if you update with bcbio_nextgen.py upgrade -u development it should pull these in and hopefully work cleanly now. Apologies for all the issues with novoalign, I should have tested this better after the latest round of refactoring. We primarily use bwa so it hadn't gotten as much love.
As an aside, you'll want to have a license for novoalign if you're planning to use it. I'm not sure if your example is just from a test machine without a license, but the logs indicate you're using the unlicensed version. That is limited to a single core so will be pretty slow to run.
Thanks again for the patience and hope this fixes everything for you.


Overlay data source does not support 'configurations' directive.

Hi,
I've noticed that the kustomization_overlay data source does not support the Kustomize configurations directive, which would be used to allow specifying varReferences. This is particularly useful as vars only works with a subset of native Kubernetes resources out of the box. In order to be able to use vars with kinds for things like Istio, we'd need to add a varReference spec in a configuration yaml and then specify that in the configurations section.

I just remembered I did not implement configurations on purpose, because it's incompatible with plugins. It's also not documented here: https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/ So I assume it may be deprecated. I removed the good first issue label accordingly. This would probably require a deeper investigation first.

Closing this, since there hasn't been any activity for a month.


pyproject.toml: Add repository url

Add missing project link to PyPi.

Thanks!

Won't release a new version for this change, so it will show up in the next release

Would You also like to add
homepage = "https://securitylabs.datadoghq.com/articles/guarddog-identify-malicious-pypi-packages/"
and
documentation = "https://github.com/DataDog/guarddog"
?
https://python-poetry.org/docs/pyproject/#homepage

The homepage should still be the GitHub repository. And I think people can easily figure out where to find docs from the GitHub repository


Add event that is emitted to component on sticky

There is currently a class added (sticky-top or sticky-bottom) on the element when stickiness is activated but it would be great to be able to catch an event in the parent component also. Is this possible or likely to be added?

There is a PR open for this: #12 .


Add a Windows theme

We can follow https://docs.microsoft.com/en-us/windows/uwp/design/

Done #20


Explicitly call python found in system

Some users are unable to run the installer because the line 124 in install.sh:
ROOTDIR=$(python -c "from pathlib import Path; print(Path('${ROOTDIR}').expanduser().resolve())")
expects an executable in the path named python, or else it will fatally crash.
Some users have python installed as python3 on their systems and not simply python, thus causing the error.
Prior sections of the installer script already find the full path to a user's python executable in a variable called $PYTHON, so this change simply adds that discovered python in place of the hard-coded python call.
This will fix #2166

hi, im new to this I am getting the same issue and I don't understand what it is im suppose to do? and I suppose to copy paste something to line 124?

I changed line 124 to python3, and it still doesn't work.
line 124: python3: unbound variable

I changed line 124 to python3, and it still doesn't work the same as well ...


[feat] @sveltejs/environment

Banish import.meta.env from our codebase so that @sveltejs/kit works without bundling
Fixes https://github.com/vitest-dev/vitest/issues/2298 and a ton of other issues I've seen like this around the ecosystem
We should get users to use this directly or get svelte-package to replace import { DEV, SSR } from '@sveltejs/kit' with imports from this package. That will make packages built with svelte-package work for the whole Svelte ecosystem and not just in SvelteKit or Vite projects.

this is neat!  can we rely on browser and development conditions in exports maps to always be correctly resolved.
As long as it happens in the vite build step i think that is the case, but what about edge runtimes, do they always get output of vite or another bundler? or would there be a point where we have to rely on them to do the right thing with these conditions?

using !browser for ssr a good step for compatibility :+1:   otherwise node vs deno vs x would be playing catchup.

what about edge runtimes, do they always get output of vite or another bundler?

Yes. If they weren't then the code currently in main wouldn't work since those environments wouldn't know how to handle import.meta.env either

Thanks! I wasn't aware of __SVELTEKIT_DEV__. I've replaced it as well. However, doing so causes two tests to fail that I believe is due to a bug that Rich discovered in Vite 3 (https://github.com/vitejs/vite/issues/9203). I fixed it for Vite 4, so after we upgrade, I'll update this branch against master and I imagine those tests should start passing. I'll mark this as a draft until then


[BUG] Getting ld errors with very old GCC versions

Describe the bug
using the ./a.out option with very old GCC versions (4.1.2 through 4.5.3) gives linker errors "/usr/bin/ld: cannot find crti.o: No such file or directory"
Expected behavior
The code should link as it does in later versions (see link)
Link
https://godbolt.org/z/zh5ljl

Duplicate of https://github.com/mattgodbolt/compiler-explorer/issues/1414


Error with version beta 17

error when starting dev server:
Error [ERR_REQUIRE_ESM]: require() of ES Module .../node_modules/chalk/source/index.js from .../node_modules/vite-plugin-laravel/dist/index.cjs not supported.
Instead change the require of index.js in .../node_modules/vite-plugin-laravel/dist/index.cjs to a dynamic import() which is available in all CommonJS modules.

Thanks! Should be fixed by https://github.com/innocenzi/laravel-vite/commit/601480c7746ba07ab40d967fa33dbae693454435, feel free to reopen if it's failing after beta 18.


Devl/dynamic topo

Adds CLI commands to add/delete topology elements

I don't think this is quite the right way to do this.
It should almost certainly be handled in the Link and Intf classes. Then the code in Mininet should be trivial.

Also, does this replace #401 ?

oops, I forgot about #401. It could either replace it or abandon this one.


Update business readiness rake task screenshots

@barrucadu The tag_metadata task is still being used, so I think we should keep the screenshot.

The screenshot is still there, github just displays the diff a bit unhelpfully - click "View file"


Out Of Memory crash when running Minecraft 1.12.2 modpack with 8 GB RAM

latest.log

Resolved here https://github.com/LoliKingdom/LoliASM/issues/152


Calling two API's in the same time

Hi,
I have two API calls in the componentDidMount(). I want to wait until they are all finished before component mounts in. Is there efficient way to do it ? is there something like Promise.all() available?
Thanks,
Pawel

Sure you can! Something like this should work in componentDidMount:
Promise.all([
  dispatch(requestCreatorOne()),
  dispatch(requestCreatorTwo())
]).then(results) => {
  if(results.some(r => r.error)) {
   // If there are any errors in the response, you could trigger an error path like so
   dispatch(componentFetchError())
   // OR by connecting the component to relevant redux store properties set by the request actions
  } else {
   // Otherwise, signal the UI that it should proceed
   dispatch(componentFetchSuccess())
    // OR connect your component to redux state set by the request actions
  }
})

Let me know if that helps!


Why set momentum = 0 in lstm_bucketing example

I find in lstm_bucketing example, https://github.com/dmlc/mxnet/blob/master/example/rnn/lstm_bucketing.py#L29, momentum is set to zero.
Seems momentum is always set to numbers close to 1 (e.g. 0.9).
Why use 0.0 here.
I find this problem because I want to use lstm to to sentiment classification, and find momentum = 0 can not converge, but 0.9 can converge.
@antinucleon

seems momentum = 0 means do not use momentum.


Typescript typings issue with Button component prop in combination with certain other props (like varient)

I am trying to follow along with https://material-ui.com/components/buttons/#third-party-routing-library and leveraging the nextjs-with-typescript example from material-ui.  It appears that in some cases TypeScript has issues with certain combinations of properties.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

It feels very similair to https://github.com/mui-org/material-ui/issues/16846 but that issue has been closed...

Current Behavior 😯

I've made two changes from https://github.com/mui-org/material-ui/tree/master/examples/nextjs-with-typescript to demonstrate the expected behavior and the bug.

In pages/about.tsx, on lines 17-19, I've replaced the Link component with a Button using the component={Link} prop as mentioned in the third-party-routing-library guide. I have also added a variant="outlined" prop to style the button, which causes TypeScript to throw this error:

No overload matches this call.
  Overload 1 of 3, '(props: { href: string; } & { children?: ReactNode; color?: "inherit" | "default" | "primary" | "secondary" | undefined; disabled?: boolean | undefined; disableElevation?: boolean | undefined; ... 6 more ...; variant?: "text" | ... 2 more ... | undefined; } & { ...; } & CommonProps<...> & Pick<...>): Element', gave the following error.
    Type '{ children: string; component: ForwardRefExoticComponent<Pick<LinkProps, "slot" | "style" | "title" | "className" | "classes" | "innerRef" | "key" | "defaultChecked" | "defaultValue" | "suppressContentEditableWarning" | ... 272 more ... | "prefetch"> & RefAttributes<...>>; href: string; variant: "outlined"; }' is not assignable to type 'IntrinsicAttributes & { href: string; } & { children?: ReactNode; color?: "inherit" | "default" | "primary" | "secondary" | undefined; disabled?: boolean | undefined; ... 7 more ...; variant?: "text" | ... 2 more ... | undefined; } & { ...; } & CommonProps<...> & Pick<...>'.
      Property 'component' does not exist on type 'IntrinsicAttributes & { href: string; } & { children?: ReactNode; color?: "inherit" | "default" | "primary" | "secondary" | undefined; disabled?: boolean | undefined; ... 7 more ...; variant?: "text" | ... 2 more ... | undefined; } & { ...; } & CommonProps<...> & Pick<...>'.
  Overload 2 of 3, '(props: { component: ForwardRefExoticComponent<Pick<LinkProps, "slot" | "style" | "title" | "className" | "classes" | "innerRef" | "key" | "defaultChecked" | "defaultValue" | "suppressContentEditableWarning" | ... 272 more ... | "prefetch"> & RefAttributes<...>>; } & { ...; } & { ...; } & CommonProps<...> & Pick<...>): Element', gave the following error.
    Type 'string' is not assignable to type 'undefined'.
  Overload 3 of 3, '(props: DefaultComponentProps<ExtendButtonBaseTypeMap<ButtonTypeMap<{}, "button">>>): Element', gave the following error.
    Type '{ children: string; component: ForwardRefExoticComponent<Pick<LinkProps, "slot" | "style" | "title" | "className" | "classes" | "innerRef" | "key" | "defaultChecked" | "defaultValue" | "suppressContentEditableWarning" | ... 272 more ... | "prefetch"> & RefAttributes<...>>; href: string; variant: "outlined"; }' is not assignable to type 'IntrinsicAttributes & { children?: ReactNode; color?: "inherit" | "default" | "primary" | "secondary" | undefined; disabled?: boolean | undefined; ... 7 more ...; variant?: "text" | ... 2 more ... | undefined; } & { ...; } & CommonProps<...> & Pick<...>'.
      Property 'component' does not exist on type 'IntrinsicAttributes & { children?: ReactNode; color?: "inherit" | "default" | "primary" | "secondary" | undefined; disabled?: boolean | undefined; ... 7 more ...; variant?: "text" | ... 2 more ... | undefined; } & { ...; } & CommonProps<...> & Pick<...>'.ts(2769)
Button.d.ts(55, 5): The expected type comes from property 'variant' which is declared here on type 'IntrinsicAttributes & { component: ForwardRefExoticComponent<Pick<LinkProps, "slot" | "style" | "title" | "className" | "classes" | "innerRef" | "key" | "defaultChecked" | ... 274 more ... | "prefetch"> & RefAttributes<...>>; } & { ...; } & { ...; } & CommonProps<...> & Pick<...>'

Expected Behavior 🤔

In pages/index.tsx I've made the same change but instead of using variant="outlined", I've used color="secondary" and everything works as expected.

Steps to Reproduce 🕹

Refer to this codesandbox for a reproduction of the bug: https://codesandbox.io/s/bold-water-9xdld?file=/pages/about.tsx
Context 🔦

I'm guessing this is a silly TypeScript issue (I'm still learning and appreciate the value but also get frustrated by silly things like this).  I want to be able to use the full power of buttons and not just certain combinations so this is blocking me.  Other workarounds I've tried have various drawbacks as well..
Your Environment 🌎

Tech
Version

Material-UI
v4.11.0

React
v16.13.1

TypeScript
v4.0.2 (see codesandbox for .tsconfig)

Next.js
v9.5.3

This was fixed in #21552 which is available in<EMAIL_ADDRESS>We will not backport this fix to v4.

👍


Channel stuck at "WAIT_FOR_FUNDING_CONFIRMED" when transaction was not broadcasted.

The Electrum server was offline when I tried to open a channel.
The other node was cooperative in opening the channel, but the signed smart contract was
eventually never sent to the bitcoin network, so it never arrived in the mempool.
Now the channel is stuck in WAIT_FOR_FUNDING_CONFIRMED forever.
The only thing you can do is force-closing it.
There should be a re-broadcast feature for the transaction to open the channel.
That could be automated, but a manual option would be sufficient as a quick fix here.

What makes you think that the tx was never sent to the bitcoin network ?
Do you see it in the Transaction History tab ?
Eclair normally does not let you open a channel if it is not connected to an electrum server, and does not transition to WAIT_FOR_FUNDING_CONFIRMED if there was en error when it tried to publish the funding tx. So here, the only option that is really safe is to wait and see if it will eventually be confirmed.

What made me believe that something went wrong on broadcasting the funding tx is that I opened the the channel details, scrolled all the way down to the Transaction ID and tapped on "Open in Explorer". The blockchain explorer would tell me that the transaction was not found; even after an hour now.
The transaction hash is: e9a4259f7e0f8ca390b4999f25ce7c7802f138a56b68872d7607329841ad73a4

There's nothing in the transaction list that relates to that issue. This is just about opening the channel, so I would not try to use it for LN transactions yet

You mean it is not there ? In the transaction history you should see both regular onchain transactions and LN transactions, and your funding tx should be there, with a negative amount in red, and "0 conf" written just below.

I just opened two more payment channels to check; and indeed, they would show up as on-chain tx with 0 confirmations. But the tx in question did not show up there.
Since I got the feeling the channel would never open, I decided to force-close it. Now it's waiting to close (uncooperative). I wonder how that works when it cannot address the original smart contract.

I wonder how that works when it cannot address the original smart contract.

If the funding tx is never confirmed then your commit tx will also never confirm and the channel will remain this way.
If the funding tx was never published then it won't show in your onchain balance (displayed with a small bitcoin icon). But we must be sure that it will never be published (we may have a bug somewhere, but we should assume that it did reach the bitcoin network and was not relayed, which does not mean that it will never be. Onchain fees have gone up a lot recently and it may explain why your tx does not show).

I believe that this is not an issue about the tx fees. If the fees were too low, than it would at least land in the mempool and the blockexplorer would report "blockheight: -1" for the transaction hash. However, the transaction hash seems to be unknown to the two block explorer that I checked.
So, if the transaction was actually sent out, it never actually reached the mempool of the miners.
I suspect that the Electrum Server was maybe rebooting when my client sent the funding tx.
If that was the case, then this issue can be fixed by checking if the tx hash is known to a blockexplorer, and if not, then the tx gets re-broadcasted.
Afaik, nothing can go wrong with that approach.

Yes but afaict the tx was sent to an electrum server which did replied that it was broadcast without errors. What I don't understand yet is why it does not show in your list, which would mean that our electrum server does not know about it ??
But you're right, even if it's a corner case we need to find a way to address it, and allowing users to rebroadcast the tx is a potential solution.

Well, the only thing I can add here is that I noticed that my app seemed to have problems with the connection to the electrum server and eventually connected to another one.
Somewhere in between the funding tx was not properly handled.
I notice that it hops between the servers testnet.hsmiths.com and testnet1.bauerj.eu.

We try to keep a pool of at least 3 electrumx connections, one of them our master, and switch when it falls behind or is disconnected. You may be right: your master server failed, and we switched to another one that never saw the funding tx. What is really bad here is that before it failed it told us that the tx was broadcasted without errors and it was not. Unfortunately electrumx servers are much less reliable on testnet that on mainnet, and there are less of them (testnet is also "harder" : huge reorgs, unpredictable intervals between blocks, spikes in fee rates, ... which is good for testing).

I have the same problem on the mainnet. Channel is stuck in WAIT_FOR_FUNDING_CONFIRMED state forever, the funding transaction never made it to the mempool. The transaction is not shown in the Transaction history tab. The wallet shows wrong total balance 4,9mBTC, but I only sent 2,5mBTC to Eclair. It shows the bitcoin in both the on-chain balance and the lightning balance.
One more info, I initialized the wallet with an existing 12 words seed.

@sstone I have the same problem on the mainnet and here is another same issue #43. I believe this is a serious issue because our funds are tied up and it seems to never get back unless this issue is fixed. If eclair-wallet stores the raw funding transaction, we could manually rebroadcast it to network.

After I chose to close the failed channel the funds were released and I successfully opened another channel. No loss of btc occurred. The failed channel is stuck in CLOSING (uncooperative) state forever.

@kozo-cz In this issue #43 , it cannot close channel because funding transaction was never broadcast, AND the funds in funding transaction has not been released.
How were the funds released even if the failed channel is stuck in CLOSING state?

My funding tx was not broadcast either. I noticed that the failed channel didn't deduct btc from the on-chain balance. So the funds were not locked probably. Do you see the Close option for the failed channel? What is your on-chain balance?

@kozo-cz Yes, I know what you mean. When I looked into the outpoint where the funding tx tried to spend, the output is still spendable. However, the channel is stuck in CLOSING state, so that amount of BTC that I tried to open a channel with doesn't go to neither off-chain nor on-chain in eclair wallet. This is the problem here.

I think I'm having a similar issue. I have a channel that's been stuck on "CLOSING" for 1 day already. The funding transaction was never broadcasted and the UTXO that was meant to fund it was later spent into succesfully opening another channel, but it's still trying to close the first one. I'm using ECLAIR 0.2-beta8 and it's kind of annoying to have that stale channel in my channels list.

This is addressed by https://github.com/ACINQ/eclair/pull/714

However, the channel is stuck in CLOSING state, so that amount of BTC that I tried to open a channel with doesn't go to neither off-chain nor on-chain in eclair wallet. This is the problem here.

No, this doesn't affect the funds, they can still be spent on an other on-chain transaction or channel opening. This is only visually annoying, there is no other consequence to the best of our knowledge.


PS1 emulation on cosmic emu

Will the emulator have support for ps1 emulation ? and if yes, will it support certain titles or the majority of it ? Just asking out of curiosity
Some other ps2 emulators do have support for ps1 emulation but it is buggy, incomplete or there is no support at all

This project focuses exclusively on PS2 games but if I, for miracle developer a better SIF than the actual PCSX2 dudes certain will run a lot of PS1 games also
All the graphic engine is emulated by software in EE when the PS1 mode is activated...


"TypeError: Boolean value of this clause is not defined" with Enum column

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the SQLModel documentation, with the integrated search.
[X] I already searched in Google "How to X in SQLModel" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to SQLModel but to Pydantic.
[X] I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from enum import Enum
from typing import Optional
from uuid import UUID

from sqlmodel import Column, SQLModel, Field
from sqlmodel import Enum as EnumField

class LocationType(str, Enum):
    A = "A"
    B = "B"
    C = "C"

class Location(SQLModel, table=True):
    __tablename__ = "locations"
    __table_args__ = {"schema": "my_schema"}
    uuid: Optional[UUID] = Field(default=None, primary_key=True)
    location_type: LocationType = Column(EnumField(LocationType))
    name: str
    description: str
    x: int
    y: int
    z: int
    additional_info: Optional[str] = None

Description

Create a LocationType Enum that allows three types of location (e.g. "A", "B", "C")
Create a Location model with a location_type Column
The following error appears:

Traceback (most recent call last):
  File "/Users/manchineel/Desktop/test.py", line 15, in <module>
    class Location(SQLModel, table=True):
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/sqlmodel/main.py", line 277, in __new__
    new_cls = super().__new__(cls, name, bases, dict_used, **config_kwargs)
  File "pydantic/main.py", line 204, in pydantic.main.ModelMetaclass.__new__
  File "pydantic/fields.py", line 488, in pydantic.fields.ModelField.infer
  File "pydantic/fields.py", line 419, in pydantic.fields.ModelField.__init__
  File "pydantic/fields.py", line 528, in pydantic.fields.ModelField.prepare
  File "pydantic/fields.py", line 552, in pydantic.fields.ModelField._set_default_and_type
  File "pydantic/fields.py", line 422, in pydantic.fields.ModelField.get_default
  File "pydantic/utils.py", line 652, in pydantic.utils.smart_deepcopy
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 589, in __bool__
    raise TypeError("Boolean value of this clause is not defined")
TypeError: Boolean value of this clause is not defined

Maybe I'm doing something completely wrong. How would I set up an Enum column properly?
Operating System
macOS
Operating System Details
12.5 (21G72)
SQLModel Version
0.0.6
Python Version
Python 3.10.2
Additional Context
No response

You should use the Field class to define your fields:
location_type: LocationType = Field(sa_column=EnumField(LocationType))

This worked, thank you!