neovim: 0.8.3 -> 0.9.0

Description of changes

Changelog: https://github.com/neovim/neovim/releases/tag/v0.9.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

cc @rvolosatovs @manveru

Most likely will need https://github.com/NixOS/nixpkgs/pull/225148 . Also are you able to build without libiconv ?

Most likely will need #225148 . Also are you able to build without libiconv ?

Indeed, I needed to update tree-sitter as well.
libiconv seems to be a darwin dependency only. I don't have a mac so I am not able to test the build without it.

The treesitter build fails for me with:
       >   = note: ld: framework not found CoreServices
       >           clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
       >
       >
       > error: could not compile `tree-sitter-cli` due to previous error
       For full logs, run 'nix log /nix/store/fpbb0vpl6dsbcl07rha38b1ni4r8wis6-tree-sitter-0.20.8.drv'.
error: 1 dependencies of derivation '/nix/store/jrfpcsii6il38cwdkvzk9334pk5g6axb-neovim-unwrapped-0.9.0.drv' failed to build

I think we need to add CoreServices to treesitter if it's on a mac.

I think we need to add CoreServices to treesitter if it's on a mac.

Done, can you try again please N

cc @raboof	for #214231

libiconv is added automatically on darwin by buildRustPackage because libc depends on it, so you don't have to add it explicitly

Are things like luv, luajit should also be updated? Neovim usually bumps them regularly.

Despite trying several GITHUB_API_TOKEN, I am getting Rate limited by the Github API...
If someone could run the tree-sitter grammar update that would be great !

it's GITHUB_TOKEN, not GITHUB_API_TOKEN

The dependencies are listed here https://github.com/neovim/neovim/blob/56e4d79b280b2da1c8d9705d2f300cd93e955f53/cmake.deps/CMakeLists.txt#L135 . Note the treesitter grammars that should be installed along with neovim. For now it's not a problem if they are not installed but it will be in a future release.

This PR builds and runs fine on my M1 mac.

cc @raboof for #214231

verified neovim-unwrapped is indeed properly reproducible without the patch on this version :tada: :+1:

Apologies, I wasn't overriding nixpkgs correctly in my derivative derivations. This builds just fine! :tada:

Apologies, I wasn't overriding nixpkgs correctly in my derivative derivations. This builds just fine! tada

Should I try to remove CoreServices again then ?

@GaetanLepage I think that it won't build without CoreServices. The change you made is necessary AFAICT. I ran nix build "github:teto/nixpkgs?rev=18adb220145f31f7b1bb507b13b7badb76f4c98b"#neovim which is just the derivation without CoreServices, and that fails to link. But this branch as it currently stands builds correctly.

I am not able to run nixpkgs-review pr 225152. Indeed, it fails for some reason and I am not dropped in the result shell.
It seems that a few packages are broken.
For instance, one test of nvimpager fails:
❮ nix-build . -A nvimpager
this derivation will be built:
  /nix/store/9g519gl3flbf2qadis0dhf3lcxgjfvdy-nvimpager-0.11.0.drv
building '/nix/store/9g519gl3flbf2qadis0dhf3lcxgjfvdy-nvimpager-0.11.0.drv'...
unpacking sources
unpacking source archive /nix/store/lczpm66faxaygvgnwjm5wknpki5pan24-source
source root is source
patching sources
configuring
no configure script, doing nothing
building
patching script interpreter paths in nvimpager
nvimpager: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/0hx32wk55ml88jrb1qxwg5c5yazfm6gf-bash-5.2-p15/bin/bash"
build flags: SHELL=/nix/store/0hx32wk55ml88jrb1qxwg5c5yazfm6gf-bash-5.2-p15/bin/bash PREFIX=\$\(out\) nvimpager.configured nvimpager.1
sed 's#^RUNTIME=.*$#RUNTIME='"'/nix/store/mvhvkh41cpfq52j22cxf5kp7bf4w7ws9-nvimpager-0.11.0/share/nvimpager/runtime'"'#;s#version=.*$#version=0.11.0#' < nvimpager > nvimpager.configured
chmod +x nvimpager.configured
sed '1s/$/ "nvimpager 0.11.0"/' nvimpager.md | scdoc > nvimpager.1
running tests
Script started, output log file is 'typescript'.
●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●◼●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
128 successes / 1 failure / 0 errors / 0 pending : 2.30485 seconds

Failure → test/nvimpager_spec.lua @ 241
pager mode starts up and quits correctly
./test/helpers.lua:44: command failed
Expected objects to be equal.
Passed in:
(string) '1
'
Expected:
(string) '0
'
Script done.
error: builder for '/nix/store/9g519gl3flbf2qadis0dhf3lcxgjfvdy-nvimpager-0.11.0.drv' failed with exit code 1;
       last 10 log lines:
       > pager mode starts up and quits correctly
       > ./test/helpers.lua:44: command failed
       > Expected objects to be equal.
       > Passed in:
       > (string) '1
       > '
       > Expected:
       > (string) '0
       > '
       > Script done.
       For full logs, run 'nix log /nix/store/9g519gl3flbf2qadis0dhf3lcxgjfvdy-nvimpager-0.11.0.drv'

09f4976 built nivm 0.9 with no problems at all for me on aarch64-darwin, thanks @GaetanLepage .

@ofborg build neovim neovim.tests tree-sitter tree-sitter.tests vimPlugins.nvim-treesitter.tests

09f4976 built nivm 0.9 with no problems at all for me on aarch64-darwin, thanks @GaetanLepage .

Failed to build on mine (M1 macbook pro), though:
/nix/store/aj1qd82jb4pipx45pyx16rzbirx5fcza-make-shell-wrapper-hook/nix-support/setup-hook: line 115: /nix/store/29lay5mb4aj501fnxm2hxac12qhndz1w-neovim-0.9.0/bin/nvim-python3: Permission denied

(Full log below)

symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/bin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/lib:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/lib/nvim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/man:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/man/man1:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sk:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sk/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/zh_CN.UTF-8:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/zh_CN.UTF-8/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/vi:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/vi/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sv:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sv/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ga:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ga/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/cs.cp1250:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/cs.cp1250/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/da:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/da/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/no:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/no/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ko.UTF-8:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ko.UTF-8/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/pt_BR:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/pt_BR/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ja:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ja/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/it:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/it/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ca:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ca/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/cs:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/cs/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ru:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ru/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ja.euc-jp:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/ja.euc-jp/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/uk:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/uk/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/en_GB:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/en_GB/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/pl.UTF-8:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/pl.UTF-8/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/zh_TW.UTF-8:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/zh_TW.UTF-8/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/nl:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/nl/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/af:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/af/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/nb:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/nb/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/de:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/de/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/fi:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/fi/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/eo:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/eo/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/fr:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/fr/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/es:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/es/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sk.cp1250:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/sk.cp1250/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/tr:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/locale/tr/LC_MESSAGES:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/indent:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/indent/testdir:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/ftplugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/tools:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/spell:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries/vim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries/vimdoc:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries/lua:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries/query:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/queries/c:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/termdebug:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/termdebug/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/justify:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/justify/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/cfilter:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/cfilter/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/shellmenu:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/shellmenu/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/swapmouse:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/swapmouse/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/vimball:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/vimball/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/vimball/doc:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/vimball/autoload:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/matchit:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/matchit/plugin:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/matchit/doc:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/pack/dist/opt/matchit/autoload:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua/vim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua/vim/treesitter:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua/vim/lsp:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua/vim/filetype:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/lua/nvim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/macros:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/colors:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/tutor:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/tutor/en:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/keymap:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/doc:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload/zig:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload/health:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload/provider:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload/xml:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/autoload/remote:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/syntax:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/syntax/vim:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/syntax/shared:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/nvim/runtime/compiler:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/icons:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/icons/hicolor:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/icons/hicolor/128x128:
symlinkJoin: warning: keeping existing file: /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0/share/icons/hicolor/128x128/apps:
/nix/store/aj1qd82jb4pipx45pyx16rzbirx5fcza-make-shell-wrapper-hook/nix-support/setup-hook: line 115: /nix/store/29lay5mb4aj501fnxm2hxac12qhndz1w-neovim-0.9.0/bin/nvim-python3: Permission denied

using:
diff --git a/flake.lock b/flake.lock
index da93b48..5ecfa7f 100644
--- a/flake.lock
+++ b/flake.lock
@@ -719,6 +719,22 @@
         "type": "github"
       }
     },
