Error: Building package boost-regex:x64-windows failed with: BUILD_FAILED

I'm on windows 10 and Visual Studio 2017, I was trying to install the whole boost package with vcpkg install boost:x64-windows and it was fine in the beginning then when building the regex library it failed.
There is no space in my vcpkg root. I try to reinstall VS2017 but no use.I have already changed VS2017 language from chinese to English
`PS E:\lastdesign\Facial_Details_Synthesis\src\proxyEstimator\vcpkg> ./vcpkg install boost  --triplet x64-windows
The following packages will be built and installed:
boost[core]:x64-windows

boost-accumulators[core]:x64-windows
boost-algorithm[core]:x64-windows
boost-align[core]:x64-windows
boost-any[core]:x64-windows
boost-asio[core]:x64-windows
boost-assign[core]:x64-windows
boost-atomic[core]:x64-windows
boost-beast[core]:x64-windows
boost-bimap[core]:x64-windows
boost-callable-traits[core]:x64-windows
boost-chrono[core]:x64-windows
boost-circular-buffer[core]:x64-windows
boost-compute[core]:x64-windows
boost-container[core]:x64-windows
boost-context[core]:x64-windows
boost-contract[core]:x64-windows
boost-convert[core]:x64-windows
boost-coroutine[core]:x64-windows
boost-coroutine2[core]:x64-windows
boost-crc[core]:x64-windows
boost-date-time[core]:x64-windows
boost-disjoint-sets[core]:x64-windows
boost-dll[core]:x64-windows
boost-dynamic-bitset[core]:x64-windows
boost-endian[core]:x64-windows
boost-exception[core]:x64-windows
boost-fiber[core]:x64-windows
boost-filesystem[core]:x64-windows
boost-flyweight[core]:x64-windows
boost-foreach[core]:x64-windows
boost-format[core]:x64-windows
boost-functional[core]:x64-windows
boost-geometry[core]:x64-windows
boost-gil[core]:x64-windows
boost-graph[core]:x64-windows
boost-graph-parallel[core]:x64-windows
boost-hana[core]:x64-windows
boost-heap[core]:x64-windows
boost-histogram[core]:x64-windows
boost-hof[core]:x64-windows
boost-icl[core]:x64-windows
boost-interprocess[core]:x64-windows
boost-interval[core]:x64-windows
boost-intrusive[core]:x64-windows
boost-io[core]:x64-windows
boost-iostreams[core]:x64-windows
boost-lambda[core]:x64-windows
boost-lexical-cast[core]:x64-windows
boost-local-function[core]:x64-windows
boost-locale[core]:x64-windows
boost-lockfree[core]:x64-windows
boost-log[core]:x64-windows
boost-logic[core]:x64-windows
boost-math[core]:x64-windows
boost-metaparse[core]:x64-windows
boost-mp11[core]:x64-windows
boost-msm[core]:x64-windows
boost-multi-array[core]:x64-windows
boost-multi-index[core]:x64-windows
boost-multiprecision[core]:x64-windows
boost-odeint[core]:x64-windows
boost-outcome[core]:x64-windows
boost-parameter[core]:x64-windows
boost-parameter-python[core]:x64-windows
boost-phoenix[core]:x64-windows
boost-poly-collection[core]:x64-windows
boost-polygon[core]:x64-windows
boost-pool[core]:x64-windows
boost-process[core]:x64-windows
boost-program-options[core]:x64-windows
boost-property-map[core]:x64-windows
boost-property-tree[core]:x64-windows
boost-proto[core]:x64-windows
boost-ptr-container[core]:x64-windows
boost-python[core]:x64-windows
boost-qvm[core]:x64-windows
boost-random[core]:x64-windows
boost-range[core]:x64-windows
boost-ratio[core]:x64-windows
boost-rational[core]:x64-windows
boost-regex[core]:x64-windows
boost-safe-numerics[core]:x64-windows
boost-scope-exit[core]:x64-windows
boost-serialization[core]:x64-windows
boost-signals2[core]:x64-windows
boost-sort[core]:x64-windows
boost-spirit[core]:x64-windows
boost-stacktrace[core]:x64-windows
boost-statechart[core]:x64-windows
boost-system[core]:x64-windows
boost-test[core]:x64-windows
boost-thread[core]:x64-windows
boost-timer[core]:x64-windows
boost-tokenizer[core]:x64-windows
boost-tti[core]:x64-windows
boost-type-erasure[core]:x64-windows
boost-ublas[core]:x64-windows
boost-units[core]:x64-windows
boost-unordered[core]:x64-windows
boost-uuid[core]:x64-windows
boost-variant[core]:x64-windows
boost-variant2[core]:x64-windows
boost-vmd[core]:x64-windows
boost-wave[core]:x64-windows
boost-winapi[core]:x64-windows
boost-xpressive[core]:x64-windows
boost-yap[core]:x64-windows
bzip2[core]:x64-windows
libffi[core]:x64-windows
openssl[core]:x64-windows
openssl-windows[core]:x64-windows
python3[core]:x64-windows
zstd[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/114: boost-regex:x64-windows
Building package boost-regex[core]:x64-windows...
-- Using cached E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/downloads/boostorg-regex-boost-1.72.0.tar.gz
-- Using source at E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/src/ost-1.72.0-a233385537
-- Building x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/tools/boost-build/b2.exe --stagedir=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/x64-windows-rel/stage --build-dir=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/x64-windows-rel --user-config=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/x64-windows-rel/user-config.jam -j8 --debug-configuration --debug-building --debug-generators --disable-icu --ignore-site-config --hash -q -sZLIB_INCLUDE=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/include -sBZIP2_INCLUDE=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/include -sLZMA_INCLUDE=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/include -sZSTD_INCLUDE=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/include threading=multi threadapi=win32 runtime-link=shared link=shared address-model=64 architecture=x86 toolset=msvc -sZLIB_BINARY=zlib -sZLIB_LIBPATH=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/lib -sBZIP2_BINARY=bz2 -sBZIP2_LIBPATH=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/lib -sLZMA_BINARY=lzma -sLZMA_LIBPATH=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/lib -sZSTD_BINARY=zstd -sZSTD_LIBPATH=E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/lib variant=release debug-symbols=on
Working Directory: E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/src/ost-1.72.0-a233385537/build
Error code: 1
See logs for more information:
E:\lastdesign\Facial_Details_Synthesis\src\proxyEstimator\vcpkg\buildtrees\boost-regex\build-x64-windows-rel-out.log

Call Stack (most recent call first):
installed/x64-windows/share/boost-build/boost-modular-build.cmake:288 (vcpkg_execute_required_process)
ports/boost-regex/portfile.cmake:20 (boost_modular_build)
scripts/ports.cmake:94 (include)
Error: Building package boost-regex: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: boost-regex:x64-windows
Vcpkg version: 2020.01.17-nohash
Additionally, attach any relevant sections from the log files above.`
Here are build-x64-windows-rel-out.log
notice: found boost-build.jam at E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/tools/boost-build/boost-build.jam notice: loading Boost.Build from E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/tools/boost-build/src/kernel notice: Site configuration files will be ignored due to the notice: --ignore-site-config command-line option. notice: Loading explicitly specified user configuration file:     E:\lastdesign\Facial_Details_Synthesis\src\proxyEstimator\vcpkg\buildtrees\boost-regex\x64-windows-rel\user-config.jam notice: Searching 'E:\lastdesign\Facial_Details_Synthesis\src\proxyEstimator\vcpkg\buildtrees\boost-regex\x64-windows-rel' for user-config configuration file 'user-config.jam'. notice: Loading user-config configuration file 'user-config.jam' from 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/buildtrees/boost-regex/x64-windows-rel'. notice: [msvc-cfg] msvc-14.1 detected, command: 'D:\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\HostX64\arm\cl.exe' notice: will use 'D:\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe' for msvc, condition <toolset>msvc-14.1 notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>32', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>32', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>64', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat amd64' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>64', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat amd64' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_ia64' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>64', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_ia64' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_arm' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>32', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_arm' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_arm64' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>64', setup: 'E:/lastdesign/Facial_Details_Synthesis/src/proxyEstimator/vcpkg/installed/x64-windows/share/boost-build/nothing.bat x86_arm64' building project Jamfile<E:\lastdesign\Facial_Details_Synthesis\src\proxyEstimator\vcpkg\buildtrees\boost-regex\src\ost-1.72.0-a233385537\build>  ('object(project-target)@280') with <address-model>64 <architecture>x86 <debug-symbols>on <link>shared <runtime-link>shared <threadapi>win32 <threading>multi <toolset>msvc <variant>release
build-x64-windows-rel-out.log

