“_zsh_autosuggest_async_pty_create: pty command name already used”

I'm in the middle of a complete refresh of my Zsh config; and after trying ZSH_AUTOSUGGEST_USE_ASYNC=true, my terminal looks like … this:

i.e. every command results in additional erroneous output along these lines:
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response

(This appears to not occur when ZSH_AUTOSUGGEST_USE_ASYNC is disabled, but I suppose that's to be expected. 😅)

I'm having trouble reproducing this. What version of zsh are you using?
Can you reproduce with no extra configuration?
% zsh -f
%% ZSH_AUTOSUGGEST_USE_ASYNC=true; source zsh-autosuggestions.zsh

Also, if you have the time to write a failing spec it would be greatly appreciated.
Thanks

Hmmm! I cannot reproduce as demonstrated / without config …
Unfortunately, I've completed aforementioned complete refresh, and I also cannot reproduce with my current config. The bug was persistent at the time, so I suspect it's still lurking — but I suppose I'll have to close this, unless someone comes across later who's experiencing it in realtime!

I'm also seeing this when used with find:
🤔 ~/c/dotfiles (5d0c056)|master⚡
± [i]: find .
.
./.agignore
./.alacritty.yml
./.aliases
./.config
./.config/nvim
./.config/nvim/init.vim
./.config/pep8
./.config/pgcli
./.config/pgcli/pglcli
./.docker-aliases
./.docker-functions
./.functions
./.git
./.git/COMMIT_EDITMSG
./.git/config
./.git/description
./.git/FETCH_HEAD
./.git/HEAD
./.git/hooks
./.git/hooks/applypatch-msg.sample
./.git/hooks/commit-msg.sample
./.git/hooks/post-update.sample
./.git/hooks/pre-applypatch.sample
./.git/hooks/pre-commit.sample
./.git/hooks/pre-push.sample
./.git/hooks/pre-rebase.sample
./.git/hooks/pre-receive.sample
./.git/hooks/prepare-commit-msg.sample
./.git/hooks/update.sample
./.git/index
./.git/info
./.git/info/exclude
./.git/logs
./.git/logs/HEAD
./.git/logs/refs
./.git/logs/refs/heads
./.git/logs/refs/heads/master
./.git/logs/refs/remotes
./.git/logs/refs/remotes/origin
./.git/logs/refs/remotes/origin/HEAD
./.git/logs/refs/remotes/origin/master
./.git/objects
./.git/objects/06
./.git/objects/06/23d681abd163f955700572d8d7666a3c7ab6a6
./.git/objects/09
./.git/objects/09/abc26786f4ebca188946a3e7d9743ca0fa42ce
./.git/objects/0a
./.git/objects/0a/d9dfe5fed37ece12d9a417ff339117c1965021
./.git/objects/0b
./.git/objects/0b/715532b2fdd7cb11d494c733c714492a014e6e
./.git/objects/1d
./.git/objects/1d/8fc5b26e7a7e7ccb4aed08da983fe887662b3b
./.git/objects/1e
./.git/objects/1e/d158a250c7d8c5b19d4f84931e98cc6d3f3d93
./.git/objects/1f
./.git/objects/1f/cc16b5098ddd841b9693b9a4dc603e5b251e41
./.git/objects/22
./.git/objects/22/d80a2a72a443725fd629c136e7eb13a055258d
./.git/objects/25
./.git/objects/25/087fa510866d702f67c24a52e1de4dcbb36de8
./.git/objects/25/9bd8434e50128baeae04863eed2b23ae70e840
./.git/objects/26
./.git/objects/26/c07b7b432bebdaf07d9bfb6a72af74fd769b4d
./.git/objects/27
./.git/objects/27/25f37488662ebe61f0248ab8d2875eeb687a9c
./.git/objects/27/e6fe9c41cc80d5884d477a1998a22f7becf5fe
./.git/objects/28
./.git/objects/28/5b17831ce229f1ed58bfc6841fb7b90fb1fa9f
./.git/objects/29
./.git/objects/29/a43b04b68e9f96af9822730a672f79f36526de
./.git/objects/29/c484bcb5970de445db787bbfaef904336c1af7
./.git/objects/2c
./.git/objects/2c/d2d909a16650bd07616cf4d682eb7678e6572c
./.git/objects/32
./.git/objects/32/9577c927072d70cbbba99e553c93aee8d57d13
./.git/objects/33
./.git/objects/33/91255efe0a2b8295803552b4f37b0ced94adc0
./.git/objects/34
./.git/objects/34/3a152cab8cb86416a985b5152cebfd90fa67cd
./.git/objects/35
./.git/objects/35/b839e09b80d9cbfd66762f92e3c138a6234bf0
./.git/objects/3a
./.git/objects/3a/d1be43d0a01abafbc058786114cf6c9521bcf4
./.git/objects/3f
./.git/objects/3f/6a97a5b9bc428b83f9f1696ab2cea1e8b99292
./.git/objects/3f/8277bd953fb4884fe4a3589ef5463a2ad61165
./.git/objects/40
./.git/objects/40/1f8c19ab063bf79f6bc4b3e1fbcaad47467806
./.git/objects/45
./.git/objects/45/04e32ddfc4d6e581773780a36792d5867c587b
./.git/objects/49
./.git/objects/49/62710636d8553c788eb2354530088bf3cb261a
./.git/objects/4d
./.git/objects/4d/0a4b06ceee6bef31df2763460059a616b13695
./.git/objects/50
./.git/objects/50/7db2440bdf118c532967a72e72292350a9ab02
./.git/objects/51
./.git/objects/51/0684b0616ca2268c0db5a25332bc3989a6f637
./.git/objects/51/7993372d2c52bb0d2b70b416dc3be2dcd9b70e
./.git/objects/51/996c6157b9d744edbcfaa609114e4b284c0ba5
./.git/objects/57
./.git/objects/57/8aa66874d32020f4db817881de31c547013e31
./.git/objects/57/e12c90590bea2b2c590d2dfe0ae82dae597249
./.git/objects/5b
./.git/objects/5b/96ce46b911d0527a951774808524fd59f676ef
./.git/objects/5b/f5c3ef1426bd570bd78f832c8ca7a5c2079064
./.git/objects/5d
./.git/objects/5d/0c056bc93d0a93c23d00140b73d970e14cf7b7
./.git/objects/60
./.git/objects/60/90c1bad6937c231437235f0d24e8d3af57db60
./.git/objects/61
./.git/objects/61/8c0582f65c09f02c1ff83c490808c0fbb81dd7
./.git/objects/64
./.git/objects/64/390dd4dd3e405e441a70cd5593f044cbecee95
./.git/objects/67
./.git/objects/67/903e48a3fd37dbfae3ecc581ac1bacf48602c7
./.git/objects/69
./.git/objects/69/0d75c8479e0abd09c7f435c255923dcc704ede
./.git/objects/6d
./.git/objects/6d/fc6a74b216206a104ded5ab3742a64132111a0
./.git/objects/6f
./.git/objects/6f/61de70fced7118558d3b158bec60937d215579
./.git/objects/70
./.git/objects/70/14e45ea5e2d1643bdd296457f084bd99fa0e35
./.git/objects/70/43d9437e9558928026976f844c987ae053c082
./.git/objects/75
./.git/objects/75/2c5c43fbf897251645ab8b52d0c86940c835e2
./.git/objects/76
./.git/objects/76/ca24a2480c50cc4f7c6df591c54ebfbc14bc00
./.git/objects/78
./.git/objects/78/192233a5792f22e1e6ff56c01701ec1393a986
./.git/objects/79
./.git/objects/79/18623d086175871dba2c64fd1ceffcdb30ab05
./.git/objects/79/87d315997baa09f6849654c6968cfab1a605d0
./.git/objects/7b
./.git/objects/7b/da2bc7e69d87138d17dfe0ae33459095d627f8
./.git/objects/7c
./.git/objects/7c/00707ea89617f35c2fffce36c55f337c20fbe4
./.git/objects/81
./.git/objects/81/84d92e7707f27c38ea01ee7f646ece4b482bcd
./.git/objects/84
./.git/objects/84/c42e2596a7b792b735858b622cf853a1418264
./.git/objects/88
./.git/objects/88/66adf4eac9c7f2902b1aebec7ef0a31b2aa5a0
./.git/objects/8d
./.git/objects/8d/c31491acfd356e8f022ab809578a981e85c692
./.git/objects/8f
./.git/objects/8f/0d270e9b63e7eb41f41e201ce2217b26059928
./.git/objects/93
./.git/objects/93/3048743f329ed89db634d634c0ae095f5fa2a3
./.git/objects/94
./.git/objects/94/a20e3fec2d1f7c3c96bb045cae4d3be3918472
./.git/objects/95
./.git/objects/95/117432539b382fe40f01061afc982f989f32eb
./.git/objects/96
./.git/objects/96/d42eaab679dcf06390885d950330b819569f29
./.git/objects/97
./.git/objects/97/f690f01141014520ebc9606922112952373f49
./.git/objects/9e
./.git/objects/9e/e57b517fd06359ac7bb5052ba3159ea3cf1862
./.git/objects/9f
./.git/objects/9f/caee63fe7dfaf2da264f3ec63797c4dea7dfe0
./.git/objects/a0
./.git/objects/a0/5bb8a2faaa66bf5ac271c148bc34e5760a39e5
./.git/objects/a5
./.git/objects/a5/581abf8bbb7816343ac17c8a8142b0a5fcae77
./.git/objects/a5/708d26cba5d8b78667f83ff518582e6f723159
./.git/objects/a5/894a99ab26eec6c8973ad5a752098d09ade609
./.git/objects/b0
./.git/objects/b0/7180eb582dee9c294ca67428ba09a215cf8b6e
./.git/objects/b3
./.git/objects/b3/aeec16771df50c3535d09d351a16129a7c2c44
./.git/objects/b4
./.git/objects/b4/d0cdb69ec0334def28f8032decacebc0367214
./.git/objects/b9
./.git/objects/b9/d0c5ee63aacc854c82e69caed1ed6eedcfd935
./.git/objects/b9/ebcb036b18b807c4a26aa5f5687f91c0cd1a94
./.git/objects/ba
./.git/objects/ba/700d50a070a315672f622662ed910f7cd8bec1
./.git/objects/bb
./.git/objects/bb/e26b604403f829f3f861ae38be974a9729697b
./.git/objects/c2
./.git/objects/c2/54a2446aac1b20e7d0d70585d507dee4d5381c
./.git/objects/c2/8f6cb3f49a17e158a7eddad0ccb005477ec020
./.git/objects/c4
./.git/objects/c4/32fc6581a13a70a5b6d23c53fb5eed43f8e11a
./.git/objects/c7
./.git/objects/c7/2fe63cccad79a4cde272c765944700c01e8d83
./.git/objects/c8
./.git/objects/c8/c629a4f54e0734a8c6530c04b05c151389e56b
./.git/objects/cb
./.git/objects/cb/851733a398caeb353ca4a24465439497dd55e4
./.git/objects/d1
./.git/objects/d1/78bf23154e8d2a9853a4a28ccd45aa59a53361
./.git/objects/d3
./.git/objects/d3/de0a2af35f70ef2569621eb7fbb58f5a3c9cbf
./.git/objects/d4
./.git/objects/d4/1de7df0fac8f2905b7b066ceea979fbbdd0539
./.git/objects/d4/41fda52148804da5b43baaa13d364aaa0f791d
./.git/objects/d4/8f0134f629f6ad2da22ae5e1de96e70930ef9c
./.git/objects/d7
./.git/objects/d7/e0d1f30c238b9dd9e890140d2f4b2024c68e00
./.git/objects/da
./.git/objects/da/8cde0a0c4035d771eba099c36092fbdb94e4a2
./.git/objects/dd
./.git/objects/dd/a17fe7c8b9da154b858ef773753911fa59b003
./.git/objects/de
./.git/objects/de/dba1677819bd4205d53bfb7ff0f67d3a75d57e
./.git/objects/de/ff954134056c893e90ab98cc4fde4f248035e5
./.git/objects/df
./.git/objects/df/8be7cb2b424b6879695d6e9fdd3763f7bc56e7
./.git/objects/e6
./.git/objects/e6/601f75335476edf4120dd3643b6b470a7a0e3f
./.git/objects/e6/86f5e8cc1083c725bf6be81eb9cfe36c6129d2
./.git/objects/e8
./.git/objects/e8/d068e280559c45cf57613757ef757ba47f2d69
./.git/objects/e9
./.git/objects/e9/b9c46edf021994625b845efa1fac7ac5527069
./.git/objects/ea
./.git/objects/ea/404276746a04bd6479679577c9ef53127f78c2
./.git/objects/ea/7afcca8202c54b92f8d539b8553e97b469eb15
./.git/objects/eb
./.git/objects/eb/7ee26d562f7144083d08b6f8b410f7f09ae51f
./.git/objects/ec
./.git/objects/ec/84372b191855abf32d8a15b609384c7f2e6178
./.git/objects/ec/896423e46586ca3cb11de708e98ba5bb82bc38
./.git/objects/f3
./.git/objects/f3/71025b76b97adc67b7d6109ebd0e2411d7c515
./.git/objects/f3/c62dc6a54c9b45b42b226d92b5520264bc8188
./.git/objects/f5
./.git/objects/f5/fb116f33a30cf6d28271adb1e50c011bdb5a96
./.git/objects/f6
./.git/objects/f6/d1576ce6166687056bff7586c8fa4dd99e2150
./.git/objects/f8
./.git/objects/f8/0dfa711ceb34e2a58c68565314b48e5cf171b7
./.git/objects/f8/c9c89d94d68c2b96ac0144cfe0435fe5b69b24
./.git/objects/fa
./.git/objects/fa/50a408df63065b36b1b0c1057960a791267b25
./.git/objects/fa/7f30571453b6944244c45a1b14d304df7c6ac1
./.git/objects/fd
./.git/objects/fd/7e12a7c3ce077349b5f5ace0defa75d042936e
./.git/objects/fe
./.git/objects/fe/41f0fea0a46e3a2438d2ca5e229dca6e552e34
./.git/objects/fe/b60f54e7861e9f509c4525baded7cd385e9cc8
./.git/objects/info
./.git/objects/pack
./.git/objects/pack/pack-751d41b2501023148ed57414a217b0cf05d5267b.idx
./.git/objects/pack/pack-751d41b2501023148ed57414a217b0cf05d5267b.pack
./.git/ORIG_HEAD
./.git/packed-refs
./.git/refs
./.git/refs/heads
./.git/refs/heads/master
./.git/refs/remotes
./.git/refs/remotes/origin
./.git/refs/remotes/origin/HEAD
./.git/refs/remotes/origin/master
./.git/refs/tags
./.git-aliases
./.git-functions
./.git-prompt
./.gitconfig
./.oh-my-zsh
./.oh-my-zsh/plugins
./.oh-my-zsh/plugins/vi-mode
./.oh-my-zsh/plugins/vi-mode/vi-mode.plugin.zsh
./.oh-my-zsh/themes
./.oh-my-zsh/themes/smt.zsh-theme
./.profile
./.tmux-aliases
./.tmux-functions
./.tmux-gruvbox-dark.tmux
./.tmux-gruvbox-light.tmux
./.tmux.conf
./.vim
./.vim/ftplugin
./.vim/ftplugin/python.vim
./.vimrc
./.zprofile
./.zshenv
./.zshrc
./apply
./dev-private
./README.md
./save
./terminfo
./terminfo/tmux-256color.terminfo
./terminfo/tmux.terminfo
./terminfo/xterm-256color-italic.terminfo
./usr
./usr/local
./usr/local/bin
./usr/local/bin/b
./usr/local/bin/ftwind
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response

Please reopen; I can reproduce this with zsh-autosuggestions c7d4a85031c101ef9bce0018096622087894dd09 + zsh 5.3.1-4+b1 on Debian 9 (stretch) by holding down ctrl-c for ~10 seconds, on one particular server to which I have a slow (200ms) connection.
My zsh-autosuggestions settings are
ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE=fg=6
ZSH_AUTOSUGGEST_STRATEGY=match_prev_cmd
ZSH_AUTOSUGGEST_USE_ASYNC=1

and the rest of the zshrc is here.
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
at@paris2:/root#
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root#
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root# dpkg -l | grep zsh
ii  zsh                             5.3.1-4+b1                        amd64        shell with lots of features
ii  zsh-common                      5.3.1-4                           all          architecture independent files for Zsh
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response
at@paris2:/root# uname -a
Linux paris2 4.14.0-9-amd64 #1 SMP Debian 4.14.3-2 (2017-11-30) x86_64 GNU/Linux
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response

I have this happening in an open terminal — I cannot generally reproduce, but it returns to show up in one terminal session once in a blue moon. Definitely needs to stay open!

I get this too sometimes, but when/why is unknown.

I'm getting it after I execute:
a=$(exit 1)

Then all next commands will show this output:
_zsh_autosuggest_async_pty_create:zpty:12: pty command name already used: zsh_autosuggest_pty
_zsh_autosuggest_async_pty_create:zle:22: Bad file descriptor number for -F: _zsh_autosuggest_async_response

Looks like even just $(exit) will get us into this state reliably... Nice find @kriansa

As a workaround for now, it looks like you can run zpty -d $ZSH_AUTOSUGGEST_ASYNC_PTY_NAME to fix things when you get into this state.

Looks like there's some kind of underlying bug in the zpty module here that causes pty's to exit when a subshell exits...
This was with zsh 5.4.2 with no additional config loaded:
% zmodload zsh/zpty
% zpty -b foo cat
% zpty -b bar cat
% zpty
(31689) bar: cat
(31666) foo: cat
% $(exit)
% zpty
(finished) bar: cat
(finished) foo: cat

Ok, this has been fixed on develop with df5fb85 and will go out with the next release.
The upstream issue remains, but it looks like we can fix this issue without fixing upstream.


StringFieldMapper.Builder and analyzer definition

I have analyzer defined for my index but cant figure out how to get NamedAnalyzer object to be used in StringFieldMapper.Builder.indexAnalyzer method?
Code should look like this:
new StringFieldMapper.Builder("doc_authors").store(true).indexAnalyzer(NamedAnalyzer ...)
I know its not primarly JEST related problem, but I cant figure out it in JEST environment. Appreciate any advice here.

Hello
Perhaps, below link is give to help you.
public NamedAnalyzer(String name,
org.apache.lucene.analysis.Analyzer analyzer)
http://xbib.org/elasticsearch/1.3.1/apidocs/org/elasticsearch/index/analysis/NamedAnalyzer.html
Best Regards
happyprg


Lifted ResourceT funcitons

It would be nice to have functions such as allocate, but lifted into Eff monad.
For example:
allocate
  :: Resource :> es
  => Eff es a
  -> (a -> Eff es ())
  -> Eff es (ReleaseKey, a)

Naive usage of it with withEffToIO with any unlift strategy cause error version (5) /= storageVersion (0) for me.

I'll send a PR

For the record, I adjusted your PR in 376a121 by adding your variants instead of replacing the original function with them since they add an overhead of cloning the environment.


Need Border for mask

Please add a border around the mask.

The purpose is to mask, not to create borders.


Object browser issue

👉🏻 Issue text goes here.
We are trying to evaluate VS code for IBMi development in our CVS IBMi application before rolling the same out for DEV usage.
While performing the evaluation we ran into some issues, reaching out to this group to get feedback for resolving these issues.
Let me know if there is a separate forum that I should use to log these items for feedback, we may have more such items in upcoming weeks. Thanks

Unable to add Object Browser Filter once added. Tried Right Click+Delete Filter but created filter is not getting removed. Did refresh and also tried restarting VS code but did not work.

Similar issue with Profiles, once a profile is created I am unable to delete/remove it.

In few of our machines, we are runing into issues with adding object brower/source filters. Getting error ‘CPC2957: No records copied from file O_C4ZSGSMW in ZU031055.
CPF2817: Copy command ended because of error.’
We have validated system temporary setting’s to ensure Temporary library(ZU031055) and Temporary IFS directory are setup correctly. This is holding many developers to evaluate Code for IBMi.

⚠ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠

Context
Version

Code for IBM i version
2.4.0

Visual Studio Code version
1.74.1

Operating System
win32_x64

Active extensions
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.3.2
Configuration Editing (configuration-editing): 1.0.0
Emmet (emmet): 1.0.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
JSON Language Features (json-language-features): 1.0.0
Merge Conflict (merge-conflict): 1.0.0
Microsoft Account (microsoft-authentication): 0.0.1
Node Debug Auto-attach (debug-auto-launch): 1.0.0
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
WSL: Recommender (remote-wsl-recommender): 0.0.18

Remote system

Setting
Value

IBM i OS
V7R4M0

Tech Refresh
n/a

CCSID
65535

SQL
Disabled

Source dates
Disabled

Enabled features

/QOpenSys/pkgs/bin
/usr/bin

/QSYS.LIB
/QIBM/ProdData/IBMiDebugService/bin

bash
attr
ZU031055.GETNEWLIBL
QZDFMDB2.PGM
startDebugService.sh

chsh
iconv

git
setccsid

ls
tar

md5sum

sort

stat

Shell env

Variants
{
  "american": "#@$",
  "local": "#@$"
}

Errors
[
  {
    "command": "system \"QSYS/CPYTOIMPF FROMFILE(ZU031055/O_C4zSGsMW O_C4zSGsMW) TOSTMF('/home/u031055/vscodetemp-O_TiCu1dVS') MBROPT(*REPLACE) STMFCCSID(1208) RCDDLM(*CRLF) DTAFMT(*DLM) RMVBLANK(*TRAILING) ADDCOLNAM(*SQL) FLDDLM(',') DECPNT(*PERIOD)\"",
    "code": 255,
    "stderr": "CPC2957: No records copied from file O_C4ZSGSMW in ZU031055.\nCPF2817: Copy command ended because of error.",
    "cwd": "/home/U031055"
  },
  {
    "command": "export BUILDLIB=\"QGPL\" && export CURLIB=\"QGPL\" && export USERNAME=\"u031055\" && export HOST=\"rxcdev\" && export HOME=\"/home/U031055\" && export LIBLS=\"SOFTMENU2X DBU11 SSAPRDOBJ SSAPRDFIL CDAPRDSRC CDAPRDFIL CDAPRDOBJ CDAQATOBJ CDADEVOBJ UTDPRDOBJ UTDPRDFIL UTCPRDOBJ UTCPRDFIL QUSRTOOL TAATOOL V2SYRPG V2SYCBL V2SYVENG V2SY Y28110524 V1SYVENG V1SY APIUTILS QATUTILS QGPL CLMPRDOBJ CLMQATOBJ CLMINDOBJ MSBDEVEXT CLMDEVEXT CLMDEVOBJ CLMDEVFIL COMPRDOBJ COMQATOBJ COMINDOBJ COMDEVOBJ COMDEVFIL APIPRDOBJ APIPRDSRC APIQATOBJ APIINDOBJ APIDEVOBJ APIDEVFIL MSBDEVFIL APICETFIL ELGDEVFIL EZTDEVFIL ECLDEVFIL O_Y2GEN70 O_Y2GEN86 V5R12EPTF1 RTOPRDOBJ RTOQATOBJ RTODEVOBJ QMOD APCSGPL APCSGPL2 CMKPRDGPL QTEMP\" && env",
    "code": 1,
    "stderr": "bsh: BUILDLIB=QGPL: is not an identifier",
    "cwd": "/home/U031055"
  },
  {
    "command": "export BUILDLIB=\"QGPL\" && export CURLIB=\"QGPL\" && export USERNAME=\"u031055\" && export HOST=\"rxcdev\" && export HOME=\"/home/U031055\" && export LIBLS=\"SOFTMENU2X DBU11 SSAPRDOBJ SSAPRDFIL CDAPRDSRC CDAPRDFIL CDAPRDOBJ CDAQATOBJ CDADEVOBJ UTDPRDOBJ UTDPRDFIL UTCPRDOBJ UTCPRDFIL QUSRTOOL TAATOOL V2SYRPG V2SYCBL V2SYVENG V2SY Y28110524 V1SYVENG V1SY APIUTILS QATUTILS QGPL CLMPRDOBJ CLMQATOBJ CLMINDOBJ MSBDEVEXT CLMDEVEXT CLMDEVOBJ CLMDEVFIL COMPRDOBJ COMQATOBJ COMINDOBJ COMDEVOBJ COMDEVFIL APIPRDOBJ APIPRDSRC APIQATOBJ APIINDOBJ APIDEVOBJ APIDEVFIL MSBDEVFIL APICETFIL ELGDEVFIL EZTDEVFIL ECLDEVFIL O_Y2GEN70 O_Y2GEN86 V5R12EPTF1 RTOPRDOBJ RTOQATOBJ RTODEVOBJ QMOD APCSGPL APCSGPL2 CMKPRDGPL QTEMP\" && env",
    "code": 1,
    "stderr": "bsh: BUILDLIB=QGPL: is not an identifier",
    "cwd": "/home/U031055"
  }
]

You are on an older version of VS Code, 1.74. Please upgrade to 1.83.

Thanks Liam, are all these issues related to older version ?
Re-confirming as this object browser issue is not occurring  for all developers but few selective. Thanks

@digvijay2k2 It could well be. We generally only support ~0.03 versions of VS Code.


JRTB-3: added Command pattern for handling Telegram Bot commands

JRTB-3: added Command pattern for handling Telegram Bot commands


GetLatestTotalDataFromCountry

Awesome tool! I added the ability to pull from a country's total and not just provide a list of it's regions.

@josephglaspie Thanks. I really appreciate your efforts but this functionality was already there in the library. I think you missed the file locations.go.

@itsksaurabh I saw that but was pulling all the regions' data (for the usa that's a lot) and wanted pull the aggregated total from the country.

