Fish shell colors broken with latest update

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

VS Code Version:

Version: 1.80.0
Commit: 660393deaaa6d1996740ff4880f1bad43768c814
Date: 2023-07-04T13:40:17.963Z (1 wk ago)
Electron: 22.3.14
ElectronBuildId: 21893604
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0

OS Version: MacOS 12.6.2 (21G320)

Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
set_color: Unknown color 'py[learning]'
set_color: Unknown color '~/r/v/requests-frontend'
set_color: Unknown color 'py[learning]'
set_color: Unknown color '~/r/v/requests-frontend'
set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '
set_color: Unknown color '~/r/v/requests-frontend'
set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '
set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '

fish -v
fish, version 3.6.1

Can you try enabling trace logging mode (F1 > Set Log Level > Trace) and pasting in the content from the "Terminal" channel in the Output panel? This will tell us what the shell process is telling the terminal to do which will identify whether it's an issue with rendering or the process telling us the wrong thing.
/label "info-needed"

2023-07-14 10:57:19.482 [trace] terminalMultiLineLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:19.482 [trace] terminalLocalLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:19.482 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.483 [trace] terminalMultiLineLinkDetector#detect text ["Type help for instructions on how to use fish"]
2023-07-14 10:57:19.483 [trace] terminalLocalLinkDetector#detect text ["Type help for instructions on how to use fish"]
2023-07-14 10:57:19.483 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.485 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.485 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.485 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.492 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:19.492 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:19.493 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:19.493 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:19.501 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.501 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.501 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.509 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:19.509 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:19.509 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:19.509 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:19.518 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.518 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.518 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.534 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.534 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.534 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.543 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.543 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:19.543 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:19.560 [trace] terminalMultiLineLinkDetector#detect text ["    set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.560 [trace] terminalLocalLinkDetector#detect text ["    set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:19.560 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:20.851 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:20.851 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:20.851 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:20.886 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:20.886 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:20.887 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:21.172 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.172 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.173 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:21.173 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:21.192 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:21.192 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:21.192 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:21.217 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.218 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.218 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:21.218 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:21.234 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:21.234 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:21.234 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:21.261 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.261 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:21.261 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:21.261 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:21.496 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:21.496 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:21.497 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:21.518 [trace] terminalMultiLineLinkDetector#detect text ["Type help for instructions on how to use fish"]
2023-07-14 10:57:21.518 [trace] terminalLocalLinkDetector#detect text ["Type help for instructions on how to use fish"]
2023-07-14 10:57:21.519 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:21.543 [trace] terminalMultiLineLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:21.544 [trace] terminalLocalLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:21.544 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:22.162 [trace] terminalInstance#dispose (instanceId: 1) []
2023-07-14 10:57:22.209 [debug] Terminal process exit ["instanceId",1,"code",null,"processState",5]
2023-07-14 10:57:23.522 [trace] terminalInstance#ctor (instanceId: 2) [{}]
2023-07-14 10:57:23.536 [debug] Unbinding from mouse events. []
2023-07-14 10:57:23.539 [debug] Buffer content tracker: [0," lines cached"]
2023-07-14 10:57:23.539 [debug] Viewport content update complete,  [0," lines in the viewport"]
2023-07-14 10:57:23.539 [debug] Buffer content tracker: set  [0," lines"]
2023-07-14 10:57:23.559 [trace] Webgl was loaded []
2023-07-14 10:57:23.633 [debug] Buffer content tracker: [0," lines cached"]
2023-07-14 10:57:23.633 [debug] Viewport content update complete,  [0," lines in the viewport"]
2023-07-14 10:57:23.633 [debug] Buffer content tracker: set  [0," lines"]
2023-07-14 10:57:23.637 [debug] terminalInstance added capability [1]
2023-07-14 10:57:23.667 [debug] Terminal process ready (shellProcessId: 57690) []
2023-07-14 10:57:23.667 [debug] terminalInstance added capability [3]
2023-07-14 10:57:24.548 [debug] parsing data "Welcome to fish, the friendly interactive shell
Type help(B for instructions on how to use fish
" [[87,101,108,99,111,109,101,32,116,111,32,102,105,115,104,44,32,116,104,101,32,102,114,105,101,110,100,108,121,32,105,110,116,101,114,97,99,116,105,118,101,32,115,104,101,108,108,13,10,84,121,112,101,32,27,91,51,50,109,104,101,108,112,27,40,66,27,91,109,32,102,111,114,32,105,110,115,116,114,117,99,116,105,111,110,115,32,111,110,32,104,111,119,32,116,111,32,117,115,101,32,102,105,115,104,13,10]]
2023-07-14 10:57:24.554 [debug] parsing data "" [[27,91,63,50,48,48,52,104]]
2023-07-14 10:57:24.554 [debug] parsing data "]633;P;Cwd=/Users/gkatsanos/repos/visable/requests-frontend" [[27,93,54,51,51,59,80,59,67,119,100,61,47,85,115,101,114,115,47,103,107,97,116,115,97,110,111,115,47,114,101,112,111,115,47,118,105,115,97,98,108,101,47,114,101,113,117,101,115,116,115,45,102,114,111,110,116,101,110,100,7]]
2023-07-14 10:57:24.554 [debug] terminalInstance added capability [0]
2023-07-14 10:57:24.555 [debug] parsing data "]633;D" [[27,93,54,51,51,59,68,7]]
2023-07-14 10:57:24.555 [debug] terminalInstance added capability [2]
2023-07-14 10:57:24.556 [debug] CommandDetectionCapability#handleCommandFinished [0,2,null,{"commandFinishedMarker":{"line":2,"isDisposed":false,"_disposables":[{"_listeners":[null],"_disposed":false},{},{},{},{}],"_id":11,"_onDispose":{"_listeners":[null],"_disposed":false}}}]
2023-07-14 10:57:24.645 [debug] parsing data "set_color: Unknown color 'py[learning]'
" [[115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,112,121,91,108,101,97,114,110,105,110,103,93,39,13,10]]
2023-07-14 10:57:24.646 [debug] parsing data "set_color: Unknown color '~/r/v/requests-frontend'
set_color: Unknown color 'py[learning]'
" [[115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,126,47,114,47,118,47,114,101,113,117,101,115,116,115,45,102,114,111,110,116,101,110,100,39,13,10,115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,112,121,91,108,101,97,114,110,105,110,103,93,39,13,10]]
2023-07-14 10:57:24.646 [debug] parsing data "set_color: Unknown color '~/r/v/requests-frontend'
" [[115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,126,47,114,47,118,47,114,101,113,117,101,115,116,115,45,102,114,111,110,116,101,110,100,39,13,10]]
2023-07-14 10:57:24.692 [debug] parsing data "set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '
set_color: Unknown color '~/r/v/requests-frontend'
set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '
" [[115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,57504,32,69,88,80,76,45,51,50,57,49,45,105,109,112,108,101,109,101,110,116,105,110,103,45,69,80,45,108,97,110,100,105,110,103,45,112,97,103,101,32,39,13,10,115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,126,47,114,47,118,47,114,101,113,117,101,115,116,115,45,102,114,111,110,116,101,110,100,39,13,10,115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,57504,32,69,88,80,76,45,51,50,57,49,45,105,109,112,108,101,109,101,110,116,105,110,103,45,69,80,45,108,97,110,100,105,110,103,45,112,97,103,101,32,39,13,10]]
2023-07-14 10:57:24.692 [debug] parsing data "set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '
" [[115,101,116,95,99,111,108,111,114,58,32,85,110,107,110,111,119,110,32,99,111,108,111,114,32,39,57504,32,69,88,80,76,45,51,50,57,49,45,105,109,112,108,101,109,101,110,116,105,110,103,45,69,80,45,108,97,110,100,105,110,103,45,112,97,103,101,32,39,13,10]]
2023-07-14 10:57:24.693 [debug] parsing data "]0;~/r/v/requests-frontend(B
" [[27,93,48,59,126,47,114,47,118,47,114,101,113,117,101,115,116,115,45,102,114,111,110,116,101,110,100,7,27,91,51,48,109,27,40,66,27,91,109,13]]
2023-07-14 10:57:24.693 [debug] parsing data "]633;A(B  (B (B(B (B]633;B
" [[27,93,54,51,51,59,65,7,27,40,66,27,91,109,32,32,27,40,66,27,91,109,32,27,40,66,27,91,109,27,40,66,27,91,109,32,27,40,66,27,91,109,27,93,54,51,51,59,66,7,27,91,75,13,27,91,52,67]]
2023-07-14 10:57:24.693 [debug] CommandDetectionCapability#handlePromptStart [0,10]
2023-07-14 10:57:24.694 [debug] CommandDetectionCapability#handleCommandStart [4,10]
2023-07-14 10:57:25.328 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:25.330 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:25.330 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:25.387 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:25.388 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:25.388 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:25.878 [trace] terminalMultiLineLinkDetector#detect text ["    "]
2023-07-14 10:57:25.878 [trace] terminalLocalLinkDetector#detect text ["    "]
2023-07-14 10:57:25.879 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:26.840 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.840 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.840 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:26.856 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.856 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.857 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:26.873 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.873 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.873 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:26.873 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:26.889 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.890 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color ' EXPL-3291-implementing-EP-landing-page '"]
2023-07-14 10:57:26.890 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:26.906 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.906 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.906 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:26.907 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:26.924 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:26.924 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:26.924 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:26.941 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.941 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color '~/r/v/requests-frontend'"]
2023-07-14 10:57:26.941 [trace] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":26,"text":"~/r/v/requests-frontend"}}]]
2023-07-14 10:57:26.941 [trace] terminalLocalLinkDetector#detect linkCandidates [["~/r/v/requests-frontend"]]
2023-07-14 10:57:26.987 [trace] terminalMultiLineLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:26.987 [trace] terminalLocalLinkDetector#detect text ["set_color: Unknown color 'py[learning]'"]
2023-07-14 10:57:26.987 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]
2023-07-14 10:57:28.423 [trace] terminalMultiLineLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:28.423 [trace] terminalLocalLinkDetector#detect text ["Welcome to fish, the friendly interactive shell"]
2023-07-14 10:57:28.424 [trace] terminalLocalLinkDetector#detect parsedLinks [[]]