+    "nixpkgs-nvim": {
+      "locked": {
+        "lastModified":<PHONE_NUMBER>,
+        "narHash": "sha256-ahLLzydOSrdgZzxBzugQL+kiN2Y9/dZ26Itf+ymss/k=",
+        "owner": "GaetanLepage",
+        "repo": "nixpkgs",
+        "rev": "09f49769746a9ba87ea3985402615e0f90dc7ffb",
+        "type": "github"
+      },
+      "original": {
+        "owner": "GaetanLepage",
+        "ref": "neovim",
+        "repo": "nixpkgs",
+        "type": "github"
+      }
+    },
     "nixpkgs-stable": {
       "locked": {
         "lastModified":<PHONE_NUMBER>,

Actually, I can build pkgs.neovim-unwrapped - just not pkgs.neovim.

I was able to reproduce the build on aarch64-darwin:
$ nix build .#neovim-unwrapped .#neovim
$ ls
...
result   -> /nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0
result-1 -> /nix/store/fgjf4f0lvrwi6xvbyb10wfph2msai0q1-neovim-unwrapped-0.9.0
$ ./result/bin/nvim --version
NVIM v0.9.0
Build type: Release
LuaJIT 2.1.0-beta3
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/nix/store/fgjf4f0lvrwi6xvbyb10wfph2msai0q1-neovim-unwrapped-0.9.0/share/nvim"
...

Failed to build on mine (M1 macbook pro), though:
/nix/store/aj1qd82jb4pipx45pyx16rzbirx5fcza-make-shell-wrapper-hook/nix-support/setup-hook: line 115: /nix/store/29lay5mb4aj501fnxm2hxac12qhndz1w-neovim-0.9.0/bin/nvim-python3: Permission denied

Is it possible this might be caused by your configuration?

https://discourse.nixos.org/t/help-needed-neovim-completions-fail-to-build/14223
https://github.com/NixOS/nixpkgs/issues/137829

As the update of tree-sitter has already been merged, I just removed the corresponding commit from this PR.

@GaetanLepage I've submitted a PR to bump luv https://github.com/NixOS/nixpkgs/pull/225499 , have you looked into the required tree-sitter grammars ? we should install them I think . Also have you tried to set doCheck to true on the unwrapped neovim ?  I disabled it from the default build because some tests didn't pass but make functionaltest should give a better idea of how well neovim is packaged.

Works on my machine. Though, when opening up neovim my config fails with
Error executing lua [string ":lua"]:22: module 'nvim-treesitter.configs' not found

mhh doesn't look good for me on a m1pro
2 packages marked as broken and skipped:
vimPlugins.stylish-nvim vimPlugins.vim-xkbswitch

7 packages failed to build:
gnvim lua51Packages.sqlite luaPackages.sqlite lua53Packages.sqlite lua54Packages.sqlite nvimpager vimPlugins.openscad-nvim

M1 here too, seems to work fine with latest nixpkgs unstable + this patch, at least with the plugins that I use:
028 ~/githome/neovim-flake master
❯ nix run '.#' -- --version
warning: Git tree '/Users/aorith/githome/neovim-flake' is dirty
NVIM v0.9.0
Build type: Release
LuaJIT 2.1.0-beta3

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/nix/store/fgjf4f0lvrwi6xvbyb10wfph2msai0q1-neovim-unwrapped-0.9.0/share/nvim
"

Run :checkhealth for more info

thats strange nixpkgs-review pr 225152
doesn't work. how did you build it @aorith

thats strange nixpkgs-review pr 225152 doesn't work. how did you build it @aorith

Probably not in the proper and intended way, I'm new to all this:

Cloned nixpkgs in unstable: git clone --depth 1 --branch nixpkgs-unstable https://github.com/NixOS/nixpkgs.git, (got: https://github.com/NixOS/nixpkgs/tree/da0b0bc6a5d699a8a9ffbf9e1b19e8642307062a)
Got the PR diff and applied it: wget https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/225152.diff && git apply 225152.diff
I didn't build it directly, but using a flake that wraps my neovim config (https://github.com/aorith/neovim-flake), changed it to use the pkgs from my local nixpkgs repo:

diff --git a/flake.nix b/flake.nix
index 8d04cfe..61e1841 100644
--- a/flake.nix
+++ b/flake.nix
@@ -2,7 +2,8 @@
   description = "Aorith's neovim flake";

   inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
+    #nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
+    nixpkgs.url = "/Users/aorith/githome/nixpkgs";
     #nixpkgs.url = "github:NixOS/nixpkgs/?rev=e3652e0735fbec227f342712f180f4f21f0594f2";

     flake-utils.url = "github:numtide/flake-utils";
diff --git a/packages/neovim/default.nix b/packages/neovim/default.nix
index eeb21c4..744f66f 100644
--- a/packages/neovim/default.nix
+++ b/packages/neovim/default.nix
@@ -4,8 +4,8 @@
   inputs,
 }: let
   # Choose a base nvim package to override
-  #neovimPackage = pkgs.neovim-unwrapped;
-  neovimPackage = inputs.neovim.packages.${pkgs.system}.neovim;
+  neovimPackage = pkgs.neovim-unwrapped;
+  #neovimPackage = inputs.neovim.packages.${pkgs.system}.neovim;

   # https://github.com/NixOS/nixpkgs/blob/b4d8662c4a479b7641d28fe866b018adf8d8f2e1/pkgs/applications/editors/neovim/utils.nix
   neovimConfig = pkgs.neovimUtils.makeNeovimConfig {

executed nix build and went ok
executed nix run and tested it a bit and then pasted the output of --version here

I just tested it again like this:
/tmp ❯ export NIXPKGS=~/githome/nixpkgs
/tmp ❯ nix-build $NIXPKGS -A neovim
this derivation will be built:
  /nix/store/wcaxpqg2snr86scr6bqf1f37k4ywqgyh-neovim-0.9.0.drv
building '/nix/store/wcaxpqg2snr86scr6bqf1f37k4ywqgyh-neovim-0.9.0.drv'...
Generating remote plugin manifest
/nix/store/l160yrpx84lmxgm7djqvxab2n80lr5cr-neovim-0.9.0
/tmp ❯ ./result/bin/nvim --version
NVIM v0.9.0
Build type: Release
LuaJIT 2.1.0-beta3

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/nix/store/fgjf4f0lvrwi6xvbyb10wfph2msai0q1-neovim-unwrapped-0.9.0/share/nvim
"

Run :checkhealth for more info

/tmp ❯ uname -vp
Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103 arm
/tmp ❯

Sorry for the noise, I'll check nixpkgs-review.

The rebuilds are mostly vim plugins. If running nixpkgs-review is feasible we probably don't need to target staging

lua54Packages.sqlite

not available on hydra yet

nvimpager

vimPlugins.coc-imselect

Those are broken on master

@teto I think https://github.com/NixOS/nixpkgs/pull/207908 does what you want


fix agent jobs not loading issue

This PR fixes #16872
in this PR https://github.com/microsoft/azuredatastudio/pull/16833/files#diff-6d616df90e2be6440c679403f6e161d5b65c7f91ba86c816789b309a764b7c3cR95, we are using the options without checking for undefined.
fix: add a default options class and use it when not specified.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0002%) to 42.043%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/base/browser/ui/table/plugins/headerFilter.plugin.ts
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0002%

Covered Lines:
26395

Relevant Lines:
56917

💛  - Coveralls


[hi] Localize Edge Computing to Hindi

Why this term needs to be updated? (briefly)
https://glossary.cncf.io/edge-computing/
Edge Computing should also be added in Hindi

Hi @jihoon-seo I want to work on this issue Assign me, thanks

@dixitrathi7 instead of asking me, it would be great to ask Hindi localization approvers (@Garima-Negi @sayantani11 @anubha-v-ardhan @jayesh-srivastava) to be assigned.

Hi @Garima-Negi (@sayantani11 @anubha-v-ardhan @jayesh-srivastava) I want to work on the issue that raise by @neelshah2409
Assign me.

Hey there! @Garima-Negi @sayantani11 @anubha-v-ardhan @jayesh-srivastava! I would love to work on this issue. Could you please assign it to me?

@kumarankit999  If no one is working on it please assign to me

Hey @Aryan-Singla, @akshatcoder-hash has already raised a PR and you can check the latest comment on that!

Since a long time, there isn't any response from Akshat's side. So, Aryan you can work on this issue.

@aj11anuj I will raise PR in a few days


50035 Invalid Form Body upon basically anything register-related

Hi all, hope all is well and you are safe.
I'm attempting to test my bot with discord-py-slash-command, but I'm getting a RequestFailure: Request failed with resp: 400 | {"code": 50035, "errors": {"application_id": {"_errors": [{"code": "NUMBER_TYPE_COERCE", "message": "Value \"<built-in function id>\" is not snowflake."}]}}, "message": "Invalid Form Body"} when I try to discord_slash.utils.manage_commands.get_all_commands, or when I try to manage_commands.add_slash_command.
I'm only using example code from the docs and in the issues while troubleshooting, so I'm really confused about what's happening!
I'm running this:
    def __init__(self, bot):
        if not hasattr(bot, "slash"):
            # Creates new SlashCommand instance to bot if bot doesn't have.
            bot.slash = SlashCommand(bot, override_type=True, auto_register=True)
        self.bot = bot
        self.bot.slash.get_cog_commands(self)

    def cog_unload(self):
        self.bot.slash.remove_cog_commands(self)

    @cog_ext.cog_slash(name="ping")
    async def ping(self, ctx: SlashContext):
        await ctx.send(content="Pong!")

def setup(bot):
    bot.add_cog(Slash(bot))

Any help would be extremely appreciated!
Thanks,
-Dan
Edit: It's almost definitely my own incompetence and stupidly causing something!

... when I try to discord_slash.utils.manage_commands.get_all_commands, or when I try to manage_commands.add_slash_command.

I think it might be the problem of passed args at those functions, can I see how did you use that? (Hide the token when you post it of course.)

... when I try to discord_slash.utils.manage_commands.get_all_commands, or when I try to manage_commands.add_slash_command.

I think it might be the problem of passed args at those functions, can I see how did you use that? (Hide the token when you post it of course.)

I'm pretty sure you are not passing bot.user.id to the functions.

I'm pretty sure you are not passing bot.user.id to the functions.


cv::FileStorage de-serialization of std::vectorcv::KeyPoint fails

OpenCV version and host system

OpenCV version: git b3ac274617beb8e54c8bfebcb141090a57165ea2, but unchanged in HEAD
Host OS: Windows 7

In which part of the OpenCV library you got the issue?

core/types.hpp

Expected behaviour

Take a cv:KeyPoint kp with kp.octave = 1 and kp.class_id = -1
serialize this keypoint as part of a std::vector to a cv::FileStorage
the entry in the file correctly shows "..., 1, -1, ..."
deserialize the keypoint
kp.octave is 1
kp.class_id is -1

Actual behaviour
after deserialization:

kp.octave is<PHONE_NUMBER> (a 1.0f reinterpreted as int)
kp.class_id is -1082130432 (a -1.0f reinterpreted as int)

Additional description
cv::Keypoint instances with octave or class_id != 0 are not deserialized correctly.
The cv::KeyPoint class declares octave and class_id as int (in addition to the five float members), but DataType declares a vector of seven floats. When read in, the integer values are converted to float in cvReadRawDataSlice(), but interpreted as int in the datastructure.
Code example to reproduce the issue / Steps to reproduce the issue
// File was written with:
// cv::FileStorage fs( featuresFile, cv::FileStorage::WRITE );
// cv::write( fs, "keypoints", keypoints );
// fs.release();
cv::FileStorage fs;
std::vectorcv::KeyPoint keypoints;
fs.open( featuresFile, cv::FileStorage::READ );
fs["keypoints"] >> keypoints;

I'm trying to fix this bug.
After investigation, there is a dedicated function to read vector in persistence.hpp
CV_EXPORTS void read(const FileNode& node, std::vector<KeyPoint>& keypoints);
However, the '>>' operator does not call the function. DMatch may have similar issue.
I am going to overload the '>>' operator so that it calls the dedicated function in persistence.hpp.

I have send a pull request (#6375) for the fix.


[Runtime] Detect and log redundant subclass/superclass conformances.

When we rely on a protocol conformance, and the type in question has multiple conformances to that protocol in its inheritance chain, emit a runtime warning.
It's quite tricky to cause this problem - you need a type in one dylib that is extended to conform to a protocol in another dylib, subclassed in another module and then some subclass has protocol conformance added as well.  If they're in
the same module, the compiler will give an error and prevent the problem completely.
rdar://73364629

@swift-ci Please smoke test

Note that you'll only get a warning if you rely on a protocol conformance and there are multiple redundant conformances in the inheritance hierarchy. It's fairly tricky to trigger (I needed two dylibs and an executable). I haven't added a test to Swift for it; I don't know whether that's worth doing?

Looks good. I think a test is worthwhile. We have other tests that build dylibs from multiple files so you should be able to find examples to crib from.

@swift-ci Please smoke test

@swift-ci Please smoke test macOS platform


Upgrade to org.sonarsource.java to <IP_ADDRESS>201 (breaks S2755)

[x] org.sonarsource.java:java-checks-testkit
[ ] org.sonarsource.java:java-frontend
[ ] org.sonarsource.java:java-checks

Upgrading org.sonarsource.java:java-frontend induce a lot of breaking behaviour in the code. It is better to create an issue and deal with it.

We need to find proper release notes before jumping into this issue. They have split a lot of APIs into different packages. For example, we would also need org.sonarsource.sonarqube:sonar-plugin-api-impl.

@khaes-kth @monperrus I think we can focus on this issue before adding any further rules.

yes, 100% agree.

All later versions of the plugin break S2755.

For this, since we want to depend on the latest sonar-java, two options:

we drop the rule
we re-write the detector ourselves (we have Spoon right ;-)

I'd be in favor of the latter

@monperrus I will report this to SonarJava and then we can surely confirm if the issue is at our end or theirs. Then we can take the action.

great

I forgot to update it here. I checked this myself and found out that the source position is correctly detected when the static analysis is executed by SonarQube itself.

New goal next week - resolve this issue. Work already started at #900. 5 test cases are failing. It should not be hard to resolve them unless it breaks one of our processors.


Error when running example code

I'm running through the example code in the README:
setwd("~/git/bayroot")
source("bayroot.R")
require(ape)
require(lubridate)

# 50 trees generated from a simulation of cell dynamics
trees <- read.tree("data/testdata-latent2.nwk")
times <- read.csv("data/testdata-latent2.csv")

# export one of the replicates to new files
rep <- 1
tf <- "data/example.nwk"
write.tree(trees[[rep]], file=tf)

cf <- "data/example.csv"
int.times <- times$int.time[times$rep==rep]
names(int.times) <- times$sample[times$rep==rep]
write.csv(as.data.frame(int.times), file=cf)

phy <- read.tree(tf)
settings <- list(
  seq.len=1233,  # AY772699
  format="%Y-%m-%d",
  # we arbitrarily assigned 2000-01-01 as the actual origin date
  mindate=as.Date("1999-12-01"),  # one month before origin
  maxdate=as.Date("2000-02-01"),  # one month after origin
  meanlog=-5, sdlog=2,  # hyperparameters for lognormal prior on rate
  root.delta=0.01,  # proposal on root location
  date.sd=10,  # days, origin proposal
  rate.delta=0.01,  # proposal on clock rate
  censored = phy$tip.label[grepl("^Latent", phy$tip.label)]
)

source("scripts/validate.R")  # loads package chemCal
set.seed(1)  # make this reproducible
res <- fit.bayroot(tf, cf, settings=settings, nstep=2e4, skip=20,
                   max.date=as.Date("2001-04-01"), echo=TRUE)
plot(res$chain, burnin=100)

rt <- root2tip(phy)
true.vals <- get.true.values(rt, cf)
est <- get.estimates(res, rt)

This is throwing the followng error on my system (Ubuntu 22.04, R version 4.3.2):
> rt <- root2tip(phy)
Error in cor(y, x) : incompatible dimensions
In addition: There were 50 or more warnings (use warnings() to see the first 50)

I get the same error if I manually step through the root2tip code:
>   phy <- multi2di(phy)
>   tip.dates <- sapply(phy$tip.label, function(x) as.integer(strsplit(x, "_")[[1]][3]))
>   censored <- ifelse(grepl("Active", names(tip.dates)), tip.dates, NA)
>   names(censored) <- names(tip.dates)
>   rooted <- ape::rtt(t=phy, tip.dates=censored)
Error in cor(y, x) : incompatible dimensions
In addition: There were 50 or more warnings (use warnings() to see the first 50)

This indicates that the problem is associated with the rtt function.  However if I step through the rtt code, no error gets thrown:
opt.tol <- .Machine$double.eps^0.25
objective <- function(x, y) {
  cor(y, x)
}

ut <- unroot(phy)
dist <- dist.nodes(ut)[, seq_len(Ntip(ut))]
X <- matrix(1, Ntip(ut), 2)
f <- function(x, parent, child) {
  edge.dist <- x * dist[parent, ] + (1 - x) * dist[child,
  ]
  objective(tip.dates, edge.dist)
}
obj.edge <- apply(ut$edge, 1, function(e) {
  opt.fun <- function(x) f(x, e[1], e[2])
  optimize(opt.fun, c(0, 1), maximum = TRUE, tol = opt.tol)$objective
  })

best.edge <- which.max(obj.edge)
best.edge.parent <- ut$edge[best.edge, 1]
best.edge.child <- ut$edge[best.edge, 2]
best.edge.length <- ut$edge.length[best.edge]

opt.fun <- function(x) f(x, best.edge.parent, best.edge.child)
best.pos <- optimize(opt.fun, c(0, 1), maximum = TRUE, tol = opt.tol)$maximum
new.root <- list(edge = matrix(c(2L, 1L), 1, 2), tip.label = "new.root",
                 edge.length = 1, Nnode = 1L, root.edge = 1)
class(new.root) <- "phylo"
ut <- bind.tree(ut, new.root, where = best.edge.child, position = best.pos *
                  best.edge.length)
ut <- collapse.singles(ut)
ut <- root(ut, "new.root")

rooted <- drop.tip(ut, "new.root")

In rtt(t, tip.dates, ncpu = 1, objective = correlation, opt.tol = .Machine$double.eps^0.25), could changing the measure for goodness of fit resolve this problem - e.g. objective="rms" or objective="rsquared


Dropdown formatting: fix corner radii

In the dropdown component, the list container and highlight for selected items have rounded corners. They should be square. Related to side navigation issue #2927

Something like this is expected? @enowak1031 @apaddock
or
![Image](https://github.com/user-attachments/assets/e743121c-e333-45dc-bb56-694c2d0a7123)

Ideally we would like to change the corner radius to 0 pixels for all dropdowns with an option to customize it or increase it to 2 or 4 pixels.


[Rust] Cargo cache persistence in Docker Volume

Do you think it is worth including in the template with the following settings, which share the Cargo cache between builds and containers, commented out?
{
	"source": "devcontainer-cargo-cache",
	"target": "/usr/local/cargo",
	"type": "volume"
}

I think we could. How about adding something like 👇 ?
    "mounts": [
        {
            "source": "devcontainer-cargo-cache-${devcontainerId}",
            "target": "/usr/local/cargo",
            "type": "volume"
        }
    ]

I think we could. How about adding something like 👇 ?
    "mounts": [
        {
            "source": "devcontainer-cargo-cache-${devcontainerId}",
            "target": "/usr/local/cargo",
            "type": "volume"
        }
    ]

Thanks for your response.
I think this is a safe volume to share among all containers, but your suggestion is more safer so I think it is ok.


Documentation for parameters is incomplete, inadequate

The parameters
--hostname
The host name of the custom domain. Must be a domain name.

--name -n
Name of the custom domain.

and the example:
az cdn custom-domain create -g group --endpoint-name endpoint --profile-name profile -n domain-name --hostname www.example.com

do not provide enough information to use this command. --hostname and --name appear to describe the same thing, conceptually.  The example is useless, as values like --endpoint-name endpoint, --profile-name profile, and --name domain-name do not provide any information about the intended format or nature of the parameter.
As an example,
az cdn custom-domain create --profile-name cdnp-myproject-b4d55 --endpoint-name cdne-myproject-b4d55 --hostname cdn.myproject.com --name myproject.com --resource-group rg-myproject --location eastus

returns the error
BadRequest: Property 'CustomDomainEntityKey.CustomDomainName' cannot be set to 'myproject.com'.

so --name clearly is not expecting a domain name despite the description being "Name of the custom domain" and the property's internal label being CustomDomainName.
To make things more confusing, the Az.Cdn PowerShell cmdlet New-AzCdnCustomDomain defines
-HostName
Specifies the host name of the custom domain.

-CustomDomainName
Specifies the resource name of the custom domain.

Is --name in the az cli supposed to refer to an internal Azure resource identifier?  If so, where is a user supposed to find that information?
In the Azure Portal, only two tokens are required to create a custom domain: "Endpoint hostname" (pre-filled, and fixed by context) and "Custom hostname".
As it stands, neither the az cli nor the New-AzCdnCustomDomain cmdlet are usable without proper documentation of what the parameters mean and how they used in the instantiation of a custom domain.
[Aside: this is a consistent problem in the documentation for all az cli commands and Az cmdlets: terse, inadequate descriptions of parameters and examples that do not represent real-world usage.]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ed8c61db-b294-77fb-0e92-eae01d07b776
Version Independent ID: 958b6e8d-609b-2a58-dbe1-240d3fd894bb
Content: az cdn custom-domain
Content Source: latest/docs-ref-autogen/cdn/custom-domain.yml
Service: cdn
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

CDN

I was just struggling with this same issue. I exported the ARM template and I see my custom domain being used as a name within the template, where my domain dots are replaced with dashes.
www-mydomain-com. I replaced www.mydomain.com in my command line with www-mydomain-com and it worked. But I see that name nowhere within the portal. So, docs need to be updated. Portal needs to be updated. And maybe the az command needs to be updated.

@slbentley I've done some research in the interim and you may find this helpful.
A "custom domain name" in Azure isn't an attribute of a CDN endpoint; it's actually an independent Azure resource all on its own.  The --name parameter for az cdn custom-domain create and the -CustomDomainName parameter for New-AzCdnCustomDomain refers to the Azure resource name for the custom domain name resource.  Since the resource name for an Azure resource is part of the path in the URL to the Azure ARM APIs, it can't have periods in it.  That's why ARM is silently replacing them with dashes in your exported template.
The portal isn't showing the name because the portal displays the custom domain name as if it's an attribute of a CDN endpoint, even though it isn't.
Hope that helps.  The user experience between the az cli, the Az PowerShell module, the Portal, and ARM templates/Bicep keeps fragmenting.  It's like Microsoft doesn't want people using IaC tools.

Interesting. I grew curious and went and checked my QA region which was created from an ARM template  just a few days ago, and has yet to be  reviewed or tested. I was curious to see what the custom domain ended up being set to as my input parameter included dots. Looks like for that input the dots worked. So I guess its just on the cli...maybe.... Its like I'm feeling around in the dark.  But I do continue to move forward. Albeit more slowly that I would like.


mysql DataType for 'verifyChanges' in user item

I am using sequelize to store my users in a database and I'm not sure which Data Type I should use for 'verifyChanges'. The docs suggest verifyChanges: // an object (key-value map), e.g. { field: "value" }, but I don't know how to accomplish that in mysql. Any experiences?

I don't have sequelize experience, but can you store it as JSON data?

ryan.wheale says
Postgres has support for JSON fields. Before that, it was not uncommon to store JSON in a TEXT field. ... Not sure if sequelize would stringify an object for you or throw an error.
You could use hooks to convert to-from JSON.

I assume we can close this now. Feel free to reopen the issue if there is more to discuss.

Sequelize does throw an error when using a STRING or TEXT in MySQL: "string violation: verifyChanges cannot be an array or an object"
Maybe we should add an example hook to the docs or fix the issue?

I believe you have to make that field JSON in some databases. What would your example be?

I didn't try to use a hook, so I don't have an example at the moment, but thought it's worth mentioning that an error is emitted and that it doesn't currently work as is with MySQL.

This may be useful for this issue https://www.npmjs.com/package/sequelize-json

I just used mongodb instead.

I don't have a better answer than "I believe you have to make that field JSON in some databases." as that's what some people reported doing.

This issue is further handled in the a-l-m rewrite of this repo. Full details at https://github.com/feathers-plus/authentication-local-management/blob/master/misc/upgrading.md
Please add any further comments in a-l-m.


Do diagnostics on activate in case inspection report already exist

This pull requests splits out the diagnostic parts to a reusable file so we are able to run diagnostics on extension-activation as well as after code inspection.
This is useful as the inspectioncode.xml may already exist in the workspace and re-inspecting code can be time-consuming.
To make this work i had to add onLanguage:csharp as an activationEvent so it will actually fire.
As a bonus i added a refreshdiagnostics command that walks through the existing inspection file (if exists) and refreshes the diagnostic collection. Useful if you are running ReSharper CLI commands outside of the extension and want to diagnose based on inspection-reports not generated by fakesharper.

Give me some time to review about 3 hours. Big thanks :)

@ryskov May Reload Diagnostics command name better here?
For functions loadDiagnostics and loadAllDiagnostics?


Add booking site functionality

user will be able to book site
options include no. of nights spending, check-in date and time etc.
no other user can book the same site while the user stay is not completed.

pls assign me this issue as i have added this feature in my website also which i made in delta batch by apna college

@Asjdnnc progress?


Adding Windows Support

Unfortunately the developers of this library did not spend any amount on effort to make this library compilable on Windows. Even the build-system, it not portable.
I updated the windows port from https://github.com/bureau14/leveldb/blob/master, which was based on levelDB 1.18 to version 1.20. The following patches are necessary:
1.) The CMakeList file from https://github.com/bureau14/leveldb/blob/master which works with 1.18
2.) Some changes to this file to make it compatible with 1.20
3.) Several files, which are necessary for windows (also taken form https://github.com/bureau14/leveldb/blob/master) combined with some adoptions to make everything compatible to 1.20.
4.) Some adoptions to the tests. Windows don't like to delete a file, which is currently in use by the same process.
You can find the patches in the attached ZIP.
patches.zip
Furthermore this is a appveyor.yml file, which compiles levelDB 1.20 on AppVeyor CI Build system for Windows 64bit, 32bit as Release and Debug build:
image: Visual Studio 2015
version: 1.0.{build}

