Ruckus certificate script not working

Thanks for the script
however, it seems to not work with Unleashed 200.14 atleast.
Tried to tweak it a bit (Effective URL say 404, so used admin/login.jsp for CSRF, but the tr -d cut it all, so removed it)
still, can't make it work :q/

What are you running it from? pfSense? or a Linux distro?

OPNsense actually, BSD.

And you've setup split DNS for the FQDN you're using for Unleashed? I.e. you can ping the FQDN and it returns your unleashed master IP?

OK. I just ran the script from the commandline of a pfSense box (BSD) to an AP running Unleashed <IP_ADDRESS>.199. It worked OK.

And you need to make sure you've replaced myruckususername and myruckuspassword with your actual Unleashed admin user and password, that the paths to the fullchain and key files are correct, and the fullchain is for either your AP's fqdn or a wildcard at the same level as your AP's name.
Then you're calling the script with the fullchain, key & fqdn as args, e.g. (for a wildcard cert) /path/to/export_zd_cert.sh /path/to/churator.net.fullchain /path/to/churator.net.key unleashed.churator.net

Hi @Churator. Do let me know if my comments helped you to get this working, so I can close the issue

Hi
I can't make it work from OPNsense CLI, but I'll keep trying since you verified its working.


test: add test for getEmbedConfig

The new test will probably failed, until fixed inside Flat.

rebased

Fixed internally in flat/flat#6403, for WebApp release 35.90.0.


Improve fake k8s client object tracking

We are currently using a fake k8s client to mock our interactions with the K8s API, however the client is not very good at tracking objects sent to the cluster via the Apply method. There is a hook in there but it needs to be wired in a lot of cases where the tests are checking code that uses the Apply method in order for the objects to be properly managed. We can simplify this by using the object tracker in a better way and adding objects to it and only using the pre-apply hook to check the object that was passed to the method or return an error if we wish to

fixed https://github.com/ocurity/dracon/pull/200


Fix issue #50 by adding package_base, but without changing current behaviour

As mentioned in the title, this is a fix for #50 which I've tested at this repository and correctly allows controlling the package base without changing the default.
Setting the default on line 303 to "" would allow the default to be changed, introducing breaking behaviour.

@googlebot I signed it!

@googlebot I signed it!

@googlebot I consent.

Thanks for doing this.


Feed URL
https://www.jackfranklin.co.uk/feed.xml
More Info
No response

fixed in https://github.com/murtuzaalisurti/rssed/commit/463cb1711638319f9ce32925b64e0233e83cdd41


Confusing phrasing in README.md

"Errors that occur in the middleware added before the error middleware will invoke this middleware when errors occur."
WTF?

Hi, @tomers, thanks for the feedback! I tried to make some adjustments to better this, but I'm not sure if it helps. If you are not satisfied with the new wording, please make a PR with your suggested wording :)


rosbridge_suite: 0.10.1-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosbridge_suite to 0.10.1-0:

upstream repository: https://github.com/RobotWebTools/rosbridge_suite
release repository: https://github.com/RobotWebTools-release/rosbridge_suite-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.9
previous version for package: 0.9.0-0

rosapi

No changes