at your service!

I'm facing this exact same issue and I've managed to pinpoint the fish commands that cause the issue. This doesn't really have anything to do with the colours themselves but rather variable scoping.
Personally I'm using the agnoster theme and I'm assuming @gkatsanos is using something similar. The prompt function calls a bunch of functions like these:
function prompt_dir -d "Display the current directory"
  prompt_segment $color_dir_bg $color_dir_str (prompt_pwd)
end

And through experimentation I found that $color_dir_bg is not set when I'm in the VS Code terminal, leading prompt_segment to interpret the PWD as a color, which is what gives the error. These color variables were supposed to be set earlier in the script:
set -q color_user_bg; or set color_user_bg black
set -q color_user_str; or set color_user_str yellow
set -q color_dir_bg; or set color_dir_bg blue
set -q color_dir_str; or set color_dir_str black
# ...

I think it has something to do with scoping since one workaround I found was to change all the set color_* to set -g color_. So for some reason, a plain set without global scoping doesn't make the variables available to the other functions in the script when in the VS Code terminal.

Same problem for me, started immediately after the latest upgrade on MacOS (Monterey 12.5), MacBook Pro M1 machine. Is there a way to revert to a previous version?

@tylertian123 does disabling shell integration workaround the issue?
"terminal.integrated.shellIntegration.enabled": false

@Tyriar Yes, the issue seems to disappear if shell integration is turned off.
@eblumstengel-dbkg I also tried running omf update and that solved my issue as well. I'm using the agnoster theme myself. There is apparently a commit in the theme at https://github.com/oh-my-fish/theme-agnoster/commit/0262111883b47cd09fb08dec65beeef8657936d4 which adds the -g flags exactly like the workaround I found. The commit message mentions something about the theme being wrapped by other scripts and so the variables get declared in a different scope.
By the way my version info is exactly the same as @eblumstengel-dbkg except I'm on Ubuntu 20.04, Linux 5.15.0-76-generic.

I am having the same issue on macOS with Fish shell.
 set_color: Unknown color '...'
set_color: Unknown color ' ... 📁'
set_color: Unknown color '...'
set_color: Unknown color ' ... 📁'

@kelvinthh I fixed it by uninstalling and reinstalling my omf theme. https://github.com/oh-my-fish/oh-my-fish#omf-remove-name.

Thanks @tylertian123 for looking into this. As mentioned in their comment you should update your fish packages with omf update which will set certain variables as global which will work correctly when fish_prompt gets wrapped.


add_reader/add_writer/remove_writer crash when using not using Pycopy, as otherwise required by README

Hi,
not sure if this belongs in Picoweb or in uasyncio - but when I try to run the example webserver I get the following crashlog:
Traceback (most recent call last):
  File "main.py", line 30, in <module>
  File "/lib/picoweb/__init__.py", line 298, in run
  File "/lib/uasyncio/core.py", line 155, in run_forever
  File "/lib/uasyncio/core.py", line 130, in run_forever
  File "/lib/uasyncio/__init__.py", line 60, in remove_writer
  TypeError: function takes 2 positional arguments but 3 were given

The webserver code isn't anything special, just wait for WiFi and host an app; both a route and a static folder.
I tried upip.install as well as copy & past the latest Picoweb, uasyncio & uasyncio.core from the Github repos.

The traceback you posted is cut off, and doesn't show what error happens. But likely, you need to use https://github.com/pfalcon/micropython , as the README suggests.

The traceback you posted is cut off, and doesn't show what error happens.
Ah yes, sorry! Fixed in the original description.

I'll give your suggestion a try to see if that fixes the issue.

I can confirm the issue and also that it's gone when applying @ernstnaezer's fix

it seems to go wrong on the last line of remove_writer:

It doesn't go wrong, it goes right. That's a recent fix applied for uasyncio to work under different circumstances, and efficiently: https://github.com/pfalcon/micropython-lib/commit/4f70217e4fce6a6ca3c50ea8552a8ec094af0d34
Once again, that requires up to date MicroPython, from https://github.com/pfalcon/micropython , as specified in the README. Corresponding patch was submitted upstream long ago too: https://github.com/micropython/micropython/pull/4217

I just built micropython from git using the AUR and this error still seems to be there? Using the non-git version I don't have access to ussl, so I don't have upip.
I can chalk a certain amount up to just archlinux weirdness, I suppose that's just a problem with source packages sometimes. But still, it's odd.

People writing, or intended to write, here should instead go to https://github.com/micropython/micropython/pull/4217 and let the maintainers of that repo know that that unmerged patch causes them unneeded complications.

