build: Incorrect python interpreter found by python.cmake on Nix

Describe the bug
TL;DR: CMake's FindPython module has 3kloc to handle many edge cases, and carefully does things with find_program that we are not doing. I happened to find an edge case seemingly.
I'd expect python.cmake to choose the first python in my path, it instead seems to choose somewhat at random a python interpreter on my path.
find_package(Python COMPONENT INTERPRETER) seems to do this just fine, the current find_program() usage does not.
I've added some message() outputs in python.cmake and west.cmake to try and provide some clues, diff attached
output from this...
(env) tburdick@zefire ~/z/z/doc (main)> make html-fast
make html DT_TURBO_MODE=1
make[1]: Entering directory '/home/tburdick/z/zephyr/doc'
cmake \
	-GNinja \
	-B_build \
	-S. \
	-DDOC_TAG=development \
	-DSPHINXOPTS="-j auto -W --keep-going -T" \
	-DSPHINXOPTS_EXTRA="" \
	-DLATEXMKOPTS="-halt-on-error -no-shell-escape" \
	-DDT_TURBO_MODE=1
Loading Zephyr module(s) (Zephyr base): doc
Python currently ,
python found /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python
python found /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python version 3.10
python3 found /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python
python3 found /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python version 3.10
Calling find_package Python3, /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python
-- Found Python3: /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python (found suitable version "3.10.13", minimum required is "3.8") found components: Interpreter
Called find_package Python3, /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin/python
-- Cache files will be written to: /home/tburdick/.cache/zephyr
-- Zephyr base: /home/tburdick/z/zephyr
-- Found Doxygen: /nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6/bin/doxygen (found version "1.9.6") found components: doxygen dot
CMake Error at CMakeLists.txt:33 (message):
  The 'sphinx-build' command was not found

-- Configuring incomplete, errors occurred!
See also "/home/tburdick/z/zephyr/doc/_build/CMakeFiles/CMakeOutput.log".
make[1]: *** [Makefile:24: configure] Error 1
make[1]: Leaving directory '/home/tburdick/z/zephyr/doc'
make: *** [Makefile:18: html-fast] Error 2
(env) tburdick@zefire ~/z/z/doc (main) [2]> which python
/home/tburdick/z/env/bin/python
(env) tburdick@zefire ~/z/z/doc (main)> ls -alh /home/tburdick/z/env/bin/python
lrwxrwxrwx 1 tburdick users 74 Dec  1 13:03 /home/tburdick/z/env/bin/python -> /nix/store/c3cjxhn73xa5s8fm79w95d0879bijp04-python3-3.10.13/bin/python3.10
(env) tburdick@zefire ~/z/z/doc (main)> ls -alh /nix/store/c3cjxhn73xa5s8fm79w95d0879bijp04-python3-3.10.13/bin/python3.10
-r-xr-xr-x 1 root root 16K Dec 31  1969 /nix/store/c3cjxhn73xa5s8fm79w95d0879bijp04-python3-3.10.13/bin/python3.10