rosbridge_library
* Inline cbor library (#377 <https://github.com/RobotWebTools/rosbridge_suite/issues/377>)
  Prefer system version with C speedups, but include pure Python implementation.
* Contributors: Matt Vollrath

rosbridge_server

No changes

rosbridge_suite

No changes

https://github.com/RobotWebTools/rosbridge_suite/issues/368

close and reopen to retrigger travis


Command in double

Hello
The Matter Plug in find my Philips Hue Bridge (they have the Matter Beta)
For all Lights the command are in double usable but they have for (see the picture)
And juste for the esthetique, they have no icon

Matter bridge device support is not yet ready. Please use an already supported device type to try out Matter.
I expect/hope to work out the latest issues with bridges for next HA release.


[WIP] Coarse global search

Just starting work. Everybody is welcome to contribute. Only the simplest constructor code is in right now. The real works has not been started yet.

Codecov Report

Merging #222 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #222      +/-   ##
==========================================
+ Coverage   97.34%   97.39%   +0.04%
==========================================
  Files          42       45       +3
  Lines        1960     1994      +34
==========================================
+ Hits         1908     1942      +34
  Misses         52       52

Impacted Files
Coverage Δ

packages/Search/src/DTK_CoarseGlobalSearch_def.hpp
100% <100%> (ø)

...ackages/Search/src/DTK_CoarseGlobalSearch_decl.hpp
100% <100%> (ø)

packages/Search/test/tstLinearBVH.cpp
99.39% <100%> (ø)
:arrow_up:

packages/Search/test/tstCoarseGlobalSearch.cpp
100% <100%> (ø)

...ch/src/details/DTK_DetailsTreeConstruction_def.hpp
98.23% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Is this PR replaced by #272 ? If so we should close without merging.

Correct


[nrf-ble-driver:x64-windows] build failure

Host Environment

OS: Windows 10 Version 2004
Compiler: Microsoft Visual Studio 2019 Version 16.7.3

To Reproduce
Steps to reproduce the behavior:
./vcpkg install nrf-ble-driver:x64-windows
Failure logs
Computing installation plan...
The following packages will be built and installed:
nrf-ble-driver[core]:x64-windows
Detecting compiler hash for triplet x64-windows...
Starting package 1/1: nrf-ble-driver:x64-windows
Building package nrf-ble-driver[core]:x64-windows...
Could not locate cached archive: C:\Users\jimmy\AppData\Local\vcpkg/archives\2a\2a2c83c5627b8eb36e9592342ff8ce18d4f6771a.zip
-- Using cached F:/GitHub/vcpkg/downloads/NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz
-- Cleaning sources at F:/GitHub/vcpkg/buildtrees/nrf-ble-driver/src/v4.1.2-d61ceeeb19.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source F:/GitHub/vcpkg/downloads/NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz
-- Applying patch 001-arm64-support.patch
-- Using source at F:/GitHub/vcpkg/buildtrees/nrf-ble-driver/src/v4.1.2-d61ceeeb19.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:141 (message):
Command failed: F:/GitHub/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
Working Directory: F:/GitHub/vcpkg/buildtrees/nrf-ble-driver/x64-windows-dbg
See logs for more information:
F:\GitHub\vcpkg\buildtrees\nrf-ble-driver\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/nrf-ble-driver/portfile.cmake:34 (vcpkg_install_cmake)
scripts/ports.cmake:79 (include)
Error: Building package nrf-ble-driver:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: nrf-ble-driver:x64-windows
Vcpkg version: 2020.06.15-nohash
Additionally, attach any relevant sections from the log files above.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

@Jimmy-Hu ，Sorry to reply you so late，Thanks for posting this issue.
I cannot reproduce this with both Visual Studio 2017 and Visual Studio 2019 on my machines.
It seems that the errors you encountered are related with Visual Studio.
Could you please try to check or reinstall Visual Studio and rebuild this?

@Jimmy-Hu ，Sorry to reply you so late，Thanks for posting this issue.
I cannot reproduce this with both Visual Studio 2017 and Visual Studio 2019 on my machines.
It seems that the errors you encountered are related with Visual Studio.
Could you please try to check or reinstall Visual Studio and rebuild this?

@JonLiu1993 Thank you for the reply. I re-cloned the repo and updated Visual Studio 2019 to version 16.8.4. The problem resolved. Happy to close the issue. Thank you so much.
> ./vcpkg install nrf-ble-driver:x64-windows
Computing installation plan...
A suitable version of cmake was not found (required v3.19.2). Downloading portable cmake v3.19.2...
Downloading cmake...
  https://github.com/Kitware/CMake/releases/download/v3.19.2/cmake-3.19.2-win32-x86.zip -> G:\vcpkg\downloads\cmake-3.19.2-win32-x86.zip
Extracting cmake...
A suitable version of 7zip was not found (required v18.1.0). Downloading portable 7zip v18.1.0...
Downloading 7zip...
  https://www.nuget.org/api/v2/package/7-Zip.CommandLine/18.1.0 -> G:\vcpkg\downloads\7-zip.commandline.18.1.0.nupkg
Extracting 7zip...
A suitable version of nuget was not found (required v5.5.1). Downloading portable nuget v5.5.1...
Downloading nuget...
  https://dist.nuget.org/win-x86-commandline/v5.5.1/nuget.exe -> G:\vcpkg\downloads\22ea847d-nuget.exe
The following packages will be built and installed:
  * asio[core]:x64-windows -> 1.18.0
  * catch2[core]:x64-windows -> 2.13.1
  * cli11[core]:x64-windows -> 1.9.1
  * fmt[core]:x64-windows -> 7.1.3
    nrf-ble-driver[core]:x64-windows -> 4.1.2
  * spdlog[core]:x64-windows -> 1.8.0#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of powershell-core was not found (required v7.1.0). Downloading portable powershell-core v7.1.0...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v7.1.0/PowerShell-7.1.0-win-x86.zip -> G:\vcpkg\downloads\PowerShell-7.1.0-win-x86.zip
Extracting powershell-core...

-- Downloading https://github.com/chriskohlhoff/asio/archive/asio-1-18-0.tar.gz -> chriskohlhoff-asio-asio-1-18-0.tar.gz...
-- Extracting source G:/vcpkg/downloads/chriskohlhoff-asio-asio-1-18-0.tar.gz
-- Using source at G:/vcpkg/buildtrees/asio/src/sio-1-18-0-8730731baf.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/asio_x64-windows/share/asio/asio-config.cmake
-- Installing: G:/vcpkg/packages/asio_x64-windows/share/asio/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\8c\8c208fad2b3a4e698facf0b7202fd2c40ef004f3.zip
Building package asio[core]:x64-windows... done
Installing package asio[core]:x64-windows...
Installing package asio[core]:x64-windows... done
Elapsed time for package asio:x64-windows: 15.79 s
Starting package 2/6: catch2:x64-windows
Building package catch2[core]:x64-windows...
-- Downloading https://github.com/catchorg/Catch2/archive/fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz -> catchorg-Catch2-fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz...
-- Extracting source G:/vcpkg/downloads/catchorg-Catch2-fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz
-- Using source at G:/vcpkg/buildtrees/catch2/src/3a90f1c64d-e9f0b88781.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/catch2_x64-windows/share/catch2/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\ad\adb2ee218dba4bd263a1a164400e8d5b1c76c49c.zip
Building package catch2[core]:x64-windows... done
Installing package catch2[core]:x64-windows...
Installing package catch2[core]:x64-windows... done
Elapsed time for package catch2:x64-windows: 6.04 s
Starting package 3/6: cli11:x64-windows
Building package cli11[core]:x64-windows...
-- Downloading https://github.com/CLIUtils/CLI11/archive/2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz -> CLIUtils-CLI11-2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz...
-- Extracting source G:/vcpkg/downloads/CLIUtils-CLI11-2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz
-- Using source at G:/vcpkg/buildtrees/cli11/src/acb1147631-f28fa02023.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/cli11_x64-windows/share/cli11/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\ab\ab3194137f5b1852cbbd4e3538b36f20f5921c5b.zip
Building package cli11[core]:x64-windows... done
Installing package cli11[core]:x64-windows...
Installing package cli11[core]:x64-windows... done
Elapsed time for package cli11:x64-windows: 9.051 s
Starting package 4/6: fmt:x64-windows
Building package fmt[core]:x64-windows...
-- Downloading https://github.com/fmtlib/fmt/archive/7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz -> fmtlib-fmt-7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz...
-- Extracting source G:/vcpkg/downloads/fmtlib-fmt-7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz
-- Applying patch fix-warning4189.patch
-- Using source at G:/vcpkg/buildtrees/fmt/src/2b3b374f0b-8ea71ee8ea.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/fmt_x64-windows/share/fmt/copyright
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz -> msys-mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz...
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz... Failed. Status: 22;"HTTP response code said error"
-- Downloading https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz -> msys-mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz...
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst -> msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst...
-- Using msys root at G:/vcpkg/downloads/tools/msys2/c809757c94447846
-- Fixing pkgconfig file: G:/vcpkg/packages/fmt_x64-windows/lib/pkgconfig/fmt.pc
-- Fixing pkgconfig file: G:/vcpkg/packages/fmt_x64-windows/debug/lib/pkgconfig/fmt.pc
-- Installing: G:/vcpkg/packages/fmt_x64-windows/share/fmt/usage
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\09\09bd5c955dab4fe2ff3caba3d9ec18b716329293.zip
Building package fmt[core]:x64-windows... done
Installing package fmt[core]:x64-windows...
Installing package fmt[core]:x64-windows... done
Elapsed time for package fmt:x64-windows: 26.86 s
Starting package 5/6: spdlog:x64-windows
Building package spdlog[core]:x64-windows...
-- Downloading https://github.com/gabime/spdlog/archive/4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz -> gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz...
-- Extracting source G:/vcpkg/downloads/gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz
-- Applying patch fix-featurebuild.patch
-- Using source at G:/vcpkg/buildtrees/spdlog/src/41254eaeef-61b213204a.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/spdlog_x64-windows/share/spdlog/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\8f\8f56208186903b8bfd5d2dbc7087a7e1844b1a36.zip
Building package spdlog[core]:x64-windows... done
Installing package spdlog[core]:x64-windows...
Installing package spdlog[core]:x64-windows... done
Elapsed time for package spdlog:x64-windows: 23.06 s
Starting package 6/6: nrf-ble-driver:x64-windows
Building package nrf-ble-driver[core]:x64-windows...
-- Downloading https://github.com/NordicSemiconductor/pc-ble-driver/archive/v4.1.2.tar.gz -> NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz...
-- Extracting source G:/vcpkg/downloads/NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz
-- Applying patch 001-arm64-support.patch
-- Using source at G:/vcpkg/buildtrees/nrf-ble-driver/src/v4.1.2-d61ceeeb19.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/connectivity_4.1.2_1m_with_s130_2.0.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/connectivity_4.1.2_1m_with_s132_2.0.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s130_nrf51_2.0.1_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s130_nrf51_2.0.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s132_nrf52_2.0.1_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s132_nrf52_2.0.1_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_1m_with_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_for_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_with_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_with_s132_3.1.0_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/s132_nrf52_3.1.0_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/s132_nrf52_3.1.0_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_1m_with_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_for_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_with_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_with_s132_5.1.0_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/s132_nrf52_5.1.0_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/s132_nrf52_5.1.0_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_1m_with_s132_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_1m_with_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_for_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_with_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_with_s140_6.1.1_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s132_nrf52_6.1.1_licence-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s132_nrf52_6.1.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s140_nrf52_6.1.1_licence-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s140_nrf52_6.1.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\70\70f645e6110502eeb877812d37085687a87671fb.zip
Building package nrf-ble-driver[core]:x64-windows... done
Installing package nrf-ble-driver[core]:x64-windows...
Installing package nrf-ble-driver[core]:x64-windows... done
Elapsed time for package nrf-ble-driver:x64-windows: 2.271 min

Total elapsed time: 9.309 min

The package nrf-ble-driver:x64-windows provides CMake targets:

    find_package(nrf-ble-driver CONFIG REQUIRED)
    # Note: 4 target(s) were omitted.
    target_link_libraries(main PRIVATE nrf::nrf_ble_driver_sd_api_v2_shared nrf::nrf_ble_driver_sd_api_v2_static nrf::nrf_ble_driver_sd_api_v3_shared nrf::nrf_ble_driver_sd_api_v3_static)

@JonLiu1993 Thank you for the reply. I re-cloned the repo and updated Visual Studio 2019 to version 16.8.4. The problem resolved. Happy to close the issue. Thank you so much.
> ./vcpkg install nrf-ble-driver:x64-windows
Computing installation plan...
A suitable version of cmake was not found (required v3.19.2). Downloading portable cmake v3.19.2...
Downloading cmake...
  https://github.com/Kitware/CMake/releases/download/v3.19.2/cmake-3.19.2-win32-x86.zip -> G:\vcpkg\downloads\cmake-3.19.2-win32-x86.zip
Extracting cmake...
A suitable version of 7zip was not found (required v18.1.0). Downloading portable 7zip v18.1.0...
Downloading 7zip...
  https://www.nuget.org/api/v2/package/7-Zip.CommandLine/18.1.0 -> G:\vcpkg\downloads\7-zip.commandline.18.1.0.nupkg
Extracting 7zip...
A suitable version of nuget was not found (required v5.5.1). Downloading portable nuget v5.5.1...
Downloading nuget...
  https://dist.nuget.org/win-x86-commandline/v5.5.1/nuget.exe -> G:\vcpkg\downloads\22ea847d-nuget.exe
The following packages will be built and installed:
  * asio[core]:x64-windows -> 1.18.0
  * catch2[core]:x64-windows -> 2.13.1
  * cli11[core]:x64-windows -> 1.9.1
  * fmt[core]:x64-windows -> 7.1.3
    nrf-ble-driver[core]:x64-windows -> 4.1.2
  * spdlog[core]:x64-windows -> 1.8.0#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of powershell-core was not found (required v7.1.0). Downloading portable powershell-core v7.1.0...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v7.1.0/PowerShell-7.1.0-win-x86.zip -> G:\vcpkg\downloads\PowerShell-7.1.0-win-x86.zip
Extracting powershell-core...

-- Downloading https://github.com/chriskohlhoff/asio/archive/asio-1-18-0.tar.gz -> chriskohlhoff-asio-asio-1-18-0.tar.gz...
-- Extracting source G:/vcpkg/downloads/chriskohlhoff-asio-asio-1-18-0.tar.gz
-- Using source at G:/vcpkg/buildtrees/asio/src/sio-1-18-0-8730731baf.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/asio_x64-windows/share/asio/asio-config.cmake
-- Installing: G:/vcpkg/packages/asio_x64-windows/share/asio/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\8c\8c208fad2b3a4e698facf0b7202fd2c40ef004f3.zip
Building package asio[core]:x64-windows... done
Installing package asio[core]:x64-windows...
Installing package asio[core]:x64-windows... done
Elapsed time for package asio:x64-windows: 15.79 s
Starting package 2/6: catch2:x64-windows
Building package catch2[core]:x64-windows...
-- Downloading https://github.com/catchorg/Catch2/archive/fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz -> catchorg-Catch2-fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz...
-- Extracting source G:/vcpkg/downloads/catchorg-Catch2-fd9f5ac661f87335ecd70d39849c1d3a90f1c64d.tar.gz
-- Using source at G:/vcpkg/buildtrees/catch2/src/3a90f1c64d-e9f0b88781.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/catch2_x64-windows/share/catch2/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\ad\adb2ee218dba4bd263a1a164400e8d5b1c76c49c.zip
Building package catch2[core]:x64-windows... done
Installing package catch2[core]:x64-windows...
Installing package catch2[core]:x64-windows... done
Elapsed time for package catch2:x64-windows: 6.04 s
Starting package 3/6: cli11:x64-windows
Building package cli11[core]:x64-windows...
-- Downloading https://github.com/CLIUtils/CLI11/archive/2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz -> CLIUtils-CLI11-2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz...
-- Extracting source G:/vcpkg/downloads/CLIUtils-CLI11-2b059cbdbe844450e1675a5dda3cb8acb1147631.tar.gz
-- Using source at G:/vcpkg/buildtrees/cli11/src/acb1147631-f28fa02023.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/cli11_x64-windows/share/cli11/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\ab\ab3194137f5b1852cbbd4e3538b36f20f5921c5b.zip
Building package cli11[core]:x64-windows... done
Installing package cli11[core]:x64-windows...
Installing package cli11[core]:x64-windows... done
Elapsed time for package cli11:x64-windows: 9.051 s
Starting package 4/6: fmt:x64-windows
Building package fmt[core]:x64-windows...
-- Downloading https://github.com/fmtlib/fmt/archive/7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz -> fmtlib-fmt-7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz...
-- Extracting source G:/vcpkg/downloads/fmtlib-fmt-7bdf0628b1276379886c7f6dda2cef2b3b374f0b.tar.gz
-- Applying patch fix-warning4189.patch
-- Using source at G:/vcpkg/buildtrees/fmt/src/2b3b374f0b-8ea71ee8ea.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/fmt_x64-windows/share/fmt/copyright
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz -> msys-mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz...
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz... Failed. Status: 22;"HTTP response code said error"
-- Downloading https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz -> msys-mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz...
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst -> msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst...
-- Using msys root at G:/vcpkg/downloads/tools/msys2/c809757c94447846
-- Fixing pkgconfig file: G:/vcpkg/packages/fmt_x64-windows/lib/pkgconfig/fmt.pc
-- Fixing pkgconfig file: G:/vcpkg/packages/fmt_x64-windows/debug/lib/pkgconfig/fmt.pc
-- Installing: G:/vcpkg/packages/fmt_x64-windows/share/fmt/usage
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\09\09bd5c955dab4fe2ff3caba3d9ec18b716329293.zip
Building package fmt[core]:x64-windows... done
Installing package fmt[core]:x64-windows...
Installing package fmt[core]:x64-windows... done
Elapsed time for package fmt:x64-windows: 26.86 s
Starting package 5/6: spdlog:x64-windows
Building package spdlog[core]:x64-windows...
-- Downloading https://github.com/gabime/spdlog/archive/4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz -> gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz...
-- Extracting source G:/vcpkg/downloads/gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz
-- Applying patch fix-featurebuild.patch
-- Using source at G:/vcpkg/buildtrees/spdlog/src/41254eaeef-61b213204a.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: G:/vcpkg/packages/spdlog_x64-windows/share/spdlog/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\8f\8f56208186903b8bfd5d2dbc7087a7e1844b1a36.zip
Building package spdlog[core]:x64-windows... done
Installing package spdlog[core]:x64-windows...
Installing package spdlog[core]:x64-windows... done
Elapsed time for package spdlog:x64-windows: 23.06 s
Starting package 6/6: nrf-ble-driver:x64-windows
Building package nrf-ble-driver[core]:x64-windows...
-- Downloading https://github.com/NordicSemiconductor/pc-ble-driver/archive/v4.1.2.tar.gz -> NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz...
-- Extracting source G:/vcpkg/downloads/NordicSemiconductor-pc-ble-driver-v4.1.2.tar.gz
-- Applying patch 001-arm64-support.patch
-- Using source at G:/vcpkg/buildtrees/nrf-ble-driver/src/v4.1.2-d61ceeeb19.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/connectivity_4.1.2_1m_with_s130_2.0.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/connectivity_4.1.2_1m_with_s132_2.0.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s130_nrf51_2.0.1_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s130_nrf51_2.0.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s132_nrf52_2.0.1_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v2/../sd_api_v2/s132_nrf52_2.0.1_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_1m_with_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_for_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_with_s132_3.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/connectivity_4.1.2_usb_with_s132_3.1.0_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/s132_nrf52_3.1.0_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v3/../sd_api_v3/s132_nrf52_3.1.0_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_1m_with_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_for_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_with_s132_5.1.0.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/connectivity_4.1.2_usb_with_s132_5.1.0_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/s132_nrf52_5.1.0_license-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v5/../sd_api_v5/s132_nrf52_5.1.0_softdevice.hex
-- Up-to-date: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_1m_with_s132_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_1m_with_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_for_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_with_s140_6.1.1.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/connectivity_4.1.2_usb_with_s140_6.1.1_dfu_pkg.zip
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s132_nrf52_6.1.1_licence-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s132_nrf52_6.1.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s140_nrf52_6.1.1_licence-agreement.txt
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/hex/sd_api_v6/../sd_api_v6/s140_nrf52_6.1.1_softdevice.hex
-- Installing: G:/vcpkg/packages/nrf-ble-driver_x64-windows/share/nrf-ble-driver/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\jimmy\AppData\Local\vcpkg\archives\70\70f645e6110502eeb877812d37085687a87671fb.zip
Building package nrf-ble-driver[core]:x64-windows... done
Installing package nrf-ble-driver[core]:x64-windows...
Installing package nrf-ble-driver[core]:x64-windows... done
Elapsed time for package nrf-ble-driver:x64-windows: 2.271 min

Total elapsed time: 9.309 min

The package nrf-ble-driver:x64-windows provides CMake targets:

    find_package(nrf-ble-driver CONFIG REQUIRED)
    # Note: 4 target(s) were omitted.
    target_link_libraries(main PRIVATE nrf::nrf_ble_driver_sd_api_v2_shared nrf::nrf_ble_driver_sd_api_v2_static nrf::nrf_ble_driver_sd_api_v3_shared nrf::nrf_ble_driver_sd_api_v3_static)


Tag Router should support multiple tags.

Static:

provider: tag="tag1, tag2, tag3"
consumer, support limited expressions, regex for example

I want to try


134 Adds hyper spectral imaging to qt3scan

Adds hyper spectral imaging to qt3scan --> #134

Also, we need to add documentation to the README

Overall, this is a good implementation of hyper spectral scans. I will submit a second round of reviews, once I see this in action today. One thing I would like to see is an explanation of who a person would go about adding their own spectrometer classes, and making this code easily accept different spectrometers.

@vasilisniaouris more documentation is definitely needed. The README already had some documentation around implementing support for new hardware. We did need to make a fundamental code change to split the DAQ controller interface into one that supports counters and one that supports spectra. @cmordi we should document that in the readme.
I think the current documentation in README is pretty good and probably makes a lot more sense to @cmordi now. So perhaps he'll be able to provide an update to that doc.
Having said that, I know there's pressure to release something. Given that documentation is usually something that doesn't get done, I highly recommend that we at least put something in the README that explains what's happening and how to implement a new spectrometer. It should be a natural extension of the information that is currently there.

Overall, this is a good implementation of hyper spectral scans. I will submit a second round of reviews, once I see this in action today. One thing I would like to see is an explanation of who a person would go about adding their own spectrometer classes, and making this code easily accept different spectrometers.

@vasilisniaouris more documentation is definitely needed. The README already had some documentation around implementing support for new hardware. We did need to make a fundamental code change to split the DAQ controller interface into one that supports counters and one that supports spectra. @cmordi we should document that in the readme. I think the current documentation in README is pretty good and probably makes a lot more sense to @cmordi now. So perhaps he'll be able to provide an update to that doc.
Having said that, I know there's pressure to release something. Given that documentation is usually something that doesn't get done, I highly recommend that we at least put something in the README that explains what's happening and how to implement a new spectrometer. It should be a natural extension of the information that is currently there.

@gadamc Just updated the docs. One or two of the hyperlinks are for this branch which is obviously not correct but I will changed those when we updated the main branch. Please let me know if I included incorrect info in the docs


[react-form-state] validate form programatically

Overview
The same way we get submit as a render prop from FormState, it would be great if we could get validate as a prop from FormState. We have a few use cases now where we need to run validation on initial render or hooked into other events than dirtying the form. Facebook Ads, Facebook Marketplace(@michelleyschen) and Marketing section (@darrenhebner).
Motivation

What inspired this enhancement? What makes you think this should be in quilt?

For us, we need to run validation right away because the data gets pre-populated from the backend so the merchant needs to know what fields are invalid according to our app.

Checklist

[x] Please delete the labels section before submitting your issue
[x] I have described this issue in a way that is actionable (if possible)

@macdonaldr93 do you think it would make sense / be enough to just have a validateOnMount or validateOnInitialize prop?

Not quite, the form fields can also hide / show based on a state change. I would also need to re-validate when those state change.

I'm not really sure I follow, if fields can hide and show based on a state change but the form was validated at the start wouldn't that be good enough? They'd still have their initial errors they would just be hidden.

Yeah I think in this particular case, a given field selection may drastically change the fields required in the form and therefore the validations needed. So when the field value changes, we'd want to re-run validation since some of the field requirements will change.
More concretely, we have a field that is product category. So if the product category field is set to Apparel, that means the MPN, Size, and Field X are required. But if the product category gets changed to something else, that won't be the case. Does that make sense?

The use case I am running into:

Form start with 5 fields, validate on init => 5 errors count is shown on screen
User trigger a state change
The form now show 3 fields, (but the form it self still have 5)
I have two choice at this point.
1⃣ re-run validation (where my validation are based on state)
2⃣ count the number of error only for the form fields that's being shown.

I would prefer 1⃣ because I have a few components that will count / show text acoordingly
but 2⃣ is do able

Yeah, but what I'm asking is would that usecase not be handled by having all fields validate when any one is updated + the ability to have fields validate even when not dirty?

cc @laranoell also have the same use case

closing this for now as the public validateForm method + validateOnSubmit should enable these usecases :)