Hi,
I’ll try to write here because I think the problem that I'm having using Picoweb is similar to that described in this thread.
My test is done on the ESP32 module and I’m using the uPithon ver. 1.11 with the Picoweb and Uasyncio Ulogging,  taken from pfalcon/Picoweb and pfalcon/pcopy-lib. As soon as I lunch the webserver example I have this output:
exec(open('./picoTest.py').read(),globals())
[0;32mI (81912) modsocket: Initializing [0m

Running on picoweb/, in run_fo "/lib/uasyncio/init.py", line 31, in add_reader
TypeError: function expected at most 3 arguments, got 4

At line 31 of uasyncio we have:
self.poller.register(sock, select.POLLIN, cb)
I’d like to try to build the Pcopy executable but I think that it is a bit over my head; thank you in advance for any suggestion.

The suggestion is to read README: https://github.com/pfalcon/picoweb/blob/master/README.rst, which states clearly that yes, Pycopy (https://github.com/pfalcon/pycopy) is required for Picoweb, as Picoweb is part of the Pycopy project (https://github.com/topics/pycopy).

Hi, thank you for the prompt replay, summarizing, at this time there is not a workaround to run Picoweb with  uPython (some month ago this option was possible) the suggested way is to build the Pcopy binary.

As the author of both Pycopy and Picoweb, I intend Picoweb to be run with Pycopy, and I don't have resources to support other implementations. (Except for CPython, it's on my TODO to make Picoweb run there, by implementing set of Pycopy-compatible APIs for CPython.)

Ok all clear, thank you @pfalcon .
Anybody here can share resources to make picoweb WORKING again for ESP32 boards?
Thanks to all,
m

@mauroesposito Picoweb is working on ESP32 boards. You just have to swap the base uPython. Picoweb is working with @pfalcon s uPython implementation named "Pycopy" it is based on Micropython as he was a long contributer to the project... (whole story in Pycopy FAQ).
So, if you need it, change from Micropython to Pycopy that's it.

Thank you @mrwhy-orig ,  in this moment I've no time to setup all for build: and until now, I believed that somewhere was possible found a *.bin ready to flash on the chip, nothing else.

@pfalcon I can imagine you are sad or angry that micropython didn't take over your suggestion according asyncio. But to me and probably others, it's too great a risk and too much work to switch to an alternative for the micropython framework with a much smaller userbase, as opposed to the widely used and supported "official" micropython.
I took the chance, and it seems at least on today, I can use picoweb's great features just as easily with the slightly less perfect but de facto standard uasyncio (upip.install('uasyncio')).
@pfalcon Your picoweb is a wonderful and very elegant solution for those wanting to serve web pages (like me). I think it would greatly expand the user base of your software if you let people have the choice of which asyncio variant people use (your more perfected version, or the default micropython one) instead of pushing them into the pycopy direction. You could even point it out clearly in the documentation that you greatly recommend your implementation, and why.

@zeekoe: Let me be short and simple: if you would like to hire me to perform some work, certainly feel free to send your offer. If you not, feel free to use my works, in accordance with its licensing terms, which in particular require recognizing and upholding my copyright and authorship. In that regard, I've written the original uasyncio and picoweb, and I continue to maintain them, according to my approach and ability.
I'm sorry to hear that other projects cause your confusion. When I decided to go with my own MicroPython fork, the project initially was called "micropython-pfalcon", but I got a suggestion to rename it, and with that being a reasonable suggestion, I followed it and renamed the project to "Pycopy". I now return this suggestion to other projects which try to use names of my work(s) for their benefit, don't follow the approach of my original projects, don't give proper credit to me, and cause overall confusion in the community - please get some respect and use different names for derivative (or even original) work. For all concerned parties, I would also encourage them to look up definition of https://en.wikipedia.org/wiki/Plagiarism .
With this explanation, please don't come to me with terms like

de facto standard uasyncio (upip.install('uasyncio')).

For that sounds insulting, given that I'm the author of things mentioned there (including upip!), and by any account would be let to decide what they should be/how they should work, with other parties to pay at least the baseline respect for my work.

Hi pfalcon,
I'm sorry if I insulted you - I did not mean to do that in any way. I'm not in the position to hire you, just an enthousiastic hobbyist very happy that a form of python is available on the ESP32 platform.
Thank you for the short history! Things are more clear to me now.
The least I can do then is to express my thanks for your work; upip, too, is a wonderful tool.


An Issue with the desktop app

Jaku everything works great except the fact that the hotkeys will NOT work with the program if it is minimized. It has to be maximized the same time as OBS and be on top of OBS for the hotkeys to work. Has anybody found a work around for this? Possibly docking it? I'm not sure, I ran out of ideas and this seems to be the only place people are talking about this program anymore.

I believe this has always functioned like this. Nothing I did to the application should/would have broken this.
Perhaps an application like auto-hot key can be used in addition to focus on the snap camera input for the hotkeys so it can be activated anywhere?

Yea I knew it had nothing to do with your work on the application, I just was not sure if this has been brought up or if you knew a simple fix. I'll check auto hotkey and hopefully someone reading this knoes of some ideas. Thanks again !!! Excited for the future of this project !!!

No worries, I honestly wasn't sure if it worked before or not, but suspected it didn't.
With AHK, I'm pretty sure the command you are looking for is ControlSend and it lets you set a window to send the keystroke to. Not the best solution but it should in theory work.
Additionally, I am looking to bring back some of the Twitch features they had in an older version, not sure how feasible it is yet, but some of the code is still there.


Add UI Support for AssociatePublicIPAddress

Add UI Support for https://github.com/rancher/rancher/issues/15419. We will need a boolean field associateWorkerNodePublicIp. The field should default to true.  If the field is set to false, then the user must also specify a custom VPC and Subnet(s).

ready to test on master

Version: master 2.2 (11/29/18)
Confirmed new UI feature VPC & Subnet section of EKS config. I tested all the different options in the UI with the radio buttons. I made sure that we can select a custom VPC and that the calls to amazon API went thru correctly and that the UI updates to show the subnets once we pick a VPC. My customized cluster worked without any issues as well as with default options. I made sure I can select multiple subnets as well. Halo testing was also performed.


Some whitespace between two variables inside a slot gets removed

Steps to reproduce

Create a template with a slot
When including the template, put inside the slot two variables with space in between (tried non-breaking space and some other spaces, like em space)
There is no character between the two variable values in the output

What do you expect
I expect any characters between variables to be preserved, including spaces.
Additional info
Putting a linebreak in between the two variables ends up creating/preserving a space between them.
cotton/vartest.html
{{ slot }}

index.html
<!-- var1="one" var2="two" -->
<c-vartest>
{{var1}} {{var2}}
</c-vartest>

Output:
onetwo

Fixed in v0.9.37


Adding locations to expressions

Hey,
I'm currently working on migrating from ppx_tools/metaquot to this one since I can't figure out how to get ppx_tools working with jbuilder.
I've run into an issue where this library doesn't seem to support the @metaloc attribute so I was wondering what you use instead or if it would be possible to add support for it?
I.e. if I currently have this:
[%expr do_some_stuff ] [@metaloc loc]
which creates an expression node and sets its location to be loc, what would I want in ppx_metaquot?
Thanks in advance!

@diml, can you comment on this ?

ppx_metaquot always the variable loc in scope for the location. So [%expr X] [@metaloc loc] is the same as [%expr X]. To do the same as [%expr X] [@metaloc blah], you would need to write:
let loc = blah in
[%expr X]

ppx_metaquot was merged into https://github.com/ocaml-ppx/ppxlib/.
If you have more questions, it should happen there.

Excellent! Thanks for the response! Looks like my code shouldn't need many changes then.


Field, value => rawInputValue

https://github.com/get-focus/focus-redux/issues/39

Rename value property from Form into rawInputValue.
@pierr @Ephrame

This issue was moved to get-focus/focus-components#5


Fix one critical memory leak in main while loop and one small memory leak in save_if_interesting()

Thanks.


fix: LSDV-5031: Adding new region after filter it is not filtered

Hi @robot-ci-heartex!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/1352

/git merge develop


Question - Create new project (within a "Group") using New-GitLabProject

1. Provide a general summary of the issue in the Title above
How do you specify a "group", is it the -Path or -Namespace or something else?
The GitLab visual interface seems to have an entity known as "groups".
When using the online interface, you create projects under groups.
2. Describe Your Environment
Operating System and PowerShell version:
Win 2012/R2
Powershell
Major  Minor  Build  Revision
5         1          14409   1005
3. Expected Behavior
Run some command to create a project in a group
4.Current Behavior
Test 1
$projName = "MyCompany.MyNewProjectName"
$groupName = "ExistingGroupName"
New-GitLabProject -name $projName -path $groupName
Results
WARNING: All tokens will be sent over HTTP. Recommendation: Use HTTPS.
New-GitLabProject : Cannot bind parameter because parameter 'name' is specified more than once. To provide multiple values to parameters that can accept
multiple values, use the array syntax. For example, "-parameter value1,value2,value3".
At line:15 char:35

New-GitLabProject -name $projName -path $groupName

                              ~~~~~

CategoryInfo          : InvalidArgument: (:) [New-GitLabProject], ParameterBindingException
FullyQualifiedErrorId : ParameterAlreadyBound,New-GitLabProject

Test 2
$projName = "MyCompany.MyNewProjectName"
$groupName = "ExistingGroupName"
New-GitLabProject -name $projName -namespace $groupName
Results:
WARNING: All tokens will be sent over HTTP. Recommendation: Use HTTPS.
QueryGitLabAPI :  -
At C:\Program Files (x86)\WindowsPowerShell\Modules\PSGitLab\3.0.1\PSGitLab.psm1:1775 char:9

    QueryGitLabAPI -Request $Request -ObjectType 'GitLab.Project'

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,QueryGitLabAPI

5. Possible Solution
Update doc to link the concept of a group to whatever you call it in the API, assuming it does existin the API.
6. Context
See number 1 above

I don’t have anything around a wiki in the pipeline. You can treat the wiki as a git repository so you should be able to push changes via git.
Close the issue when you’ve seen the reply!
Sent with GitHawk


Integration with vue-formio

I'm currently trying to integrate vue-formio into an existing project which is already using Bootstrap 3.
I've tried several methods to override the form styling with this package but haven't been very successful, could you please provide some advice (or possible documentation) on how this can be integrated with the vue-formio package?

Okay, I found a solution for anyone who hits a similar issue.
import bootstrap3 from "@formio/bootstrap3";

Formio.use(bootstrap3);

Not sure if this is the ideal method, and perhaps someone can confirm/deny whether this is best way of doing it, but it works!


feat(usephoneinput): usePhoneInput supports national format

Closes #
📝 Description

Add a brief description

⛳ Current behavior (updates)

Please describe the current behavior that you are modifying

🚀 New behavior

Please describe the behavior or changes this PR adds

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (df77bac) 100.00% compared to head (7cbdb75) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##            master       #77   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        18    +1
  Lines          309       322   +13
  Branches        83        89    +6
=========================================
+ Hits           309       322   +13

Flag
Coverage Δ

PhoneInput
100.00% <100.00%> (ø)

useBreakpoint
100.00% <ø> (ø)

useClickOutside
100.00% <ø> (ø)

usePreserveInputCaretPosition
100.00% <ø> (ø)

usePrevious
100.00% <ø> (ø)

useSelectionRange
100.00% <ø> (ø)

useToggle
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use a delegate for client callbacks in the CHIP Darwin Framework

Problem
The current API to register callbacks makes the client side code difficult to maintain. i.e, clients end up with inline dispatch blocks while registering the callbacks.
A delegate protocol is much better suited to our needs
Summary of Changes
Added a Delegate Protocol for the CHIPDeviceController and updated CHIPTool to use it.

LGTM

please take a look - @woody-apple @BroderickCarlin @hawk248


Convert src/core/parser.js to ES6 syntax and write more unit tests for the lexer and the parser

I recommend to review each commit with the ?w=1 flag to reduce the size of the diff.

/botio test

/botio unittest


refactor: Better compatibility with multiple templates.

DO NOT MERGE

:books: Documentation preview :books:: https://serious-scaffold-python--235.org.readthedocs.build/en/235/

Close since the branch is too old.


initrd_builder: Create empty resolv.conf in rootfs

Create an empty /etc/resolv.conf in initrd rootfs
so that the agent can bind mount it for DNS in
kata VM.
Fixes: #365
Signed-off-by: Nitesh Konkar<EMAIL_ADDRESS>

/test

I see this error in the CI logs:
04:43:21 Creating image based on rootfs-ubuntu with command: /tmp/jenkins/workspace/kata-containers-osbuilder-ubuntu-16-04-PR/go/src/github.com/kata-containers/osbuilder/image-builder/image_builder.sh -o /tmp/osbuilder-test.TkkiP8o/images/kata-containers-image-ubuntu.img /tmp/osbuilder-test.TkkiP8o/rootfs-osbuilder/ubuntu_rootfs
04:43:54 INFO: Creating container for ubuntu
04:43:54 INFO: running: /tmp/jenkins/workspace/kata-containers-osbuilder-ubuntu-16-04-PR/go/src/github.com/kata-containers/osbuilder/tests/../../tests/cmd/kata-manager/kata-manager.sh reset-config
04:43:54 INFO: running: /tmp/jenkins/workspace/kata-containers-osbuilder-ubuntu-16-04-PR/go/src/github.com/kata-containers/osbuilder/tests/../../tests/cmd/kata-manager/kata-manager.sh configure-image /tmp/osbuilder-test.TkkiP8o/images/kata-containers-image-ubuntu.img
04:43:57 docker: Error response from daemon: OCI runtime create failed: rpc error: code = Internal desc = Could not create destination mount point: /etc/resolv.conf: open /etc/resolv.conf: no such file or directory: unknown.
04:43:57 INFO: ERROR: test failed

@chavafg : The PR makes changes to the initrd_builder, but the error seems to generate from the image built from image-builder/image_builder.sh .

you are right @nitkon, seems that master is broken when building the image with ubuntu.
Any idea @devimc @jodh-intel @jcvenegas?

@chavafg : Strange that the agent complains only for ubuntu even when the file exists.
root@soe13:/tmp/initrd# zcat /usr/share/kata-containers/kata-containers-initrd.img | cpio -idmv

root@soe13:/tmp/initrd# file etc/resolv.conf
etc/resolv.conf: symbolic link to ../run/systemd/resolve/stub-resolv.conf

/retest

PTAL @chavafg @amshinde

/retest

@marcov : Thnx. Updated with comments.
/retest


.Net: Bug: AzureCosmosDBNoSQLMemoryStore - CreateCollectionAsync results in 400 error

Describe the bug
Using AzureCosmosDBNoSQLMemoryStore,  the method CreateCollectionAsync results in a 400 error:

"Vector Indexing is not supported for shared throughput offer"

To Reproduce
Steps to reproduce the behavior:
Create AzureCosmosDBNoSQLMemoryStore instance and call CreateCollectionAsync
Expected behavior
Cosmos Collection should be created with proper vector support enabled
Platform

OS: Windows
IDE: VS
Language: C#
Source: 1.16.2

I'll add that this is attempting to create a new Container in an existing DB

@westdavidr Thanks for reporting this issue.
Based on error message, it looks like you are facing a limitation from your created Azure CosmosDB for NoSQL database with shared throughput:
https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/vector-search#current-limits-and-constraints

In order to resolve it, I think you should uncheck following setting:
https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-provision-database-throughput?tabs=dotnetv2#provision-throughput-using-azure-portal

Let us know if this helps to resolve your problem. Thanks a lot!

Thanks for the explanation. It makes sense now.


Errors when trying to install the code to a production/developer's org

Hi Douglas,
I hope your are doing fine so far. I am trying to install you app for converting attachment to files, since it tried installing the one from salesforce labs and it does not let me install it. When I try to install yours into my org, it display the following errors:
This app can't be installed.
There are problems that prevent this package from being installed.
Dependent class is invalid and needs recompilation: Class dca_cnvrt_file.ConvertAttachmentsToFilesBatchable : Dependent class is invalid and needs recompilation: Class dca_cnvrt_file.ConvertAttachmentsToFilesService : Field is not writeable: ContentVersion.CreatedById | ConvertAttachmentsRunOnceController: Dependent class is invalid and needs recompilation: Class dca_cnvrt_file.ConvertAttachmentsToFilesBatchable : Dependent class is invalid and needs recompilation: Class dca_cnvrt_file.ConvertAttachmentsToFilesService : Field is not writeable: ContentVersion.CreatedById.
I thank you before hand for any help you can provide me regarding this matter.

Hello, thanks for trying my migration app out!
For either app to install you will need to enable Create Audit Fields and grant permission to your profile.
https://help.salesforce.com/articleView?id=000213290&type=1&language=en_US


SU, PR and PE missing from Format Field

Hello,
I have followed instructions from Tutorial.md (which is great by the way) to create "merged.sv.pruned.vcf.gz" and it went smoothly. However, when I checked the file it includes SU, PR and PE only in the INFO field but lacking the same for sample based analysis. Is there a way to preserve this information if not all at least SU ?
Best,
Nick

Similar information should be available from svtyper in the format fields. It sounds like you are most interested in the amount of support for the SV (I assume PR is a typo and you actually want SR). Note that for most of the below there are matching fields detailing reference support for the evidence type.
AO - Alternate allele observations, with partial observations recorded fractionally (Equivalent to SU)
AS - Alternate allele split-read observation count, with partial observations recorded fractionally (Equivalent to SR)
ASC - Alternate allele clipped-read observation count, with partial observations recorded fractionally
AP - Alternate allele paired-end observation count, with partial observations recorded fractionally (Equivalent to PE).
Does this meet what you are looking for? Or were you specifically interesting in preserving the original lumpy information for each sample independently?

Thanks Dave,
Sorry the PR was indeed typo.
Yes, I am mostly interested in support for the SV, primarily because I am looking for de novo deletions in Trios and wanted filtered calls if there observed some level of support in parents. With that "AO" should satisfy the need , however, I did observe some significant different between SU and AO field as well the Pearson correlation between them is 0.67 in one sample that I tested.
Do you have any suggestions for setting thresholds for "AO" (or any other field) for de novo detection.
Best,
Nick

Hi Nick,
I believe svtyper is a bit more sensitive in its inclusion of SV-supporting reads so I don't think that the differences you're observing between support reported by Lumpy and support reported by svtyper are unexpected. That said, I've not evaluated the differences myself so I'm not entirely certain what a normal amount of difference is.
Unfortunately, my personal experience is with large cohorts as opposed to analyzing family data. If it were me, I might start with filtering for AO in both parents to try to find de novos and then start backing off the cutoff to a few reads of support to allow for some miscalling.

Hello Dave,
Thank you for response. I ended up using AO for extracting De novo candidates and works great. For other users, I used AO > 5 in proband and < 5 in parents. And, since we are interested in rare SVs I limited SV frequency to the 0.003 (n = 1000).
Thanks,
Nick

Glad to hear that worked and thank you very much for reporting the cutoffs you ended up using.


Error reporting component is broken

I have created an issue on JetBrains tracker, but they closed saying that the error is inside the plugin itself. So I posted this issue here.
This is the link to the original ticket with description of the problem: https://youtrack.jetbrains.com/issue/IDEA-154882

Thanks. This is a rather strange problem because IntelliJ generated code which triggers a Java classloader class name validation error.
Anyway, I fixed this for the next update.


Issues to generate SDK with swagger-codegen

I am trying to generate PySDK with swagger-codegen. I am using latest release of KubeVirt v0.0.2
I use following command to do that.
$ java -jar swagger-codegen-cli-2.2.1.jar generate -i "http://<IP_ADDRESS>:8183/swaggerapi/apis/kubevirt.io/v1alpha1" -l python -o /tmp/kubevirt-pysdk

I noticed that there are several exceptions in log during generation. Please see attached log-file:
kubevirt-pysdk.log
However the sdk gets generated and, auto-generated tests passes as well 😄
$ tox
........................................................................................
----------------------------------------------------------------------
Ran 88 tests in 0.211s

OK

Observing auto-generated SDK, only two calls were generated as I would expected: console & spice
Remaining methods were generated with meaning-lees names, like func1_8 or func1_10.
I would expect some meaningful names like list_vms, create_vm, ...
You can take a look at full result at https://github.com/lukas-bednar/kubevirt-pysdk-generated#documentation-for-api-endpoints
You can also find there log, and json file which was SDK generated from.
I generated SDK from KubeVirt master, and it has same issue, the main change there is about vms - > virtualmachines .
Feel free to take a look: https://github.com/lukas-bednar/kubevirt-pysdk-generated/tree/kubevirt-master

@lukas-bednar created #475 which will address the function names. Regarding to the errors, we probably don't set a type field or so. Will look into that too. Thanks for reporting!

@rmohr thanks for quick response, it looks good.
If I can help with something, I would be glad to do so ... just point me where to look.
Also I noticed that there are Doc("testX") strings or they are missing, for example here:
https://github.com/kubevirt/kubevirt/blob/a0fc1ec3297fd24fc20cbbf2636a309f1e60a6b5/pkg/virt-api/rest/kubeproxy.go#L105-L109
I can fill them up if you don't mind.

I see that Route object has many documentation related attributes.
https://github.com/emicklei/go-restful/blob/7a380bfc22e94bfe4fc605b9a15a7be1347ebe39/route_builder.go#L31
I will take a look at it and see what I can add there.

I can fill them up if you don't mind.

Yes please!

These errors
Error obtaining the datatype from RefProperty:io.swagger.models.properties.RefProperty@e8fe9c77. Datatype default to Object
[main] ERROR io.swagger.codegen.DefaultCodegen - null

are interesting. It looks like swagger-codegen tries to dereference the model in the swagger 2.0 way, although we have version 1.2 specified in the document. In 1.2 one can reference entities viea "$ref": "myobject" in the models section. In 2.0 one would have to write #/models/myobject.
I did not run swagger-codegen, but the Swagger Editor reacts that way with our spec.

what do you think about kube_connection_healthz_func function, I think it would deserve better name.
https://github.com/lukas-bednar/kubevirt-pysdk-generated/blob/kubevirt-master/docs/ApiskubevirtiovalphaApi.md#kube_connection_healthz_func
Do you have any preference? like health_status / health_page / service_health / health_check

Yes please!
I submitted it here #476 please comment on it!

I did not run swagger-codegen, but the Swagger Editor reacts that way with our spec.

I was checking documentation, and current swagger-codegen (2.2.1) should be compatible with 1.2.
https://swagger.io/docs/swagger-tools/
But apparently no, I will investigate it .
@fabiand in addition I was playing with that swager plugin for GitBook, and it doesn't generate doc well.
https://lukas-bednar.gitbooks.io/kubevirt-api-doc/content/
I think it will be probably from same reason ... strange thing is that GitBook doesn't report any error, everything seems to be OK, just documentation is not rendered.

@rmohr I think I found what causes that errors in code-generation: #480  I am just working on verification.

Yes, that's probably it. Good catch!

I am closing this issue all things which I had problem with, were addressed.
I don't have problem to generate SDK anymore ...


[test] Allow test scripts to import types from deployed contracts

Description
Below is a working example of utilizing types from deployed contracts, inside of a test script:
import Test
// The address `0x0000000000000005` comes from the account created in the lines below.
// This is where the `FooContract` is also deployed in the `setup()` function.
// However, we can't avoid the chicken-and-egg problem, developers will have to probably
// log the account to get the address, which will be sequential and guaranteed to be the same.
// import FooContract from account.address is not possible.
import FooContract from 0x0000000000000005

pub let blockchain = Test.newEmulatorBlockchain()
pub let account = blockchain.createAccount()

pub fun setup() {
    let contractCode = Test.readFile("../contracts/FooContract.cdc")
    let err = blockchain.deployContract(
        name: "FooContract",
        code: contractCode,
        account: account,
        arguments: []
    )

    Test.expect(err, Test.beNil())

    blockchain.useConfiguration(Test.Configuration({
        "../contracts/FooContract.cdc": account.address
    }))
}

pub fun testGetSpecialNumber() {
    let script = Test.readFile("../scripts/get_special_number.cdc")
    let result = blockchain.executeScript(script, [])

    Test.expect(result, Test.beSucceeded())

    // Type-cast from `AnyStruct` to the `SpecialNumber` type defined on `FooContract` contract
    let specialNumbers = result.returnValue! as! [FooContract.SpecialNumber]
    let specialNumber = specialNumbers[0]

    // We can even create an instance of the `SpecialNumber` type, and use it in assertions
    let expected = FooContract.SpecialNumber(n: 1729, trait: "Harshad")
    Test.assertEqual(expected, specialNumber)
}

pub fun testAddSpecialNumber() {
    let code = Test.readFile("../transactions/add_special_number.cdc")
    let tx = Test.Transaction(
        code: code,
        authorizers: [account.address],
        signers: [account],
        arguments: [78557, "Sierpinski"]
    )

    let result = blockchain.executeTransaction(tx)
    Test.expect(result, Test.beSucceeded())

    // No need to construct `CompositeType` for filtering blockchain events
    let typ = Type<FooContract.NumberAdded>()
    let events = blockchain.eventsOfType(typ)
    Test.assertEqual(1, events.length)

    // We can even type-cast events from `AnyStruct` to their actual type, and use
    // this object to perform assertions on the event payload.
    let event = events[0] as! FooContract.NumberAdded
    Test.assertEqual(78557, event.n)
    Test.assertEqual("Sierpinski", event.trait)
}

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

This assumes blockchain.createAccount() always creates the same account (with the same address) in each run, which might not always be the case.

One way around this, could be to use emulator.WithSimpleAddresses(), which contains the following documentation:
WithSimpleAddresses enables simple addresses, which are sequential starting with 0x01.

Another workaround could be to for developers to deploy contracts to blockchain.serviceAccount(), which seems rather limiting, but the address is not likely to change, e.g.:
import Test
import FooContract from 0xf8d6e0586b0a20c7

pub let blockchain = Test.newEmulatorBlockchain()
pub let admin = blockchain.serviceAccount()

pub fun setup() {
    let contractCode = Test.readFile("../contracts/FooContract.cdc")
    let err = blockchain.deployContract(
        name: "FooContract",
        code: contractCode,
        account: admin,
        arguments: []
    )

    Test.expect(err, Test.beNil())

    blockchain.useConfiguration(Test.Configuration({
        "../contracts/FooContract.cdc": admin.address
    }))
}

What are your thoughts on these?

Nice, using flow.MonotonicEmulator seems a much better approach 👌

How about:
import Test
import FooContract from "../contracts/FooContract.cdc"

pub let blockchain = Test.newEmulatorBlockchain()
pub let admin = blockchain.serviceAccount()

pub fun setup() {
    let err = blockchain.deployContract(
        name: "FooContract",
        source: "../contracts/FooContract.cdc",
        account: admin,
        arguments: []
    )
    Test.expect(err, Test.beNil())
}

this way we will also have editor support ( I assume )
@SupunS knows better but probably we can have import handler ( as we track on deploy address and source location )

@bluesign You are correct, this would give us editor support. However, we need the address to "trick" the type checker into thinking that the types returned from blockchain scripts, are indeed imported in the test script.
For example, if a script returns the FooContract.NumberAdded nested type (assuming it is deployed on 0x0000000000000005), then in the test script, we need to import from that specific address, for the following to work:
let typ = Type<FooContract.NumberAdded>()
let events = blockchain.eventsOfType(typ)
let event = events[0] as! FooContract.NumberAdded
Test.assertEqual(78557, event.n)
Test.assertEqual("Sierpinski", event.trait)

( as we track on deploy address and source location )

This seems promising though :ok_hand: , it didn't cross my mind that we do track both deploy address and source location. I will try to see if I can use the relative path import, and replace it with the actual deploy address in the import handler.

it didn't cross my mind that we do track both deploy address and source location. I will try to see if I can use the relative path import, and replace it with the actual deploy address in the import handler.

yeah I changed the signature of deploy in the example for that purpose, can be some new function like: blockchain.deployContractFromPath etc.
then we can inject imports after setup phase. ( I assume setup is running before )

Oh right :sweat_smile: Right now we are just passing the code. Good point :+1:
The setup phase runs once, before test cases.
However, the parsing and checking of imports has already been done. I have to check if we can do something in interpreterContractValueHandler.

Yeah, I agree with @bluesign, we could try to make the experience even more smoother, if possible.
I was also thinking it might be a good idea to merge the two environments. e.g.: https://github.com/onflow/cadence/issues/1993. I have been advocating against it earlier, but you are right, and I'm also starting to feel it might be actually good. i.e: It might be OK to just have one blockchain per test suite/file, and both the test script and the 'testing codes' share that.
@m-Peter Can you maybe open another issue for this? So we can discuss it further. We could also propose this change as a FLIP if needed. But might have to do some proof-of-concept on what's possible and how would it work afterward, before we propose.

Yeah, I agree with @bluesign, we could try to make the developer experience even more smoother, if possible.

@SupunS & @bluesign Unfortunately this is hard to overcome. The reason is that imports from StringLocation, are a sign that the developer will be writing unit tests, no blockchain involved, and the contract has to be instantiated within the test script, e.g:
import FooContract from "../contracts/FooContract.cdc"

pub let fooContract = FooContract()

If I try to cast a contract nested type, returned from a script executed against a blockchain, I get the following error:
error: failed to force-cast value: expected type `[S.../contracts/FooContract.cdc.FooContract.SpecialNumber]`, got `[A.0000000000000005.FooContract.SpecialNumber]`

I was also thinking it might be a good idea to merge the two environments. e.g.: https://github.com/onflow/cadence/issues/1993. I have been advocating against it earlier, but you are right, and I'm also starting to feel it might be actually good. i.e: It might be OK to just have one blockchain per test suite/file, and both the test script and the 'testing codes' share that.

The two environments here being the script environment and the one from EmulatorBackend's blockchain, right? It is possible that it may simplify things, but I can't know for sure, before I see the end result :sweat_smile:

@m-Peter Can you maybe open another issue for this? So we can discuss it further. We could also propose this change as a FLIP if needed. But might have to do some proof-of-concept on what's possible and how would it work afterward, before we propose.

Sure thing, I'll create another issue for this :+1:

How currently tests are run ? When file is loaded there is no FooContract at 0xf8d6e0586b0a20c7 no ? Is setup somehow running before hand?
import Test
import FooContract from 0xf8d6e0586b0a20c7

pub let blockchain = Test.newEmulatorBlockchain()
pub let admin = blockchain.serviceAccount()

pub fun setup() {
    let contractCode = Test.readFile("../contracts/FooContract.cdc")
    let err = blockchain.deployContract(
        name: "FooContract",
        code: contractCode,
        account: admin,
        arguments: []
    )

    Test.expect(err, Test.beNil())

    blockchain.useConfiguration(Test.Configuration({
        "../contracts/FooContract.cdc": admin.address
    }))
}

@bluesign You are right, there is no FooContract at 0xf8d6e0586b0a20c7. We simply ignore the address part, and load the source code from its respective file. With this trick, when we try to cast return values from scripts, then we have the correct type to make the type checker happy. E.g Type<FooContract>() => f8d6e0586b0a20c7.FooContract. This is mainly to get access to the nested types defined in FooContract, and not to actually interact with this. Scripts & transactions should still be used to get data and mutate the contract's state. I hope this clarifies things a bit more.

@m-Peter all clear now, thanks a lot. I think @SupunS suggestion of merging environments still not solving the issue though. As we cannot import before we deploy.
I think the easiest way would be, swizzling the declaration on deploy contract. import FooContract from "../contracts/FooContract.cdc" declares a FooContract global variable, when we call  blockchain.deployContract I believe we can inject the FooContract from sub blockchain and replace existing one.

As we cannot import before we deploy.

That's exactly right @bluesign . I have mentioned this problem in the description:
// However, we can't avoid the chicken-and-egg problem, developers will have to probably
// log the account to get the address, which will be sequential and guaranteed to be the same.
// import FooContract from account.address is not possible.

Yes, correct, merging two won't solve it. Even if we merge the two, it would need to construct the contract value later, at the time of the deployContract() is invoked (We would still have to do what we do right now under the hood)
However, by merging, we might be able to remove some of the pain points for developers, e.g: there would not be a blockchain
blockchain.deployContract() would be simply deployContract(). And the unit tests and integration tests would become one thing.
e.g:
Currently unit tests:
import FooContract from "../contracts/FooContract.cdc

var foo = FooContract()  // construct value
foo.sayHello()           // and then call the function

But after:
import FooContract from "../contracts/FooContract.cdc

FooContract.sayHello()  // FooContract is already the instance, just like in integration tests. So can directly call the function

So it is unified for both integration tests and unit tests.
We would also be able to get rid of setting the configurations for the blockchain. i.e:
blockchain.useConfiguration(Test.Configuration({
        "../contracts/FooContract.cdc": admin.address
    }))

Instead can make use of the flow.json directly.

yeah I just looked at this from integration tests perspective, but I agree unit tests would be much better if we merge.

Contracts were made first-class in https://github.com/onflow/cadence-tools/pull/210. And thus also scripts can become first class (methods in the same test script) too.


Fix RBAC on catalog items toolbar actions

This PR is fixing more issues on Catalog item toolbars' actions. It's fixing also identifiers of the product features already defined, and add some new ones. Then it's merging New/Edit/Delete Button and Button Groups actions to the one action for Button/Button Group.
I created this PR after removing duplicated product features in https://github.com/jrafanie/manageiq/commit/2fcae9692072d286cf2a975a24202fdb275b511d and basically it's reworked https://github.com/ManageIQ/manageiq/pull/3987 + completed RBAC fixes for all toolbars in Catalog Items.

I'm going to clean up the PR tomorrow(contains some debug outputs), revise it, split to commits, create screenshots (if needed) and write some specs. But feel free to review.

btw. I've noticed some strange behavior of displaying "Reload" and "History" buttons.

@jzigmund did some testing in UI, found some issue while logged in as super admin see my comment below, i haven't tried the user with limited feature access yet.
In Catalog Explorer
I was successfully able to add a new Button Group & Button. But there are no toolbar buttons available to edit/delete the buttons.

In Automate/Customization Explorer:
There are no toolbar buttons available on Button Group screen, to add/edit/delete the group or buttons under the group

On Button summary screen, there is no option available to edit/delete the selected Button

I see new product features added under Catalog Items in product features tree, correct me if i am wrong but i was under the impression that we were going to check RBAC access of existing hidden features under Automate/Customization & catalog item edit feature to show/hide Custom Buttons/Groups in Catalog Explorer.

@h-kataria fixed issues, please retest.

Screenshots:

Selected one catalog item (admin):

the same screen as user with view permission only:

Selected one Catalog Item - accordion Actions (as admin):

the same screen as an user with view permission only:

Selected one Catalog Item - its accordion button and button group (As Admin):

the same screens as an user with view permission only:

screenshots from Automate/Customization:

@jzigmund i still don't understand the need for new features to Add/Edit Button/Button group under Catalog Items. Do we need those, can't we use existing features under Automate/Customization along with a check whether a user can add/edit catalog Items?

@h-kataria I've reworked the whole PR, now when user has not "catalogitems_admin" feature Add/Edit actions are not allowed. Please review.

@miq-bot remove_label wip

@miq-bot add_label wip

@h-kataria updated PR, now a user with Add/Edit Catalog Item permission can manipulate with any Button/Button Group (includes all actions - not CRUD only).
I'm not sure what to do when user has "Edit Button" permission (ab_button_edit), please ping (gitter/irc) me when you are back at work to discuss it. For now, WIP label has been added.

@h-kataria updated PR, removed 'Edit Button' product feature from Catalog Items' features.

@miq-bot remove_label wip

@jzigmund found couple of issues:

while i am logged in as admin, i selected a custom button node in the Catalog Items tree, then pressed "Edit this button" in toolbars, that shows me Flash message "The user is not authorized for this task or item." see screenshot

created a role with acces to add atomic catalog item, see screenshot below:

then logged in as the user with role created above, i dont see toolbatr button to add/edit custom buttons or group. see screenshot

@h-kataria the last screenshot is in Service Catalogs, not Catalog Items

@jzigmund updated my comment above, removed the accidentally added screenshot.

@jzigmund : please, follow the pattern seen here: https://github.com/ManageIQ/manageiq/pull/7692
and my description about making the button classes in that PR and split the functionality here in separate button classes.
We are trying to get rid of button-specific logic in app/helpers/application_helper/toolbar_builder.rb

@h-kataria could you confirm that current PR is properly fixing the issue and I can split the button functionality to the class as @martinpovolny requests ?

verified fix.

@jzigmund : please, move the code to the proper place in a follow-up PR.

linking the follow-up PR: #10916


Switching to Dask Runners

This PR aims to resolve #52 by adding a Dask runner setup following the Kedro Tutorial.

Hello @stroblme! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/quafel/hooks.py:

Line 99:89: E501 line too long (92 > 88 characters)

This PR resolved #38 because enabling this backend leads to more resource allocation than actually available and thus to extreme slow down of code execution.


homepage image error

Project-Vani.github.io/images/illustrations/pointing.svg

Sorry, something went wrong. Reload?

solved this problem!


DjangoCon AU 2016: fix Markus Holtermann's talk recorded date and speaker

Done in #294 (as recommended).


[Refact] Reviewing block generators

Related to https://github.com/pasqal-io/qadence/issues/266
All unitary operators have an hermitian generator such that
$$\hat{U}=exp(-i\hat{H})$$
In Qadence we have block.generator which is supposed to return $\hat{H}$. However, if we want to use HamEvo to then represent the original unitary, we have to specify a time value since it implements $exp(-i\hat{H}t)$. Currently, some blocks seems to have some inconsistent definitions.
This also affects GPSR, since there the paper assumes a generator structure of $exp(-iG/2x)$ for some gate $U(x)$.
Probable requirements:

Make all gates follow the GPSR format, as suggested in https://github.com/pasqal-io/qadence/issues/266
Have a specific GPSR function to handle HamEvo differentiation, so that any arbitrary HamEvo(G, x) is processed in a way that the the $1/2$ factor is "considered" in $G$, and $x$ is an angle.

@jpmoutinho You mentioned something about it in the planning, right ?

@Roland-djee yes, for @chMoussa to be aware of this while planning how GPSR is integrated into pyqtorch

Closing with #526


Update-metadata-AdrienAllard.FileConverter

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @licon4812,
This manifest removes Apps and Features entries that are present in previous PR versions. These entries should be added to this version, to maintain version matching, and prevent the 'upgrade always available' situation with this package.
(Automated response - build 876.)


include prohibited regular expressions from a .gitprohibited file

Update git-secrets to include prohibited regular expressions from a .gitprohibited file
Issue #, if available:
Add the possibility of using a .gitprohibited file in the repository root to include prohibited patterns - much the same as .gitallowed is used to mark false positives
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Would love to see this merged in!


Change state when scrolling

Is it possible to animate the segmentedControl state change based off of swiping the whole page, not just by swiping the segmentedControl? It would be much more fluid if you could swipe either way.

It would be possible if segmented control exposed setter for percentage state, however it doesn't at the moment. May be a good feature though.


Support testing bigger vms

Various tweaks to support testing bigger vms with more cpus, memory, and large disks.

Add script for watching replication changes
Allow pulling from insecure local registry
Use v2 instead of latest
Enlarge kubevirt environment

@nirs I think you had an intention to change the registry image?

@nirs I think you had an intention to change the registry image?

I can but this is not a new issue introduced by this change, so I wan to do this later. We don't use this in the CI yet, this is a sample configuration that developers can use.

@akalenyu I added a commit using the image you suggested, thanks!


Interpolate the Go version in the test log name

Artifacts are "global" to the run, not scoped to the matrix. Without interpolating something like the Go version, we only end up with one log file, the last one to get uploaded.

This is a fixup for #83

Looks correct now: https://github.com/pion/ci-sandbox/actions/runs/2160116979 :smile:


Outdated package normalization

Looking into #657, I found npm now allows the repository property to be a string:

For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same shortcut syntax you use for npm install:

{
  "repository": "npm/npm",
  "repository": "github:user/repo",
  "repository": "gist:11081aaa281",
  "repository": "bitbucket:user/repo",
  "repository": "gitlab:user/repo"
}

The first case (not sure about others right now) isn't currently handled correctly:
	"githubRepo": null, // should not be null
	"repository": {
		"type": "git",
		"url": "npm/security-holder", // probably should be an actual URL?
		"project": "security-holder",
		"user": "npm",
		"host": "github.com",
		"path": "",
		"branch": "master"
	},

Npm's tool normalize-package-data normalizes this to the object format in the latest version. As it turns out, however, nice-package, which is used in this project, doesn't use normalize-package-data despite claiming so in the readme, it uses normalize-registry-metadata instead, which seems abandoned.
The reason repository has at least some information is it goes through hosted-git-info as well, which handles this format. This is likely not blocking #657 since we can check for repository.project and repository.user but still, the normalization library looks fairly outdated and there may be various other cases where it doesn't parse correct data.

Great catch, I wasn't aware that the normalisation has changed

Note that we currently don't handle repository.directory field because of the old hosted-git-info version. Might be something to fix on our side if we don't decide to upgrade that package as the field is useful for mono repos: https://github.com/jupyterlab/jupyterlab/issues/6443

Maybe we switch to the new version, but patch the breaking changes?

Maybe we switch to the new version, but patch the breaking changes?

It's an option for sure.


Misconfigured babel plugins - Cannot compile the library out of the box

babel-loader settings in webpack.config.js need to be fixed.
ESNext feature proposal-class-fields won't be handled printing the message below
ERROR in ./src/ImageResize.js
Module parse failed: /Users/carl/workspace/theta_cursor/node_modules/quill-image-resize-module/src/ImageResize.js Unexpected token (50:22)
You may need an appropriate loader to handle this file type.
|     }
|
|     initializeModules = () => {
|         this.removeModules();
|

You have to edit babel-loader plugins as shown below
                        "plugins": ["transform-class-properties"]

still unsolved

+1
Any solution?

I'm having the same issue.... do we have any instructions to compile locally at all?


Context sensitive online help (press '?' in console)

From<EMAIL_ADDRESS>on 2010-08-11T07:26:34Z
Online help should open the right page when ? is entered in the console.
Example::
writing in console
> os.path?
==> this should open os.path in the online help
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=279

From pierre.raybaut on 2011-10-29T04:28:56Z
Pressing '?' is already triggering the object inspector.
Status: WontFix

From pierre.raybaut on 2010-08-17T10:17:44Z
Summary: Context sensitive online help (press '?' in console)
Status: Accepted
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

From pierre.raybaut on 2011-05-16T01:07:54Z
Labels: Cat-Console


[Bug] Application frame too small under Windows (+ fix) [sf#20]

Reported by jdubery on 2003-03-10 20:17 UTC
hi all,
I think this comes under the heading of 'bug', though it's
a bit indeterminate.
On starting wxGlade the Properties frame is a little too
small on all my Windows machines - resulting in annoying
scrollbars obscuring things. I've put up with it for a while,
but this evening it annoyed me one time too many ...
there's a very simple change I've made in my copies of
main.py that (on Windows at least) makes wxGlade look
good on startup ...
self.frame2.SetSize((250, 350))
jdubery changed to:
    self.frame2.SetSize((260, 365))

It would be nice if it could all auto-size, but I think those
additional few pixels will do as a quick fix for now.
thanks
John

Commented by agriggio on 2003-03-10 23:46 UTC
Logged In: YES
user_id=375945
Thanks for raising the issue.
I thought I was the only one to be annoyed by this, and
since I never use windows, I was too lazy to fix it. Now it
should be better on CVS (hopefully)


Schema and migrations how to?

Using Lumen how do I create a migration file? I was using artisan to generate the migration file which looks like
<?php

use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class UsersCollection extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('users', function($collection)
        {
            $collection->index('name');
            $collection->password('password');
            $collection->unique('email');
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        //
    }
}

than I try to migrate
php artisan migrate
and I get the following error
  [Illuminate\Database\QueryException]
  SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected (SQL: create table `migrations` (`migration` varchar(255) not null, `batch` int not null) default ch
  aracter set utf8 collate utf8_unicode_ci)

  [PDOException]
  SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected

it seems like in this case wants to access the Mysql driver, however I have the right config under config/database.php
I do not find a proper description  how should be done in this case

What I did:
<?php

use Jenssegers\Mongodb\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateActionsTable extends Migration
{
    /**
    	 * The name of the database connection to use.
    	 *
    	 * @var string
    	 */
    protected $connection = 'mongodb';

    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::connection($this->connection)
        ->table('actions', function (Blueprint $collection)
        {
            $collection->index('name');
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::connection($this->connection)
        ->table('actions', function (Blueprint $collection)
        {
            $collection->drop();
        });
    }
}

the just
php artisan migrate

... and it worked.

How do you delete only the index added in the up method, instead of dropping the whole collection?

@Oyelaking Too late for you, but info for future visitors. To remove index just use:
$collection->dropIndex();


Add canonical form (DAG)

Summary
I added another form of DAG, the canonical form (reference: https://arxiv.org/abs/1909.05270). The DAGcanonical class can be found at qiskit.dagcircuit.dagcanonical. It is the basis for a new type of DAG. The nodes correspond to operations (gate, measurements, etc...). The edges correspond to non-commutation between two operations. The structure of this class shares similarities with the class DAGCircuit.
Two converters were added qiskit.converters.circuit_to_dagcanonical and qiskit.converters.dagcanonical_to_circuit.  The first one creates a DAGcanonical() object from a QuantumCircuit(). The second one does the opposite.
The qiskit.visualization.dag_visualization was adapted (add of a 'type' argument) to include the new form of DAG.
A test for converters was also added at test.python.converters.test_circuit_to_dag_canonical
Simplest example
Bell circuit without measurement;here the edge represents non commutation between the Hadamard gate and Cnot.
from qiskit import QuantumCircuit
from qiskit.converters.circuit_to_dagcanonical import circuit_to_dagcanonical

def build_bell_no_measurement():
    circuit=QuantumCircuit(2)
    circuit.h(0)
    circuit.cx(0, 1)
    return circuit

circuit =  build_bell_no_measurement()
dag_canonical = circuit_to_dagcanonical(circuit)

dag_canonical.draw(filename='bell.png')

Comments
The function 'commute' in qiskit.dagcircuit.dagcanonical that checks commutation relation can be improved. The lists of commutation and non-commutation are not complete.
Closes #1914 .

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.MOYARD Romain seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.MOYARD Romain seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 All committers have signed the CLA.

 All committers have signed the CLA.

Concerning commutation in the Z-basis, I prefer to let this as non-commuting at least for the moment in order not to affect templating matching.
Yes it could be great to have a separate node type for the DAGDependency(), then all attributes are at the same level. I will do this change and also the one for the _update_edge() as soon as possible.
Thank you for your comments.


Warning : Std.is is deprecated. Use Std.isOfType instead.

while running the code shown in https://docs.colyseus.io/colyseus/getting-started/haxe-client/

which haxe version do you use?
where this error exactly comes from? please post a full stack trace.

Fixed on 0.15 https://github.com/colyseus/colyseus-websocket-hx/commit/82cac588a1fe44fb5667e2b12b3c9232ccd5e260


Supporting locks

Any chance you could add support for things like rados_lock_exclusive ? I want to switch from my CGO use of librados to your library, but it's missing this piece.

Wait, I see that this is the old repo, let me look around some more

@immesys hi yes the maintained repo is at github.com/ceph/go-ceph could you resubmit there?


Can't commit due to biome error

Bug description
git commit is failing
✔ Preparing lint-staged...
⚠ Running tasks for staged files...
  ❯ package.json — 2 files
    ↓ *.{js,ts,tsx,svelte} — no files
    ❯ *.{md,css,json} — 1 file
      ✖ biome format --write [FAILED]
↓ Skipped because of errors from tasks.
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...

✖ biome format --write:
internalError/io ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × No files were processed in the specified paths.

Formatted 0 files in 258µs. No fixes applied.
husky - pre-commit script failed (code 1)

pnpm biome works:
$ pnpm biome format
Checked 1766 files in 434ms. No fixes applied.

https://biomejs.dev/guides/getting-started/
Operating system
Ubuntu
Installation Method
Other
Version
next (development version)
Steps to reproduce
No response
Relevant log output

Additional context
No response

It seems like biome doesn't support markdown?
https://biomejs.dev/internals/language-support/
So probably should continue to use prettier for that (*.md files), no?

#8970

pnpm biome format --write --log-level=debug website/docs/migrating-from-docker/managing-docker-compatibility.md
  2024-12-29T21:00:03.505099Z DEBUG  The file website/docs/migrating-from-docker/managing-docker-compatibility.md has the following feature sets:
{Assists: FileNotSupported, Debug: FileNotSupported, Format: FileNotSupported, Lint: FileNotSupported, Search: FileNotSupported, OrganizeImports: FeatureNotEnabled}
    at crates/biome_service/src/workspace.rs:238 on biome::worker_0
    in with_settings_and_language with file_source: Unknown, path: "website/docs/migrating-from-docker/managing-docker-compatibility.md"

Formatted 0 files in 340µs. No fixes applied.
internalError/io ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ No files were processed in the specified paths.

$ pnpm biome --version
Version: 1.9.4

Nice, there are trailing newlines and stuff all over the place in the markdown.
[warn] Code style issues found in 181 files. Run Prettier with --write to fix.
But at least the git commit hook works again. As in: pnpm lint-staged is green.
--- a/package.json
+++ b/package.json
@@ -72,8 +72,8 @@
     "test:watch": "vitest watch",
     "test:website": "vitest run -r website --passWithNoTests --coverage",
     "watch": "node scripts/watch.mjs",
-    "format:check": "biome format",
-    "format:fix": "biome format --write",
+    "format:check": "biome format && prettier --cache --check \"website/**/*.md\"",
+    "format:fix": "biome format --write && prettier --cache --write \"website/**/*.md\"",
     "markdownlint:check": "markdownlint-cli2 \"website/**/*.md\" \"#website/node_modules\" \"#website/api\"",
     "markdownlint:fix": "markdownlint-cli2-fix \"website/**/*.md\" \"#website/node_modules\"",
     "lint:clean": "rimraf .eslintcache",
@@ -112,7 +112,8 @@
       "node --max-old-space-size=6144 node_modules/eslint/bin/eslint.js --cache --fix",
       "biome format --write"
     ],
-    "*.{md,css,json}": "biome format --write"
+    "*.md": "prettier --cache --write",
+    "*.{css,json}": "biome format --write"
   },
   "devDependencies": {
     "@biomejs/biome": "^1.9.4",
@@ -166,6 +167,7 @@
     "lint-staged": "^15.2.11",
     "minimist": "^1.2.8",
     "msw": "^2.7.0",
+    "prettier": "^3.3.3",
     "postcss-import": "^16.1.0",
     "proxy": "^2.2.0",
     "typescript": "5.6.3",

The markdownlint looks broken as well, but maybe that was known already?
--- a/package.json
+++ b/package.json
@@ -75,7 +75,7 @@
     "format:check": "biome format && prettier --cache --check \"website/**/*.md\"",
     "format:fix": "biome format --write && prettier --cache --write \"website/**/*.md\"",
     "markdownlint:check": "markdownlint-cli2 \"website/**/*.md\" \"#website/node_modules\" \"#website/api\"",
-    "markdownlint:fix": "markdownlint-cli2-fix \"website/**/*.md\" \"#website/node_modules\"",
+    "markdownlint:fix": "markdownlint-cli2 --fix \"website/**/*.md\" \"#website/node_modules\"",
     "lint:clean": "rimraf .eslintcache",
     "lint:fix": "node --max-old-space-size=6144 node_modules/eslint/bin/eslint.js --cache . --cache-strategy content --fix",
     "lint:check": "node --max-old-space-size=6144 node_modules/eslint/bin/eslint.js --cache . --cache-strategy content",
--- a/.markdownlint.yaml
+++ b/.markdownlint.yaml
@@ -8,5 +8,7 @@ MD014: false
 MD024: false
 # We have multiple top-level headings in the same document to set different page title and navigation title:
 MD025: false
+# Allow actual numbers in numbered lists:
+MD029: false
 # We allow inline HTML (icon):
 MD033: false

Just some minor issues for the newly added markdown, that the"fix" would fix.
Summary: 13 error(s)
website/blog/2022-11-17-develop-podman-using-codespaces.md:147 MD039/no-space-in-links Spaces inside link text [Context: "...top/devcontainer-parent:next ]"]
website/blog/2024-11-26-ai-lab-first-app.md:44 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:56 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:68 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:102 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:144 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:162 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/blog/2024-11-26-ai-lab-first-app.md:194 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/docs/discover-podman-desktop.md:97 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "Built-in extensions"]
website/docs/discover-podman-desktop.md:109 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "Other extensions"]
website/docs/installation/windows-install/index.md:175 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/docs/podman/gpu.md:100 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
website/docs/podman/gpu.md:109 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

hello, as you have discovered, it's related to markdown. If you only have changes in markdown files, husky will send the path to md files to biome that will say that it can't handle it.

husky will send the path to md files to biome that will say that it can't handle it

Or crash and burn with a cryptic Rust error, depending on your view? :-)