I'd note that which python points at my virtual environment, which itself holds a static link to a nix install of python with various python packages (nix will generate a virtualenv like wrapper itself), and that links to a real python interpreter. None of those are actually selected though. Instead it appears that, at perhaps random or some undefined ordering, another python in my PATH var is selected. That's seemingly, to me, the wrong behavior and very unexpected.
If I replace all of python.cmake with a simple find_package(Python COMPONENT INTERPRETER) as seen in #65995 the symlinked python in my virtualenv is found correctly.
Some other useful environment variables perhaps give some clues
nix will set PATH, CMAKE_, and other environment variables when being used to enable builds with its unique filesystem layout.
env | grep python3-3.10.13 shows... (sorry for the large text blob here)
XDG_DATA_DIRS=/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/share:/nix/store/n7nrikml13ipr3gishnbf2x0g3zbia16-minicom-2.8/share:/nix/store/04p9vxaplyd4a1m4q8qyh371dfmny3pl-ninja-1.11.1/share:/nix/store/sj207xd8h848inbwqpqz9lq89yii08sj-gperf-3.1/share:/nix/store/h8q4r7f1j906rlffj96dlbbmwc9zbirk-cmake-3.25.3/share:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/share:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/share:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/share:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/share:/nix/store/xbm2s7589mswrgngv8ci1zcqfh1l6v2w-xxd-vim-9.0.1441/share:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/share:/nix/store/gw2ql840xwh37fp7dv430mrxc1bgyxsz-lldb-16.0.6/share:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/share:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/share:/nix/store/b8gwvz4hiq9227321s3lqbk3c6pv22kz-llvm-16.0.6/share:/nix/store/k6ssc7alckmv6gbympghw365ribdlj31-rustup-1.26.0/share:/nix/store/gwf21xyl0x0bhgapi66avzf6qmddr44s-patchelf-0.15.0/share:/nix/store/1wbc95psbpyzlc8s20qpmbic1706dfhk-gnome-console-45.0/share:/nix/store/n1qj6nna92xldmqxdqfwj8b4naxiznaj-gsettings-desktop-schemas-45.0/share/gsettings-schemas/gsettings-desktop-schemas-45.0:/nix/store/k11r1l1q236cjim5piz6gp8xs1y7ir2k-gtk4-4.12.3/share/gsettings-schemas/gtk4-4.12.3:/nix/store/1wbc95psbpyzlc8s20qpmbic1706dfhk-gnome-console-45.0/share/gsettings-schemas/gnome-console-45.0:/nix/store/cv38v8k6nf1ng6cr9mjfqq1as3vnb43w-gnome-mimeapps/share:/nix/store/cib1rhpk4653hbf8hqwlw9hanf11yhig-desktops/share:/home/tburdick/.nix-profile/share:/nix/profile/share:/home/tburdick/.local/state/nix/profile/share:/etc/profiles/per-user/tburdick/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share:/nix/store/ja4xq4ra1w9j4g6cnvkkmmhjyh1qxpbh-gnome-shell-45.1/share/gsettings-schemas/gnome-shell-45.1:/nix/store/78yrfskcsbds6876kgwjdja2ws3d2p1d-gnome-shell-extensions-45.1/share/gsettings-schemas/gnome-shell-extensions-45.1:/nix/store/gl3sw9c9hkhkn5mqi7s2aj1y30fy8h2i-gnome-session-45.0/share:/nix/store/n1qj6nna92xldmqxdqfwj8b4naxiznaj-gsettings-desktop-schemas-45.0/share/gsettings-schemas/gsettings-desktop-schemas-45.0:/nix/store/1jkmjwd4d5c9x520kw2wzpw09bfcldcq-gtk+3-3.24.38/share/gsettings-schemas/gtk+3-3.24.38:/nix/store/bf6d3mj74kmffq97fliq4084fvcr5hq0-gnome-settings-daemon-45.0/share/gsettings-schemas/gnome-settings-daemon-45.0:/nix/store/gl3sw9c9hkhkn5mqi7s2aj1y30fy8h2i-gnome-session-45.0/share/gsettings-schemas/gnome-session-45.0:/nix/store/ja4xq4ra1w9j4g6cnvkkmmhjyh1qxpbh-gnome-shell-45.1/share
NIX_CFLAGS_COMPILE= -frandom-seed=nhccmaiznb -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include -isystem /nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include
_OLD_VIRTUAL_PATH=/nix/store/y033c1zj8h064wm8kbnpmfcf6w54cn3z-zephyr-sdk/bin:/nix/store/21096vzf5ljl6lhplmfd301kb8zyvj05-rimage/bin:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin:/nix/store/n7nrikml13ipr3gishnbf2x0g3zbia16-minicom-2.8/bin:/nix/store/04p9vxaplyd4a1m4q8qyh371dfmny3pl-ninja-1.11.1/bin:/nix/store/sj207xd8h848inbwqpqz9lq89yii08sj-gperf-3.1/bin:/nix/store/dp3ghxdzqfqpzkvmsay2026lhjn19lg7-ccache-4.8/bin:/nix/store/h8q4r7f1j906rlffj96dlbbmwc9zbirk-cmake-3.25.3/bin:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/bin:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/bin:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/bin:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/bin:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/bin:/nix/store/xbm2s7589mswrgngv8ci1zcqfh1l6v2w-xxd-vim-9.0.1441/bin:/nix/store/7rm5784szfma17yklz4dmds20ws8g5v9-nixpkgs-fmt-1.3.0/bin:/nix/store/xnklwbh91g7if2mzy5mh4zcsg818jfls-gcc-wrapper-12.2.0/bin:/nix/store/6504znvqq8hb7qaf5hnfxiccc0g3zmbb-gcc-12.2.0/bin:/nix/store/wskdac6dzswp59qrf8p213ld23l1p0bf-glibc-2.37-45-bin/bin:/nix/store/aifz5nf4xvl2m94ayap13ys48drkhmzk-coreutils-9.1/bin:/nix/store/39x21ag4yfahwjm24a3zrqyhp1rc5mvm-binutils-wrapper-2.40/bin:/nix/store/drdpyvbbp0vylmzmlra408fyj6zv22lq-binutils-2.40/bin:/nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6/bin:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/bin:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/bin:/nix/store/nnjs5w63rc54fg33myzmvx6qknymiksj-clang-tools-14.0.6/bin:/nix/store/gw2ql840xwh37fp7dv430mrxc1bgyxsz-lldb-16.0.6/bin:/nix/store/zfdj9lm7rqizrjj8lk9bkxq4djxkbjh7-clang-wrapper-16.0.6/bin:/nix/store/bmcs67kwf560sv434jaycqdpwg3vivw4-clang-16.0.6/bin:/nix/store/sb5sf8pnbb5dxgr5p8qm344ky8k7f62r-glibc-2.37-45-bin/bin:/nix/store/w8vm09hri2zz7yacryzzzxvsapik4ps4-coreutils-9.1/bin:/nix/store/88bh6zy2sbkj83jcpvmzgqf74213wk2f-binutils-wrapper-2.40/bin:/nix/store/3r87a2wq1w4l66wnsm7rqvy608mx23h6-binutils-2.40/bin:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/bin:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/bin:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/bin:/nix/store/b8gwvz4hiq9227321s3lqbk3c6pv22kz-llvm-16.0.6/bin:/nix/store/k6ssc7alckmv6gbympghw365ribdlj31-rustup-1.26.0/bin:/nix/store/gwf21xyl0x0bhgapi66avzf6qmddr44s-patchelf-0.15.0/bin:/nix/store/vaqs26d33rgz2acf81n35v809g8g27vh-clang-wrapper-11.1.0/bin:/nix/store/7wqhmdl4cd8yh7xi32c2ss7l6804i1p7-clang-11.1.0/bin:/nix/store/ximnbjgjqkmyp88hjz9bgsfdfy431ilp-binutils-wrapper-2.40/bin:/nix/store/hf6q72gb3nj3fbfh7j2a14vfjmsgbg25-compiler-rt-libc-16.0.6/bin:/nix/store/82fqlfr6d9s3yvhxp0zv0zswl5w12n19-compiler-rt-libc-11.1.0/bin:/nix/store/w8vm09hri2zz7yacryzzzxvsapik4ps4-coreutils-9.1/bin:/nix/store/4cxs4cigh2zdxvma52ygm3mh2igq70iw-findutils-4.9.0/bin:/nix/store/vikpb6rhmi8zzgsx8syjng9dic8dplm7-diffutils-3.9/bin:/nix/store/4mca20b13q88s6llkr8mc468rh9l9bmr-gnused-4.9/bin:/nix/store/b4in4hmq54h6l34a0v6ha40z97c0lzw2-gnugrep-3.7/bin:/nix/store/p7v8rc82yi4zngjw2z7isgqvfi32l1aj-gawk-5.2.1/bin:/nix/store/2gcfy5f68y7gkryp3wrjmvlci42qb61a-gnutar-1.35/bin:/nix/store/5xzh0z66hpcd3k578my76lx4qgra334q-gzip-1.12/bin:/nix/store/6d9vlwwy7kvxjqmqg4cldgg9mr8nflff-bzip2-1.0.8-bin/bin:/nix/store/qlcm8dzsaa6wyycmx7in8rz6x3pzf6zf-gnumake-4.4.1/bin:/nix/store/0rwyq0j954a7143p0wzd4rhycny8i967-bash-5.2-p15/bin:/nix/store/0g52i0ih3h0d9s40m84gksi2jjm4k3bf-patch-2.7.6/bin:/nix/store/agry2lhy6ilgyacx75w2ycqsdfwr513f-xz-5.4.3-bin/bin:/nix/store/rgg874xkzlfmkzkm7911dwnihswkf54g-file-5.44/bin:/run/wrappers/bin:/home/tburdick/.nix-profile/bin:/nix/profile/bin:/home/tburdick/.local/state/nix/profile/bin:/etc/profiles/per-user/tburdick/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin
CMAKE_INCLUDE_PATH=/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev/include
NIX_LDFLAGS=-rpath /home/tburdick/z/outputs/out/lib64 -rpath /home/tburdick/z/outputs/out/lib  -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib -L/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib
PATH=/home/tburdick/z/env/bin:/nix/store/y033c1zj8h064wm8kbnpmfcf6w54cn3z-zephyr-sdk/bin:/nix/store/21096vzf5ljl6lhplmfd301kb8zyvj05-rimage/bin:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/bin:/nix/store/n7nrikml13ipr3gishnbf2x0g3zbia16-minicom-2.8/bin:/nix/store/04p9vxaplyd4a1m4q8qyh371dfmny3pl-ninja-1.11.1/bin:/nix/store/sj207xd8h848inbwqpqz9lq89yii08sj-gperf-3.1/bin:/nix/store/dp3ghxdzqfqpzkvmsay2026lhjn19lg7-ccache-4.8/bin:/nix/store/h8q4r7f1j906rlffj96dlbbmwc9zbirk-cmake-3.25.3/bin:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/bin:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1/bin:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/bin:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/bin:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/bin:/nix/store/xbm2s7589mswrgngv8ci1zcqfh1l6v2w-xxd-vim-9.0.1441/bin:/nix/store/7rm5784szfma17yklz4dmds20ws8g5v9-nixpkgs-fmt-1.3.0/bin:/nix/store/xnklwbh91g7if2mzy5mh4zcsg818jfls-gcc-wrapper-12.2.0/bin:/nix/store/6504znvqq8hb7qaf5hnfxiccc0g3zmbb-gcc-12.2.0/bin:/nix/store/wskdac6dzswp59qrf8p213ld23l1p0bf-glibc-2.37-45-bin/bin:/nix/store/aifz5nf4xvl2m94ayap13ys48drkhmzk-coreutils-9.1/bin:/nix/store/39x21ag4yfahwjm24a3zrqyhp1rc5mvm-binutils-wrapper-2.40/bin:/nix/store/drdpyvbbp0vylmzmlra408fyj6zv22lq-binutils-2.40/bin:/nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6/bin:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/bin:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/bin:/nix/store/nnjs5w63rc54fg33myzmvx6qknymiksj-clang-tools-14.0.6/bin:/nix/store/gw2ql840xwh37fp7dv430mrxc1bgyxsz-lldb-16.0.6/bin:/nix/store/zfdj9lm7rqizrjj8lk9bkxq4djxkbjh7-clang-wrapper-16.0.6/bin:/nix/store/bmcs67kwf560sv434jaycqdpwg3vivw4-clang-16.0.6/bin:/nix/store/sb5sf8pnbb5dxgr5p8qm344ky8k7f62r-glibc-2.37-45-bin/bin:/nix/store/w8vm09hri2zz7yacryzzzxvsapik4ps4-coreutils-9.1/bin:/nix/store/88bh6zy2sbkj83jcpvmzgqf74213wk2f-binutils-wrapper-2.40/bin:/nix/store/3r87a2wq1w4l66wnsm7rqvy608mx23h6-binutils-2.40/bin:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev/bin:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev/bin:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/bin:/nix/store/b8gwvz4hiq9227321s3lqbk3c6pv22kz-llvm-16.0.6/bin:/nix/store/k6ssc7alckmv6gbympghw365ribdlj31-rustup-1.26.0/bin:/nix/store/gwf21xyl0x0bhgapi66avzf6qmddr44s-patchelf-0.15.0/bin:/nix/store/vaqs26d33rgz2acf81n35v809g8g27vh-clang-wrapper-11.1.0/bin:/nix/store/7wqhmdl4cd8yh7xi32c2ss7l6804i1p7-clang-11.1.0/bin:/nix/store/ximnbjgjqkmyp88hjz9bgsfdfy431ilp-binutils-wrapper-2.40/bin:/nix/store/hf6q72gb3nj3fbfh7j2a14vfjmsgbg25-compiler-rt-libc-16.0.6/bin:/nix/store/82fqlfr6d9s3yvhxp0zv0zswl5w12n19-compiler-rt-libc-11.1.0/bin:/nix/store/w8vm09hri2zz7yacryzzzxvsapik4ps4-coreutils-9.1/bin:/nix/store/4cxs4cigh2zdxvma52ygm3mh2igq70iw-findutils-4.9.0/bin:/nix/store/vikpb6rhmi8zzgsx8syjng9dic8dplm7-diffutils-3.9/bin:/nix/store/4mca20b13q88s6llkr8mc468rh9l9bmr-gnused-4.9/bin:/nix/store/b4in4hmq54h6l34a0v6ha40z97c0lzw2-gnugrep-3.7/bin:/nix/store/p7v8rc82yi4zngjw2z7isgqvfi32l1aj-gawk-5.2.1/bin:/nix/store/2gcfy5f68y7gkryp3wrjmvlci42qb61a-gnutar-1.35/bin:/nix/store/5xzh0z66hpcd3k578my76lx4qgra334q-gzip-1.12/bin:/nix/store/6d9vlwwy7kvxjqmqg4cldgg9mr8nflff-bzip2-1.0.8-bin/bin:/nix/store/qlcm8dzsaa6wyycmx7in8rz6x3pzf6zf-gnumake-4.4.1/bin:/nix/store/0rwyq0j954a7143p0wzd4rhycny8i967-bash-5.2-p15/bin:/nix/store/0g52i0ih3h0d9s40m84gksi2jjm4k3bf-patch-2.7.6/bin:/nix/store/agry2lhy6ilgyacx75w2ycqsdfwr513f-xz-5.4.3-bin/bin:/nix/store/rgg874xkzlfmkzkm7911dwnihswkf54g-file-5.44/bin:/run/wrappers/bin:/home/tburdick/.nix-profile/bin:/nix/profile/bin:/home/tburdick/.local/state/nix/profile/bin:/etc/profiles/per-user/tburdick/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin
CMAKE_PREFIX_PATH=/nix/store/y033c1zj8h064wm8kbnpmfcf6w54cn3z-zephyr-sdk:/nix/store/21096vzf5ljl6lhplmfd301kb8zyvj05-rimage:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env:/nix/store/n7nrikml13ipr3gishnbf2x0g3zbia16-minicom-2.8:/nix/store/04p9vxaplyd4a1m4q8qyh371dfmny3pl-ninja-1.11.1:/nix/store/sj207xd8h848inbwqpqz9lq89yii08sj-gperf-3.1:/nix/store/dp3ghxdzqfqpzkvmsay2026lhjn19lg7-ccache-4.8:/nix/store/h8q4r7f1j906rlffj96dlbbmwc9zbirk-cmake-3.25.3:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0:/nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0:/nix/store/xbm2s7589mswrgngv8ci1zcqfh1l6v2w-xxd-vim-9.0.1441:/nix/store/7rm5784szfma17yklz4dmds20ws8g5v9-nixpkgs-fmt-1.3.0:/nix/store/xnklwbh91g7if2mzy5mh4zcsg818jfls-gcc-wrapper-12.2.0:/nix/store/39x21ag4yfahwjm24a3zrqyhp1rc5mvm-binutils-wrapper-2.40:/nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12:/nix/store/nnjs5w63rc54fg33myzmvx6qknymiksj-clang-tools-14.0.6:/nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev:/nix/store/gv2cl6qvvslz5h15vqd89f1rpvrdg5yc-stdenv-linux:/nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib:/nix/store/gw2ql840xwh37fp7dv430mrxc1bgyxsz-lldb-16.0.6:/nix/store/zfdj9lm7rqizrjj8lk9bkxq4djxkbjh7-clang-wrapper-16.0.6:/nix/store/88bh6zy2sbkj83jcpvmzgqf74213wk2f-binutils-wrapper-2.40:/nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev:/nix/store/pzis69n8rva6rxkkp5vp4c4mklxgp5yf-ncurses-6.4-dev:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4:/nix/store/j0zwp9zygvadcly9dxpm0f4ga7h0n8c9-zlib-1.2.13-dev:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib:/nix/store/b8gwvz4hiq9227321s3lqbk3c6pv22kz-llvm-16.0.6:/nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6:/nix/store/k6ssc7alckmv6gbympghw365ribdlj31-rustup-1.26.0:/nix/store/gwf21xyl0x0bhgapi66avzf6qmddr44s-patchelf-0.15.0:/nix/store/vaqs26d33rgz2acf81n35v809g8g27vh-clang-wrapper-11.1.0:/nix/store/ximnbjgjqkmyp88hjz9bgsfdfy431ilp-binutils-wrapper-2.40:/nix/store/xbdp4qia936b7bkq1axr89r7f2isjn10-compiler-rt-libc-16.0.6-dev:/nix/store/hf6q72gb3nj3fbfh7j2a14vfjmsgbg25-compiler-rt-libc-16.0.6:/nix/store/yjnzgabj270d1v5ppygbhw5lrshlywa8-compiler-rt-libc-11.1.0-dev:/nix/store/82fqlfr6d9s3yvhxp0zv0zswl5w12n19-compiler-rt-libc-11.1.0
CMAKE_LIBRARY_PATH=/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/cwlwbcpkji2mgdb0vcxj878n4051qdac-lldb-16.0.6-lib/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/wnblw3rp0qr0z6wyzhaahch3mkk42gmi-ncurses-6.4/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/8mw6ssjspf8k1ija88cfldmxlbarl1bb-zlib-1.2.13/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/3wljiz2pj44sj63hzjr6b0ni60r8897a-llvm-16.0.6-lib/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib:/nix/store/z2wwdfrh2wyrf2xkbm0di5pi55szbfrz-libcxx-16.0.6/lib
nativeBuildInputs=/nix/store/y033c1zj8h064wm8kbnpmfcf6w54cn3z-zephyr-sdk /nix/store/21096vzf5ljl6lhplmfd301kb8zyvj05-rimage /nix/store/d9h22m8c7irvn866jmc6ilkk8j460bxg-python3-3.10.13-env /nix/store/n7nrikml13ipr3gishnbf2x0g3zbia16-minicom-2.8 /nix/store/04p9vxaplyd4a1m4q8qyh371dfmny3pl-ninja-1.11.1 /nix/store/sj207xd8h848inbwqpqz9lq89yii08sj-gperf-3.1 /nix/store/dp3ghxdzqfqpzkvmsay2026lhjn19lg7-ccache-4.8 /nix/store/h8q4r7f1j906rlffj96dlbbmwc9zbirk-cmake-3.25.3 /nix/store/kzwn4zngw9h10k2msk3cm5n2yp07qz96-dtc-1.7.0 /nix/store/lqwlz76ns9c46qj9lcihb6vzxp3gmy0q-gnumake-4.4.1 /nix/store/ld4wra61gxq0spf16p0a6z3pcklagg6f-gdb-13.1 /nix/store/047yg0alvlwlx2k7nf3qilq3hp0rb7z4-segger-jlink-766 /nix/store/89af5sqf1rcjd7x149mwbcbzvsr8wcny-nrf-command-line-tools-10.16.0 /nix/store/xbm2s7589mswrgngv8ci1zcqfh1l6v2w-xxd-vim-9.0.1441 /nix/store/7rm5784szfma17yklz4dmds20ws8g5v9-nixpkgs-fmt-1.3.0 /nix/store/xnklwbh91g7if2mzy5mh4zcsg818jfls-gcc-wrapper-12.2.0 /nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6 /nix/store/pq8mdg40n1ggphcicx3ymvbxq56vkyx7-graphviz-7.1.0 /nix/store/hq9gk0b60w877fbmqhq95xv5kxz3p3mp-protobuf-3.21.12 /nix/store/nnjs5w63rc54fg33myzmvx6qknymiksj-clang-tools-14.0.6 /nix/store/xp3d0pv6rzsliy5sizxw3h5qj1c61ny4-glibc-multi-2.37-45-dev /nix/store/gv2cl6qvvslz5h15vqd89f1rpvrdg5yc-stdenv-linux /nix/store/b5b05l62zs5gifwx87pm8ii9vrw5xn1v-lldb-16.0.6-dev /nix/store/zfdj9lm7rqizrjj8lk9bkxq4djxkbjh7-clang-wrapper-16.0.6 /nix/store/745cgiby2z7gy05iwv938vzv6s7yw9sp-llvm-16.0.6-dev /nix/store/h9ksqivblnqc6pakafffvgpz0m82cb0z-libcxx-16.0.6-dev /nix/store/k6ssc7alckmv6gbympghw365ribdlj31-rustup-1.26.0

