Offchain python package install error [Windows 11]

Tried installing. Install failed due to error (same error in this log). Hard installed Microsoft Visual C++ 14.0. Also verified Python version 3.11. On Microsoft Windows [Version 10.0.22000.1098] machine. Error log below is after trying to install.
Is this an issue because of Poetry dependency management? Is this something I should install before trying to install the offchain package again?
Log:
C:\Users\user>pip install offchain
Collecting offchain
Using cached offchain-0.1.3-py3-none-any.whl (52 kB)
Collecting pydantic<2.0.0,>=1.9.2
Using cached pydantic-1.10.2-cp311-cp311-win_amd64.whl (2.1 MB)
Collecting python-json-logger<3.0.0,>=2.0.4
Using cached python_json_logger-2.0.4-py3-none-any.whl (7.8 kB)
Collecting requests<3.0.0,>=2.28.1
Using cached requests-2.28.1-py3-none-any.whl (62 kB)
Collecting tenacity<9.0.0,>=8.0.1
Using cached tenacity-8.1.0-py3-none-any.whl (23 kB)
Collecting urllib3<2.0.0,>=1.26.11
Using cached urllib3-1.26.12-py2.py3-none-any.whl (140 kB)
Collecting web3<6.0.0,>=5.30.0
Using cached web3-5.31.1-py3-none-any.whl (501 kB)
Collecting typing-extensions>=4.1.0
Using cached typing_extensions-4.4.0-py3-none-any.whl (26 kB)
Collecting charset-normalizer<3,>=2
Using cached charset_normalizer-2.1.1-py3-none-any.whl (39 kB)
Collecting idna<4,>=2.5
Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting certifi>=2017.4.17
Using cached certifi-2022.9.24-py3-none-any.whl (161 kB)
Collecting aiohttp<4,>=3.7.4.post0
Using cached aiohttp-3.8.3-cp311-cp311-win_amd64.whl (317 kB)
Collecting eth-abi<3.0.0,>=2.0.0b6
Using cached eth_abi-2.2.0-py3-none-any.whl (28 kB)
Collecting eth-account<0.6.0,>=0.5.9
Using cached eth_account-0.5.9-py3-none-any.whl (101 kB)
Collecting eth-hash[pycryptodome]<1.0.0,>=0.2.0
Using cached eth_hash-0.5.0-py3-none-any.whl (8.9 kB)
Collecting eth-rlp<0.3
Using cached eth_rlp-0.2.1-py3-none-any.whl (5.0 kB)
Collecting eth-typing<3.0.0,>=2.0.0
Using cached eth_typing-2.3.0-py3-none-any.whl (6.2 kB)
Collecting eth-utils<2.0.0,>=1.9.5
Using cached eth_utils-1.10.0-py3-none-any.whl (24 kB)
Collecting hexbytes<1.0.0,>=0.1.0
Using cached hexbytes-0.3.0-py3-none-any.whl (6.4 kB)
Collecting ipfshttpclient==0.8.0a2
Using cached ipfshttpclient-0.8.0a2-py3-none-any.whl (82 kB)
Collecting jsonschema<5,>=3.2.0
Downloading jsonschema-4.17.0-py3-none-any.whl (83 kB)
---------------------------------------- 83.8/83.8 kB 669.1 kB/s eta 0:00:00
Collecting lru-dict<2.0.0,>=1.1.6
Using cached lru-dict-1.1.8.tar.gz (10 kB)
Preparing metadata (setup.py) ... done
Collecting protobuf==3.19.5
Using cached protobuf-3.19.5-py2.py3-none-any.whl (162 kB)
Collecting websockets<10,>=9.1
Using cached websockets-9.1.tar.gz (76 kB)
Preparing metadata (setup.py) ... done
Collecting pywin32>=223
Using cached pywin32-304-cp311-cp311-win_amd64.whl (12.1 MB)
Collecting multiaddr>=0.0.7
Using cached multiaddr-0.0.9-py2.py3-none-any.whl (16 kB)
Collecting attrs>=17.3.0
Using cached attrs-22.1.0-py2.py3-none-any.whl (58 kB)
Collecting multidict<7.0,>=4.5
Using cached multidict-6.0.2.tar.gz (50 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting async-timeout<5.0,>=4.0.0a3
Using cached async_timeout-4.0.2-py3-none-any.whl (5.8 kB)
Collecting yarl<2.0,>=1.0
Using cached yarl-1.8.1.tar.gz (172 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting frozenlist>=1.1.1
Using cached frozenlist-1.3.1.tar.gz (66 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting aiosignal>=1.1.2
Using cached aiosignal-1.2.0-py3-none-any.whl (8.2 kB)
Collecting parsimonious<0.9.0,>=0.8.0
Using cached parsimonious-0.8.1.tar.gz (45 kB)
Preparing metadata (setup.py) ... done
Collecting bitarray<3,>=1.2.1
Using cached bitarray-2.6.0.tar.gz (102 kB)
Preparing metadata (setup.py) ... done
Collecting eth-keyfile<0.6.0,>=0.5.0
Using cached eth_keyfile-0.5.1-py3-none-any.whl (8.3 kB)
Collecting eth-keys<0.4.0,>=0.3.4
Using cached eth_keys-0.3.4-py3-none-any.whl (21 kB)
Collecting rlp<3,>=1.0.0
Using cached rlp-2.0.1-py2.py3-none-any.whl (20 kB)
Collecting pycryptodome<4,>=3.6.6
Using cached pycryptodome-3.15.0-cp35-abi3-win_amd64.whl (1.9 MB)
Collecting eth-utils<2.0.0,>=1.9.5
Using cached eth_utils-1.9.5-py3-none-any.whl (23 kB)
Collecting cytoolz<1.0.0,>=0.10.1
Using cached cytoolz-0.12.0.tar.gz (502 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0
Using cached pyrsistent-0.19.1-py3-none-any.whl (57 kB)
Collecting toolz>=0.8.0
Using cached toolz-0.12.0-py3-none-any.whl (55 kB)
Collecting varint
Using cached varint-1.0.2.tar.gz (1.9 kB)
Preparing metadata (setup.py) ... done
Collecting six
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting base58
Using cached base58-2.1.1-py3-none-any.whl (5.6 kB)
Collecting netaddr
Using cached netaddr-0.8.0-py2.py3-none-any.whl (1.9 MB)
Building wheels for collected packages: cytoolz, frozenlist, multidict, yarl
Building wheel for cytoolz (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for cytoolz (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [55 lines of output]
[1/5] Cythonizing cytoolz/utils.pyx
[2/5] Cythonizing cytoolz/dicttoolz.pyx
[3/5] Cythonizing cytoolz/functoolz.pyx
[4/5] Cythonizing cytoolz/itertoolz.pyx
[5/5] Cythonizing cytoolz/recipes.pyx
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-311
creating build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\compatibility.py -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz_signatures.py -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz_version.py -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz_init_.py -> build\lib.win-amd64-cpython-311\cytoolz
creating build\lib.win-amd64-cpython-311\cytoolz\curried
copying cytoolz\curried\exceptions.py -> build\lib.win-amd64-cpython-311\cytoolz\curried
copying cytoolz\curried\operator.py -> build\lib.win-amd64-cpython-311\cytoolz\curried
copying cytoolz\curried_init_.py -> build\lib.win-amd64-cpython-311\cytoolz\curried
copying cytoolz\dicttoolz.pyx -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\functoolz.pyx -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\itertoolz.pyx -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\recipes.pyx -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\utils.pyx -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\cpython.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\dicttoolz.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\functoolz.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\itertoolz.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\recipes.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz\utils.pxd -> build\lib.win-amd64-cpython-311\cytoolz
copying cytoolz_init_.pxd -> build\lib.win-amd64-cpython-311\cytoolz
creating build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\dev_skip_test.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_compatibility.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_curried.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_curried_toolzlike.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_dev_skip_test.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_dicttoolz.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_docstrings.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_doctests.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_embedded_sigs.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_functoolz.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_inspect_args.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_itertoolz.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_none_safe.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_recipes.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_serialization.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_signatures.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_tlz.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
copying cytoolz\tests\test_utils.py -> build\lib.win-amd64-cpython-311\cytoolz\tests
UPDATING build\lib.win-amd64-cpython-311\cytoolz/_version.py
set build\lib.win-amd64-cpython-311\cytoolz/_version.py to '0.12.0'
running build_ext
building 'cytoolz.dicttoolz' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for cytoolz
Building wheel for frozenlist (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for frozenlist (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [33 lines of output]
*********************
* Accelerated build *
*********************
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-311
creating build\lib.win-amd64-cpython-311\frozenlist
copying frozenlist_init_.py -> build\lib.win-amd64-cpython-311\frozenlist
running egg_info
writing frozenlist.egg-info\PKG-INFO
writing dependency_links to frozenlist.egg-info\dependency_links.txt
writing top-level names to frozenlist.egg-info\top_level.txt
reading manifest file 'frozenlist.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '.pyc' found anywhere in distribution
warning: no previously-included files matching '.pyd' found anywhere in distribution
warning: no previously-included files matching '.so' found anywhere in distribution
warning: no previously-included files matching '.lib' found anywhere in distribution
warning: no previously-included files matching '.dll' found anywhere in distribution
warning: no previously-included files matching '.a' found anywhere in distribution
warning: no previously-included files matching '*.obj' found anywhere in distribution
warning: no previously-included files found matching 'frozenlist*.html'
no previously-included directories found matching 'docs_build'
adding license file 'LICENSE'
writing manifest file 'frozenlist.egg-info\SOURCES.txt'
copying frozenlist_init_.pyi -> build\lib.win-amd64-cpython-311\frozenlist
copying frozenlist_frozenlist.pyx -> build\lib.win-amd64-cpython-311\frozenlist
copying frozenlist\py.typed -> build\lib.win-amd64-cpython-311\frozenlist
running build_ext
building 'frozenlist._frozenlist' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for frozenlist
Building wheel for multidict (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for multidict (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [59 lines of output]
*********************
* Accelerated build *
*********************
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-311
creating build\lib.win-amd64-cpython-311\multidict
copying multidict_abc.py -> build\lib.win-amd64-cpython-311\multidict
copying multidict_compat.py -> build\lib.win-amd64-cpython-311\multidict
copying multidict_multidict_base.py -> build\lib.win-amd64-cpython-311\multidict
copying multidict_multidict_py.py -> build\lib.win-amd64-cpython-311\multidict
copying multidict_init_.py -> build\lib.win-amd64-cpython-311\multidict
running egg_info
writing multidict.egg-info\PKG-INFO
writing dependency_links to multidict.egg-info\dependency_links.txt
writing top-level names to multidict.egg-info\top_level.txt
reading manifest file 'multidict.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files found matching 'multidict_multidict.html'
warning: no previously-included files found matching 'multidict*.so'
warning: no previously-included files found matching 'multidict*.pyd'
warning: no previously-included files found matching 'multidict*.pyd'
no previously-included directories found matching 'docs_build'
adding license file 'LICENSE'
writing manifest file 'multidict.egg-info\SOURCES.txt'
C:\Users\user\AppData\Local\Temp\pip-build-env-rx5z3tzo\overlay\Lib\site-packages\setuptools\command\build_py.py:202: SetuptoolsDeprecationWarning:     Installing 'multidict._multilib' as data is deprecated, please list it in packages.
!!
      ############################
      # Package would be ignored #
      ############################
      Python recognizes 'multidict._multilib' as an importable package,
      but it is not listed in the `packages` configuration of setuptools.

      'multidict._multilib' has been automatically added to the distribution only
      because it may contain data files, but this behavior is likely to change
      in future versions of setuptools (and therefore is considered deprecated).

      Please make sure that 'multidict._multilib' is included as a package by using
      the `packages` configuration field or the proper discovery methods
      (for example by using `find_namespace_packages(...)`/`find_namespace:`
      instead of `find_packages(...)`/`find:`).

      You can read more about "package discovery" and "data files" on setuptools
      documentation page.

  !!

    check.warn(importable)
  copying multidict\__init__.pyi -> build\lib.win-amd64-cpython-311\multidict
  copying multidict\py.typed -> build\lib.win-amd64-cpython-311\multidict
  running build_ext
  building 'multidict._multidict' extension
  error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for multidict
Building wheel for yarl (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for yarl (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [37 lines of output]
C:\Users\user\AppData\Local\Temp\pip-build-env-5lrpf28p\overlay\Lib\site-packages\setuptools\config\setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
warnings.warn(msg, warning_class)
**********************
* Accelerated build *
**********************
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-311
creating build\lib.win-amd64-cpython-311\yarl
copying yarl_quoting.py -> build\lib.win-amd64-cpython-311\yarl
copying yarl_quoting_py.py -> build\lib.win-amd64-cpython-311\yarl
copying yarl_url.py -> build\lib.win-amd64-cpython-311\yarl
copying yarl_init_.py -> build\lib.win-amd64-cpython-311\yarl
running egg_info
writing yarl.egg-info\PKG-INFO
writing dependency_links to yarl.egg-info\dependency_links.txt
writing requirements to yarl.egg-info\requires.txt
writing top-level names to yarl.egg-info\top_level.txt
reading manifest file 'yarl.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '.pyc' found anywhere in distribution
warning: no previously-included files matching '.cache' found anywhere in distribution
warning: no previously-included files found matching 'yarl*.html'
warning: no previously-included files found matching 'yarl*.so'
warning: no previously-included files found matching 'yarl*.pyd'
no previously-included directories found matching 'docs_build'
adding license file 'LICENSE'
writing manifest file 'yarl.egg-info\SOURCES.txt'
copying yarl_init_.pyi -> build\lib.win-amd64-cpython-311\yarl
copying yarl_quoting_c.pyi -> build\lib.win-amd64-cpython-311\yarl
copying yarl_quoting_c.pyx -> build\lib.win-amd64-cpython-311\yarl
copying yarl\py.typed -> build\lib.win-amd64-cpython-311\yarl
running build_ext
building 'yarl._quoting_c' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for yarl
Failed to build cytoolz frozenlist multidict yarl
ERROR: Could not build wheels for cytoolz, frozenlist, multidict, yarl, which is required to install pyproject.toml-based projects

hey there, this error seems to be related to your environment missing necessary items to build certain python dependencies that are powered by C under the hood


test: drivers.flash.common.default: fails on frdm and ite.

Describe the bug
The tests/drivers/flash/common/drivers.flash.common.default fails on frdm and ite board.
To Reproduce
Steps to reproduce the behavior:

cd zephyr workspace
source zephyr-env.sh

twister --device-testing --hardware-map ./map_frdm.yml -p frmd_k64f -T tests/drivers/flash/common/drivers.flash.common.default -vv

twister --device-testing --hardware-map ./map_ite.yml -p it8xxx2_evb -T tests/drivers/flash/common/drivers.flash.common.default -vv

Impact
annoyance
Logs and console output
<path_to>/twister-out/frdm_k64f/tests/drivers/flash/common/drivers.flash.common.default/handler.log
*** Booting Zephyr OS build v3.7.0-1436-g4c16ec1fba56 ***
Running TESTSUITE flash_driver
===================================================================
Test will run on device flash-controller@40020000
START - test_flash_erase
PASS - test_flash_erase in 0.012 seconds
===================================================================
START - test_flash_fill
PASS - test_flash_fill in 0.048 seconds
===================================================================
START - test_flash_flatten
PASS - test_flash_flatten in 0.050 seconds
===================================================================
START - test_flash_page_layout
start_offset=0xe2000    size=4096       index=226
page_count=256
PASS - test_flash_page_layout in 0.006 seconds
===================================================================
START - test_negative_flash_erase
TEST_FLASH_START = 0x0
TEST_FLASH_SIZE = 0x100000
PASS - test_negative_flash_erase in 0.005 seconds
===================================================================
START - test_negative_flash_fill
E: Negative offset not allowed
E: Incorrect size or offset alignment, expected 8
PASS - test_negative_flash_fill in 0.008 seconds
===================================================================
START - test_negative_flash_flatten
PASS - test_negative_flash_flatten in 0.001 seconds
===================================================================
START - test_negative_flash_read
E: ***** BUS FAULT *****
E:   Precise data bus error
E:   BFAR Address: 0xffffffff
E: r0/a1:  0x200009f0  r1/a2:  0xffffffff  r2/a3:  0x000001ff
E: r3/a4:  0x200009ef r12/ip:  0x00005b21 r14/lr:  0x00005b33
E:  xpsr:  0xa1000000
E: Faulting instruction address (r15/pc): 0x000063ba
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20000058 (test_negative_flash_read)
E: Halting system

<path_to>/twister-out/it8xxx2_evb/tests/drivers/flash/common/drivers.flash.common.default/handler.log
***** delaying boot 500ms (per build configuration) *****
*** Booting Zephyr OS build v3.7.0-1394-g0a7908588c75 (delayed boot 500ms) ***
Running TESTSUITE flash_driver
===================================================================
Test will run on device flash-controller@f01000
START - test_flash_erase
PASS - test_flash_erase in 0.068 seconds
===================================================================
START - test_flash_fill
PASS - test_flash_fill in 0.110 seconds
===================================================================
START - test_flash_flatten
PASS - test_flash_flatten in 0.123 seconds
===================================================================
START - test_flash_page_layout
start_offset=0x60000	size=4096	index=96
page_count=256
PASS - test_flash_page_layout in 0.006 seconds
===================================================================
START - test_negative_flash_erase
TEST_FLASH_START = 0x80000000
TEST_FLASH_SIZE = 0x100000
PASS - test_negative_flash_erase in 0.006 seconds
===================================================================
START - test_negative_flash_fill
E: Incorrect size or offset alignment, expected 4
E: Negative offset not allowed
E: Incorrect size or offset alignment, expected 4
PASS - test_negative_flash_fill in 0.013 seconds
===================================================================
START - test_negative_flash_flatten
PASS - test_negative_flash_flatten in 0.001 seconds
===================================================================
START - test_negative_flash_read
Assertion failed at WEST_TOPDIR/<path_to>tests/drivers/flash/common/src/main.c:427: flash_driver_test_negative_flash_read: (rc < 0 is false)
Invalid use of flash_read returned 0
FAIL - test_negative_flash_read in 0.021 seconds
===================================================================
START - test_negative_flash_write
ASSERTION FAIL [!terminate] @ <path_to>/kernel/sched.c:493
aborted _current back from dead
E:      a0: 00000004    t0: 00000000
E:      a1: 000001ed    t1: 00000008
E:      a2: 00000000    t2: aaaaaaaa
E:      a3: 80100958    t3: 00000010
E:      a4: 00000000    t4: 00000003
E:      a5: 80100e80    t5: 00000000
E:      a6: 00000000    t6: 00000010
E:      a7: 0000002d
E:      sp: 80101840
E:      ra: 8000636e
E:    mepc: 80001e2c
E: mstatus: 00001880
E:
E:      s0: 80100e80    s6: 00000000
E:      s1: 80100000    s7: 00000000
E:      s2: 00001888    s8: 00000000
E:      s3: 00000001    s9: 00000000
E:      s4: 80100864   s10: 00000000
E:      s5: 80100000   s11: 00000000
E:
E: call trace:
E:
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x80100958 (main)
E: Halting system

Environment:

OS: Linux
Toolchain Zephyr_sdk: zephyr-sdk-0.16.8
Zephyr version: v3.7.0-1394-g0a7908588c75

Result of bisect:
1a48a0174fd519f08703c1e1c0658c545bab3372 is the first bad commit
commit 1a48a0174fd519f08703c1e1c0658c545bab3372
Author: Sebastian Głąb<EMAIL_ADDRESS>Date:   Wed Jul 3 09:04:49 2024 +0200

    tests: drivers: flash: common: Increase test coverage

    Add functional test for flash_erase().
    Add negative tests for flash_read(), flas_write(), flash_erase(),
    flash_fill() and flash_flatten().
    Add functional test for flash page layout.

    Signed-off-by: Sebastian Głąb<EMAIL_ADDRESS>
 tests/drivers/flash/common/src/main.c    | 282 +++++++++++++++++++++++++++++++
 tests/drivers/flash/common/testcase.yaml |   4 +-
 2 files changed, 285 insertions(+), 1 deletion(-)

@nordic-segl can you take a look ?

test_negative_flash_read checks return value from flash_read() when:

memory address is (TEST_FLASH_START - 1);
memory address is (TEST_FLASH_START + TEST_FLASH_SIZE);
length of data to be read is bigger than flash size;
length of data to be read is 0;

I see that on frdm_k64f:
TEST_FLASH_START = 0x0
TEST_FLASH_SIZE = 0x100000
There is BUS ERROR when flash_read() tries to read from (TEST_FLASH_START - 1) = 0xffffffff.
It's not trivial for 'generic' driver to know flash boundaries for the target selected for compilation.
I can add skip in this test when flash starts at 0x0. For example:
	if (TEST_FLASH_START == 0) {
		/* Skip this test because some drivers are unable to detect that address 0xffffffff is invalid. */
		ztest_test_skip();
	}

However, I don't know what will happen in next three checks (see points 2. - 4. above).
I see that on it8xxx2_evb:
TEST_FLASH_START = 0x80000000
TEST_FLASH_SIZE = 0x100000
test_negative_flash_read is FAILED because reading from 0x7fffffff was successful.
test_negative_flash_write resulted in Kernel panic when flash_write() was called with invalid memory address.
On both targets flash_erase(), flash_fill(), flash_flatten() were able to detect invalid addresses / sizes.
While, issue occurs for flash_read() and flash_write() only.
Issue is observed at run time. Since, I don't have these boards on my desk, it will be difficult for me to investigate.
It seems that driver lacks check for memory boundary in read/write functions.
However, there is no clear statement that such check must be done. API says that return value is 0 on success, negative errno code on fail.
Let me know your opinion. Can this be handled by adding more checks in the driver? Or, negative tests shall be removed as they require checking input values by the read/write functions. Which is NOT clearly stated by API as mandatory.

Hi I'm also seeing failures on mr_canhubk3 board.
test_negative_flash_erase pass, but the parameter errors detected by the driver are actually different than the one the test was attempting to check (address out of range). And I believe most of the NOR flash drivers will present a similar behavior. A similar situation happens with test_negative_flash_flatten.
START - test_negative_flash_erase
TEST_FLASH_START = 0x400000
TEST_FLASH_SIZE = 0x3f4000
E: addr 4194303 is not sector-aligned          -> /* Check error returned when erasing memory at wrong address (too low) */
E: size 512 is not a multiple of sectors       -> /* Check error returned when erasing memory at wrong address (too high) */
E: size 4145153 is not a multiple of sectors   -> /* Check error returned when erasing to large chunk of memory */
 PASS - test_negative_flash_erase in 0.017 seconds

 START - test_negative_flash_flatten
E: addr 4194303 is not sector-aligned           -> /* Check error returned when flatten memory at wrong address (too low) */
E: size 512 is not a multiple of sectors        -> /* Check error returned when flatten memory at wrong address (too high) */
E: size 4145153 is not a multiple of sectors    -> /* Check error returned when flatten to large chunk of memory */
 PASS - test_negative_flash_flatten in 0.012 seconds

test_negative_flash_fill fails because the offset=0x003F_FFFF / size=32 of the flash_write() being called by flash_fill(), falls within the memory device which has size of 0x0080_0000. The issue here is that the negative tests are taking the TEST_FLASH_START/TEST_FLASH_SIZE from zephyr,flash chosen, which in in my target is the internal SoC flash, but the flash device under test containing the TEST_AREA is a different external flash. The same applies for test_negative_flash_read and test_negative_flash_write
START - test_negative_flash_fill

    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/flash/common/src/main.c:369: flash_driver_test_negative_flash_fill: (rc < 0 is false)
Invalid use of flash_fill returned 0
 FAIL - test_negative_flash_fill in 0.018 seconds
===================================================================
START - test_negative_flash_read

    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/flash/common/src/main.c:427: flash_driver_test_negative_flash_read: (rc < 0 is false)
Invalid use of flash_read returned 0
 FAIL - test_negative_flash_read in 0.017 seconds
===================================================================
START - test_negative_flash_write

    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/flash/common/src/main.c:456: flash_driver_test_negative_flash_write: (rc < 0 is false)
Invalid use of flash_write returned 0
 FAIL - test_negative_flash_write in 0.017 seconds

I will move negative tests to a separate test and add filter for platforms. Many vendors are affected.
Taking Flash start address and it's size from zephyr,flash doesn't work for all targets.

I will move negative tests to a separate test and add filter for platforms. Many vendors are affected.

ok, that makes sense! Thanks

First attempt to fix this issue is here:
https://github.com/zephyrproject-rtos/zephyr/pull/77380

Issue seen on STM32 as well

Fix is ready:
https://github.com/zephyrproject-rtos/zephyr/pull/77380
Please, do review. "At least 2 approving reviews are required by reviewers with write access."

Fix is ready: #77380
Please, do review. "At least 2 approving reviews are required by reviewers with write access."

Let me verify this fix form frdm and ite perspective.

ITE passes with this fix.
twister --device-testing --hardware-map <path_to>/ite.yaml -T tests/drivers/flash/common/ -v
INFO    - Using Ninja..
INFO    - Zephyr version: v3.6.0-9205-gaf09fcff7d19
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report <path_to>/zephyrproject/zephyr/twister-out/testplan.json

Device testing on:

| Platform    | ID       | Serial device   |
|-------------|----------|-----------------|
| it8xxx2_evb | A50285BI | /dev/ttyUSB0    |

INFO    - JOBS: 4
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - 14/14 it8xxx2_evb               tests/drivers/flash/common/drivers.flash.common.default PASSED (device: A50285BI, 7.187s)

INFO    - 14 test scenarios (14 test instances) selected, 13 configurations skipped (13 by static filter, 0 at runtime).
INFO    - 1 of 14 test configurations passed (100.00%), 0 failed, 0 errored, 13 skipped with 0 warnings in 25.95 seconds
INFO    - In total 5 test cases were executed, 65 skipped on 1 out of total 1 platforms (100.00%)
INFO    - 1 test configurations executed on platforms, 0 test configurations were only built.

Hardware distribution summary:

| Board       | ID       |   Counter |   Failures |
|-------------|----------|-----------|------------|
| it8xxx2_evb | A50285BI |         1 |          0 |
INFO    - Saving reports...
INFO    - Writing JSON report <path_to>zephyrproject/zephyr/twister-out/twister.json
INFO    - Writing xunit report <path_to>/zephyrproject/zephyr/twister-out/twister.xml...
INFO    - Writing xunit re

Regarding:
frdm_k64f
twister --device-testing --hardware-map ../../frdm_map.yaml -T tests/drivers/flash/common/ -vv
twister throws. FAILED RunID mismatch.

It looks like a Twister issue. Does it happen every time?
I see that test was compiled with following RUNID=78a9c8383f24bf2eaf670dbb87abf08d
DEBUG   - Calling cmake: /usr/bin/cmake -B<path_to>/zephyrproject/zephyr/twister-out/frdm_k64f/tests/drivers/flash/common/drivers.flash.common.default -DTC_RUNID=78a9c8383f24bf2eaf670dbb87abf08d -DCONFIG_COMPILER_WARNINGS_AS_ERRORS=y -DEXTRA_GEN_DEFINES_ARGS=--edtlib-Werror -GNinja -S<path_to>/zephyrproject/zephyr/tests/drivers/flash/common -DBOARD=frdm_k64f -DMODULES=dts,kconfig -P<path_to>/zephyrproject/zephyr/cmake/package_helper.cmake

while console output is from RUNID=3a609a6bb41743f92519b53d0fcd0bd7
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: RunID: 3a609a6bb41743f92519b53d0fcd0bd7
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL

As if Twister parsed output from before device was flashed.

You're right, My setup issue. I've tested in on two different boards and is working properly.

DEBUG   - DEVICE: START - test_read_unaligned_address
DEBUG   - DEVICE: PASS - test_read_unaligned_address in 0.015 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: TESTSUITE flash_driver succeeded
DEBUG   - DEVICE:
DEBUG   - DEVICE: ------ TESTSUITE SUMMARY START ------
DEBUG   - DEVICE:
DEBUG   - DEVICE: SUITE PASS - 100.00% [flash_driver]: pass = 5, fail = 0, skip = 0, total = 5 duration = 0.131 seconds
DEBUG   - DEVICE: - PASS - [flash_driver.test_flash_erase] duration = 0.013 seconds
DEBUG   - DEVICE: - PASS - [flash_driver.test_flash_fill] duration = 0.047 seconds
DEBUG   - DEVICE: - PASS - [flash_driver.test_flash_flatten] duration = 0.050 seconds
DEBUG   - DEVICE: - PASS - [flash_driver.test_flash_page_layout] duration = 0.006 seconds
DEBUG   - DEVICE: - PASS - [flash_driver.test_read_unaligned_address] duration = 0.015 seconds
DEBUG   - DEVICE:
DEBUG   - DEVICE: ------ TESTSUITE SUMMARY END ------
DEBUG   - DEVICE:
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: RunID: 0d9c445fa65192ceedf1c3a6669fee91
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - Expected suite names:['flash_driver']
DEBUG   - Detected suite names:['flash_driver', 'flash_driver', 'flash_driver', 'flash_driver', 'flash_driver', 'flash_driver']
DEBUG   - Release DUT:frdm_k64f, Id:02400b0177384e45002070016f01001ac401000197969900, counter:1, failures:0
DEBUG   - run status: frdm_k64f/tests/drivers/flash/common/drivers.flash.common.default passed
INFO    - 14/14 frdm_k64f                 tests/drivers/flash/common/drivers.flash.common.default PASSED (device: 02400b0177384e45002070016f01001ac401000197969900, 4.631s)

Fix was merged. Please verify whether issue is still observed.

No reproductive on ITE and FRDM. I close it.


Create proofs for Cairo

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#899  👈 (View in Graphite)
#897
#852 : 1 other dependent PR (#856 )
#832
#831
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Codecov Report
Attention: Patch coverage is 79.09091% with 23 lines in your changes missing coverage. Please review.

Project coverage is 90.79%. Comparing base (af9250e) to head (90ff535).
Report is 8 commits behind head on dev.

Files with missing lines
Patch %
Lines

crates/prover/src/core/fri.rs
78.89%
23 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #899      +/-   ##
==========================================
- Coverage   91.77%   90.79%   -0.99%
==========================================
  Files          93       93
  Lines       13282    13256      -26
  Branches    13282    13256      -26
==========================================
- Hits        12190    12036     -154
- Misses        979     1107     +128
  Partials      113      113

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


Add missing install rules for jar and jni targets

Could somone confirm the naming convention jxl_jni_wrapper.jar, I would have expected org.jpeg.jpegxl.jar, right ?

Lets switch to org.jpeg.jpegxl.jar.


buildRustCrate: overridable stdenv, and propagatedBuildInputs

Motivation for this change
These changes are both necessary to build crate nettle-sys.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@GrahamcOfBorg build buildRustCrateTests
@GrahamcOfBorg build cargo-vendor

I started rebasing this onto master and also fixing a few nitpicks that I have.
@P-E-Meunier do you have the exact list of packages that you added? Which of these (besides nettle) required the overrides? I am also working on adding a few tests for the override feature so we can verify that things work (now and in the future).

Hi! I don't think there's anything really requiring work besides nettle, but I noticed a few problems when I started packaging the latest Pijul, due to the fact that Rust doesn't generate the same Cargo.lock for all featuresets (due to optional dependencies). I've published Carnix 0.10.1 onto crates.io last week, but haven't yet had the time to package it to nixpkgs yet. Also, I believe we need a giant common Cargo.lock in nixpkgs itself, which could be parsed more easily, and from which we could regenerate the nix expression.

the HEAD of my modified branch is at a89441cd584ff459469f7c75b0e02d32b57949e. I'm leaving PR untouched for now.
We really need a mechanism to keep the crates.io package list smaller and thus should document  / automate the process on how to generate the current list. If packages drop out of nixpkgs and those dependencies are no longer used we shouldn't carry it on forever.

Regarding requiring a giant Cargo.lock:
Not sure if you saw my idea in one of the previous carnix bumps that we could just iterate through all the packages that we know are using buildRustCrate (on a high-level, not all the crates-io.nix packages) and then re-generate the index with those.
I hacked a very simple & error proune PoC https://gist.github.com/andir/c637c78450e6ae7815d98e7fa08d45dd
We could probably eliminate the getSource hack there if we would provide the Cargo.toml and Cargo.lock files as additional outputs of each of the crates. We would then just need the part where we iterate (and probably harder list) all the relevant packages.

Heya !
It seems this got out of sync with master - is anyone looking into this ?:)


HHH-11904  EnumExplicitTypeTest test assert fails on mariadb clusters

https://hibernate.atlassian.net/browse/HHH-11904

Applied upstream, thanks.
For the 5.1 branch, @gbadner might want to integrate it.


Fix detection of ARMv7 and ARM64 CPU features on FreeBSD

OpenSSL assumes AT_HWCAP = 16 (as on Linux), but on FreeBSD AT_HWCAP = 25
OpenSSL calls elf_auxv_info() with AT_CANARY which returns ENOENT
resulting in all ARM acceleration features being disabled.
CLA: trivial
Checklist

Would it be preferable to instead do something like:
#ifndef AT_HWCAP
#  define AT_HWCAP 16
#endif

And then use AT_HWCAP to avoid the FreeBSD specific ifdefs?

Would it be preferable to instead do something like:
#ifndef AT_HWCAP
#  define AT_HWCAP 16
#endif

And then use AT_HWCAP to avoid the FreeBSD specific ifdefs?

Yeah, that would look better to me.

I've opened a different pull request for the alternative version, I agree it is cleaner: https://github.com/openssl/openssl/pull/17082


Doesn't work with .Net Blazor

This is probably an edge case. But when I integrate this library and use Blazor data binding, once I hit the separator character, e.g. comma, the entire  element is just gone. Tried without data binding it works though.

Since I've never tried Blazor I don't know how to debug it, could you please provide a demo to reproduce the problem?

I would if I could. It's not easy to provide a Blazor demo though. Here I'm attaching 2 screenshots in the hope of helping locate the issue.

Here I've got 2 input textboxes. The upper one works fine but once I hit comma on the second one both textboxes are gone. Something I observe is that the size, height especially, changes. Maybe this is the reason why they don't show anymore.

Please try the latest version, let me know if it works or not

Please try the latest version, let me know if it works or not

Glad to see that it fixes the issue! One small issue though, for the re-initialization case, is that after the new tag gets added, the input textbox lost focus automatically, while in normal cases I can keep typing and adding tags constantly.

Reinitializing means deleting the previous element and creating a new element. As a result, the focus state will be lost automatically.
I don't understand why Blazor has to reinitialize the input.

Well, I can't observe the Blazor reinitialization explicitly, since the resulting input element has nothing different than it is in the Blazor source code file. It's the tag library that hides the original input element and adds a couple of new ones.
Anyway, after a second thought, since the tag library hides the original input there's no point to attach Blazor's data binding attributes to it. So using it as a regular input element is fine and I need to call the getValues method explicitly and set it to the bound model before POSTing.


BAAS (web) interface

Users must be able to control the machines (for example, turning it off and on) remotely. Some kind of interface for this is necessary.

Moved to a separate repository


Pagination

The list of product on 'Store' page should be limited and have button(s) to go the the product list if the list is too long.


Sharing work on COVID19-related tutorials

If you're interested in writing/contributing to tutorials related to https://covid19.galaxyproject.org/, feel free to add your name and the kind of tutorial you would like to contribute here.
The idea is to come up with a bunch of separate tutorials teaching people the various analysis techniques employed on the covid19 site using some of that same input data.
For a start I'm already adding myself and a few people from Galaxy EU. Note: ticked off boxes do NOT mean that you cannot contribute to these topics. They only indicate that at least one person is volunteering to do work on them. Double assignments are welcome :)

[x] Data preprocessing for Genomic analyses
@wm75

[x] nCov2 intra-sample variant calling
@wm75

[x] Assembly of nCov2 short reads
@khanteymoori

[ ] S-gene/protein analysis

[ ] MRCA

[ ] Evolutionary analysis / Recombination analysis

[x] Cheminformatics
@simonbray

Made a start on the docking tutorial here: https://github.com/galaxyproject/training-material/pull/1864

@simonbray merged and online here: https://training.galaxyproject.org/training-material/topics/computational-chemistry/tutorials/covid19-docking/tutorial.html

Preprocessing and Assembly now covered by https://training.galaxyproject.org/training-material/topics/assembly/tutorials/assembly-with-preprocessing/tutorial.html

during running Protein-ligand docking tutorial, using the same examples but at this function always have an error  (Search ChEMBL database) the error is :
0.00 USD
This job requested 1 cores and 6.0 Gb. Given this, the smallest EC2 machine we could find is m3.large (7.5 GB / 2 vCPUs / Intel Xeon E5-2670 v2 (Ivy Bridge/Sandy Bridge)). That instance is priced at 0.158 USD/hour.
what shall i do?

@esraaa, can you submit a bug report? You can see an insect symbol on the errored job for this.
Will reply to you there, this page is for a different discussion.

ok i will,sorry for that

From: Simon Bray<EMAIL_ADDRESS>Sent: Friday, April 24, 2020 2:12 PM
To: galaxyproject/training-material<EMAIL_ADDRESS>Cc: esraa<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [galaxyproject/training-material] Sharing work on COVID19-related tutorials (#1863)
@esraaahttps://github.com/esraaa, can you submit a bug report? You can see an insect symbol on the errored job for this.
Will reply to you there, this page is for a different discussion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/galaxyproject/training-material/issues/1863#issuecomment-618973013, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABC46NH7EM2NM6MQOAXYU4DROF64LANCNFSM4LTOOCVQ.


[Bug]: Code block automatically add a blank line, and Copy button should not copy the line number

Version
System:
    OS: macOS 14.1.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 154.03 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 119.0.6045.159
    Safari: 17.1
  npmPackages:
    rspress: ^1.7.0 => 1.7.0

Details
Codebase: https://github.com/recallwei/web-dev-handbook/blob/main/docs/linux/certbot.md
After Upgrade to v.1.7.0,
In my .md:
```bash
dnf install -y epel-release
dnf install -y certbot python3-certbot-nginx
```

But with an extra blank line:

And try to copy the code block, the result below contains line number:
1dnf install -y epel-release
2dnf install -y certbot python3-certbot-nginx
3

Reproduce link
https://web-dev.brucesong.xyz/linux/certbot.html
Reproduce Steps
Add a code block.

Thanks for feedback. I will fix it right away.

@recallwei v1.7.1 has fixed


How to click on a nested element

Hello, it's me again :)
class Todo extends Component {
  render() {
    return (

 console.log('div clicked')}>
        {this.props.name}
        <button onClick={() => console.log('button clicked')}>Finish it</button>

    );
  }
}

class TodoList extends Component {
  render() {
    let list = [
      { id: 42, name: 'foo' },
      { id: 43, name: 'bar' }
    ];

    return (

        {list.map(item => {
          return <Todo key={item.id} {...item} />;
        })}

    );
  }
}
expect(
  TestUtils.renderIntoDocument(<TodoList />),
  'with event click', 'on', <Todo id={42} ><button/></Todo>
);

Basic todo list example, but instead of clicking the item, you have to click a button. I want to click on the button for a specific item, therefore I wrap button in a Todo with id. The problem is that this clicks the parent tag of the Todo, the div, and not the button. I've also tried different variations of 'queried for', <Todo />, but that doesn't let me click anything afterwards

Using the full renderer, this should be possible with queried for (note: not with the shallow renderer, yet)
However, I've just tried it, and you're right, it doesn't work.  I see the issue, should have a fix out shortly.

Fixed in 3.1.2.
You should now be able to do
expect(component, 'queried for', <Todo id={42} />,
    'with event click', 'on', <button />,
    'to have rendered',
    <Todo>foo</Todo>);

Let me know if that works now :)

Works perfectly, thanks a bunch!


Prebuilt extension experiment

Test out using prebuilt extensions. This still has a handful of issues, but it almost kind of works.
TODO:

[x] launcher:create duplicate command error (wrapped call in try catch in the meantime)
[x] not all styles are loading properly
[x] seems like runtime image metadata isn't loading

both the launcher and metadata issues seem to stem from installing elyra in editable mode. When doing so jupyterlab doesn't pick up on things in etc/config, maybe a python person would know more
EDIT: this seems to be a limitation of the cookie-cutter jupyterlab extension as well
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Closing this now that #2447 is open


Cannot return header fields with dash

The workflow definition does not allow me to access header fields that contain a dash, like X-B3-Traceid. Workflow execution fails with parse error: Invalid literal at line 1, column 7
My workflow:
apiVersion: 1
output: ReturnTraceId
tasks:
  ReturnTraceId:
    run: compose
    inputs:
      invocationId: "{$.Invocation.Id}"
      traceId: "{$.Invocation.Inputs.headers.X-B3-Traceid}"

Workflow validation succeeds.
This is the output of $.Invocation, so the $.Invocation.Inputs.headers.X-B3-Traceid field exists.
{
    "CreatedAt":<PHONE_NUMBER>697262000,
    "Id": "wi-7181aaf1-1ece-4de1-9b8b-0d8c0d70fb25",
    "Inputs": {
      "body": {
         ...
      },
      "default": {
      },
      "headers": {
        "Accept": "*/*",
        "Accept-Encoding": "gzip",
        "Connection": "close",
        "Content-Length": "132",
        "Content-Type": "application/json",
        "User-Agent": "curl/7.54.0",
        "X-B3-Sampled": "1",
        "X-B3-Spanid": "7d0a3b5cf1043d11",
        "X-B3-Traceid": "70d09604e9f38942ad351354bef2be5c"
        ...
      },
      "method": "POST",
      "query": {}
    }
}

Hi @sebastianroesch - thanks for raising the issue. This might be a 'bug' in the javascript expression evaluator: it is an invalid field name in javascript. $.Invocation.Inputs.headers['X-B3-Traceid'] should work.
Regardless, it is indeed something that we should catch earlier on in validation 👍

$.Invocation.Inputs.headers['X-B3-Traceid'] works for me, thank you!


Stepper colors not always correct

When I start a new application and arrive at Informatie over de onderzoeker the stepper circles are colored in an unexpected way:
First circle Basisgegevens is green (expected)
Next circle Onderzoeker is yellow (expected, current page, no information given yet)
Next circle Andere onderzoekers is green (unexpected, not even seen this page); should be yellow I suppose.
Next circle Financiering is yellow (expected)
Next circle Onderzoeksdoel is yellow (expected)
Next bigger circle WMO is green (unexpected, not even seen this page); should be grey I suppose
Other circles are grey (expected)
Something similar happens if I arrive at Eén of meerdere trajecten?:

Basisgegevens is yellow (unexpected, every field already filled in); should be green,
2 WMO is green (expected)
3 Trajecten is yellow (expected)
Traject afronding is yellow (expected)
4 Documenten is grey (expected)
5 Data management is yellow (unexpected); should be grey
6 Indienen is green (unexpected); should be grey

Not sure if this occurs more often, but I'll keep an eye on it.
Do I need to add other occurrences to this issue?

In addition, here "Ontwerp" is green but should be yellow (form validation works correctly though):


Fix DB executor warning

Before this change, the following warning was constantly spammed in my HA
development environment:
2022-07-11 20:15:19.933 WARNING (SyncWorker_6) [homeassistant.helpers.frame] Detected code that accesses the database without the database executor; Use homeassistant.components.recorder.get_instance(hass).async_add_executor_job() for faster database operations. Please report this issue.

Great 👍


Future Multiple Client/Transport Support

Hello,
I was just curious if there are any plans for eRPC to support multiple clients and/or transports in the future.
Looking at previous posts (#52), I see that a workaround is suggested but it is not clear whether it will cause other problems.
Thank you in advance for the help!

Hello @ramlco , supporting multiple clients and providing such examples is on the todo list but due to other work priorities this is not going to be done soon, unfortunately.

what about a router system which will be able to handle more than one client and more than one transport? The concept is similar in nature to a message router I used to work on which could transfer messages between devices in the system whether they were running on the same processor, directly connected to another, or connected between different transports.
Let's start with this arrangement:
MCU A <---UART---> MCU B
One transport is easy enough, and bidirectional client/server is taken care of by the transport arbitrator which looks at the message type (invocation / one way: pass it to the server; otherwise, process it in the client)
MCU A has WiFi, Bluetooth, CAN. MCU B has USB, another CAN. One or the other might have an audio DAC attached. Some of the IO pins that need to be twiddled might be on the other end. They use eRPC to pass information back and forth to each other so the application code doesn't need to care which core it's running on
Would be great to use the same idea to provide RPC for a desktop or mobile app client over those other transports so you have one single source of truth: the IDL. Imagine some Python script running on the PC to assist in automated testing, debugging, or development
the tricky part becomes how do you get the WiFi client able to call something on MCU B?
Well, if you expand the arbitrator approach a little bit, it could handle such a situation where the thing that receives it is not directly able to service it, but it knows who can
I think an eRPC "server hello" message could be created to say what is its server name and what are the service IDs it serves. Maybe there is a client hello, as well.
The router would have a list of registered transports, a list of servers, and the service IDs those servers have.
After the startup "hello", MCU A has the following list:
Transports:

UART (ID 1)

Server 1: self

Service: Net (service ID 1)
Service: CAN A (service ID 2)

Server 2: MCU B

Service: USB (service ID 3)
Service: Audio (service ID 4)
Service: CAN B (service ID 5)

TCP (ID 2)

Server 1...

Bluetooth (ID 3)

Server 1...

CAN (ID 4)

Server 1...

etc.

A client connects over TCP and requests something from the USB drive. MCU A knows that service 3 is available on server 2, over UART, so it forwards the message to that transport. (Perhaps there is a transport ID and client ID added to the header so that when the response comes back, the router knows which TCP client to send it back to)
This assumes each service can only be served by one device in the system, and you don't mind all services being available to all clients
Indirectly routing may be easy enough as well. Let each server post the services it has available across all its transports. Then if a transport is running over CAN on MCU B, and an external device connects with a server that has a "diagnostic" service ID 6, then MCU B posts back to MCU A that it not only handles 3, 4, and 5, but now 6 as well. MCU B then has this routing list:

UART (ID 1)

Server 1: self

Service: USB (service ID 3)
Service: Audio (service ID 4)
Service: CAN B (service ID 5)

Server 2: MCU A

Service: Net (service ID 1)
Service: CAN A (service ID 2)

CAN (ID 4)

Server 1: self
Server 3: diagnostic

Service: diagnostic (service ID 6)

etc

And MCU A now has this routing list:

UART (ID 1)

Server 1: self

Service: Net (service ID 1)
Service: CAN A (service ID 2)

Server 2: MCU B

Service: USB (service ID 3)
Service: Audio (service ID 4)
Service: CAN B (service ID 5)
Service: diagnostic (service ID 6)

TCP (ID 2)

Server 1...

etc.

Could get a little foggy as to how the multiple bounces works, so maybe at first it only supports one degree of Kevin Bacon
Hope at least some of that was clear enough. I love me some pipe dreams.


(1369) Use new task endpoint

The /tasks/{id} endpoint now returns allocatable users, negating the need for us to do this stuff on the frontend. Frustratingly, the contract tests didn't pick this up, so we may have to go back to the drawing board on these 😢

 Update assessment allocations


The Run/Debug console

Type: Bug
I have an html file I'm working on but if I try to run it, it doesnt work and the Run/ Debug console shows a rectangle divided vertically into two 2x8 with a triangle in the 2 and some other options in the other box.
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.78GB (1.06GB free)

Process Argv
--crash-reporter-id 08ab541e-9f61-49c2-bb8a-713f155c30cf

Screen Reader
no

VM
0%

Extensions (24)

Extension
Author (truncated)
Version

vscode-chatgpt
gen
4.0.2

chatgpt-vscode
gen
0.0.6

isort
ms-
2023.9.10861010

python
ms-
2023.6.0

vscode-pylance
ms-
2023.3.40

jupyter
ms-
2023.3.1000892223

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

cmake-tools
ms-
1.13.45

cpptools
ms-
1.14.5

cpptools-extension-pack
ms-
1.3.0

mutable-ai
mut
1.2.0

java
red
1.16.0

snyk-vulnerability-scanner
sny
1.18.1

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.49.1

vscode-java-dependency
vsc
0.21.2

vscode-java-pack
vsc
0.25.10

vscode-java-test
vsc
0.38.2

vscode-maven
vsc
0.41.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
vsccsb:30677849
pythonb192cf:30669361
defaultazurewalk:30687958
pythonms35:30701012

Sorry, I don't follow, can you give some more details about what you are seeing and what the problem is? Maybe a screenshot or recording?

I’ll get a recording of the screen and send it to you
On Mon, Apr 3, 2023 at 11:17 AM Rob Lourens @.***>
wrote:

Sorry, I don't follow, can you give some more details about what you are
seeing and what the problem is? Maybe a screenshot or recording?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/178904#issuecomment-1494696108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4XVWFHOW6METYIRZHRTDP3W7MAZ7ANCNFSM6AAAAAAWP3VMLI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey @roblourens, this issue might need further attention.
@12112122, you can help us out by closing this issue if the problem no longer exists, or adding more information.


Feature request: Open pdf in a detached process

Hello,
unfortunately my command line fu is not advanced enough to modify the startup script myself.
What I would like is that after pressing return the selected pdf is opened but the fast-p terminal stays unchanged. So I could change my search and open another pdf from the same terminal.

What is your current bashrc definition of the command p?

I tried several combination of xargs, nohup and & with no success.
p () {
  open=xdg-open   # this will open pdf file withthe default PDF viewer on KDE, xfce, LXDE and perhaps on other desktops.
  i3-msg layout tabbed > /dev/null 2> /dev/null
  rg --files -g "*.{pdf}"  \
    | fast-p \
    | fzf --read0 --reverse -e -d $'\t'  \
    --height 100% --preview-window up --preview '
  v=$(echo {q} | tr " " "|");
  echo -e {1}"\n"{2} | grep -E "^|$v" -i --color=always;
  ' \
    | cut -z -f 1 -d $'\t' | tr -d '\n' | xargs -r --null $open > /dev/null 2> /dev/null
  p # keep fast-p open
}

You may have some luck with the -m option of fzf that lets you send multiples entries (each selected with tab).  However, you would have to completely change the command following fzf to parse the multiple entries from fzf.
Launching p is supposed to be very fast thanks to the cache, you may simply type p again in the terminal.

Closing this since the desired custom behavior can be achieved by tweaking .bashrc.

Just for the record. This works:
pdf() {
    open=xdg-open   # this will open pdf file withthe default PDF viewer on KDE, xfce, LXDE and perhaps on other desktops.

    ag -U -g ".pdf$" \
    | fast-p \
    | fzf --read0 --reverse -e -d $'\t'  \
        --preview-window down:80% --preview '
            v=$(echo {q} | tr " " "|");
            echo -e {1}"\n"{2} | grep -E "^|$v" -i --color=always;
        ' \
    | cut -z -f 1 -d $'\t' | tr -d '\n' | xargs -r --null sh -c 'nohup "$0" "$@" >/dev/null 2>&1 &' "$open"
}


[dev-v2.7] Sync-up development branch after Rancher v2.7.11 System Charts Release

Issue:
https://github.com/rancher/rancher/issues/44274
Problem
This PR syncs the release-v2.7 branch back to the dev-v2.7 branch after the v2.7.11 System Charts Release.

@recena I don't have merge permission here. Could you merge it for me, please?

@lucasmlp I can't


nixpkgs-review: 2.10.5 -> 2.11.0

Things done
Changelog: https://github.com/Mic92/nixpkgs-review/releases/tag/2.11.0
cc @Mic92

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 347428

x86_64-linux

:white_check_mark: 4 packages built:

nix-update
nix-update.dist
nixpkgs-review
nixpkgs-review.dist

aarch64-linux

:white_check_mark: 4 packages built:

nix-update
nix-update.dist
nixpkgs-review
nixpkgs-review.dist

x86_64-darwin

:white_check_mark: 4 packages built:

nix-update
nix-update.dist
nixpkgs-review
nixpkgs-review.dist

aarch64-darwin

:white_check_mark: 4 packages built:

nix-update
nix-update.dist
nixpkgs-review
nixpkgs-review.dist

cc @zowoq this also adds a "system" field to the json. I believe nixpkgs-update is parsing report.json? Here is what the new json looks like: https://github.com/Mic92/nixpkgs-review/pull/419/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R184

It looks like it just inserts the contents of report.md at the bottom of its PR template. I'll check to make sure that it still works after the bot it updated to use this version.

New version works with nixpkgs-update: https://github.com/NixOS/nixpkgs/pull/347683


Typescript

Could someone give me an example how I can use this library in typescript project ?
It doesn't compile at all;(
...
import { Field } from 'redux-form';
import { SelectField } from 'redux-form-material-ui';
...

render() {
   return (
              <Field
                name="hui"
                component={SelectField}
              />);
}

I assume, you must be using redux-form-material-ui@next which currently doesn't support typings.
I am open for the PR, you can take example of this file and create def file for next version ?


Fix #612

Also, would a unit test be appropriate here?

I do want to add a unit test. I was up far too late last night doing this, so I just made a quick fix and PR so that I could run the CI tests. I'll add something before merging.


consider using 32-bit offsets for start and end in yp_location_t

YARP provides precise location information for any number of things in its AST, which is great!  But each of those locations on a 64-bit platform costs 16 bytes, which means every YARP node (yp_node_t) on those platforms is at least 24 bytes, which is rather large.
For some concrete numbers, nearly half (~47%) of the memory size as measured by YARP::Debug.memsize on a subset of Stripe's codebase is consumed by locations.  YARP::Debug.memsize doesn't measure this as-is; the count(s) of locations were obtained from this branch (and note whatever the branch counts needs to be multiplied by 16 to obtain the size):
https://github.com/ruby/yarp/compare/main...froydnj:froydnj-location-counting
so I might have done something wrong.
Using 32-bit offsets (well, probably 31-bit offsets so there's still some way to mark locations as "invalid" or "unavailable") would immediately shrink the memory required by ~25%; I haven't put together a proof-of-concept branch with that change, but my belief is that there would be a performance gain as well, though probably not of the same magnitude.  One can also imagine more complicated schemes where nodes hold a 32-bit key into some side table, which would shrink things still more, but one step at a time.
This change would limit the kinds of Ruby source files that YARP could consume.  But other Ruby-consuming tools/implementations (Sorbet and--I think--TruffleRuby cc @eregon ) already maintain 32-bit offsets internally.  I believe Clang and Go also only store 32-bit offsets for their locations.  If Clang and Go can get away with it, I think YARP can too.

I assume we're already limited in very non-obvious ways, so I'm not particularly worried about switching to 32-bits. I think this is a good idea.
I disagree with @eregon here I don't think we can halt merging entirely in service of getting this over the finish line, so I'd like to explore other ways to do this incrementally.
I think one way to start would be to modify a single location field on a single node. You would do this by creating a new kind of field called OffsetsField (as opposed to LocationField). Presumably this could be done in the various yp_*_node_create functions where it would subtract from the beginning of the parser. That way we could test out the implications of a single node's fields while still being able to keep the codebase healthy.

Officially got confirmation that we can make this happen! Yay! https://bugs.ruby-lang.org/issues/20488#note-1


vue range slider example from the docs crashes

Description
The vue range slider example from the docs crashed with the following error:
Cannot read properties of undefined (reading 'max')

at Proxy. (./node_modules/.pnpm/@ark-ui+vue@3.7.2_vue@3.4.37/node_modules/@ark-ui/vue/dist/components/slider/slider-thumb.js.js:18:80)

the only difference to the react example is the missing defaultValue. note that the react example also crashes when i remove the defaultValue prop.
Link to Reproduction (or Detailed Explanation)
https://github.com/stefanprobst/issue-ark-ui-slider
Steps to Reproduce

clone repro
pnpm install && pnpm run dev
open http://localhost:3000/

Ark UI Version
3.7.2
Framework

[ ] React
[ ] Solid
[X] Vue

Browser
firefox 128
Additional Information
No response

This is a docs/example issue. The default value or value is required when using a range slider.

I'm update the docs accordingly


GetHostSessionInfo changed to GetLiveData

It looks like in the latest version of Connectwise Control  the following endpoint has changed name.
#$Endpoint = 'Services/PageService.ashx/GetHostSessionInfo'
$Endpoint = 'Services/PageService.ashx/GetLiveData'
I have updated the Get-CWCSession.ps1 to see can I get it to work but receiving an error index out of range.
Possibly due to action center in the payload:
[{"HostSessionInfo":{"sessionType":2,"sessionGroupPathParts":["All Machines"],"filter":"","findSessionID":"GUIDKEY","sessionLimit":1000},"ActionCenterInfo":{}},340713519]
Have tried changing
$Body = ConvertTo-Json @($Number,@($Group),$Search,$null,$Limit)
to
$Body = ConvertTo-Json @($Number,@($Group),$Search,$null,$Limit),($null) and different variations but my knowledge of how that works is limited

Line |
33 |      $Data =  Invoke-CWCWebRequest -Arguments $WebRequestArguments
|               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| An error has been thrown. -->  --> {"errorType":"ArgumentException","message":"Unable to process arguments:
| Index was out of range. Must be non-negative and less than the size of the collection.\r\nParameter name:
| index","detail":null} at Invoke-CWCWebRequest,
| C:\Users\Documents\PowerShell\Modules\ConnectWiseControlAPI\<IP_ADDRESS>\Private\Invoke-CWCWebRequest.ps1: line 25 at Get-CWCSession, C:\Users\Documents\PowerShell\Modules\ConnectWiseControlAPI\<IP_ADDRESS>\Public\PageService\Get-CWCSession.ps1: line 33 at , C:\Auditman\scripts\TierneysMagicDash.ps1: line 123 at , : line 1

It's not pretty, but I found updating Get-CWCSession.ps1 with the below has worked for me with the same results as previously. So no modification to any implementations you have already coded :).
`
function Get-CWCSession {
[CmdletBinding()]
param (
[Parameter(Mandatory=$True)]
[ValidateSet('Support','Access','Meeting')]
$Type,
[string]$Group = $script:defaultGroup,
[string]$Search,
[int]$Limit
)
$Endpoint = 'Services/PageService.ashx/GetLiveData'

switch($Type){
    'Support' { $Number = 0 }
    'Meeting' { $Number = 1 }
    'Access' { $Number = 2 }
    default { return Write-Error "Unknown Type, $Type" }
}

#$Body = ConvertTo-Json @($Number,@($Group),$Search,$null,$Limit)

Write-Debug $Group

$Body = @"

[
{
"HostSessionInfo": {
"sessionType": 2,
"sessionGroupPathParts": [
"$Group"
],
"filter": "$Search",
"findSessionID": null,
"sessionLimit": 1000
},
"ActionCenterInfo": {}
},
0
]
"@
Write-Verbose $Body

$WebRequestArguments = @{
    Endpoint = $Endpoint
    Body = $Body
    Method = 'Post'
}

$Data =  Invoke-CWCWebRequest -Arguments $WebRequestArguments
$Data.ResponseInfoMap.HostSessionInfo.sessions
#$Data.sessions

}
`

Thank you. That works perfectly. Im back in action.

Thank you alot !

Thank you @twistedpro
You resolved my issue too.


lgiordani fork added

I added my fork that uses the punch version updater instead of bumpversion

Thank you!


Use JMH to do the benchmark

http://www.baeldung.com/java-microbenchmark-harness

JMH is not appropriate.


[Bug] Select widget - disable functionality dosent work

Description
The disable functionality in the select widget seems to be broken. On changing the toggle or adding a JS binding no change is observed
Steps to reproduce the behaviour:

Drag & drop a select widget
Toggle disable prop
Observe that the widget does not disable

Important Details

Version: [Cloud / Self-Hosted vx.x]
OS: [e.g.MacOSX]
Browser [chrome, safari]
Environment [production,]

@Tooluloope lets triage the issue here, how was this bug introduced

@somangshu this is already fixed in the Multiselect PR,
Check the video if it's exactly what you mean
https://www.loom.com/share/4499c1712b4a47a088f1cb49b4b821f6

It seems that the select widget is disabled, but it doesn't look disabled.
@Tooluloope Can you ensure the disabled states look same for all input widgets? Please ask for help from Momcilo if you need designs.

@Tooluloope @vivekverma2312 is this verified for the select widget as well?

@somangshu It's tested and working fine for both select and multi-select on deploy preview
https://deploy-preview-5228--appsmith-editor-ce.netlify.app/
https://www.loom.com/share/8f45a58f9b2b42779d56687d282cdb44


webUILogin/openidLogin.feature:38 test fails in OCIS master

Demonstration PR #2346
https://drone.owncloud.com/owncloud/ocis/6203/44/6
runsh: Total unexpected failed scenarios throughout the test run:
webUILogin/openidLogin.feature:38

This is an existing problem in master. Somehow we merged something into owncloud/ocis that broke a web test scenario.
Note: ordinary PRs only run the web smokeTest scenarios. So we do not notice if there is a regression where all the core API tests pass, the web smokeTests pass, but some other web test(s) fail. We only ffind this out when someone runs full-ci

Note: the scenario passes every time in owncloud/web - see demonstration PR https://github.com/owncloud/web/pull/5622

Fix already is on the web release-4.0.0 branch as @pascalwengerter pointed out. The selector for error messages on the ocis login page changed. Still wondering though how that commitid update for ocis didn't have issues in CI then.

I don't understand why this fails in the current OCIS master, with the current web-commit-id that CI is using.
It passes in owncloud/web current master, with whatever OCIS commit-id is specified there.
So something has been merged to owncloud/ocis master branch that has broken this - regardless of any pending "release" PRs in owncloud/web and owncloud/ocis
This highlights the problem that we do not run the full set of web test scenarios for OCIS PRs. We notice "some time later" that there is a problem.
Probably this will get sorted out with the upcoming web and ocis releases. But if there were not releases already in progress, then we would have to investigate separately.

Still wondering though how that commitid update for ocis didn't have issues in CI then.

If full-ci was not run, then we would not notice that a web test scenario failed.

IMO not running full CI in ocis is fine. This is a special case: we changed UI code that is located in the ocis repo (idp module) but has a test scenario in another repo (web).  This feels weird and shouldn't be a reason against a sparse webUI CI in ocis in general.
Things we could do:

add snapshot tests for our customized parts of the idp UI (feels meh)
live with it because it's a rare edge case that we change idp UI 😅
set up e2e tests for the idp module like we have it for the accounts and settings UIs with their own pipelines
...

What do you think @phil-davis ? 🤔

I vote for "live with it".
There are some elements of the web UI workflow whose source code is not in owncloud/web. But tests in owncloud/web need to be able to know about those elements in order to traverse the pages to get through real web UI tests. If those elements change in a not-backward-compatible way, then the web test code has to change. That's life.

This scenario is no longer in expected-failures. It is passing since a while ago.


There is this error that appears namely file contains data in an unknown format. No matter whatever mp3 file I chose the same error pops up

Use Wav files


Also run grunt docs

Or a subset of tasks of grunt docs

I propose grunt clean:docs copy:docs as the subset

:+1:

IIRC clean already runs though.

dist only includes clean:dist, not clean:docs, as a subtask

Yeah, but docs includes clean:docs.

So, doing grunt dist docs should be enough.

docs also does lint checks, generates raw-files, and other overkill stuff, hence I am inclined to avoid it.

Well, I agree about the lint stuff, but raw-files is still part of docs.

Yes, but it would cause so much extra churn.


Last Tiltbrush SDK with what version of Unity in 2019

Hi, there are a lot of Unity version in 2019. With the first 2019.1.0f2 it's OK, I have all my brushes and colors, but with 2019.3.5f1 I lost all of them. What's the last version who work ?
Thank you

Hi, Scenarman. The toolkit works on the 2018.4 (LTS, Long Term Support) version of Unity. Once 2019.4 LTS is released, we will be able to look at supporting 2019.

For me, it' work with 2019.1.0f2. I need that because I use a new tool "Interhaptics" and it doesn't work on 2018.


Latitude/Longitude lines and set_extent fix

Addresses #930 by adding latitude/longitude contours to spatial maps if spatial map.
Also fixes issue where set_extent does not work properly, by parsing it the map projection.
Contribution checklist
Aim to have all relevant checks ticked off before merging. See the developer's guide for more detail.

[ ] Documentation has been updated to reflect change.
[ ] New code has tests, and affected old tests have been updated.
[ ] All tests and CI checks pass.
[ ] Ensured the pull request title is descriptive.
[ ] Conda lock files have been updated if dependencies have changed.
[ ] Attributed any Generative AI, such as GitHub Copilot, used in this PR.
[ ] Marked the PR as ready to review.

TODO: ensemble applicability and catch cases where spatial coordinates are not latitude/longitude.


add: Napong Jantaranimi

Description

Related Issues

Changes Proposed

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@devlopersabbir

@NongBritee Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


Testing Steps

Hello,
If we deploy Upgrade Readiness, does it block any current Windows Updates process?
As example now updates set on Windows 10 PC's to run automatically, used Intune Delivery Optimization profile & Software Update rings,
If we will deploy Upgrade Readiness, does all updates stop work until we follow steps and go to "Step 3 Deploy updates"?
Or all current Windows Updates will be continue working process as they are now (using automatic update settings) and then Upgrade Readiness is more like optional solution to control Windows Updates issues?

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

ID: d6dc80d9-7606-664b-d292-9909c7793484
Version Independent ID: 096e6a8d-600f-dae6-57fe-a8509cabbf4e
Content: Manage Windows upgrades with Upgrade Readiness (Windows 10)
Content Source: windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@officedocsbot assign @e0i

@lightupdifire Thank you for reaching out and helping improve MS Docs.  Please see this latest article on Upgrade Readiness and let me know if it helps answer your questions.  I can have the link added to this article for other users if you think it would help them as well - https://docs.microsoft.com/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.

@lindspea Thanks for information, let me try ask in a different way:
If we deploy Upgrade Readiness and stop use it after it is deployed, is it possible that updates will be stopped on devices until someone follow all steps 1-2-3 from Upgrade Readiness ?
Or all updates continue works as they were before Upgrade Readiness deployment in a tenant?
Asking because we plan deployment of Device Health, that could give us information regards WIP, but in Device Health article, the Upgrade Readiness is in perquisites.. So idea is to deploy Upgrade Readiness for Device Health, but for Windows Updates delivery we just want to keep for a moment solution with standard options:

Intune policy to apply update release and settings -> Software Rings
Intune policy for delivery optimization

@lightupdifire I'll investigate some more with the team and get back to you as soon as possible.

@lightupdifire Sorry for the delay, I'm still investigating with the team to help answer your questions. In the meantime here is a new article that was added recently. https://docs.microsoft.com/windows/deployment/upgrade/upgrade-readiness-get-started.

@lindspea Thanks for information, let me try ask in a different way:
If we deploy Upgrade Readiness and stop use it after it is deployed, is it possible that updates will be stopped on devices until someone follow all steps 1-2-3 from Upgrade Readiness ?
Or all updates continue works as they were before Upgrade Readiness deployment in a tenant?
Asking because we plan deployment of Device Health, that could give us information regards WIP, but in Device Health article, the Upgrade Readiness is in perquisites.. So idea is to deploy Upgrade Readiness for Device Health, but for Windows Updates delivery we just want to keep for a moment solution with standard options:
1. Intune policy to apply update release and settings -> Software Rings

2. Intune policy for delivery optimization

@greg-lindsay Would you be able to shed light on this question if possible? Thank you.

@Deepamdubey is the person who can actually answer this question.

No, it doesn't. You have complete control of your deployments and they work as configured within your organization. So your windows updates or Intune delivery settings will not be impacted if you onboard to Windows or Desktop Analytics. As, mentioned none of the deployments will happen automatically until initiated.

Thanks for info! Will proceed with deployment.


refactor: copy & rename  Receive's reusable step screens for new add account flow

✅ Checklist

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

📝 Description
Please read this before merging 🚨
Main PR changes structure
apps/
└── ledger-live-mobile/
    └── src/
        ├── components/
        │   └── RootNavigator/
        │       ├── BaseNavigator.tsx //add new navigators (feature flagged)
        │       └── types/
        │           └── BaseNavigator.ts // add new navigators params list types here
        ├── const/
        │   └── navigation.ts // add navigator names
        ├── navigation/
        │   └── DeeplinksProvider.tsx // support entry point to new Add account flow via feature flag
        └── newArch/
            ├── features/
            │   ├── Accounts/
            │   │   ├── Navigator.tsx // main navigator of the Account context
            │   │   └── screens/
            │   │       ├── AddAccount/
            │   │       │   ├── components/
            │   │       │   │   └── SelectAddAccountMethod/
            │   │       │   │       └── useSelectAddAccountMethodViewModel.ts
            │   │       │   ├── types.ts
            │   │       │   └── screens/
            │   │       │       ├── ScanDeviceAccounts/ // Accounts scanner from device
            │   │       │       │   └── index.tsx
            │   │       │       └── SelectAccounts/ // Retrieved account selector screen
            │   │       │           └── index.tsx
            │   ├── AssetSelection/ // a feature where user can select crypto & network
            │   │   ├── Navigator.tsx
            │   │   └── screens/
            │   │       ├── SelectCrypto/
            │   │       │   └── index.tsx
            │   │       ├── SelectNetwork/
            │   │       │   └── index.tsx
            │   │       └── types.ts
            │   ├── DeviceSelection/ // a feature where user can select/connect device
            │   │   ├── Navigator.tsx
            │   │   └── screens/
            │   │       ├── ConnectDevice/
            │   │       │   └── index.tsx
            │   │       ├── SelectDevice/
            │   │       │   └── index.tsx
            │   │       └── types.ts

In this feature we introduce the following changes:

This work is protected by a feature flag, there will be no visible impact on the functional side
Use the component contract and the business logic of the following screens (from the current Receive flow)
➡03a-ConnectDevice.tsx & 02-AddAccountSelectDevice : copied and put in newArch as a standalone feature screens  called DeviceSelection/ with it's own Navigator and types
➡ 01-SelectCrypto.tsx & 02-SelectNetwork.tsx : copied and arranged under newArch as AssetSelection feature  screens
➡ under newArch/Accounts , copied the business logic and screens API from 02-SelectAccount.tsx as SelectAccount & 02-AddAccount.tsx as ScanDeviceAccount (proper naming here)

-📝 Each same scope screens are regrouped in a standalone feature with a single Navigator each.
Navigation process between screen is done by either navigating with ScreenNames for local scoped screens or via NavigatorName for cross Navigator screens.

✅ Deeplinks support the new entry point for add acount v2 through navigator. The main Screen is AddAccountSelectCrypto with different NavigatorName in feature flag ON & OFF.

⚠ Integration tests cannot be integrated in this ticket as business logic will depend on add account context

Navigation Preview 📸
Feature Flag ON 📱
https://github.com/user-attachments/assets/86567bc6-4820-4ab5-b6f6-3c7afdcf6889
Feature Flag 📴
https://github.com/user-attachments/assets/2c71e573-fa15-433e-9e65-32f3c50a3e58

❓ Context

JIRA or GitHub link:

https://ledgerhq.atlassian.net/browse/LIVE-14631
🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Tested with and without ff. Without ff activated all good but when enabled I have a blank screen instead of the flow from account screen (see video on click on add new).
https://github.com/user-attachments/assets/8d5a68c1-ca72-466e-a184-e23e340d11e4


Overwriting ItemSparse.db2 crash

Hello, after I overwrite the ItemSparse.db2 (FDID: 1572924) file and enter the world I get the following error message few seconds after the loading screen ends:

This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program:    E:\Modding\Schattenhain...\Local\Game\SchattenhainLocal03.exe
ProcessID:    13028
ThreadID:    20132
Exception:    ACCESS_VIOLATION
The instruction at "0x00000284ff270032" referenced memory at "0x00000284ff270032".
The memory could not be "executed".

GameVersion: <IP_ADDRESS>325
Used Launcher: Custom.Server.Launcher.Mods.Silent.Windows.zip

The issue was not related to the launcher or db2 it was just a combination of some other issues!