I was looking for the countries aggregated total like this:
  "latest": {
        "confirmed": 25489,
        "deaths": 307,
        "recovered": 0
    },

Have a good one!


Attach Cloudflare Zero Trust headers in API calls to Baby Buddy server

Issue #7
Allow setting of (optional) Cloudflare Zero Trust headers so that the Echo devices can talk to a Baby Buddy instance protected by CF Zero Trust using a Service Token.
Description of changes:
Attach CF-Access-Client-Id and CF-Access-Client-Secret headers to API requests from the Alexa skill to the baby buddy server.
This allows the user to specify the headers in the bin/setup.sh script (though in the future, presumably this should be optional, probably through some command line argument if it were to be merged).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Bear with me here as I'm not well versed in either TS or Alexa... my review basically suggests that we make the CloudFlare headers optional to support this.

Definitely can make it optional.  My initial PR was just my hacked up code so that I could get it to work.  I just created a commit that I believe makes the Cloudflare header support optional.  I believe I addressed the points you made in your initial review but let me know if you've got questions or any other concerns!
Thanks for the quick responses / review.

@cdubz any thoughts on this?

I was hoping @rplankenhorn could pop in and review but I will keep this in my queue and follow up soonish.

Ok after much fiddling I was able to get CZFT working with a test instance of Baby Buddy 🎉
This all looks good but it definitely is a hyper-specific use case. I think an ideal future state would be a configuration process allowing the user to define any number of arbitrary headers to send with API request.
An end result .env file could look like:
BABY_BUDDY_API_KEY=KEY
BABY_BUDDY_API_URL=URL
EXTRA_HEADERS=CF-Access-Client-Id,CF-Access-Client-Secret
EXTRA_HEADERS_VALUES=CLIENT_ID,SECRET