If you look carefully PATH shows my virtualenv as the first path in the list, /home/tburdick/z/env/bin
BUT
The found cmake interpreter is the first thing in CMAKE_LIBRARY_PATH, CMAKE_PREFIX_PATH, CMAKE_INLCUDE_PATH
Perhaps find_program is somehow looking at those paths first despite my PATH, the thing I actually care about, having the virtualenv correctly there? So I tried and I found...
(env) tburdick@zefire ~/z/z/doc (main)> export CMAKE_PREFIX_PATH=$HOME/z/env/bin/:$CMAKE_PREFIX_PATH
(env) tburdick@zefire ~/z/z/doc (main)> rm -rf _build
(env) tburdick@zefire ~/z/z/doc (main)> rm -rf ~/.cache/zephyr
(env) tburdick@zefire ~/z/z/doc (main)> make html-fast
make html DT_TURBO_MODE=1
make[1]: Entering directory '/home/tburdick/z/zephyr/doc'
cmake \
	-GNinja \
	-B_build \
	-S. \
	-DDOC_TAG=development \
	-DSPHINXOPTS="-j auto -W --keep-going -T" \
	-DSPHINXOPTS_EXTRA="" \
	-DLATEXMKOPTS="-halt-on-error -no-shell-escape" \
	-DDT_TURBO_MODE=1
Loading Zephyr module(s) (Zephyr base): doc
Python currently ,
python found /home/tburdick/z/env/bin/python
python found /home/tburdick/z/env/bin/python version 3.10
python3 found /home/tburdick/z/env/bin/python
python3 found /home/tburdick/z/env/bin/python version 3.10
Calling find_package Python3, /home/tburdick/z/env/bin/python
-- Found Python3: /home/tburdick/z/env/bin/python (found suitable version "3.10.13", minimum required is "3.8") found components: Interpreter
Called find_package Python3, /home/tburdick/z/env/bin/python
-- Cache files will be written to: /home/tburdick/.cache/zephyr
-- Found west (found suitable version "1.2.0", minimum required is "1.0.0")
-- Zephyr base: /home/tburdick/z/zephyr
-- Found Doxygen: /nix/store/xknvdvpqg40cnd10gbyr3q29imgsra4k-doxygen-1.9.6/bin/doxygen (found version "1.9.6") found components: doxygen dot
-- Could NOT find LATEX (missing: LATEX_COMPILER PDFLATEX)
CMake Warning at CMakeLists.txt:39 (message):
  LaTeX components not found.  PDF build will not be available.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/tburdick/z/zephyr/doc/_build