environment:
  matrix:
    - PLATFORM: x86
      BUILDTYPE: Debug
    - PLATFORM: x64
      BUILDTYPE: Debug
    - PLATFORM: x86
      BUILDTYPE: Release
    - PLATFORM: x64
      BUILDTYPE: Release

clone_folder: c:\projects\leveldb
init:
- if "%PLATFORM%"=="x64" call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
- if "%PLATFORM%"=="x86" call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
build_script:
- cmd: >-
    cd c:\projects\leveldb

    mkdir build

    cd build

    cmake --version

    cmake -G "NMake Makefiles" .. -DCMAKE_INSTALL_PREFIX=../../install/appveyor -DCMAKE_BUILD_TYPE=%BUILDTYPE% -DBOOST_ROOT=C:\Libraries\boost_1_62_0

    nmake install
test_script:
- cmd: nmake test

I have not tested the CMake-build system on linux so far. But I will do it within the next weeks. If I see issues, I will release some additional patches.
By the way: Even on *nix systems CMake is a better choice as build system than pure Makefiles. It solves many dependencies by itself and on top of it will give you cross-compile possibility for free. Yeah I know, it is hard to use something different, when you are used to pure Makefiles. But give it a try.

Today I notices, that the current windows build with the above patches will not enable SNAPPY for levelDB. If you are working with databases which use SNAPPY, this can be an issue.
Thus I created 4 more patch files. All patch files are contained in the following ZIP.
patches.zip
The following files are relevant (in addition to the files, described above):
5.) The library files are now installed during installation step.
6.) All Header files are installed during installation step.
7.) Enable SNAPPY support for windows.
8.) Check environment variable SNAPPY_ROOT to set root dir automatically.
For the Snappy support I used as base the file "FindSnappy.cmake" from repository https://github.com/lemire/FastPFor
This files was published under Apache license. I adapted the file to work together with the precompiles windows version of snappy which can be downloaded from here: https://snappy.machinezoo.com/

