kotatogram-desktop: 1.4.1 -> 1.4.9 and add Darwin support

Motivation for this change
#148654
Things done
Package updated to the latest upstream version + tried to enabled building on macos since both tdesktop and kotatogram have upstream mac builds

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is macOS/SDK version is older than CMVideoFormatDescriptionGetHEVCParameterSetAtIndex was introduced? Can't I choose other macOS/SDK version somehow?

Looks like I'm hitting #130963

meh, x86_64-darwin times out, is there a way to increase the timeout?

Should be ready for the review now, should I call Darwin maintainers somehow explicitly (I have a friend with macOS who helped me to ensure that it builds & runs at least)?
Although, I had to patch out calls for APIs newer than 10.12 like requesting permissions and etc, nixpkgs also doesn't seem to have iconutil for some reason (I replaced it with png2icns, but looks like that makes 2x icons out of the train), headers of system libraries in nixpkgs seem to have some check macros that forced me to insert #undef check in a lot of files and the headers don't seem to have API_AVAILABLE macros for some reason.

Updated to 1.4.8

Nice, darwin fails at range-v3 tests due to -Werror

Nice, darwin fails at range-v3 tests due to -Werror

ofborg shows a test failure:
[211/1409] Building CXX object CMakeFiles/tg_owt.dir/src/rtc_base/async_socket.cc.o
=== test/integration/aligned_alloc ===
MALLOC_CONF="dirty_decay_ms:-1,muzzy_decay_ms:-1" /nix/store/4nmqxajzaf60yjribkgvj5j54x9yvr1r-bash-5.1-p12/bin/bash test/test.sh test/integration/aligned_alloc test/integration/allocated test/integration/extent test/integration/malloc test/integration/mallocx test/integration/MALLOCX_ARENA test/integration/overflow test/integration/posix_memalign test/integration/rallocx test/integration/sdallocx test/integration/slab_sizes test/integration/thread_arena test/integration/thread_tcache_enabled test/integration/xallocx test/integration/cpp/basic
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
=== test/integration/aligned_alloc ===
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (non-reentrant): fail
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (libc-reentrant): fail
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (arena_new-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (non-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (libc-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (arena_new-reentrant): fail
test_alignment_and_size (non-reentrant): pass
test_alignment_and_size (libc-reentrant): pass
test_alignment_and_size (arena_new-reentrant): pass
test_zero_alloc (non-reentrant): pass
test_zero_alloc (libc-reentrant): pass
test_zero_alloc (arena_new-reentrant): pass
--- pass: 6/12, skip: 0/12, fail: 6/12 ---
=== test/integration/allocated ===
test_main_thread (non-reentrant): pass
test_main_thread (libc-reentrant): pass
test_main_thread (arena_new-reentrant): pass
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (non-reentrant): fail
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (libc-reentrant): fail
test_alignment_errors:test/integration/aligned_alloc.c:24: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 0
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 9
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 17
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 33
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 129
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 257
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 513
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1025
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2049
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4097
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 8193
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 16385
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 32769
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 65537
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 131073
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 262145
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 524289
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 1048577
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 2097153
test_alignment_errors:test/integration/aligned_alloc.c:32: Failed assertion: (p != ((void*)0) || get_errno() != 22) == (false) --> true != false: Expected error for invalid alignment 4194305
test_alignment_errors (arena_new-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (non-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (libc-reentrant): fail
test_oom_errors:test/integration/aligned_alloc.c:63: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(9223372036854775808,<PHONE_NUMBER>854775808)
test_oom_errors:test/integration/aligned_alloc.c:76: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(4611686018427387904,<PHONE_NUMBER>5282163713)
test_oom_errors:test/integration/aligned_alloc.c:88: Failed assertion: (p != ((void*)0) || get_errno() != 12) == (false) --> true != false: Expected error for aligned_alloc(&p, 16,<PHONE_NUMBER>3709551600)
test_oom_errors (arena_new-reentrant): fail
test_subthread (non-reentrant): pass
test_alignment_and_size (non-reentrant): pass
test_alignment_and_size (libc-reentrant): pass

Yeah, I don't know what to do with that, jemalloc started failing tests with clang after rebasing to latest nixpkgs :(

Updated to 1.4.9


Filtering options for GET console/v1/gates

🚀 Deployed on https://64bed9da8af19f0e5a8b1039--cozy-fox-0defec.netlify.app


Update concept-authentication-phone-options.md

Fixed misspelled communications word
Added New Zealand as a possible country to receive Whatsapp message with MFA code instead using normal SMS, as announced on https://techcommunity.microsoft.com/t5/microsoft-entra-blog/what-s-new-in-microsoft-entra/ba-p/3796395

#sign-off


Allow focus change

This fixes clicks on menu items in steam client.

You can just copy-pasta the XWM instead of maintaining a fork.


Doesn't compile on rustc 1.63.0 OSX 12.6 Intel

when I try to build an empty project with just anyhow as a dependency it gives the following compiling errors:
❯ cargo build
   Compiling anyhow v1.0.65
error[E0407]: method `provide` is not a member of trait `StdError`
   --> $CARGO_HOME/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.65/src/context.rs:131:5
    |
131 | /     fn provide<'a>(&'a self, demand: &mut Demand<'a>) {
132 | |         self.error.provide(demand);
133 | |     }
    | |_____^ not a member of trait `StdError`

error[E0407]: method `provide` is not a member of trait `StdError`
   --> $CARGO_HOME/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.65/src/context.rs:145:5
    |
145 | /     fn provide<'a>(&'a self, demand: &mut Demand<'a>) {
146 | |         demand.provide_ref(self.error.backtrace());
147 | |         self.error.provide(demand);
148 | |     }
    | |_____^ not a member of trait `StdError`

I'm on a 2018 MacBook Pro 13" Intel with OSX 12.6, rustc 1.63.0, cargo 1.63.

I am not able to reproduce this. Possibly you have an old version of rust-analyzer or intellij-rust screwing up the target directory (old versions of those tend to do that).
% cargo --version
cargo 1.63.0 (fd9c4297c 2022-07-01)

% rustc --version
rustc 1.63.0 (4b91a6ea7 2022-08-08)

% cargo init
     Created binary (application) package

% cargo add anyhow
    Updating crates.io index
      Adding anyhow v1.0.65 to dependencies.
             Features:
             + std
             - backtrace

% cargo build
    Updating crates.io index
  Downloaded anyhow v1.0.65
  Downloaded 1 crate (43.6 KB) in 0.23s
   Compiling anyhow v1.0.65
   Compiling repro v0.1.0
    Finished dev [unoptimized + debuginfo] target(s) in 1.49s

If you have repro steps that reliably reproduce this, we can reopen.

I have met the similar problem and the solution is to clear the target directory by cargo clean and it successfully compiles then.


Remove oss storage driver and alicdn storage driver middleware

Similar to https://github.com/distribution/distribution/pull/3982, also tracked in https://github.com/distribution/distribution/issues/3978.
This PR removes oss storage driver from distribution as well asalicdn storage middleware which only works with the oss driver.
There are several reasons for it:

no real-life expertise among the maintainers
oss is compatible with S3 API operations required by S3 storage driver

This will also remove dependencies that are also hard to keep up with.
NOTE: OSS is S3 compatible (see https://www.alibabacloud.com/help/en/oss/developer-reference/compatibility-with-amazon-s3) so users should consider relying on that

Codecov Report
Patch and project coverage have no change.

Comparison is base (65b5746) 55.85% compared to head (3f1859a) 55.85%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3985   +/-   ##
=======================================
  Coverage   55.85%   55.85%
=======================================
  Files         110      110
  Lines       11069    11069
=======================================
  Hits         6183     6183
  Misses       4193     4193
  Partials      693      693

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


Appending to the DOM rather than re-rendering entire DOM?

I have a page that can load easily, 6000 elements at once. I'm trying to lazy-load this data on-scroll so the dom gets updated as you scroll. However, I'm unsure whether ractive will re-render the entire dom when data is appended or whether it will simply append the elements to the dom.
Another issue is removing all of these elements and re-doing this process when changing views (performance).

It would be cool if we can reuse existing DOM on first ractive.render()  event. Makes ractive.render()  use whats already in DOM. This way we can render HTML on server, serve it to client with ractive app and data, ractive would set all events on existing DOM and change content only if data is changed.

As progressive enhancement is coming to 0.8 (yay), I'm closing this.


Index of Coincidence

The index of coincidence "provides a measure of how likely it is to draw two matching letters by randomly selecting two letters from a given text" (reference: https://en.wikipedia.org/wiki/Index_of_coincidence).
As we know this index will be around 0.067 for English text, this may be a useful indicator for plaintext strings. An example usage can be seen here: https://gchq.github.io/CyberChef/#recipe=Index_of_Coincidence()&input=VGhpcyBhIHRlc3QgZm9yIHRoZSBpbmRpY2F0b3Igb2YgY29pbmNpZGVuY2U
I've added this function for both data offsets/string values to the math module. I've also added documentation and tests for it.

Updated for compatibility with YARA v4.3.2; tests passing as expected.


JSON output type, to output file, is cut-off to 8k file.

When using the JSON output type, the output file is cut-short at 8192 bytes.  Interestingly, the CSV output does not have the same problem.
I can work-around the issue by not specifying an output file and instead redirect stdout to a file.
Repro Info:
I am processing this pdf:
http://epra.ca/wp-content/uploads/2016/04/April-2016-National-List-v5.pdf
using this command line:
C:\tabula>java -jar ./tabula-java.jar -p2 -fJSON -oout.json April-2016-National-List-v5.pdf
The out.json file is exactly 8192 bytes (should be about 17k), and the end of the file leaves the json object unclosed.  It looks like this:
        {
          "top": 262.71,
          "left": 645.96,
          "width": 88.13997650146484,
          "height": 7.019999980926514,
          "text": "$0.75 ?"
        }
      ],
      [ { "top":<eof>

Thank you.

Odd... I get a file that's 16384 bytes, but it's also truncated. I can confirm this, but don't know enough about Java to take it on. Mike or Manuel?

Hrm...looks like we need to flush() the output stream in CommandLineApp.

Fixed with @melisabok's contribution: 653599f3dee2e7dbe1939b465e5423d331a7c9d5


Breaking changes and plan forward: drop legacy vim/neovim support

I have been maintaining a minimal level of backward compatibility support for outdated neovims -- but from now on, there will be no backward compatibility support for old versions of neovim.
This means that neovim will be always assumed to be latest (but not including nightly).

The minimum neovim version supported will be 0.7.0 and catching up with latest neovim version will be mandatory.
config/init.vim will be also re-written as config/init.lua
vimrc will be heavily refactored to (modular) lua configs as much as possible.
Plugin managers will be switched from vim-plug to packer.nvim. Vanilla vim will have almost no plugins working.
Overall, these changes will limit the vanilla vim support, but in practice it should have no problem for most of the users.

This is inevitable because all the plugins keep changing and breaking as they require latest features, so there's no point of supporting different versions of neovim using a lot of has('nvim-0.x.x') branchings..

Minimum neovim version will be 0.8.0 since May 2023.

Starting 2024, neovim 0.8.0 will retire, requiring neovim 0.9+. FYI, neovim 0.10 is expected to ship in March 2024.


Failing to build current dev version (OpenSSL 3.0.0-dev)

navix@navix0:~/Downloads/openssl$ ./Configure linux-x86_64 --prefix=/usr

Configuring OpenSSL version 3.0.0-dev for target linux-x86_64
Using os-specific seed configuration
Creating configdata.pm
Creating Makefile

**********************************************************************
***                                                                ***
***   OpenSSL has been successfully configured                     ***
***                                                                ***
***   If you encounter a problem while building, please open an    ***
***   issue on GitHub <https://github.com/openssl/openssl/issues>  ***
***   and include the output from the following command:           ***
***                                                                ***
***       perl configdata.pm --dump                                ***
***                                                                ***
***   (If you are new to OpenSSL, you might want to consult the    ***
***   'Troubleshooting' section in the INSTALL file first)         ***
***                                                                ***
**********************************************************************

Correctly detects OS and successful message.
navix@navix0:~/Downloads/openssl$ make -j4

Error in crypto/trace.c, something seems to not be defined.
CC="gcc" /usr/local/bin/perl crypto/md5/asm/md5-x86_64.pl elf crypto/md5/md5-x86_64.s
crypto/trace.c:119:46: error: 'OSSL_TRACE_CATEGORY_PROV' undeclared here (not in a function); did you mean 'OSSL_TRACE_CATEGORY_NUM'?
  119 | #define TRACE_CATEGORY_(name)       { #name, OSSL_TRACE_CATEGORY_##name }
      |                                              ^~~~~~~~~~~~~~~~~~~~
crypto/trace.c:135:5: note: in expansion of macro 'TRACE_CATEGORY_'
  135 |     TRACE_CATEGORY_(PROV),
      |     ^~~~~~~~~~~~~~~
crypto/trace.c:119:46: error: 'OSSL_TRACE_CATEGORY_FETCH' undeclared here (not in a function); did you mean 'OSSL_TRACE_CATEGORY_TRACE'?
  119 | #define TRACE_CATEGORY_(name)       { #name, OSSL_TRACE_CATEGORY_##name }
      |                                              ^~~~~~~~~~~~~~~~~~~~
crypto/trace.c:136:5: note: in expansion of macro 'TRACE_CATEGORY_'
  136 |     TRACE_CATEGORY_(FETCH),
      |     ^~~~~~~~~~~~~~~
make[1]: *** [Makefile:10145: crypto/libcrypto-lib-trace.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/navix/Downloads/openssl'
make: *** [Makefile:165: all] Error 2

Dump from configdata.pm

Command line (with current working directory = .):

    /usr/local/bin/perl ./Configure linux-x86_64 --prefix=/usr

Perl information:

    /usr/local/bin/perl
    5.30.0 for x86_64-linux

Enabled features:

    afalgeng
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    fips
    gost
    idea
    legacy
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    pinshared
    ocb
    ocsp
    padlockeng
    pic
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    static-engine
    stdio
    tests
    threads
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    ktls                    [default]        OPENSSL_NO_KTLS
    asan                    [default]        OPENSSL_NO_ASAN
    buildtest-c++           [default]
    crypto-mdebug           [default]        OPENSSL_NO_CRYPTO_MDEBUG
    crypto-mdebug-backtrace [default]        OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE
    devcryptoeng            [default]        OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128     [default]        OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                     [default]        OPENSSL_NO_EGD
    external-tests          [default]        OPENSSL_NO_EXTERNAL_TESTS
    fuzz-libfuzzer          [default]        OPENSSL_NO_FUZZ_LIBFUZZER
    fuzz-afl                [default]        OPENSSL_NO_FUZZ_AFL
    md2                     [default]        OPENSSL_NO_MD2 (skip crypto/md2)
    msan                    [default]        OPENSSL_NO_MSAN
    rc5                     [default]        OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                    [default]        OPENSSL_NO_SCTP
    ssl-trace               [default]        OPENSSL_NO_SSL_TRACE
    trace                   [default]        OPENSSL_NO_TRACE
    ubsan                   [default]        OPENSSL_NO_UBSAN
    unit-test               [default]        OPENSSL_NO_UNIT_TEST
    uplink                  [no uplink_arch] OPENSSL_NO_UPLINK
    weak-ssl-ciphers        [default]        OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                    [default]
    zlib-dynamic            [default]
    ssl3                    [default]        OPENSSL_NO_SSL3
    ssl3-method             [default]        OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "r",
    CC => "gcc",
    CFLAGS => "-Wall -O3",
    CXX => "g++",
    CXXFLAGS => "-Wall -O3",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    asm_arch => "x86_64",
    bn_ops => "SIXTY_FOUR_BIT_LONG",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-pthread -m64",
    cppflags => "",
    cxxflags => "-std=c++11 -pthread -m64",
    defines => [  ],
    disable => [  ],
    dso_ldflags => "-z defs",
    dso_scheme => "dlfcn",
    enable => [ "afalgeng" ],
    ex_libs => "-ldl -pthread",
    includes => [  ],
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DOPENSSL_USE_NODELETE -DL_ENDIAN",
    lib_defines => [  ],
    module_cflags => "-fPIC",
    module_cxxflags => "",
    module_ldflags => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    multilib => "64",
    perl_platform => "Unix",
    perlasm_scheme => "elf",
    shared_cflag => "-fPIC",
    shared_defflag => "-Wl,--version-script=",
    shared_defines => [  ],
    shared_ldflag => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,-soname=",
    shared_target => "linux-shared",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = ar
    ARFLAGS         = r
    CC              = gcc
    CFLAGS          = -Wall -O3
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXX             = g++
    CXXFLAGS        = -Wall -O3
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = /usr/local/bin/perl
    RANLIB          = ranlib
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl
    Configurations/common.tmpl

Makefile.zip

Thank you for reporting this issue. A fix is already in preparation, see #9218. For the moment, you can either download and apply the patch, or simply remove the two lines yourself.

... or simply remove the two lines yourself.

see https://github.com/openssl/openssl/pull/9218/files#diff-a8a70aedef9f628d7c0b463f75f8a323

#9218 now merged


Fix 'zh-tw' language detection.

Exception occurs for some documents:
org.grobid.core.utilities.LanguageUtilities: Cannot detect language because of:
org.grobid.core.exceptions.GrobidException: [GENERAL] Language id should consist of two or three letters, but was: zh-tw

Coverage remained the same at 39.105% when pulling d698a1ecd6dee793ff826c881dbedc5cf047c969 on aoboturov:fix/add_zh_tw_locale into 49e8fe036f24c80d11a257eee3edda5c4c26e45c on kermitt2:master.

Many thanks !


ApiClient$StatusCodeException: 400 when use getMetadata4Album

Describe the bug
bug appear when get Track meta
To Reproduce
session.api().getMetadata4Track(TrackId.fromUri("Track id to here"))
Expected behavior
work without err
Screenshots/Stracktraces/Logs
xyz.gianlu.librespot.dealer.ApiClient$StatusCodeException: 400:
    at xyz.gianlu.librespot.dealer.ApiClient$StatusCodeException.checkStatus(ApiClient.java:366)
    at xyz.gianlu.librespot.dealer.ApiClient$StatusCodeException.access$000(ApiClient.java:357)
    at xyz.gianlu.librespot.dealer.ApiClient.clientToken(ApiClient.java:345)
    at xyz.gianlu.librespot.dealer.ApiClient.buildRequest(ApiClient.java:79)
    at xyz.gianlu.librespot.dealer.ApiClient.send(ApiClient.java:114)
    at xyz.gianlu.librespot.dealer.ApiClient.send(ApiClient.java:131)
    at xyz.gianlu.librespot.dealer.ApiClient.getMetadata4Album(ApiClient.java:168)
    at org.librespotapis.Main.loadmeta(Main.java:265)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Version/Commit
xyz.gianlu.librespot:librespot-lib:1.6.3

I also encountered this.
Did Spotify change the api?

Likely cause: Your classpath is incorrect.
Version.java returns "versionString" as the current version of librespot-java, and if the package does not find a version it will populate ?.?.? which I'm guessing Spotify recently added validation against. I don't fully understand what is happening here.
To fix it, you should try switching your dependency from librespot-lib -> librespot-player. For me this made the version number populate correctly and the library began functioning again. You may also run into issues depending on how your Java build is packaged and ran. To validate that you don't encounter the issue, check Version.versionString() at runtime to see if it is set correctly.

I can confirm what @Lustyn is saying, they recently added a check on the version string probably to parse it for their own stuff.
I had to fix this in go-librespot too: https://github.com/devgianlu/go-librespot/commit/92ade8e23f0ccabf77594f7d470ed104cc04c306


typo

Point 3 under 'Guaranteed order' section has a typo.  I guess "Customer adds removes Item A from their shopping cart" should say "Customer removes Item A from their shopping cart"

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

ID: 6b70ef3e-1007-803f-4cce-8fbc91c26fd2
Version Independent ID: 38703e02-7db4-b545-9855-4e2e7a19b305
Content: Change feed design patterns in Azure Cosmos DB
Content Source: articles/cosmos-db/change-feed-design-patterns.md
Service: cosmos-db
GitHub Login: @timsander1
Microsoft Alias: tisande

@swasifali, Thank you for pointing this out. We are working on this and would update the doc accordingly.

@swasifali Thanks for pointing out, I submitted a fix. We will now close this issue.
#please-close


Enable Milagro BLS in CI

This draft PR shows the CI errors in phase 1 tests.
FAILED eth2spec/test/phase1/sanity/test_blocks.py::test_with_shard_transition_with_custody_challenge_and_response
FAILED eth2spec/test/phase1/block_processing/test_process_shard_transition.py::test_multiple_offset_slots
FAILED eth2spec/test/phase1/sanity/test_blocks.py::test_custody_slashing - As...
FAILED eth2spec/test/phase1/block_processing/test_process_shard_transition.py::test_basic_crosslinks
FAILED eth2spec/test/phase1/sanity/test_blocks.py::test_process_beacon_block_with_normal_shard_transition
FAILED eth2spec/test/phase1/sanity/test_blocks.py::test_process_beacon_block_with_empty_proposal_transition

@protolambda using --bls-type=milagro doesn't make the CI too slow with minimal config (it takes ~3 to 5 minutes to run the tests). I'd say let's enable it.

To reviewers: #1990 fixes the CI.

looks fine, pending #1990


Use tab to navigate

project requirement

When logging out button doesn't work with tab and enter
Unable to hover over poll in poll list with tab.


輸出狀況改變

Coverage decreased (-0.1%) to 46.986% when pulling c1b2f1308209379f09685279188cc03c28ed2c2b on 輸出狀況改變 into afdb60a1ffcd71a3a5f8e9f084af3da7d7716830 on master.


Mock should also track named arguments

This issue was originally filed by<EMAIL_ADDRESS>
Currently, the mock package can only manage calls to methods that use positional parameters. It would be great if we could use the mock package with named parameters as well.
Maybe this is related: https://code.google.com/p/dart/issues/detail?id=14725

This issue has been moved to dart-lang/mock#8.


[Request] add sql-migrate

Hi, I'm using sql-migrate and it would be nice to have it in Nix:
https://github.com/rubenv/sql-migrate

There's a few ways you can package sql-migrate to work with devbox. Not all require nix, but they all require a bit of work outside of devbox:

You could package it with a flake (See https://github.com/F1bonacc1/process-compose for an example). This allows devbox to install it using a flake reference (e.g. github:F1bonacc1/process-compose")
If sql-migrate publishes released binaries you can use runx (see https://github.com/jetpack-io/devbox/blob/main/devbox.json#L6-L7 for example)
You could add it to nixpkgs (https://github.com/nixos/nixpkgs) and devbox search would pick it up (roughly a day after it gets merged).

An alternative would be to modify devbox to be able to build go projects independent of nix, but we currently don't support this. I can look into what that would entail, but the approaches above are likelier to be much faster routes.

Hi, thanks for the quick response!
I will look into your options, I'm relatively new to devbox and currently figuring it out, to eventually (if it fits our needs) introduce it to my team


"Bugeac", "Esechioi" are listed in the drop-down menu

Description:
When user writes "Bugeac", "Esechioi" the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Bugeac"

Expected results
The location appears in the drop-down menu as "Sat Bugeac, CONSTANȚA, (Ostrov)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Esechioi"

Expected results
The location appears in the drop-down menu as "Sat Esechioi, CONSTANȚA, (Ostrov)"


frontend: increases contrast of text on login/register pages

Fixes #4883.
I believe I covered all of the text covered in the issue description. I went for AAA-compliance except for the .split-view .left-side .description a in portico-signin.css, as the AAA version would make it hard for them to be differentiated from normal text.

Automated message from Dropbox CLA bot
@vaidap, it looks like you've already signed the Dropbox CLA. Thanks!

CAn you post screenshots so people can do quick design review before checking out the PR?

of course!
i got the last one by emulating my changes through the inspector tools of https://chat.zulip.org/accounts/login/ -- couldn't find a way to get to that page through the dev environment.

@brockwhittaker can you give this another review?

updated with hsl colour assignments.

I don't really like the color of the site url being dark grey but not the same color as above. That one is one of the AAA-compliant pieces, right? Could we perhaps dip back to AA and make it lighter grey? Otherwise the rest feels fine.

in order to AA-comply it has to be hsl(0,0%,46%) -- it's a bit lighter.

We could just go ahead and merge this @timabbott.

Merged, thanks @vaidap!


Definition files not found with Visual Studio 2015 and Typescript 2.0

TypeScript Version: 2.0
Visual Studio 2015 is complaining about definitions not found (because they are in a root folder).
But in my tsconfig.json file, I'm referencing explicitly the parent typings folder (possible using wildcards since Typescript 2.0).
The compilation works on command line, which means definitions files are resolved correctly, but Visual Studio Intellisense stills complain about them.
Will this problem be solved soon ?
Thanks

Thanks for the report.
A few points to help us investigate this:

Which version of NTVS  and VS are you on? It may be helpful if you could just go to Help -> About Microsoft Visual Studio and use Copy Info to provide a list of all installed extensions and their versions.
What is the specific error? Can you please provide the text of the message.
Can you please provide a sample tsconfig.json file, plus an example, simple directory layout to show where the typings are. This will help us setup a repo.

Thanks.

Hello,
Versions are  :

Microsoft Visual Studio Professional 2015
Version 14.0.25425.01 Update 3
Installed Version: Professional
Node.js Tools   1.2.40627.01
Adds support for developing and debugging Node.js apps in Visual Studio
Node.js Tools - Profiling   1.2.40627.01
Profiling support for Node.js projects.
TypeScript   <IP_ADDRESS>
TypeScript tools for Visual Studio

The errors are the same everywhere in Visual Studio only (compilation oustide Visual Studio works !)

cannot find module 'xxx'

where 'xxx' is a module that has a declaration file which is NOT located in subfolder of the one containing the tsconfig.json file.
But in tsconfig, these declarations are specifically referenced in "includes" directive.
"include": [
        "**/*.ts",
        "../../typings/**/*.ts",

I'm preparing a sample demo for you.
Thanks

Here is a sample demo, which produce the error on my Visual Studio version.
demo

@djflex68 The example does not work in VS or outside of it. I had to make these basic edits:

"target": "ES5" -> "target": "ES6"
import { _ } from "lodash"; -> import _ from "lodash";
Include server and some additional files that were not in the solution but on the file system.

But then everything compiled fine in VS, including the resolution of the typings modules. I was unable to repo the problem with this setup. Can you please attach an updated demo. Also, what commands are you using outside of VS to compile?
Thanks.

Hello,
I'm sorry, I think I gave you a wrong url. I made the same edits than yours but this is still not working in Visual Studio.
Here you can find the updated demo
The command I'm using outside VS is simply "tsc" in www or server folder.
In the zip file, I've attached a screen capture with the error I'm getting.
Thanks

@djflex68 Can you share your demo on dropbox, or onedrive...

This should work with @types. http://www.typescriptlang.org/docs/handbook/declaration-files/consumption.html


add support for npm / yarn

there is no tooling to compile javascript in themes?

No, there is no reason to include it.

run it locally (add a make command). Usually the best Option, if your system has node and yarn/npm. Local cache for npm or yarn.
Add a container to a project that needs it


Accept commas in default copyright pattern

Summary

Adds commas as an accepted separator between copyright years by default, which is actually documented in one spot, but not currently accurate. Fixes #9477.
Test Plan

Just trying to add tests for this... It seems like Copyright (c) 2018, 2019 Developers is actually accepted on main? See: https://play.ruff.rs/5c5932af-5fef-4990-bcc5-c854c0b46255

It seems like the current regex could be described as "Must contain Copyright\s+(\(C\)\s+)?\d{4}, followed by anything". So Copyright (c) 2018, 2019 Developers would match as "Copyright (c) 2018, followed by anything".

It seems like the current regex could be described as "Must contain Copyright\s+(\(C\)\s+)?\d{4}, followed by anything". So Copyright (c) 2018, 2019 Developers would match as "Copyright (c) 2018, followed by anything".

Nit: you probably want [0-9] instead of \d. Or, equivalently, (?-u:\d). See: https://docs.rs/regex/latest/regex/#example-validating-a-particular-date-format

Closing for now, but happy to revisit if we get more info.


ATs - not all are running in GHA

I think there is something wrong with the AT test splitter script - if I'm reading this right -
I'm getting failures from this AT ExecutionEngineShanghaiAcceptanceTest running locally on main, and I can't see any evidence that this test is running in GHA - but actually no tests matching Execution* are running. And going by count of occurrence of --tests on eg this page (even when I expand all the sections), there's only 25 AT classes being picked up. When I run acceptanceTestNotPrivacy locally I get a report with 59 class files.

maybe it's parameterized tests that are missing? eg BftBlockRewardPaymentAcceptanceTest and friends also missing
currentTests.txt

Related to this https://github.com/hyperledger/besu/pull/7317, we need to add a dummy @Test to be sure they are selected, at least until https://github.com/gradle/gradle/issues/29895 is fixed


Error obtaining certificate: Time limit exceeded.

I'm testing this cool stack, didnt work...
Any ideas ?
2017-6-1 16:30:59level=info msg="Using Let's Encrypt Production API"
2017-6-1 16:30:59level=info msg="Trying to obtain SSL certificate (odoo.bewave.io,unifi.bewave.io) from Let's Encrypt Production CA"
2017-6-1 16:35:56level=error msg="[odoo.bewave.io] Error obtaining certificate: Time limit exceeded. Last error: NS aws-8fc0eba3b9.bewave.io. returned NXDOMAIN for _acme-challenge.odoo.bewave.io."
2017-6-1 16:35:56level=error msg="[unifi.bewave.io] Error obtaining certificate: Time limit exceeded. Last error: NS aws-8fc0eba3b9.bewave.io. returned NXDOMAIN for _acme-challenge.unifi.bewave.io."

Oh never mind, that name server doesn't see the new domains... Within AWS it sees our Simple AD Server... I'll find a way around.


Change Providers/Models order in Ask menu

Fixes #641
This PR moves the Providers list above the Models list in the Ask menu.
Additionally, I changed the selection icon to a checkmark for better clarity. I aligned the menu to its button and changed the variant of the search bar.

I love how clean this looks @menghif!
Question: can we do something about how the overflow gets applied, so it stays limited to the models vs. the entire menu.  On providers with a lot of models, you lose track easily:
https://github.com/tarasglek/chatcraft.org/assets/427398/15476be0-0cc1-48c1-bbbc-693736cc2e17
If that's too complicated, we can leave that for a follow-up.

@humphd Yesterday I tried changing the overflow to only the Models list but I wasn't sure how it would behave with a long list of providers. I only tested it with up to 3.

This works well for me (sorry for lower video quality, had to reduce it to fit in 10M):
https://github.com/tarasglek/chatcraft.org/assets/427398/d44c79c7-60cd-48de-98ab-cc8c480ea075
I'd say "ship it."
Anyone else have feedback before we merge?

One last thing I noticed from your video is that I messed up the Menu placement. It should be top-end. Fixed it now!

this a nice improvement

This is a bit weird in mobile as we now cover up search results by keyboard on ios :(

This is a bit weird in mobile as we now cover up search results by keyboard on ios :(

I'll look into how to fix it.


tl.make_block_ptr silently incorrect with sizes above 2**31

Repro
import triton
import triton.language as tl
import torch

@triton.jit
def triton_(in_ptr0, out_ptr0, XBLOCK : tl.constexpr):
    xnumel =<PHONE_NUMBER>
    xoffset = tl.program_id(0).to(tl.int64) * XBLOCK
    xindex = xoffset + tl.arange(0, XBLOCK)[:].to(tl.int64)
    xmask = xindex < xnumel
    tmp0 = tl.load(tl.make_block_ptr(in_ptr0, shape=[2147483649], strides=[1], block_shape=[XBLOCK], order=[0], offsets=[xoffset]), boundary_check=[0])
    tmp1 = tl.full([1], 1, tl.int8)
    tmp2 = tmp0 + tmp1
    tl.store(tl.make_block_ptr(out_ptr0, shape=[2147483649], strides=[1], block_shape=[XBLOCK], order=[0], offsets=[xoffset]), tmp2, boundary_check=[0])

x=torch.zeros(2147483649, dtype=torch.int8, device="cuda")
y=torch.zeros(2147483649, dtype=torch.int8, device="cuda")

triton_[(triton.cdiv(2147483649, 1024),)](x, y, 1024)
del x

torch.testing.assert_close(y, torch.ones_like(y))

Fails because:
actual=tensor([1, 1, 1,  ..., 1, 1, 0], device='cuda:0', dtype=torch.int8),
expected=tensor([1, 1, 1,  ..., 1, 1, 1], device='cuda:0', dtype=torch.int8),

@LyricZhao @goostavz Can you please remind us why offsets have to be i32? I can confirm that it is the root cause of this bug

https://github.com/openai/triton/blob/main/python/triton/language/semantic.py#L1552

Maybe it's because tensor coordinates are 32 bits, but I think it's only a restriction when lowering to sm90. If we choose to lower make_tensor_ptr to other architectures, 64 bits coordinates should be allowed.

The vector operand tensorCoords specifies the starting coordinates in the tensor data in the global memory from or to which the copy operation has to be performed. The number of tensor coordinates in the vector argument tensorCoords should be equal to the dimension specified by the modifier .dim. The individual tensor coordinates in tensorCoords are of type .s32.

Rather than producing incorrect code, it would be a lot better to throw an error message like: "make_block_ptr only supports 32 bit indexing, add a .to(tl.int32) or use regular indexing for 64 bit support"

Maybe it's because tensor coordinates are 32 bits, but I think it's only a restriction when lowering to sm90.
Yes, I remember it is only a restriction for sm90. For other architectures, I think the behavior better to be consistent currently and a temporary fix would be enough. With #2842, it fixes the implicit cast from i64 to i32 of offsets and asserts that it must be i32.

Now shape/strides are i64, while offsets/block_shape are i32. So #2821 would raise a compiler error, and #2826 should work.


Automated Package Upgrade

:tada: This PR is included in version 26.0.79 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to use on layer2 arb network?

How to use on layer2 arb network?

it just works, you can simply use an RPC for arb.


feat!: Make OutOfGasError a VirtualMachineError

What I did
fixes: Ape-369

fixes: APE-369
change the base class of outofgas to virtualmachineError
How I did it

How to verify it

Checklist

[x] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

APE-369

does this need tests?

don't think it needs anything additional, more a UX thing

does this need tests?

It is tested by the fact that we should now be able to remove this type ignore: https://github.com/ApeWorX/ape-hardhat/blob/main/ape_hardhat/provider.py#L483


Upgrade to Gradle8

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 92.491% (-6.5%) from 98.999% when pulling 0ae7e091af54b60b85a07f2532ca3924ff0d30d4 on gradle8 into 0b8db51016b755bb171bb87f867c026cf3353b53 on main.


DOC: Add missing word

I believe the sentence should read "MATLAB-like creation syntax via the semicolon", as in the numpy example a = np.matrix('1 2; 3 4').
I also re-wrapped the paragraph.  In hindsight that probably should've been a separate commit.  I will change and resubmit if desired.

Sorry about that.  I should have looked around more before submitting.  I will be less hasty in the future.

The rendered doc improvements from these changes look sensible so I'll just merge this minor improvement in as-is. np.matrix may eventually be removed, but for now this remains ok for a doc improvement.


⚠ SceneTime has degraded performance

In 31354c3, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3297 ms

Resolved: SceneTime performance has improved in 21d6bc0 after 7 minutes.


[packagers] Support Zip based distributions with Winget

Follow up to https://github.com/jreleaser/jreleaser/issues/185
Affects the following distributions:

BINARY
JAVA_BINARY
JLINK

Sample package with Zip https://github.com/microsoft/winget-pkgs/pull/99033/files

🎉 This issue has been resolved in v1.6.0 (Release Notes)


Release Candidate Comments (Sponsorship)

This issue was created to collect comments about the upcoming metrics release.
This thread is for comments about Sponsorship
GitHub location: https://github.com/chaoss/wg-diversity-inclusion/blob/master/focus-areas/leadership/sponsorship.md
See all release candidates of metrics are at:
https://chaoss.community/metrics-202001/

Remove Focus Area prior to metric name -- this is consistent with the layout of the other release candidate metrics.

"Resources" should be "References"


[Bug] installation problems

after installing this integration using HACS, nothing really happens.
I can't find any config page, nor do i see any sensors
I've uninstalled and reinstalled, without success.
The image below shows all i can see

Have you rebooted HA?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: ametodi @.>
Sent: Thursday, May 19, 2022 7:05:19 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Assign @.>
Subject: [jeroenterheerdt/HAsmartirrigation] [Bug] installation problems (Issue #93)
after installing this integration using HACS, nothing really happens.
I can't find any config page, nor do i see any sensors
I've uninstalled and reinstalled, without success.
The image below shows all i can see
[image]https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41694393%2F169312504-ee551967-4811-4061-aa75-74d5434bbf29.png&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=AmFWoM8RxjCIZvbVou4eTRypKD12Z38K00H3W95Qfv0%3D&reserved=0
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F93&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=J2SioITpoeKEoaREMBvmdT2llowecDPEX5YdwB7UFIg%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPUEJSWRUAIJB6EM3RTVKZDB7ANCNFSM5WMLGI6Q&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=vBMdx%2F0tzG11uzuO1EYyoHiYTQ8%2FD9kEkLSyOFTwq9I%3D&reserved=0.
You are receiving this because you were assigned.Message ID: @.***>

Hi Jeroen, yes i have several times
Op do 19 mei 2022 16:45 schreef Jeroen ter Heerdt @.***

:

Have you rebooted HA?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: ametodi @.>
Sent: Thursday, May 19, 2022 7:05:19 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Assign @.>
Subject: [jeroenterheerdt/HAsmartirrigation] [Bug] installation problems
(Issue #93)
after installing this integration using HACS, nothing really happens.
I can't find any config page, nor do i see any sensors
I've uninstalled and reinstalled, without success.
The image below shows all i can see
[image]<
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41694393%2F169312504-ee551967-4811-4061-aa75-74d5434bbf29.png&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=AmFWoM8RxjCIZvbVou4eTRypKD12Z38K00H3W95Qfv0%3D&reserved=0

—
Reply to this email directly, view it on GitHub<
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F93&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=J2SioITpoeKEoaREMBvmdT2llowecDPEX5YdwB7UFIg%3D&reserved=0>,
or unsubscribe<
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPUEJSWRUAIJB6EM3RTVKZDB7ANCNFSM5WMLGI6Q&data=05|01||846e04c23e014567d96008da39a09bdb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637885659210452607|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=vBMdx%2F0tzG11uzuO1EYyoHiYTQ8%2FD9kEkLSyOFTwq9I%3D&reserved=0

.
You are receiving this because you were assigned.Message ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/jeroenterheerdt/HAsmartirrigation/issues/93#issuecomment-1131811796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ6DJOJBEIGHQ5ODYEL3MXDVKZHXXANCNFSM5WMLGI6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks, this helped (sorry i missed it).
Now i was asked to enter the ETA's per month, the amount of sprinklers and throughput.
I did this for one zone (not sure if i should have done it for all zones??)
but i don't see any other configuration options, like adding zones and nozzles, etc...
the result of my actions now i that i have these three entities

Thank you so much for you help, i've now managed to set-up the zones and created a test automation.
The documentation tells that it's possible to have this running in multiple modes, of which a mixed mode.
I have entered the open weather API key, but i also have a POPP rain meter, which i'd like to add. Any idea how i can do this?
I didn't find n option to choose these modes

I've found that there's a checkbox when you try to add the instance.
When you uncheck it asks you for the sensors.
It does not say anything about modes, but i assume that it affects it?
I've entered my sensors, but how do i know in which mode it runs?

It's simple really: if you uncheck this checkbox you need to specify a sensor for ET, so you bypass the entire calculation in the component. That's one mode.
If you use any sensors but leave this checkbox checked you are in the other mode (sensor mode)
If you specified a OWM API key you are in the OWM mode.
Verzonden vanuit Outlookhttp://aka.ms/weboutlook
From: ametodi @.>
Sent: Monday, May 23, 2022 6:14 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Assign @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] installation problems (Issue #93)
I've found that there's a checkbox when you try to add the instance.
When you uncheck it asks you for the sensors.
It does not say anything about modes, but i assume that it affects it?
I've entered my sensors, but how do i know in which mode it runs?
[image]https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41694393%2F169827258-923b8ceb-045d-425e-ab39-9b76f8bdd6c3.png&data=05|01||e2b446eda22342c4f93208da3cbe2ac3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637889084709492271|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2FZ0oCzSKEdNTQBjA6pSquT%2F277vQkSytZbHzuahHEcU%3D&reserved=0

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F93%23issuecomment-1134664126&data=05|01||e2b446eda22342c4f93208da3cbe2ac3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637889084709492271|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ncz6Hwv5IXEev9gNNuhabIAUkab1HjTbBVlqUkFte04%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPTF3NXSZZG66IKCXPTVLOADJANCNFSM5WMLGI6Q&data=05|01||e2b446eda22342c4f93208da3cbe2ac3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637889084709492271|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=cuHcbTGJAaarUS%2FT%2BJEW5QCBMQ4wG8kmqfOBoMPZDn4%3D&reserved=0.
You are receiving this because you were assigned.Message ID<EMAIL_ADDRESS>

Hi Jeroen,
The system only asks for sensors when i uncheck the checkbox.
I'm trying to get a mixed mode, but i can't figure out how.

you mentioned in your manual that there were 5 modes. I'm trying to get it into the mixed mode
quoting you: "Mixed. A combination of 1) and 2). In this mode part of the data is supplied by sensors and part by Open Weather Map".
How can i do this?

Provide the API key and then also provide some sensors. What sensors you don't provide will be loaded from OWM.
Verzonden vanuit Outlookhttp://aka.ms/weboutlook
From: ametodi @.>
Sent: Friday, May 27, 2022 7:49 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Assign @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] installation problems (Issue #93)
you mentioned in your manual that there were 5 modes. I'm trying to get it into the mixed mode
quoting you: "Mixed. A combination of 1) and 2). In this mode part of the data is supplied by sensors and part by Open Weather Map".
How can i do this?

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F93%23issuecomment-1139690547&data=05|01||a1b9e216e6fb4956d15908da3feffcbc|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637892597219502072|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=WUykQXCxu2Ihzvb1uJbQvqLfUaTwq1xUTY7iGXcyK8c%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPTIWLHS4PQY5STVMRDVMDOEPANCNFSM5WMLGI6Q&data=05|01||a1b9e216e6fb4956d15908da3feffcbc|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637892597219502072|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9CMdYjK6bwoKHMAzUIHK4CuL0ZaAHmP9dcS%2B2yd7obI%3D&reserved=0.
You are receiving this because you were assigned.Message ID<EMAIL_ADDRESS>

Hello Jeroen, thank you for your help.
I think i've managed to set everything in YAML.
I've set a daily schedule to irrigate all zones and empty the daily buckets.
What i found strange is that the daily adjusted runtimes are even being filled when it rained or when rain was predicted.
Is there something particular i need to pay attention to?

ps. here's an example of one of the zones:
 "entry_id": "ae4944cf9644d656b6c0d32ec8662f95",                 "version": 1,                 "domain": "smart_irrigation",                 "title": "Gazon Oost",                 "data": {                     "number_of_sprinklers": 5.0,                     "flow": 6.6,                     "area": 100.0,                     "api_key": "90010a2ebd7fb441169021eeb01290f8",                     "reference_evapotranspiration": [                         4.1,                         7.6,                         19.6,                         37.6,                         53.0,                         63.7,                         63.6,                         49.6,                         30.7,                         16.1,                         6.0,                         2.9                     ],                     "name": "Smart Irrigation Gazon Oost",                     "sources": {                         "use_owm_precipitation": false,                         "use_owm_temperature": false,                         "use_owm_min_temperature": false,                         "use_owm_max_temperature": false,                         "use_owm_dewpoint": true,                         "use_owm_pressure": true,                         "use_owm_humidity": true,                         "use_owm_windspeed": true,                         "calculate_solar_radiation": true,                         "calculate_ET_value": true                     },                     "sensors": {                         "sensor_et": "sensor.pir_achtertuin_air_temperature_3",                         "sensor_precipitation": "sensor.popp_rain_sensor_general_purpose"                     }                 },                 "options": {},                 "pref_disable_new_entities": false,                 "pref_disable_polling": false,                 "source": "user",                 "unique_id": "Smart Irrigation Gazon Oost",                 "disabled_by": null             }

please don't share your API key :), even if rain is expected, things like wind, temperature, sun intensity could push the component to still want to irrigate. Imagine that all these things remove 10 units of moisture and rain adds 5, then we are still missing 5 so we need to irrigate.

We had some heavy rain a few weeks ago. The next morning the irrigation anyway ran for quite a while and that same day it was again going to rain all day

if you want to, you can monitor the attributes of the component over the day. I notice you are using OWM so that is not very accurate. My guess is that it rained but that OWM did not indicate as such and therefore the component ran. Only way to tell is to monitor the attributes like rain, windspeed, temp, etc from OWM and do the math yourself.

No trying to be snarky, but why don't you read the Readme before asking these questions? Everything is detailed there.
Verzonden vanuit Outlookhttp://aka.ms/weboutlook
From: Adrien Bonnat @.>
Sent: Friday, May 20, 2022 1:41 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Assign @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] installation problems (Issue #93)
You need to add the integration for each zone, the name field in the config flow is used in the entity name, make it unique to easily recognize who is who.

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F93%23issuecomment-1132639324&data=05|01||8c31a64920aa4b15e19008da3a3c69b1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637886328379752788|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=npk2u4AoWMJodGBQQt8H5qDRILDSXt32Nv9THvyBSYc%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPQES5AOTX55SIACOMLVK5FYJANCNFSM5WMLGI6Q&data=05|01||8c31a64920aa4b15e19008da3a3c69b1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637886328379752788|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2BHfgg3PQD2hIPDKyzhWRGZImcs7XHzY6r7vffRuHC%2Bs%3D&reserved=0.
You are receiving this because you were assigned.Message ID<EMAIL_ADDRESS>


autoComplete is Boolean but should be String on input

So it can accept beautiful valid strings like: "false". 😁

Is this true of all autoComplete attributes or just input (or even specific input types)?

I don't understand why you want to pass a Boolean as a string. It really is a Boolean, right?

Apparently it is not a Boolean, it's a space-separated list of the values described here: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete

To be quite honest, I just used this attribute and react complained. When I unsafeCoerced "false" it took it. I'd go with what @hdgarrood says.

I don't think a type like data AutofillDetailToken = On | Off | Name etc. is desirable, because adding a new constructor to an existing data type is always a breaking change. I would recommend something like
newtype AutofillDetail = AutofillDetail String

on :: AutofillDetail
on = AutofillDetail "on"

off :: AutofillDetail
off = AutofillDetail "off"

name :: AutofillDetail
name = AutofillDetail "name"

[...]

and also exporting the constructor so that people can add their own ones if necessary, eg if the list of values expands. Alternatively I think just using String would be justifiable here too.

String seems fine to me since the rest of the dom library just uses primitives (or zero typing, in the case of css). There could be an alternative dom library which types all the fields and styles more strictly, or more often a much smaller subset like a component library.

It's probably a bigger issue that we currently have the autoComplete prop on every element 😅

It's probably a bigger issue that we currently have the autoComplete prop on every element

@spicydonuts There's an easy solution to that, in codegen/react-html-attributes.json simply move autoComplete from * to all the places it should appear, one of them being input.  I don't have the complete list to hand, or I would do a quick PR.

:) https://github.com/lumihq/purescript-react-basic/pull/120

Looks like it's input, textarea, select, and form. I'll add it to the PR above.


Adds compiler-base minimal images for use by go/node/python/java images

Issue #, if available:
Description of changes:
Adds a new base image for future compiler base images. The idea is to have 3 variants, base, yum and gcc.  For the bulk of our usages of golang we could use the base image which has the real bare minimal utils in it.  In the one case we use cgo, having a variant gcc + yum will be helpful.  I also made yum its own variant since adding gcc adds a lot and based on other examples out there I feel being able to install additional utils/libs could be important during certain build situations.
Once we add the language specific images we would have 3 images for every language version, ie golang-1.18 golang-1.18-yum golang-1.18-gcc
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


docker networking with default gateway issue

the command is not working if a network with a default gateway is used. for my build of other containers i fixed this by adding "--network host" on the build command. Is there any way to tell d2vm to add "--network host" to the build command ?
the issue i get is "W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease  Connection timed out [IP: <IP_ADDRESS> 80]" im using the container to build it. it's wokring on my local system but not on my cloud build server, since the build server has only an internal network and adds a route default route/gateway for internet downloads.
basically i should be able to solve it by adding "--network host" to the build command, is there any way give additional parameters for the used build command ?

Hello @mahald !
No, I'm sorry.


Fix log_struct usage

Currently kwargs are not supported, though adding them would probably be a good feature.

@waprin As an alternative to this, you could take all of the logging snippets and put them in docs/logging_snippets.py (though that's a bigger project)

Interesting, I'll take a look at that, seems like a great idea. For now we should prob fix what we have though.

@waprin, @dhermes FWIW I have a logging_snippets branch locally where I have started that process.

@tseaver Great news!


Docker parameters in UI

Would like to open this issue regarding the lack of UI on the tasks side.
It'd be great if Singularity could allow a "write" access by adding the the API resources in the new request UI bits:

Using Singularity 0.4.9, it's really limited (even more than in v0.4.5).
Maybe keep the current UI but allow an attribute to be specified in the YAML to allow adding tasks parameters like Marathon:

Thoughts ?

@scalp42 most of what you are looking for is on the new deploy page. On the page for the request you just created, click on deploy and you will get a set of fields very similar to that. The request holds over-arching information for all deploys (number of instances, type of request, etc), while the individual deploy has information about the resources, docker image, ports, ...

@ssalinas found it, but it's still more or less the same as in you can't pass a command for example to override the container one (you have to rely on the container one).

fixed by #962


Naming convensins

It seem your naming conventions and abbreviations does not give a good experience IMO. Long naming might be better in some cases.
Like;
Image image = imread("/path/to/image.png"); // read an image from filesystem.

auto slice = image.sliced; // slice image data (calls std.experimental.ndslice.slice.sliced on image data)

slice
    .asType!float[0..$, 0..$, 1] // convert slice data to float, and take the green channel only.
    .conv!symmetric(sobel!float(GradientDirection.DIR_X)) // convolve image with horizontal Sobel kernel.
    .byElement
    .ranged(0, 255).array.sliced(slice.shape[0..2]) // scale values to fit the range between the 0 and 255
    .imshow("Sobel derivatives"); // preview changes on screen.

waitKey();

some thing like readImage(), showImage().
You tend to mix them, like there is byElement() which is not consistent with imread(), imshow() etc.

imread/imshow/imwrite are function names already widely used for that purpose throughout most popular computer vision toolkits. Even if this naming is not consistent with the convention used by D community (and this library for that matter), I left those names so people who are familiar with any of those popular toolkits would easily find their way around, without consulting the API reference. And of course, since those names are used so much, I believe it would annoy people to name them otherwise.
So, those are exceptions purposefully named that way. Sorry, but I'd really like to keep it as is.

:ok:


[behavior_server-50] [INFO] [1696977463.430187368] [behavior_server]: Activating spin
[behavior_server-50] [INFO] [1696977463.430218823] [behavior_server]: Activating backup
[behavior_server-50] [INFO] [1696977463.430241172] [behavior_server]: Activating drive_on_heading
[behavior_server-50] [INFO] [1696977463.430265285] [behavior_server]: Activating assisted_teleop
[behavior_server-50] [INFO] [1696977463.430286222] [behavior_server]: Activating wait
[behavior_server-50] [INFO] [1696977463.430324596] [behavior_server]: Creating bond (behavior_server) to lifecycle manager.
[lifecycle_manager-54] [INFO] [1696977463.549759051] [lifecycle_manager_navigation]: Server behavior_server connected with bond.
[lifecycle_manager-54] [INFO] [1696977463.549848622] [lifecycle_manager_navigation]: Activating bt_navigator
[bt_navigator-51] [INFO] [1696977463.551281823] [bt_navigator]: Activating
[bt_navigator-51] [INFO] [1696977463.686763274] [bt_navigator]: Creating bond (bt_navigator) to lifecycle manager.
[lifecycle_manager-54] [INFO] [1696977463.793108047] [lifecycle_manager_navigation]: Server bt_navigator connected with bond.
[lifecycle_manager-54] [INFO] [1696977463.793163675] [lifecycle_manager_navigation]: Activating waypoint_follower
[waypoint_follower-52] [INFO] [1696977463.793704658] [waypoint_follower]: Activating
[waypoint_follower-52] [INFO] [1696977463.793750029] [waypoint_follower]: Creating bond (waypoint_follower) to lifecycle manager.
[lifecycle_manager-54] [INFO] [1696977463.910225275] [lifecycle_manager_navigation]: Server waypoint_follower connected with bond.
[lifecycle_manager-54] [INFO] [1696977463.910377981] [lifecycle_manager_navigation]: Activating velocity_smoother
[velocity_smoother-53] [INFO] [1696977463.911395516] [velocity_smoother]: Activating
[velocity_smoother-53] [INFO] [1696977463.911624103] [velocity_smoother]: Creating bond (velocity_smoother) to lifecycle manager.
[controller_server-47] [INFO] [1696977463.970581630] [local_costmap.local_costmap]: StaticLayer: Resizing static layer to 0 X 0 at 0.050000 m/pix
[lifecycle_manager-54] [INFO] [1696977464.039675154] [lifecycle_manager_navigation]: Server velocity_smoother connected with bond.
[lifecycle_manager-54] [INFO] [1696977464.039724629] [lifecycle_manager_navigation]: Managed nodes are active
[lifecycle_manager-54] [INFO] [1696977464.039742339] [lifecycle_manager_navigation]: Creating bond timer...
[planner_server-49] [WARN] [1696977464.302509575] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [INFO] [1696977464.302571405] [global_costmap.global_costmap]: StaticLayer: Resizing costmap to 0 X 0 at 0.050000 m/pix
[planner_server-49] [WARN] [1696977465.302486014] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977466.302495791] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977467.302557581] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977468.302564227] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977469.302472040] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977470.302638812] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977471.302580186] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977472.302466250] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977473.302586259] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977474.302517659] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977475.302483278] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977476.302564769] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977477.302523442] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977478.302491723] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977479.302543504] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977480.302575995] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977481.302505321] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977482.302498915] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977483.302507857] [nav2_costmap_2d]: Robot is out of bounds of the costmap!
[planner_server-49] [WARN] [1696977484.302557076] [nav2_costmap_2d]: Robot is out of bounds of the costmap!