cmake --build _build --target html
[0/2] Generating Devicetree bindings documentation...
[1/2] Running Sphinx HTML build...
Running Sphinx v6.2.1
Building Kconfig database...... done
Preparing Doxyfile...
Checking if Doxygen needs to be run...
Running Doxygen...
Syncing Doxygen output...
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 1 source files that are out of date
updating environment: [new config] 1603 added, 0 changed, 0 removed
reading sources... [ 66%] samples/basic/basic .. samples/bluetooth/central_gatt_write/README

So to me, it appears like CMAKE_PREFIX_PATH is taking precedence over my shell path for find_program. It seems this is just the expected behavior of CMake which... seems incredibly wrong and unintuitive.
So much so that FindPython.cmake finds the correct python! It does that by...
https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/FindPython/Support.cmake#L1846
Avoiding all the cmake environment variables, ignoring all the cmake paths...
So we have a bug in our python.cmake that does not exist in cmake's own FindPython support package.
To Reproduce
I suppose try adding a bogus python install to CMAKE_PREFIX_PATH and watch everything fail oddly.
Expected behavior
The first python interpreter in my PATH var is used.
Impact
Building docs is broken for me

@teburd thanks a lot for this useful information.
I already now have some idea of what might be happening, but need to do some testing on this, but unfortunately not having time atm for further investigation.
Marked as priority: low, as this is impacting a very specific setup and a workaround does exist (setting Python3_EXECUTABLE)

See https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/FindPython/Support.cmake#L1786 to start, the very first branch for virtualenvs ignores the cmake env vars.
cmake's FindPython module works well for me, but I can understand if there's confusing things that happen when it goes looking around registries and such for the latest python install.
@tejlmand did you try setting the strategy for FindPython? https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/FindPython.cmake#L314 seems like using the LOCATION strategy might be just fine?

@tejlmand did you try setting the strategy for FindPython? https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/FindPython.cmake#L314 seems like using the LOCATION strategy might be just fine?

Unfortunately its not. Been there, tried that.
The location still doesn't guarantee the order in which Python installations are tried (those in path which https://github.com/zephyrproject-rtos/zephyr/pull/24364 fixes).

Setting Python3_EXECUTABLE doesn't seem to be possible when running twister unless I've missed something (very possible!). I'm carrying around a patch to do my work now which is kind of painful. It seems like in retrospect all the issues here are related to windows and python, can we use the cmake python module on all platforms but windows perhaps?

@tejlmand Setting Python3_EXECUTABLE doesn't seem to be possible when running twister unless I've missed something (very possible!). I'm carrying around a patch to do my work now which is kind of painful. It seems like in retrospect all the issues here are related to windows and python, can we use the cmake python module on all platforms but windows perhaps?

Ok I figured it out with, hilariously... I do
-x Python3_EXECUTABLE="`which python`"

It seems like in retrospect all the issues here are related to windows and python, can we use the cmake python module on all platforms but windows perhaps?

I think the "bigger" question is: if the real-world issues are (as expected) very different between Windows and Linux, then why is 100% of the workaround code shared between the two?
Zephyr's C code is (correctly) split between "arch/" code for arch-specific problems versus common code for common problems. So why does python.cmake's re-invention of FindPython insists on being 100% "portable" when (according to @teburd) most of the problems it tries to solve are not "portable" at all?
PS: we haven't even looked at macOS/brew yet...

Related, and probably better described issue #70258


Stale information in page “Control CPU Management Policies on the Node”

Dear Kubernetes,
Based on the prototyping, I have discovered that there are some aspects that do not correspond to the documentation I followed and are not fully described. I would like to share this experience with you, and I believe that addressing these points will improve the documentation as a whole.
Regarding my assignment, I have been working on prototyping a requirement that was quite challenging to implement CPU-control based on the documentation, which also took a lot of time. Here are the points that i would like to share:

The use of Kubernetes flags mentioned in the documentation as arguments is not supported, as the current version does not support this approach.

When configuring the CPU manager in the Kubelet configuration file, it is important to set the values for "systemReserved" and "kubeReserved". When configuring the CPU manager in the Kubelet configuration file, However, this is not mentioned in the documentation, despite the fact that the proper functioning of the kubelet service depends on it.

In addition, it may be helpful to indicate where the kubelet configuration file can be found. In Ubuntu, this file is located at /var/lib/kubelet/config.yaml.

Related Doc - https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/
/sig docs

/retitle Stale information in page “Control CPU Management Policies on the Node”
/kind bug
/triage accepted
/sig node
/priority backlog

/help
/good-first-issue

I can see the that the documentation has been updated :)

@zackaria-12, I see the updates on the page but I also see in the Configuration section that it shows these options being passed as either command-line flags or config file options.
But in the kubelet ref docs docs, I see that all these command line flags have been deprecated.

(DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag.

So the doc still appears to be outdated in that respect. What do you think?
FYI @sftim

There are still some configuration options that can only be specified with command line flags. There are some new settings that can only be configured in the kubelet config file.
Those warnings can be safely ignored at the moment. But if you are cautious about this, feel free to raise a question on the #sig-node slack channel.

Thanks @tengqm. What about adding a link to the ref doc which lists all the available options (command line flags and config file options) and includes the deprecation notices, so that the user can see which are the valid options, all in one place?

Hey @zackaria-12 . I am completely new to open source and looking forward to make my fist open source contribution. Can you please say more about this issue and what i have to solve because i am unable to understand

Hi @aritraxchatterjee
You mentioned that you are completely new to open source. Well done for specifically looking for issues with the good-first-issue label. I actually am not sure this is was ever a good first issue. I will remove the label that made you think it was.
/remove-good-first-issue
/remove-help

Thank your sir for your response. Actually I will be entering the first
year of my college within a month. So I have just started practicing web
development. Can you help me by pointing out some good first issues so that
I can give a try to solve them?
On Sat, 8 Jul, 2023, 4:22 pm Tim Bannister, @.***>
wrote:

Hi @aritraxchatterjee https://github.com/aritraxchatterjee
You mentioned that you are completely new to open source. Well done for
specifically looking for issues with the good-first-issue label. I actually
am not sure this is was ever a good first issue. I will remove the label
that made you think it was.
/remove-good-first-issue
/remove-help
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/40818#issuecomment-1627104343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAUKVIXRDEXP4XS56GHIJ6TXPE3VTANCNFSM6AAAAAAXJCPGZ4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reorganise render pass objects, add support for some extensions

Changelog:
### Breaking changes
Changes to render pass objects:
- Resolve attachments are now provided as `ResolvableAttachmentReference` values, as part of the `color_attachments`, `depth_attachment` and `stencil_attachment` values. In the `single_pass_renderpass` and `ordered_passes_renderpass` macros, the resolve attachment is indicated by a single arrow, and the resolve mode by a following colon, for example `[color -> color_resolve:Average]`.
- Depth and stencil attachments are now provided separately. They must still use the same attachment, but their layouts and resolve modes can differ.
- Input attachments are now provided as `InputAttachmentReference` values.
- If an attachment has a format with a stencil component, you must now provide `stencil_initial_layout` and `stencil_final_layout` to `AttachmentDescription`, in the same way as `stencil_load_op` and `stencil_store_op`.
- Renamed `LoadOp` and `StoreOp` to `AttachmentLoadOp` and `AttachmentStoreOp` to match the Vulkan names.
- In the `single_pass_renderpass` and `ordered_passes_renderpass` macros, the `load` and `store` fields for attachments are renamed to `load_op` and `store_op`, and ordered below the `format` and `samples` fields, to match the fields of the `AttachmentDescription` structure.

### Additions
- Support for the `khr_depth_stencil_resolve` extension.
- Support for the `khr_separate_depth_stencil_layouts` extension.
- Added `flags` to `RenderPassCreateInfo`, `AttachmentDescription` and `SubpassDescription`.

This adds support for two extensions, that were already supported for dynamic rendering but still missing from render pass objects. I've taken the opportunity to rearrange the subpass attachments a fair bit, so that they match how dynamic rendering does it, which feels a lot cleaner and more consistent. The underlying Vulkan API of course still uses the old structure, so it's converted on the fly when the Vulkan call is made.

All the examples work for me, and I don't get any validation errors either. Do you get any?

That should be fixed now. Still no idea what's going on with the indirect example though.

No, it's there, create.rs lines 122, 273 and 375.

Vulkano treats depth and stencil as entirely separate attachments, but they have to have the same attachment number. Vulkan treats them as a single combined attachment type from the get go, but lets you specify a separate layout for the stencil. The translation between them happens in the code after line 245.

That's why I only did it because there's a model in dynamic rendering. Dynamic rendering already works exactly this way, and I suspect that if Khronos were to redesign the API they'd do it that way for render passes too.

This is done now.


Migrate release to gh actions workflow

Details

Migrate release pipeline to GH actions workflow
Migrate dist-tag pipeline to GH actions workflow
Update release section CONTRIBUTING.md
Update status badge in README.md

@v1v
in the Jenkinsfile there were some functions to setup docker credentials and docker login steps.
However, there were no docker related scripts.
Can you confirm that those were leftovers and it's safe to omit?


SensorNotRequired Error

I am receiving the following warning in Chrome:
SensorNotRequired: https://developers.google.com/maps/documentation/javascript/error-messages
The warning is explained here:
https://developers.google.com/maps/documentation/javascript/error-messages
"The sensor parameter is no longer required for the Google Maps JavaScript API. It won't prevent the Google Maps JavaScript API from working correctly, but we recommend that you remove the sensor parameter from the script element."
This has been causing really weird problems for me causing my app to crash.
I managed to resolve this by deleting the following lines, would be great if you can apply this fix please.
https://github.com/aerisweather/googlemaps-amd/blob/master/src/googlemaps.js#L118

Sure -- if you submit a pull request, I'll merge it in

Please disregard this, I discovered that the issues I experienced were introduced by switching from Bootstrap Tabs to jQuery Tabs, most likely to do with history.pushState calls that I was making to update the URL.


Removing buttonGroup behavior

Removing buttonGroup behavior based on github issue 604
https://github.com/stardust-ui/react/issues/604

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


extract_imports and extract_memories do push_memory duplicated  inModule::instantiate

When building module, memory is collected by both imports and memories now.
What I means Memory::new is called twice when there is only one import  "env" "memory".
The first one is called by me for pass it to linker, but the second one is called by extract_memories.
But if we do not import memory, Memory::new never be called.

Sorry but I don't understand at all what exactly the problem is supposed to be here.

Ok, I will add a test to show it.

See #589

Thank you for the draft PR.
So it seems you want support for Wasm files with multiple memories which is not supported in Wasm MVP.
There is a Wasm proposal call multi-memories which will enable support for having more than just one linear memory at per Wasm file: https://github.com/WebAssembly/multi-memory
However, there are currently no plans to support that in wasmi since it will likely introduce overhead for memory instructions.

Hi @Robbepop Could you give me some feedback?

Sorry, my initial answer was wrong, so I deleted it again, then I forgot to write another. I wrote a new answer as review comment to your PR.


NBT Specification

While this isn't strictly an issue relating to the project, I was wondering what NBT specification/documentation this is based on?
I'm working on implementing a similar library in rust and the Wiki.VG specification is breaking on the JoinGame packet

There is no one specification I can point to as having based this off of. I'm pretty sure it was just based off whatever reference info I could find out there, plus testing it against known good files.
I know the Minecraft Wiki also has a page on NBT. Feel free to also use this library as a reference if you want.


Out of memory

When submitting the command by shell "php import.php" , I always get the message
"Fatal error: Out of memory (allocated<PHONE_NUMBER>)"
Happens on both the remote server and the local server
On xampp I put in import.php:
" Ini_set ('memory_limit', '14400M'); "
But always goes wrong

" Ini_set ('memory_limit', '-1'); " try this

What is Attribute numbers ??

closing the issue


Intel D4 Board V3 doesn´t work and no valid SKU

Hello, I am using the Intel D450 camera with the D4 V3 module.
When I connect both via USB, it says "Intel Corp. Intel(R) RealSense(TM) Invalid SKU."
When I connect only the D4 V3 module windows says "it does not recognize the USB device, it is not working correctly"
I have tried updating the firmware in two ways as I have seen in other issues:
Way 1: I have installed RealSense Viewer SDK on WIndows 10, but when I connect the camera it does not detect it, so I cannot update the firmware
Way 2: I have tried using the command rs-fw-update -l on Ubuntu 20.04.06 LTS but this returns:
"rs-fw-update: command not found" (I have tried other tools, but they all return the same).
¿What can I do? I think the problem is the firmware in D4 V3 but I don´t know how I can update it.
KERNEL

Required Info

Camera Model
D450

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(5.15.0-89-generic)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

Hi @albertoo22  When combining a D450 depth module with the Vision Processor D4 V3, the Invalid SKU error can occur if a newer version of the D450 module is being used with an older version of the D4 V3, as described at https://github.com/IntelRealSense/librealsense/issues/11621#issuecomment-1536539701
There are two approaches to solving this.

Connect the older K83121-100 version of the D450 depth module to the D4 board, update the firmware and then re-connect the depth module that you were using before.

This option would not work though unless you already owned an older K83121-100 version of the D450, as there is no way to know which version you are getting when ordering from a retailer.
Or the other approach is:

Disconnect the D450 depth module and try to perform a firmware update (the firmware is stored on the D4 V3, so it can update firmware without a depth module attached).  The D4 on its own should be recognized as D405i Tester instead of D450.

A problem with this method though is that 'D405i Tester' is not currently recognized as a RealSense camera model ID when attempting firmware update and so it does not work.  Intel are planning to add support for 'D405i Tester' to allow firmware update in this mode, so this invalid SKU issue should hopefully be fixable in future without having to obtain an older board.
The other approach of changing the D450 board for an older version did work for a RealSense user who had such a board and tried it, as described at https://github.com/IntelRealSense/librealsense/issues/12205

When I connect D4 V3 only, Windows doesn't detect the USB, so I can not make the second way that you say :/.
Are there other option to update the firmware?
Also, if i conect the camera and write this command: 'roslaunch realsense2_camera rs_camera.launch' . I get this error:
NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
auto-starting new master
process[master]: started with pid [3908]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 18beac90-8ab2-11ee-be1d-99d3306807f9
process[rosout-1]: started with pid [3918]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [3925]
process[camera/realsense2_camera-3]: started with pid [3926]
[ INFO] [1700820803.170722498]: Initializing nodelet with 3 worker threads.
[ INFO] [1700820803.379232005]: RealSense ROS v2.3.2
[ INFO] [1700820803.379377640]: Built with LibRealSense v2.50.0
[ INFO] [1700820803.379408279]: Running with LibRealSense v2.50.0
[ INFO] [1700820803.440641909]:
[ WARN] [1700820803.773818755]: Device 1/1 failed with exception: hwmon command 0x10( 0 0 0 0 ) failed (response -844431340= unknown)
[ERROR] [1700820803.774141915]: The requested device with  is NOT found. Will Try again.
Do you know if this error is related to the problem of 'Invalid SKU'?

The ROS wrapper likely cannot detect the camera because the D450 module is not being identified.
There is nothing that you can do yourself to correct this issue with firmware updating, unfortunately.  I will discuss your situation with my Intel RealSense colleagues in the coming week.  Thanks very much for your patience until then.

Good morning!! Is there any news on the issue?

I am awaiting a response.   Thanks very much for your patience.

Hello MartyG-RealSense, any news? Thank you

Hi @albertoo22  My colleagues have responded to me.  Can you send me your postal address and the number of D450 depth modules that you have to my email address below please so that I can continue the support discussion with you privately.
<EMAIL_ADDRESS>

Now, in order to update the firmware and be able to use the D450 module, how can I do it?
I connect the module D430 with the Visor Processor D4v3 and I receive this notification (photo attached)

Hi @developajarit  The message box indicates that you have version 2.48.0 of the RealSense SDK and firmware driver version <IP_ADDRESS>.
You should be using firmware version <IP_ADDRESS> with SDK 2.48.0.
The appropriate firmware update procedure would be:

Download the bin file for firmware <IP_ADDRESS> from the firmware archive page at the link below.

https://dev.intelrealsense.com/docs/firmware-releases#d400-series-firmware-downloads

In the RealSense Viewer tool, go to the More option near the top of the Viewer's options side-panel and select the Update Firmware option from its drop-down menu.
.
A file selector window will pop up.  Navigate to the location on your computer that you downloaded the bin file to and select it.  The firmware update should then automatically begin.

Your Viewer images shows that you are using the D430 module.  The D4 V3 board will only work with the D450 module.  If you have a D430 board then you need to use the V1 board if you don't need an IMU (Motion Module), or the V2 board if you need an IMU.

I am currently using the D450 K83121-101 module with the D4V3 K94249-110 vision processor.
Connected to the computer, it shows what I mentioned above.

I repeat the steps I have followed:

I have connected the vision processor to D4V3 with the D430 module to be able to update the firmware in order to later use the D450 module with the D4V3 vision processor, since it had 'invalid SKU'.

I have updated the firmware to <IP_ADDRESS>.

Once the firmware was updated, I connected the D4V3 vision processor to the D450 module again. The 'Invalid SKU' message no longer appears, but the module is detected as: Intel RealSense USB2 D4xx Recovered

I forgot to say that I am the same user as albertoo22, just with a different account!!

Thank you for the confirmation of the module that you are using.  Your Viewer was identifying the camera as a D430i.

My understanding from previous Invalid SKU cases is that the K83121-101 version of the D450 module prefers the latest firmware to be used with it, as described at https://github.com/IntelRealSense/librealsense/issues/11621#issuecomment-1536539701
Could you try updating the firmware to <IP_ADDRESS> please.

Now it is recognized correctly, thank you very much!!
Now there is a problem receveing frames form the cameras, I was already seeing something related to this and I read that it probably because it is being detected as USB 2.0 instead of USB 3.0, right?
When I active the Stereo Module I recived this error:

This error is likely because you have SDK 2.48.0 installed.  Using the latest firmware with old SDK versions results in this Auto Exposure Limit error message.
Please visit the link below and download and run the file Intel.RealSense.Viewer.exe in the 'Assets' file list at the bottom of the page.  This will launch the 2.54.2 version of the Viewer that is designed for use with firmware <IP_ADDRESS>.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.54.2
Installing this Viewer will not overwrite the 2.48.0 SDK installation already on your computer.

Perfect, it seems to be working correctly now.

One last question, can the fact that the connection is being detected as USB 2.0 have any influence on the use of this camera?
I also have the T265 tracking module and it is also detected as USB 2.0 and in this case the fisheye cameras do not start when I try to start it through ROS and RVIZ

If you are using a depth module then you would not have had an official RealSense USB cable supplied with it.  If you are using a USB cable that you purchased yourself then there is a chance that it could be a USB2 cable rather than a USB3 cable.  USB2 cables are missing extra wires that USB3 cables have, and that prevents USB3 devices from operating at USB3 speed.
If it is a USB3 cable, the camera would also be detected as USB2 if the camera was plugged into a USB2 hub or in a USB2 port on the computer.

Okay, thank you very much for the clarification. What is the specific USB 3.0 cable for RealSense cameras?

The official cable is not available for purchase separately but a company called Newnex supplies RealSense-compatible USB3 cables of equal quality to the official one.
https://www.newnex.com/realsense-3d-camera-connectivity.php
However, other USB3 cables should work so long as they are described in their store listing as data transfer cables and are not charging cables.

Hi @albertoo22  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Fix two class context errors

DsMonad is required due to the use of dsExp at line 163.

This should fix issue #2

Great - thanks a lot!


Snapshots not related correctly with Families

➤ Kodey Converse commented:
https://github.com/FundacionParaguaya/FP-PSP-SERVER/pull/123


[Bug]: Cant delete melonloader from boneworks

All of the following criteria must be met

[X] All Requirements must be installed.
[ ] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
I deleted melonloader folders from the boneworks, and i have this issue (it crashes the game) (screenshot)

After that i reinstalled boneworks and i still have this
Did you attach your log file?

[ ] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Well your first mistake was trying to manually delete things.
You could have just used the installer to uninstall MelonLoader.
Either way delete version.dll to fix it.

thanks, someone on reddit told me to delete it manually


LISA test harness

This issue is to develop a single test execution framework (test harness) to use by LISA:
Currently we have 3 ways:

executor
Android experiments
WA

We should have a single streamlined way of running a workload and collecting its data, than all these multiple ways.
Next, workloads can be any of the following:

workload generator (wlgen)
Android workloads (camera, uibench etc)
Android behaviors (turn screen on/off)

Its best if all the above workloads are also in a single place, like WA.  The wlgen can probably be a devlib instrument or something, with a corresponding WA frontend.
This was discussed at ARM with @qperret  @valschneider and @douglas-raillard-arm . Please update the issue with anything I missed.

Yes sounds good, also probably that category can include wlgen stuff as well?

Most likely, unless there are strong advantages to define a "pure" wlgen workload.

I think that discussion can happen on the code itself now (see https://lisa-linux-integrated-system-analysis.readthedocs.io/en/next/kernel_tests.html#module-lisa.tests.kernel.test_bundle)


Don't use enhanced lang to support switchy 2.1.1

Hello! One of the other times we made a PR, we swapped the lang files to use lib39 dessicant's enhanced  lang feature, like switchy does.
We've stopped bundling lib39 in 2.1.1 because we were using it for... only this. So, here you go!

hi hi! we were just sweeping through all the override jars we currently have in our modpack - any chance of this getting a release?

hi hi! we were just sweeping through all the override jars we currently have in our modpack - any chance of this getting a release?

Yes! although I’ve been thinking about just giving you push access to the repo and adding you as a project maintainer on modrinth, since I rarely manage to sit down to push an update. Let me know if you’d be interested in that or not! If not I’ll publish the update hopefully within a couple of days

🛠 released and cleaned up where I could! filled in a the missing github ones


Add support for per frame meta data.

I think at this point we have established that the sidecar dictionary for metadata doesn't really belong within fileseq proper. It is a specialized use of the library and can be done downstream in applications or libraries that use fileseq.


No playback found.

Describe the bug
Yesterday, after a reset the spotify-player can't play any song because of the
"No playback found. Please make sure there is a running Spotify client and try to connect to it using the 'SwitchDevice' command." error
I tried to connect again from my phone, but it doesn't work.
To Reproduce
Steps to reproduce the behavior.
Log and backtrace
spotify_player::client::handlers: Failed to handle client request: failed to handle the player request: no playback found
Environment

OS: Arch
Application version: 0.15.2

Yesterday, after a reset the spotify-player can't play any song

Do you mean device reset like resetting your phone?

I tried to connect again from my phone, but it doesn't work.

Can you describe specifically what you do by "connect again from my phone"? Does any devices shown up if you press D (SwitchDevice command)?

Do you mean device reset like resetting your phone?
Yes, i just turned off and on the phone and the pc
Can you describe specifically what you do by "connect again from my phone"? Does any devices shown up if you press D (SwitchDevice command)?
Yeah, i thought it will work if i "connect" to spotify-player from the android app. In the spotify android app, i see the spotify-player device, but from the spotify-player i didn't saw any

Thanks for the clarification.

In the spotify android app, i see the spotify-player device, but from the spotify-player i didn't saw any

You don't see any devices from spotify_player probably because you haven't set up https://github.com/aome510/spotify-player#spotify-connect.
"connect" spotify-player from any external app should work unless you left the player not running for a while in which it may need a manual restart (by calling RestartIntegratedClient command) or it may take a while to re-initialize the application's state when handling the connect request.
Can you also include the full log? Looking into a single line does not help investigate.

"connect" spotify-player from any external app should work unless you left the player not running for a while in which it may need >a manual restart (by calling RestartIntegratedClient command) or it may take a while to re-initialize the application's state when >handling the connect request.

I used the player every day before this issue, but i restarted it as u mentioned still the same problem (+a strange alsa lib pcm_dmix.c when i tried it with the R).

You don't see any devices from spotify_player probably because you haven't set up https://github.com/aome510/spotify-
player#spotify-connect.

'm done with this too, but when it worked, i used with the default clientId (yes, i tried to use the default again)

Can you also include the full log? Looking into a single line does not help investigate.

Of course!
logs

2023-11-12T17:36:43.926279Z  INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, initial_volume: Some(45875), has_volume_ctrl: true, autoplay: false }
2023-11-12T17:36:43.926316Z  INFO spotify_player::streaming: Initializing a new integrated player with device_id=8bf3e1d0-dc82-42e9-a50b-a1733b3f0767
2023-11-12T17:36:43.926428Z  INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol
2023-11-12T17:36:44.048909Z  INFO spotify_player: No playback found on startup, trying to connect to an available device...
2023-11-12T17:36:44.049119Z  INFO spotify_player::cli::client: Starting a client socket at <IP_ADDRESS>:8080
2023-11-12T17:36:44.050519Z  INFO spotify_player::media_control: Initializing application's media control event watcher...
2023-11-12T17:36:44.162607Z  INFO client_request{request=GetCurrentUser}: spotify_player::client: successfully handled the client request, took: 113ms
2023-11-12T17:36:44.173989Z  INFO client_request{request=GetUserFollowedArtists}: spotify_player::client: successfully handled the client request, took: 124ms
2023-11-12T17:36:44.262941Z  INFO client_request{request=GetUserPlaylists}: spotify_player::client: successfully handled the client request, took: 213ms
2023-11-12T17:36:44.363898Z  INFO client_request{request=GetUserSavedAlbums}: spotify_player::client: successfully handled the client request, took: 314ms
2023-11-12T17:36:44.497762Z  INFO client_request{request=GetUserSavedTracks}: spotify_player::client: successfully handled the client request, took: 448ms
2023-11-12T17:36:45.122595Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Available devices: []
2023-11-12T17:36:45.122634Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Trying to connect to device (id=myDevice)
2023-11-12T17:36:45.523840Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Connection succeeded (device_id=myDevice)!
2023-11-12T17:36:45.523882Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: successfully handled the client request, took: 1474ms
2023-11-12T17:36:46.862267Z  INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Playlist(PlaylistId("myPlaylist")))), update the context state
2023-11-12T17:36:46.862351Z  INFO client_request{request=GetContext(Playlist(PlaylistId("myPlaylist")))}: spotify_player::client: Get playlist context: spotify:playlist:myPlaylist
2023-11-12T17:36:47.542221Z  INFO client_request{request=GetContext(Playlist(PlaylistId("myPlaylist")))}: spotify_player::client: successfully handled the client request, took: 679ms
2023-11-12T17:36:47.893207Z ERROR client_request{request=Player(StartPlayback(Context(Playlist(PlaylistId("myPlaylist")), Some(Uri("spotify:track:trackID")))))}: spotify_player::client::handlers: Failed to handle client request: failed to handle the player request: no playback found
2023-11-12T17:36:49.029226Z ERROR client_request{request=Player(StartPlayback(Context(Playlist(PlaylistId("myPlaylist")), Some(Uri("spotify:track:trackID")))))}: spotify_player::client::handlers: Failed to handle client request: failed to handle the player request: no playback found