Form-jsx: Create new post that can store data into database

[ ] Create a Form that can create Post and store data in the database
[ ] Consider receiving data back to the front-end if possible, eg. new post created, updating your posts list.. eg. new order created, updating your order list

cannot get user id to work, the form is there, but leak of the user id data I cannot create post


Fixcaldates2  fix calendar module date processing, using<EMAIL_ADDRESS>

here is an updated test version of the fixes for all kinds of calendar date problems.
NOTE: the changed branch name
NOTE: this used the<EMAIL_ADDRESS>library UNCHANGED
best to make a new folder and git clone there
git clone https://github.com/sdetweil/MagicMirror
cd MagicMirror
git checkout fixcaldates2 // <------ note this is a changed branch name
npm run install-mm
copy your config.js and custom.css from the prior folder
and the non-default modules you have installed…
this ONLY changes the default calendar
but DOES ship an updated node-ical library too
if you need to fall back, just rename the folders around again so that
your original is called MagicMirror
all the testcases for node-ical and MagicMirror execute successfully.
the ‘BIG’ change here is to get the local NON-TZ dates for the
rrule.between()
all the checking and conversion code is commented out or not used
the node-ical fixes are for excluded dates (exdate) values being adjusted for DST/STD time… waiting to submit that PR
one fix in calendar.js for checking if a past date was too far back,
but it never checked to see IF the event date was in the past… (before today) so it chopped off too many
and one change in calendarfetcher.js to put out a better diagnostic message of the parsed data… (exdate was excluded cause JSON stringify couldn’t convert the complex structure)
I added the tests you all have documented
please re-pull and checkout the new branch (I deleted the old branch)
and npm run install-mm again