If anyone else is having the same problems, the workaround is to do do --no-verify and run the checks locally.
pnpm commitlint --last
pnpm lint:check
pnpm format:check


Documentation on usage of gazebo simulation

Feature summary
We should let people now that the robot can be simulated with the gazebo repository or the ignition repository.
Adding the documentation in the usage documentation of this driver would add more awareness on different ways to simulate your solution before testing it on real hardware. I therefore suggest to add a section in the usage documentation where we explain gazebo/ignition simulation and a description on how to set it up or a link to the repository with a description on how to set it up.

Just a note: IMHO this should not necessarily be part of this repo, but documented inside their respective repos and we should finally build our comprehensive documentation putting together all the different repos into one deployed doc.

I wasn't aware of that, but that sounds like a much better solution. I am just under the impression that people isn't aware of the possibility of using gazebo with UR robots. I thought  a good way of creating more awareness, was to put some information about it inside this drivers documentation, but I prefer the idea of one comprehensive documentation.

So, what is the proper way then? I'm struggling with it.
So far, I'm using the UR10e moveit package + driver to visualize in rviz or control the real robot.
I have seen that the urdf supports something with gazebo but it seems like both mentioned packages do not give the possibility to set sim_gazebo to true. How should it be done in humble?


Provide a way to see query duration through session logger and QueryStatistics