Official support for Windows is probably the most requested enhancement. We are currently working on CMake support with continuous integration via AppVeyor. Using issue #466 to track this work.


224 fetch run predictors and more.

Fixes #224 and potentially #164
The server url used in the front end was not put into an environment variable but is in a config file.
Also updates the nginx image being used by docker since the current one in master is no longer supported.

At first glance, changes LGTM. I need to clean up a few things on the testing/production server, and then im going to try running this branch there to give it a whirl.


Update tls-1.0-and-1.1-deprecation-for-office-365.md

Added references to provide guidance to help make sure that clients are using TLS 1.2 or a later version and to disable TLS 1.0 and 1.1.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/4177

@msbemba

@WorkShay Please merge this PR. Thanks

@WorkShay Gentle reminder please merge this PR. Thanks.


IconButton onClick fires twice

What RMWC Version are you using [major.minor.patch]: 14.0.7

Name your build system [Webpack, Rollup...]: Vite

Describe the bug with as much detail as possible: When I click an IconButton the click event is fired two times as seen here, https://codesandbox.io/p/devbox/gallant-keldysh-6wrkyl
Check the chrome devtools using F12 for the console.log (not the integrated codesandbox "Preview Console" button as this dosen't happen there although the same thing happens in the regular browser)

What happened, and what was supposed to happen: After some investigation, I came to the conclusion that there's an event attached to both the <button> and  <i> tags and they're both fired at the same time, is the extra event on the <i> intended?

Thanks for creating the issue. We will look into it. Do you know if you're running strict mode? We have an issue that causes things to fire twice. https://github.com/rmwc/rmwc/issues/815


[SPARK-21585]: Application Master marking application status as Failed for Client Mode

The fix deployed for SPARK-21541 resulted in the Application Master to set the final status of a spark application as Failed for the client mode as the flag 'registered' was not being set to true for client mode. So, in order to fix the issue, I have set the flag 'registered' as true in client mode on successfully registering Application Master.
How was this patch tested?
Tested the patch manually.
Before:

After:

Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

ok to test

Test build #80095 has started for PR 18788 at commit 63e01b8.

Test build #80095 has finished for PR 18788 at commit 63e01b8.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class OneVsRestParams(HasFeaturesCol, HasLabelCol, HasWeightCol, HasPredictionCol):
case class UnresolvedSubqueryColumnAliases(
sealed trait FrameType
sealed trait SpecialFrameBoundary extends Expression with Unevaluable
sealed trait WindowFrame extends Expression with Unevaluable
class ArrowWriter(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80095/
Test PASSed.

+1

Merged


AppVoyer CI build and push preview packages to MyGet

TODO BEFORE MERGING:

Transfer ownership of myget feed
Create appveyor.com account

Update badge in README.md

https://ci.appveyor.com/project/ACCOUNTNAME/ahoy/settings/badges

Encrypt and replace MyGet push secret in appveyor.yml

https://ci.appveyor.com/tools/encrypt

See TODO note in appveyor.yml

@moander - thanks for this awesome contribution

Np and thank you for this excelent middleware! Reach out when you're ready to complete the TODO's :)


547 update cache after user actions

Closes #547
For all top-level "create" mutations—Project, Language, User, Partner—we call the update method and use cache.modify to write the new item to the items field of the relevant List query. This required refactoring all relevant mutations to use a fragment so that fragment can be used in the write operation.

@CarsonF So, even though I'm up and running with the app again I still can't really tests this because neither the root user nor another user I create can actually read the items they create. But the code looks good!


Include FFMPEG INJECTION

Hi,
thanks for this repo is very usefull!
You should also add the ffmpeg injection, looks at the links below for more info:
https://hackerone.com/reports/242831
https://docs.google.com/presentation/d/1yqWy_aE3dQNXAhW8kxMxRqtP7qMHaIfMzUDpEqFneos/edit#slide=id.p
cheers

I'm glad you like it :)
You can find the FFMPEG injection via HLS here : https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Upload insecure files/Ffmpeg HLS
Best regards ;)

Cool :+1:

<3 <3 thanks people


⚠ Bofrost.de has degraded performance

In 5766146, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 911 ms

Resolved: Bofrost.de performance has improved in 48fda2e after 6 minutes.


Diff working in a separate go routine from merge. Parallel diff and merge

Codecov Report

Merging #887 into feature/overlap-diff-and-merge will decrease coverage by 0.11%.
The diff coverage is 57.14%.

@@                        Coverage Diff                         @@
##           feature/overlap-diff-and-merge     #887      +/-   ##
==================================================================
- Coverage                           45.05%   44.94%   -0.12%
==================================================================
  Files                                 141      141
  Lines                               10779    10722      -57
==================================================================
- Hits                                 4857     4819      -38
+ Misses                               5332     5323       -9
+ Partials                              590      580      -10

Impacted Files
Coverage Δ

catalog/cataloger_merge.go
69.64% <57.14%> (-1.70%)
:arrow_down:

catalog/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

db/database.go
0.61% <0.00%> (-0.02%)
:arrow_down:

catalog/cataloger.go
71.22% <0.00%> (ø)

catalog/cataloger_create_repository.go
62.96% <0.00%> (+3.70%)
:arrow_up:

catalog/cataloger_export.go
90.00% <0.00%> (+18.81%)
:arrow_up:

Continue to review full report at Codecov.

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

Exit worker variable seems racy. @nopcoder any idea why go test --race doesn't pick it up?

n/m, not an issue with race detection.  https://codecov.io/gh/treeverse/lakeFS/pull/887/diff?src=pr&el=tree#D2-150 says that line never ran in a test.  We should have a test that does run it.

Here's a simplified example of the race condition:
package main

import "testing"

type Task struct {
	Exit   bool
	Output chan int
}

func (t *Task) Run() {
	for i := 0; !t.Exit; i++ {
		t.Output <- i
	}
	close(t.Output)
}

func TestRace(t *testing.T) {
	task := Task{Output: make(chan int, 9999999)}

	go task.Run()

	for i := 0; i < 10000; i++ {
		_ = <-task.Output
	}

	count := 0
	task.Exit = true
	for range task.Output {
		count++
	}

	t.Log(count, " before stop")
}

(also attached)
ariels@ariels:~/Dev/Tests$ go test -race stop_test.go
==================
WARNING: DATA RACE
Write at 0x00c000118490 by goroutine 7:
  command-line-arguments.TestRace()
      /home/ariels/Dev/Tests/stop_test.go:27 +0x13c
  testing.tRunner()
      /snap/go/6633/src/testing/testing.go:1123 +0x202

Previous read at 0x00c000118490 by goroutine 16:
  command-line-arguments.(*Task).Run()
      /home/ariels/Dev/Tests/stop_test.go:11 +0x87

Goroutine 7 (running) created at:
  testing.(*T).Run()
      /snap/go/6633/src/testing/testing.go:1168 +0x5bb
  testing.runTests.func1()
      /snap/go/6633/src/testing/testing.go:1439 +0xa6
  testing.tRunner()
      /snap/go/6633/src/testing/testing.go:1123 +0x202
  testing.runTests()
      /snap/go/6633/src/testing/testing.go:1437 +0x612
  testing.(*M).Run()
      /snap/go/6633/src/testing/testing.go:1345 +0x3b3
  main.main()
      _testmain.go:43 +0x236

Goroutine 16 (running) created at:
  command-line-arguments.TestRace()
      /home/ariels/Dev/Tests/stop_test.go:20 +0xdc
  testing.tRunner()
      /snap/go/6633/src/testing/testing.go:1123 +0x202
==================
--- FAIL: TestRace (0.01s)
    stop_test.go:32: 3425  before stop
    testing.go:1038: race detected during execution of test
FAIL
FAIL	command-line-arguments	0.014s
FAIL

stop_test.go.gz


Add field to external donation link

Should using this optional field also disable the donation button?

Yes please

HI Nathan, can you update me about this please?

HI Nathan, can you update me about this please?

Done

Thanks all good and working fine.


"your 131072x1 screen size is bogus, expect trouble"

Issue Type: Bug
ctrl-shift-p, "Debug: Start Debugging" leads to this error. I saw that this error was previously mentioned and fixed in a recent update, but the error persists.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 4.19.104-microsoft-standard

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (4 x 2594)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.88GB (1.95GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Ubuntu/home/v-naugur --remote=wsl+Ubuntu

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 4.19.104-microsoft-standard

CPUs
Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (4 x 2593)

Memory (System)
6.10GB (4.98GB free)

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

regex
chr
0.2.0

gitlens
eam
10.2.2

vscode-pull-request-github
Git
0.17.0

vscode-codemetrics
kis
1.24.0

cpptools
ms-
0.28.3

vscode-versionlens
pfl
1.0.8

java
red
0.63.0

vscodeintellicode
Vis
1.2.8

application-insights
Vis
0.4.2

vscode-java-debug
vsc
0.26.0

vscode-java-dependency
vsc
0.10.2

vscode-java-pack
vsc
0.9.1

vscode-java-test
vsc
0.23.0

vscode-maven
vsc
0.22.0

code-lens-roundup
wad
1.0.0

remote-containers
ms-
0.122.1

remote-ssh
ms-
0.51.0

remote-ssh-edit
ms-
0.51.0

remote-wsl
ms-
0.44.3

vscode-remote-extensionpack
ms-
0.20.0

Same problem vscode v1.47.3. any update on this issue?

Same problem vscode v1.47.3. any update on this issue?

@Alirezanet The issue was fixed in this insiders release: https://github.com/microsoft/vscode-cpptools/releases/tag/0.29.0-insiders2

@Alirezanet what debugger are you using?

@weinand Dotnet Core.
      "name": ".NET Core Attach",
         "type": "coreclr",
         "request": "attach",
         "processId": "${command:pickProcess}",

@Alirezanet thanks. That debugger is a separate extension (C#). Please file an issue against that.
We have fixed a similar problem with the Node.js debugger (which is built into VS Code). But that fix does not cover the C# debugger.


Promise in an onEnter hook causes TypeError in component render to be swallowed.

Summary
A promise is used in an onEnter hook. It resolves after one second and invokes done(), as it should. There's an intentional run-time error in one of the component's render(). Inside match()'s callback, error is null, and renderProps is present. When attempting to renderToString() the error is encountered, but is somehow wrapped in a promise, and being swallowed. By enabling the promise lib's rejection tracking, you can confirm an unhandled rejection has happened.
Really, I can't tell if I'm handling something wrong, or if React Router is.
There's a bit more context here: https://gist.github.com/tybro0103/8c131f6e7b73741c08bf
Relevant Code
server.js
// without this, you see no error at all!
require('promise/lib/rejection-tracking').enable();

app.get('*', (req, res, next) => {
  match({routes, location: req.url}, (error, redirect, renderProps) => {
    if (error) return next(error);
    if (redirect) return res.redirect(`${redirect.pathname}${redirect.search}`);
    if (renderProps) {
      let comp = <RouterContext {...renderProps} />;

      // tmp fix is to wrap this in try/catch
      let html = renderToStaticMarkup(component);

      return res.send(`<!DOCTYPE html>${html}`);
    }
    next();
  });
});

routes.js
let onEnter = function(nextState, replaceState, done) {
  new Promise((resolve, reject) => {
    setTimeout(resolve, 1000);
  }).then(done, done);
};

export default (
  <Route path="/" component={App} onEnter={onEnter}>
    <IndexRoute component={Home}/>
    <Route path="about" component={About} />
  </Route>
);

about.jsx
export default class About extends Component {
  render() {

    // intentional error
    this.what.the();

    return
About
;
  }
}

I should add I'm using version 2 RC5

This is a general problem when using promises with a callback-based API. If you don't want the errors to be swallowed, you have to use setTimeout.
let onEnter = function(nextState, replaceState, done) {
  new Promise((resolve, reject) => {
    setTimeout(resolve, 1000);
  }).then(
    () => setTimeout(() => done()),
    (err) => setTimeout(() => done(err))
  );
};

What @taurose said, this is just a general promise-related consequence, nothing we can really do here.

&$@($ing promises. Good to know.

broken promises ... so many broken promises.


Add a paged array template

Used for reusable stacks, or filling arrays from multiple threads efficiently.

Thanks!


Add ULR, Dataflow V2 and Java11 Jenkins statuses to PR template

These tests went red and seemingly went unnoticed.
The format of the PR template is showing its limits. I switched to HTML because editing the huge lines was very difficult. Probably could use a refactor and probably should be autogenerated. For now, just adding the additional statuses.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Also I think @tysonjh may be interested.

LGTM, thanks, @kennknowles . As you noticed, consider adding ULR suite while at it.

Done!


C# Samples for Direct Line Speech and Direct Line ASE Previews

This contains C# samples for Direct Line Speech Preview (Echo and Core Bot) and Direct Line App Service Extension Preview (Echo and Core Bot).

Also, in README.md for this version of the echo bot, you'll need to change the path to the sample. It still says "In a terminal, navigate to samples/csharp_dotnetcore/02.echo-bot". I'm guessing the same for the README.md of the core-bot.


Produce a dependency graph during CI

Anywhere that we currently generate a dependency report we should also publish a dependency graph. #8597 and Azure/azure-sdk-tools#278 will be needed for the implementation.

https://github.com/Azure/azure-sdk-for-net/pull/9964


Disable upstream analytics

Bug Description
Logs are flooded with failure messages regarding upstream analytics:
msg="failed to send usage report" retries=0 err="Post \"https://stats.grafana.org/agent-usage-report\": context deadline exceeded

See also: https://github.com/grafana/loki/issues/10648
To Reproduce

Deploy grafana-agent charm.
Relate to compatible machine charm.
Watch /var/log/syslog for error.

Environment
Grafana-agent is related to machine charms in an openstack cloud.
Relevant log output
msg="failed to send usage report" retries=0 err="Post \"https://stats.grafana.org/agent-usage-report\": context deadline exceeded

Additional context
No response

We have a few duplicates of this issue, so I'm closing this one in favor of #266.


firefox html2canvas text display unusual

use the latest [1.0.0]
text display unusual on result image.

3 problems
1.text overlapping
2.add letter-spacing can figure out overlapping，but text margin irregular event it is a single word !!!  for example "Let" "first" in above image
3.only happen in firefox
OS
macOS Big Sur 11.4; firefox version: 89.0.2(64Bit)

@niklasvh help

@cookcc can you create a repro on jsfiddle.net ?

i figure out this problem by using image replace the text.
there isn't any other handle，u can try it out with html include text，then html2canvas，the result image displays font space is abnormal. the font family is "DIN Alternate";

@cookcc can you create a repro on jsfiddle.net ?

i figure out this problem by using image replace the text.
there isn't any other handle，u can try it out with html include text，then html2canvas，the result image displays font space is abnormal. the font family is "DIN Alternate";

22https://github.com/xinconan/blog/issues/22
this is the same problem：text overlapping，but is doesn't solve yet

22
this is the same problem：text overlapping，but is doesn't solve yet

I get this exact same issue in both Chrome and Firefox when using a non-standard font family, such as CiscoSansTT
CiscoSansTTRegular
OS
macOS Monterey 12.0.1; firefox version: 94.0.2 (64-bit); chrome 92.0.4515.159 (x86_64)

Hello,
I also faced the same problem there is a sample,
run index.html, wait 2 sec and look at variable
window.resultPng < there is PNG with illustration
index.zip


Add Alias To Discard All Unstaged Files

Added alias gda => git discard all to checkout all unstaged files & folders in the project.

gco . is not hard to remember.


Move java arrays module to another repo

Description:
This is a part of Standard Library Repo migration
Based on other dependencies: https://thisaruguruge.github.io/ballerina_dependencies/

Related issues: #23559, #23527, #23506

Related issue https://github.com/ballerina-platform/ballerina-lang/issues/21313

Blocking due to this issue https://github.com/ballerina-platform/ballerina-lang/issues/25301


No means to style opened drop-down

I wanted to style the caret in the drop-down differently when the menu was open, so I changed this line:
template = '
';

to this:
template = '
';

which worked great, but maybe this should be incorporated into the main codebase?

open is set on the root div in the current version


Check if there are at least 20 open concept exercise issues

@SleeplessByte I'm gonna merge this. If you have any comments, please do post them and I can fix them later :)


Add Map Roulette Integration to Rapid

Description
OK, so the TL;DR is that I want to be able to open up Rapid and look at the map and see all the Map Roulette Issues on the map and address them.
This is how I would propose that the feature is added:

Add a new Section to the "Issues" panel that would be "MapRoulette Tasks"
This new section would be a check box to enable or disable map roulette tasks. Once enabled I would propose that there is an additional box that would allow the user enter a Map Roulette Challenge ID so that the user would only see the issues from a specific challenge populated on the map.

The user would be able to get that challenge ID from the URL that they are using to look at the map roulette challenge

Once the user has enabled maproulette tasks and optionally filled in a specific challenge ID then Rapid would use the Map Roulette API to fetch the Tasks from the bounding box as shown on the map.
curl -X 'PUT'
'https://maproulette.org/api/v2/tasks/box/-71.0749/42.3564/-71.0868/42.3764?limit=5&page=0&excludeLocked=false&order=ASC&includeTotal=false&includeGeometries=true&includeTags=false'
-H 'accept: application/json'
[
...
  {
    "id": 186693991,
    "owner": -1,
    "ownerName": "",
    "title": "w817137122@2",
    "parentId": 41497,
    "parentName": "Boston - Untagged Crossing Ways",
    "point": {
      "lat": 42.3703402020978,
      "lng": -71.0801099567685
    },
    "bounding": "",
    "blurb": "",
    "modified": "2023-10-06T17:48:31.605Z",
    "difficulty": -1,
    "type": 2,
    "status": 0,
    "pointReview": {},
    "priority": 0
  },
...
]

Each of the returned items would be added on the map as a dot of some kind as the point indicated in the data retrieved.

When a user hovers over the dot they would see the title of the issue (e.g. - "Boston - Untagged Crossing Ways")
When a user clicks on the dot then rapid would make another request to Map Roulette to fetch the task details.

curl -X 'GET'
'https://maproulette.org/api/v2/task/186693991'
-H 'accept: application/json'
{
  "id": 186693991,
  "name": "w817137122@2",
  "created": "2023-10-06T14:52:10.172Z",
  "modified": "2023-10-06T14:53:46.747Z",
  "parent": 41497,
  "instruction": "",
  "location": {
    "type": "Point",
    "coordinates": [
      -71.0801099567685,
      42.3703402020978
    ]
  },
  "geometries": {
    "type": "FeatureCollection",
    "features": [
      {
        "type": "Feature",
        "geometry": {
          "crs": {
            "type": "name",
            "properties": {
              "name": "EPSG:0"
            }
          },
          "type": "LineString",
          "coordinates": [
            [
              -71.0801215,
              42.3702846
            ],
            [
              -71.0801112,
              42.3703298
            ],
            [
              -71.0800999,
              42.3703961
            ]
          ]
        },
        "properties": {
          "footway": "crossing",
          "highway": "footway",
          "surface": "asphalt",
          "priority": 0,
          "identifier": "w817137122@2",
          "instructions": "None",
          "osmIdentifier": "way/817137122"
        }
      }
    ]
  },
  "status": 0,
  "review": {},
  "priority": 0,
  "changesetId": -1,
  "errorTags": "",
  "tags": []
}

Node: If the instructions are "none" then you might need to fetch the instructions from the challenge.
curl -X 'GET'
'https://maproulette.org/api/v2/challenge/41497'
-H 'accept: application/json'
Then Rapid would pop up a box with the following info:
Challenge Name, Feature ID, Instructions, etc
Also there would be a Button to "Lock" the task (so no one else works on this task). If the lock doesn't work then you report that someone else has it locked. If the Lock works then display the locked state.
The mapper then fixes the issue and clicks one of the resolution buttons on the dialog box associated with this issue.
"fixed", "not an issue", "too hard", "skip", "already fixed".
Rapid would then update the task and unlock it.
Note: I don't know that locking is that important. It is more important for mapathons when lots of people are working on the same challenge. In most cases it is not needed.
I'd like to be able to see the dots and zoom in and fix a bunch of issues and then click the dots and "fix" each one.
To be able to lock and update the MR task the mapper will have had to enter a Map Roulette UserID.
Note: I don't know what the API to fetch tasks from a specific challenge in a bounding box is. I've asked because they must have it... or maybe they get all and filter on the "parent" field? (yuck).
There is  JOSM plugin that performs this entire workflow if you are interested.
Map Roulette swagger is here: https://maproulette.org/docs/swagger-ui/index.html#/

There is JOSM plugin that performs this entire workflow if you are interested.

Poke me if there are questions on the API.

cc: @mvexel

All righty- there's a lot of raw material here to work with, so let's break this work down.
Maproulette has challenges, which are themed groupings of small tasks. For example, somebody might create a challenge that's to 'map all the parking spaces in a city', consisting of thousands of tasks to map a single parking lot. Challenge creators have a lot of latitude in the tasks they create- they can include descriptions of what the challenge requires. Some challenges might ask for simple things like 'if this is a parking lot, just draw the perimeter of the parking lot'. The same challenge could instead be much more detailed and might ask the user to map the individual parking spot geometries, parking ways with directional information, etc. It's very open and free-form, which makes this task quite a big one!
Task 1: Getting started and Understanding the API

[ ]  head to maproulette.org and sign in using your OSM id.
[ ] Pop open the browser devtools networking tab and filter on requests to '/api'.
[ ] Navigate around on the site and click on a challenge. What happens, API-wise? What HTTP verb is being used? Can you cross-reference the calls you're seeing with the Swagger Documentation? (Note: the API is pretty big, for now we will focus on just task and challenge APIs.
[ ] Can you see if you can figure out how to fetch all the challenges that exist in a certain bounding box?
[ ] Do the API calls change as you zoom in closer to the map? What different APIs are called once you zoom close enough to see individual task pins?

After this investigation,  you should have a handle on the API. Now see if you can hand-construct some API calls using a tool such as curl or postman:

[ ] Get all the challenges in a bounding box.
[ ] Get all the tasks for one of the challenges you just obtained from your bbox query.
[ ] Extra credit: As @atiannicelli mentions above, we're not sure if it's possible to obtain tasks for a challenge filtered by BBOX. Spend some time and see if you can figure that out!
[ ] Are the tasks filterable somehow? How might we allow users to only display certain types of tasks?

@voscarmv Next task will be to write a Service in Rapid to obtain all of the challenges in an area, and all the tasks for a specific challenge.  I'll fill that in when we get to it. :)

If you need some sample API returns, https://github.com/JOSM/MapRoulette/tree/master/src/test/resources/__files/api/v2 has samples from MapRoulette's API (note: the responses are ~9 months old at this point)

Since it was not easy to find I thought I'd answer the extra credit :)
I did find out how to get tasks in a specific bounding box using the /tasks/box/ API. I forgot to post that I had asked the developers how to do it and they replied that the /tasks/box API should work and you can add a "cid" to show tasks from a specific challenge or "pid" if you want tasks from a project. (A project is just a collection of challenges).
Also, if you have MapRoulette specific API questions you can ask them in the maproulette-dev channel on the OpenStreetMap slack (osmus.slack.com).

Thank you for the tips @tsmock and @atiannicelli !

https://github.com/maproulette/maproulette3/issues/2211 was filed by Alex I. as a result of @voscarmv's investigation.

This feature landed in 2.3 and is receiving updates in 2.4. Closing!


Feat/test suite

What does this PR do?

Adds block test
Adds test for wallets endpoints

@cedriking @kouraf please test and give me feedback


Day1P1-3, Day4P4, starter materials index.md

@brianhlin @osg-cat: I updated docs/materials/index.md from last year with Day1P1-3 and Day4P4 parts updated, but left everything after Monday commented out. Brian will need to update index.md for Monday P4.


(PUP-10943) Puppet read registry until WCHAR_NULL

On Windows, it is possible to have a registry that contains corrupted
data after the WCHAR_NULL characters, that can break puppet when reading
the registy.
Part of the fix was done in PUP-10536, but when the WCHAR_NULL from the
registry is \u0000 instead of \u0000\u0000, the split did not work.
Now WCHAR_NULL is forced encoded to UTF-16LE, meaning \u000 so puppet
will now stop at the WCHAR_NULL char.
The initial issue can be reproduced by importing file.reg using
reg import  .\file.reg
----file.reg----
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PUP105360000]
"DisplayName"="PUP105"
"DisplayVersion"=hex(2):32,0,0,0,f3,23,8a,bc,fa,7f,0,0,10,65,74,b9,fa,7f,0,0,90,d8,55,6f,59

Just a note that the merge-up will have to be done manually (or a different PR should be created for main) because this file is in a different path in Puppet 7.


Tune-in don't show a favorites

I entered my email to retrieve my TUNE-IN  favorites, but it doesn't work

I entered my username (visible below your email when you check your account profile in the TuneIn website)

Yeah, I should probably make that more clear in the docs. Tune-In is kind of strict when it comes to that. You need your username indeed instead of your email.

I'm sorry, but entering the username and making the last update, the job remains in the background and displays nothing.
The profile set is public in my account.

what do you mean with "the job remains in the background" ? Did you wait long enough until the initial sync is done ? That could take a few minutes on large collections

yes, it remains for a few minutes as shown in the photo, then it remains empty

That is strange but I found out that the Tune-In structure is a bit strange...
Are you using the new library in Intune ? Music Assistant will (for now) only show items that are in your Tune-In library

I think so, the library are the favorites I have both in the phone app and in web access

Are you running version 1.0.13 of Music Assistant ?

yes, the lastest

May I ask your Tune In username ? Or send it to me as PM on discord.
The profile is public so I have a look what is special about it

how do i find you on discord

marcelveldt

Or the Music Assistant channel
https://discord.com/channels/753947050995089438/753947050995089442

in addition to your name I need the 4 numbers    #xxxx

0393

As discussed in discord you now see the TuneIn stations in MA.
I've just checked in a small fix for the buffer of radio stations which might also fix playback on Sonos devices.
If you have time, please test with the new 1.0.14 version. Thanks!

closing this as it was confirmed fixed by another user. If you still experience issues, please reopen this issue or create a new one. thanks!

@marcelveldt can you describe how you fixed this issue as I'm experiencing the same...
Thanks

@marcelveldt can you describe how you fixed this issue as I'm experiencing the same... Thanks

please open a new issue report, thanks!


Conformance issue with JSON specification (ECMA-404)

VBA-JSON does not conform to the ECMA-404 JSON stanadard. A valid JSON document contains a value, but VBA-JSON only allows an object or array. For example, the following are valid JSON documents:
Group 1 (success)
ParseJson("{ }").count Result 0, allowed by VBA.JSON
ParseJson("{ ""abc"": 1, ""def"": 2 }").count Result 2, allowed by VBA-JSON
ParseJson("[ ]").count Result 0, allowed by VBA-JSON
ParseJson("[ 1, 2, 3]").count Result 3, allowed by VBA-JSON
Group 2 (failure)
ParseJson("""abc""") Result Error 10001, not allowed by VBA-JSON
ParseJson("123") Result Error 10001, not allowed by VBA-JSON
ParseJson("true") Result Error 10001, not allowed by VBA-JSON
ParseJson("false") Result Error 10001, not allowed by VBA-JSON
ParseJson("null") Result Error 10001, not allowed by VBA-JSON
Supporting Group 2 in VBA-JSON is complicated. Until Group 2 is supported it is suggested that the documentation reflect that VBA-JSON only supports objects and arrays as a JSON document.

Related to this I manually added the following method to the JsonConverter module to support the reading of a JSON string.
Public Function ParseJsonString(json_String As String) As String
    Dim index As Long
    index = 1
    ParseString = json_ParseString(json_String, index)
End Function

This was relatively easy to write. I haven't looked at the others.
    Dim result As String
    result = JsonConverter.ParseJsonString("""abc""")
    Rem result is "abc"

Heres ParseJsonNumber
Public Function ParseJsonNumber(json_String As String) As Variant

    Dim index As Long
    index = 1
    Rem Pad the right with whitespace so json_ParseNumber has an explicit signal
    Rem we reached end of number.
    ParseJsonNumber = json_ParseNumber(json_String + " ", index)

End Function


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 8414948:
:clock10: Pending: waiting for processors (25 builds ahead of you)
:warning: Docs Build is busy, currently there are 25 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 8414948:
:clock10: Full build: the average full build time is 5 min(s) 7 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 8414948:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Pagination docs

Is there a maximum for limit and offset?

/pkgs: 1000
/maintainers:  1000
/pkgs/{package_name}/history:  50
/search:  50

Thanks!


Retry on not published events in case of status 207

If event publishing to nakadi returns status 207 at least one event was not published. In this case, retry to send not published events and postpone throwing an exception.
https://github.com/zalando-nakadi/fahrschein/blob/master/fahrschein/src/main/java/org/zalando/fahrschein/ProblemHandlingRequest.java#L115

Would you expect the fahrschein library to do this automatically, or do you mean the todo at https://github.com/zalando-nakadi/fahrschein/blob/master/fahrschein/src/main/java/org/zalando/fahrschein/ProblemHandlingRequest.java#L124 which would allow the application code to more easily resend failed events?
I don't remember in which situations nakadi would respond with a 207, but I could also imagine that an immediate retry would not work, as nakadi could need some time to recover.

Would you expect the fahrschein library to do this automatically, or do you mean the todo at https://github.com/zalando-nakadi/fahrschein/blob/master/fahrschein/src/main/java/org/zalando/fahrschein/ProblemHandlingRequest.java#L124 which would allow the application code to more easily resend failed events?
I don't remember in which situations nakadi would respond with a 207, but I could also imagine that an immediate retry would not work, as nakadi could need some time to recover.

This can happen during nakadi deployments.


kleurringNummer from tblWaarneming not present in tblKleurring

In observations (table tblWaarneming) there are some KleurringNummer values which don't match any value in birds (table tblKleurring). However, for all of them except one it is a question of uppercase/lwoercase difference. See details here below:

WaarnemingNummer
notes

AAAr
AAAR present in tblKleurring

aaar
AAAR present in tblKleurring

ACAZ

bzaa
BZAA present in tblKleurring

bzaf
BZAF present in tblKleurring

dbaz
DBAZ present in tblKleurring

knaf
KNAF present in tblKleurring

ygac
YGAC present in tblKleurring

ZMAt
ZMAT present in tblKleurring

@Eric, Marc: I can easily transform all values to uppercase while pre-processing. Feel free to change it in tblWaarneming database table if you wish. If there is a special reason to leave them lowercase or other thoughts about, please let me know asap. Thanks.
About ACAZ, I found 31 observations with such code. I show here below just some observations (action code is also given) to give an idea about the kind of values present in these records:

raw_Nummer
raw_Datum
raw_EuringCode
raw_LeeftijdCode
raw_KleurringNummer
raw_KleurringPlaats
...
 In the meanwhile I filter them out.

Eric's answer about uppercase/lowercase problem:

alles omgezet naar uppercase.

Eric's answer about ACAZ:

Het probleem van ACAZ snap ik niet.
Die zit wel degelijk in de tblKleurring. Het is een omgeringde vogel die tegenwoordig niet meer de ring A
Life history rapport.pdf
CAZ draagt, maar de ring B0 (zie bijgevoegde lifelist). Overigens vind ik 33 (en niet 31 observaties van deze vogel!!!!!!).

I confirm that all birds$raw_Nummer are all uppercase:
> all(toupper(birds$raw_Nummer) == birds$raw_Nummer)
[1] TRUE

and obs_and_acts$raw_KleurringNummer as well
obs_and_acts %>%
  filter(raw_KleurringNummer != toupper(raw_KleurringNummer)) %>%
  distinct(raw_KleurringNummer) %>% nrow()

I still perform these checks in the pipeline in case future anomalies would appear.

About ACAZ I found the problem: there is a bird with Nummer equal to ACAZ , i.e. ACAZ + space. The space at the end should be removed: for a computer they are two different birds.
In any case, I added a permanent check in pipeline for detecting presence of spaces in all columns of tblKleurring:
map_dfr(birds, ~ mutate(birds, space_detect = str_detect(., pattern = " "))) %>%
  filter(space_detect == TRUE)

There are also two observations in tblWaarneming with KleurringNummerequal to ACAZ  (ACAZ + space):

raw_Nummer
raw_Datum
raw_EuringCode
raw_LeeftijdCode
raw_KleurringNummer

519
1999-07-02
05920
PU
ACAZ

16186
1999-06-01
05920
PU
ACAZ

Space removal should also happen in this table.

Thanks Eric. All anomalies are solved at db level.


Filter by max file size and with-height of image

Additionally to minimum file size and with-height filter sometimes needed also filter by max file size and with-height. Can you add it too, if this is not so hard?

Instead of large images, you need smaller ones?

I need middle - not small, not large :)
вт, 21 мая 2019 г., 8:35 eight<EMAIL_ADDRESS>
Instead of large images, you need smaller ones?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eight04/image-picka/issues/196?email_source=notifications&email_token=AACSGFQGB6E46RMKJKGOXO3PWOC2BA5CNFSM4HOHMER2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV2ZTFY#issuecomment-494246295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACSGFVBQGEMQFYWFN7FD7DPWOC2BANCNFSM4HOHMERQ
.


Don't use detached with Windows; kill process with taskkill

Fixes https://github.com/jasongilman/proto-repl/issues/300
It appears that spawning detached in Windows isn't the correct approach. This reverts 'detached' when running in Windows. Also, nodejs and killing the child process also doesn't play nicely in Windows, so this uses the native taskkill command instead.
This commit fixes the issue of the extra terminal window starting in Windows. It also fixes the killing of the JVM process associated with the REPL on REPL-exit (as the original PR intended).
@jasongilman Please take a look at this one soon, as proto-repl is unusable on Windows in the current release.

Thanks for submitting this!

Thanks for looking at it so quickly!


Introduce NVVMtoLLVM Pass

MLIR has a new pass now NVVMToLLVM. It is introduced to generate PTX easily using tablegen.
This PR adds the pass in ConvertToNVVM pipeline.

It needs following PR from upstream
https://reviews.llvm.org/D155060

Already submitted in https://github.com/openxla/iree/pull/14391


notNull Violation: Revision.documentId cannot be null

hi,
First off: great project! Really appreciated.
I'm having a bit of a trouble to get it working, though.
When I update trailed model, sequelize returns:
{ SequelizeValidationError: notNull Violation: Revision.documentId cannot be null
    at Promise.all.then (..../node_modules/sequelize/lib/instance-validator.js:77:15)

I've left options as defaults. My update query runs as expected.
What exactly is purpose of document / documentId fields?
Should I include documentId in query somewhere?

@ketus update the libraries (and sequelize) and check if this error persists.

document store all entity data in JSON format, in revision number
documentId is the primary key of the changed entity, utilized with model field to track the changes.

I resolve that issue with putting  revision.documentId = revision.document._id in function createAfterHook, before save.

@RsHalit if it's still a problem with the latest version without that manual change please reopen the issue and I'll look into it.


remove double build

make all has build as a dependency, and... a "recipe", which is the same as build.
Consequently, the build procedure was performed twice.
Also the top CmakeList has been removed because it is not used.
Signed-off-by: Bruno Vavala<EMAIL_ADDRESS>

done


C# Export vertices coordinates

Hello,

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
{Win 10

Platform
PC

SDK Version
2.16.1

Language
C#

Segment
others

I'm trying to export a data snapshot of the vertices in a json format.
Below, a sample of my code inspired by the C# capture example :
//...
using (var frames = pipeline.WaitForFrames())
                        {
                            var depthFrame = frames.DepthFrame.DisposeWith(frames);
                            PointCloud pc = new PointCloud();
                            var points = (Points) pc.Process(depthFrame).DisposeWith(frames);
                            var colorizedDepth = colorizer.Process(depthFrame).DisposeWith(frames);
                            Dispatcher.Invoke(DispatcherPriority.Render, updateDepth, colorizedDepth);
                            **Dispatcher.Invoke(DispatcherPriority.Render, savePoints, points);**

                        }
//...

static Action<Points> savePointClouds()
        {
            return new Action<Points>(points =>
            {
            using (points)
            {
                        Points.Vertex vertex = Marshal.PtrToStructure<Points.Vertex>(points.VertexData);
                        for (int i = 0; i < points.Count; i++)
                        {
                            var str = string.Format("x:{0}, y:{1}, z:{2}", vertex.x, vertex.y, vertex.z);
                        }
                }
            });
        }

My comprehension of the SDK tells me that variable vertex should be an Array of struct Vertex.
But I have failed to extract it after many code attempts
If someone has an idea, it will be helpful.
Thanks a lot

Hi there, I think I was trying to a very similar thing to yours but in C++, difference also being I was trying to save the data in .CSV format. Here was my issue, but from what I know this doesn't sound possible.

My comprehension of the SDK tells me that variable vertex should be an Array of struct Vertex.

That's right, you should use something like this:
var vertices = new Points.Vertex[points.Count];
points.CopyTo(vertices);

Thanks to you,
@HippoEug : efore I posted my issue I read yours but it was hard to me to correlate the methods in c++ with c# methods.
@ogoshen : Why I didnt' find the copyTo method in the sdk doc... :( I guess that it s because I didn't succeed in generating the doc for the wrapper C# when I compiled to the realsense dll.
Is there a place where I can find the C# doc, or I have to generate it ?
I will close this issue after I had an answer about this 👍
Best,

Hi @yohanb78,
Still need any support for this topic?
It looks the C# API doc needs to be improved.

Hello,
Yes you're right. I will close this issue, I have now moved my devlopment around the nodejs wrapper in order to be coherent with the stack of the rest of my apps.
Regards


phalcon 3,4 webhook problem

i have a webhook which i receive data from it , i run a function responsable for extracting data from that webhook and send a response , it takes to much within 20 min without sending the reposne while the 3 rd parti thinks that there is no response and it triggers again the webhook
in a normal way my function takes 11 sec to be executed when i run the function and replay the webhook from ngrok it works perfectly , also when i eliminate all my code and send only response when i receive the webhook it works perfectly
phalcon 3,4
linux
ngrok
Uplisting (webhook 3rd partie

)

@faroukdon, Since you are just asking for coding help, your question needs to be posted on a general coding site like StackOverflow.com.
Github is used for posting specific Phalcon bug reports and asking for new Phalcon features.
This issue is likely to get closed as an incomplete bug report here.

thanks