I can't create the timeout on 20.x electron test
 PASS   electron  tests/electron/modules/calendar_spec.js (45.347 s)
  Calendar module
    Test css classes
      ✓ has css class dayBeforeYesterday (2531 ms)
      ✓ has css class yesterday (2539 ms)
      ✓ has css class today (2471 ms)
      ✓ has css class tomorrow (2501 ms)
      ✓ has css class dayAfterTomorrow (2602 ms)
    Events from multiple calendars
      ✓ should show multiple events with the same title and start time from different calendars (2602 ms)
    rrule
      ✓ Issue #3393 recurrence dates past rrule until date (2552 ms)
    Exdate: LA crossover DST before midnight GMT
      ✓ LA crossover DST before midnight GMT should have 2 events (2496 ms)
    Exdate: LA crossover DST at midnight GMT local STD
      ✓ LA crossover DST before midnight GMT should have 2 events (2531 ms)
    Exdate: LA crossover DST at midnight GMT local DST
      ✓ LA crossover DST before midnight GMT should have 2 events (2516 ms)
    Exdate: SYD crossover DST before midnight GMT
      ✓ LA crossover DST before midnight GMT should have 2 events (2443 ms)
    Exdate: SYD crossover DST at midnight GMT local STD
      ✓ LA crossover DST before midnight GMT should have 2 events (2486 ms)
    Exdate: SYD crossover DST at midnight GMT local DST
      ✓ SYD crossover DST at midnight GMT local DST should have 2 events (2577 ms)
    sliceMultiDayEvents
      ✓ Issue #3452 split multiday in Europe (2517 ms)
    sliceMultiDayEvents direct count
      ✓ Issue #3452 split multiday in Europe (2490 ms)
    germany timezone
      ✓ Issue #unknown fullday timezone East of UTC edge (2493 ms)
    germany all day repeating moved (recurrence and exdate)
      ✓ Issue #unknown fullday timezone East of UTC event moved (2448 ms)
    chicago late in timezone
      ✓ Issue #unknown rrule US close to timezone edge (2454 ms)