It seems reasonable to assume in dev/test/production folks will want to profile their setup to find any performance bottlenecks and to do so they might use a tool like Glimpse or logging to the debug console.
I looked around Marten's codebase and npgsql's but did not see anything suitable as an extension point to add this kind of logging for query execution duration. npgsql has a logging provider implementation but only command text is passed through.
The IMartenSessionLogger is very close to what I'd need to add Glimpse support but duration of the command execution is not exposed. I was thinking it was something that ManagedConnection might be able to take care of and pass along, as well as exposing it off of QueryStatistics for one-offs.
For example, IMartenSessionLogger could change to pass a wrapper object that contains the command + any relevant statistics.
Statistics I'd be interested in:

Query Duration (Time to execute raw query)
Total Duration (Total time including Marten + Serialization overhead)

I completely buy the idea of using Glimpse to understand Marten behavior and we're already doing that kind of thing with FubuMVC diagnostics in our shop. But for performance, I think I'd rather opt for something like New Relic or some other kind of performance monitoring tooling instead of trying to build something into Marten itself.

Makes sense, I was only thinking of query logging in scope for this to
allow plugin integration. I'm on Azure so I need all the help I can get.
On Wed, Aug 24, 2016, 09:25 Jeremy D. Miller<EMAIL_ADDRESS>wrote:

I completely buy the idea of using Glimpse to understand Marten behavior
and we're already doing that kind of thing with FubuMVC diagnostics in our
shop. But for performance, I think I'd rather opt for something like New
Relic or some other kind of performance monitoring tooling instead of
trying to build something into Marten itself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JasperFx/marten/issues/457#issuecomment-242083603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiaa2l-FQ8JqF3Kenlq_QDURU7r93FWks5qjFRngaJpZM4JOAhw
.

@jeremydmiller Does the way exist at this moment(marten 2.8.0) write custom interceptor to measure query duration?
Something like this or via app metrics:
	var sw = Stopwatch.StartNew();

	//query execution

	sw.Stop();

This can be done now with the latest logging changes for v4


Fix tweet not found error

Codecov Report

Merging #26 (080b36d) into master (61800a2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           68        68
  Lines          922       935   +13
=========================================
+ Hits           922       935   +13

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...tweet/tweets_by_ids_runner/tweets_by_ids_result.py
100.00% <100.00%> (ø)

...tweet/tweets_by_ids_runner/tweets_by_ids_runner.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 61800a2...0f9d4c4. Read the comment docs.


Improve Router API

Realized that I used a wrong name for the / combinator.

Coverage increased (+0.29%) to 91.34% when pulling e7bd959047fb8194642da7b5d7f070c4ddde25fd on improve-router-api into ed7f816cf8a60fcc005de80b9686b747a16ca3a7 on master.