Maybe a comma-separated list of items would be limiting in some way but something like that.
Anyway! This Alexa skill itself is enough of a niche that I have no problem merging this as-is.

Definitely agree. I wouldn't want to add service specific configuration for every conceivable option in the future.
If this comes up again, I was thinking something like a json structure of header / values would be preferred. Can tackle that in the future when it comes up.
Thanks for taking a look! Will hopefully get the next patches lined up soon


Faker Truck Factor

As part of my PhD research on code authorship, we calculated the Truck Factor (TF) of some popular GitHub repositories.
As you probably know, the Truck (or Bus) Factor designates the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In our work, we consider that a system is in trouble if more than 50% of its files become orphan (i.e., without a main author).
More details on our work in this preprint: https://peerj.com/preprints/1233
We calculated the TF for Faker and obtained a value of 23.
The developers responsible for this TF are:
Francois Zaninotto - author of 26% of the files
John Was - author of 10% of the files
Bernhard Essl - author of 3% of the files
Hugo Fonseca - author of 3% of the files
Tz-Huan Huang - author of 3% of the files
Tim Düsterhus - author of 2% of the files
Roman Shvets - author of 2% of the files
umpirsky - author of 2% of the files
Domingo Oropeza - author of 1% of the files
ognjen miletic - author of 1% of the files
bazo - author of 1% of the files
Abu Ashraf Masnun - author of 1% of the files
Mikulas - author of 1% of the files
WouterJ - author of 1% of the files
toin0u - author of 1% of the files
Wim Vandersmissen - author of 1% of the files
pdaether - author of 1% of the files
AlesÌŒ FarcÌŒnik - author of 1% of the files
YAMANE Nana - author of 1% of the files
zaid-86 - author of 1% of the files
Huy TQ - author of 1% of the files
Ulrik Johansson - author of 1% of the files
Birkir Rafn Gudjonsson - author of 1% of the files
To validate our results, we would like to ask Faker developers the following three brief questions:
(a) Do you agree that the listed developers are the main developers of Faker?
(b) Do you agree that Faker will be in trouble if the listed developers leave the project (e.g., if they win in the lottery, to be less morbid)?
(c) Does Faker have some characteristics that would attenuate the loss of the listed developers (e.g., detailed documentation)?
Thanks in advance for your collaboration,
Guilherme Avelino
PhD Student
Applied Software Engineering Group (ASERG)
UFMG, Brazil
http://aserg.labsoft.dcc.ufmg.br/

#656

Holy crap

Sorry to open a duplicated issue!


Investigate how to add WebSocket to Python-Flask service

Motivation
WebSocket enables real-time update of the client. I used websocket with the Node-Express server developed for the SageBio Collaboration Portal to automatically update the content of a page without reload and to display real-time notification (e.g. another client sent a notification or changed permission to access an entity).

Using the package flask-socketio seems the way to go!


Update README.md

Added a dataset containing 1500 PubMed articles with 4409 annotated chemicals, 5818 diseases, and 3116 chemical-disease interactions.

Thanks!


os/mac/diagnostic: allow Ruby 2.6.10 on < Ventura

2.6.10 got backported to 11.7.1 and 12.6.1.
We'll bump the minimum when enough people have updated - it's been less than 24 hours.

Review period skipped due to critical label.

We'll bump the minimum when enough people have updated

Let's build a new portable Ruby for when we do this too 👍🏻

Well get a PR open for that today.


Question - New Grafana operator version and alerting support

Hello, I'm following new info about updating Grafana version with alerting support.
In this line there was a comment about plugin update.
https://github.com/Altinity/clickhouse-operator/blob/26f65d0f30e6ac83fa5fcb2d48a22086f6ad35c8/deploy/grafana/grafana-with-grafana-operator/grafana-dashboard-operator-cr-template.yaml#L16
It's merged long time ago and current version is here:
https://github.com/Altinity/grafana-plugin-repository/blob/ebd76585b7f8dea7b048e06da0718efb13877755/repo.json#L2173
So what's the status of this change? Is it still blocked by something else?
Thanks in advance for your reply.

yep, currently, we wait when grafana-operator will publish the next stable release which will contain https://github.com/integr8ly/grafana_plugins_init/pull/2 and grafana plugins init side container 0.0.3 version
you can try to install
GRAFANA_OPERATOR_VERSION=latest ./deploy/grafana/grafana-with-operator/install-grafana-operator.sh

change ./deploy/grafana/grafana-with-operator/grafana-dashboard-operator-cr-template.yaml, and run
./deploy/grafana/grafana-with-operator/install-grafana-with-operator.sh

Thanks for info. :+1:
I look forward to new grafana_plugins_init new stable version.


Alexa App Unable to Discover Node-Red Hub

Summary:
After adding the npm package node-red-contrib-amazon-echo, and following the setup instructions, as well as going through the applicable troubleshooting on the Wiki, I'm still unable to discover the hub. I'm able to access <IP_ADDRESS>:80/api/description.xml, which is the server I am running node-red on. The description.xml returns the device name that is in my flow.
Devices:

Alexa Android App - Using Device Discovery as well as audio command "Alexa, discover new devices"
CentOS 7 virtual machine running node-red (not docker as some of the other issues seem to relate to this configuration)
Windows 10 PC running node-red during my troubleshooting, same issue

Node-Red debug logging
[root@ANSON ~]# node-red
25 Jul 21:38:06 - [info]

Welcome to Node-RED
===================