I give a try in https://github.com/aome510/spotify-player/pull/289. Not sure if it works. Can you check out the branch and run the application with cargo run to confirm.


helm template --output-dir x --name release renders to colliding path

Output of helm version: Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Output of kubectl version: N/A
For example, say I want to render two releases of nginx, mine1 and mine2:
% helm template -n mine1 --output-dir out docs/examples/nginx
wrote out/nginx/templates/pre-install-secret.yaml
wrote out/nginx/templates/configmap.yaml
wrote out/nginx/templates/service.yaml
wrote out/nginx/templates/service-test.yaml
wrote out/nginx/templates/deployment.yaml
wrote out/nginx/templates/post-install-job.yaml
% helm template -n mine2 --output-dir out docs/examples/nginx
wrote out/nginx/templates/pre-install-secret.yaml
wrote out/nginx/templates/configmap.yaml
wrote out/nginx/templates/service.yaml
wrote out/nginx/templates/service-test.yaml
wrote out/nginx/templates/deployment.yaml
wrote out/nginx/templates/post-install-job.yaml

The second invocation clobbers the first. I would have expected out/nginx/templates to include the release name to avoid such a collision.

https://github.com/helm/helm/compare/master...nickatsegment:template-include-release-name fixes the issue, but in a backwards-incompatible way.
% bin/helm template -n mine1 --output-dir out docs/examples/nginx
wrote out/mine1/nginx/templates/pre-install-secret.yaml
wrote out/mine1/nginx/templates/configmap.yaml
wrote out/mine1/nginx/templates/service.yaml
wrote out/mine1/nginx/templates/service-test.yaml
wrote out/mine1/nginx/templates/deployment.yaml
wrote out/mine1/nginx/templates/post-install-job.yaml