getting the same error ...
    chicago late in timezone
      ✕ Issue #unknown rrule US close to timezone edge (20080 ms)

  ● Calendar module › chicago late in timezone › Issue #unknown rrule US close to timezone edge

    thrown: "Exceeded timeout of 20000 ms for a test.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

      178 |
      179 |     describe("chicago late in timezone", () => {
    > 180 |             it("Issue #unknown rrule US close to timezone edge", async () => {
          |             ^
      181 |                     await helpers.startApplication("tests/configs/modules/calendar/chicago_late_in_timezone.js", "01 Sept 2024 10:38:00 GMT-5:00", ["js/electron.js"], "America/Chicago");
      182 |                     await expect(doTestTableContent(".calendar .event", ".time", "10th.Sep, 20:15")).resolves.toBe(true);
      183 |             });

      at it (tests/electron/modules/calendar_spec.js:180:3)
      at describe (tests/electron/modules/calendar_spec.js:179:2)
      at Object.describe (tests/electron/modules/calendar_spec.js:3:1)

yeh. thats not the real error.  something has made it fail (variable, coding)  but i don't see anything locally
manual or the test runs.
only diff is i added logLevel to this js testcase, but logs are nooped in test runs

removed the logLevel  config.js  setting for chicago test..

anyone have ideas how to see the stdout/err during the jest run?
i cannot recreate this

node@89788bc75cde:/opt/magic_mirror$ cat tests/configs/modules/calendar/chicago_late_in_timezone.js
let config = {
        timeFormat: 24,
        modules: [
                {
                        module: "calendar",
                        position: "bottom_bar",
                        config: {
                                fade: false,
                                urgency: 0,
                                dateFormat: "Do.MMM, HH:mm",
                                fullDayEventDateFormat: "Do.MMM",
                                timeFormat: "absolute",
                                getRelative: 0,
                                maximumNumberOfDays: 20,
                                calendars: [
                                        {
                                                maximumEntries: 100,
                                                //url: "http://localhost:8080/tests/mocks/chicago_late_in_timezone.ics"
                                                url: "http://localhost:8080/modules/default/calendar/chicago_late_in_timezone.ics"
                                        }
                                ]
                        }
                }
        ]
};

the referenced file modules/default/calendar/chicago_late_in_timezone.ics doesn't exist.
By the way, the new test config's are missing the lines address and ipWhitelist ...

thx
doh!

but, how did you see that

fixed those

So, the testcase that is failing here is due to the fact that today+6 months gets April 9 in view of the repeating rule
if the event date is April 10 and not April 9, only 10 events are returned from RRULE.between()
because the code does ==>now<===+maximumNumberOfDay(10000) for the end date of between
number of days until Mar 9 2052 from now = 9999
but that implies that the systemdate in the testcase didn't execute in the helper
await helpers.startApplication("tests/configs/modules/calendar/show-duplicates-in-calendar.js", "15 Sep 2024 12:30:00 GMT");
			if (systemDate) {
				await global.page.evaluate((systemDate) => {
					Date.now = () => {
						return new Date(systemDate).valueOf();
					};
				}, systemDate);
			}

if I add this date setting to the testcase .js itself,  it works..
};

Date.now = () => {
  return new Date("15 Sep 2024 12:30:00 GMT").valueOf();
};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {
	module.exports = config;
}

how do we want to fix this testcase?

see fails in all other PR's today.

yes, the date changed and another event was published(total 11 from each is)  (making the total 22 instead ot the expected 20) , which now breaks every test run

use my fixdate pr #3596

I updated calendar.js
on commit I received this warning
✖ eslint --fix:

/home/sam/MagicMirror.old/modules/default/calendar/calendar.js
  0:0  warning  File ignored because of a matching ignore pattern. Use "--no-ignore" to disable file ignore settings or use "--no-warn-ignored" to suppress this warning

I don't know much about eslint, but maybe the ".old" in the folder name is the problem...

ee did put in a new eslint

what is going on here?
on my system the test:e2e works correctly and the individual configs work as expected.
the ONLY thing that changed was the eslint run that 'cleaned up' calendar.js and calendarfetcher.js too
wrong count from classes is a calander.js issue.

all worked ok yesterday

last successful run at  — Today at 2:57 AM (my time? us central) on merge of the compliments update
my update at 8:45 for calendar failed.

user installed pr, and sees extra data, but it doesn't appear during test. what is going on here

there is no change in behavior during test.  something is wrong w test build

I think this is a playwright problem
the e2e testcase runner uses
	const testTextContain = async (element, text) => {
		const elem = await helpers.waitForElement(element, "undefinedLoading");  // wait for module, .calendar
		expect(elem).not.toBeNull();  // make sure its not not found/empt
		expect(elem.textContent).toContain(text); // check that the textContent of that element contains, but return is different
		return true;
	};

which returns
"undefinedBirthdayBirthdayBirthdayBirthdayBirthdayBirthday

from
it(`should contain text "Mar 25th" in timezone UTC ${-i}`, async () => {
				await expect(testTextContain(".calendar", "Mar 25th")).resolves.toBe(true);
});

so it gets the total textContent from the .calendar css object , not focused on AN element (time in a event)
I saw that playwright was updated, but says 2 weeks ago...

still don't get it..
checked out PR clean, new folder
ran e2e, worked great
 PASS   e2e  tests/e2e/modules/calendar_spec.js (78.647 s)
  Calendar module
    Default configuration
      ✓ should show the default maximumEntries of 10 (1321 ms)
      ✓ should show the default calendar symbol in each event (201 ms)
    Custom configuration
      ✓ should show the custom maximumEntries of 5 (1328 ms)
      ✓ should show the custom calendar symbol in four events (202 ms)
      ✓ should show a customEvent calendar symbol in one event (200 ms)
      ✓ should show a customEvent calendar eventClass in one event (201 ms)
      ✓ should show two custom icons for repeating events (201 ms)
      ✓ should show two custom icons for day events (201 ms)
    Recurring event
      ✓ should show the recurring birthday event 6 times (1282 ms)
    FullDayEvent over several days should show how many days are left from the from the starting date on
      ✓ should contain text 'Ends in' with the left days (1712 ms)
      ✓ should contain in total three events (200 ms)
    FullDayEvent Single day, should show Today
      ✓ should contain text 'Today' (1215 ms)
      ✓ should contain in total two events (202 ms)
    Recurring event per timezone
      ✓ should contain text "Mar 25th" in timezone UTC 12 (1219 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 11 (1241 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 10 (1218 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 9 (1238 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 8 (1311 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 7 (1223 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 6 (1376 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 5 (1278 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 4 (1261 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 3 (1315 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 2 (1339 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 1 (1334 ms)
      ✓ should contain text "Mar 25th" in timezone UTC 0 (1267 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -1 (1370 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -2 (1247 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -3 (1270 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -4 (1274 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -5 (1275 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -6 (1274 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -7 (1343 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -8 (1240 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -9 (1589 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -10 (1207 ms)
      ✓ should contain text "Mar 25th" in timezone UTC -11 (1476 ms)

what is the test system date and timezone?

ok, ready to merge... no additional testers have found anything, or commited to finish testing.


pyDARN

I noticed PyDARN is on your list however is pointing to the wrong github link.
pyDARN is a new library to replace DaViTpy found at https://github.com/superdarn/pydarn
The main developer is Marina Schmidt

Updating...

Closing with merge of #55.


Transform/Update across model versions

A definitive problem space for OSCAL will always been the cognitive burden of keeping documents up to date and working to ensure cross-version compatibility. This has been less apparent currently as the modifications and backwards compatibility of the models has been stable - but there may be a time when a major change could induce a blocking state for apps to process.
In having this project generating the required struct types and storing them for downstream consumption - it can also consume these for native use in providing other functionality.
Evaluate writing helper command(s) for transforming the version of an ingested document to another version of the model schema.

Additional command creation
Focus on forward compatibility (backward would be nice too)
parse the release notes of one version to another
perform generation of each and confirm
write functionality to perform the update

Solutioning thoughts: (Ignore if needed)

It would be good if this were exposed as a public function

parameters (input doc, target version)

consideration for upgrade flow. We don't want to write every permutation for one version -> another.

Instead look at perfomance of explicit logic for one version to the next and then traversing multiple calls if upgrading across 2+ versions.

depends on #37


Add missing Emacs editor preset values to the README

I struggled a bit to find out how to hook up better_errors to my
Emacs. Realised that the README didn't mention how to do this but that
it was supported, so I added the relevant preset values

Documentation for the editor links have been moved to the wiki: https://github.com/charliesome/better_errors/wiki/Link-to-your-editor


How to make modal open when page opnes ( ie don't have to click)

Hi. Sorry for basic question but can you tell me how to set it up so that the modal opens when the page loads ( ie not only on click)? Thanks

You could just call the modal open on document ready, like so:
$( document ).ready(function() {
  $('[data-remodal-id=modal]').remodal().open();
});

Thanks!


NetlifyCMS handling Staticman comment moderation

- Do you want to request a feature or report a bug?
Feature
- What is the expected behaviour?
NetlifyCMS handling Staticman comment moderation.
Staticman brings user-generated content to static sites like reviews, comments and ratings
Staticman Rating Demo

This request seems small, but it has major implications that I'm pretty excited about. Here's why.
Staticman comment moderation happens via pull requests, the same method we're currently using for the editorial workflow. This is going to become a common pattern as git based projects embrace the JAMstack moving forward. That said, the editorial workflow interface isn't ideal for comments for a few reasons:

Ideally, you'd burn through a bunch of comment approvals and then merge them all at once, in a single build. The editorial workflow produces a commit per item, which would result in a crazy number of superfluous build requests for sites with any volume.
There should be a way to separate comments from different parts of a site, whereas the editorial workflow combines everything into one view.
The editorial workflow is a kanban board, and would likely prove cumbersome for comment moderation.

The point is, it should be possible to create entire new views within Netlify CMS, and to have full access to all available data from within those views. This would enable a Staticman plugin to be created with an ideal comment moderation interface and the ability to interact with pull requests as it sees fit.
Netlify CMS as a platform
This is a precursor to a more detailed writeup that I'll get together at some point, but I thought I'd drop a preview here:
Every view within Netlify CMS, including the collections view and the editor, should be built as an extension.
We're just scratching the surface of what can be done on the JAMstack, and Netlify CMS is in position to make all of it user editable, so long as we give the community something to build on. If everything is an extension, and a shared library of UI components is available for continuity, we could make it straightforward to create a dedicated comment moderation view.
So sort of a good news/bad news thing. Good news is, we should definitely support staticman and tools like it, and I believe we're going to. Not as good news is that it's going to take some time. I'll link back to this ticket when a real write up is in place for tracking.

I guess this topic could benefit from @eduardoboucas 's opnion.

Please forgive my ignorance, as I am really new to all of this, but would it be possible to use Staticman in tandem with NetlifyCMS?

@michaelkornblum yep, they coexist just fine. This issue is just about integrating Staticman moderation into the Netlify CMS UI.

allow extensions to create entire interfaces within Netlify CMS, in which case you could build a file tree manager if you wanted that functionality

@erquhart, as you have mentioned about extension in the issue https://github.com/netlify/netlify-cms/issues/1575#issuecomment-416655560, why don't you add label to this issue like area: extension

Because the API's don't exist for this to be an extension yet, that's all.

This post from @eduardoboucas may help
https://eduardoboucas.com/posts/2020-12-23-staticman-netlify-functions/

Closing as stale


Fix syntax error insert report ... version

Lower releases do not support version addition for insert report (see docs).
For the cases where insert report is required, abapGit will rely on default system behavior which sets version = X.
It's probably one of the cases where we need a 750 code base and automatic downport. 🤷
Ref https://github.com/abapGit/abapGit/pull/6299#issuecomment-1610326468

https://github.com/abaplint/abaplint/pull/3037


Run subcommand in context manager

If would like to run a subcommand inside of a context manager that would be setup in a higher command. How is it possible to do that with click? My pseudo-code looks something like:

import click

from contextlib import contextmanager

@contextmanager
def database_context(db_url):
    try:
        print(f'setup db connection: {db_url}')
        yield
    finally:
        print('teardown db connection')

@click.group
@click.option('--db',default='local')
def main(db):
    print(f'running command against {db} database')
    db_url = get_db_url(db)
    connection_manager = database_context(db_url)
    # here come the mysterious part that makes all subcommands
    # run inside the connection manager

@main.command
def do_this_thing()
    print('doing this thing')

@main.command
def do_that_thing()
    print('doing that thing')

And this would be called like:
> that_cli do_that_thing
running command against local database
setup db connection: db://user:pass@localdb:db_name
doing that thing
teardown db connection

> that_cli --db staging do_this_thing
running command against staging database
setup db connection: db://user:pass@123.456.123.789:db_name
doing this thing
teardown db connection

Interface could be:
@click.group
@click.option('--db',default='local')
@click.pass_context
def main(ctx, db):
    print(f'running command against {db} database')
    db_url = get_db_url(db)
    with database_context(db_url) as db_context:
        ctx.obj["db"] = db_context
        yield

@main.command
@pass_context
def do_this_thing(ctx)
    print('doing this thing with db', ctx.obj["db"])

click could detect the usage of yield with inspect.isgeneratorfunction

I'm also looking for this. An ugly workaround is to run the click main function from within an ExitStack and somehow pass it inside (using obj for examle). You can then use enter_context inside the main function to enter the database context and then overwrite the ctx.obj.

from contextlib import ExitStack, contextmanager

class DatabaseConnection:
    pass

@contextmanager
def database_context(where):
    print(f"Connecting to db {where}")
    try:
        yield DatabaseConnection()
    finally:
        print(f"Cleaning up db connection {where}")

pass_db = click.make_pass_decorator(DatabaseConnection)

@click.group()
@click.pass_context
def main(ctx):
    estack = ctx.obj

    db: DatabaseConnection = estack.enter_context(database_context("url"))
    ctx.obj = db

@main.command()
@pass_db
def do_this(db):
    # Yay, i have a db
    print(db)

if __name__ == '__main__':
    with ExitStack() as es:
        main(obj=es)

This has already been possible with Context.call_on_close() as long as the resource provides a close() method (or just pass its __exit__() method. Instead of using a with block, create the resource, register its close() method, and add it to ctx.obj.
That can be a bit verbose, #1191 switches to using an ExitStack internally for both call_on_close() and a new with_resource() method that will return a resource after entering it into the stack.
In 8.0 it will be possible to do this:
@click.group()
@click.option("--username")
def cli(username):
    ctx = click.get_current_context()
    ctx.ensure_object(dict)["db"] = ctx.with_resource(connect_db(username))


doc: Doc updates

Doc updates to fix version number and build command

Btw, we need to sync with upstream example-application, it contains a few updates. @carlescufi


Remove restriction to public [SerializationConstructor]

The given code will throw a InvalidOperationException when trying to Deserialize the test class:
public class TestImmutable
{
	[SerializationConstructor]
	private TestImmutable(int x)
	{
		this.X = x;
	}

	public TestImmutable(string xstr)
	{
		this.X = int.Parse(xstr);
	}

	public int X {get;}
}

Changing the private constructor to public will fix the issue.
Is there a good reason for the public constraint (implemented here: https://github.com/neuecc/Utf8Json/blob/master/src/Utf8Json/Internal/Emit/MetaType.cs#L68)?
I suggest removing the public-constraint. In my opinion serialization constructors should not be public as they might expose fields that should not be accessible to the consumer.

I have the same issue.

Same here, Newtonsoft allows you to apply a "JsonContructor" attribute to the non-public constructors.

Is there a good reason for the public constraint (implemented here: https://github.com/neuecc/Utf8Json/blob/master/src/Utf8Json/Internal/Emit/MetaType.cs#L68)?

To avoid MethodAccessException.
Utf8Json internally creates formatter classes by dynamic code generation.
generated formatter calls serialization constructor directly while deserializing it.
But we cannot calling private constructor directly.Because generated formatter classes are in different assembly from private constructor.
To avoid this issue,we should do followings.

Create wrapper factory method of private constructor using DynamicMethod.
We can stop worry about accessibility while using DynamicMethod.

Call wrapper factory method from formatter class.


multiple person video input

Dear authors,
Does the current demo support videos with multiple people?

It seems only one person is visualized on the right side of the demo.

Hi @linjiangya
Currently, WHAM outputs world-grounded pose and shape of all people in the scene. However, their global trajectories are estimated individually, thus, we don't have such an implementation to constrain everyone on the same world coordinates.
We will implement a naive solution later that will anchor a single world coordinate on a representative individual and visualize all other people accordingly -- this is just for visualization purposes. But at the current stage, we only support to visualize the global-trajectory for only one person in the scene.

Just want to follow up on this thread. Amazing work!
Any thoughts on how to map the camera slam output into the world coordinates as well?

I also want to know, hope you can let us know.
Thanks!


Draft up should pipe logs immediately to the log file

During longer builds, in another terminal I find myself wanting to inspect the logs from the current build. Because we only write to the log file once the build has finished, the user doesn't know about the build status until it finishes. I'd love for us to pipe these logs straight to the log file rather than through a buffer.

Also see #584 for another scenario

closed by #638


feat(form-field): disabled styles on label

TASK: #1066
Description, Motivation and Context
See attached issue
Types of changes

[x] ✨ New feature (non-breaking change which adds functionality)
[x] 🧾 Documentation
[x] 💄 Styles

Screenshots - Animations

Can you test how does it work if it's readOnly and disabled? The right one must be disabled, is the most relevant natively


Fix _is_expired_token logic error

The expired logic should be: time.time() > issue_date + DEFAULT_TOKEN_LIFETIME

I found out about this issue as well. Is there an issue with this pull request that's preventing it from getting merged in?

@barumrho I saw broken tests and postponed reviewing this PR. Looks like I postponed too much 🙃
@SearchDream thx for contribution


Cancellation and Conditions

Up until recently I haven't been using conditions much. However, I'm now refactoring my network stack so that every operation has a condition that certain bits of information are set. So now I'm starting to run into this assert every so often, with no code changes from me:
assert(cancelled == false, "\(__FUNCTION__) was called on cancelled operation.")

This doesn't seem like something I can avoid in my own code. I'll investigate more but it's very intermittent, which seems to indicate a race between cancelled being set and this code being called:
case .Pending:
    // If the operation is cancelled, isReady should return true
    if cancelled {
        state = .Ready
        return true
    }
    if super.ready {
        return evaluateConditions()
    }
    // Until conditions have been evaluated, we're not ready
    return false

Any guidance?

Hi @jshier - thanks for this. I think it's the same known issue which I'm currently working on.
This bit of code is getting refactored. Essentially I'm making all of the properties (such as cancelled etc) thread safe.

For guidance - if you can work around it for now, that would be great. I hope to have this race condition fixed in development by end of day tomorrow.

Hi @jshier! Regarding this issue.. I think the issues you have experienced here might be related to the general KVO issues which have been investigated this week and are being tracked in #175, with some improvements merged in #180.
Would be interested to see if the changes in #180 have alleviated this issue for you at all.
If not: I think the nest step is to clarify if it's a "cancelled" state race condition issue, or... something else I guess.
One thing which I do want to check on, is that we should be returning "Cancelled" (in addition to "State") as a KVO path affecting isReady which is a class function inside Operation. If you're able to test this inside your fork that would be really helpful :)

@jshier I'll see if I can sort this out this week - would be great to fix this in 2.6.0.

Okay - so I've made this change in v2.6.0: see here. I'm not actually sure if this will fix this issue, and I've not been able to write a unit test to reproduce this issue. However that change is something which should have been inlace already. If the cancelled state changes, so should the conditions readiness.

I haven't seen this in quite a while, so I think it was fixed in 2.6 or 2.7.

Thanks @jshier for getting back to me on this - gonna close it for now.


Support non-Safari browsers

If other browser engines come to iOS in the EU, we should support using Game Play in those browsers.

Related to #68.

Lock-screen and browser restrictions to be lifted as part of #242.


Create a Phone Number Value Object

No ideas, no previous researches.

Added this library to manage the phone numbers: https://github.com/giggsey/libphonenumber-for-php


trojan XTLS Direct Mode ReadV

Now when using trojan XTLS direct mode, you can also get the best performance of current V2Ray platform,just like using VLESS XTLS direct mode.

已经经过性能对比测试,表现和VLESS一致.

Build failed on some platforms.


Transactor: GetBalance

Call rusk, method GetBalance, and return the result.

Related to #411

Fixed via #450


fixed broken images in cp-starter-digitalexp-mobilecards-2-create

fixed broken images in cp-starter-digitalexp-mobilecards-2-create

@jitendrakansal Next time, we prefer you not say "note" in a note, just give the note, like:

In CF trial accounts,...


Test performance on separate VMs for DUT and robot load test

Acceptance tests:

[x] Deploy robot load test on VM 1
[x] Deploy eUPF on another VM
[x] VMs are in 1 VLAN and hypervisor
[x] Test eupf performance

Up to 100-300Kpps. Hard to tune tcpreplay и VMs.


fix: align css hash in prebundling and disable hmr

alternative to #949
this preserves hmr for dependencies that are in node_modules but excluded from optimizeDeps and also ensures that cssHash function is applied consistently so that it does not break during hydration

cc @trueadm  @Conduitry
this fixes it too but does not prevent hmr in node_modules completely

hmr inside node_modules is blocked by 2 other problems, one being that node_modules is on vites watch ignore list by default, the other that at least with pnpm, handleHotUpdate gets called with symlink name and empty modules list so that the update is discarded by vite-plugin-svelte
see https://github.com/vitejs/vite/issues/8619#issuecomment-2254154530
we can still go ahead with this PR as it is a quite minimal fix for the problem described by https://github.com/sveltejs/svelte/issues/12601


Add Inter-Post Navigation

The inter-post navigation is able to be toggled by a build settings variable in _config.yml (inter_post_navigation).

:+1:


add support for nullable struct members when generating AWS SDKs

Motivation and Context

smithy-rs#1767 aws-sdk-rust#536
Description

This PR adds support for nullability i.e. much less unwraps will be required when using the AWS SDK. For generic clients, this new behavior can be enabled in codegen by setting generateOptionsForRequiredShapes = false in their codegen config.
Testing

Ran existing tests
Checklist

[x] I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates
[x] I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I think we should also note that certain fields are required in the generated docs

Currently blocked on https://github.com/aws/aws-models/pull/819

@Velfi the blocked changes have been merged


[R] AppVeyor CI for R package

Two additional appveyor jobs that build the R package:

cmake + VC2015 x64 build + unit tests
make + Rtools/mingw x64 build + R check
I've disabled the multiarch build for mingw since xgboost is crashing 32 bit R at exit on windows #2319

Codecov Report

Merging #2954 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2954   +/-   ##
=========================================
  Coverage     43.19%   43.19%
  Complexity      207      207
=========================================
  Files           155      155
  Lines         11606    11606
  Branches       1159     1159
=========================================
  Hits           5013     5013
  Misses         6265     6265
  Partials        328      328

Continue to review full report at Codecov.

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

The following are available as AppVeyor artifacts:

pre-built binary packages for Win64, built with Rtools (within the "rmingw" job) and VC2015 ("rmsvc" job)
source package
R check log file
when R check fails, its whole output would be kept in failure.zip

The latter three are only done in the "rmingw" job.


Has anyone tried different learning rates to assess their impact on experimental results?

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
During the process of full parameter fine-tuning, has there been an attempt to examine the effect of different lr sizes on the experimental results, such as lr=5e-5, 1e-5, 5e-6, and so on?
Expected behavior
No response
System Info
No response
Others
No response

Great question, I'm thinking about same thing :)

I've adopted this advice:

We found a larger rank (e.g. 256) and higher learning rate (e.g. 2e-4) worked best.

See here: https://github.com/allenai/open-instruct


Arduino Leonardo clone (Pro Micro) fails to reset and upload from Raspberry Pi

I'm trying to program an Arduino Pro Micro (Leonardo based) from a Raspberry Pi. I've taken the following steps but haven't yet succeeded in uploading anything using ino, or anything else.

Installed arduino-core (It's a headless setup so I'm assuming this is all I need)
Installed ino using sudo pip install ino
Followed the quickstart tutorial here. (In the code I changed the LED pin number to 17, as is needed on a Pro Micro)
Built the project using sudo ino build -m leonardo (successfully)
Attempted to upload using sudo ino upload -m leonardo
It returns:
Guessing serial port ... /dev/ttyACM0 (which is correct)
And then stops. I have to Ctrl-C to get out of it.

I've read about similar problems but no solution I've found has worked for me. Writing my own Python script to connect and disconnect at 1200 baud does not reset my Arduino.
I've tried this patch, as suggested on another thread with a similar problem. No change.
The same Arduino resets as expected when programming from Windows, using the Leonardo settings, so I'm confident the hardware is not at fault.

I discovered two problems:
A process running on my machine which was blocking access to the port and causing the crash, this is fixed now, so upload.py runs to completion.
The patch linked above uses the deprecated setBaudrate(1200) command, so I've changed it to ser.baudrate = 1200 instead.
It's still not working though. The code runs, waits for the reset, then attempts to run AVRDude, but the Arduino has not been reset into bootloader mode, so it can't connect, and returns:
Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding

I think I've located the problem to another service running on my Pi with access to the serial port. Ino didn't warn of any conflicts, but closing the service allowed it to upload correctly. I'll close this case.


Updated the vendor directory for the existing dependencies

Corrected the gopkg.in version name and added lib/pq

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/21/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/60/


[kafka] Specify heap size, fix memory overhead.

With the current default memory settings, the Kafka scheduler will get OOM killed when you try to do too much with it. This PR adds a) an option to specify the heap size and b) increases the memory requirement such that our scheduler doesn't get OOM killed.
cc @joestein

reviewing

LGTM.. limited testing but looks good.

thnx!


Inference on new satellite imagery

Hi,
I am trying to use infer.py with a new satellite image that I obtained to get results from your trained model. Therefore, I would like to ask you which packages do I need to install to use your model?
I am using Windows 10. I noticed that you have some print statements without parenthesis, so I guess you use Python 2.7. I found out that TensorFlow is not supported on Windows with Python 2.7. Does that mean that I can't run your code?
If not, please provide some guidance.

I don't know about TensorFlow on Windows, but yes it is Python 2.7 and need TensorFlow any version between 1.10 to 1.14 should be good (but not 2.0). Version for other packages shouldn't matter as much, if you get ImportError then you can install the package.

I created a virtual machine running Ubuntu 18.04 and I am using the following command to get results from your trained model:
python infer.py /home/.../data/model/model out-ntelo.graph --t /home/.../data/imagery/image.tiff --g /home/.../data//graphs --j /home/.../data/json/ --r 'new york' --s 0.03 --f 0.75

I receive the following error:
reading tiles
Traceback (most recent call last):
  File "infer.py", line 277, in <module>
    tiles = tileloader.Tiles(PATHS_PER_TILE_AXIS, SEGMENT_LENGTH, 16, TILE_MODE)
  File "/home/.../roadtracer-master/roadtracer/tileloader.py", line 149, in _init_
    self.all_tiles = get_tile_list()
  File "/home/.../roadtracer-master/roadtracer/tileloader.py", line 99, in get_tile_list
    with open(pytiles_path, 'r') as f:
IOError: [Errno 2] No such file or directory: '/home/.../roadtracer-master/data/json/pytiles.json'

I already changed the following part of the code inside infer.py:
USE_TL_LOCATIONS = False
MANUAL_POINT1 = geom.Point(101206, 869770)
MANUAL_POINT2 = geom.Point(101485, 869090)

The image that I want to use belongs to the Massachussets Road Detection Dataset and is the following:
https://drive.google.com/file/d/10ZJH80b5UMSE8VNhb49mwFbgSWkRhFkd/view?usp=sharing
Can you please help me solve this issue and infer results?

Using the following code:
python infer.py ~/.../roadtracer-master/data/model/model out.graph --t ~/.../roadtracer-master/data/imagery/ --g ~/.../roadtracer-master/data/graphs/ --j ~/.../roadtracer-master/data/json/

produces the following error:
IOError: [Errno 2] No such file or directory: '/.../roadtracer-master/data/graphs/chicago.graph'

I though that by specifying manual points, it wouldn't care about graph and json file. Can you please help me run infer.py for a new image, which I uploaded already in the previous comment?

Using the following code:
python infer.py ~/.../roadtracer-master/data/model/model out.graph --t ~/.../roadtracer-master/data/imagery/ --g ~/.../roadtracer-master/data/graphs/ --j ~/.../roadtracer-master/data/json/

produces the following error:
IOError: [Errno 2] No such file or directory: '/.../roadtracer-master/data/graphs/chicago.graph'

I though that by specifying manual points, it wouldn't care about graph and json file. Can you please help me run infer.py for a new image, which I uploaded already in the previous comment?

Hi, have you figured out how to inference on a custom image without graph? I did it this way:

Initialize a graph with the following lines. W and H refers to the width and height of the image, MANUAL_POINT1 can be any points as it will not be used during inference, MANUAL_POINT2 is the actual starting point that will be used.

    TILE_START = geom.Point(0, 0)
    TILE_END = TILE_START.add(geom.Point(W, H))

    rect = geom.Rectangle(TILE_START, TILE_END)
    start_loc = [{
        'point':MANUAL_POINT1,
        'edge_pos':None,
    },{
        'point':MANUAL_POINT2,
        'edge_pos':None
    }]
    tile_data = {
        'region': REGION,
        'rect': rect,
        'search_rect': rect.add_tol(-WINDOW_SIZE/2),
        'cache': None,
        'starting_locations': [start_loc],
    }

Use the function "make_path_input" to draw path already generated on the cropped image patch.

Forward the model with following lines:

        batch_angle_outputs, batch_stop_outputs, batch_detect_outputs = \
            session.run([m.angle_outputs, m.action_outputs, m.detect_outputs], feed_dict=feed_dict)
        batch_angle_outputs, batch_stop_outputs = fix_outputs(batch_angle_outputs, batch_stop_outputs)

Insert newly generated vertex into the graph.

My infer codes are modified based on the infer.py script, it generates slightly different results compared with the infer.py script, and sometimes, inference quality rely on the location where it starts tracing.


Enhance project_id/project_name variable assignment

Add code to handle conventions in CIS Services folder where convention is project_name != project_id. Also ensures project_id meets API requirements of < 30 characters, no spaces, lower case.

I pushed a new commit that removes the locals { project_id = foo } block and instead does a null check on project_id. I was worried about maintaining API/module compatibility and the naming convention in the CIS Services basically requires me to set project_id and project_name independently. The convention there is that project names get prefixed with a development tag (dev/qa/prod), but project_ids are set at creation without those tags in the name. The lower(replace(substr())) call I do on project_name should be compatible with previous and future releases of the module.
An example would go this way for the CIS Services folder:
CIS-VO wants to deploy a new application to GCP called foobar analyzer. It is going out initially as a dev version, so it looks like this:

project_name: DEV Foobar Analyzer
project_id: foobar-analyzer-fas4
Weeks or months later, the application deployment has been called a success. Rather than lose all the iterative changes, the entire project is promoted to PROD. The environment variable changes to PROD and based on this, the project_name changes to Foobar Analyzer, but the project_id can remain foobar-analyzer-fas4 without Terraform destroying/creating because of a project_id change. Then new Dev/QA versions can be deployed to support continued development.

PR labeler didn't run, but I think it's okay?


Added one new game and corrected 2 others (second attempt)

Apologies in advance for any issues!

Thank you for the fixes and additions. I will look later into it because I do not have too much time now and because there are conflicts and it cannot simply be rebased on the master branch without solving some conflicts (it seems you want to add Physics Platformer twice, it was already done with the last PR, you may have forgotten to synchronize again. The Git workflow there is a bit more complicated than necessary).

I don't think I successfully updated my fork after your previous commit.  If it's easier for you, I'll cancel this PR, refork and re-add my changes, so there should be no conflicts?

Okay. Sounds good to me.

This recipe https://gist.github.com/Chaser324/ce0505fbed06b947d962 might be helpful.


Shift+Tab should respect sequence of SearchField in a form with SuggestionState.hidden

Describe the bug
If the searchfield is in a form, move to the next field and try to return with shift+tab, it stops working, that is, it only returns to the inner field with 3x shift+tab, and if before 3x, it stops selecting the desired option.
It seems to me that it is lost.
The problem occurs when the searchfield is between other TextFormField's and suggestionState is marked as Suggestion.hidden, so that when you return with shift+tab, you cannot navigate between the options with the Tab
To Reproduce
Try to return with shift+tab after passing through the searchfield field (when the searchfield is between other TextFormField's and suggestionState is marked as Suggestion.hidden)
Expected behavior
Just respect the sequence of the fields
Code sample

Show code sample
import 'package:flutter/material.dart';
import 'package:searchfield/searchfield.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter App',
      theme: ThemeData(
        colorSchemeSeed: Colors.indigo,
        useMaterial3: true,
        brightness: Brightness.light,
      ),
      darkTheme: ThemeData(
        colorSchemeSeed: Colors.blue,
        useMaterial3: true,
        brightness: Brightness.dark,
      ),
      home: SearchFieldSample(),
      debugShowCheckedModeBanner: false,
    );
  }
}

class SearchFieldSample extends StatefulWidget {
  const SearchFieldSample({Key? key}) : super(key: key);

  @override
  State<SearchFieldSample> createState() => _SearchFieldSampleState();
}

class _SearchFieldSampleState extends State<SearchFieldSample> {
  int suggestionsCount = 12;
  final focus1 = FocusNode();
  final focus2 = FocusNode();
  final focus3 = FocusNode();

  @override
  void initState() {
    suggestions = [
      'United States',
      'Germany',
      'Washington',
      'Paris',
      'Jakarta',
      'Australia',
      'India',
      'Czech Republic',
      'Lorem Ipsum',
    ];
    super.initState();
  }

  final TextEditingController searchController = TextEditingController();
  var suggestions = <String>[];
  int counter = 0;
  @override
  Widget build(BuildContext context) {
    Widget searchChild(x) => Padding(
          padding: const EdgeInsets.symmetric(vertical: 4.0, horizontal: 12),
          child: Text(x, style: TextStyle(fontSize: 18, color: Colors.black)),
        );
    return Scaffold(
        appBar: AppBar(title: Text('Searchfield Keyboard Support')),
        floatingActionButton: FloatingActionButton(
          onPressed: () {
            setState(() {
              suggestionsCount++;
              counter++;
              suggestions.add('suggestion $suggestionsCount');
            });
          },
          child: Icon(Icons.add),
        ),
        body: Padding(
          padding: const EdgeInsets.all(8.0),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.start,
            children: [
              TextFormField(
                  focusNode: focus1,
                  textInputAction: TextInputAction.next,
                  autovalidateMode: AutovalidateMode.onUserInteraction,
                  decoration: InputDecoration(
                    labelText: 'Flutter TextFormField',
                  ),
                  validator: (value) {
                    if (value == null || value.length < 4) {
                      return 'error';
                    }
                    return null;
                  }),
              SizedBox(
                height: 50,
              ),
              SearchField(
                focusNode: focus2,
                suggestionDirection: SuggestionDirection.flex,
                onSearchTextChanged: (query) {
                  final filter = suggestions
                      .where((element) =>
                          element.toLowerCase().contains(query.toLowerCase()))
                      .toList();
                  return filter
                      .map((e) =>
                          SearchFieldListItem<String>(e, child: searchChild(e)))
                      .toList();
                },
                onTap: () {},
                controller: searchController,
                autovalidateMode: AutovalidateMode.onUserInteraction,
                validator: (value) {
                  if (value == null || !suggestions.contains(value.trim())) {
                    return 'Enter a valid country name';
                  }
                  return null;
                },
                onSubmit: (x) {},
                autofocus: false,
                key: const Key('searchfield'),
                hint: 'Search by country name',
                itemHeight: 50,
                onTapOutside: (x) {
                  // focus.unfocus();
                },
                suggestionStyle:
                    const TextStyle(fontSize: 18, color: Colors.black),
                searchStyle: TextStyle(fontSize: 18, color: Colors.black),
                suggestionItemDecoration: BoxDecoration(
                  // color: Colors.grey[100],
                  // borderRadius: BorderRadius.circular(10),
                  border: Border(
                    bottom: BorderSide(
                      color: Colors.grey.shade200,
                      width: 1,
                    ),
                  ),
                ),
                searchInputDecoration: InputDecoration(
                  hintStyle: TextStyle(fontSize: 18, color: Colors.grey),
                  focusedBorder: OutlineInputBorder(
                    borderRadius: BorderRadius.circular(24),
                    borderSide: const BorderSide(
                      width: 1,
                      color: Colors.orange,
                      style: BorderStyle.solid,
                    ),
                  ),
                  border: OutlineInputBorder(
                    borderRadius: BorderRadius.circular(24),
                    borderSide: const BorderSide(
                      width: 1,
                      color: Colors.black,
                      style: BorderStyle.solid,
                    ),
                  ),
                  fillColor: Colors.white,
                  filled: true,
                  contentPadding: const EdgeInsets.symmetric(
                    horizontal: 20,
                  ),
                ),
                suggestionsDecoration: SuggestionDecoration(
                    // border: Border.all(color: Colors.orange),
                    // elevation: 8.0,
                    selectionColor: Colors.grey.shade100,
                    hoverColor: Colors.purple.shade100,
                    gradient: LinearGradient(
                      colors: [
                        Color(0xfffc466b),
                        Color.fromARGB(255, 103, 128, 255)
                      ],
                      stops: [0.25, 0.75],
                      begin: Alignment.topLeft,
                      end: Alignment.bottomRight,
                    ),
                    borderRadius: BorderRadius.only(
                      bottomLeft: Radius.circular(10),
                      bottomRight: Radius.circular(10),
                    )),
                suggestions: suggestions
                    .map((e) =>
                        SearchFieldListItem<String>(e, child: searchChild(e)))
                    .toList(),
                suggestionState: Suggestion.hidden,
                onSuggestionTap: (SearchFieldListItem<String> x) {
                  print('suggestion');
                  FocusScope.of(context).requestFocus(focus3);
                },
              ),
              SizedBox(
                height: 50,
              ),
              TextFormField(
                  focusNode: focus3,
                  autovalidateMode: AutovalidateMode.onUserInteraction,
                  decoration: InputDecoration(
                    labelText: 'Flutter TextFormField',
                  ),
                  validator: (value) {
                    if (value == null || value.length < 4) {
                      return 'error';
                    }
                    return null;
                  }),
            ],
          ),
        ));
  }
}

In fact, it "returns" to the options, even if the boxsuggestions are hidden, giving the impression of having to press shift+tab several times.
Somehow, the component should only leave the main field if a previous option is already selected when executing shift+tab, as it behaves in the normal tab (advancing).

This exception is occurring:
Another exception was thrown: Assertion failed: file:///C:/flutter/packages/flutter/lib/src/widgets/overlay.dart:207:12
Another exception was thrown: This widget has been unmounted, so the State no longer has a context (and should be considered defunct).

Hello @DessisInformatica, Thanks for filing the issue, and Good catch. Will get that fixed soon.

Hi @DessisInformatica, Navigating between suggestions with the tab key should only work if suggestions are visible on the screen, Is this the intended behavior?  Searchfield will only lose focus (switch to other widget) with Tab key when Overlay (Suggestions)is not shown.

I have made a PR as per the above fix can you please test this behavior by adding the following to pubspec.yaml
  searchfield:
    git:
      url: https://github.com/maheshmnj/searchfield.git
      ref: fix-125

Thanks for answering.
I took the test, but this issue is still not good.
Follow the code. If you test, you will see that the sequence between widgets appears to be a problem.
Thank you for your attention.
import 'package:flutter/material.dart';
import 'package:searchfield/searchfield.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter App',
      theme: ThemeData(
        colorSchemeSeed: Colors.indigo,
        useMaterial3: true,
        brightness: Brightness.light,
      ),
      darkTheme: ThemeData(
        colorSchemeSeed: Colors.blue,
        useMaterial3: true,
        brightness: Brightness.dark,
      ),
      home: SearchFieldSample(),
      debugShowCheckedModeBanner: false,
    );
  }
}

class SearchFieldSample extends StatefulWidget {
  const SearchFieldSample({Key? key}) : super(key: key);

  @override
  State<SearchFieldSample> createState() => _SearchFieldSampleState();
}

class _SearchFieldSampleState extends State<SearchFieldSample> {
  int suggestionsCount = 12;
  final foco1 = FocusNode();
  final foco2 = FocusNode();
  final foco3 = FocusNode();
  TextEditingController cont1 = TextEditingController();
  TextEditingController cont2 = TextEditingController();
  TextEditingController cont3 = TextEditingController();

  @override
  void initState() {
    suggestions = [
      'United States',
      'Germany',
      'Washington',
      'Paris',
      'Jakarta',
      'Australia',
      'India',
      'Czech Republic',
      'Lorem Ipsum',
    ];
    super.initState();
  }

  final TextEditingController searchController = TextEditingController();
  var suggestions = <String>[];
  int counter = 0;
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(title: const Text('Searchfield Keyboard Support')),
        body: Padding(
          padding: const EdgeInsets.all(8.0),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.start,
            children: [
              SizedBox(
                width: 200,
                height: 50,
                child: SearchField(
                  focusNode: foco1,
                  controller: cont1,
                  hint: 'Basic SearchField',
                  suggestions: ['ABC', 'DEF', 'GHI', 'JKL']
                      .map(SearchFieldListItem<String>.new)
                      .toList(),
                  suggestionState: Suggestion.expand,
                ),
              ),
              SizedBox(
                width: 200,
                height: 50,
                child: SearchField(
                  focusNode: foco2,
                  controller: cont2,
                  hint: 'Basic SearchField',
                  suggestions: ['ABC', 'DEF', 'GHI', 'JKL']
                      .map(SearchFieldListItem<String>.new)
                      .toList(),
                  suggestionState: Suggestion.expand,
                ),
              ),
              SizedBox(
                width: 200,
                height: 50,
                child: SearchField(
                  focusNode: foco3,
                  controller: cont3,
                  hint: 'Basic SearchField',
                  suggestions: ['ABC', 'DEF', 'GHI', 'JKL']
                      .map(SearchFieldListItem<String>.new)
                      .toList(),
                  suggestionState: Suggestion.expand,
                ),
              ),
            ],
          ),
        ));
  }
}

Thanks for the response @DessisInformatica, Can you please clarify how the behavior should be? This is currently as described above.

Searchfield will only lose focus (switch to other widget) with Tab key when Overlay (Suggestions)is not shown.

Alternatively, can you test this behavior by just commenting this line
https://github.com/maheshmnj/searchfield/blob/ef0b40accaf8041c6a852c727fb5324c5e8cbb43/lib/src/searchfield.dart#L755
But you won't be able to navigate between suggestions using tab key.

Upon investigating little about different web components I have found that tab/shift+tab should only switch focus to other components and not navigatet the suggestions so the above fix should work. Looking forward to hearing from you @DessisInformatica

This will be published in the upcoming release v1.0.0


Text style for image titles/credits?

Looking at the "Updated Workplan" post, I find it hard to distinguish the name & credit info for the images from the surrounding text, because it is the same size, font, and style as the prose content.  Can we change this--maybe use a sans serif or at least italics?

Fixed: https://github.com/e-lo/fast-trips-project/commit/e816d93e39c4c99db129ebfba645c5fb4208edb7


WalkingHeartRateAverage is not exposed in JS

Describe the bug
Permissions and methods exist in the native code to access WalkingHeartRateAverage. However, no code exists on the JS side to actually read the values or set the permission.
Expected behavior
Permission and getter should exist in JS.

I can look into this and create a PR to resolve.