25 Jul 21:38:06 - [info] Node-RED version: v1.1.2
25 Jul 21:38:06 - [info] Node.js  version: v14.6.0
25 Jul 21:38:06 - [info] Linux 3.10.0-1127.el7.x86_64 x64 LE
25 Jul 21:38:06 - [info] Loading palette nodes
25 Jul 21:38:08 - [warn] Missing node modules:
25 Jul 21:38:08 - [warn]  - node-red-contrib-alexa-local (0.3.24): alexa-local
25 Jul 21:38:08 - [info] Removing modules from config
25 Jul 21:38:08 - [info] Settings file  : /root/.node-red/settings.js
25 Jul 21:38:08 - [info] Context store  : 'default' [module=memory]
25 Jul 21:38:08 - [info] User directory : /root/.node-red
25 Jul 21:38:08 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Jul 21:38:08 - [info] Flows file     : /root/.node-red/flows_ANSON.json
25 Jul 21:38:08 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

25 Jul 21:38:08 - [info] Starting flows
  node-ssdp:server discovering all IPs from interface lo +0ms
  node-ssdp:server discovering all IPs from interface enp0s3 +1ms
  node-ssdp:server Will use interface enp0s3 +0ms
25 Jul 21:38:08 - [info] Started flows
  node-ssdp:server SSDP listening: { address: 'http://<IP_ADDRESS>:1900', interface: '<IP_ADDRESS>' } +239ms
25 Jul 21:38:08 - [info] Server now running at http://<IP_ADDRESS>:1880/
25 Jul 21:38:08 - [info] [mqtt-broker:909c3b6c.3fc918] Connected to broker: mqtt://<IP_ADDRESS>:1883
  node-ssdp:server Sending an advertisement event +3s
  node-ssdp:server Setting LOCATION header "http://<IP_ADDRESS>:80/description.xml" on message ID 0720b8ddc86747be +1ms
  node-ssdp:server Sending a message to <IP_ADDRESS>:1900 +2ms
  node-ssdp:server Sending an advertisement event +2ms
  node-ssdp:server Setting LOCATION header "http://<IP_ADDRESS>:80/description.xml" on message ID 1a04eae8c931faeb +0ms
  node-ssdp:server Sending a message to <IP_ADDRESS>:1900 +0ms
  node-ssdp:server Sending an advertisement event +1ms
  node-ssdp:server Setting LOCATION header "http://<IP_ADDRESS>:80/description.xml" on message ID 7e5b3b689398f6bf +0ms
  node-ssdp:server Sending a message to <IP_ADDRESS>:1900 +1ms
  node-ssdp:server Outgoing server message: { message: 'NOTIFY * HTTP/1.1\r\n' + 'HOST: <IP_ADDRESS>:1900\r\n' + 'NT: upnp:rootdevice\r\n' + 'NTS: ssdp:alive\r\n' + 'USN: uuid:00112233-4455-6677-8899-60be5a8449c344::upnp:rootdevice\r\n' + 'CACHE-CONTROL: max-age=1800\r\n' + 'SERVER: node.js/14.6.0 UPnP/1.1 node-ssdp/4.0.0\r\n' + '\r\n', id: '0720b8ddc86747be' } +4ms

Description.xml:

Node-Red flow
[{"id":"d7ef8621.922dc8","type":"tab","label":"Send NRF24L01","disabled":false,"info":"Send data to NRF24L01 topic"},{"id":"cbcade4e.b0b5f","type":"mqtt out","z":"d7ef8621.922dc8","name":"","topic":"","qos":"","retain":"","broker":"909c3b6c.3fc918","x":710,"y":200,"wires":[]},{"id":"787ec2b0.536c9c","type":"inject","z":"d7ef8621.922dc8","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"10","crontab":"","once":true,"onceDelay":0.1,"topic":"nrf24l01/bedroomlight","payload":"off","payloadType":"str","x":390,"y":200,"wires":[[]]},{"id":"fc017a21.0ebc58","type":"inject","z":"d7ef8621.922dc8","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"10","crontab":"","once":true,"onceDelay":"20","topic":"nrf24l01/bedroomlight","payload":"on","payloadType":"str","x":320,"y":260,"wires":[[]]},{"id":"a4446a01.a73198","type":"debug","z":"d7ef8621.922dc8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":830,"y":340,"wires":[]},{"id":"6bc8ba79.f212b4","type":"mqtt in","z":"d7ef8621.922dc8","name":"","topic":"nrf24l01/bedroomlight","qos":"2","datatype":"auto","broker":"909c3b6c.3fc918","x":580,"y":340,"wires":[["a4446a01.a73198"]]},{"id":"60be5a84.49c344","type":"amazon-echo-hub","z":"d7ef8621.922dc8","port":"80","processinput":0,"discovery":true,"x":250,"y":100,"wires":[["4a9011f9.b8e65"]]},{"id":"4a9011f9.b8e65","type":"amazon-echo-device","z":"d7ef8621.922dc8","name":"Bedroom Light","topic":"nrf24l01/bedroomlight","x":490,"y":80,"wires":[["cbcade4e.b0b5f"]]},{"id":"909c3b6c.3fc918","type":"mqtt-broker","z":"","name":"","broker":"<IP_ADDRESS>","port":"1883","clientid":"","usetls":false,"compatmode":false,"keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","closeTopic":"","closeQos":"0","closePayload":"","willTopic":"","willQos":"0","willPayload":""}]
Is there anything I've missed? I've gone through many of the issues with these and unfortunately I have struggled to find one that matches my exact setup. I'm running node-red as root, and am able to access the description.xml from all devices on my network (mobile phone running Alexa app, my PC, etc.). I can run Wireshark on my network but I wasn't able to identify the filters to show only Alexa App related traffic.
Any advice would be greatly appreciated!

Seems it's a common issue for whom running NR with root permissions. NR stuff recommend to install without root

Just updating, I've nuked and reinstalled Node-red, NodeJS and NPM all without installing under root permissions.
I'm now running node-red without root permissions, which as expected doesn't allow it to bind to port 80. I haven't yet bound port 80 to the app directly, but running node-red with sudo (as before) doesn't change anything.

please follow what they clearly reccomend, do not run node red with sudo and do not install it as root, in both cases I suppose it uses different path. Simply start node red with the line node-red-start
Do the nat of port 80 as we did too

Just confirming, I have not run node-red with sudo and I have not installed it as root. I also have not installed any packages through node red, all of them managed through npm. I don't believe a NAT of port 80 will help

You need the NAT on port 80, else it will not work. Without root you can't open a port lower than 1024, and you need 80.

Same issue using docker with node setcap to use port 80 with nodered user and macvlan to use own IP
Dockerfile

FROM nodered/node-red:latest
USER root
RUN setcap 'cap_net_bind_service=+ep' $(eval readlink -f which node)
USER node-red
COPY package.json .
RUN npm install --unsafe-perm --no-update-notifier --no-fund --only=production

Run fixed nodered
docker build . -t juampe/node-red
docker run  --init -d --restart=always --network=macvlannet --ip <IP_ADDRESS> --dns <IP_ADDRESS> --hostname="nodered" --name="nodered" -v /opt/docker/nodered/data:/data  -e NODE_RED_ENABLE_SAFE_MODE=false -e DEBUG="node-ssdp:*" juampe/node-red:latest

From other host in the same net SSPD seems to respond  to multicast (upnp UDP 1900)
gssdp-discover -i br0 --timeout=5
resource available
  USN:      uuid:00112233-4455-6677-8899-cd272225bd01a8::upnp:rootdevice
  Location: http://<IP_ADDRESS>:80/description.xml
resource available
  USN:      uuid:00112233-4455-6677-8899-cd272225bd01a8::urn:schemas-upnp-org:device:basic:1
  Location: http://<IP_ADDRESS>:80/description.xml
resource available
  USN:      uuid:00112233-4455-6677-8899-cd272225bd01a8
  Location: http://<IP_ADDRESS>:80/description.xml

curl http://<IP_ADDRESS>:80/description.xml
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
  <specVersion>
    <major>1</major>
    <minor>0</minor>
  </specVersion>
  <URLBase>http://<IP_ADDRESS>:80/</URLBase>
  <device>
    <deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
    <friendlyName>Philips hue (<IP_ADDRESS>)</friendlyName>
    <manufacturer>Royal Philips Electronics</manufacturer>
    <manufacturerURL>http://www.philips.com</manufacturerURL>
    <modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
    <modelName>Philips hue bridge 2012</modelName>
    <modelNumber>1000000000000</modelNumber>
    <modelURL>http://www.meethue.com</modelURL>
    <serialNumber>93eadbeef13</serialNumber>
    <UDN>uuid:00112233-4455-6677-8899-cd272225bd01a8</UDN>
    <serviceList>
      <service>
        <serviceType>(null)</serviceType>
        <serviceId>(null)</serviceId>
        <controlURL>(null)</controlURL>
        <eventSubURL>(null)</eventSubURL>
        <SCPDURL>(null)</SCPDURL>
      </service>
    </serviceList>
    <presentationURL>index.html</presentationURL>
    <iconList>
      <icon>
        <mimetype>image/png</mimetype>
        <height>48</height>
        <width>48</width>
        <depth>24</depth>
        <url>hue_logo_0.png</url>
      </icon>
      <icon>
        <mimetype>image/png</mimetype>
        <height>120</height>
        <width>120</width>
        <depth>24</depth>
        <url>hue_logo_3.png</url>
      </icon>
    </iconList>
  </device>
</root>

"Alexa please search new devices" seems not work to find the hub

Ok I found the poblean and is realated to a  Malfunctioning Switch with  a bad IGMP Snooping from Wifi Acces Point
I disabled IGMP Snopping from the switch and Alexa can found my devices

Glad you solved this tricky problem,
@datech it would be useful I guess to put this solution on troubleshooter too

Were you able to discover node red devices without an Echo device, just using the Alexa Android app?
My situation is very similar to yours, I can open description.xml successfully, but Alexa app doesn't find any devices. I'm not sure if not having any Echo devices in my network could by the root problem.

Were you able to discover node red devices without an Echo device, just using the Alexa Android app?
My situation is very similar to yours, I can open description.xml successfully, but Alexa app doesn't find any devices. I'm not sure if not having any Echo devices in my network could by the root problem.

Same issue using docker with node setcap to use port 80 with nodered user and macvlan to use own IP
UPDATE: Ok I found the problem and it is realated to a malfunctioning switch with a bad IGMP Snooping implementation, that causes deny unicast/multicast from Wifi Acces Point ethernet port I disabled IGMP Snopping from the switch and Alexa can found my devices. Thanks!

Thank you for this, it may have been my issue too.
I have NR setup in Docker with its own IP address, listening on port 80. Occasionally the Echo Dot would pickup new devices but it was unreliable so I never got past the testing phase. The first 'discover devices' after completely disabling IGMP snooping on my switch and several new devices were found (some from my existing ZigBee gateway).


Dynamically change style (background color) of input field on button click

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x ] support request

Current behavior