@Rita-ritally, could you get a clean source and try to build again? I can't repro this issue locally.
Starting package 28/28: boost-regex:x86-windows
Building package boost-regex[core]:x86-windows...
-- Downloading https://github.com/boostorg/regex/archive/boost-1.72.0.tar.gz...
-- Extracting source F:/VCPKG/src/downloads/boostorg-regex-boost-1.72.0.tar.gz
-- Using source at F:/VCPKG/src/buildtrees/boost-regex/src/ost-1.72.0-a233385537
-- Building x86-windows-rel
-- Building x86-windows-rel done
-- Building x86-windows-dbg
-- Building x86-windows-dbg done
-- Packaging x86-windows-rel
-- Packaging x86-windows-rel done
-- Packaging x86-windows-dbg
-- Packaging x86-windows-dbg done
-- Packaging headers
-- Packaging headers done
-- Using cached F:/VCPKG/src/downloads/boost_LICENSE_1_0.txt
-- Installing: F:/VCPKG/src/packages/boost-regex_x86-windows/share/boost-regex/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-regex[core]:x86-windows... done
Installing package boost-regex[core]:x86-windows...
Installing package boost-regex[core]:x86-windows... done
Elapsed time for package boost-regex:x86-windows: 29.45 s
Total elapsed time: 2.17 min

@Rita-ritally, could you get a clean source and try to build again? I can't repro this issue locally.
Starting package 28/28: boost-regex:x86-windows
Building package boost-regex[core]:x86-windows...
-- Downloading https://github.com/boostorg/regex/archive/boost-1.72.0.tar.gz...
-- Extracting source F:/VCPKG/src/downloads/boostorg-regex-boost-1.72.0.tar.gz
-- Using source at F:/VCPKG/src/buildtrees/boost-regex/src/ost-1.72.0-a233385537
-- Building x86-windows-rel
-- Building x86-windows-rel done
-- Building x86-windows-dbg
-- Building x86-windows-dbg done
-- Packaging x86-windows-rel
-- Packaging x86-windows-rel done
-- Packaging x86-windows-dbg
-- Packaging x86-windows-dbg done
-- Packaging headers
-- Packaging headers done
-- Using cached F:/VCPKG/src/downloads/boost_LICENSE_1_0.txt
-- Installing: F:/VCPKG/src/packages/boost-regex_x86-windows/share/boost-regex/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-regex[core]:x86-windows... done
Installing package boost-regex[core]:x86-windows...
Installing package boost-regex[core]:x86-windows... done
Elapsed time for package boost-regex:x86-windows: 29.45 s
Total elapsed time: 2.17 min

Do you mean I delete the source of  vcpkg/downloads/boostorg-regex and build again?

https://github.com/microsoft/vcpkg/issues/9945#issuecomment-583288695 @PhoebeHui

@PhoebeHui  Do you mean I delete the source of vcpkg/downloads/boostorg-regex and build again?

@Rita-ritally, sorry for my late reply.
Could you try the following steps and see if the issue still occur?
./vcpkg remove boost-modular-build-helper --recurse
./vcpkg remove boost-build --recurse
./vcpkg install boost-regex

@PhoebeHui  it doesn't work......
`PS C:\Users\Rita_悦> cd E:\lastdesign\vcpkg
PS E:\lastdesign\vcpkg> ./vcpkg remove boost-modular-build-helper --recurse
The following packages will be removed:
boost-modular-build-helper:x64-windows
Removing package boost-modular-build-helper:x64-windows...
Removing package boost-modular-build-helper:x64-windows... done
Purging package boost-modular-build-helper:x64-windows...
Purging package boost-modular-build-helper:x64-windows... done
PS E:\lastdesign\vcpkg> ./vcpkg remove boost-build --recurse
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be removed:
boost-build:x64-windows
Removing package boost-build:x64-windows...
Removing package boost-build:x64-windows... done
Purging package boost-build:x64-windows...
Purging package boost-build:x64-windows... done
PS E:\lastdesign\vcpkg> ./vcpkg install boost-regex
Computing installation plan...
The following packages will be built and installed:

boost-build[core]:x64-windows
boost-modular-build-helper[core]:x64-windows
boost-regex[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/3: boost-build:x64-windows
Building package boost-build[core]:x64-windows...
-- Using cached E:/lastdesign/vcpkg/downloads/boostorg-build-boost-1.72.0.tar.gz
-- Using source at E:/lastdesign/vcpkg/buildtrees/boost-build/src/ost-1.72.0-fa8b817276
-- Using cached E:/lastdesign/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached E:/lastdesign/vcpkg/downloads/boost-1.72.0-boostcpp.jam
-- Installing: E:/lastdesign/vcpkg/packages/boost-build_x64-windows/share/boost-build/copyright
-- Installing: E:/lastdesign/vcpkg/packages/boost-build_x64-windows/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-build[core]:x64-windows... done
Installing package boost-build[core]:x64-windows...
Installing package boost-build[core]:x64-windows... done
Elapsed time for package boost-build:x64-windows: 35.24 s
Starting package 2/3: boost-modular-build-helper:x64-windows
Building package boost-modular-build-helper[core]:x64-windows...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-modular-build-helper[core]:x64-windows... done
Installing package boost-modular-build-helper[core]:x64-windows...
Installing package boost-modular-build-helper[core]:x64-windows... done
Elapsed time for package boost-modular-build-helper:x64-windows: 2.243 s
Starting package 3/3: boost-regex:x64-windows
Building package boost-regex[core]:x64-windows...
-- Using cached E:/lastdesign/vcpkg/downloads/boostorg-regex-boost-1.72.0.tar.gz
-- Using source at E:/lastdesign/vcpkg/buildtrees/boost-regex/src/ost-1.72.0-a233385537
-- Building x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: E:/lastdesign/vcpkg/installed/x64-windows/tools/boost-build/b2.exe --stagedir=E:/lastdesign/vcpkg/buildtrees/boost-regex/x64-windows-rel/stage --build-dir=E:/lastdesign/vcpkg/buildtrees/boost-regex/x64-windows-rel --user-config=E:/lastdesign/vcpkg/buildtrees/boost-regex/x64-windows-rel/user-config.jam -j8 --debug-configuration --debug-building --debug-generators --disable-icu --ignore-site-config --hash -q -sZLIB_INCLUDE=E:/lastdesign/vcpkg/installed/x64-windows/include -sBZIP2_INCLUDE=E:/lastdesign/vcpkg/installed/x64-windows/include -sLZMA_INCLUDE=E:/lastdesign/vcpkg/installed/x64-windows/include -sZSTD_INCLUDE=E:/lastdesign/vcpkg/installed/x64-windows/include threading=multi threadapi=win32 runtime-link=shared link=shared address-model=64 architecture=x86 toolset=msvc -sZLIB_BINARY=zlib -sZLIB_LIBPATH=E:/lastdesign/vcpkg/installed/x64-windows/lib -sBZIP2_BINARY=bz2 -sBZIP2_LIBPATH=E:/lastdesign/vcpkg/installed/x64-windows/lib -sLZMA_BINARY=lzma -sLZMA_LIBPATH=E:/lastdesign/vcpkg/installed/x64-windows/lib -sZSTD_BINARY=zstd -sZSTD_LIBPATH=E:/lastdesign/vcpkg/installed/x64-windows/lib variant=release debug-symbols=on
Working Directory: E:/lastdesign/vcpkg/buildtrees/boost-regex/src/ost-1.72.0-a233385537/build
Error code: 1
See logs for more information:
E:\lastdesign\vcpkg\buildtrees\boost-regex\build-x64-windows-rel-out.log

Call Stack (most recent call first):
installed/x64-windows/share/boost-build/boost-modular-build.cmake:286 (vcpkg_execute_required_process)
ports/boost-regex/portfile.cmake:20 (boost_modular_build)
scripts/ports.cmake:90 (include)
Error: Building package boost-regex: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: boost-regex:x64-windows
Vcpkg version: 2020.02.04-nohash
Additionally, attach any relevant sections from the log files above.`

@PhoebeHui  I think my visual studio settings may have some problems, but i don't know the specific

@Rita-ritally, thanks for your updates!
Could you also attach failure log E:\lastdesign\vcpkg\buildtrees\boost-regex\build-x64-windows-rel-out.log?

@PhoebeHui
here is my failure log
build-x64-windows-rel-out.log

@PhoebeHui thank you for your reply
this is my failure log
build-x64-windows-rel-out.log

@Rita-ritally, from your log, it seems 'boost_regex-vc141-mt-x64-1_72.dll' linked correctly, I didn't see any compiler errors or link errors, so it's unclear for me.
Boost currently upgrade to 1_73, could you get latest source and see this issue still exist?

I have the same issue and try to fix it.
@Rita-ritally : did you find a solution ?
Working Directory: C:/local/vcpkg/buildtrees/boost-regex/src/ost-1.73.0-a7219fe4ec.clean/build
Error code: 1
See logs for more information:
  C:\local\vcpkg\buildtrees\boost-regex\build-x64-windows-rel-out.log

Call Stack (most recent call first):
installed/x64-windows/share/boost-build/boost-modular-build.cmake:339 (vcpkg_execute_required_process)
ports/boost-regex/portfile.cmake:12 (boost_modular_build)
scripts/ports.cmake:79 (include)
Error: Building package boost-regex:x64-windows failed with: BUILD_FAILED

