I tested on Mac with clang compiler, there are some compile errors:

c++20 should change to c++2a
other errors:

In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:16:
async_simple/async_simple/coro/FutureAwaiter.h:44:35: error: expected ';' at end of declaration
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
                                  ^
                                  ;
async_simple/async_simple/coro/FutureAwaiter.h:44:36: error: expected unqualified-id
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
                                   ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
async_simple/async_simple/coro/CoAwait.h:96:25: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is defined
    static ViaCoroutine create(Executor* ex) { co_return; }
                        ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:40:18: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is
      defined
    auto lazy1 = [&]() -> Lazy<> {
                 ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
In file included from async_simple/async_simple/coro/CoAwait.h:30:
async_simple/async_simple/coro/Traits.h:70:12: error: call to deleted constructor of 'async_simple::Future<int>'
    return std::forward<Awaitable>(awaitable);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
async_simple/async_simple/coro/CoAwait.h:184:26: note: in instantiation of function template specialization 'async_simple::coro::detail::getAwaiter<async_simple::Future<int> &, 0, 0>' requested here
        decltype(detail::getAwaiter(std::forward<Awaitable>(awaitable)));
                         ^
async_simple/async_simple/coro/Lazy.h:97:24: note: in instantiation of function template specialization 'async_simple::coro::detail::coAwait<async_simple::Future<int> &, 0>' requested here
        return detail::coAwait(_executor, std::forward<Awaitable>(awaitable));
                       ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: in instantiation of function template specialization
      'async_simple::coro::detail::LazyPromiseBase::await_transform<async_simple::Future<int> &>' requested here
        auto val = co_await fut;
                   ^
async_simple/async_simple/Future.h:63:5: note: 'Future' has been explicitly marked deleted here
    Future(const Future&) = delete;
    ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
async_simple/async_simple/coro/CoAwait.h:139:43: error: no member named 'await_suspend' in 'async_simple::Future<int>'
        decltype(std::declval<Awaiter&>().await_suspend(
                 ~~~~~~~~~~~~~~~~~~~~~~~~ ^
async_simple/async_simple/coro/CoAwait.h:185:12: note: in instantiation of template class 'async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> >' requested here
    return ViaAsyncAwaiter<std::decay_t<AwaiterType>>(
           ^
async_simple/async_simple/coro/Lazy.h:97:24: note: in instantiation of function template specialization 'async_simple::coro::detail::coAwait<async_simple::Future<int> &, 0>' requested here
        return detail::coAwait(_executor, std::forward<Awaitable>(awaitable));
                       ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: in instantiation of function template specialization
      'async_simple::coro::detail::LazyPromiseBase::await_transform<async_simple::Future<int> &>' requested here
        auto val = co_await fut;
                   ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: call to 'await_transform' implicitly required by 'co_await' here
        auto val = co_await fut;
                   ^        ~~~
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:49:18: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is
      defined
    auto lazy2 = [&]() -> Lazy<> {
                 ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:56:20: error: function 'operator co_await<async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> > >' with deduced return type
      cannot be used before it is defined
        auto val = co_await std::move(fut);
                   ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> > >' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
8 errors generated.
make[2]: *** [async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/FutureAwaiterTest.cpp.o] Error 1
make[1]: *** [async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/all] Error 2
make: *** [all] Error 2

Have you tested it on Mac?

yes, i passed all test on libc++ mode, but got one error about link -lstdc++fs, we need fix it in another pr
$ make -j4
[  5%] Building CXX object async_simple/test/CMakeFiles/async_simple_test.dir/FutureStateTest.cpp.o
[  5%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/FutureAwaiterTest.cpp.o
[  7%] Building CXX object async_simple/executors/test/CMakeFiles/async_simple_executor_test.dir/SimpleIOExecutorTest.cpp.o
[ 10%] Building CXX object async_simple/util/test/CMakeFiles/async_simple_util_test.dir/ThreadPoolTest.cpp.o
[ 13%] Building CXX object async_simple/executors/test/CMakeFiles/async_simple_executor_test.dir/__/__/test/dotest.cpp.o
[ 15%] Linking CXX executable async_simple_executor_test
[ 15%] Built target async_simple_executor_test
[ 18%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/LazyTest.cpp.o
[ 21%] Building CXX object async_simple/util/test/CMakeFiles/async_simple_util_test.dir/__/__/test/dotest.cpp.o
[ 23%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/SleepTest.cpp.o
[ 26%] Building CXX object async_simple/test/CMakeFiles/async_simple_test.dir/FutureTest.cpp.o
[ 28%] Linking CXX executable async_simple_util_test
[ 28%] Built target async_simple_util_test
[ 31%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/TraitsTest.cpp.o
[ 34%] Building CXX object demo_example/CMakeFiles/smtp_client.dir/smtp/smtp_client.cpp.o
[ 36%] Building CXX object demo_example/CMakeFiles/block_http_server.dir/http/block_http/block_http_server.cpp.o
[ 39%] Linking CXX executable block_http_server
[ 39%] Built target block_http_server
[ 42%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/ViaCoroutineTest.cpp.o
[ 44%] Linking CXX executable smtp_client
ld: library not found for -lstdc++fs
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [demo_example/smtp_client] Error 1
make[1]: *** [demo_example/CMakeFiles/smtp_client.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 47%] Building CXX object async_simple/test/CMakeFiles/async_simple_test.dir/TryTest.cpp.o
[ 50%] Building CXX object async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/__/__/test/dotest.cpp.o
[ 52%] Building CXX object async_simple/test/CMakeFiles/async_simple_test.dir/dotest.cpp.o
[ 55%] Linking CXX executable async_simple_test
[ 55%] Built target async_simple_test
[ 57%] Linking CXX executable async_simple_coro_test
[ 57%] Built target async_simple_coro_test
make: *** [all] Error 2

-lstdc++fs removed
$ make -j4
-- CMAKE_MODULE_PATH: /Users/rain/Project/async_simple/cmake
-- FindAio.cmake:
CMake Warning (dev) at /usr/local/Cellar/cmake/3.20.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (aio) does
  not match the name of the calling package (Aio).  This can lead to problems
  in calling code that expects `find_package` result variables (e.g.,
  `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindAio.cmake:22 (find_package_handle_standard_args)
  CMakeLists.txt:8 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Could NOT find aio (missing: LIBAIO_LIBRARIES)
CMake Warning (dev) at /usr/local/Cellar/cmake/3.20.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (gmock) does
  not match the name of the calling package (GMock).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindGMock.cmake:25 (find_package_handle_standard_args)
  CMakeLists.txt:9 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at /usr/local/Cellar/cmake/3.20.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (gtest) does
  not match the name of the calling package (GTest).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindGTest.cmake:25 (find_package_handle_standard_args)
  CMakeLists.txt:10 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at /usr/local/Cellar/cmake/3.20.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (benchmark)
  does not match the name of the calling package (Benchmark).  This can lead
  to problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindBenchmark.cmake:25 (find_package_handle_standard_args)
  CMakeLists.txt:11 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Could NOT find benchmark (missing: BENCHMARK_LIBRARIES BENCHMARK_INCLUDE_DIR)
-- GTest found.
-- GTest: /usr/local/include, /usr/local/lib/libgtest.a
-- GMock found.
-- GMock: /usr/local/include, /usr/local/lib/libgmock.a
-- Use flag -m64
-- Skipping benchmarks
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/rain/Project/async_simple/oxs
Consolidate compiler generated dependencies of target async_simple_test
Consolidate compiler generated dependencies of target async_simple_util_test
Consolidate compiler generated dependencies of target async_simple_coro_test
Consolidate compiler generated dependencies of target async_simple_executor_test
[  7%] Built target async_simple_executor_test
[ 15%] Built target async_simple_util_test
[ 28%] Built target async_simple_test
Consolidate compiler generated dependencies of target smtp_client
[ 47%] Built target async_simple_coro_test
Consolidate compiler generated dependencies of target block_http_server
[ 50%] Building CXX object demo_example/CMakeFiles/http_client.dir/http/coroutine_http/http_client.cpp.o
[ 52%] Building CXX object demo_example/CMakeFiles/CountChar.dir/CountChar.cpp.o
[ 55%] Linking CXX executable smtp_client
[ 60%] Built target block_http_server
[ 63%] Building CXX object demo_example/CMakeFiles/http_server.dir/http/coroutine_http/http_server.cpp.o
[ 65%] Built target smtp_client
[ 68%] Building CXX object demo_example/CMakeFiles/block_echo_client.dir/block_echo_client.cpp.o
[ 71%] Linking CXX executable CountChar
[ 71%] Built target CountChar
[ 73%] Building CXX object demo_example/CMakeFiles/block_echo_server.dir/block_echo_server.cpp.o
[ 76%] Linking CXX executable block_echo_client
[ 76%] Built target block_echo_client
[ 78%] Building CXX object demo_example/CMakeFiles/async_echo_server.dir/async_echo_server.cpp.o
[ 81%] Linking CXX executable http_client
[ 81%] Built target http_client
[ 84%] Building CXX object demo_example/CMakeFiles/async_echo_client.dir/async_echo_client.cpp.o
[ 86%] Linking CXX executable block_echo_server
[ 86%] Built target block_echo_server
[ 89%] Building CXX object demo_example/CMakeFiles/ReadFiles.dir/ReadFiles.cpp.o
[ 92%] Linking CXX executable http_server
[ 92%] Built target http_server
[ 94%] Linking CXX executable async_echo_server
[ 94%] Built target async_echo_server
[ 97%] Linking CXX executable async_echo_client
[ 97%] Built target async_echo_client
[100%] Linking CXX executable ReadFiles
[100%] Built target ReadFiles

 12:08:48  rain@RaindeMacBook-Pro  ...Project/async_simple/oxs   off_uthread ✘ ✹ ✭  23s 
$ make test
Running tests...
Test project /Users/rain/Project/async_simple/oxs
    Start 1: run_async_simple_test
1/4 Test #1: run_async_simple_test ............   Passed    1.49 sec
    Start 2: run_async_simple_util_test
2/4 Test #2: run_async_simple_util_test .......   Passed    0.29 sec
    Start 3: run_async_simple_coro_test
3/4 Test #3: run_async_simple_coro_test .......   Passed   10.93 sec
    Start 4: run_async_simple_executor_test
4/4 Test #4: run_async_simple_executor_test ...   Passed    0.28 sec

100% tests passed, 0 tests failed out of 4

Total Test time (real) =  13.00 sec

I tested on Mac with clang compiler, there are some compile errors:

c++20 should change to c++2a
other errors:

In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:16:
async_simple/async_simple/coro/FutureAwaiter.h:44:35: error: expected ';' at end of declaration
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
                                  ^
                                  ;
async_simple/async_simple/coro/FutureAwaiter.h:44:36: error: expected unqualified-id
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
                                   ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
async_simple/async_simple/coro/CoAwait.h:96:25: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is defined
    static ViaCoroutine create(Executor* ex) { co_return; }
                        ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:40:18: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is
      defined
    auto lazy1 = [&]() -> Lazy<> {
                 ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
In file included from async_simple/async_simple/coro/CoAwait.h:30:
async_simple/async_simple/coro/Traits.h:70:12: error: call to deleted constructor of 'async_simple::Future<int>'
    return std::forward<Awaitable>(awaitable);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
async_simple/async_simple/coro/CoAwait.h:184:26: note: in instantiation of function template specialization 'async_simple::coro::detail::getAwaiter<async_simple::Future<int> &, 0, 0>' requested here
        decltype(detail::getAwaiter(std::forward<Awaitable>(awaitable)));
                         ^
async_simple/async_simple/coro/Lazy.h:97:24: note: in instantiation of function template specialization 'async_simple::coro::detail::coAwait<async_simple::Future<int> &, 0>' requested here
        return detail::coAwait(_executor, std::forward<Awaitable>(awaitable));
                       ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: in instantiation of function template specialization
      'async_simple::coro::detail::LazyPromiseBase::await_transform<async_simple::Future<int> &>' requested here
        auto val = co_await fut;
                   ^
async_simple/async_simple/Future.h:63:5: note: 'Future' has been explicitly marked deleted here
    Future(const Future&) = delete;
    ^
In file included from async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:17:
In file included from async_simple/async_simple/coro/Lazy.h:21:
async_simple/async_simple/coro/CoAwait.h:139:43: error: no member named 'await_suspend' in 'async_simple::Future<int>'
        decltype(std::declval<Awaiter&>().await_suspend(
                 ~~~~~~~~~~~~~~~~~~~~~~~~ ^
async_simple/async_simple/coro/CoAwait.h:185:12: note: in instantiation of template class 'async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> >' requested here
    return ViaAsyncAwaiter<std::decay_t<AwaiterType>>(
           ^
async_simple/async_simple/coro/Lazy.h:97:24: note: in instantiation of function template specialization 'async_simple::coro::detail::coAwait<async_simple::Future<int> &, 0>' requested here
        return detail::coAwait(_executor, std::forward<Awaitable>(awaitable));
                       ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: in instantiation of function template specialization
      'async_simple::coro::detail::LazyPromiseBase::await_transform<async_simple::Future<int> &>' requested here
        auto val = co_await fut;
                   ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:45:20: note: call to 'await_transform' implicitly required by 'co_await' here
        auto val = co_await fut;
                   ^        ~~~
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:49:18: error: function 'operator co_await<std::experimental::coroutines_v1::suspend_always>' with deduced return type cannot be used before it is
      defined
    auto lazy2 = [&]() -> Lazy<> {
                 ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<std::experimental::coroutines_v1::suspend_always>' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
async_simple/async_simple/coro/test/FutureAwaiterTest.cpp:56:20: error: function 'operator co_await<async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> > >' with deduced return type
      cannot be used before it is defined
        auto val = co_await std::move(fut);
                   ^
async_simple/async_simple/coro/FutureAwaiter.h:44:6: note: 'operator co_await<async_simple::coro::detail::ViaAsyncAwaiter<async_simple::Future<int> > >' declared here
auto operator co_await(T&& future) requires IsFuture<std::decay_t<T>>::value {
     ^
8 errors generated.
make[2]: *** [async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/FutureAwaiterTest.cpp.o] Error 1
make[1]: *** [async_simple/coro/test/CMakeFiles/async_simple_coro_test.dir/all] Error 2
make: *** [all] Error 2

It looks like the version of your compiler is not high enough to support concept.

Good, could you also update the doc, add how to compile the library on Mac?
The fs issue i will solve it, no need depend on fs i think, you can remove fs link in this PR.

Good, could you also update the doc: how to compile the library on Mac? The fs issue i will solve it, no need depend on fs i think, you can remove fs link in this PR.

ok

@qicosmos
stdc++fs related issue: https://gitlab.kitware.com/cmake/cmake/-/issues/17834
I tested result

clang11 + libstdc++ need link stdc++fs
clang13 + libc++ can not found stdc++fs

Revert because of #69


Safari/Flexbox alignment issues with button--fullWidth

For some reason, safari doesn't apply align-items correctly when a flex or inline-flex item has a width: 100%

fixed in release/2.0.0


Background map color turns black when base map visibility is OFF and transparency is turned ON

Bkackground map color turns black when base map visibility is turned off AND background map transparency is more than 0.
To reproduce:

Open a geo-located Bing (i.e you can see the Bing background).

You can turn off the base map visibility by running this key in: fdt set base map visibility false

At point, you should get a white background, which is expected.

Turn ON the transparency option is display-test-app:

Now the background map is grey (i.e black is half transparency). it should remains white.

This only happens if background map transparency set, if you set base map transparency (i.e fdt set map base transparency), it has no impact.
This appears to be a bug, but might be a limitation when there is no textures to be displayed... to strange thing is, although display is correct when no transparency is applied.  Maybe we should simply ignore background map transparency when there base map visibility is off (and there is no any other layer).

I attempted a fix in MapTile.getDrapeTextures() by returning undefined if no imagery tiles were available, which fix the problem if there is no other background map-layers.  If a single background map-layers is added, you get a black background again.


Fail to burn fuses and initiate the secure boot (Mallow board V1.1A, AM62)

Hello,
I have a problem with secure boot implementation for Toradex Mallow board V1.1A with Verdin AM62D 1GB WBIT. I followed the instructions but cannot progress further. First I encountered problems with Yocto build (tdx-reference-multimedia-image) when using meta-toradex-security layer (INHERIT += "tdx-signed") but it was resolved by creating clean build with all updates, layers, and patches already applied in first build.
I provided custom keys (backMpk.key, backMpk.pem, custMpk.key, custMpk.pem, and ti-degenerate-key.pem) during build (TDX_K3_HSSE_KEY_DIR ?= "${TOPDIR}/keys/ti"). I short-cut the pins to enter recovery mode, flash the EasyInstaller and install the image as usual. However, if I want to connect to the device, I cannot. UART and USB do not show any information. I supposes this is correct behaviour as the fuses were not burned so the boot fails (altough I cannot debug it and be sure as long as UART does not send any information).
I followed the instruction from TI docs and OTP Keywriter, creating tiboot3.bin file that should be able to burn the fuses.
Here: https://dev.ti.com/tirex/explore/node?node=A__AfTbl6-QQ9.goHdZtWK8.w__AM62-ACADEMY__uiYMDcq__<IP_ADDRESS> v1, they show how to flash the tiboot3.bin file to burn the fuses. But Mallow does not have configuration of the boot mode switches for USB-DFU boot mode as shown in Figure 1. Is that correct? I am not sure how to flash the tiboot3.bin into Mallow. When I run "sudo dfu-util -l" I see no devices. The tiboot3.bin provided by Toradex within the Yocto image does not burn the fuses, right?
Did anyone test the Mallow board with AM62 and secure boot? How to burn he fuses in this setup using TI's tiboot3.bin?
In this thread: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1342080/sk-am62-lp-sequence-for-enabling-secure-boot-using-custom-keys, I cannot proceed with:
7 Rebuild u-boot, now signed with the new custom key.
8 The tiboot3.bin is loaded by dfu boot, it is executed and burning the eFuses.
as I do not know how to load the tiboot3.bin.
Thanks for any information.
Matej I.

Hello,

I have a problem with secure boot implementation for Toradex Mallow board V1.1A with Verdin AM62D 1GB WBIT. I followed the instructions but cannot progress further. First I encountered problems with Yocto build (tdx-reference-multimedia-image) when using meta-toradex-security layer (INHERIT += "tdx-signed") but it was resolved by creating clean build with all updates, layers, and patches already applied in first build.

You should not have any build issues. Feel free to report them, providing the logs, so we can help you investigate it.

I provided custom keys (backMpk.key, backMpk.pem, custMpk.key, custMpk.pem, and ti-degenerate-key.pem) during build (TDX_K3_HSSE_KEY_DIR ?= "${TOPDIR}/keys/ti"). I short-cut the pins to enter recovery mode, flash the EasyInstaller and install the image as usual. However, if I want to connect to the device, I cannot. UART and USB do not show any information. I supposes this is correct behaviour as the fuses were not burned so the boot fails (altough I cannot debug it and be sure as long as UART does not send any information).

Yes, that is correct. A signed image will not boot on a device with no keys fused.

I followed the instruction from TI docs and OTP Keywriter, creating tiboot3.bin file that should be able to burn the fuses.
Here: https://dev.ti.com/tirex/explore/node?node=A__AfTbl6-QQ9.goHdZtWK8.w__AM62-ACADEMY__uiYMDcq__<IP_ADDRESS> v1, they show how to flash the tiboot3.bin file to burn the fuses. But Mallow does not have configuration of the boot mode switches for USB-DFU boot mode as shown in Figure 1. Is that correct?

Yeas, Mallow doesn't have the switches. But you can get it into recover mode as documented here: https://developer.toradex.com/easy-installer/toradex-easy-installer/loading-toradex-easy-installer/?module=verdin_am62&carrier=mallow#start

I am not sure how to flash the tiboot3.bin into Mallow. When I run "sudo dfu-util -l" I see no devices.

If you are not seing the device when running 'sudo dfu-util -l', it is probably because the device is not in recovery mode. For your record, this is the command I used to boot tiboot3.bin and fuse the keys:
sudo dfu-util -c 1 -i 0 -a bootloader -D tiboot3.bin

The tiboot3.bin provided by Toradex within the Yocto image does not burn the fuses, right?

No, it doesn't.

Did anyone test the Mallow board with AM62 and secure boot? How to burn he fuses in this setup using TI's tiboot3.bin?

I tested on Verdin Develoment Board, but not on Mallow.
One important thing to mention is that, to fuse the keys, you have to toggle the VPP pin while you are writing to the fuses. Did you implemented that in our keywriter software?

Hello,
Thank you for the information. I was able to find the devices (right after switching to recovery mode). However, I did not toggle the VPP pin. It seems that in SODIMM, it corresponds to pin 104 (SOC_VPP ballname) but I did not find it on the Mallow board. How is it connected to the board so I can configure it?

VPP pin is connected to SODIMM 104. I quickly looked at the Mallow board datasheet, and didn't find any connection to it. It seems this pin is not exposed in the Mallow board. You might want to confirm this with a Toradex FAE via the community website (https://community.toradex.com/).
This is the correct programming sequence to write to the fuses:

Power on the board per the power-up sequencing. No voltage should be applied on the VPP terminal during power up and normal operation.
Load the OTP write software required to program the eFuse (you need to contact a TI representative for the OTP software package, which requires NDA).
Apply the voltage on the VPP terminal according to the AM62 datasheet (Section 7.9.1).
Run the software that programs the OTP registers.
After validating the content of the OTP registers, remove the voltage from the VPP terminal.

Hello,
Toradex technical support confirmed that on Mallow V1.1, the VPP pin is not exposed to the board. However, we were able to connect small wire to the VPP pin and use pin 3 in X10 header of Mallow board to provide 1.8 V during fusing. But, it still does not work.
I want to confirm one thing that I am doing it right. First, I reset the device to recovery mode. Than, I provide 1.8 V to VPP pin and call:
sudo dfu-util -c 1 -i 0 -a bootloader -D tiboot3.bin

Which provides very similar output to what is expected in https://dev.ti.com/tirex/explore/node?node=A__AfTbl6-QQ9.goHdZtWK8.w__AM62-ACADEMY__uiYMDcq__LATEST
Then, to flash the image, I again reset the device to recovery mode and flash Easy Installer and install image via USB flash disc. My question is: Is this procedure correct? Can I reset the device to recovery mode again or is it wrong? I suppose it would be better to flash the image directly without using "Easy Installer" by Toradex but would this solve the problem?
Thank you.
Matej I.

@xistva02 Unfortunatelly, it is not that simple.
You have to follow the AM62X OTP Keywriter User Guide to prepare a development environment with TI tools to create a custom boot container (tiboot3.bin). This boot container should have a custom R5 firmware provided by TI under NDA and your key writer application.
Now, one important thing is that you have to toggle the VPP pin only when writing to the fuses. So this needs to be done in software, in your key writer application.
This is the main() function of my keywriter application for your reference (in my tests, the VPP pin was connected to a GPIO, so I could toggle it in software):
int main()
{
    uint32_t gpio_vpp_base_addr, gpio_vpp_pin;

    System_init();
    Drivers_open();

    DebugP_log("\r\n");
    DebugP_log("Starting Keywriting 1.0\r\n");

    gpio_vpp_base_addr = (uint32_t) AddrTranslateP_getLocalAddr(GPIO_VPP_BASE_ADDR);
    gpio_vpp_pin = GPIO_VPP_PIN;

    GPIO_setDirMode(gpio_vpp_base_addr, gpio_vpp_pin, GPIO_VPP_DIR);

    DebugP_log("Writing to fuses\r\n");
    GPIO_pinWriteHigh(gpio_vpp_base_addr, gpio_vpp_pin);
    keywriter_processKeyConfig();
    GPIO_pinWriteLow(gpio_vpp_base_addr, gpio_vpp_pin);
    DebugP_log("Done!\r\n");

    Drivers_close();
    System_deinit();

    loop_forever();

    return 0;
}


Flaky test: VSCode Smoke Tests (Web)

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=235762&view=logs&j=260a512b-e5ca-5cf1-3f8e-20c0fa41efc9&t=82df682a-a732-590f-d041-2bbd067871c9
  1) VSCode Smoke Tests (Web)
       Extensions
         install and enable vscode-smoketest-check extension:
     Error: Command: Extensions: Focus on Extensions View Not found
      at QuickAccess.runCommand (/Users/runner/work/1/s/test/automation/src/quickaccess.ts:202:9)
      at Extensions.searchForExtension (/Users/runner/work/1/s/test/automation/src/extensions.ts:22:3)
      at Extensions.installExtension (/Users/runner/work/1/s/test/automation/src/extensions.ts:48:3)
      at Context.<anonymous> (src/areas/extensions/extensions.test.ts:18:4)

/duplicate
https://github.com/microsoft/vscode/issues/193046

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


⚠ Empornium has degraded performance

In 4a62896, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 3534 ms

Resolved: Empornium performance has improved in 3ad0158 after 8 minutes.


Rewards page, reward history and reward shop

All tested need to implement api calls.

Description

Created the rewards page where users can see the total points they currently have accumulated. There is also 2 additional section, the history tab where users can look at their previous task completion as well as rewards claimed. And the Shop tab where they can use their points.
You can access the rewards page at "/rewards".
Tests

Tested the history and shop tabs are rendered properly.
Tested task history completion as well as claimed rewards render correctly.
Covering 100% of the code except 1 error line related to sad path for API call which isn't being mad yet, To do.

UI Changes

Issues
#124 #119 #116 #117 #120 #123

Additional Notes
Add any other information about the PR here.
Shop tab has been temporarily commented out until we figure out how to integrate it in our user-interaction.

This PR was not complete and still needed to use api calls


the size of the boundary box

What I need to do if I want to increase the size of the boundary box so that It covers the whole face from hair at the top to the bottom of the face. wherein code need to be changed?

You can change as follows
`def refined_box(left, top, width, height):
right = left + width
bottom = top + height
original_vert_height = bottom - top
**top = int(top + original_vert_height * 1.30)
bottom = int(bottom - original_vert_height * 1.30)**

margin = ((bottom - top) - (right - left)) // 2
left = left - margin if (bottom - top - right + left) % 2 == 0 else left - margin - 1

right = right + margin

return left, top, right, bottom

`

@naveenmula
Thank you. It helped


[Event Request] Page 6662 - Posted Return Receipts & Page 6660 - Posted Return Receipt - OnBeforePrintRecords

Hi AL-Team,
can you please add the following publisher to action Print?
We want to add further information from the Rec to the ReturnRcptHeader variable.
            action("&Print")
            {
                ApplicationArea = SalesReturnOrder;
                Caption = '&Print';
                Ellipsis = true;
                Image = Print;
                Promoted = true;
                PromotedCategory = Category4;
                ToolTip = 'Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out.';

                trigger OnAction()
                begin
                    // NEW >>>>
                    OnBeforePrintRecords(Rec,ReturnRcptHeader);
                    // NEW <<<<
                    CurrPage.SetSelectionFilter(ReturnRcptHeader);
                    ReturnRcptHeader.PrintRecords(true);
                end;
            }

    [IntegrationEvent(false, false)]
    local procedure OnBeforePrintRecords(var Rec: Record "Return Receipt Header"; var ReturnRcptHeader: Record "Return Receipt Header")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Deprecation: remove injection of NIR in deeplabv3

Features from #134 are still present in GDL. Have they been used lately? Maybe time for deprecation.

@remtav Do you want me to delete all the deeplabv3_dualhead associated code?

@remtav I close it?

@CharlesAuthier please proceed with removing Deeplav3 dualhead. see models and docs.


Data type returned by text-embeddings-inference does not match the specified type

System Info
docker-compose.yml
version: "3"
services:
  embedding:
    image: ghcr.io/huggingface/text-embeddings-inference:0.6
    container_name: tei_bge
    restart: always
    command: --model-id /data/checkpoints/bge_large/ --dtype float32
    ports:
      - "8080:80"
    volumes:
      - /data:/data
    deploy:
      resources:
        reservations:
          devices:
            - driver: "nvidia"
              device_ids: [ "0" ]
              capabilities: [ "gpu" ]

Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
Describe the bug
When using text-embeddings-inference, I specified --dtype float32, but the data returned seems to be of float16 type.
Steps to reproduce

Start text-embeddings-inference with --dtype float32 specified.
Call the model via the interface.
Check the returned data.

Expected behavior
Expected behavior
I expect the data returned to be of float32 type, consistent with what I specified when starting text-embeddings-inference.
Actual behavior
The data returned seems to be of float16 type.
Additional context
The printout when starting the model is:
Args { model_id: "/dat//rge/", revision: None, tokenization_workers: None, dtype: Some(Float32), pooling: None, max_concurrent_requests: 512, max_batch_tokens: 16384, max_batch_requests: None, max_client_batch_size: 32, hf_api_token: None, hostname: "842c3aa5253b", port: 80, uds_path: "/tmp/text-embeddings-inference-server", huggingface_hub_cache: Some("/data"), json_output: false, otlp_endpoint: None }
An example of the returned data is: [0.03771281, -0.035546724, -0.04045037, 0.04029212, -0.003022021, ...].
Could you please advise on how to ensure the data returned is always of float32 type? Thank you.

I am seeing that this embeddings server causes my classifier to work not as well as when I run the same embeddings model with pytorch. Could this be the reason? It's fast but not working so well?
Also the output numbers have less decimals 18 versus 10.


[move-vm] Revisit session extension API.

This puts the extensions into the Session struct instead of passing them as parameters to exec functions. This design was in some earlier version not possible, as the execute functions had extra type parameters for extensions; however, since we use the new NativeContextExtensions object, its natural and cleaner.
One does now
let session = vm.new_session_with_extensions(remote, extensions);
<<work with the session>>
let (change_set, events, extension) = session.finish_with_extensions()?;

Furthermore the ExecutionResult::Success has been extended to have a new field for extensions, which is a breaking change, but a marginal one.
In this design, if one wants to access the extensions on a failed execution, we can just add another function to the Session API to do so. This is currently not there but can be easily added.
Motivation
Better API.
Have you read the Contributing Guidelines on pull requests?
Yes

/land Thanks for the prompt review.


pipeline run get error message, should be more careful about reading

non-existing keys, also cancel pipeline run if get_logs fails

CLOUDBLD-8220

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates

no rn, fix for unreleased change


Help on skooner and OIDC connect via keycloak?

This is what my client looks like -

My Keycloak is running at http://<IP_ADDRESS>:8080/
This is how my secret looks like
kubectl create secret -n kube-system generic skooner \
--from-literal=url="$OIDC_URL" \
--from-literal=id="$OIDC_ID" \
--from-literal=secret="$OIDC_SECRET"

where
OIDC_URL=http://<IP_ADDRESS>:8080/realms/master
When I login to http://a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com it shows invalid

Anything wrong I am doing or any wrong values that I gave?

oidc with keycloak is anyhow currently broken - see #322

I was able to redirect to keycloak and authenticate but after the the sooner screen is just refreshing and not showing anything.
} POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
[HPM] Error occurred while proxying request a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com/apis/authorization.k8s.io/v1/selfsubjectrulesreviews to https://<IP_ADDRESS>:443/ [ECONNRESET] (https://nodejs.org/api/errors.html#errors_common_system_errors)
Error in proxied request Error: socket hang up
    at connResetException (internal/errors.js:609:14)
    at TLSSocket.socketCloseListener (_http_client.js:401:25)
    at TLSSocket.emit (events.js:326:22)
    at net.js:675:12
    at TCP.done (_tls_wrap.js:568:7) {
  code: 'ECONNRESET'
} POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews
2022-07-21T09:22:50.010Z GET / 200
2022-07-21T09:22:50.321Z GET /static/css/main.ce0f149c.chunk.css 304
2022-07-21T09:22:50.339Z GET /static/css/2.b522e268.chunk.css 304
2022-07-21T09:22:50.628Z GET /static/js/2.23699fe9.chunk.js 304
2022-07-21T09:22:50.635Z GET /static/js/main.519bfd42.chunk.js 304
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
2022-07-21T09:22:50.991Z POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews 401
2022-07-21T09:22:51.005Z GET /oidc 200
2022-07-21T09:22:51.670Z GET /?state=http%3A%2F%2Fa3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com%2F&session_state=b24e6921-20ee-49db-b1cb-2ee8f433f68a&code=4f704a8f-7515-4ae4-b56c-08268e6617ac.b24e6921-20ee-49db-b1cb-2ee8f433f68a.5c6c7280-2da3-444e-b834-9614464d7665 200
2022-07-21T09:22:51.970Z GET /static/css/2.b522e268.chunk.css 304
2022-07-21T09:22:51.979Z GET /static/js/2.23699fe9.chunk.js 304
2022-07-21T09:22:51.981Z GET /static/js/main.519bfd42.chunk.js 304
2022-07-21T09:22:51.986Z GET /static/css/main.ce0f149c.chunk.css 304
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
2022-07-21T09:22:52.401Z POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews 401
2022-07-21T09:22:52.445Z POST /oidc 200
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
2022-07-21T09:22:52.784Z POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews 401
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews -> https://<IP_ADDRESS>:443
2022-07-21T09:22:53.142Z POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews 401

Until the next stable image I built my image from master and it is working with the keycloak: devopstales/skooner:20220802

@devopstales great, thanks for providing this container...

@devopstales can you also share Keycloak details?
"$OIDC_URL"
"$OIDC_ID"
I also used the image built from master.

its OIDC_CLIENT_ID not OIDC_ID -> see README.md https://github.com/skooner-k8s/skooner#troubleshooting
        - name: OIDC_SCOPES
          value: "openid email groups"
        - name: OIDC_URL
          value: "https://auth.example.com/realms/master/.well-known/openid-configuration"
        - name: OIDC_CLIENT_ID
          valueFrom:
            secretKeyRef:
              name: oidc-k8s
              key: OIDC_CLIENT_ID
        - name: OIDC_SECRET
          valueFrom:
            secretKeyRef:
              name: oidc-k8s
              key: OIDC_SECRET

I can confirm that @devopstales image works fine...

Thanks @maltegrosse, I am no expert in Keycloak, can you see the secrets and URLS I used are right ?
id - skooner
URL - http://<IP_ADDRESS>:8080/realms/skooner
redirect URL - http://a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com/*
This is where my skooner is running - http://a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com

better try to setup keycloak properly behind an https endpoint + subdomain and get to used to the basic functionalities...  (there are plenty of tutorials out there). once you 100% sure that its working go further and start again with skooner.. (also use an ingress in front of skooner...)

So if you see above the skooner is the ingress
NAMESPACE     NAME      CLASS    HOSTS                                               ADDRESS   PORTS   AGE
kube-system   skooner   <none>   a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com

Keycloak setup is straightforward... I will recheck - I am pretty sure its one of the URL's -> redirect URL that I am not getting right.

@saiyam1814 I faced similar error when I was using KUBE_CONF file generated by Rancher. Since Rancher usage its own auth proxy, Skooner will not work with it.
When switched to KUBE_CONF context with direct url to cluster, it worked fine with Keycloak+Skooner.

Great @ashokkumarprajapati , I still couldn't make it work
I have these https://github.com/skooner-k8s/skooner/issues/341#issuecomment-1206341794
and I did not run with Rancher generated cluster.
What does your URl's etc looks like in skooner and keycloak?

Hey guys we pushed a new stable version a month ago, would that resolve your issues?

Thanks @maltegrosse, I am no expert in Keycloak, can you see the secrets and URLS I used are right ?
id - skooner URL - http://<IP_ADDRESS>:8080/realms/skooner redirect URL - http://a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com/* This is where my skooner is running - http://a3869259-c651-4eab-be4e-ddcba12856f1.k8s.civo.com

I think it's important to use ingress and use the https endpoint as skooner base URL: elsewise you'll meet "An error occurred during the request TypeError: only valid absolute URLs can be requested"

New stable was released and we fixed two pieces of documentation flaws.
Please follow through with the keycloak troubleshooting section and report any issues with a new ticket or reopen this. Thanks!


Problem building the package

when trying to install newest version (commit ff34cce) I get:
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [35 lines of output]
      Traceback (most recent call last):
        File "/local/home/a.pirogov/.local/share/virtualenvs/irdm-dev-e7pFVQEY/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
          main()
        File "/local/home/a.pirogov/.local/share/virtualenvs/irdm-dev-e7pFVQEY/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/local/home/a.pirogov/.local/share/virtualenvs/irdm-dev-e7pFVQEY/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 320, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 335, in run_setup
          exec(code, locals())
        File "<string>", line 1, in <module>
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 108, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 159, in setup
          dist.parse_config_files()
        File "/local/home/a.pirogov/.local/share/virtualenvs/irdm-dev-e7pFVQEY/lib/python3.9/site-packages/_virtualenv.py", line 21, in parse_config_files
          result = old_parse_config_files(self, *args, **kwargs)
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 881, in parse_config_files
          setupcfg.parse_configuration(
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py", line 163, in parse_configuration
          options.parse()
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py", line 508, in parse
          section_parser_method(section_options)
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py", line 482, in parse_section
          self[name] = value
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py", line 290, in __setitem__
          value = parser(value)
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/_vendor/packaging/specifiers.py", line 711, in __init__
          parsed.add(Specifier(specifier))
        File "/tmp/pip-build-env-gnvw110t/overlay/lib/python3.9/site-packages/setuptools/_vendor/packaging/specifiers.py", line 245, in __init__
          raise InvalidSpecifier(f"Invalid specifier: '{spec}'")
      setuptools.extern.packaging.specifiers.InvalidSpecifier: Invalid specifier: '>=3.7.*'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

This is fixed when using python_requires = >=3.7 (removing the *)

Thanks @apirogov for your report! Much appreciated! :+1:
That's interesting, I never had this problem. Neither in said commit ff34cce and also not for HEAD.
You seem to have used a virtual env. Could you tell me the steps you used? I would like to reproduce that on my machine.
Thanks!

I reproduced this in a fresh venv created with python -m venv (on Python 3.8.15, installed using pyenv)
and in the venv running:
pip install git+ssh://git@github.com/python-semver/python-semver.git@ff34cce

Happens with pip 22.0.4 and also 23.0.1, and it uses setuptools 56.0.0

Thanks @apirogov for your test efforts. If I'm not mislead, I saw this asterisk syntax somewhere else.
Well, it's fixed now so you can use it with any errors. I hope I can build the RC release this week.
Many thanks!

Thanks for the quick reaction :-)


feat: Add execute command to handle Execute code lens

Description
Problem*

Ref https://github.com/noir-lang/noir/pull/2330
Summary*

This adds a nargo.execute command that will be triggered via the > Execute code lens.
Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'm building this with npm run package (and then selecting "Install Extension VSIX" in the sidebar) and running it with Nargo built from your PR. I'm not getting any display and a "Unable to locate any nargo binary. Did you install it?" error.
Should I be doing something different to test this?

So the published extension doesn't work for you either? I use a custom absolute path to my nargo binary since I iterate on the features so I've not experienced this. Seems entirely unrelated to this PR

Yeah, I really doubt it has anything to do with this PR. Just trying to get to a state where I can meaningfully test it.

I don't get any errors on the published extension (v0.0.3) but nothing past syntax highlighting either. I've switched back to the locally installed extension and don't get the error anymore but no output either. Adding an explicit path causes no change.

Ah ha! I've managed to get signs of life.


⚠ Samsung has degraded performance

In 39e7913, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2515 ms

Resolved: Samsung performance has improved in 18052e3.


Advertisement as owner-ref in virtual node

Description
This commit replaces the deployment of the vk previously used as owner
reference in the virtual node with the advertisement

/rebase

/rebase


[SPARK-35972][SQL] When replace ExtractValue in NestedColumnAliasing we should use semanticEquals

What changes were proposed in this pull request?
In our product env, we meet a case that when  matching NestedColumnAliasing.
In the first loop we got nestedFieldReferences as  below,
data.a
data.a.b
data.a.c
data.a.d

then after handle duplicated we got alias map
data.a -> gen_alias_xxxx

but when call replaceToAliases -> getNewProjectList, when replace   data.a.b ,  data.a.c ,  data.a.d  it can't match since we call  map.contains.
Then the nest loop  we got nestedFieldReferences as  below,
data.a.b
data.a.c
data.a.d

but we gen aliasMap as
data -> gen_alias_xxx

data.a.b -> gen_alias_yyy
data.a.c  -> gen_alias_zzz
data.a.d  -> gen_alias_uuu

attrToAliases as
data -> [gen_alias_yyy, gen_alias_zzz, gen_alias_uuu]

since we got the reference as data,
but in current's project 's child's output, we don't contains data since we have replace it to data.a
then the final plan when execute will throw exception like
Couldn't find _gen_alias_yyy#yyy in [.......]

Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manul tested in our prod env.

Ping @cloud-fan @dongjoon-hyun @viirya

Test build #140563 has started for PR 33183 at commit bd8bb1c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45075/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45075/

cc @karenfeng

@AngersZhuuuu can you add a test?

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

+1 for adding test.

updated

Test build #140580 has started for PR 33183 at commit 170520d.

Test build #140563 has finished for PR 33183 at commit bd8bb1c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45091/

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45091/

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

Test build #140580 has finished for PR 33183 at commit 170520d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #140596 has started for PR 33183 at commit d3262ed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45107/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45107/

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

Test build #140596 has finished for PR 33183 at commit d3262ed.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Any more suggestion?

cc @viirya again

Doesn't the query shown in the PR description look the same as sql("select employer.company, employer.company.name, employer.company.address from contacts") in SchemaPruningSuite? It is basically querying a nested struct (employer.company) and a few nested columns inside the struct.
I ran such query in SchemaPruningSuite. It seems working without any error?

Could you provide an end-to-end test case?

Doesn't the query shown in the PR description look the same as sql("select employer.company, employer.company.name, employer.company.address from contacts") in SchemaPruningSuite? It is basically querying a nested struct (employer.company) and a few nested columns inside the struct.
I ran such query in SchemaPruningSuite. It seems working without any error?

Our prod have a very complex job and spark version is 3.1.2. I have tried to put it in UT but it run as normal. But this error actually happen in our prod. With this patch our job can run well.

Test build #140673 has started for PR 33183 at commit d073d7a.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45184/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45184/

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

Our prod have a very complex job and spark version is 3.1.2. I have tried to put it in UT but it run as normal. But this error actually happen in our prod. With this patch our job can run well.

What you mean "you put it in UT but it runs as normal"? Do you mean you put the failed case into UT and it works well?

Our prod have a very complex job and spark version is 3.1.2. I have tried to put it in UT but it run as normal. But this error actually happen in our prod. With this patch our job can run well.

What you mean "you put it in UT but it runs as normal"? Do you mean you put the failed case into UT and it works well?

Yea, it work like sql("select employer.company, employer.company.name, employer.company.address from contacts") as expect.
But in prod it failed because this bug.  Didn't find the reason why cause parse employer.company, employer.company.name's  employer.company yet.
But any way, since we handle duplicated filed use semanticEqual, use semanticEquals here is more rigorous

Test build #140673 has finished for PR 33183 at commit d073d7a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Let me look at this closely.

@AngersZhuuuu Could you update the PR description with the root cause https://github.com/apache/spark/pull/33183#discussion_r664272768? The current description is verbose and difficult to know what the root cause to fix here. Thanks.

Put this in comment for easy understand this issue
In our product env, we meet a case that when  matching NestedColumnAliasing.
For input plan

Project [struct_data#6.search_params AS value#7, struct_data#6.search_params.col1 AS col1#8, struct_data#6.search_params.col2 AS col2#9]
+- Repartition 100, true
   +- LocalRelation <empty>, [struct_data#6]

In the first loop we got nestedFieldReferences as  below,
struct_data.search_params
struct_data.search_params.col1
struct_data.search_params.col2

then after handle duplicated we got alias map
struct_data -> struct_data.search_params

nestedFieldToAlias as
struct_data.search_params -> (struct_data.search_params as extract_search_params)

attrToAliases  as
struct_data -> [struct_data.search_params as extract_search_params]

but when call replaceToAliases -> getNewProjectList, when replace   struct_data.search_params.col1 ,  struct_data.search_params.col2   it can't match  struct_data.search_params since we when call  map.contains and they don't have same construct method.
we can get result plan as
Project [_extract_search_params#12 AS value#7, struct_data#6.search_params.col1 AS col1#8, struct_data#6.search_params.col2 AS col2#9]
+- Repartition 100, true
   +- Project [struct_data#6.search_params AS _extract_search_params#12]
      +- LocalRelation <empty>, [struct_data#6]

Then in the second loop  we got nestedFieldReferences as  below,
struct_data.search_params.col1
struct_data.search_params.col2

but we gen aliasMap as
struct_data -> [struct_data.search_params.col1, struct_data.search_params.col2]

nestedFieldToAlias as
struct_data.search_params.col1 -> extract_col1
struct_data.search_params.col2  -> extract_col2

attrToAliases  as
struct_data -> [extract_col1, extract_col2]

since we got the reference as struct_data,
but in current's project 's child's output, we don't contains struct_data col since we have replace it to data.a
then the final plan will be as below
!Project [_extract_search_params#16 AS value#7, _extract_col1#17 AS col1#8, _extract_col2#17 AS col2#9]
+- Repartition 100, true
   +- Project [struct_data#6.search_params AS _extract_search_params#16]
      +- LocalRelation <empty>, [struct_data#6]

when execute will throw exception like
Couldn't find extract_col1#14in [_extract_search_params#16]

@AngersZhuuuu Could you update the PR description with the root cause #33183 (comment)? The current description is verbose and difficult to know what the root cause to fix here. Thanks.

Done

Thanks. Merging to master/3.2.

We have a refactoring before. So this conflicts in branch-3.1. Could you backport to 3.1?

We have a refactoring before. So this conflicts in branch-3.1. Could you backport to 3.1?

Sure


Splitting Swagger object descriptions

Hi Robert,
This is a suggestion for enhancement.  In addition to the definitions.adoc that gets generated, I would like to generate individual files for each object (ex: person.adoc, address.adoc, purchase.adoc ...). I'd like to reference the model from a separate document that I've written, but I would like to include the object definitions individually in specific sections rather than in a single section. Do you think this would be something useful? I haven't dived into the code yet, but I'd be willing to take a stab at it. Do you think it would be something horribly difficult as the design stands, and would it be something possibly useful to others?
Thanks!
Sebastien

Hi,
I like the idea. But this feature would mean a refactoring, which breaks backwards compability.
But the project needs a refactoring anyway. Maybe its time for a new refactored Version.
Kind regards,
Robert

Hi Robert,
I went ahead and tried my hand at implementing a solution.  I've created PR https://github.com/RobWin/swagger2markup/pull/19 so you can take a look and let me know what you think.
Thanks!
Sebastien

Hi Sebastien,
thank you very much. I like it when people show their own initiative an create PRs.
I will have a look at it.
Thx

Your PR looks good and it is a good temporary solution.
But Swagger2Markup definitely needs a refactoring, because the design is not flexible enough for further extensions. The design should be more composable.
I think I merge the PR, but will start refactoring soon.

If you like, you can join the Gitter channel:
https://gitter.im/RobWin/swagger2markup

I keep the issue open, until the PR is released

Thx for your contribution!

I referenced your PR in the Community contributions chapter


Refactor serving metrics to be more generalizable+extendable

Implemented with https://github.com/trustyai-explainability/trustyai-explainability/pull/281


Support TS for Range, RangeInclusive, Path, PathBuf

Most types are already covered by ts-rs, but the stdlib contains a few more ones that would be useful to have.
This is a list of what is included in serde by default, it would probably make sense to support most of these in ts-rs as well: https://docs.rs/serde/latest/serde/ser/index.html

Fixed in 6.1.1

Thanks! :D


Update OWNERS to reflect current being status

@Honry @Shao-Feng please take a look at this, thanks.

LGTM


Accessing Franka Control Buttons from ROS

Hi,
Is it possible to access the Franka control buttons at the end effector from ROS?
Thanks

Unfortunately, this is currently not possible.


Draft to refactor query execution with retry

Some notes I had in mind:

we want a retry on 3 types of requests: fetch docs request, search request, search stream request
we distribute those types of queries according to split id. Getting the list of queries to send to nodes is a sort of query plan
it should be possible to share the code between those types of requests

I think I would remove the root out of the picture here and just focus on the problem of "how do I refactor the code that dispatch tasks to leaves, get back the results and retries if necessary".
The root stuff seems less easy to refactor, and also yields less benefit I believe.
... also I would ideally find another word than ExecutionPlan. That term has usually a different meaning.
Maybe QueryPlacement?

Yes, this is too early to refactor as is. With issue #422 it's clear that we need some scheduling and some query prioritization strategy.

Closing it in favor of #498


Fixed UI was not updating health, mana, and stamina UI elements

I looked at your UI_HUD and it didn't show any changes. I'm guessing that you just tried setting the blueprint node inline Attribute variables back to Health, Mana, and Stamina. 4.23 has a bug where inline node Attribute variables reset back to "None" when the blueprint is compiled. The workaround is to create blueprint variables of the Attributes and plug those into the nodes. I added the blueprint variable fix to Master. The bug is fixed in 4.24.

Yes, they were all set to None in my UI_HUD Blueprint. Didn't know about that bug. Thanks for fixing it the right way then. :-)


Speed up re-signing via per-file hash

Certain models like huggingface repositories currently do not support versioning. This means that signing multiple times with small diffs can be expensive. It may be useful to have a format listing per-file hashes, in order to speed up re-hashing. Example:
path/a/b ...hash1...
file2       ...hash2...

This file would be kept under the model folder or in another configuration folder (probably the latter?). When signing, the caller would give us a list of files that need to be re-computed (from git diff), and our library would only re-hash the necessary files. We'd also pass back the recomputed file to the caller, so that they can store it where they want. The user would need a git hook that does all this for them.
This file could be the final file we sign, or a helper file that is only stored on a dev machine to speed up signing when making changes to the repo. (probably the latter?)
The main danger (?) is that:

If someone edits the file (by mistake), we'd be re-computing the hash wrong.
Folks start sharing this file. It would only take one bad actor to backdoor the model for multiple users (?)

@McPatate any thoughts?

Certain models like huggingface repositories currently do not support versioning.

Do you mean per-file versioning? You have access to a git log, which can be interpreted as a versioning system since you know if a file changed across commits & the commit id being the version.
Regarding 2., could we not sign the file each time it's changed?

Certain models like huggingface repositories currently do not support versioning.

Do you mean per-file versioning?

No, just repository versioning.

You have access to a git log, which can be interpreted as a versioning system since you know if a file changed across commits & the commit id being the version.

Correct. I thought the huggingface API did support git versioning and it could only download at head. I was wrong. from_tretrained supports git tag, called revision (https://huggingface.co/docs/transformers/main_classes/model). So effectively users can tag upon release. I don't think the feature is commonly used by users today.. but maybe that's fine?

Regarding 1., we could encode the file in a binary format that is not human readable.
Regarding 2., could we not sign the file each time it's changed?

+1, I had a similar idea. I think that should work.
@McPatate do you think we need this optimization at all? The motivation was to improve signing speed because we thought that model versioning was not supported by the huggingface API, but that assumption was wrong. Do you think it'd be enough to:

Nudge users to version their models (git tag)
Provide a CLI they can run when they push a tag. (the CLI in this repo when it's v1 ready)

If users version their models, they'd only need to sign when the model actually changes.. which means they need to re-sign large files and cannot use the per-file hash anyway... Wdut?

Closing in favor of https://github.com/google/model-transparency/issues/111


Destroying the existing Template and establishing the proper routes for that

This user story entails removing a specific template from the database and subsequently incorporating the necessary routes to support this deletion, ensuring a seamless and efficient process for template management.


prometheus data loss with error "Error indexing label pair to fingerprints batch...."

I am using kubernetes + prometheus + node exporter for node cpu/memory/disk monitor. Now the prometheus work very unstable. I have 3 node in kubernetes, at first it lost cpu data on node1 and node2, after restart it lost cpu data on node1 and disk data on node3. I found below errors in logs:
time="2017-06-06T11:03:39Z" level=warning msg="Flag -storage.local.memory-chunks is deprecated. Its value 2097152 is used to override -storage.local.target-heap-size to<PHONE_NUMBER>." source="config.go:317"
time="2017-06-06T11:03:39Z" level=info msg="Starting prometheus (version=1.6.3, branch=master, revision=c580b60c67f2c5f6b638c3322161bcdf6d68d7fc)" source="main.go:88"
time="2017-06-06T11:03:39Z" level=info msg="Build context (go=go1.8.1, user=root@a6410e65f5c7, date=20170522-09:15:06)" source="main.go:89"
time="2017-06-06T11:03:39Z" level=info msg="Loading configuration file /prometheus/prometheus-sailoros.yml" source="main.go:251"
time="2017-06-06T11:03:39Z" level=info msg="Loading series map and head chunks..." source="storage.go:421"
time="2017-06-06T11:03:39Z" level=info msg="0 series loaded." source="storage.go:432"
time="2017-06-06T11:03:39Z" level=info msg="Starting target manager..." source="targetmanager.go:61"
time="2017-06-06T11:03:39Z" level=info msg="Listening on :9090" source="web.go:259"
time="2017-06-06T11:03:39Z" level=info msg="Using pod service account via in-cluster config" source="kubernetes.go:94"
time="2017-06-06T11:03:39Z" level=info msg="Using pod service account via in-cluster config" source="kubernetes.go:94"
time="2017-06-06T11:03:51Z" level=error msg="Error indexing label pair to fingerprints batch: open data/labelpair_to_fingerprints/000002.log: no such file or directory" source="persistence.go:1410"
time="2017-06-06T11:03:51Z" level=error msg="The storage is now inconsistent. Restart Prometheus ASAP to initiate recovery." error="open data/labelpair_to_fingerprints/000002.log: no such file or directory" source="persistence.go:415"
time="2017-06-06T11:03:59Z" level=error msg="Error indexing label pair to fingerprints batch: open data/labelpair_to_fingerprints/000002.log: no such file or directory" source="persistence.go:1410"
time="2017-06-06T11:08:39Z" level=info msg="Checkpointing in-memory metrics and chunks..." source="persistence.go:633"
time="2017-06-06T11:08:39Z" level=error msg="Error while checkpointing: open data/heads.db.tmp: no such file or directory" source="storage.go:1468"
time="2017-06-06T11:13:39Z" level=info msg="Checkpointing in-memory metrics and chunks..." source="persistence.go:633"
time="2017-06-06T11:13:39Z" level=error msg="Error while checkpointing: open data/heads.db.tmp: no such file or directory" source="storage.go:1468"
time="2017-06-06T11:18:39Z" level=info msg="Checkpointing in-memory metrics and chunks..." source="persistence.go:633"
time="2017-06-06T11:18:39Z" level=error msg="Error while checkpointing: open data/heads.db.tmp: no such file or directory" source="storage.go:1468"
Could you help about this? Thanks you very much!

seems due to ssd unstable, after change to another env without ssd, it works


Setting RoslynToolPath to allow ASPX compilation with newer language versions

Hey @CZEMacLeod! 👋🏻
Thanks for stepping up and creating this amazing SDK 🙏🏻
What do you think about setting RoslynToolPath in the SDK to allow the Roslyn CodeDOM provider to pick up the newer version of the compiler?
We've solved this by using GeneratePathProperty on PackageReference:
<ItemGroup>
  <PackageReference Include="Microsoft.Net.Compilers.Toolset" Version="4.5.0" IncludeAssets="none" PrivateAssets="all" GeneratePathProperty="true" />
</ItemGroup>

And then setting RoslynToolPath:
<PropertyGroup>
  <RoslynToolPath>$(PkgMicrosoft_Net_Compilers_Toolset)\tasks\net472</RoslynToolPath>
</PropertyGroup>

This allows us to pass /langversion:11 to the CodeDOM provider and compile our ASPX-files using the newest version of the language.
Are you willing to accept a PR for this?

@khellang As a temporary work around until something is figured out, perhaps something like the following in your Directory.Build.targets would get you what you need.
<ItemGroup>
  <PackageReference Update="Microsoft.Net.Compilers.Toolset">
    <GeneratePathProperty>true</GeneratePathProperty>
  </PackageReference>
</ItemGroup>

This Sdk's default/automatical inclusion of the Microsoft.Net.Compilers.Toolset PackageReference will happen before Directory.Build.targets is processed, so using an update style statement there would allow you to set the GeneratePathProperty .

I have everything working nicely, so no need for a workaround. I was simply pitching it to be included in the SDK by default ☺

@khellang I've pushed a small update V4.0.88 which should now natively do this.
I thought the Microsoft.Net.Compilers.Toolset package set the RoslynToolPath property internally (and I'm slightly surprised it doesn't).
There is an internal property _RoslynTasksDirectory which is used by MSBuild, but not a TargetFramework (or resolved framework) based one for RoslynToolPath.
This change was included as part of some other ongoing work, but in general, I love feedback and enhancements and generally accept PRs.

It does set it, but it brings its own version of the compiler, matching the version number. So currently the latest version is 3.6.0. This results in the older version of the compiler being used for dynamic compilation at runtime, not the version from the Toolset package ☺

@khellang I think that is where I got confused. Microsoft.CodeDom.Providers.DotNetCompilerPlatform seems to embed a couple of versions of Roslyn depending on the target version of .net and yes - it sets RoslynToolPath based on the last version of Microsoft.Net.Compilers that was embedded in the package.
I thought that Microsoft.Net.Compilers.Toolset (the replacement for Microsoft.Net.Compilers) set RoslynToolPath to point to the newer version included. However, it isn't quite that simple as the version required at runtime and the version require for MSBuild are not the same.
In our case, the SDK only support V4.7.2+ of .NET Framework so it is easier to manage this.
Regardless, the new SDK version does the magic and sets the property from the package using the method you mentioned so no more mismatches between build time and runtime compilers.
Thanks for the input and the clarifications.

Yeah, the change looks good 😎 Thank you so much! 👍🏻


Sequence of execution of functions in setup arduino sketch

Hi Wolfgang Ewald,
In the setup function call of [MPU9250_acceleration_data.ino] sketch, there is a comment before the setSampleRateDivider function to call this function only if the DLPF filter is enabled. But, the DLPF enable function call is made later. What is the sequence to  follow? I altered the function calls, but do not see any difference in output values.

Hi,
the sequence doesn't matter. And at least I see differences if I change the DLPF. You need to look at the raw values. Here I have taken the unchanged settings, i.e. DLPF = 6. The module was just lying unmoved on the table. To see more values to compare I only printed the corrected raw values.

And here I have changed the DLPF to 0 and you will get similar results if you deactivate the DLPF with  enableAccDLPF(false). Just commenting out is not enough as documented in the tutorial and the function list.

I would say this is quite a difference in noise.
To check if the sample rate divider works I have set the sample rate divider to 255. That means the output rate is 4 Hz. In order to see the effect you need to have an output rate on the serial monitor which is higher. I have applied reduced the delay of 100 ms in the example sketch and as expected I saw that only every second to third value is a new one:

I also applied a sample rate divider of 1 and as expected after 100 ms I always got a new value.

So, DLPF and a sample rate divider are working.
The interesting thing I found is that the the sample rate divider seems to work even if I deactivate the DLPF or set it level 0 or 7.

But since I don't know if there are maybe different generations of the MPU9250 which behave diffenrently, I keep the comment.

@RamkumarGorre , can I close this issue now? Or are you still checking?

Hi Wolfgang Ewald,
You can close this case. Thanks for your support.
regards,
Ram Kumar Gorre
On Thu, Jul 28, 2022 at 12:07 PM Wolfgang (Wolle) Ewald <
@.***> wrote:

@RamkumarGorre https://github.com/RamkumarGorre , can I close this
issue now? Or are you still checking?
—
Reply to this email directly, view it on GitHub
https://github.com/wollewald/MPU9250_WE/issues/8#issuecomment-1197726113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ24GFWJTBFVZXONA7CB3YDVWITC7ANCNFSM53NAK7RQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
The information contained in this electronic communication is intended
solely for the individual(s) or entity to which it is addressed. It may
contain proprietary, confidential and/or legally privileged information.
Any review, retransmission, dissemination, printing, copying or other use
of, or taking any action in reliance on the contents of this information by
person(s) or entities other than the intended recipient is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us by responding to this email or telephone and
immediately and permanently delete all copies of this message and any
attachments from your system(s). The contents of this message do not
necessarily represent the views or policies of BITS Pilani.


Problem Trying to get monitor capture

[zoom_and_follow_mouse.py] {}
[zoom_and_follow_mouse.py] Traceback (most recent call last):
[zoom_and_follow_mouse.py]   File "C:\Program Files\obs-studio\OBS PYTHON\zoom_and_follow_mouse.py", line 371, in toggle_zoom
[zoom_and_follow_mouse.py]     zoom.update_source_size()
[zoom_and_follow_mouse.py]   File "C:\Program Files\obs-studio\OBS PYTHON\zoom_and_follow_mouse.py", line 66, in update_source_size
[zoom_and_follow_mouse.py]     data = loads(data)['monitor']
[zoom_and_follow_mouse.py] KeyError: 'monitor'

it supports only Window Capture

I have the same issue

Please try the most recent commit, I believe this is an issue with single monitor setups. There is a patch for that behavior. If the issue persists, please let me know and I will reopen the issue.


fix: export WithTranslation props type for typescript

Fixes #360
WithTranslationHocType is a new type that's used internally to type withTranslation HoC.It has been previously called WithTranslation.
That resulted in a name clash since react-i18next exports its own WithTranslation interface. This interface is the interface of the pros injected by withTranslation HoC (yes that naming is quite counter-intuitive).
The issue was missed in the tests because the dummy component was not typed.

Can you please explain your changes here, and the need for two withTranslation types?

@isaachinman I updated the description

@Averethel If you check the history of this file, you will see we've flip-flopped on this withTranslation value several times now. Are we absolutely sure this accomplishes everything surrounding withTranslation?

@isaachinman Yeah I just browsed and realized what was going on. It depends on what the vision is.
I see next-i18next as the only i18n related dependency I need in my next project. For that to work (if I'm using typescript), I need to be able to get the i18n related types that I need in my project so they need to be re-exported.
Of course, there are alternatives:

importing them directly from the source, but then I'm in i18n dependency hell where I need to have react-i18n dependency version matching the one used in next-i18n, plus I'm adding it to only get a type
declaring the prop type myself, but then I need to keep it in sync with what react-i18next is declaring and I risk unexpected errors
Of all the 3 re-exporting the types seem like the cleanest and most user-friendly to me.

I see next-i18next as the only i18n related dependency I need in my next project

Yes, that's right. All typing should be available via next-i18next. We need to re-export.

@isaachinman any news?


License

Hi!
I'm from ReDrawing team for the OpenCV AI 2021 competition, and we used a part of this repository code. We noticed that the repository don't have any license, so we can't derive from it, technically not even run it.
If not on purpose, could you please add a license? We also used your
depthai_hand_tracker project. Here some help about licenses.
Our project repository: link

I am not familiar with licensing, that's probably why I always forget to include one :-))
Here, as I am using models from Mediapipe which under Apache 2.0 license, do I need to use the same or can I use directly MIT license ? It is not clear to me. Do you know ?

I'm not too familiar either. For what I know, yes, you can use the MIT license, but you need to keep the original license file and also explicitly say if you modified any original file.

Repo updated with MIT license. Will do on depthai_hand_tracker too.


labelExtractor doesn't affect initial value

It doesn't seem like passed in via the value prop are run through the labelExtractor if set.
For example, if I have an array of objects with a label property containing uppercased labels, and a labelExtractor that lowercases them, the initial value appears uppercase, unformatted. The values are only lowercased in the dropdown list and after an option has been selected, but even then, the unformatted label appears first for a split second.

Nevermind, I think I was passing values incorrectly which was resulting in the reported behavior.


[nitpick] padding for login nudge is tight

this isn't a big deal, but the padding in the login nudge is a little snug

I just realized that #412 was intended to fix a different issue — this isn't a nav thing


Add test ci

Add test action and golangci-lint action

Bump patch version to push version tag image to ghcr.io.

Test workflow works fine.
https://github.com/FeLvi-zzz/tentez/actions/workflows/test.yaml


Feat/add dark mode

fixes #48

[X] Move project from css to scss to easy change dark and light mode.
[x] Create a service to switch between styles.

Great job @sanchis thx a lot 🔥
I added you to contributor list in readme

Great job @sanchis thx a lot 🔥
I added you to contributor list in readme

Thanks!! 🤘


Update tutorial for vm1.3.1

I'm getting an error when running the deploy-multisig.ts script in this tep:
  const tx = await aaFactory.deployAccount(
    salt,
    owner1.address,
    owner2.address,
    { gasLimit: 500000 } // added later
  );
  await tx.wait();

Without gasLimit, it fails with:
Error: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"error\":{\"code\":3,\"message\":\"Failed to submit transaction: cannot estimate transaction: out of gas.\",\"data\":{\"code\":104,\"message\":\"cannot estimate transaction: out of gas.\"}},\"id\":50}\n","error":{"code":3,"data":{"code":104,"message":"cannot estimate transaction: out of gas."}}

Setting gasLimit: 500000 the transaction goes through but fails. For example https://goerli.explorer.zksync.io/tx/0xdd79071f9998794884596c6be76b21d0531c11c37e55af052c9bea40ae8600bb


[Text Translation] Preparation for 1.0.0-beta.1 release

Preparation for Text Translation SDK release, version 1.0.0-beta.1.

API change check
API changes are not detected in this pull request.


Remove stale information about apiVersion.

Removing stale information, referring to apiVersion change in v1.9.

/lgtm
/approve


Added password attacking tools in main readme

You are always welcome to contribute!!
Looking forward to hearing from you.


Calibrated Laser Targeting

Hi, great work on the program! I use it all the time. Would you mind adding Calibrated Laser Targeting's ability to add 1 focus result? I think there are actually a couple of other cards it would be useful for as well.

Yes, definitely on the todo list! Hoping to get to a few of the smaller effects from Wave 3 (including CLT) later this week.


dependency: upgrade TiDB dependency

What problem does this PR solve?

Issue Number: close #4298
What is changed and how it works?
Check List
Tests

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

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update key monitor metrics in both TiCDC document and official document

Release note
None

/run-all-tests

/run-all-tests

/run-kafka-integration-test

/merge

/run-all-tests

/run-kafka-integration-test


Helm needs a complete template function reference

A very common issue users have writing charts is not knowing what chart functions are available, how to call them, and what their behavior is.  It would be good to have a nicely formatted complete reference:

Functions by category with an alphabetical index
Arguments they take and their types
Expected output
Examples of how they could be used in charts (example arguments, a template snippet, and the rendered output)

This will be somewhat duplicative of the upstream docs for gotpl and Sprig, but especially the last point I think would be useful for new chart authors.

I just wanted to chime in and say that the lack of function documentation has been a huge hinderance to my ability to adopt Helm.  There are so many useful functions (e.g. AsConfig/AsSecrets) simply mentioned in passing in the documentation examples but they're never fully elaborated upon.  It makes me wonder how many useful tools I have at my disposal that I simply don't know exist because they're not documented.
I don't need anything fancy.  Just a list of functions, their parameters, and a brief description of what they do.

PRs welcome: https://helm.sh/docs/chart_template_guide/functions_and_pipelines/

The people looking for the documentation are not the people with the knowledge to write a PR for it, by definition.

The ticket’s been open for 2 years. I’m closing it due to inactivity.

For me, it does not make sense closing the issue without anything actually been done.
Current documentation on functions sounds just ridiculous:

Helm has over 60 available functions. Some of them are defined by the Go template language itself. Most of the others are part of the Sprig template library. We'll see many of them as we progress through the examples.

and then gives example of 3 of them

Some seem to have been added by this PR https://github.com/helm/helm-www/pull/700

I believe this issue is still valid just as before and must be reopened.
Although there is this "functions list" https://helm.sh/docs/chart_template_guide/function_list/ it is far from being complete.
Just today I was working on a chart using I dare to say pretty basic functions like "join", "split" and "index". None of them is listed in that function list. Which is frankly embarrassing.


feat: add grafana support as metrics service

As titled.
Usage:

Run ./run d to bootstrap prometheus and grafana service.
Run with RUNKV_METRICS=true.
Access grafana at http://localhost:3000.

Overview:

Ref: #66 .

@ytaoeer You can refer to this PR to add metrics.


influxdb: document which paramters may be used from triggerauthentication

This updates the influxdb scaler docs for 2.4 to state which parameters can be specified from (cluster)triggerauthentication, as a followup to https://github.com/kedacore/keda/pull/1904
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)
[x] A PR is opened to update the documentation on our docs repo

Is there an example scaler that's formatted the way we want? I'm having a hard time understanding what needs to be changed.

I have added some more suggestions which hopefully help but https://github.com/kedacore/keda-docs/blob/master/content/docs/2.4/scalers/azure-service-bus.md is typically the one I refer to

@acobaugh do you think you'll have a time to finish this PR?

Thank you! Can you have a look at https://github.com/kedacore/keda-docs/pull/472#discussion_r659206737 please?

Hi @acobaugh ,
Could you add it also to version 2.6?


update metadata link

Updated link to use Apache licensed tarball created from oamg/leapp-repository.

@heatmiser, as discussed...


explicit example section to prompt

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls


fix(codegen): preserve parentheses for ChainExpression

close: #6385
The fixing way was referenced from esbuild, it is according to these states(determined in the parser) to determine whether to print parenthesis
￼Due to differences in implementation details, we are unable to record certain information like esbuild does in its parser. But fortunately, The ParenthesisExpression AST is actually like what esbuild stored states.

[!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

#6430  👈
#6429
main

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

Join @Dunqing and the rest of your teammates on  Graphite

The minifier removes parenthesized expressions, this is difficult :-(

The minifier removes parenthesized expressions, this is difficult :-(

I've found that esbuild will preserve parenthesis for ChainExpression even if minify is enabled. So it is possible not to remove ParenthesizedExpression if its inner expression is ChainExpression?
Please check out https://esbuild.github.io/try/#dAAwLjI0LjAALS1taW5pZnkAZyA9IChhPy5iKS5j

Merge activity

Oct 13, 4:03 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Language bar links exclude files within language groups from search queries

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
Files with parent languages (files with prefixed file extensions that are consolidated into language groups) are excluded from the search results pages that Linguist links to in the language bar. For example, this repository reports "3.7% HTML" usage but when clicking the link in the language bar to view those files, GitHub says it couldn’t find any code. To view those files the user has to click the HTML+EEX link in the languages sidebar.
Ideally names within language groups would be combined in the link's search query but I'm not sure if GitHub's web search endpoints support this. Another idea is to have the most prevalent extension within the language group take precedence. So if I mostly have EEx templates in my repo, the "HTML" link would pass a l=html%2Beex query instead of l=html.
URL of the affected repository:
All repositories with files containing prefixed file extensions that are aggregated into language groups (.html.erb, .html.eex, etc.)
Last modified on:
2019-07-27
Expected language:
N/A
Detected language:
N/A

That's an old, known issue on GitHub NS side :(
/cc @lildude

That's an old, known issue on GitHub NS side :(

Yup. Linguist is responsible for the grouping, but the main GitHub app is responsible for the search behaviour so not really something Linguist can control short of not grouping. As per the discussions in https://github.com/github/linguist/issues/4291 this would be a case where the grouping makes sense and isn't likely to change.

Closing as this isn't a problem with Linguist.


Point at the official website

@scottfrazer @knoblett can you two check this out?

uhh I didn't think we were gutting the whole entire thing...  those are good examples which just need a little bit of updating!  It'd be a shame to lose them entirely... and also the website doesn't (yet) entirely cover these examples.  For example, I was unable to find an example that used a read_int function
If we're going to remove them from this README, can we make sure all concepts are exercised in these examples are also on the web site in some form?

Oof that does seem a bit extreme. I would recommend copying that content to a separate document that is labeled as a developer-oriented resource.

@scottfrazer The gutting part is what I was asking about earlier, not updating them. I think the less overlap we have with the website the better - @vdauwera @knoblett can we get richer examples on the website at some point in the not too distant future?

Certainly we can plan to add examples to cover all of this on the website -- how about creating issues to that effect in this repo?

@vdauwera All of it or just the stuff which doesn't overlap with the site? The fact that we have this issue here demonstrates the pain of having the same effective stuff in multiple places

@vdauwera my last comment was in response to your comment prior to the issue filing btw.

@geoffjentry Yep, got that. I'm reluctant to get rid of any of that content right away because I wonder if it might be useful as an orthogonal approach aimed at developers. I'd like to keep it in the back pocket until we've had a chance to get more feedback on how different types of people feel about the website content and presentation.

So I guess I'm saying, keep the whole thing on the side for now, with the possibility of removing it entirely a few months down the road.

Well sorry I misunderstood you... I don't think we should remove these until the web site covers these concepts sufficiently... I know that people have used and liked these examples!  It'd be a shame to remove them with only a promise that eventually they'll be added to the web site again... I'll very gladly fix these docs this weekend if that's what it'll take

@vdauwera I was hoping to avoid having to actually fix what's broken in there, doh ;) I'll close this for now, may or may not get around to fixing the examples & moving them

Well it would still be good to add the reference to the website (the first paragraph you added) and maybe state explicitly that there are these two types of docs -- say "read on for a developer-oriented quick-start doc, or head over to the website for more hand-holding"


failed install

Installing dependencies ...
bash: line 112: npm: command not found
Unable to install dependencies!
MagicMirror Version: Now that the versions have split, tell us if you are using the PHP version (v1) or the newer JavaScript version (v2).
Description: Provide a detailed description about the issue and include specific details to help us understand the problem. Adding screenshots will help describing the problem.
Steps to Reproduce: List the step by step process to reproduce the issue.
Expected Results: Describe what you expected to see.
Actual Results: Describe what you actually saw.
Configuration: What does the used config.js file look like? Don't forget to remove any sensitive information!
Additional Notes: Provide any other relevant notes not previously mentioned. This is optional.

Make sure you have node and npm installed. Test with node -v and npm -v

Please refer to http://forum.magicmirror.builders for support and troubleshooting.
I'm closing this issue for now. If you feel this issue should remain open, please let me know.


Projects in the Visual Studio solution in the dev branch won't load in VS2015

After cloning the dev branch to my machine, I tried to open the Mvc.sln in VS2015. However every single project failed to load due to:

and:
error  : The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DNX\Microsoft.DNX.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.  D:\Source Control\GitHub\AspNet\Mvc\src\Microsoft.AspNet.Mvc.Xml\Microsoft.AspNet.Mvc.Xml.xproj

Any suggestions on what could be wrong?

The .xproj files include references to $(VSToolsPath)\DNX, which seems to be $(VSToolsPath)\AspNet on my machine. Updating those references seems to work, but is probably not a good idea. Any suggestions on how I might have ended up with the wrong things?

I've dropped VS entirely, favouring dnu build. However, I don't have a working local copy either. Word has it that the next CTP drop will have xproj support, but that's all conjecture. Maybe someone else has more definitive news?

If you just want to play around with the code in VS, you can modify the xproj file by changing
$(VSToolsPath)\DNX\Microsoft.DNX.Props and $(VSToolsPath)\DNX\Microsoft.DNX.targets with $(VSToolsPath)\AspNet\Microsoft.Web.AspNet.Props and $(VSToolsPath)\AspNet\Microsoft.Web.AspNet.targets
That seems to work at the moment. I assume the props and targets used in the xproj-files will be added in a future VS drop or something... Or I just have a messed up environment...

@ChrisKlug your environment is not messed up.  You simply have older VS tooling than we currently need to use.  That tooling has not yet been released but should be soon.  Switching to the older paths is a fine temporary workaround.  The other option is to use one of our older branches -- something still using the older paths.

Unfortunately the latest ASP.NET 5 bits from our dev branch are not compatible with Visual Studio 2015 CTP 6. We will be releasing new tooling soon that will address this issue. Thank you for your patience!