When I added the code below to change the color of an input field when a tag input is clicked, the color of the input field is not changed, what else do I need?
addonRight: {
class: 'fa fa-code',
onClick: (to, fieldType, $event) => {
this.showInputSelector(to, fieldType, $event);
},
}
showInputSelector(to, fieldType, $event) {
   fieldType.field.templateOptions.attributes.style = "background: green; border-color: green;";
   to.placeholder = "test";
    $event.stopPropagation();
}

Expected behavior

Update color of input field
Minimal reproduction of the problem with instructions

https://stackblitz.com/edit/angular-objr91
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.X

Angular 4

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

Node (for AoT issues): node --version =

fixed in 5.0.0-beta.3, in order to take account of attributes you have to override it:
fieldType.field.templateOptions.attributes = {
  style: "background: green; border-color: green;"
};

Thanks..works very well.


getmetatable ignores __metatable flag in typechecker

With the following code (image required)

When indexing the V field, the getmetatable type emits the defined metatable object, instead of the type of the __metatable field if its defined
This happens with both solvers, but I guess the V1 solver is now obsolete /shrug

Are you really sure that this is a bug? It looks expected to me, but maybe I am misunderstanding the issue.


A.25.IR31.TGR26.datasetFeedDownloadLink, A.28.IR31.TGR29.datasetFeedDownloadLinkDetails

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
These seem to overlap significantly.
Proposed Change
Consider to merge both test cases.

Agreed, but my proposal is not to change anything. The overlap is already mentioned in the Notes of A.28.IR31.TGR29.datasetFeedDownloadLinkDetails.md:

this overlaps with TG Requirement 26. This requirement gives more details about how to encode the link.

For the ATS it is important to have tests for each requirement (if feasible). The overlap can be solved on the executable test level.

However, we could also request a change in the TG, because of this overlap.
TG Requirement 26 and 29 could be combined I think.

No comments received.
Conclusion: Don't change anything in the ATS. Request a change in the TG to combine requirement 26 en 29.


Proposal for fixing #464 - invalid XML in output.

This fixes the issue with invalid characters in the XML output.
I guess it could also be fixed by overloading the toString function - that is maybe a better solution, as this quickfix has a performance cost since all strings are parsed...

Sorry - looks like I referenced this issue in a commit a while back but never followed up to make sure it was now addressed. Is this still outstanding or is it covered by that commit? (IIRC I did it differently as I used a more integrated approach that, I believe mitigates the extra performance overhead, amongst other things).

In the year and a half since this was open, XML handling has been completely overhauled and there is no test case here to recheck.
If this is still problem, please open a new issue/PR.


Missing title for  tag; "lang" and/or "xml:lang" attribute for html tag; HTML title for project

Missing title attribute for  tag under test>url.html
Missing "lang" and/or "xml:lang" attribute for the tag under test>url.html
Missing html title under test>url.html

Bug fixed on 9918a74


Fixing Depreciation, Saving and Performance Tweaks

I can break this up, but simply this fixes:

Django deprecation warnings.
A previous commit broke sql and profile saving entirely.
Stop attaching the profiler every run if not used.
Better update of total queries (Though this really could be refactored into one update)

@Wrhector Thanks for fixing the broken collection. Truly was a mistake on my part. Also, I appreciate the effort to the project.
In the interest of progress I have decided to to merge it in!

@Wrhector 958d843 breaks django=1.7.x, is this version of django no longer supported?

Django 1.7 has been end of life for 6 months now, though oddly travis passed checks with Django 1.7, I'll write a patch to support both.

@Wrhector I already sent a patch, thanks


Remove rkyv features from rkyv_dyn

This is only partly actionable.
The archive_le and archive_be features can be removed from rkyv_dyn since it pulls all its endianness from rkyv.
The harder part is removing the strict feature. Ideally, this should be completely controlled by rkyv and everything else should pull from the source. I think the only way to do this might be to export a macro or proc-macro that adds #[repr(C)] if strict is on in rkyv. This is yucky.

Moving this out of rkyv's 0.8 milestone


Nevermind - Fixed some issues with PM2 on reboot

I had 2 issues with PM2 :

The script generated by pm2 startup was using the wrong user (root instead of pi)
The dump file containing the applications to ressurect was set to empty by PM2 when rebooting, therefore the applications where not starting automatically when rebooting manually

So I made 2 changes to rpi-2-install.sh script.
This might need to be tested on distro others than raspbian.

Thanks for the PR ! I'll look at it this week.

Be careful, don't mix PR ! If you want to correct minor bugfix, correct in another PR :)

I konw, but when I clicked on "Create a PR" on my repo, it asked for a title (that was different than this one) and then when i submitted it was merged with the first PR. Don't know why. Is it because the previous was still open ?

I get it, I think I should have make a branch for each PR. Can't undo it unfortunately.

PR to delete as I did another one cleaner. I can't delete the PR on my side.


Add shields to readme

Build
TODO counter

While you're at it, fix the rest of the readme. Something's gone awry with the code delimiters.

I think this looks better than the code-block for the guidelines tbh


Syntax highlighting

What:
Fixes #113. This PR adds support for syntax highlighting of additional pragmas (js, bash, html).

Why:
Static code blocks; such as npm install glamorous have no syntax highlighting.

How:

Include Prismjs (react-live component seems to utilize this, so this was chosen for consistency)
utils/highlighter.js decouples highlighting of code blocks from Prismjs and the underlying components that will render the highlighted code

functional approach: create a Prismjs specific highlighter, then Prismjs language specific highlighters, and use each of these for each of the new pragmas

update basics page for bash and html code block pragmas

This is my first PR into an OSS project! If there is any feedback you are able to give on direction, code quality, or really anything, it would be greatly appreciated.

test coverage is 100% for newly added functionality
-unfortunately, bash Prismjs support is not shipped with Prismjs and therefore requires an additional stylesheet. I do not particularly like including the stylesheet, but unsure of other options.

One unfortunate thing about using the pragma handlers and stuff is that it breaks out of the context of the markdown which busts out of the current context of HTML. Which means that if you nest a pragma inside HTML, you'll basically close the tags you're currently in. Ultimately this means you can't put a pragma inside of <details> which is unfortunate:

This is why there are clickToRender and summary options for the interactive pragma. Perhaps we could have the same thing for the others?

I was trying to keep the pattern for ClickToRender and CodePreview portions. I think I understand what you mean. Is this in the ball park of what you were thinking?
~~~js {summary: 'This is a summary'}
// some js code
~~~

I think it makes sense to do this; especially since the interactive and callout ones support this type of functionality. Assuming I understand correctly, I will update the PR with that functionality. Thanks!

I'm thinking that you'd have to opt-into it more though, so:
~~~js
// some js code
~~~

That would render as we do now, and
~~~js {clickToRender: true, summary: 'This is a summary'}
// some js code
~~~

That would render in the clickToRender thing :)

I opened a new PR #125 that is the successor to this thread. In hindsight, I should have simply left this PR open, so not to split up the conversation around it.


settings: Update label for realm-level default of send_read_receipts.

This PR updates the label for realm-level default of send_read_receipts as discussed here.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @sahil839!


Remove iOS copy of CSSLayout, update podspec

We're checking in a central copy of css-layout under ReactCommon. @astreet already made the xcodeproj point at it, now we can actually remove the code copy (pending internal changes).
I've also updated the Podspec to deal with the new location and fixed the xcodeproj and Podspec to handle <CSSLayout/CSSLayout> includes correctly.

cc @alloy, would you mind checking the Podfile? It works alright when I test it locally through :path but fails when I run pod lib lint

Landing internally.


docs: add documentation for temporary branch strategy

Description
Adds documentation for our temporary branching strategy during the dialtone 8 migration, since it is rather confusing and will remain this way until all applications are migrated.
View as rendered markdown here: https://github.com/dialpad/dialtone/blob/4adcb10cfd8dd2eab0af8fe2765beb7f84a8a808/migration_guide/temporary_branch_strategy.md
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Nice! we were missing this documentation so much. Should the dialtone-vue part be added to dialtone-vue too? I don't think its necessary as this is mostly internal, just for us, but asking just in case.

Probably not necessary since it's just internal, I'd rather keep it one place


Uncaught Error: Pane items must be objects. Attempted to add item undefined.

Steps to reproduce:

Add a new empty pane to the layout using e.g. Cmd-K Cmd-L Cmd-2.
Attempt to move an open tab to the new empty pane, not realizing that focus is still on the empty pane, using Cmd-K Cmd-M Cmd-2.

Atom Version: 1.0.2
System: Mac OS X 10.10.4
Thrown From: pane-manager package, v0.1.5
Stack Trace
Uncaught Error: Pane items must be objects. Attempted to add item undefined.
At /Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:311

Error: Pane items must be objects. Attempted to add item undefined.
    at Pane.module.exports.Pane.addItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:311:15)
    at Pane.module.exports.Pane.moveItemToPane (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:427:19)
    at Function.module.exports.PaneUtilities.moveItemTo (/Users/lawrence/.atom/packages/pane-manager/lib/pane-utilities.coffee:73:55)
    at Object.module.exports.moveToPane (/Users/lawrence/.atom/packages/pane-manager/lib/pane-manager.coffee:228:41)
    at atom-workspace.<anonymous> (/Users/lawrence/.atom/packages/pane-manager/lib/pane-manager.coffee:123:24)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:241:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:520:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:355:22)
    at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:177:20)

Commands
     -0:07.0 core:close (atom-text-editor.editor.is-focused)
     -0:04.0 pane-manager:changeLayoutTwo (atom-text-editor.editor.is-focused)
     -0:01.5.0 pane-manager:moveToPaneTwo (atom-pane.pane.active)

Config
{
  "core": {
    "themes": [
      "one-light-ui",
      "one-dark-syntax"
    ],
    "disabledPackages": [
      "cursor-count",
      "cursor-count",
      "incremental-search",
      "emmet"
    ]
  }
}

Installed Packages
# User
emmet-simplified, v2.4.2
jshint, v1.3.9
language-ejs, v0.2.0
linter-tidy, v1.0.1
minimap, v4.10.1
pane-manager, v0.1.5
pigments, v0.8.3
tidy-tabs, v0.2.0

# Dev
No dev packages

This is sort of caused by user error, because the focus wasn't on the pane I intended to move from; but of course it would be nice if the attempt did nothing rather than pop up an uncaught error dialog.
It would be even nicer if the command automatically moved the active tab in the last-used non-empty pane. :)

Since version 1.0, I can't reproduce your bug, I think its fixed via the JD342's PR.

In 1.0 it no longer throws an error, but the desired behavior still doesn't happen. JD342's PR is about moving a file to a pane that already exists. My repro steps are about creating a new pane, and then attempting to move a file to it.

If I understand well, to desired behavior is to get back the focus to the element which has it before the split, right?

Yes, exactly.

Ok, thanks.
I'm on it.

Thank you!

Fixed with version 1.0.1.
 I feel terrible for the long delay on this.


add unit test cases about mariadb;

Changes proposed in this pull request:
add unit test cases about mariadb;

Pull Request Test Coverage Report for Build 9130