I have the same problem. Were you able to visualize anything in rviz without running nav2?

Can you both start off by making sure that you are running the latest of all of the turtlebot packages? (sudo apt update and sudo apt upgrade)
The command that you shared works as intended on my system. How do you have your system set up in terms of networking. Do you happen to still have it set up for discovery server from working with a physical robot? This can interfere with simulations.

I was able to fix the issue with the robot being out of bounds. It turns out that when I visualized the lidar rays, they were not behaving normally, aka they only extended to the perimeter of the robot. (I'm not really sure why that is) but I managed to fix that after changing the render engine as was mentioned in #20 from ogre to ogre2

@HyydenJakcz Can you clarify, are you using hardware acceleration (GPU) to run the simulation?
Same question for you @yeetus-skeetus.

I am not sure how to check if I am using hardware acceleration. And for your second question, yes I just changed the one line

@yeetus-skeetus yes start there. Personally I have two separate lines in my bashrc and I comment/uncomment them based on whether I am running simulation/simple discovery or discovery server.
@HyydenJakcz if you don't have a GPU, I wonder if this issue you had is related to that. The lidar rays sometimes seem to misbehave when not run on a gpu. I will look into that setting. Thank you for getting back to me.

I also have the same two lines that I comment/uncomment out of my bashrc when networking with the robot so I don't think that's the issue.

I've also commented out simple discovery from .bashrc, which has not changed anything.
I don't know for sure if Gazebo is being hardware accelerated, but the machine does have drivers for its Nvidia GeForce RTX 3060.

nvidia-smi doesn't list anything related to Gazebo while the system is running. I've tried reinstalling Gazebo and the simulator but the error remains the same. How should I proceed?

@yeetus-skeetus The easiest way to ensure that the simulation uses the GPU is to set your GPU to always be used. There are several guides online such as this one: https://www.linuxbabe.com/desktop-linux/switch-intel-nvidia-graphics-card-ubuntu

Step 4: Switch to Nvidia Graphics Card
Once rebooted, open Nvidia X Server Settings (nvidia-settings)

Click PRIME Profiles tab on the left pane, and then select Nvidia card on the right pane. If you don’t have PRIME Profiles, reboot your computer so PRIME can be enabled.

@yeetus-skeetus The easiest way to ensure that the simulation uses the GPU is to set your GPU to always be used. There are several guides online such as this one: https://www.linuxbabe.com/desktop-linux/switch-intel-nvidia-graphics-card-ubuntu

Step 4: Switch to Nvidia Graphics Card

Once rebooted, open Nvidia X Server Settings (nvidia-settings)

Click PRIME Profiles tab on the left pane, and then select Nvidia card on the right pane. If you don’t have PRIME Profiles, reboot your computer so PRIME can be enabled.

Thank you! This appears to have fixed the issue. I went under PRIME in nvidia-settings and set it to Performance Mode.