Yes！！I changed my computer ID Rita_悦 to Rita，which not contains chinese character. It ran successful after it！！You can try it～
| |
廉悦
|
|
<EMAIL_ADDRESS>|
签名由 网易邮箱大师 定制
On 09/23/2020 11:02, SwordenBlue wrote:
I have the same issue and try to fix it.
@Rita-ritally : did you find a solution ?
Working Directory: C:/local/vcpkg/buildtrees/boost-regex/src/ost-1.73.0-a7219fe4ec.clean/build
Error code: 1
See logs for more information:
C:\local\vcpkg\buildtrees\boost-regex\build-x64-windows-rel-out.log
Call Stack (most recent call first):
installed/x64-windows/share/boost-build/boost-modular-build.cmake:339 (vcpkg_execute_required_process)
ports/boost-regex/portfile.cmake:12 (boost_modular_build)
scripts/ports.cmake:79 (include)
Error: Building package boost-regex:x64-windows failed with: BUILD_FAILED
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

It looks similar issue with https://github.com/microsoft/vcpkg/issues/15201, the Chinese characters cause this issue, I will use that issue to track the Upstream changes.

It looks similar issue with https://github.com/microsoft/vcpkg/issues/15201, the Chinese characters cause this issue, I will use that issue to track the Upstream changes.


Add compassRuntimeID to OperationStatus GraphQL struct to return information if the runtime is registered in Compass

Implementation of https://github.com/kyma-project/control-plane/issues/3085 Proposal 1
Adding new field compassRuntimeID to OperationStatus GraphQL struct to return information whether runtime is registered in Compass.
The value returned by this field is now the same as runtimeID the Runtime is still registered in Compass.
This is first part of the migration.
Than we will run migration to annotate all Kyma resources with compass-runtime-id-for-migration value.
Next step will be Removing Compass integration code from the Provisioner
Finally the field compassRuntimeID will be returned as empty and runtimeID will contain some random ID generated locally in Provisioner.

/retest

/retest

/test pre-main-provisioner-e2e-tests

The compassRuntimeID as a field of the RuntimeStatus looks good. This change seems to be backward compatible (just adding new field in the result) so you can merge it as soon as possible.


Is there a way to connect several roombas at the same time?

I'm trying to do it, but I don't know what the way is, I know that the issues are not for this, but I don't find an answer on the other hand

From one computer, you should be able to launch multiple instances of ca_driver for each robot.
For example, after connecting the robots to your computer, you should be able to see each in the devices list:
$ ls /dev/ttyUSB*
/dev/ttyUSB0
/dev/ttyUSB1

Once you've identified the device paths, you can create a custom parameter file for each robot, changing the dev parameter (see the default.yaml for an example).  You should probably update the base_frame and odom_frame values for each robot so that they don't clash. Then you can load the parameters in a launch file (see example launch file.
You should also namespace the driver node for each robot so they do not clash. You can do this by adding a ns attribute to the node tag in your launch file.

thanks for the fast response :) , i have one more question , what's a ns attribute?

i solve it with ns! (namespace) thanks a lot! <3

happy to help!


Text: Placeholder, fill and function to go to the next line.

Contact Details
<EMAIL_ADDRESS>Feature
1- The copied text does not fill the "placeholder" text area.
Now I need to select the number of lines in the "max lines" section, but I expected it to be done automatically. Also, because I cannot know how many lines I need for the copied text.
2- Within the text field in the Node section, if I go to a new line in the entered text (by pressing "enter"), it treats it as a completion. The same thing happens if I press shift + enter.
https://github.com/buildwiththeta/buildwiththeta/assets/91491171/c23c02f8-39e9-43d5-9233-ea1346bad60a
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @kasapiniz let’s add an empty value to maxLines for Texts


Not getting notifications on IOS

I'm using ESign and have an Apple developer certificate my other apps send notis just not bunny. I have notis turned on in app and settings.

Not for everyone, probably something wrong on your end. You can seek support from the discord server (I am not an expert in iOS stuff though)

Also getting this issue, did you manage to get it working?


ReadMe-mn.md added

Hi Zorig,
Thank for you the contribution. :+1:
The new translation and changes look good. 17 commits is quite a large number for 1 PR though. If possible, could you please squash these changes to a single commit resend them as a new PR? Thanks.

@Maikuolan sure, oh i think i did something wrong to do squash them

@Maikuolan like told it here i did that

Hm.. I think something has gone wrong. When I look at the changes now, the completed translation isn't showing, and instead, only two other files seem to be changed:

I think, I'll try some experimental PRs from your fork to my fork to try to figure it out before merging this or others back to the parent.

Yeah.. Something has definitely gone wrong there, I think. I can't actually see the newly completed translation in your fork anymore. 😟
When I tried pulling from your fork into my fork, it also wasn't showing there either.
I'm not sure what others would do in this and other similar situations, or whether there are better solutions, but personally, what I would do is just close the PR, manually copy out the modified files from the repository to a separate location temporarily, delete the entire branch, rebase, fork a new a branch, move the modified files back into to newly forked branch, commit, sync, and then send a PR from that (that should eliminate any risk of corrupt/unwanted commits and so on). In this case though, because your working branch has been master, it might be worth just deleting the fork and reforking from the parent (of course, if you go with this idea, don't forget to backup your work beforehand, so that it doesn't get accidentally deleted with everything else).

Ok got it let me do that immediately
On Aug 6, 2017 2:50 AM, "Caleb Mazalevskis"<EMAIL_ADDRESS>wrote:

Yeah.. Something has definitely gone wrong there, I think. I can't
actually see the newly completed translation in your fork anymore. 😟
When I tried pulling from your fork into my fork, it also wasn't showing
there either.
I'm not sure what others would do in this and other similar situations, or
whether there are better solutions, but personally, what I would do is just
close the PR, manually copy out the modified files from the repository to a
separate location temporarily, delete the entire branch, rebase, fork a new
a branch, move the modified files back into to newly forked branch, commit,
sync, and then send a PR from that (that should eliminate any risk of
corrupt/unwanted commits and so on). In this case though, because your
working branch has been master, it might be worth just deleting the fork
and reforking from the parent (of course, if you go with this idea, don't
forget to backup your work beforehand, so that it doesn't get accidentally
deleted with everything else).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shieldfy/API-Security-Checklist/pull/81#issuecomment-320463312,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABN-6JD3nfnPp0iFsMzKThogM0ES3hg4ks5sVLlmgaJpZM4OqE-F
.


Update to changedNameHow field

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/NFDIV-753
Change description
Update the changeNameHow field so that it can be used as checkboxes on the FE
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

you will need to bump the case type for this as the type of field has changed.
But also you will need to update gas type configured for manage cases in xui


Add instruction to manually npm i functions dir

I'm not sure if I only had this problem because of using Yarn instead of NPM, but I had to manually run npm i within the functions dir in order to get the deploy:functions script to run correctly.

Ahhh, yes yes. I'll update the command. Thank you!

@TheNando looks like there are already instructions in the README to install in the functions directory already.


default.nix at repo root, for nix-env -qa

Fix for https://github.com/NixOS/nixos-hardware/issues/52

Thanks!


save image as JPEG; use blob API

Hi @everestpipkin, thanks for your work on this!
This PR makes two related changes to the saving functionality:

Images are stored as a JPEG rather than a PNG, providing much-reduced file sizes.
The code now uses the toBlob() functionality rather than toDataURL() for notably better performance.

I hope these are helpful changes.

Thank you! Extremely helpful, this is a huge speed bump especially on mobile.


Set isValid to false if Character.isJavaIdentifierPart(ch) is false

This looks like a mistake. The reason why it does is because the loop will only run if it is valid, and once isValid is true, |= means it will never be false, when it runs, meaning the check does nothing.
Having it be replaced by a simple = makes more sense

@ryanmkurtz Any update on this?

I've directed it to the appropriate developer.


register v0.2.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/52307
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" fea30a01e93c636239f9e99f00531ea144c655e1
git push origin v0.1.1

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

@JuliaRegistrator register

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/52307
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" a900545295a981a50a33c8aea8f5994b5bf1650a
git push origin v0.1.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/74639
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 74998358ea1c8a735590922bee650522f466780f
git push origin v0.1.2


Add documentation link checking

What problem does your feature request solve?

Sometimes link's can "rot", where they stop working for whatever reason.
Describe the solution you'd like

We should use the sphinx built in linkcheck builder to avoid this.
Describe alternatives you've considered

As this could occasionally fail due to a temporary outage we shouldn't have it on the release documentation build, only the PR checks.

Duplicate of #555 as my browser did something funny.


Prelude import

Depending on the discussion in https://github.com/gtk-rs/gio/pull/250, we might not want to merge this PR...
cc @sdroege @EPashkin

👍


refactor expander

Fixes #3523 https://github.com/microsoft/botbuilder-dotnet/issues/3523
Description
Refactor lg expander to support full functions of LG and fix several issues such as excape, double quotation. Also change the return type from string array to object array.
Specific Changes

[x] Support all kinds of LG functions

[x] Discard the 'builtin.' prefix

[x] Fix escape issues, including double quotation, escape character

[x] change return type from string array to object array

Testing
Corresponding test cases are added in lg.test.js

Pull Request Test Coverage Report for Build 119432

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 67.204%

Totals

Change from base Build 119067:
0.2%

Covered Lines:
10272

Relevant Lines:
14465

💛  - Coveralls