Coverage increased (+0.29%) to 91.34% when pulling e7bd959047fb8194642da7b5d7f070c4ddde25fd on improve-router-api into ed7f816cf8a60fcc005de80b9686b747a16ca3a7 on master.


Verify recommendation for --flat-nodes when --append is indicated

URL pattern on localhost
http://localhost:5000/recommendation?system_ram_gb=64&osm_pbf_gb=10.4&append=True&pbf_filename=north-america-latest&pgosm_layer_set=run
Returns:
osm2pgsql -d $PGOSM_CONN \
--cache=0 \
--slim \
--flat-nodes=/tmp/nodes \
--output=flex --style=./run.lua \
~/pgosm-data/north-america-latest.osm.pbf

Printed description indicates there is sufficient RAM to not need --flat-nodes.

"A server with 64.0 GB RAM should be able to allow up to 42.2 GB RAM to osm2pgsql and still give room for Postgres. Running osm2pgsql entirely in-memory requires 27.0 GB RAM. "

Changing append to false:
http://localhost:5000/recommendation?system_ram_gb=64&osm_pbf_gb=10.4&append=False&pbf_filename=north-america-latest&pgosm_layer_set=run
No flat nodes (as well as no slim, expected w/out append)
osm2pgsql -d $PGOSM_CONN \
--output=flex --style=./run.lua \
~/pgosm-data/north-america-latest.osm.pbf