0 of 0   changed or added relevant lines in 0 files are covered.
78 unchanged lines in 15 files lost coverage.
Overall coverage increased (+0.6%) to 64.656%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/sql/execute/result/DistinctQueryResult.java
1
98.0%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/sql/execute/result/MemoryQueryResult.java
1
97.83%

sharding-core/sharding-core-optimize/src/main/java/org/apache/shardingsphere/core/optimize/sharding/statement/dml/ShardingInsertOptimizedStatement.java
1
76.92%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/InsertCipherNameTokenGenerator.java
1
93.75%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/InsertQueryAndPlainNamesTokenGenerator.java
1
96.77%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/SelectEncryptItemTokenGenerator.java
1
96.15%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/WhereEncryptColumnTokenGenerator.java
1
97.5%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/org/apache/shardingsphere/shardingjdbc/orchestration/internal/datasource/AbstractOrchestrationDataSource.java
1
97.5%

sharding-transaction/sharding-transaction-2pc/sharding-transaction-xa/sharding-transaction-xa-core/src/main/java/org/apache/shardingsphere/transaction/xa/XAShardingTransactionManager.java
1
67.44%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/InsertSetCipherColumnTokenGenerator.java
2
92.0%

Totals

Change from base Build 231:
0.6%

Covered Lines:
9090

Relevant Lines:
14059

💛  - Coveralls

Thank you for contribution.


Improve the main readme

beautify the current readme

Can I work on this

Hi Akshita! I worked on this issue previously :) and made a mistake while making a pull request, Can you check again and then tell the other person to make changes if needed, otherwise both works will go in vein :) thank you!

Closing this issue

Hello Akshita, Can I add some custom made banner or something in the readme file ? and if yes can you create a issue for the same, I'll happily contribute


Add additional callbacks for SharedPV handlers

This PR adds three new callback functions for use by SharedPV (p4p.server.raw) handlers. They are:

open() - called when a SharedPV is opened
post() - called each time a post operation is performed on a SharedPV
close() - called when a SharedPV is closed.

The associated changes to the p4p.server.raw.Handler class, additional new decorators, and unit tests (src/p4p/test/test_sharedpv.py) are included. The changes to src/p4p/server/raw.py are relatively minor but the examples and unit tests make this look like a much bigger PR! There was some initial discussion of the idea at #150.
Three examples that make use of the new callback functions are also included:

example/auditor.py - demonstrates using open() and close() callbacks along with the existing put() callback to record when an auditing PV that records who's made changes to other PVs is or isn't available. Probably redundant compared to the more complex example/persist.py.
example/ntscalar_control.py - implements the Control field logic for an NTScalar. This illustrates how put(), post(), and open() lead to a natural separation of concerns. Logic that does not depend on the previous state of the PV may be implemented in the handler open(), e.g. altering the value dependent on control.limitHigh and control.limitLow. Logic that depends on the current state of the PV and the proposed changes may be implemented in the post(), e.g. applying control.minStep. The put() may then be solely concerned with authorisation.
example/persist.py - demonstrates using an SQLite3 database to automatically save and restore the values of PVs. Makes use of the new handler_open_ and handler_post_ prefix arguments to make configuration convenient and to transmit information from a put() to a post() respectively. Makes full use of the new open() callback to automatically restore the value and timeStamp information of a PV and post() to automatically record this information each time it changes.

I believe the example/persist.py file probably makes the strongest case for the kind of new features that these callbacks allow or make easier.
Breaking Changes
I believe these changes may be considered largely backwards compatible. They will only cause compatibility issues:

if an existing handler implements open(), close(), or post() functions.
if a PV includes top-level fields names beginning with handler_open_ or handler_post_.

It was suggested at a meeting on 9 Oct that I tag @coretl and @AlexanderWells-diamond for attention or review. Apologies if this comes as a surprise!


fork utest, unfreeze Scala.js

fyi @sjrd

Jenkins is busy carving the Buddha from a grain of rice, but I'm doing a local test run


How to deal with the need for Nx4 data of some materials

Intro
With vertex buffers, if a shader input is vec4, and the vbo has Nx2, the z and w element will be zero. This works, because for vertex buffers we provide additional information about the striding of the data. With storage buffers (aka SSBO) we just have some bytes that read from/write to in the shader. This means the data must match with what the shader expects.
There is also a thing with vec3's being padded to 16 bytes. Things are confusing:

It looks to me like the Khronos docs say that this padding does not occur when using std430 memory layout.
But if I create a glsl shader with a vec3-array buffer and compile it to SpirV, then I see it's ArrayStride always being 16.
I added some code in PyShader to annotate the array's stride to 12, but that does not help (the context gets lost in both cases).
also see this

I think that even if we do find a way to use vec3-arrays in storage buffers, we probably should not, because I would not feel confident that all drivers support it. Plus it might cause trouble for people who want to write shaders in glsl.
The situation
In short, the rendering of some materials (e.g. lines) require the buffers data to match with the shader, and cannot use vec3.
Options
More a list of ideas. We may use a combination of these:

Test and require these restrictions in the render functions where they're needed.
Require these restrictions always.
Disallow Nx3 arrays.
Render functions to which this applies can also implement both 2D (vec2) and 3D (vec4) versions.
Autoconvert data. E.g. positions and colors always become Nx4 when doing Geometry(positions=[[1,2], [3,4], [5,6]])
Add padding for Nx3 data when it's uploaded.
Provide a function that makes it explicit but easy to convert data.
The 4th element can be used for other means.

Mmm, instead of using (pyshader.RES_BUFFER, (0, 2), Array(vec4)), we can use an array of f32, and sample each element from the 1D array in the shader. If we go that route, we could e.g. force all position data to be 3D (which would be alright, I think).

We basically did what I suggested in the last comment.


First stab at application of document analysis settings

The analysis settings in this PR represent a fairly simple (but hopefully not totally unreasonable) first stab; I fully expect the analysis settings to change as we make further progress and learn more through test searches. A new dockerfile for ES + installed plugin as well as a docker-compose file for the ES+Kibana stack are provided to facilitate testing.

@mhl10 We went ahead and merged so we could work with it right away


Why based on RNet, is it feasible to use ONet? Because I think it looks like ONet is more accurate。

@Royzon It depends. The reason I use RNet is that it is fast and has a not bad accurate.


you can go past stair teleports to cheese hijack

Description
Building a chair and then sitting on it allows for you to get past the teleporters, allowing you to sit back and watch as xenos helplessly try to run at you.
https://github.com/user-attachments/assets/e98e7da6-61f6-4b27-89c8-534f18b04ade

dupe of armoks issue

No, can't find an exact issue, the other one is about permanence. This is about an exploit with teleportation.

No, can't find an exact issue, the other one is about permanence. This is about an exploit with teleportation.

this one? #3728

You're right


social network links are not active

same for CGU and privacy
https://talao.co/md_file?file=privacy
https://talao.co/md_file?file=terms_and_conditions
https://www.facebook.com/TalaoDAO/
https://twitter.com/Talao_io
https://t.me/TalaoCommunity
<EMAIL_ADDRESS>

and "Follow use" to change to "Follow us" in the footer

done


Trying power calc but having this issue

Please see log of process
2021-11-05 07:53:22,658 [INFO] Selected powermeter: tasmota
2021-11-05 07:53:22,659 [INFO] Selected Light controller: hass
2021-11-05 07:53:22,664 [DEBUG] Starting new HTTP connection (1): <IP_ADDRESS>:8123
2021-11-05 07:53:22,670 [DEBUG] http://<IP_ADDRESS>:8123 "GET /api/ HTTP/1.1" 200 35
2021-11-05 07:53:22,673 [DEBUG] Starting new HTTP connection (1): <IP_ADDRESS>:8123
2021-11-05 07:53:25,711 [DEBUG] http://<IP_ADDRESS>:8123 "POST /api/config/core/check_config HTTP/1.1" 200 42
2021-11-05 07:53:25,717 [DEBUG] Starting new HTTP connection (1): <IP_ADDRESS>:8123
2021-11-05 07:53:25,804 [DEBUG] http://<IP_ADDRESS>:8123 "GET /api/states HTTP/1.1" 200 148701
? Select the color mode?  brightness
? Do you want to generate model.json?  Yes
? Specify the full light model name  aa
? Which device (manufacturer, model) do you use to take the measurement?  aaa
? Do you want to gzip CSV files?  Yes
? Are you measuring multiple lights. In some situations it helps to connect multiple lights to be able to measure low cu
rrents.  No
? Select the light?  (Use arrow keys)
❯ light.amirlight
light.backdoor_light
light.balcony_room_balcony_light
light.balcony_room_light_1
light.balcony_room_light_2
light.balcony_room_light_3
light.balcony_room_light_4
light.browser_mod_0041c973_a6987460
light.browser_mod_06502d15_7f90c071
light.browser_mod_08172c6c_0a6882b3
light.browser_mod_08782156_ac4ff6e0
light.browser_mod_0c5e8ef3_1e6cb908
light.browser_mod_14a89de3_5756074c
light.browser_mod_169d1ad1_6476ccf0
light.browser_mod_372bf6b7_5f72fe1e
light.browser_mod_3b606df3_6665183f
light.browser_mod_5a01f79c_06547d98
light.browser_mod_5aa036e2_6fc1ba47
light.browser_mod_5d5a0bb0_eaf4ada1
light.browser_mod_5fac7583_b2ad72b6
light.browser_mod_5fd329ba_a97daebc
light.browser_mod_674bcf64_3d060958
light.browser_mod_6a3567a0_e945417e
light.browser_mod_89c934dc_ac78e213
light.browser_mod_8b3ab103_685e027b
light.browser_mod_94092165_584198fb
light.browser_mod_991fb5fa_e8254f74
light.browser_mod_9988e37a_42db0dca
light.browser_mod_9f1e8f8c_122deee4
light.browser_mod_a053e698_0068bf90
light.browser_mod_a150d472_f24187b1
light.browser_mod_a54fba09_8db1952c
light.browser_mod_ab7bf736_6fd86aa3
light.browser_mod_ace1997b_a8dbc0e0
light.browser_mod_ae75573a_885c5a1f
light.browser_mod_b2c69743_7b98015a
light.browser_mod_b46db178_20a5579d
light.browser_mod_bb11ace1_2e76db31
light.browser_mod_c0aeb2ef_b728f150
light.browser_mod_c0e4c5da_b3080bf9
light.browser_mod_c3383802_9bd4f6a0
light.browser_mod_c6799fef_c581f24f
light.browser_mod_caddaf23_053fa260
light.browser_mod_cb6b6ccd_0c2a9290
light.browser_mod_d5c92ae3_5902b626
light.browser_mod_d60325aa_b729d72f
light.browser_mod_d7cf00fb_208fc8b4
light.browser_mod_da2e8aba_87a3e540
light.browser_mod_dcd6d374_8747dbc7
light.browser_mod_ea62c14a_c7360eca
light.browser_mod_ec52f4bd_e42af21d
light.browser_mod_f3a6e58c_a738f8e3
? Select the light?  light.amirlight
? What model is your light? Ex: LED1837R5  aaaa
Traceback (most recent call last):
File "measure.py", line 488, in
main()
File "measure.py", line 485, in main
measure.start()
File "measure.py", line 110, in start
self.light_info = self.light_controller.get_light_info()
File "/app/light_controller/hass.py", line 34, in get_light_info
state = self.client.get_state(self._entity_id)
File "/usr/local/lib/python3.8/site-packages/homeassistant_api/client.py", line 207, in get_state
raise MalformedInputError(f"The entity_id, {entity_id!r}, is malformed")
homeassistant_api.errors.MalformedInputError: The entity_id, 'light.amirlight', is malformed