@nickatsegment Thanks for raising this.
At the moment the output works as expected, using the chart name as the directory after the output root. As you have mentioned, if we change this to use the release name then it would be backward incompatible.
cc @mattfarina @bacongobbler @adamreese what do you think?

I wouldn't complain except there's no way to avoid the chart name suffix. I could do
name=mine1
helm template -n $name --output-dir out/$name docs/examples/nginx

But that ends up in out/mine1/nginx/templates. (The templates thing is weird too; not important though.)

@nickatsegment We discussed this at the weekly dev call yesterday. As the change directly would break backward compatibility, then we would be against this. However, if you added a flag something like --release-name then that would be ok.
If you are interested, do you want to push a PR for review?


Cursor is flickering when terminal is active

No issues with the cursor while running the following script using :term job.sh, but it is flickering with :vert term job.sh (in both vim and gvim) and with :bo term job.sh on gvim:
$ cat job.sh
#!/bin/bash
for i in seq 1 20000;
do
sleep 0.005
echo "$i"
done
To reproduce:
$ (g)vim -u NONE
:vert term job.sh " or :bo
CTRL-Ww
" look at the cursor
I'm running Vim 8.1.10 on RHEL 6.
Thanks,
Ramel

I cant reproduce on debian jessie with xterm and vim-8.1.0001.

Actually, I noticed something strange with gnome terminal on ubuntu (16.04) -when I open a terminal and also after starting vim the cursor is blinking, but when I start :term inside vim the cursor stops blinking, also after exiting vim (so there is no flickering). I believe that this is another issue..
You can still see the original issue in the gui (after moving the empty window to the top):

Got it on xterm, my mistake about job.sh. If not your issue, I had to think it normal. Now, it will annoy me too. :smile:
I don't know, how cursor is drawing yet and I will check it in freetime, it can be interest. Hope to see more comments here about what this can be.

Got it on xterm, my mistake about job.sh. If not your issue, I had to
think it normal. Now, it will annoy me too. :smile:
I don't know, how cursor is drawing yet and I will check it in
freetime, it can be interest. Hope to see more comments here about
what this can be.

It might be unavavoidable.  In most terminals the cursor shows up where
text is being redrawn, moving forward when outputting text.  Vim has to
hide the cursor while this is happening, and then restore it to its
original position.  Thus it will be hidden for a short moment.
In the GUI we might do something more clever, don't hide it if we are
redrawing another window (and we know no scrolling will happen, no menu
pops up, etc.).
--
For large projects, Team Leaders use sophisticated project management software
to keep track of who's doing what.  The software collects the lies and guesses
of the project team and organizes them in to instantly outdated charts that
are too boring to look at closely.  This is called "planning".
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Thanks for your answer. Nice to known it.

I have the same issue, weird part is that neovim does not have this issue.


Phone gap plugin not working with clevertap plugin ..

We are using phonegap plugin to get the notfication data in ionic2 but there are some dependency issue that we are facing ,
The reason to use phonegap plugin because we want to render push notification to the specific page based on the data which we have passed from the clevertap notification .
Here is the errors :
FAILURE: Build failed with an exception.
    * Where:
    Script '/var/www/html/jp_app/platforms/android/phonegap-plugin-push/app2-push.gradle' line: 38

    * What went wrong:
    A problem occurred evaluating root project 'android'.
    > Failed to apply plugin [class 'com.google.gms.googleservices.GoogleServicesPlugin']
        > For input string: "+"

So there is any alternate to push notification in ionic frameworks(Hybrid) or any other suggestion to implement this ..
Thanks and Regards
Pushpendra Kumar

@coder-hunt same root cause as #1718. Waiting for a cordova release so I can fix it.


change "add author" to "add creator" for datasets

Describe the improvement
There is an "add author" button and also the popup mentions authors instead of creators. Replace author by creator for datasets.
Screenshots

@sdebodt because they are authors. I guess the title of the tab "Creators" is wrong. Not @nics ?

@nicolasfranck the librecat field is author, but the labels in dataset context should be Creator, so dialog title should be Add creator


Can't put Sonoff S26 in LAN only / DIY mode

Hello, this is more of a device-related question, I'm asking because I didn't get a satisfactory response from the Itead support forums. Please delete if or close if not allowed.
I have a Sonoff S26 that I'd like to put in LAN only / DIY mode to use with this integration; these are the steps I've followed:

Press button until LED starts to blink in Compatible Pairing mode (two short blinks and one long).
Release button, then press again until it blinks in Soft AP mode (continuous short blinks).
Soft AP appears and I connect to it on my phone (Samsung S8+ with Android 9).
Once connected, access http://<IP_ADDRESS> on Chrome version 85.0.4183.101.
Chrome displays error page with either ERR_CONNECTION_RESET or ERR_SOCKET_NOT_CONNECTED. Sometimes the "loading" bar hangs indefinitely.

Has anyone else encountered this error? Am I doing something wrong?
Thank you for your time and help.

Integration works with any ewelink devices. They only need to be added to the ewelink app. If the device is on firmware 3+ it will work in local mode.

So you absolutely need to use the ewelink app to configure the Wi-Fi, right? I thought it'd display some kind of web portal while in soft AP mode, where you could configure the Wi-Fi and perhaps other settings (the classic ESP8266 Wi-Fi Manager; akin to how the Shelly devices work). I found some documentation and forum posts supporting this, but the web doesn't load for me.
Firmware of my S26 is 3.5.0. (Forgot to add that in the original question, sorry.)

Sonoff devices do not have a friendly wifi setup page. S26 does not have DIY mode for LAN only. But all devices on firmware 3+ can work using the local protocol and this component supports it.

Oh, I see. So you really can't get rid of the app or the Sonoff cloud, which was my goal. Thank you for your time and help!


Fixed app.tsx console logs + further cleanup

fixed console log tokens in app.tsx, cleaned it up a bit further

Looks great!


Add config for starting server to vscode settings

Does adding this to the config help:
"subProcess": true,