The use of --slim with --flat-nodes seems wrong.  If it is valid -- need to update printed text to explain WHY.

This has been resolved with other changes to notice.  There is an obvious note that states that --slim without --drop is required due to the inclusion of Append mode.  Closing.


Clarified Categories

Clarified categories can be both an array and a string.
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @hmbrown64,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Validate VID

Embedded proof only for phase 1

I've added the missing files in my branch and so far no build errors using the forked version that's compatible with React Native. The current issue I'm resolving is this error when attempting to verify a credential:
VALIDATION STATUS:  Object {
  "error": [VerificationError: Verification error(s).],
  "results": Array [
    Object {
      "error": [Error: crypto.subtle not found.],
      "proof": Object {
      ...

Updated estimate is 2 more days. TODOs left:

[ ] fix error with missing crypto.subtle
[ ] test on local sample data
[ ] test on live backend data

Listing other potential libraries we can use:

Veramo

Caveat: uses rn-nodeify to hack NodeJS modules into React Native

verifiable-credentials-java

We will need to create a React Native plugin to use it in the app

Verified on 0.3.0 RC2 1.1.5. Working as expected.
Created test case TSRA-52.


Added my data

if conflicts occur, what to do?
added my data to contributors.js and contributors.md

Good job @bhavyasingh75
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Use regex to only separate URLs when separator is followed by http

URL belonging to Australian member was being split into two separate entries because it contained a semi-colon. This PR fixes this particular case by ignoring the semicolon if it is not followed by 'http'

Duplicate of https://github.com/tmtmtmtm/csv_to_popolo/pull/105#event-807902249


Create extract JSON file for TvPaint

In GitLab by @friquette on Nov 22, 2022, 16:20

@rebecahayem are we dropping this feature?

Move this plugins into https://github.com/quadproduction/quad-plugins

We can put the development of this feature on stand-by until further notice. There are other priorities to attend to. We might reopen it someday, but for now we can "close it"


Remove react and react-native from dependencies

You have listed react and react-native as both dependencies and peerDependencies in package.json. Only peer dependencies should be used, so that consumers don't get conflicting versions of these in their project.
Also, the peer dependencies should use a less restrictive version range. React v17 is out, and 0.67 is the latest react-native. I guess this package should work well with both of them.

Done.


As a User, I should be able to filter itineraries, so I can have the itineraries that I am interested in

PR #137