How exactly are you running the measure script? with docker or directly with Python? And are you using the latest version?

I was able to reproduce the issue. The bug is actually in an upstream library I am using to communicate with Home Assistant API. https://github.com/GrandMoff100/HomeAssistantAPI

Bug report created. https://github.com/GrandMoff100/HomeAssistantAPI/issues/47.

Bug Resolved: https://github.com/GrandMoff100/HomeAssistantAPI/issues/47#issuecomment-961838495

Thanks a lot @GrandMoff100
Fixed with #348. Will be in upcoming release v0.10.4

Amazing mate thanks


fix: Replace zip with "itertools.izip".

Since itertools.izip became obsolete in Python 3, this PR replace it by built-in zip() function.
Fixes #163

The master is built with python2 and Django=1.11.18, you can add this fix for python3 upgrade #58  #24 , or in the branch python3.


Unable to delete containers

There is a container that I can't delete, rancher will always start new one, even the whole stack is removed.
My rancher version is old:
Rancher v0.37.1
Cattle v0.91.1
User Interface v0.47.0
Rancher Compose beta/latest
I don't want to go update, so what else can I do to just remove the container. I think somewhere rancher kept the metadata about that service, and how can I delete the meta info.
Thanks

If you navigate to the API of the container, you should be able to find the associated service. Go to the API for that service and update the state to make it "Removed". It is most likely in "Active" state, which is why it keeps re-spawning.

@deniseschannon I couldn't find the API to update the service state, could you please point it out? Thanks for your help.

The url '…/v1/projects/1a32/services/1s454/?action=remove', I suppose it should be called to remove service 1s454, but clicking that link in browser doesn't remove the service at all.

@summerQLin what is the state of the service you are trying to remove (1s454)?
This issue is very similar to https://github.com/rancher/rancher/issues/2334

@summerQLin If you are still having this issue, please re-open.


[Snyk] Security upgrade urllib3 from 2.0.7 to 2.2.2

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

requirements-doc.txt