(from https://stackoverflow.com/questions/60515935/visual-studio-code-does-not-attach-debugger-to-multi-processes-in-python-using-p)

Does adding this to the config help:
"subProcess": true,

(from https://stackoverflow.com/questions/60515935/visual-studio-code-does-not-attach-debugger-to-multi-processes-in-python-using-p)

I tried that option but it didn't seem to do anything.
I think we should merge this now as an initial version.


Multiple auth rules for multi owners

Is your feature request related to a problem? Please describe.
The documentation allows for multiple owners of a model, buth the Amplify iOS implementation is lacking this important feature.
Describe the solution you'd like
There is already some work on this, but it has been stalled for almost a year: https://github.com/aws-amplify/amplify-ios/pull/1606
Describe alternatives you've considered
The alternative is to not share data between users, but this is hardly a solution.
Is the feature request related to any of the existing Amplify categories?
DataStore
Additional context
No response

Thanks for opening this @askemottelson. We'll investigate the status of https://github.com/aws-amplify/amplify-ios/pull/1606 respond back to this issue with any updates.

Hi @atierian and @lawmicha - thanks for looking into this. I just noticed that remote DataStore real time events are also not triggered for multi auth models (i.e., only local events are fired when listening on Amplify.DataStore.observeQuery). This is a critical bug, as an app with shared data access will have to continuously and manually check for DataStore updates

@atierian any news on this? Seems like a pretty big deal that Amplify iOS cannot support data sharing across users?

any update on this? @atierian

Hello! Someone has a workaround on how to share data across users with Amplify iOS? Thank you!

Hello! Someone has a workaround on how to share data across users with Amplify iOS? Thank you!

I'm afraid not. We are still eagerly waiting for support for multi users, and receiving data update events in real time.

any update on this please ... we wait a long time for it ? @atierian

This was released in https://github.com/aws-amplify/amplify-swift/releases/tag/2.19.0

Closing since this has been released. Feel free to open another issue with the relevant schema if something isn't working as expected in Amplify 2.19.0


resolution for smartphone

hi
In my smartphone i don't see the pictures in full frame because the pictures are crop, how do i do to modify thi parameter?
Thank you

They resize due to the background cover rule. Pictures fill the size of the box, so they resize automatically - if the image is being cropped in a way you don't like at certain positions then you can change the background-position at different screen sizes using CSS media queries.


DXVK as a graphics SDK for native Linux apps?

Can DXVK be used as an alternative to OpenGL to make native Linux (not Wine) or cross-platform apps? It could be a great alternative for people who find the DirectX API cleaner than OpenGL and simpler than Vulkan.

The DirectX APIs are not cross-platform, and parts of it (specifically, DXGI) would have to be redesigned to allow native Linux support. So no, this is not possible, it could be used for wine-based ports though.


A stock set up fails to build during the init script when the app name is not provided

I ran into issues with fly deployment and when creating a new app to test, the init script fails.
Note: if an app name is supplied, the init succeeds, e.g.:
npx create-remix@latest --install --init-script --git-init --template epicweb-dev/epic-stack test-app

My env:
MacOS 13.5.2

> npx --version
9.5.1
> node --version
v18.16.0

Full terminal log: create.txt
> npx create-remix@latest --install --init-script --git-init --template epicweb-dev/epic-stack

 remix   v2.0.1 💿 Let's build a better website...

   dir   Where should we create your new project?
         ./my-remix-app

      ◼  Template: Using epicweb-dev/epic-stack...
      ✔  Template copied

      ✔  Dependencies installed

      ✔  Git initialized
      ✔  Dependencies for remix.init script installed

      ◼  Running template's remix.init script...

> setup
> npm run build && prisma generate && prisma migrate deploy && prisma db seed && playwright install

> build
> run-s build:*

> build:icons
> tsx ./other/build-icons.ts

SNIP

✘ [ERROR] Build failed with 35 errors:
app/routes/_auth+/forgot-password/index.tsx:11:37: ERROR: Could not resolve "~/components/error-boundary.tsx"
app/routes/_auth+/forgot-password/index.tsx:12:33: ERROR: Could not resolve "~/components/forms.tsx"
app/routes/_auth+/forgot-password/index.tsx:13:29: ERROR: Could not resolve "~/components/ui/status-button.tsx"
app/routes/_auth+/forgot-password/index.tsx:18:7: ERROR: Could not resolve "~/routes/resources+/verify.tsx"
app/routes/_auth+/forgot-password/index.tsx:21:44: ERROR: Could not resolve "~/utils/user-validation.ts"

SNIP

✘ [ERROR] Could not resolve "~/utils/user.ts"

    app/routes/settings+/profile.change-email.index/index.tsx:22:24:
      22 │ import { useUser } from '~/utils/user.ts'
         ╵                         ~~~~~~~~~~~~~~~~~

  You can mark the path "~/utils/user.ts" as external to exclude it from the bundle, which will remove this error.

ERROR: "build:remix" exited with 1.

      ▲  Oh no! Template's remix.init script failed

'~/utils/user.ts' should be '#app/utils/user.ts' along with the rest of those ~-prefixed paths. But that doesn't appear in the template at all. That was changed a few weeks ago 🤔
I'm unable to reproduce your issue:
~/Desktop 🦂
$ npx create-remix@latest --install --init-script --git-init --template epicweb-dev/epic-stack
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

 remix   v2.0.1 💿 Let's build a better website...

   dir   Where should we create your new project?
         ./my-remix-app

      ◼  Template: Using epicweb-dev/epic-stack...
      ✔  Template copied

      ✔  Dependencies installed

      ✔  Git initialized
      ✔  Dependencies for remix.init script installed

      ◼  Running template's remix.init script...

> setup
> npm run build && prisma generate && prisma migrate deploy && prisma db seed && playwright install

> build
> run-s build:*

> build:icons
> tsx ./other/build-icons.ts

Generated 27 icons

> build:remix
> remix build --sourcemap

 info  building... (NODE_ENV=production)
 warn  🚨  source maps enabled in production
┃ You are using `--sourcemap` to enable source maps in production,
┃ making your server-side code publicly visible in the browser.
┃ This is highly discouraged!
┃ If you insist, ensure that you are using environment variables for secrets
┃ and are not hard-coding them in your source.
┗
 info  built (1.6s)

> build:server
> tsx ./other/build-server.ts

building...

  server-build/index.js       6.3kb
  server-build/index.js.map  12.6kb

⚡ Done in 3ms
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 78ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)

import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()

See other ways of importing Prisma Client: http://pris.ly/d/importing-client

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "data.db" at "file:./data.db?connection_limit=1"

SQLite database data.db created at file:./data.db?connection_limit=1

1 migration found in prisma/migrations

Applying migration `20230914194400_init`

The following migration have been applied:

migrations/
  └─<PHONE_NUMBER>4400_init/
    └─ migration.sql

All migrations have been successfully applied.
Environment variables loaded from .env
Running seed command `tsx prisma/seed.ts` ...
🌱 Seeding...
🧹 Cleaned up the database...: 3.533ms
🔑 Created permissions...: 11.228ms
👑 Created roles...: 2.381ms
👤 Created 5 users...: 1.705s
🐨 Created admin user "kody": 637.177ms
🌱 Database has been seeded: 2.359s

🌱  The seed command has been executed.

> format
> prettier --write . --log-level warn

? Would you like to setup deployment right now? No
Ok, check the docs (https://github.com/epicweb-dev/epic-stack/blob/main/docs/deployment.md) when you're ready to set that up.
Setup is complete.

 Failed to commit changes from remix.init script.
~/Desktop 🦂
$

I tried a couple of times to make sure I was not hallucinating.
Given your success, I shall try again.
Thanks for taking a look.

I have tried three more times, all successful.


I changed one line and this has ceased to be a problem for me.
I commented out a line in BoxDecoration, which assigned him a white
child: Container(   width: CIRCLE_SIZE + CIRCLE_OUTLINE,   height: CIRCLE_SIZE + CIRCLE_OUTLINE,   decoration: BoxDecoration(     //color: Colors.white,     shape: BoxShape.circle,     boxShadow: [       BoxShadow(         color: Colors.black12,         blurRadius: 8) ])),

Thanks, I will review your PR and update.

Merged, will be in the next version


docstrings core update

added missed docstrings
formated docstrings to consistent form

@baskaryan Merging conflicts resolved.

Hey @efriis Please, let me know when you (or somebody else) want to review this PR. Then I will address the merging conflicts. Otherwise, I'm addressing them again and again and again.

@efriis Thanks!


Layout constraints are breaking when aspect ratio on UIImageView is set

Describe the bug
Well  i have collection view cell which contains UIImageView which needs to have 16:9 aspect ratio and two labels below UIImageView. UIImageView needs to be 16:9 and labels below could have dynamic height. If i set aspect ratio on UIImageView 16:9 then i get in debug console this warning:
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x60000274edf0 UIImageView:0x12a6287c0.height == 50   (active)>
Besides that when i fast scroll collection view to the bottom layout being totally messed up.
I tried also to put low priority for this aspect ratio but then i don't get properly layout(i don't see 2 labels below UIImageView) and when i scroll collection view then cells get  bigger(too much).
To Reproduce
Steps to reproduce the behaviour:

Create UICollectionViewCell which inherits MagazineLayoutCollectionViewCell.
Create UIImageView and two labels below UIImageView.
Set 16:9 aspect ratio on UIImageView.
Setup constraints between 2x UILabel and UIImageView vertically.

Expected behavior
Don't get breaking layout constraints when set aspect ratio 16:9 on UIImageView and fast scrolling should not mess up layout.
Smartphone (please complete the following information):

Device/Simulator: Apple TV 4K
OS: tvOS

Since the collection view temporarily needs to set the cell to an estimated height (before it self-sizes), your contained view needs to be able to layout at a different height without constraints breaking.
At Airbnb, we do this by setting the priority of our bottom-most constraint to .defaultLow. For example:
let bottomConstraint = label.bottomAnchor.constraint(equalTo: bottomAnchor)
bottomConstraint.priority = .defaultLow
NSLayoutConstraint.activate([
  // other constraints
  label.leadingAnchor.constraint(equalTo: leadingAnchor),
  label.trailingAnchor.constraint(equalTo: trailingAnchor),
  label.topAnchor.constraint(equalTo: imageView.bottomAnchor),
  bottomConstraint
])