HiKari datasource in spring cloud (CF) failed to set PG related connection properties

               PoolConfig poolConfig = new PoolConfig(10, 40, 5000);
		Map<String, Object> connProperties = new HashMap<>();
		connProperties.put("connectionTimeout", 5000);
		connProperties.put("reWriteBatchedInserts", "true");
		ConnectionConfig connConfig = new ConnectionConfig(
				"reWriteBatchedInserts=true&options=-c%20statement_timeout=2000&ApplicationName=ABCD");
		DataSourceConfig dbConfig = new DataSourceConfig(poolConfig, connConfig, null, connProperties);
		DataSource dataSource = connectionFactory().dataSource(dbConfig);

I found that no matter we set it in connProperties or in the connConfig String, finally,  the datasource is still used the common properties settings in hikari datasource.  In the above code, only "connectionTimeout" is OK.
Is there any way to make the settings of: "reWriteBatchedInserts" work?

Keys passed in a connection properties map or a ConnectionConfig must map to fields of the class being created, which in your case appears to be HikariDataSource. There is no reWriteBatchedInserts method in HikariDataSource, so that setting will be ignored. The Postgres JDBC driver documentation says that reWriteBatchedInserts should be added to the JDBC URL connection string, and Spring Cloud Connectors does not support modifying the JDBC URL that is read from the service binding information.
Note that Spring Cloud Connectors is in maintenance mode, and support for this library will end soon. You should replace your usage of Connectors with Java CFEnv or another alternatve.

Thanks a lot for your information.  We'll update our code to reflect the change.


Feature suggestion: alternative to compile_flags.txt that is more comprehensive, but less manual typing hostile than compile_commands.json

Suggestion: a .clangd/compile_settings.conf (or similar) that allows 1. specifying default flags like in compile_flags.txt, 2. that additionally allows specifying some sort of regex file match rule -> flags override mechanism, 3. and again additionally a file exclusion list (maybe also inclusion one that defaults to .c/.cpp/.h/.hpp but is configurable?) for clangd.
Use case: I am trying to move into a setup where opening my project in different IDEs (so not just one I wrote a project file for) makes diagnostics work out of the box, to make it usable for e.g. people using vim+clangd or other non-IDE users with a better work flow. I've been using clangd for a while in VS Code and it's quite useful, but I do run into the one problem that I get tons of false positive in one single file that needs different compile flags or to be skipped altogether (since it's not a standalone object file like all the others). However,  compile_commands.json is basically unmaintainable when written manually* and I'm not using cmake, and compile_flags.txt is way too coarse. It would be nice to have some sort of .clangd/compile_settings.conf where I can actually specify flags and/or whether to ignore a file entirely (maybe it could allow various settings like an exclusion list?) such that it is automatically picked up when the project is opened.
*regarding compile_commands.json: the reason I want a file that doesn't need to be a generated one is two fold: 1. it breaks just opening the repo and having at least remotely useful diagnostics instead of just errors without running an extra command like cmake manually which is not the best first experience for new contributors (I know this is considered standard for C/C++ projects but why does everything need to be clumsy with C/C++ for new people jumping in? I think there is a point to be made for offering ways to make this easier out of the box) 2. this project is small enough that I am using a hand-crafted Makefile for now, so I'm not actually using anything that can generate a compile_commands.json anyway and it seems a bit silly to start doing so just to be able to exclude a single file.
I hope some of this reasoning makes at least a little bit of sense, and that I didn't file a duplicate. Would be very curious if this were to be possibly considered for inclusion one day.

I apologize, GitHub redirected me to an error page on submit and I didn't realize I actually had already filed it successfully. -> #646

I apologize, GitHub redirected me to an error page on submit and I didn't realize I actually had already filed it successfully. -> #646


Connection Refused when trying to connect to iOS simulator

Hey, I had ETTrace running really smoothly on macOS Sonoma and Xcode15.1. I just updated my computer to macOS Sequoia and Xcode 16 and now I am getting the following error:

ETTrace error: Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused"

Any ideas on how to resolve? Happy to contribute if this is a lightweight fix.
ps. I really appreciate y'all open sourcing this library. It's a game changer.

Hey @ugiacoman are you trying to connect to a simulator or physical device? I just tried it on sequoia with a simulator and didn't see this. Also, do you have the firewall enabled in System Settings under the network tab? If so could you try temporarily disabling that to see if it's related? There have been some reports of bugs in the firewall configuration of sequoia

Thanks @noahsmartin, I'm testing on simulator. I do have firewall enabled but the setting is configured by my company's profile. I don't have permissions to turn off the firewall 😅

@ugiacoman could you try on macOS 15.0.1? Apparently that fixed some of the firewall issues


Notifications 2.0

Beta notifications are written in the notifications branch. For better notifications however, we should consider the following:

Split notifications into categories.
Merge notifications by category and URL (e.g. all event joins in one place which link to all events in question).
Maybe an email digest of unread notifications after a while?
@ notifications in forums etc.
Email notifications???

Most of these (except merging as I'm not sure how to deal with stuff like time mismatch) are implemented in d65ebbfcea6738abbf61044736e2f79d9d033881.


Warning in Custom Node example

https://reactflow.dev/docs/guides/custom-nodes/
The last example shown in the documentation uses the same key (edge-1) for both edges hence throwing some warnings

thanks @kasunvimu8 💯


questions regarding link keyvault private dns zone to appgw vnet

In this page it mentions below information:
Note
If using Private Endpoints to access Key Vault, you must link the privatelink.vaultcore.azure.net private DNS zone, containing the corresponding record to the referenced Key Vault, to the virtual network containing Application Gateway. Custom DNS servers may continue to be used on the virtual network instead of the Azure DNS provided resolvers, however the private dns zone will need to remain linked to the virtual network as well.
In short we must link privatelink.vaultcore.azure.net private DNS zone to appgw vnet to get private endpoint access to keyvault. I have a question here: if appgw vnet using custom DNS servers, and custom DNS server can resolve keyvault private endpoint to private IP address. Do we still need to link privatelink.vaultcore.azure.net private DNS zone to appgw vnet?
In my lab, privatelink.vaultcore.azure.net private DNS zone is not linked to appgw vnet, custom DNS server used by appgw vnet can resolve keyvault private endpoint to private IP address. When disable public access on keyvault, appgw can't get cert. When public access enabled, appgw can get cert from keyvault.
From my test result, it looks to me privatelink.vaultcore.azure.net private DNS zone must link to appgw vnet even custom dns servers used by appgw vnet can resolve keyvault private endpoint to private IP address.
Please help to confirm above behavior. Thanks.

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

ID: 4c416d5e-5bfd-c641-e9bb-324dcb921acc
Version Independent ID: 8739a044-d471-c432-3ed1-503539408ae8
Content: TLS termination with Azure Key Vault certificates
Content Source: articles/application-gateway/key-vault-certs.md
Service: application-gateway
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@Herman5006
Thanks for your feedback! We will investigate and update as appropriate.

@Herman5006 , could you please clarify your question again?
Specifically, this statement - "From my test result, it looks to me privatelink.vaultcore.azure.net private DNS zone must link to appgw vnet even custom dns servers used by appgw vnet can resolve keyvault private endpoint to private IP address."
Are you saying that whatever is mentioned in the doc seems to be correct as you were able to replicate the same in your lab?
As mentioned in the doc,
Custom DNS servers may continue to be used on the virtual network instead of the Azure DNS provided resolvers, however the private dns zone will need to remain linked to the virtual network as well.
This holds true even if the custom DNS server can resolve keyvault private endpoint to private IP address.

@Herman5006 , could you please clarify your question again?
Specifically, this statement - "From my test result, it looks to me privatelink.vaultcore.azure.net private DNS zone must link to appgw vnet even custom dns servers used by appgw vnet can resolve keyvault private endpoint to private IP address."
Are you saying that whatever is mentioned in the doc seems to be correct as you were able to replicate the same in your lab?
As mentioned in the doc, Custom DNS servers may continue to be used on the virtual network instead of the Azure DNS provided resolvers, however the private dns zone will need to remain linked to the virtual network as well.
This holds true even if the custom DNS server can resolve keyvault private endpoint to private IP address.

Yes, you're correct. what mentioned in the doc seems to be correct. I just don't understand since custom DNS server used by appgw vnet can resolve keyvault private endpoint to private IP address, why must link keyvault private DNS zone to appgw VNET. Could you help to explain more about this? I remember earlier(maybe one year ago) if custom DNS server used by appgw  VNET can resolve keyvault private endpoint to private IP address, then no need to link keyvault private DNS zone to appgw VNET. Is there any behavior change make this is a MUST(link keyvault private DNS zone to appgw VNET)? Thanks.

@Herman5006 , I checked with Azure DNS Product Group team, and they mentioned the below:
If a customer defines a custom DNS server in a spoke VNET, even if a private DNS zone is linked to that VNET, the private DNS zones will not be queried because custom DNS overrides it. So, it shouldn’t be necessary, unless there’s something particular to Key Vault.
So, they recommended to check with the Key Vault team for this.
We have assigned this to the content owner/author for review and confirmation.
@greg-lindsay , could you please get the below statement confirmed and why this is needed?
If using Private Endpoints to access Key Vault, you must link the privatelink.vaultcore.azure.net private DNS zone, containing the corresponding record to the referenced Key Vault, to the virtual network containing Application Gateway. Custom DNS servers may continue to be used on the virtual network instead of the Azure DNS provided resolvers, however the private dns zone will need to remain linked to the virtual network as well.

Hi @GitaraniSharma-MSFT @greg-lindsay got update that keyvault private dns zone must link to appgw vnet. Cause is that some of the domains are configured to be resolved by Azure default DNS irrespective of any custom DNS setup. .azure.net which covers keyvault xxx.vault.azure.net is included in this exception list.
Could you please help to update same in this public docs to avoid confusion? Thanks.

@greg-lindsay , could we please update the documentation to add this information? Thanks!

Hi @greg-lindsay , any progress regarding update in public docs? Thanks.

Hi @GitaraniSharma-MSFT , looks no update from greg-lindsay, may I know any plan to update this in public docs? Thanks.

@greg-lindsay , could you please review this doc update request and provide an update?

You can continue to comment here and I will see the note. I apologize for the delay. There are several issues open at this time. I am tracking this one as higher priority.
Closing this request and moving to internal work item 91174
#please-close


Inspect and fix artifact result (missing/wrong dependencies)

It looks like the final result (in packages) is missing the actual dependency declaration. Since the removal of the UMD header and the latest addition of window.EventBus, this does not like it should.

Fixed in 5.0.0


"ERRORS: No installed scenery detcted WILL EXIT DUE TO ERRORS"

I just installed the AO v0.5.1, then I was just changing the directories (from C drive to D drive) but when I clicked save, it crashed. Now the app won't restart. It gives an error "ERRORS: No installed scenery detcted WILL EXIT DUE TO ERRORS". Tried downloading the latest v0.6.1, but for some reason the problem was carried over.

As far as I understand the python files, it can't find installed scenery in "Custom Scenery\z_autoortho\scenery"
in .autoortho (in your user directory) make sure
use gui config at startup
gui = True
show config setup at startup everytime
showconfig = True
You should be able to change directories and reinstall.
Doesn't fix the code, but hope it helps you along

As far as I understand the python files, it can't find installed scenery in "Custom Scenery\z_autoortho\scenery" in .autoortho (in your user directory) make sure
# use gui config at startup
gui = True
# show config setup at startup everytime
showconfig = True

You should be able to change directories and reinstall. Doesn't fix the code, but hope it helps you along

Thanks, that has fixed it. I just opened the .autoortho file with wordpad and changed the aforementioned lines.

Thank you.


React Native

Any thoughts on supporting React Native for this component?

Could do. I don't have a ton of experience with React native, so PRs are welcome ;)


Switch to micro from express for the server implementation

I thought micro was the zeit choice for http servers.
Why is this project using express?

My fault, for the personalized routes I decided to use express, it did not occur to me to use micro 😿

Okay thanks for the clarification 👍
I look forward to see how you migrate because that might be a good example for others who want to switch from express to micro 😄

@styfle @timothyis I'll take care of making the migraciona to micro ❤
Thank you for making this excellent question 🙏

Fixed 👍


Update mockito-scala, ... to 1.17.22

About this PR
📦 Updates

org.mockito:mockito-scala
org.mockito:mockito-scala-scalatest

from 1.17.7 to 1.17.22
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.mockito" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #1820.


[EMB-512][Collections] Allow users to start from wherever they want on edit page

Purpose
The main purpose of this PR is to allow users to start from any point on the edit page.
This PR also fixes the problem where Discard Changes for Collection Metadata section clears all metadata instead of reverting to the saved state.
Summary of Changes
Respectively,

savedSections in the collections-submission component denotes which section of the edit form has been "saved" (meaning the Continue or Save and Continue button for that section has been clicked). Therefore, for the edit view, we set it all sections, enabling users to be able to click any section to edit.

Also change the isPageDirty logic to look at hasDirtyAttributes of the collected-metadatum model.

Add initialCollectedMetadatumProperties to collection-metadata component to save initial properties so that we can revert back to the last saved state when clicking "Discard Changes".

QA Notes
This fixes the problem in EMB-499.
Ticket

https://openscience.atlassian.net/browse/EMB-512
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2472

1 of 10 (10.0%)  changed or added relevant lines in 4 files are covered.
14 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 70.071%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/collections/addon/guid/edit/controller.ts
1
2
50.0%

lib/collections/addon/guid/edit/route.ts
0
1
0.0%

lib/collections/addon/components/collection-metadata/component.ts
0
2
0.0%

lib/collections/addon/components/collections-submission/component.ts
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

lib/collections/addon/guid/edit/controller.ts
3
68.29%

lib/collections/addon/components/collections-submission/component.ts
4
45.05%

lib/collections/addon/components/collection-metadata/component.ts
7
59.18%

Totals

Change from base Build 2464:
-0.02%

Covered Lines:
5347

Relevant Lines:
6906

💛  - Coveralls


Test

Now tests writen using local Postgres, need to rewrite them using H2DB

Салам брат
23 сент. 2018 г. 12:42 пользователь "Abdrazak Almas" <
<EMAIL_ADDRESS>написал:

Now tests writen using local Postgres, need to rewrite them using H2DB
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/strogiyotec/lightbox-jdbc/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AjhhPbRqMo-rRDa-1dEQlhDM2tsuKYSYks5udy1hgaJpZM4W1lT9
.


Segmentation fault.

Receiving Segmentation fault on my Mac M1 & hangs there itself, until I don't kill the container
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
qemu: uncaught target signal 11 (Segmentation fault) - core dumped```

I would love to provide more information, please let me know.

Mac M1 is built on arm64 architecture. I suggest you to build sqlc using GOOS=darwin and GOARCH=arm64 flags. Resulted binary should work fine on your M1.


Prettify MD/YAML files

Resolved via prettier -w .

Codecov Report

Merging #42 (433d699) into main (6de4e06) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   66.50%   66.50%
=======================================
  Files          17       17
  Lines        1606     1606
=======================================
  Hits         1068     1068
  Misses        538      538

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


CodeFolding error

Highlighter use "Object Pascal.json", Copy "BCEditor.Editor.Base.pas" all content to BCEditor, CodeFolding error on line 2244.

I tried that with my editor and no problem:

Do you have the latest source and highlighters?

I use git source latest version, In Delphi10S, Win10 x64 Chinese OS.

I think this is ' and {} conflicts, I delete ' or add ' or replace {} as a single line comment, code folding is correct.

I found this because BCEditor.Options include [cfoFoldMultilineComments].

Fixed.


how to specify an option multiple times

So I need the ability to do the following:
mycli deploy -e FOO=BAR -e BAZ=FOOBAR
but I cant seem to figure out how to do this from the wiki. Any suggestions?

@jchauncey not sure if you're still interested but I've just proposed a patch to address something like this: #468


[dev.fuzz] cmd/go: add fuzz timeout flag

We may want to consider adding a -fuzztimeout flag, which acts similar to a -timeout flag, but for a run of a single input to the f.Fuzz function.
If -fuzztimeout=100ms, then we give each execution of the fuzz function 100 milliseconds to run, and consider it a crasher if that execution takes longer than 100ms to complete.
Note that libFuzzer does this with a -timeout flag.
We could also consider retrofitting the existing -timeout flag, but that might cause confusion. The description for timeout is "If a test binary runs longer than duration d, panic." If someone sets timeout while fuzzing, we don't want to panic when we hit that timeout (which we will if there is no crash).
Related to #44483.

Will https://golang.org/pkg/testing/#T.Deadline be supported?

This is done, in the form of the -fuzztime flag.
We should wire that into T.Deadline though as @AlekSi points out.

It would be nice to support this for 1.18, but it's not a release blocker. We'll see if we get to it.

#48157 is a proposal to add a flag and a T method for per-test timeouts. We'll wait for that to be resolved. If approved, we'll use the same flag and method.


Can you provide some output files？

Can you provide the output files of these two code segments, including VOC and COCO?
python tools/zero_shot_utils.py configs/faster_rcnn_r101_fpn_1x.py --classes seen --load_from ./work_dirs/coco2014/epoch_12.pth --save_dir ./data --data_split train
python tools/zero_shot_utils.py configs/faster_rcnn_r101_fpn_1x.py --classes unseen --load_from ./work_dirs/coco2014/epoch_12.pth --save_dir ./data --data_split test

Hi @aaaaxxc ,
As far as I remember, the extracted features are stored as numpy files. But I'm not currently at the university, so I don't have access to those output files. I can upload them by Monday. Meanwhile, can you tell me what's the issue you are facing in running zero_shot_utils.py?

Hello!
I saw that in another issue you implemented the code in a higher version of torch, but mmdet and mmcv are still giving the error "undefined symbol: _ZN6caffe26detail36_typeMetaDataInstance_preallocated_7E". This seems to be a problem with the CUDA version being too high (CUDA 11.1, which is the minimum version my graphics card can support). [https://github.com/yrcong/STTran/issues/51] I tried to solve this issue by upgrading the versions of mmdet (2.28.2) and mmcv (1.7.2), but mmdet 2.x is not compatible with the models and pre-trained models of mmdet 1.x.
Moreover, the machines that I can use which support lower versions of CUDA have smaller memory, and the memory is insufficient when running COCO code. Therefore, my machine cannot simultaneously meet the requirements of supporting a lower version of CUDA and having high memory.
At the same time, I am also unsure whether different features will affect the final results. In several generative codes I have run, the VOC results seem to differ slightly from those in the paper.

Thank you for your help. I resolved the issue after adding 128GB of memory.

------------------ Original ------------------
From: @.>;
Date:  Wed, May 29, 2024 10:05 PM
To: @.>;
Cc: @.>; @.>;
Subject:  Re: [sandipan211/ZSD-SC-Resolver] Can you provide some output files？ (Issue #21)

@aaaaxxc  Sorry for the delay. Due to some unforeseen circumstances, I reached my institute today. Here are the extracted train and test features for the PASCAL VOC dataset. Unfortunately, I do not have enough cloud storage for uploading the features of COCO dataset, since it is 35 GB in size.
See if this will be enough for you. You're welcome to suggest any alternate way of sending large files over the internet if you want the COCO features as well.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Good to know that!
Regards
Sandipan Sarma
Research Scholar,
Dept. of Computer Science and Engineering,
Indian Institute of Technology (IIT) Guwahati,
Assam, India.

From: aaaaxxc @.>
Sent: Friday, May 31, 2024 6:50 AM
To: sandipan211/ZSD-SC-Resolver @.>
Cc: SANDIPAN SARMA @.>; Comment @.>
Subject: Re: [sandipan211/ZSD-SC-Resolver] Can you provide some output files？ (Issue #21)
Thank you for your help. I resolved the issue after adding 128GB of memory.

------------------ Original ------------------
From: @.>;
Date:  Wed, May 29, 2024 10:05 PM
To: @.>;
Cc: @.>; @.>;
Subject:  Re: [sandipan211/ZSD-SC-Resolver] Can you provide some output files？ (Issue #21)

@aaaaxxc Sorry for the delay. Due to some unforeseen circumstances, I reached my institute today. Here are the extracted train and test features for the PASCAL VOC dataset. Unfortunately, I do not have enough cloud storage for uploading the features of COCO dataset, since it is 35 GB in size.
See if this will be enough for you. You're welcome to suggest any alternate way of sending large files over the internet if you want the COCO features as well.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/sandipan211/ZSD-SC-Resolver/issues/21#issuecomment-2141077519, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHFGDZBMTU5MWFZF4BRSHMLZE7F7RAVCNFSM6AAAAABIG6OOT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRGA3TONJRHE.
You are receiving this because you commented.Message ID: @.***>


Why hard code 24 in a Params class?

https://github.com/NCAR/VAPOR/blob/37f56579b042b104909f46dd0b93312a25a2a3f5/apps/vaporgui/SettingsParams.cpp#L423-L427

Update on 6/11/2018:
This behavior remains the same.

Not gonna get addressed.


Add density matrix class.

from torchquantum import density

dm = density.DensityMatrix(n_wires=1)
dm.h(wires=0)

The above seems to be breaking the code:
AttributeError: 'DensityMatrix' object has no attribute 'states'
Also, does general encoder work with DensityMatrix?


Bot based outpost

Would it be possible to make it skip belts and place provider chests between the miners to support a bot based mining outpost?

This is now supported in 0.1.7, click on the transport belt button while holding a chest. I'm going to leave this issue open for now until I find a better way to integrate it with the GUI.
Thanks for the suggestion, hope you're finding the mod useful.


Package request:  libportmidi

Hello,
I'd like to request that Portmidi (cross-platform C library for interfacing with MIDI hardware) be added to the MSYS2 repositories.  There is an optional bundled GUI application that has a Java dependency, IMHO that component could be omitted and just package the libportmidi dll and headers.
Thanks

I think it need to be added into MINGW-PACKAGES instead.

Oops, sorry, I'll close the 2 issues I just opened and re-open them in MINGW-PACKAGES.  Thanks.

A new issue had been opened here


avoid displaying coverage analysis when no coverage

Fixes: https://github.com/ossf/fuzz-introspector/issues/486
Signed-off-by: David Korczynski<EMAIL_ADDRESS>


"shouldCloseOnSelect" option is not working with datepicker when time picker enabled

Description
shouldCloseOnSelect option is not working with datepicker when time picker enabled.
Expected behavior
Datepicker should not close when shouldCloseOnSelect is set to false.
Actual behavior
Datepicker is closed once you select the time.
Steps to reproduce
I have created codesandbox below to reproduce the issue.
https://codesandbox.io/s/2w4611793j

Running into the same issue, anyone have any progress on this?

@jwrlee88 I am working on it.
I found that this.setOpen(false) is being called without checking shouldCloseOnSelect.
I added the verification, but I found another problem. After I click the time, the CSS (to show what time is currently selected) is not being applied.
When I have time I will check the problem with CSS and then make a PR.


Bot webhook is setup but bot is not responding. Webhook does not seem to be be reciving anything

Webex Bot version: webex-bot          0.4.0
Python version: Python 3.9.2
Operating System:linux (GCP defaul VM)

Description
Websocket is open. But the bot does not respond.

2023-09-04 14:04:23  [INFO]  [webex_bot.webex_bot.webex_bot.get_me_info]:90 Running as bot 'testbot1' with email<EMAIL_ADDRESS>2023-09-04 14:04:59  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:160 Opening websocket connection to wss://mercury-connection-partition1-a.wbx2.com/v1/apps/wx2/registrations/xxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxxxxx/messages
2023-09-04 14:04:59  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:163 WebSocket Opened.

Hi @akshaykadidal-
How are you initializing your bot? Have you set an "approved_*"  parameter on the constructor to allow yourself to talk to the bot. There's 3 approved parameters:

@param approved_users: List of email address who are allowed to chat to this bot.
@param approved_domains: List of domains which are allowed to chat to this bot.
@param approved_rooms: List of rooms whose members are allowed to chat to this bot.

To allow your specific user, you would do something like this:
bot = WebexBot(teams_bot_token=os.getenv("WEBEX_TEAMS_ACCESS_TOKEN"),
<EMAIL_ADDRESS># add your e-mail address here
               bot_name="My Teams Ops Bot",
               include_demo_commands=True)

<EMAIL_ADDRESS># add your e-mail address here
               bot_name="My Teams Ops Bot",
               include_demo_commands=True)

I have not filled in any of these optional parameters. I see that I get a warning.
[WARNING]  [webex_bot.webex_bot.webex_bot.approval_parameters_check]:117 Your bot is open to anyone on Webex Teams. Consider limiting this to specific users, domains or room members via the WebexBot(approved_domains=

In a 1:1 conversation with a bot, I see log messages like:
2023-09-04 17:39:59  [INFO]  [webex_bot.webex_bot.webex_bot.process_incoming_message]:198 Message from my.email.com: Webex Teams Message:
{
...json blob...
}
2023-09-04 17:39:59  [INFO]  [webex_bot.webex_bot.webex_bot.process_raw_command]:216 New user_command: a test message
2023-09-04 17:39:59  [INFO]  [webex_bot.webex_bot.webex_bot.process_raw_command]:217 is_card_callback_command: False
2023-09-04 17:39:59  [WARNING]  [webex_bot.webex_bot.webex_bot.process_raw_command]:236 Did not find command for a test message. Default to help card.

My "driver" script is really simple with a fresh checkout:
~/dev/webex_bot$ cat tester.py
import os

from webex_bot.commands.echo import EchoCommand
from webex_bot.webex_bot import WebexBot

# Create a Bot Object
bot = WebexBot(teams_bot_token=os.getenv("WEBEX_TEAMS_ACCESS_TOKEN"),
               bot_name="My Teams Ops Bot",
               include_demo_commands=True)

# Add new commands for the bot to listen out for.
bot.add_command(EchoCommand())

# Call `run` for the bot to wait for incoming messages.
bot.run()

No other events are recorded nothing in the logs to show that an event was recieved.

time stamps are diffrent because the VM is probably showing GMT.

I don't think so, but I don't want to give the false response. I'm in the campus network and I'm waiting the response from IT.

I worked with IT and they guided me to disable the virtual proxy in the cloud. However after that, I'm still having the same observation.
On the terminal, it only shows the following logs. No events displayed when webex client chats to the bot.
...
2023-11-15 10:18:06  [INFO]  [webex_bot.webex_bot.webex_bot.init]:49 Registering bot with Webex cloud
2023-11-15 10:18:06  [INFO]  [restsession.webexteamssdk.restsession.user_agent]:169 User-Agent: webexteamssdk/0+unknown {"implementation": {"name": "CPython", "version": "3.10.11"}, "system": {"name": "Windows", "release": "10"}, "cpu": "AMD64", "organization": {}}
2023-11-15 10:18:07  [INFO]  [webex_bot.webex_bot.webex_bot.get_me_info]:90 Running as bot 'CCReport' with email<EMAIL_ADDRESS>2023-11-15 10:18:07  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:160 Opening websocket connection to wss://mercury-connection-partition2-a.wbx2.com/v1/apps/wx2/registrations/a26872de-a8ce-44ab-b414-143081f04e57/messages
2023-11-15 10:18:07  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:163 WebSocket Opened.
The network connection looks all OK.
nc -zv <IP_ADDRESS> 443
Connection to <IP_ADDRESS> port 443 [tcp/https] succeeded!
Any suggestions?

Are you doing a 1:1 chat or in a room? If it's a room, you need to invite the bot and @tag it.
You can turn on debug logging and see if that reveals anything. You should see some PING/PONG messages.
logging.getLogger("webex_bot.websockets").setLevel(logging.DEBUG)
logging.getLogger("websockets").setLevel(logging.DEBUG)

I'm on 1:1 chat. Here is what I did:
1, Deleted the bot and recreatd<EMAIL_ADDRESS>on developer.webex.com. Just in case.
2, Updated the example.py with 3 new lines per your suggestion:
import logging
ogging.getLogger("webex_bot.websockets").setLevel(logging.DEBUG)
logging.getLogger("websockets").setLevel(logging.DEBUG)
3, Set the environment and run python example.py on my Windows machine:
2023-11-16 09:43:16  [INFO]  [webex_bot.webex_bot.webex_bot.init]:49 Registering bot with Webex cloud
2023-11-16 09:43:16  [INFO]  [restsession.webexteamssdk.restsession.user_agent]:169 User-Agent: webexteamssdk/0+unknown {"implementation": {"name": "CPython", "version": "3.10.11"}, "system": {"name": "Windows", "release": "10"}, "cpu": "AMD64", "organization": {}}
2023-11-16 09:43:17  [INFO]  [webex_bot.webex_bot.webex_bot.get_me_info]:90 Running as bot 'Report1116' with email<EMAIL_ADDRESS>2023-11-16 09:43:17  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:160 Opening websocket connection to wss://mercury-connection-partition1-a.wbx2.com/v1/apps/wx2/registrations/e207328b-c20c-4785-b413-c8511e66f872/messages
2023-11-16 09:43:17  [INFO]  [webex_websocket_client.webex_bot.websockets.webex_websocket_client._connect_and_listen]:163 WebSocket Opened.
4, on the searching header of my webex client, I filled in<EMAIL_ADDRESS>Type something there.
Unfortunately no response. On the terminal, nothing is displayed.
Is there a way to check if Webex cloud receives any info to the given bot and if webex cloud ever tried to send request to my Windows computer?

Sorry, I forgot the webex bot creates its own logging handler which kind of breaks the normal python logging config.
Try setting env var LOG_LEVEL=DEBUG before starting the bot. My commands didn't actually enable debug logging.

Is there a way to check if Webex cloud receives any info to the given bot and if webex cloud ever tried to send request to my Windows computer?

No, not that I'm aware of.

With the update, it does pop up a lot on the terminal. Enve ping/pong looks all good, I still don't see any response in webex client. No updates on logs either.
logs.txt

I don't have an answer. I agree the logs look ok and don't see an obvious problem. I talked with someone and the recommendation was to try the (supported) project at https://github.com/webex/webex-js-sdk/ to see if that works/fails.
If that also fails, then will have more leverage with webex support.
If it works, then we'd need more info to determine what the difference is. As it is now, I've never seen webex_bot not work in the few years I've been using it, so I can't duplicate this failure case.

I am having the same issue

So I tried running the code on replit, to see if the issue is something on my side, but it still doesn't work, any ideas?

Hi figure out, Cisco changed some configuration about device data, please register for the notification over the websocket in the device data:
DEVICE_DATA = {
"deviceName": "pywebsocket-client",
"deviceType": "DESKTOP",
"localizedModel": "python",
"model": "python",
"name": "python-spark-client",
"systemName": "python-spark-client",
"systemVersion": "0.1",
"features": {
"user": [
{
"key": "direct-message-notifications",
"val": "true",
"mutable": True,
"lastModified": "2019-07-03T09:18:54.806Z",
"type": "USER",
"deletedTime": 0
},
{
"key": "group-message-notifications",
"val": "true",
"mutable": True,
"lastModified": "2019-07-03T09:26:51.902Z",
"type": "USER",
"deletedTime": 0
},
{
"key": "mention-notifications",
"val": "true",
"mutable": True,
"lastModified": "2019-07-03T09:25:21.164Z",
"type": "USER",
"deletedTime": 0
},
{
"key": "web-color-theme",
"val": "true",
"mutable": True,
"lastModified": "2021-06-08T13:48:46.908Z",
"type": "USER",
"deletedTime": 0
}
]
}

}

Closing as duplicate of #48


Please update xdgurl

As the title says. Xdgurl 2.0 was rewritten and is now using Qt. Please update it. Thanks in advance

Added to https://github.com/probonopd/AppImages/issues/29 - I think it makes most sense to enable the upstream developer to build official AppImages rather than me trying to repackage existing binaries.

https://github.com/xdgurl/xdgurl/pull/25


refactor: Changed the eventbridge rule to use the scan interval as tr…

…igger.
Currently the sidekick container runs every hour. Even if you set the scan interval to 24 hours. This change uses the value from the scan interval for the scheduled trigger in EventBridge.

Summary

When the config of the scan interval is set to 24 hours the sidekick container produces a lot of unnecessary noise in Cloudwatch. Why not set the trigger in hours to the same interval as the scan interval?
How did you test this change?

Issue

Hi @bebold-jhr, thanks for deep diving into this and finding this nuance.
Having this run every 1hr is important because there are features to scan "short lived" instances that only exist for 1hr. This also allows for splaying/sharding parts of the scan, so if you want to scan everything every 24hrs you can scan 1/24th each hour. This has a positive impact for very large infrastructures where the API limits for snapshotting and accessing snapshot data is limited.
I think the follow up here is to leave the 1hr interval, but add a comment explaining the discrepancy between the interval value and this value.

Hi @theopolis,
thank your for clarifying.


The python kernel does not appear to be a conda environment

I have installed Spyder 5.0.3 on Windows 10. I am trying to create a separate virtual environment with the following command
          "conda create -n spyder-env spyder=4"

However, i am getting the following error
"ValueError: The python kernel does not appear to be a conda environment.  Please use %pip install instead."

Hey @shailenderjain, that command is not meant to be run inside our consoles. If you want to use to other modules that don't come with our installer, you need to do the following:

Install Miniconda.

Create a conda environment after that with the packages you want to use and spyder-kernels. In your case you need to run these commands in a system terminal (i.e. cmd.exe):
 conda activate base
 conda create -n myenv spyder-kernels <foo>

Connect Spyder to that environment by following these instructions.

Please do that and let us know if it works for you.

Closing due to lack of response.


[24.1] Fix account profiling incumbency

Current implementation is racy for two reasons.
Firstly, the following scenario is possible:

Peer is a leader and profiles metrics
Leader is switched, profiling invoker is destroyed 3) Dynamic config changes, StartAccountsProfiling is called and new (epoch) invoker in created 4) Peer becomes leader again, invoker is not recreated while it is still bound to the finished epoch

Secondly, invoker is always stopped when some incumbency finishes, while it is possible that only a part of incumbencies should be finished (i.e. during the change of number of alive followers).
This PR fixes these problems and also does some code cleanup.

Co-authored-by: Grigory Reznikov<EMAIL_ADDRESS>7dca0641dbbcf55beb2bdf44bc91678f49af33b5
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/701
--

Changelog entry
Type: fix
Component: master

Fixed issues with accounts profiling disabling itself during maintenance/master leader switches.

Shipped!


vhdl files not recognized

in package.json, please change all occurrences of:
resourceExtname == vhdl
into
resourceExtname == .vhdl
Tnx,
Edwin

Ah thx. I might have been a bit inattentive there.
Should be fixed now.


Workaround for IndexError: list index out of range

Fixes #10. In my case, I believe the figcaption belonged to an embedded tweet, which caused the script to bail out (as there was no card in the stack yet). This makes sure that the script doesn't fail in these cases.

Wondering if this PR can be merged? It solved things for me as well...

Thanks! It only took me the better part of a year to merge it :)

Better late than never? :-)


Small textual edits

Just getting into Truffle and about to refactor an existing app using the framework. The readme is fantastic, just thought I'd submit a few copy edits while I was reading through.

Finally did something about this. Thanks @jdmaresco!


Client_ID Not set Error

When trying to run on the web, there is a problem with OAuth

HINT: It will be in the web folder, you have to find that metadata link and set the client ID. Client ID is in GoogleService-info.plist file

Pull request merged. commit - "Cliend_ID_Update"


[ServiceBus] prepare for 2022 Aug release

update date in CHANGELOG

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


cob_driver: 0.7.17-2 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_driver to 0.7.17-2:

upstream repository: https://github.com/4am-robotics/cob_driver.git
release repository: https://github.com/4am-robotics/cob_driver-release.git
distro file: noetic/distribution.yaml
bloom version: 0.12.0
previous version for package: 0.7.16-2

cob_base_drive_chain

No changes

cob_bms_driver

No changes

cob_canopen_motor

No changes

cob_driver

No changes

cob_elmo_homing

No changes

cob_generic_can

No changes

cob_light

No changes

cob_mimic

No changes

cob_phidget_em_state

No changes

cob_phidget_power_state

No changes

cob_phidgets

No changes

cob_relayboard

No changes

cob_scan_unifier

No changes

cob_sick_lms1xx

No changes

cob_sick_s300

No changes

cob_sound

No changes

cob_undercarriage_ctrl

No changes

cob_utilities

No changes

cob_voltage_control

No changes

laser_scan_densifier

No changes

fixup for https://github.com/ros/rosdistro/pull/40673 - see discussion in https://github.com/ros/rosdistro/pull/40670
i.e. release again from previous source/release branch to fixup tags and cob_driver-release repo

the bloom-releases got a bit messy - see https://github.com/ros/rosdistro/pull/40670 for the discussion

https://github.com/ros/rosdistro/pull/40670
https://github.com/ros/rosdistro/pull/40671
https://github.com/ros/rosdistro/pull/40672
https://github.com/ros/rosdistro/pull/40673

thus, they are now superseded by a final, eol release from the "old" dev branches - reverting the (partial) release from the "new" dev branches:

https://github.com/ros/rosdistro/pull/41016
https://github.com/ros/rosdistro/pull/41017
https://github.com/ros/rosdistro/pull/41018
https://github.com/ros/rosdistro/pull/41019

I will create one more follow-up PR once the PRs above are merged which:

marks all cob_* entries as end-of-life
fixes the discrepancy between doc branch and source branch


fixUniversalNumber: Number merge

High Level Overview of Change
Use Number for IOUAmount and STAmount arithmetic

* Guarded by amendment fixUniversalNumber
* Produces slightly better accuracy in some computations.

Context of Change
There are two many decimal floating point classes in rippled, and AMM needed a third.  This merges common code.  A side effect is that some transaction arithmetic becomes more accurate in the final digit or two.  Therefore this change is guarded by an amendment.
The first many commits introduce Number.  Only the final commit merges the common code with IOUAmount and STAmount, and introduces the amendment.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactor (non-breaking change that only restructures code)
[ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

Test Plan
Some tests are updated with the slightly more accurate results.

这个是关于ripple还是radar?

@zhangdongwei123, this repository is for the XRP Ledger and has nothing to do with radar.

雷达还开吗？

@zhangdongwei123, you are asking at the wrong site.  This site has no connection with radar.  We don't know whether radar is working or not.  Please find somewhere else to ask.

Looking into it now, thanks.

This new commit fixes the failures you observed @seelabs.  For reasons that are not clear to me, the Taker test ran with the amendment on in non-unity build, and with the amendment off in unity build.  The patch forces the amendment on in the Taker test for both non-unity and unity builds.

Rebased to 1.9.2-rc1.

Rebased to 1.9.2.

For posterity, some notes re: 6c8d3abfb1d27dab7a03556ea943c5084e892311

I've tested on two versions of macOS:  10.14 and 13.2.
The patch replaces the use of __udivti3 within the Number multiplication operator.
I tested for correctness on over 55 quintillion values of uint128_t, which is a tiny fraction of the total values that this type can hold.  I concentrated the tests at and near 0, around the transition between the upper 64 bits going from zero to non-zero, and at and near the maximum value of uint128_t.  These tests were not included with the patch because they would be far too time consuming for --unittest.
I also tested for performance on both macOS 10.14 and 13.2.  On 10.14 the patch is a little over 30x faster than __udivti3.  But on 13.2 it is the exact same speed.  Not because the patch is slower, but because __udivti3 is that much faster on 13.2 (for the divide by a constant 10 case).
I do not know if the linux gcc tools have implemented such an optimization or not.  So this may or may not improve the performance of Number::operator*= on linux.  Although it will definitely eliminate the call to __udivti3.

Internal testing:

[We are] very pleased with the results. For one of the consensus phase I picked, it used to take 3051ms to apply 458 transactions before the fix but now it only took 1063ms to apply 475 transactions to the ledger.

We observed both have a ~ 3.6 better performance than previous build. ... Submit response time also reduced significantly as well.

Just needs conflicts to be resolved @HowardHinnant . There is no need to rebase (although that is fine if that's what you prefer) - merge commits are OK since they will be squashed anyway.

Squashed and rebased to Develop (1.10.0-rc1).  Builds and passes --unittest.


hercynylcysteine etc. - user feedback on GO:0044875 and similar

Hello GO folks,
We've had a query from a PomBase user, Tomas Pluskal, about MF terms that GO added for annotations from one of his recent papers. It's probably best if I just quote directly:
"

egt1 has a GO Molecular Function annotation as "gamma-glutamyl hercynylcysteine S-oxide synthase (GO:0044875), but this should be "hercynylcysteine S-oxide synthase. The pathway involves gamma-glutamyl cysteine in bacteria, but in eukaryotes (including pombe), it involves cysteine directly. I tried to explain this in the comment that I submitted with the curation, but perhaps I was not clear enough. Probably, we need a new GO term for "hercynylcysteine S-oxide synthase. Although, there is already a term GO:1903253 ("hercynylcysteine sulfoxide biosynthetic process), but that one describes Process, not Function (see http://www.ebi.ac.uk/QuickGO/GSearch?q=hercynylcysteine).

This is unrelated to Pombase, but the Definition of the GO:0044875 term, as shown at
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0044875, is wrong. It says the reaction is between cysteine and histidine, while the title ("gamma-glutamyl hercynylcysteine S-oxide synthase) describes a reaction between cysteine and gamma-glutamyl hercynine.
"

It sounds like a def edit and a new term are required.
The previous ticket on MF terms is [ontology-requests:#10978], and I've put some previous feedback from Tomas on corresponding BP terms in [ontology-requests:#10980], which is open. I'm sure Tomas would be willing to discuss these terms with you directly if you need any assistance (I don't know much about this area myself; I'm just the messenger!).
Thanks,
m
Reported by: mah11
Original Ticket: geneontology/ontology-requests/11486

@mah11  is this resolved for us?
David says
I think this might be done if you can give me some taxon restrictions.


IE8 'Element' is undefined using zTreeObj.selectNode

LINE : 1380 at jquery.ztree.core.js
                // code src: http://jsfiddle.net/08u6cxwj/
                if (!Element.prototype.scrollIntoViewIfNeeded) {

using IE8
case 1. this is ok when Silent mode is true. but cant scroll into.
zTreeObj.selectNode(node, false, true)
case 2. this is fail. IE8 does not support "Element"
zTreeObj.selectNode(node, false, false)

Please use  the last version files of zTree.  I try it in IE8, is ok.
IE8 support the 'Element' base. please see: https://developer.mozilla.org/en-US/docs/Web/API/Element


[blocked] Update java

This is blocked until we update the rootfs in all the clusters.

The new rootfs is deployed to all clusters. This can be merged.


Expose stft arguments to MelSpectorgram

In #892, arguments for stft have been added to torchaudio.transform.Spectrogram constructor. We can further extend it to MelSpectrogram, which simply reuses torchaudio.transform.Spectrogram.
Steps

Update the MelSpectrogram.__init__

Add the arguments [src], pass them to Spectrogram.__init__
Update the docstring [src]

Add a smoke test that confirms that the MelSpectrogram transform with the combinations of these new parameters do not crush.

I was trying this task and did the step1, but wasn't familiar about how smoke test should be written.
do I add some additional checks in test_melspectrogram_load_save()? or
should I do something similar to the class SmokeTest() as in https://github.com/pytorch/audio/blob/3250d3df168c956389bd16956aa458ce111570d0/test/torchaudio_unittest/sox_io_backend/smoke_test.py?

I was trying this task and did the step1, but wasn't familiar about how smoke test should be written.
do I add some additional checks in test_melspectrogram_load_save()? or
should I do something similar to the class SmokeTest() as in https://github.com/pytorch/audio/blob/3250d3df168c956389bd16956aa458ce111570d0/test/torchaudio_unittest/sox_io_backend/smoke_test.py?

I can work on this. but I am not familiar with how smoke test should be written, do you add test inside the test_transform or do  I need to do a SmokeTest class as in https://github.com/pytorch/audio/blob/3250d3df168c956389bd16956aa458ce111570d0/test/torchaudio_unittest/sox_io_backend/smoke_test.py?

I can work on this. but I am not familiar with how smoke test should be written, do you add test inside the test_transform or do  I need to do a SmokeTest class as in https://github.com/pytorch/audio/blob/3250d3df168c956389bd16956aa458ce111570d0/test/torchaudio_unittest/sox_io_backend/smoke_test.py?

Hi @jieruan02
You can add classes MelSpectrogramTest and SpectrogramTest in transforms_test.py and add method like smoke_test in each of them.

Hi @jieruan02
You can add classes MelSpectrogramTest and SpectrogramTest in transforms_test.py and add method like smoke_test in each of them.

Hi @mthrok, thank you for the hint! Also is there any local test we should run before making a PR instead of letting the ci do all the checks after submission?

Hi @mthrok, thank you for the hint! Also is there any local test we should run before making a PR instead of letting the ci do all the checks after submission?

There were some minor issues and I figured them out. now it should be correct, let me know what you think~ Thank you!

There were some minor issues and I figured them out. now it should be correct, let me know what you think~ Thank you!


REFPLTB-3165 : Installing bundle using UspPa is not working in dac

Reason for change: Addressing the issue of Device.SoftwareModules.ExecutionUnit. not created by removing containerName code , which is creating sub directories
Test procedure : Device.SoftwareModules.ExecutionUnit. should populated when installing the bundle, more information is available in comments section
Risks : None

Need test results for both 32 bit and 64 bit
1.UsPPa cli install/uninstall
2.UsPPa cli execution active/idle
3.both .tar and .tar.gz

okay Chandra,
will test share the results in respective ticket