⚠ Warning
```
sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.
</details>

---

> [!IMPORTANT]
>
> - Check the changes in this PR to ensure they won't cause issues with your project.
> - Max score is 1000. Note that the real score may have changed since the PR was raised.
> - This PR was automatically created by Snyk using the credentials of a real user.
> - Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

**Note:** _You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs._

For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJiZDhjMGM3Yy0xZDk0LTRmZmEtYjI2Zi05ZWM4YjhmZTVhYWEiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImJkOGMwYzdjLTFkOTQtNGZmYS1iMjZmLTllYzhiOGZlNWFhYSJ9fQ==" width="0" height="0"/>
🧐 [View latest project report](https://app.snyk.io/org/fmigneault/project/1e732fcc-964b-4010-93a0-d380ee247094?utm_source=github&utm_medium=referral&page=fix-pr)
📜 [Customise PR templates](https://docs.snyk.io/scan-using-snyk/pull-requests/snyk-fix-pull-or-merge-requests/customize-pr-templates)
🛠 [Adjust project settings](https://app.snyk.io/org/fmigneault/project/1e732fcc-964b-4010-93a0-d380ee247094?utm_source=github&utm_medium=referral&page=fix-pr/settings)
📚 [Read about Snyk's upgrade logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities)

---

**Learn how to fix vulnerabilities with free interactive lessons:**

🦉 [Learn about vulnerability in an interactive lesson of Snyk Learn.](https://learn.snyk.io/?loc=fix-pr)

[//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"urllib3","from":"2.0.7","to":"2.2.2"}],"env":"prod","issuesToFix":[{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"exploit_maturity":"No Known Exploit","id":"SNYK-PYTHON-URLLIB3-7267250","priority_score":586,"priority_score_factors":[{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"6","score":300},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Improper Removal of Sensitive Information Before Storage or Transfer"}],"prId":"bd8c0c7c-1d94-4ffa-b26f-9ec8b8fe5aaa","prPublicId":"bd8c0c7c-1d94-4ffa-b26f-9ec8b8fe5aaa","packageManager":"pip","priorityScoreList":[586],"projectPublicId":"1e732fcc-964b-4010-93a0-d380ee247094","projectUrl":"https://app.snyk.io/org/fmigneault/project/1e732fcc-964b-4010-93a0-d380ee247094?utm_source=github&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"type":"auto","upgrade":[],"vulns":["SNYK-PYTHON-URLLIB3-7267250"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}'

Disabling Snyk check for this requirements file. Too many false positives. Already handled by upstream requirements installed before these optional ones.


Bootloader and upstream updates

This PR adds the following changes to XLink:

bootloader support (added new device, with a custom name: '[path]-bootloader')
upstream XLink changes from openvino (most of diff is changing direct prints to mvLog)
XLinkLog: support for Windows (setting mvLogDefaultLevel to MVLOG_LAST disables all messages on Windows as well)
Some const qualifier on public facing API
Added CI for Win, Mac and Linux for easier development

Merged to develop


Suggest troubleshooting tips when missing environment prerequisites

The first time I tried ignite new Project, my Android prerequisite was not found, which led to the Android build failing.

In my case, it came down to missing android in my PATH (when I installed RN ages ago, I don't think this wasn't needed), but I only figured that out by searching for similar git issues on this repo.
It would be super helpful to display suggestions to the user in the case of a missing prerequisite. For example, if Android is missing, some combination of these suggestions would be helpful:

Unable to find 'android' in your PATH.
Unable to find 'ANDROID_HOME' environment variable.
Make sure you've followed the latest react-native setup instructions at https://facebook.github.io/react-native/docs/getting-started.html before using ignite.
If you're only targeting iOS, you may continue now and set up Android another time. The Android files will all be generated, but the build will fail.

/gif IT SHALL BE DONE!

Bump, just installed it with $ANDROID_HOME in my path and still got the Missing android error.


Revert "FC054, check for mismatched cookbook names"

This reverts commit df3c89075bb407d8e96d7aef44e16a33c89fce78.
Chef 12 requires the name attribute so that the directory name may be renamed, so FC054 gets the spirit of requiring the name attribute backwards.
See discussion in #344

@danielsdeleo do you concur that FC054 should be pulled?

I'm pretty sure I agree, but I'm a little fuzzy on how well we support things like having multiple same-named cookbooks in a chef repo and using knife to upload them, which could be a reason you would care. What was the situation in which you encountered this? Also, I looked at the commit you referenced, which says:

In Chef 12 name metadata attribute needs to match cookbook dir name

which doesn't seem to be correct to me? I'm just all confused now :crying_cat_face:

Right, its not correct.
And we may have areas in knife where we expect the cookbook dir to match the cookbook name, or where we trust the cookbook dir over the cookbook name, but those are bugs in knife and/or just issues with the tool where the tool should be responsible for whining about the problem if it really can't be changed.
As far as foodcritic goes, I don't think we want to be enforcing this and should be encouraging those bugs to get fixed in the tooling.

Two notes, we should make sure that with the rule removed that doesn't break people that have filtered out this rules and we should make sure we never add a new FC054 for the same reason. Because of the latter it might be better to convert it to a stub rather than remove it fully?

@coderanger's suggestion seems good, is that how we've handled removals in the past?
Anyway, I'm convinced this rule can be removed, whatever the correct process is.

A comment in the rules file would probably work too, I have no strong opinions on how to accomplish that piece of things :)

comments are added.

:+1: :shipit:

Only prior art I can find is when FC001 was yanked and then restored, and the commit that yanked it just deleted it like this one does...

If this causes issues we can look at stubbing or ignoring overrides for rules that don't exist...

 You sent the PR and merged it in less than an hour. However, I'm going to wait until tomorrow morning so I don't do what you did.
Rules are configurable and people don't have to use them all... but this is a totally valid rule that can catch a horrible breakage.

I'm not Collaborator status here, but I agree with @jaymzh.  One of the beauties of this tool (and arguably it's primary purpose) is how is helps us avoid problems and mistackes, which includes not confusing yourself and your teammates.  Yes, we, as community should encourage the tool to establish a consistent source of truth (metadata or dir name) and rely only on that source of truth, but that doesn't change the fact that having a cookbook named bar in a directory named baz would confuse the hell out of most people, and just seems like you're asking for trouble.
The answer may be in @lamont-granquist's comment at the beginning of this thread:
"FC054 gets the spirit of requiring the name attribute backwards."
I thinkg there are two different issues trying to be addressed:

(correctness) Chef 12 requires the name attribute, so it must be properly defined and maintained.
(style) You will avoid a load of confusion and potential problems, if your directory names match your cookbook names.

The first sounds like FC045 needs to be worded more strongly and labeled as correctness rather than annoyances.
This (FC054) addresses the second and is valuable.
My $0.12  - inflation of $0.02 from 1971 to 2015   :-)

Well put. To put my less-angry more-explain-y post from #344 here:
Chef lets you do LOTS of things that aren't preferred that foodcritic warns you about. Like, for example putting an if around a resource. Sometimes that IS what you want, but often it's not, so we warn on it. Your argument that "it's supported" is invalid - of course it's supported... but it's LIKELY to be an error. Which is where linters come in.

This is the case of the thing where what's in metadata.rb is what's used and it's a really good idea to have the directory be named the same thing or your shit will probably break. And if you really want them to be different, to quote @lamont-granquist  from another bug yesterday, "then you know enough to disable the rule."

Correct me if I'm wrong, but it sounds like the actual thing you want to avoid is having two cookbooks with conflicting metadata?

What does that even mean? How would you know they are two different cookbooks? We specifically lint cookbooks individually (plus their depends) to catch missing dependencies, for example.
Though as a theoretical check, sure that would be nice, but no, it's not what I "really want", it's a neat additional thing.
What I really want is to NEVER upload a cookbook that looks like one thing but really is another thing. Lint is about best practice. Best practice is to name the cookbook directory the name of the cookbook.

The problem that I see is that this is a very context dependent rule.  It already bit @coderanger and he disabled all those checks.  All you have to do is download the cookbook to a different directory and foodcritic will fail the rule, making the rule not very portable.  I suspect that we'll immediately have to figure out how to disable the rule on supermarket.
I see your point, but I think it'll also cause lots of issues in fairly normal use cases.  I'd kind of like to know what @coderanger thinks since he already hit this one in actual practice.

When you download cookbooks ... it should go into a directory... as a directory. The cookbook is the entire cookbook directory. So if you download a CB to /tmp/test it should come down as /tmp/test/the_awesome_cookbook. If it doesn't, I'd say the tools are broken. You're welcome to disable rules you don't like. I disable the god awful 1.9 hash syntax rubocop rules and we disable about 10 or so FC rules... but this is definitely best practice for production.

The reason I have it disable is all my cookbooks live in temp folders so matching the name isn't an option. This isn't really a "best practice" in the way most of the others are, it's a workflow-specific error check.

It is also unlike all other rules as when I run foodcritic . I would not expect it look at anything outside of . but this does.

I'd be more inclined to have this rule in the codebase but disabled by default, then it could be enabled for specific workflows.

I'm not sure foodcritic has the concept of disabled by default, though, so that would probably be an additional feature patch...

having all our cookbooks in temp folders means they're not in a repo, which seems inandofitself poor practice. Thou shalt never edit things that are not in revision control.

@jaymzh In my case the actual cookbook is compiled output, not the thing in version control :) To be clear, my case is very much not the norm, but I still disagree with calling this a best practice. If you name your SCM folders something like ~/chef-whatever that would be totally in line with all best practices even when the cookbook is named whatever.

A lot of tooling also uses the_awesome_cookbook-1.2.3 and i'm pretty sure the tarballs uploaded to the community site to share have that as the directory.

The mandatory cookbook name stuff also came from the Berkshelf world and @sethvargo might be able to comment on that since he's also still a maintainer here as well...

@lamont-granquist  just like with any other software, when you cut a release you can make a directory with a given name. chef-client's repo doesn't have a directory called 'chef-12.4.1' ... it's just chef. When you export it from SCM to make a release you call it chef-12.4.1.

Yes but running foodcritic on a downloaded zip file from the Supermarket should work. Basically folder name == cookbook name doesn't apply in all cases and there isn't a compelling reason to tell people they should always match. I could see maybe saying that folder_name.include?(cookbook_name) is a more general rule, but I would still personally leave it disabled.

There isn't a compelling reason to tell people you should NEVER wrap an if around a resource either... SOMETIMES it's the right thing to do. There isn't a compelling reason to tell people to NEVER use a definition, sometimes it's the right thing to do. Your statement is totally valid, but completely orthogonal to whether this should be a rule.
Hmmm - maybe startswith?

There are downsides to not following those rules that are fairly universal whereas the mentioned folder names have zero downside outside of the specific workflow you mentioned.
starts_with? would block folder names like chef-whatever which IMO are fine. I've pretty often had ~/src/myapp for the application and ~/src/chef-myapp for the cookbook to deploy it.

I disagree... there's totally valid needs for if around a resource...
I suppose include? is probably good enough...

I use if around resources to avoid putting the resource on the resource collection because its just not an appropriate resource for the converging server.
The thing is that foodcritic works on that rule no matter what my workflow is.  When I override it, it is also fully encapsulated in the state of the cookbook and the override is also invariant and everyone who asks the same question gets the same answer.  This rule is pretty odd because like @coderanger pointed out it looks outside of '.' and depending on the different workflows you use, you can get a different answer.
This might be a good topic for discussion at the next community meeting.

I think with include? this would be generic enough to be enabled by default. I still would put it on a different tier than most of the other checks. I guess this is why Rubocop has error vs. warning vs. convention levels, but this is not the time or place to talk about adding that kind of thing :)

starts_with? is also vulnerable to name "foo" in a "foobar" directory matching and not triggering this rule when it should.   we could use foo-\d+-\d+-\d+ since cookbook versions are enforced to be 3 integers (although i really think we should change that at some point).

include? is also vulnerable to even more false negatives...

@lamont-granquist We need to match name, chef-name, name-chef, and name-1.2.3 at a minimum as those are all relatively common. I'll take false negatives over false positives given the nature of the check.

I like the idea of explicitly allowing common permutations...

I'm still thinking this kinda bikeshed is why we have the community meetings...

Sure, just trying to come up with a minimum check that will not throw errors for most people while still covering the specific case of "copy the cookbooks directory and forget to update the name" since that seems like the most important thing this will flag. include? seems like it fits that bill and would unblock a release.

Well, we can release it like it is and add FC054 back for 5.1.0 a week later or so (we could revert the revert for 5.0.0 and then revert the revert of the revert and release a 6.0.0 if we decide to a week later, but that seems like it would be more confusing to people).

@lamont-granquist  - too many pronouns - is "this" the above proposal, or with the revert, or as the original code was? I'd like to release with [some form of] this rule in there since we use it.

right, let's back out this reversion so that we ship 5.0.0 with FC054 included as-is.

yeah, after thinking about it over the weekend, what i'd really like to do in a perfect world is ship FC054 disabled, but FC doesn't have good support for optional rules and needs something like #290 merged at a minimum.  so given the choice between on-but-disable'able and not supported at all, i think it should be on, so so we revert the revert.  will work on that later today after the caffeine kicks in a bit more...

This is a good discussion. Clearly, some folks like and need this rule in order to prevent what are common breakages in their environment, while for others, this would break their existing (and supported explicitly by Chef 12) workflows. Here is how w'ere going to resolve it:

We are not going to ship this FC054
We are going to extend foodcritic to handle opt-in rules, rather than exclusively opt-out
Then we are going to merge FC054 as a default opt-in

Our reasoning here is two-fold:

You can extend foodcritic with custom rules today relatively easily
This rule has not shipped in a release, therefore it will do no harm in the broader community
Clearly we need to improve what rules can ship stock in foodcritic

Deciderated.
Love,
Adam


.*: Pre refine for supporting join spill in pipeline

What problem does this PR solve?
Issue Number: ref #6518
Problem Summary:
What is changed and how it works?

support  spilling blocks containing only constant columns.
support setting init task status for pipeline task, and the io event task can be submitted to io thread pool.

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-integration-test

/run-all-tests

/run-unit-test

/rebuild

/approve

/run-integration-test

/run-unit-test

/run-integration-test

/run-integration-test


Violations showing up in wrong accounts after application migration

Sometimes after migrating an application from one account to another violations of that application get still assigned to the old account. The new owners of the application don't see the violations which can lead to security issues.
Please see TGC-43 and TGC-50 in techjira for examples.

👍

I'm willing to InnerSource this if possible. Can someone explain to me where the bug is?

👍

The problem is, that it's not trivial to track if an application has actually been shut down. I was hoping to roll out the new GitHub approval flow quicker and just delete the check for MISSING_SPEC_LINKS in Fullstop, as it has some drawbacks.

That would be even better. Let me know if you need help with that.

Switching to the new GitHub flow is up to each individual team. They need to apply and will get an invitation from Tech Controlling. Please refer to our internal docs (Rules of Play) for details.

Oh, I see. You meant all teams need to switch to the Github flow. Do you recommend whitelisting our app then?

@nehalium yes, whitelisting is currently the best solution

:+1:

👍

As I promised: With complete rollout of the GitHub approval flow, the violation type in question has been removed entirely. This issue won't pop up anymore.

👍


HDDS-3822. Eliminate duplicated GitHub Actions workflow

What changes were proposed in this pull request?
Merge post-commit and pr workflows.  The only step which is unique to post-commit workflow is executed conditionally, depending on the event that triggered the run.
https://issues.apache.org/jira/browse/HDDS-3822
How was this patch tested?
push in fork:
https://github.com/adoroszlai/hadoop-ozone/runs/783452897
pr in apache:
https://github.com/apache/hadoop-ozone/pull/1090/checks?check_run_id=783788980

@adoroszlai Thanks for working on this! I always wanted to do this to avoid maintaining two workflows but didn't get the bandwidth. +1 LGTM

Thanks @vivekratnavel for the review, and @dineshchitlangia for reviewing and committing this.


Executing task fails with nushell set as default shell

I have Nushell set as my default shell in VS Code on Windows. When I run a test, I see the following:
 *  Executing task: phpunit.bat --colors=always 'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'

Error:
  × The system cannot find the file specified. (os error 2)

 *  The terminal process "C:\Users\Charles\scoop\shims\nu.exe /d /c phpunit.bat --colors=always 'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'" terminated with exit code: 1.
 *  Terminal will be reused by tasks, press any key to close it.

If I manually run the following command, it works:
cmd.exe /d /c phpunit.bat --colors=always 'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'

The extension works fine if I have Command Prompt, PowerShell, or Git Bash set as my default. Would it be be possible to force use of cmd.exe or detect if nushell is default?
The following commands work:
Executes and keeps nu running:
C:\Users\Charles\scoop\shims\nu.exe --execute 'phpunit.bat --colors=always "c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php"'

Executes and exits nu after finished running:
C:\Users\Charles\scoop\shims\nu.exe --commands 'phpunit.bat --colors=always "c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php"'

Note, I don't need the full path to nu.exe in the because I have it on my PATH.

I managed to get it working by adding the following to my settings.json:
  "terminal.integrated.automationProfile.windows": {
    "path": "pwsh.exe",
    "args": ["-NoProfile"]
  },

Note that I could not use cmd.exe because it does not like single quotes. Example:
Single quoted (cannot open file):
C:\Users\Charles>cmd.exe /d /c phpunit.bat --colors=always 'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'
PHPUnit 9.5.25 #StandWithUkraine

Cannot open file "'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'".

Double quoted (works fine):
C:\Users\Charles>cmd.exe /d /c phpunit.bat --colors=always "c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php"
PHPUnit 9.5.25 #StandWithUkraine

........                                                            8 / 8 (100%)

Time: 00:00.011, Memory: 10.00 MB

OK (8 tests, 9 assertions)

PowerShell, on the other hand, works with both single and double-quoted:
C:\Users\Charles>pwsh.exe -NoProfile -Command "phpunit.bat --colors=always 'c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php'"
PHPUnit 9.5.25 #StandWithUkraine

........                                                            8 / 8 (100%)

Time: 00:00.012, Memory: 10.00 MB

OK (8 tests, 9 assertions)

C:\Users\Charles>pwsh.exe -NoProfile -Command "phpunit.bat --colors=always "c:/Users/Charles/Dev/Exercism/php/hamming/HammingTest.php""
PHPUnit 9.5.25 #StandWithUkraine

........                                                            8 / 8 (100%)

Time: 00:00.011, Memory: 10.00 MB

OK (8 tests, 9 assertions)

Hi, I'm not very active in this repo unfortunately but I could accept a PR. It seems like two problems.

Make it work with nushell
Fix quotes for cmd (use double). The quotes are there now to work with spaces in path

I think the problem has to do with how vscode handles nushell since I'm running tasks and it will pick up the shell by default. And in your case it says that it tried running it like The terminal process "C:\Users\Charles\scoop\shims\nu.exe /d /c however from what you wrote it seems nushell doesn't have a /d /c arg and needs C:\Users\Charles\scoop\shims\nu.exe --commands.
Judging from that I assume vscode thinks nushell is cmd basically. But great you got it working with pwsh.


Update contributing guidelines to be more accessible

Resolves #414

Good point, I think it's more related to specific dev-changes than necessarily version release, so I added a check-box to the PR template for now (easy to delete the line when not relevant). We can see how that works! :wink: