[openimageio:x64-linux] build failure

Host Environment

OS: Kali Linux on WSL2
Compiler: GNU 10.2.1

To Reproduce
Steps to reproduce the behavior:
sudo ./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,pybind11,tools]
Failure logs
config-x64-linux-dbg-out.log
config-x64-linux-dbg-err.log
Shell Output
-- Using source at /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean         -- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):
                        Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean -DUSE_LIBRAW=ON -DUSE_OCIO=ON -DUSE_FFMPEG=ON -DUSE_FIELD3D=OFF -DUSE_FREETYPE=ON -DUSE_GIF=ON -DUSE_OPENCV=ON -DUSE_OPENJPEG=ON -DUSE_WEBP=ON -DUSE_PYTHON=ON -DOIIO_BUILD_TOOLS=ON -DOIIO_BUILD_TESTS=OFF -DHIDE_SYMBOLS=ON -DUSE_DCMTK=OFF -DUSE_NUKE=OFF -DUSE_QT=OFF -DUSE_PTEX=OFF -DLINKSTATIC=ON -DBUILD_MISSING_PYBIND11=OFF -DBUILD_MISSING_DEPS=OFF -DVERBOSE=ON -DCMAKE_MAKE_PROGRAM=/mnt/c/kali/vcpkg/downloads/tools/ninja-1.10.1-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/mnt/c/kali/vcpkg -D_VCPKG_INSTALLED_DIR=/mnt/c/kali/vcpkg/installed -DVCPKG_MANIFEST_INSTALL=OFF -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/mnt/c/kali/vcpkg/packages/openimageio_x64-linux/debug
                       Working Directory: /mnt/c/kali/vcpkg/buildtrees/openimageio/x64-linux-dbg
                        Error code: 1
                        See logs for more information:
                            /mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-out.log
                           /mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
    scripts/cmake/vcpkg_configure_cmake.cmake:328 (vcpkg_execute_required_process)
    ports/openimageio/portfile.cmake:50 (vcpkg_configure_cmake)
    scripts/ports.cmake:136 (include)

Error: Building package openimageio:x64-linux 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: openimageio:x64-linux
    Vcpkg version: 2020.11.12-unknownhash

Additionally, attach any relevant sections from the log files above.

Speculation
it seems like it's complaining about boost?
CMake Warning at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1204 (message): New Boost version may have incorrect or missing dependencies and imported targets
Call Stack (most recent call first):
/mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1326 (_Boost_COMPONENT_DEPENDENCIES)                                            /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1935 (_Boost_MISSING_DEPENDENCIES)                                              /mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake:598 (_find_package)                              src/cmake/externalpackages.cmake:90 (find_package)                                                  src/cmake/externalpackages.cmake:164 (checked_find_package)                                         CMakeLists.txt:117 (include)

or the naming of certain packages?
The package name passed to `find_package_handle_standard_args` (JPEG) does                          not match the name of the calling package (JPEGTurbo).

Any help would be greatly appreciated. Happy New Year.

Additional information:
in the original config-x64-linux-dbg-err.log file at the end it shows:
 CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):   Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
even though in config-x64-linux-dbg-out.log it shows:
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.18", minimum required is "2.7")
so i figured i would try uninstalling vcpkg, reinstalling, and retrying the openimageio install command excluding pybind11.
This still failed. Here are the details for my second attempt:
Log File
install-x64-linux-dbg-out.log
Steps to reproduce
./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,tools]
Shell Output
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:145 (message):
Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j9
Working Directory: /mnt/c/kali/vcpkg/buildtrees/openimageio/x64-linux-dbg
See logs for more information:
/mnt/c/kali/vcpkg/buildtrees/openimageio/install-x64-linux-dbg-out.log                                                                                Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:96 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:27 (vcpkg_build_cmake)
ports/openimageio/portfile.cmake:66 (vcpkg_install_cmake)
scripts/ports.cmake:136 (include)                                                                                Error: Building package openimageio:x64-linux 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: openimageio:x64-linux
Vcpkg version: 2020.11.12-unknownhash                                                                                Additionally, attach any relevant sections from the log files above.

The log file seems to have a number of undefined reference complaints.

Additional information:
in the original config-x64-linux-dbg-err.log file at the end it shows:
 CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):   Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
even though in config-x64-linux-dbg-out.log it shows:
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.18", minimum required is "2.7")
so i figured i would try uninstalling vcpkg, reinstalling, and retrying the openimageio install command excluding pybind11.
This still failed. Here are the details for my second attempt:
Log File
install-x64-linux-dbg-out.log
Steps to reproduce
./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,tools]
Shell Output
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:145 (message):
Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j9
Working Directory: /mnt/c/kali/vcpkg/buildtrees/openimageio/x64-linux-dbg
See logs for more information:
/mnt/c/kali/vcpkg/buildtrees/openimageio/install-x64-linux-dbg-out.log                                                                                Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:96 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:27 (vcpkg_build_cmake)
ports/openimageio/portfile.cmake:66 (vcpkg_install_cmake)
scripts/ports.cmake:136 (include)                                                                                Error: Building package openimageio:x64-linux 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: openimageio:x64-linux
Vcpkg version: 2020.11.12-unknownhash                                                                                Additionally, attach any relevant sections from the log files above.

The log file seems to have a number of undefined reference complaints.

CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
  (Required is at least version "2.7")

This shouldn't happend. the oiio should use vcpkg internal python instead of system.

CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
  (Required is at least version "2.7")

This shouldn't happend. the oiio should use vcpkg internal python instead of system.

Can you please update system inside python or remove it then retry?
Thanks.

Can you please update system inside python or remove it then retry?
Thanks.

Sorry, I'm not quite sure what you mean by "update system inside python", may I please have more details for those instructions?
as a note I don't currently have anything modifying PYTHONPATH or PATH outside the defaults for my .bashrc
Thank you for looking into this,

Sorry, I'm not quite sure what you mean by "update system inside python", may I please have more details for those instructions?
as a note I don't currently have anything modifying PYTHONPATH or PATH outside the defaults for my .bashrc
Thank you for looking into this,

@thunduaga Sorry for the confusion
-- Found PythonInterp: /usr/bin/python (found version "2.7.17")

I've confirmed that the python found in oiio is in the system.
So there are two solutions temporary:

Upgrade python in your system
Uninstall python in your system

@thunduaga Sorry for the confusion
-- Found PythonInterp: /usr/bin/python (found version "2.7.17")

I've confirmed that the python found in oiio is in the system.
So there are two solutions temporary:

Upgrade python in your system
Uninstall python in your system

This issue should be solved after the python usage issue is completely solved.
Related: #15404.

This issue should be solved after the python usage issue is completely solved.
Related: #15404.

As a note, I have both python 3.8 and python 2.7 installed on my system.
I tried renaming both python executables in /usr/bin such that vcpkg wouldn't see them.
$sudo mv /usr/bin/python /usr/bin/python_old
$sudo mv /usr/bin/python2.7 /usr/bin/python2.7_old
then re-ran my original vcpkg command:
$sudo ./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,pybind11,tools]
it still failed complaining about python in config-x64-linux-dbg-err.log:
CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message): Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE) (Required is at least version "2.7") Call Stack (most recent call first): /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE) /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPythonInterp.cmake:169 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake:634 (_find_package)     src/cmake/externalpackages.cmake:90 (find_package) src/cmake/pythonutils.cmake:27 (checked_find_package) src/python/CMakeLists.txt:6 (find_python)
Logs
config-x64-linux-dbg-out.log
config-x64-linux-dbg-err.log
Shell Output
`Computing installation plan...                                                                      The following packages will be built and installed:                                                     openimageio[core,ffmpeg,freetype,gif,libraw,opencolorio,opencv,openjpeg,pybind11,tools,webp]:x64-linux -> <IP_ADDRESS>#4                                                                                Detecting compiler hash for triplet x64-linux...                                                    Could not locate cached archive: /root/.cache/vcpkg/archives/ec/ec6c8b99b6c18228190535a0a71887e7e0d710ae.zip                                                                                Starting package 1/1: openimageio:x64-linux                                                         Building package openimageio[core,ffmpeg,freetype,gif,libraw,opencolorio,opencv,openjpeg,pybind11,tools,webp]:x64-linux...                                                                              -- Using cached /mnt/c/kali/vcpkg/downloads/OpenImageIO-oiio-e028a5264bd229e128b37a4362f7eb9c73ea82cc.tar.gz                                                                                -- Cleaning sources at /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean. Use --editable to skip cleaning for the packages you specify.                                          -- Extracting source /mnt/c/kali/vcpkg/downloads/OpenImageIO-oiio-e028a5264bd229e128b37a4362f7eb9c73ea82cc.tar.gz                                                                                -- Applying patch fix-dependency.patch                                                              -- Applying patch fix_static_build.patch                                                            -- Applying patch fix-tools-path.patch                                                              -- Applying patch fix-config-cmake.patch                                                            -- Applying patch fix-dependfmt.patch                                                               -- Applying patch fix-libheif.patch                                                                 -- Using source at /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean         -- Configuring x64-linux-dbg                                                                        CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):                        Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean -DUSE_LIBRAW=ON -DUSE_OCIO=ON -DUSE_FFMPEG=ON -DUSE_FIELD3D=OFF -DUSE_FREETYPE=ON -DUSE_GIF=ON -DUSE_OPENCV=ON -DUSE_OPENJPEG=ON -DUSE_WEBP=ON -DUSE_PYTHON=ON -DOIIO_BUILD_TOOLS=ON -DOIIO_BUILD_TESTS=OFF -DHIDE_SYMBOLS=ON -DUSE_DCMTK=OFF -DUSE_NUKE=OFF -DUSE_QT=OFF -DUSE_PTEX=OFF -DLINKSTATIC=ON -DBUILD_MISSING_PYBIND11=OFF -DBUILD_MISSING_DEPS=OFF -DVERBOSE=ON -DCMAKE_MAKE_PROGRAM=/mnt/c/kali/vcpkg/downloads/tools/ninja-1.10.1-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=v141 -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/mnt/c/kali/vcpkg -D_VCPKG_INSTALLED_DIR=/mnt/c/kali/vcpkg/installed -DVCPKG_MANIFEST_INSTALL=OFF -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/mnt/c/kali/vcpkg/packages/openimageio_x64-linux/debug                            Working Directory: /mnt/c/kali/vcpkg/buildtrees/openimageio/x64-linux-dbg
Error code: 1
See logs for more information:
/mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-out.log
/mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:328 (vcpkg_execute_required_process)
ports/openimageio/portfile.cmake:50 (vcpkg_configure_cmake)
scripts/ports.cmake:136 (include)
Error: Building package openimageio:x64-linux 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: openimageio:x64-linux
Vcpkg version: 2020.11.12-unknownhash
Additionally, attach any relevant sections from the log files above.`

As a note, I have both python 3.8 and python 2.7 installed on my system.
I tried renaming both python executables in /usr/bin such that vcpkg wouldn't see them.
$sudo mv /usr/bin/python /usr/bin/python_old
$sudo mv /usr/bin/python2.7 /usr/bin/python2.7_old
then re-ran my original vcpkg command:
$sudo ./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,pybind11,tools]
it still failed complaining about python in config-x64-linux-dbg-err.log:
CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message): Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE) (Required is at least version "2.7") Call Stack (most recent call first): /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE) /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPythonInterp.cmake:169 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake:634 (_find_package)     src/cmake/externalpackages.cmake:90 (find_package) src/cmake/pythonutils.cmake:27 (checked_find_package) src/python/CMakeLists.txt:6 (find_python)
Logs
config-x64-linux-dbg-out.log
config-x64-linux-dbg-err.log
Shell Output
`Computing installation plan...                                                                      The following packages will be built and installed:                                                     openimageio[core,ffmpeg,freetype,gif,libraw,opencolorio,opencv,openjpeg,pybind11,tools,webp]:x64-linux -> <IP_ADDRESS>#4                                                                                Detecting compiler hash for triplet x64-linux...                                                    Could not locate cached archive: /root/.cache/vcpkg/archives/ec/ec6c8b99b6c18228190535a0a71887e7e0d710ae.zip                                                                                Starting package 1/1: openimageio:x64-linux                                                         Building package openimageio[core,ffmpeg,freetype,gif,libraw,opencolorio,opencv,openjpeg,pybind11,tools,webp]:x64-linux...                                                                              -- Using cached /mnt/c/kali/vcpkg/downloads/OpenImageIO-oiio-e028a5264bd229e128b37a4362f7eb9c73ea82cc.tar.gz                                                                                -- Cleaning sources at /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean. Use --editable to skip cleaning for the packages you specify.                                          -- Extracting source /mnt/c/kali/vcpkg/downloads/OpenImageIO-oiio-e028a5264bd229e128b37a4362f7eb9c73ea82cc.tar.gz                                                                                -- Applying patch fix-dependency.patch                                                              -- Applying patch fix_static_build.patch                                                            -- Applying patch fix-tools-path.patch                                                              -- Applying patch fix-config-cmake.patch                                                            -- Applying patch fix-dependfmt.patch                                                               -- Applying patch fix-libheif.patch                                                                 -- Using source at /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean         -- Configuring x64-linux-dbg                                                                        CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):                        Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake /mnt/c/kali/vcpkg/buildtrees/openimageio/src/9c73ea82cc-c334986945.clean -DUSE_LIBRAW=ON -DUSE_OCIO=ON -DUSE_FFMPEG=ON -DUSE_FIELD3D=OFF -DUSE_FREETYPE=ON -DUSE_GIF=ON -DUSE_OPENCV=ON -DUSE_OPENJPEG=ON -DUSE_WEBP=ON -DUSE_PYTHON=ON -DOIIO_BUILD_TOOLS=ON -DOIIO_BUILD_TESTS=OFF -DHIDE_SYMBOLS=ON -DUSE_DCMTK=OFF -DUSE_NUKE=OFF -DUSE_QT=OFF -DUSE_PTEX=OFF -DLINKSTATIC=ON -DBUILD_MISSING_PYBIND11=OFF -DBUILD_MISSING_DEPS=OFF -DVERBOSE=ON -DCMAKE_MAKE_PROGRAM=/mnt/c/kali/vcpkg/downloads/tools/ninja-1.10.1-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=v141 -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/mnt/c/kali/vcpkg -D_VCPKG_INSTALLED_DIR=/mnt/c/kali/vcpkg/installed -DVCPKG_MANIFEST_INSTALL=OFF -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/mnt/c/kali/vcpkg/packages/openimageio_x64-linux/debug                            Working Directory: /mnt/c/kali/vcpkg/buildtrees/openimageio/x64-linux-dbg
Error code: 1
See logs for more information:
/mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-out.log
/mnt/c/kali/vcpkg/buildtrees/openimageio/config-x64-linux-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:328 (vcpkg_execute_required_process)
ports/openimageio/portfile.cmake:50 (vcpkg_configure_cmake)
scripts/ports.cmake:136 (include)
Error: Building package openimageio:x64-linux 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: openimageio:x64-linux
Vcpkg version: 2020.11.12-unknownhash
Additionally, attach any relevant sections from the log files above.`

After updating to the newest version of vcpkg (reinstalled) all of the warnings are gone, but this one error still keeps me up at night. Seems like the complaint is in building the pybind11 portion. Note that the system python is currently 3.9.1
Also, quick thank you to you guys for wrangling these issues, I looked over the other related tickets, much appreciated.
Command
sudo ./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,pybind11,tools]
../pybind11/x64-linux-dbg/CMakeFiles/CMakeOutput.log
CMakeOutput.log
config-x64-linux-dbg-out.log
$cat /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-out.log
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- pybind11 v2.6.0
-- CMake 3.19.2
-- Configuring incomplete, errors occurred!
See also "/mnt/c/kali/vcpkg/buildtrees/pybind11/x64-linux-dbg/CMakeFiles/CMakeOutput.log".

config-x64-linux-dbg-err.log
$cat /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-err.log
CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find Python (missing: Python_INCLUDE_DIRS Python_LIBRARIES
  Development Development.Module Development.Embed) (found version "2.7.18")
Call Stack (most recent call first):
  /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE)
  /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPython.cmake:470 (find_package_handle_standard_args)
  /mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake:634 (_find_package)
  tools/pybind11NewTools.cmake:33 (find_package)
  tools/pybind11Common.cmake:190 (include)
  CMakeLists.txt:162 (include)

Shell output (trimmed)
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):
Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake /mnt/c/kali/vcpkg/buildtrees/pybind11/src/20d59fb844-6f1ff890dc.clean -DPYBIND11_TEST=OFF -DPYBIND11_FINDPYTHON=ON -DPython3_EXECUTABLE=/usr/bin/python3 -DCMAKE_MAKE_PROGRAM=/mnt/c/kali/vcpkg/downloads/tools/ninja-1.10.1-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/mnt/c/kali/vcpkg -D_VCPKG_INSTALLED_DIR=/mnt/c/kali/vcpkg/installed -DVCPKG_MANIFEST_INSTALL=OFF -DPYTHON_IS_DEBUG=ON -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/mnt/c/kali/vcpkg/packages/pybind11_x64-linux/debug
    Working Directory: /mnt/c/kali/vcpkg/buildtrees/pybind11/x64-linux-dbg
    Error code: 1
    See logs for more information:
      /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-out.log
      /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:328 (vcpkg_execute_required_process)
  ports/pybind11/portfile.cmake:11 (vcpkg_configure_cmake)
  scripts/ports.cmake:136 (include)

Error: Building package pybind11:x64-linux 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: pybind11:x64-linux
  Vcpkg version: 2020.11.12-unknownhash

Additionally, attach any relevant sections from the log files above.```

After updating to the newest version of vcpkg (reinstalled) all of the warnings are gone, but this one error still keeps me up at night. Seems like the complaint is in building the pybind11 portion. Note that the system python is currently 3.9.1
Also, quick thank you to you guys for wrangling these issues, I looked over the other related tickets, much appreciated.
Command
sudo ./vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,pybind11,tools]
../pybind11/x64-linux-dbg/CMakeFiles/CMakeOutput.log
CMakeOutput.log
config-x64-linux-dbg-out.log
$cat /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-out.log
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- pybind11 v2.6.0
-- CMake 3.19.2
-- Configuring incomplete, errors occurred!
See also "/mnt/c/kali/vcpkg/buildtrees/pybind11/x64-linux-dbg/CMakeFiles/CMakeOutput.log".

config-x64-linux-dbg-err.log
$cat /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-err.log
CMake Error at /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find Python (missing: Python_INCLUDE_DIRS Python_LIBRARIES
  Development Development.Module Development.Embed) (found version "2.7.18")
Call Stack (most recent call first):
  /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE)
  /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/share/cmake-3.19/Modules/FindPython.cmake:470 (find_package_handle_standard_args)
  /mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake:634 (_find_package)
  tools/pybind11NewTools.cmake:33 (find_package)
  tools/pybind11Common.cmake:190 (include)
  CMakeLists.txt:162 (include)

Shell output (trimmed)
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):
Command failed: /mnt/c/kali/vcpkg/downloads/tools/cmake-3.19.2-linux/cmake-3.19.2-Linux-x86_64/bin/cmake /mnt/c/kali/vcpkg/buildtrees/pybind11/src/20d59fb844-6f1ff890dc.clean -DPYBIND11_TEST=OFF -DPYBIND11_FINDPYTHON=ON -DPython3_EXECUTABLE=/usr/bin/python3 -DCMAKE_MAKE_PROGRAM=/mnt/c/kali/vcpkg/downloads/tools/ninja-1.10.1-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/mnt/c/kali/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/mnt/c/kali/vcpkg -D_VCPKG_INSTALLED_DIR=/mnt/c/kali/vcpkg/installed -DVCPKG_MANIFEST_INSTALL=OFF -DPYTHON_IS_DEBUG=ON -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/mnt/c/kali/vcpkg/packages/pybind11_x64-linux/debug
    Working Directory: /mnt/c/kali/vcpkg/buildtrees/pybind11/x64-linux-dbg
    Error code: 1
    See logs for more information:
      /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-out.log
      /mnt/c/kali/vcpkg/buildtrees/pybind11/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:328 (vcpkg_execute_required_process)
  ports/pybind11/portfile.cmake:11 (vcpkg_configure_cmake)
  scripts/ports.cmake:136 (include)

Error: Building package pybind11:x64-linux 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: pybind11:x64-linux
  Vcpkg version: 2020.11.12-unknownhash

Additionally, attach any relevant sections from the log files above.```

I excluded pybind11 from the build.
Initially the results were essentially the same as when I tried this in my first comment.
Logs show undefined reference to GOMP stuff.
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::CompressImage(unsigned char const*, int, int, int, void*, int, float*) [clone ._omp_fn.0]':
(.text+0x3d2): undefined reference to `omp_get_num_threads'
/usr/bin/ld: (.text+0x3d9): undefined reference to `omp_get_thread_num'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::DecompressImage(unsigned char*, int, int, int, void const*, int) [clone ._omp_fn.1]':
(.text+0x682): undefined reference to `omp_get_num_threads'
/usr/bin/ld: (.text+0x689): undefined reference to `omp_get_thread_num'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::CompressImage(unsigned char const*, int, int, int, void*, int, float*)':
(.text+0x8fb): undefined reference to `GOMP_parallel'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::DecompressImage(unsigned char*, int, int, int, void const*, int)':
(.text+0x991): undefined reference to `GOMP_parallel'

Using the native/vanilla Windows Power Shell instead of kali / bash through WSL, I successfully ran the command:
PS C:\kali\vcpkg> .\vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,tools]:x64-windows
(still excluding pybind11 and specifying x64-windows)
As far as I can tell everything was installed just fine with this attempt.
Elapsed time for package openimageio:x64-windows: 4.341 min
Total elapsed time: 54.08 min

There might be something set up (or missing) in my WSL distro that could have been interfering, earlier on I did try installing/updating things like cmake, libsquish-dev ect and I figured using vanilla PS might help.
Let me know if there is any info I can provide for why it didn't work on a different shell.
My original issue although not completely solved, was evaded as I can live without the pybind11 portion,
and I don't need to explicitly install openimageio on the shell I'll be using it on.
Thank you for your time,

I excluded pybind11 from the build.
Initially the results were essentially the same as when I tried this in my first comment.
Logs show undefined reference to GOMP stuff.
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::CompressImage(unsigned char const*, int, int, int, void*, int, float*) [clone ._omp_fn.0]':
(.text+0x3d2): undefined reference to `omp_get_num_threads'
/usr/bin/ld: (.text+0x3d9): undefined reference to `omp_get_thread_num'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::DecompressImage(unsigned char*, int, int, int, void const*, int) [clone ._omp_fn.1]':
(.text+0x682): undefined reference to `omp_get_num_threads'
/usr/bin/ld: (.text+0x689): undefined reference to `omp_get_thread_num'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::CompressImage(unsigned char const*, int, int, int, void*, int, float*)':
(.text+0x8fb): undefined reference to `GOMP_parallel'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libsquish.a(squish.o): in function `squish::DecompressImage(unsigned char*, int, int, int, void const*, int)':
(.text+0x991): undefined reference to `GOMP_parallel'

Using the native/vanilla Windows Power Shell instead of kali / bash through WSL, I successfully ran the command:
PS C:\kali\vcpkg> .\vcpkg install openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,webp,openjpeg,tools]:x64-windows
(still excluding pybind11 and specifying x64-windows)
As far as I can tell everything was installed just fine with this attempt.
Elapsed time for package openimageio:x64-windows: 4.341 min
Total elapsed time: 54.08 min

There might be something set up (or missing) in my WSL distro that could have been interfering, earlier on I did try installing/updating things like cmake, libsquish-dev ect and I figured using vanilla PS might help.
Let me know if there is any info I can provide for why it didn't work on a different shell.
My original issue although not completely solved, was evaded as I can live without the pybind11 portion,
and I don't need to explicitly install openimageio on the shell I'll be using it on.
Thank you for your time,

I will handle this PR today.

I will handle this PR today.

@Hoikas  Did you know why oiio couldn't find python3 in vcpkg download/tools folder?
Although #15221 was merged, this issue still exist.

@Hoikas  Did you know why oiio couldn't find python3 in vcpkg download/tools folder?
Although #15221 was merged, this issue still exist.

@JackBoosY It looks like oiio does the same thing as cppcms and uses find_program(), so #15221 wouldn't fix it. I will prepare a PR.

@JackBoosY It looks like oiio does the same thing as cppcms and uses find_program(), so #15221 wouldn't fix it. I will prepare a PR.

This was a "fun" one to work on... Three pull requests: #15506, #15507, and #15509.

This was a "fun" one to work on... Three pull requests: #15506, #15507, and #15509.


Fix remote launching for SageMaker back-end experiments

This is about remote launching of experiments with SageMaker backend:
https://github.com/awslabs/syne-tune/blob/main/benchmarking/commons/launch_remote_sagemaker.py
https://github.com/awslabs/syne-tune/tree/main/benchmarking/nursery/launch_sagemaker
We currently run Syne Tune via a SM estimator, using the SKLearn framework (PyTorch also does not work). This kind of works, but there are at least two glitches:

SageMaker warm pool feature does not work (seems like sagemaker PyPI version is too old, even if listed as explicit dependency)
sagemaker_search in sagemaker_utils.py does not work properly (lists only subset of running jobs), which does not allow
to manage busy workers properly

Need to ensure that Syne Tune is run remotely in the same was as on a laptop, i.e. the latest sagemaker PyPI is used, and sagemaker_search works correctly.

For now, I'll fix the problem with sagemaker_search by keeping trials marked as busy if their status is not returned. Since this error seems to concern trials which have just been started, this seems the right behaviour.
Still, we should fix this difference between Syne Tune running remotely and on the laptop.

Note: @geoalgo  used to build a Docker image of Syne Tune in order to do remote launching. Only later, he proposed to do remote launching with a SM framework.
We may have to go back to building an image. But if so, this needs to be a robust process, which for example also works when you are on a SM notebook instance.

Dealt with in #482


fix: Make clear() method public

Summary

Makes clear() method from ExperimentClient public so client can reset memory cache.
Related issue: https://github.com/amplitude/experiment-ios-client/issues/27
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:

Thanks @fedejordan !

thanks for reviewing @bgiori ! Do you have an ETA for the fix release?


docker_container and port syntax

I have noticed a difference related to port bindings between the containers created with the cookbook (currently version 1.0.24) and those created with an equivalent docker client command-line.
I create my container in the cookbook like this:
docker_container 'my-app' do
  repo 'busybox'
  tag 'ubuntu-14.04'
  port ['80', '22']
  ...
end

I am trying to write an assertion in my cookbook test suite to check whether the container is publishing a given port. With version 0.37 of this cookbook (which used 'docker' client command-line instead of the API), I would just search for 80/tcp in the output of `docker inspect --format='{{ .HostConfig.PortBindings }}' for example.
However, now that the containers are created using the docker API, I can only match for 80 (without 'tcp' at the end), which means that containers created by the cookbook and by the command-line API do not docker-inspect the same anymore.
Here is a sample shell session demonstrating the problem.
# when we start, we are supposed to have converged the node and the `my-app` container exists.
root@docker-ubuntu-1404:~# docker inspect --format='{{ .HostConfig.PortBindings }}' my-app
map[22:[{ }] 80:[{ }]] # <--- new format, no '/tcp' present
root@docker-ubuntu-1404:~# docker rm -f my-app
my-app
# now I recreate the container manually using equivalent command-line
root@docker-ubuntu-1404:~# docker create --name="my-app" --publish="22" --publish="80" busybox:ubuntu-14.04 /bin/top
WARNING: Your kernel does not support swap limit capabilities, memory limited without swap.
dd7e74178fc99a23e1781028b539c2f19ba039bab17c7856309389fdbd3fe856
root@docker-ubuntu-1404:~# docker inspect --format='{{ .HostConfig.PortBindings }}'
my-app
map[22/tcp:[{ }] 80/tcp:[{ }]]  # <-- note the presence of /tcp in the output.

Would it be possible to change the way port bindings are created in the cookbook to follow the convention of the docker command-line client?

That makes sense to me.
I won't have very much time to work on this over the next week, so if you'd like to take a crack at a PR, I can point you in the right direction:
The test cookbook exercises ports beginning here -  https://github.com/bflad/chef-docker/blob/master/test/cookbooks/docker_test/recipes/container.rb#L39
... and the serverspec assertions are here - Just add the inspect line
https://github.com/bflad/chef-docker/blob/4537b99c903ff650e34137daba7b09af6db001d8/test/integration/resources-182/serverspec/assert_functioning_spec.rb#L140
The logic to generate the port data begins somewhere around here
https://github.com/bflad/chef-docker/blob/4537b99c903ff650e34137daba7b09af6db001d8/libraries/helpers_container.rb#L62
And is consumed here
https://github.com/bflad/chef-docker/blob/4537b99c903ff650e34137daba7b09af6db001d8/libraries/provider_docker_container.rb#L113
-s

Sure @someara , will try to schedule it for the end of week too (together with other PRs on your great cookbook; I'm currently porting my existing application cookbook to version 1.x of this cookbook, so discovering a lot of very subtle issues).


[chore] bump to ember 3.28

Got some code for us? Awesome 🎊!
Please include a description of your change & check your PR against this list, thanks!
Tracking the 3.28 progress, it seems like there are some outstanding octane tasks left, this should pass when those are done. I ran a few codemods locally to see if we can get some of them done.

[x] There's a clear use-case for this code change
[x] Commit message has a short title & references relevant issues
[ ] The build will pass (run ember test from the repo root - will be core/client if working from the submodule in Ghost).

More info can be found by clicking the "guidelines for contributing" link above.

Hey @gabrielcsapo 👋 We've cleared some of the other blockers for this upgrade but I've run into odd errors from Ember Data when it tries to read errors on the response, failing with TypeError: Cannot read properties of null (reading 'getErrors').
We're prepping for moving the Admin repo into the recently created Ghost monorepo so old PRs are being cleared up. Seeing as there's no immediately obvious fix and the changes here are fairly small/easy to recreate after the move I'm going to close for now.
Thanks for all your help with the Octane migrations 😊


Set default db for activations to activations-db

This PR changes the default setting of all environments to use the activations-db for activations, instead of the whisks-db.
It also requires the flag db_split_actions_and_activations to be set. It still can be false, but if it is false, you should care about the migration of your activations to the activations-db.
If you don't matter throwing away all your data, just execute the ansible playbook wipe.yml, after db_split_actions_and_activations is set to true.
If you want to keep all your data, follow the instructions on the following page:
https://gist.github.com/cbickel/37e651965781b27de245eac0ce831a53
PG1#1437

PG1#1452 is green.


Line removal from README to trigger target-tools version bump

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Coverage: 92.502%. Remained the same when pulling 9c0ff3845c051b978551dbdb1e7eac8eb80c10c5 on ericfichtel:bump_target_tools_version into bee18345fb7ddda5baff7aa4e2478ee18ef96cce on adobe:main.


Redux refactor and weight slider fix

Description
This combines the slider bug fix (an async issue that resulted in the displayed slider value being one off) and MB-289 which is part of the redux refactor that shifts to putting all data into entities.
This removes the createOrUpdatePpm and utilizes updatePPM and createPPM.  It loads the PPM into the entities when not already present after one of the previous functions through loadPPMs.
Reviewer Notes
~Currently getting an error in integration test that I've not been able to recreate locally.  Working on it.~  Fixed.
Setup
make db_dev_e2e_populate
Log into service member app
Sign in as local user<EMAIL_ADDRESS>Walk through creating a ppm move
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for the create/updatePPM change
this story for the slider change

Kim... this looks good to me and works as expected.
I've made a list of outstanding PPM things I noticed, but this pr didn't introduce them...
With the blessing from Ron, I'd say 🚢


Use Travis CI and flake8 to find syntax errors and undefined names

The owner of the this repo would need to go to https://travis-ci.org/profile and flip the repository switch on to enable free automated flake8 testing of each pull request.

Thanks for the PR.
We are already using our own CI system and running all the tests for pull requests.
Closing.


Dosn't have custom atribute

Supports custom FFmpeg command line arguments - NO!

thanks for pointing it out.
i have updated the readme, but i want to add this feature back in.

it is now supported as of v2.1.0

it is now supported as of v2.1.0

i've no clue how to use them

it is now supported as of v2.1.0

i've no clue how to use them

I am trying the same with ExecuteAsync("my ffmpeg arguments") but i can't see any effect when running it. It just jumps over it

Same for me. How to use the arguments?


File Upload Multipart not implemented

class MyMultiPart is comment out
Does HttpServer does not support File upload post?

Its pretty old and to be honest i think its abandoned project. Even if ive been thinking about it as of nice tool for testing i didnt use it for a while.
Maybe i dont know how to use it but never been able to make this part to work (sending and reading files from spiff).

ok.

Maybe @nkolban has some more to say?

Sending large file cause stack overflow.  I guess HttpServer does not handle multi-part.
D (1451808) HttpServerTask: HttpServer that was listening on port 80 has received a new client connection; sockFd=4098
D (1451819) HttpParser: >> parse: socket: fd: 4098
D (1451825) HttpParser: >> parseRequestLine: "POST /upload_file HTTP/1.1" [26]
D (1451831) HttpParser: << parseRequestLine: method: POST, url: /upload_file, version: HTTP/1.1
Guru Meditation Error: Core  0 panic'ed (Unhandled debug exception)
Debug exception reason: Stack canary watchpoint triggered (HttpServerTask)
Backtrace: 0x4000c350:0x3ffcf300 0x401436ab:0x3ffcf310 0x4013d2f9:0x3ffcf330 0x4013db3d:0x3ffcf3b0 0x4013dbae:0x3ffcf3e0 0x4010c753:0x3ffcf400 0x4010f9fe:0x3ffcf430 0x4010d82a:0x3ffd4080 0x40109e2a:0x3ffd4310 0x4010c2a0:0x3ffd4420
0x401436ab: pbuf_copy_partial at C:/Work/LibDev/esp32/esp-idf/components/lwip/core/pbuf.c:1247
0x4013d2f9: lwip_recvfrom at C:/Work/LibDev/esp32/esp-idf/components/lwip/api/sockets.c:1814
0x4013db3d: lwip_recvfrom_r at C:/Work/LibDev/esp32/esp-idf/components/lwip/api/sockets.c:1814
0x4013dbae: lwip_recv_r at C:/Work/LibDev/esp32/esp-idf/components/lwip/api/sockets.c:1814
0x4010c753: Socket::receive(unsigned char*, unsigned int, bool) at C:/Work/LibDev/esp32/esp-idf/components/cpp_utils/Socket.cpp:245
0x4010f9fe: HttpParser::parse(std::shared_ptr) at C:/Work/LibDev/esp32/esp-idf/components/cpp_utils/HttpParser.cpp:219
0x4010d82a: HttpRequest::HttpRequest(std::shared_ptr) at C:/Work/LibDev/esp32/esp-idf/components/cpp_utils/HttpRequest.cpp:98
0x40109e2a: HttpServerTask::run(void*) at C:/Work/LibDev/esp32/esp-idf/components/cpp_utils/HttpServer.cpp:323
0x4010c2a0: Task::runTask(void*) at C:/Work/LibDev/esp32/esp-idf/components/cpp_utils/Task.cpp:59


Custom units

Greetings,
I'm trying to specify a custom unit in my panel configuration. The issue I have here is the unit I need is "ampere", however it converts them to kiloamperes when the value is above 1000.  With other plugins I am simply specifying a custom unit with the tag A and avoid the conversion.
Is there any way in the .yaml configuration to specify such custom units?

Those are quite heavy currents;-) I don't get near those values at home and LV substations, I'm using "amp" for units.
Maybe custom overrides could be enabled for the panel, can you show how you make such a custom unit in other panels?
Alternatively, the number of decimals could be utilized with a negative number to indicate the number of digits you want before the decimal.

Greetings,
I'm trying to specify a custom unit in my panel configuration. The issue I have here is the unit I need is "ampere", however it converts them to kiloamperes when the value is above 1000. With other plugins I am simply specifying a custom unit with the tag A and avoid the conversion.
Is there any way in the .yaml configuration to specify such custom units?

Not at the moment. I could add a units_postfix field to the yaml that you could use alongside number maybe? I just had a look in a timeseries panel to see you they did it but couldn't see how you select a custom unit. Could you explain the steps?

I had a play & google and discovered if you type in the units field (as opposed to using the menus) you get the custom option in the normal grafana panels. I'm adding support for this in the plugins yaml with a new field unitsPostfix. There you can enter your custom units. It will get built into the next version.

This has been added now in version 1.7.0. Alongside units there's now a unitsPostfix field where you can add your custom unit.


'META-INF/imageslider_release.kotlin_module'.

hi, I get this error
More than one file was found with OS independent path 'META-INF/imageslider_release.kotlin_module'.

Can you check this page: https://stackoverflow.com/questions/44342455/more-than-one-file-was-found-with-os-independent-path-meta-inf-license

I've try it but the error doesn't resolved
On Sat, Jul 18, 2020, 10:07 AM Deniz Coskun<EMAIL_ADDRESS>wrote:

Can you check this page:
https://stackoverflow.com/questions/44342455/more-than-one-file-was-found-with-os-independent-path-meta-inf-license
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/denzcoskun/ImageSlideshow/issues/30#issuecomment-660440663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZDYTVCF243UXN2AEKG4ITR4FCZPANCNFSM4O7HOC4Q
.

Did you try it? https://stackoverflow.com/a/53165350


[Discussion] Streamlining Prisma's support channels

Hey everyone 👋 we want to use this GitHub issue to spark a discussion about the variety of Prisma's community and support channels and how to organize them better. Please leave your feedback and ideas!
We currently have the following official and unofficial community and support channels:

Slack
GitHub
Prisma forum
Spectrum
Intercom
Email
Stackoverflow

Our support team is working very hard but taking care of all the channels at once is an almost impossible task. We're currently evaluating how to streamline the channels, here are a few of our thoughts.
While we currently use Slack as our main communication channel to the community, there are some problems Slack brings when used with a community as huge as ours (we currently have more than 18k members in our Slack). Mostly, there's no way to make Slack messages searchable on the web (e.g. via Google). This means we can't point to older replies when a question is being repeatedly asked on Slack and users don't have a good way of finding previous answers in the first place. The realtime aspect of Slack is great, but to provide sustainable support it should be possible to persist and reuse previous answers.
We use the Prisma forum to enable broader discussions among community members and respond to questions with our support team. These questions and answers can be persisted, but many of our users aren't aware of the forum and rather default to asking questions on Slack. Another issue is that our forum is running on discourse which requires our users to create an extra account.
Spectrum seemed to be a great middleground between the ability to provide realtime support and persisting conversations so that they could be reused later. Many companies have already moved their communities to Spectrum (e.g. ZEIT and Apollo), however, we've been hesitant for a few reasons:

We are worried about Spectrum's reliability as it has been facing regular downtimes
Spectrum doesn't yet provide a mobile app which we consider an important factor
The chat experience often is fairly slow

While we believe that the Spectrum team would be able to fix the above issues, we're worried that Spectrum isn't actively developed any more (the last commits are from almost two months ago).
So, instead of moving our community to Spectrum, we'd rather hear your opinions and thoughts. Are you aware of a community management tool that might help or have other feedback to share? Please let us know your ideas!

Is there any place when voting on features priorities is possible?
I think github issues for bugs and features + stackoverflow for valuable questions + slack / forum for community + blog for news and plans announcing is great composition. I do not have opinion about Spectrum.

My team is going to build a software product with graphQL and selected Prisma for this.
Our first customer release will be in next 3-4 months; Now I need to know that should I go for Prisma 2 or Prisma 1.3+ ?

I understand the reasons you mention for not going to Spectrum, (worth mentioning that development seems to be active again, though) but the fact that Slack hides old conversations is really a big, big hindrance and is, in my opinion, reason enough to move away.
Hopefully Spectrum will revive its mobile client.

Struggling to get graphql-yoga to work with prisma and docker
I used this as a starting point:
https://github.com/howtographql/react-urql
I followed the docker instructions and it works locally.
However, if I add a service for the graphql-yoga server, I get a "connection refused" error when I go to the playground to test. The graphql-yoga server works but won't connect to the prisma layer as the connection is refused.

@nikolasburk I've tried to join the slack community, but it seems like the invite page is broken: https://slack.prisma.io/invite
It's been like this for a while since I tried about 2 weeks ago as well. I tried pinging Prisma on Twitter, but got no response.
Any help would be appreciated.

Bumping this. The invite link is still broken.

@MJGTwo the link is located at https://slack.prisma.io/

We use the Prisma forum to enable broader discussions among community members and respond to questions with our support team

What do you mean? The forum is closed and is in read-only mode.
Also, the slack channel has almost 30,000 people yet questions on the #general channel don't seem to get any response.

Could you maybe provide a set of criteria that you and your team are using to assess the viability / appropriateness of a platform? That would help the community provide you better answers to what you're looking for.
From "reading between the lines", you want:

Searcheable / indexable content
Platform is in active maintenance

What else?
From the above 2 criteria, I do think that slack being a closed system isn't a good candidate, which is why I think making stack overflow the de-facto forum might be the right direction. I'm not familiar with discourse, but it seems like it's achieving the same goal as Slack. Same thing with spectrum - seems like it does the same thing as SO, except it's not as well-maintained as SO.
Github could be used in tandem with SO for bug reports and feature requests.


Custom intervals

CUSTOM INTERVALS
In addition to the above intervals, the following pattern can be used to create highly specific custom intervals: every_{n}_{units}, where {n} can be any whole integer greater than 0 (zero), and {units} can be minutes, hours, days, weeks, months, or years.
Here are a few examples:
every_30_minutes
every_8_hours
every_3_days
every_2_weeks
every_6_months
every_3_years

done


BT_ros2 update to Galactic (Control with Behavior Tree demo is bugged)

Hello,
I would like to know if there are any plans to update this BT_ros2 repository with the ROS Galaxy version?
Right now I'm having trouble building everything without any deeper changes (e.g. error: ‘rclcpp::executor’ has not been declared).
Package bt_ros2 failed to build:
--- stderr: bt_ros2
/home/lj/ros2_ws/src/BT_ros2/src/send_goal.cpp: In function ‘int main(int, char**)’:
/home/lj/ros2_ws/src/BT_ros2/src/send_goal.cpp:35:21: error: ‘rclcpp::executor’ has not been declared
   35 |             rclcpp::executor::FutureReturnCode::SUCCESS)
      |                     ^~~~~~~~
/home/lj/ros2_ws/src/BT_ros2/src/send_goal.cpp:51:21: error: ‘rclcpp::executor’ has not been declared
   51 |             rclcpp::executor::FutureReturnCode::SUCCESS)
      |                     ^~~~~~~~
In file included from /home/lj/ros2_ws/src/BT_ros2/src/bt_ros2.cpp:1:
/home/lj/ros2_ws/src/BT_ros2/src/nav2_client.hpp: In member function ‘virtual BT::NodeStatus Nav2Client::tick()’:
/home/lj/ros2_ws/src/BT_ros2/src/nav2_client.hpp:98:25: error: ‘rclcpp::executor’ has not been declared
   98 |                 rclcpp::executor::FutureReturnCode::SUCCESS)
      |                         ^~~~~~~~
/home/lj/ros2_ws/src/BT_ros2/src/nav2_client.hpp:114:25: error: ‘rclcpp::executor’ has not been declared
  114 |                 rclcpp::executor::FutureReturnCode::SUCCESS)
      |                         ^~~~~~~~
In file included from /home/lj/ros2_ws/src/BT_ros2/src/bt_ros2.cpp:3:
/home/lj/ros2_ws/src/BT_ros2/src/snapshot_client.hpp: In member function ‘virtual BT::NodeStatus SnapshotClient::tick()’:
/home/lj/ros2_ws/src/BT_ros2/src/snapshot_client.hpp:36:85: error: ‘rclcpp::executor’ has not been declared
   36 |             if (rclcpp::spin_until_future_complete(node_, result_future) != rclcpp::executor::FutureReturnCode::SUCCESS)
      |                                                                                ^~~~~~~~
make[2]: *** [CMakeFiles/send_goal.dir/build.make:63: CMakeFiles/send_goal.dir/src/send_goal.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:107: CMakeFiles/send_goal.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [CMakeFiles/bt_ros2.dir/build.make:63: CMakeFiles/bt_ros2.dir/src/bt_ros2.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:80: CMakeFiles/bt_ros2.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
---
Failed   <<< bt_ros2 [8.92s, exited with code 2]

I have followed this part of README.
Best regards
Łukasz Janiec

Thank you reporting this issue, I will try to fix this.

Fixed!
See https://github.com/Adlink-ROS/BT_ros2/commit/a8e31d1e5fccb2d34b8a5646529fc442d1b566b5


Add support for swift 6 nightlies

With the upcoming migration to Swift 6 and Swift Testing it would be cool if support for swift 6 can be added early via nightlies so that work in progress towards swift 6 migration, especially around concurrency and testing, can already be part of the workflows on GitHub.

Yeah I agree this would be great! The only real hurdle is resolving the path to the pkg to download as they contain the date when the last snapshot where created (unlike stable releases that have a fixed path).
Once that is figured out (would be great if they would have a feed or something) this would be easy to implement. 🙂

Exactly, I'm aware of the limitation, I think it may need a collaboration from the swift build team to perhaps provide a stable symlink and or sum file so that the action can easily compare whether new nightly was published. Alternatively hardcoding the path with date to the action and re-release a patch version of this action automatically whenever new nightly is published, but that's I assume needles work unless automated as much as possible.

Hi! Swiftly fetches GitHub tags and uses regex to match specified snapshot and fetch date in the end (parsing snapshot function). Maybe this can be used to add snapshot support to GitHub Actions similarly as Swiftly does, and specified something like swift-version: "main-snapshot".


Update gradle version

Update Android gradle plugin to 7.4.2
Update gradle to 7.5

Is there any reason to change the gradle versions?

New versions of Android Studio require a recent version of Gradle to build the project.

I'm using Android Studio Giraffe | 2022.3.1
Build #AI-223.8836.35.2231.10406996, built on June 29, 2023
Runtime version: 17.0.6+0-b2043.56-10027231 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
That does not require or even suggest that gradle needs updating
Everything works correctly without upgrading gradle for me.

On Giraffe Stable, I've got this message as soon as I open the project.

Maybe is related to the fact I'm using Java 17.

I'm also using a JDK 17.0.6 for Gradle

I'll have a look at doing the update, but I'm most concerned about the breaking the Maven publishing scripts with the Gradle update.


mmcv>=2.0.0 compatibility

With the new mmcv 2.0.0 there's a lot of backward compatibility breaking changes. It seems like mmcls doesn't exist and has been renamed mmpretrain so all of the mmcls based configs won't load in this repo now.
        f'Please install mmcv>={mmcv_minimum_version}, <={mmcv_maximum_version}.'
E   AssertionError: MMCV==2.0.0 is used but incompatible. Please install mmcv>=1.4.2, <=1.9.0.

It will take some time for me to update everything to mmcv 2.0.0, so for now you can just install an earlier version of mmcv.

@thomasehuang the upgrade to mmcv seems pretty challenging. One approach I took was to export one of the models as TorchScript so mmcv wasn't required anymore
https://github.com/d4l3k/torchdrive/commit/4adcc18a72b98ea8c3bbd22c371b317bf0d693d0
I'm not a big fan of mmcv and it'd be great if most models were supported out of the box with a torchscript link. Doesn't seem like it's possible for the mmdet models though
btw, this project has been a huge help so thank you so much!

Thanks a lot for the suggestion! Indeed, it will be easier for users if the reliance on MMCV is removed. We will consider this for the future.


Speed Estimation of multiple vehicles

Hello Sir
Is this source code estimate speed of multiple vehicles?
Thanks and Regards
Ganesh Koushik

Speed prediction for multi-vehicles is supported except a case that vehicles are not detected by the ROI line at the same time but I will release new version of my project that will cover that case also.


Correction for raw affiliation Faculty of Business Administration, University of New Brunswick, 7 MacAulay Lane, Fredericton, NB, CanadaSystems Engineering Department, King Fahd University of Petroleum and Minerals, Dhahran 31261, Saudi Arabia

Correction needed for raw affiliation Faculty of Business Administration, University of New Brunswick, 7 MacAulay Lane, Fredericton, NB, CanadaSystems Engineering Department, King Fahd University of Petroleum and Minerals, Dhahran 31261, Saudi Arabia
raw_affiliation_name: Faculty of Business Administration, University of New Brunswick, 7 MacAulay Lane, Fredericton, NB, CanadaSystems Engineering Department, King Fahd University of Petroleum and Minerals, Dhahran 31261, Saudi Arabia
new_rors: 03yez3163;05nkf0n29
previous_rors: 03yez3163
works_examples: W2162024584
contact: f882b29f8d712b6ee51994d1ab7c6f25:2dbfde60 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 53s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

+1 :green_heart:
shadedjars
5m 22s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 17s
hbase-common in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 29s
hbase-common in the patch passed.

23m 31s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1522

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b70e066107f9 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 38954edb25

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/testReport/

Max. process+thread count
271 (vs. ulimit of 12500)

modules
C: hbase-common U: hbase-common

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 35s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 40s
master passed

+1 :green_heart:
compile
0m 25s
master passed

+1 :green_heart:
shadedjars
5m 59s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 33s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 15s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

+1 :green_heart:
shadedjars
5m 51s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 21s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 44s
hbase-common in the patch passed.

26m 43s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1522

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 034b856621c3 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 38954edb25

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/testReport/

Max. process+thread count
226 (vs. ulimit of 12500)

modules
C: hbase-common U: hbase-common

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 27s
master passed

+1 :green_heart:
checkstyle
0m 26s
master passed

+1 :green_heart:
spotbugs
0m 50s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 55s
the patch passed

-0 :warning:
checkstyle
0m 25s
hbase-common: The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m  6s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2.

+1 :green_heart:
spotbugs
0m 51s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

30m 51s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1522

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 203a8a5e4be3 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 38954edb25

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-common U: hbase-common

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1522/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Upgraded xray docker-stack 2.8.9 to 2.9.0, and now I get "error token exchange" because of "405 Method not allowed"

[2019/09/11 11:49:34 UTC] [EROR] (jfrog.com/xray/pkg/access/access_sso.(*AccessSsoClient).ExchangeToken:73) Failed to exchange token , err: statusCode: 405,  models.AccessError{Code:"", Message:"Method Not Allowed", Detail:""} [2019/09/11 11:49:34 UTC] [EROR] (jfrog.com/xray/internal/handlers/auth.AuthHandler.SsoExchange:343) statusCode: 405,  models.AccessError{Code:"", Message:"Method Not Allowed", Detail:""}
I looked at this page: https://jfrog.com/knowledge-base/why-does-my-login-to-xray-ui-fail-with-a-message-error-token-exchange-in-the-browser-after-entering-credentials-during-the-sso-redirect/
but I don't get a 401 error, plus this setup worked just fine before I updated.

Can you share the commands used to apply the upgrade?

What was changed in the setup?
One option can be a reverse proxy that translated the Method to the request between Xray<>Artifactory.
e.g
POST translated to GET
Please provide more information on the installation.

I installed the Artifactory and XRay stacks as per the instructions on this site, on CentOS 7. All required folders were created with the right permissions.
artifactory-pro: 6.12.1
xray: 2.8.9
I'm unable to use git on the server in question, so all scripts were copy-pasted in. Also, two modifications were made to the docker-compose file:

First I removed the exposing of PostgreSQL to the host. Nothing external should need to access PostgreSQL, so I saw no need to expose it.
Second, the XRAY_SERVER_PORT variable in the .env file caused us issues when we tried running the service on a custom port, because the compose-file changes both the internal and external ports for xray-server, but doesn't tell the xray service to also listen to the port inside the image. this means that in the compose-file xray-server section I have the following:
    ports:     - "$XRAY_SERVER_PORT:8000"

The stacks were then fired up, and our Apache reverse-proxy was configured as per JFrog's instuctions, I logged in as admin on both instances, triggered the vulnerability-database download on xray and everything worked great.
Then yesterday I saw that there are new versions of both xray and artifactory, so I started with xray, went into the .env-file, changed the XRAY_VERSION variable from 2.8.9 to 2.9.0 and did a
docker-compose -f xray-compose.yml up -d.
The process, pulls the new images and starts the updated xray service. I go to the URL to verify a successful upgrade, get the login-page, log in, and BAM! 405 error in the log, no login.

20190913064224|55|REQUEST|[my IP]|anonymous|POST|/ui/auth/login|HTTP/1.1|200|60<PHONE_NUMBER>4224|25|REQUEST|[my IP]|admin|GET|/ui/auth/redirect|HTTP/1.1|200|0<PHONE_NUMBER>4224|1|REQUEST|[internet proxy server address]|non_authenticated_user|GET|/api/system/gateway/openid/token|HTTP/1.1|405|0
Frustrating and a bit embarrassing, but the problem has been found and resolved.
When we set up the reverse-proxy, we did a bit of testing, and things were commented out in the proxy-config. Now that the service is up and running, one of our people cleaned out the unused (commented) code, and managed to remove the header-rewrite in the process.
So I apologize for wasting your time on a non-issue. I'm taking this as a reminder to not assume that the upstream (reverse-proxy in this case) is fine, and revise my upgrading-procedure to include some more pre-upgrade checking. But the timing of this couldn't have been worse, the reverse-proxy cleanup was done at the same time as I was upgrading, so it looked like the upgrade was the culprit. Oh well.. ;)
Thanks for great help in locating the issue

Happy it's resolved @SnorreSelmer !
We are always happy to help.

@SnorreSelmer could you provide some more details on your header rewrites? We're seeing a very similar issue and we're currently suspecting our reverse-proxy as well. We're using Haproxy so if you are too any suggestions would be greatly appreciated!

Not using HAProxy, just a standard Apache reverse proxy. The header-rewrites we used were the same as are recommended in the JFrog documentation.


Release/1.5.0

Here is an initial draft of the release notes.
endaq-python 1.5.0 is the culmination of 4 months of hard work to round out the library for general-purpose shock and vibration data analysis and visualization. It contains many new functions, numerous bug fixes, better documentation, and improved testing coverage. All users are encouraged to upgrade to this new release.
New Features

calc.fft.rolling_fft()  to calculate FFTs across many different time segments, either evenly spaced or discretely defined
calc.psd.rolling_psd()  to calculate PSDs across many different time segments, either evenly spaced or discretely defined
calc.psd.spectrogram()  a wrapper around scipy.signal.spectrogram() for an easier interface when working with dataframes with multiple channels
calc.rotation.quaternion_to_euler() to convert quaternion data to euler angles (this had been in a previous release but wasn't added to the __init__.py file or the docs)

Fixes / Changes

calc.fft.aggregate_fft() now defaults to overlap between segments of 50%

Codecov Report

Merging #203 (b40668c) into main (a878efd) will increase coverage by 8.85%.
The diff coverage is 90.09%.

@@            Coverage Diff             @@
##             main     #203      +/-   ##
==========================================
+ Coverage   61.74%   70.59%   +8.85%
==========================================
  Files          34       34
  Lines        2614     3095     +481
==========================================
+ Hits         1614     2185     +571
+ Misses       1000      910      -90

Impacted Files
Coverage Δ

endaq/plot/dashboards.py
46.87% <ø> (+40.00%)
:arrow_up:

endaq/batch/analyzer.py
91.83% <40.00%> (-1.58%)
:arrow_down:

endaq/calc/psd.py
86.66% <78.65%> (-2.96%)
:arrow_down:

endaq/ide/info.py
86.18% <80.00%> (-1.82%)
:arrow_down:

endaq/plot/plots.py
67.54% <93.01%> (+51.31%)
:arrow_up:

endaq/calc/utils.py
89.18% <94.44%> (+3.82%)
:arrow_up:

endaq/calc/stats.py
93.84% <95.65%> (+12.59%)
:arrow_up:

endaq/calc/fft.py
72.14% <96.00%> (+7.43%)
:arrow_up:

endaq/calc/shock.py
89.20% <97.56%> (+2.06%)
:arrow_up:

endaq/__init__.py
100.00% <100.00%> (ø)

... and 9 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Comment to a milestone

I do not know how to comment on the goals of a milestone, so I try it this way:
Why is it important to have the ratings working in parallel? Why not just optimize head first, and the switch to body? I imagine it is viable to switch morphs groups to evaluate for each new generation.

You are right. On the backend, you could do that. Since the 500 morphs you have, are split into a body and head group which are exclusive, you could first do the run for the heads and then do another the selection run for the body and only overwrite the morph values for the body morphs. There is one thing I didn't consider, and that is that it kind of stops being a "pure" genetic algorithm, since you stop using strictly two parents to create 1 child, but instead have two parents to create the head from, and another two parents to create the body from. But as an algorithm it can definitely work.


Add a type field when generating enum schema from EqCodec

This PR adds a type field for enum values when generating an OpenAPI schema from EqCodec.
This is required to work around an issue with swagger-ui where it does not show the enum value unless a type is also given.

Oeh that's really smart! Let's see what CI says.

Wouldn't mind a changelog here either, but let me merge #16 first.

I added a changelog entry. I put it under <IP_ADDRESS>, assuming you want to release this along with #16. Please feel free to move it if that's not your plan.

Merged and released!


Funding Cycle reconfiguration "Reserve spending" form defaults to 5%

This should default to the current Reserved token value, not 5%.
The Reserved spending value on deploy should also default to 0% instead of 5%.

fixed


docker: update default from 24 to 25

Among other improvements, this version of Docker has support for Container Device Interface (CDI) under Linux, what streamlines our capabilities to expose specialized hardware to containers without the need to configure container runtime wrappers.
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

a related PR https://github.com/NixOS/nixpkgs/pull/330130

Closing in favor of #330109


agent0: add crash reporting back in

Trading competition V1 had a first-pass version of crash reporting, but we lost that functionality. We want to add it back in time for the second competition. The TODO is here

Closing with https://github.com/delvtech/elf-simulations/pull/937


Unmute stable tests

Changelog entry
Unmuted tests : stable 605 and deleted 11
reason for each test  why it still muted
https://gist.github.com/naspirato/67e4890e3bb0b01fed5234dcaddb5668
list of unmuted tests  ( Stable > 14 days in row or no_runs > 30 day in row)
https://gist.github.com/naspirato/393d00779bb54e3fc42ba706f626d4fc
Changelog category

Not for changelog (changelog entry is not required)

Additional information
...

testing https://github.com/ydb-platform/ydb/pull/10782


Update manifest class to match discussed specification

This PR updates the manifest class to match the discussion on the dataset doc. Let's focus all further discussion on the manifest in this PR.

I included a schema defining the manifest
Data sources has been renamed to subsets
The manifest now defines which fields / columns are available in a subset and their types
The location for each subset is resolved with the base path defined in the metadata
I'm no longer leveraging dataclasses-json as I don't just want to build a 1 to 1 mapping of the json in Python
All unused keys have been removed from the manifest

The Manifest class is currently mostly focused on making an existing json manifest easily accessible, which is useful for input manifests. We might want to add functionality to create a new manifest programmatically as well, which is useful for output manifests. It might be best that these are two separate classes though, an immutable one for the input manifests and a mutable one for the output manifests.
I'd like to see a similar PR for the component specification as well.

Added functionality to create a manifest using the class as well.


Undefined constant  error Rector\Symfony\Set\SensiolabsSetList::FRAMEWORK_EXTRA_61

composer run analyse fails with "undefined constact Rector\Symfony\Set\SensiolabsSetList::FRAMEWORK_EXTRA_61 " although rector/rector-symfony exists in vendor/rector/rector/vendor/rector/rector-symfony.
I'm using this kit in my standalone library, not in a Symfony full-stack application. But contains some of symfony components.

php 8.2.10
quartetcom/static-analysis-kit v8.2.4
rector/rector 0.17.13

error output
% composer run analyse
> @php static-analysis-kit analyse

Running rector
==============

 [ERROR] Undefined constant
         Rector\Symfony\Set\SensiolabsSetList::FRAMEWORK_EXTRA_61

Script @php static-analysis-kit analyse handling the analyse event returned with error code 1

reproduced on CI:
https://github.com/77web/sendgrid-marketing-campaign-api-php-client/actions/runs/6839602776/job/18597955695

@77web Thank you for reporting this. Actually this is an known issue and (temporarily) can be fixed via pinning rector/rector to v0.17.1. Will going to upgrade v0.18 though. Sorry for inconvenience.

Fix released in v8.1.18 and v8.2.5.


fix infrastructure encryption

Description
link https://github.com/Azure/azure-sdk-for-java/issues/32470
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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

Will any other API get similarly affected?

I don't think so. I checked other "getter"-like methods in nested helper classes (another will be StorageNetworkRulesHelper) and they have "inner" as method parameter.


[objc] Make sure we can build for iOS release using mtouch. Partial fix for #237

Embedding with Xamarin.iOS is different than doing it directly with mono.
This requires some methods to be defined, like the ones only used for
release (when TOKENLOOKUP is defined).
The integration with mtouch is also incomplete (for non-debug build) as
some steps (MdbSym) and SymbolStrip (only used in release by default)
causes FileNotFoundException (some state is not set correctly).
This PR is a fix for the former (headers), a workaround for the later
(mtouch invocation) and a Makefile change to make sure we always build
release/iOS on bots (because untested stuff never works, for long)
ref: https://github.com/mono/Embeddinator-4000/issues/237

Build and tests passed.


Remove all old-style prod-related pipeline configurations, leaving just CI & OneBranch

Which issue this PR addresses:
Fixes https://dev.azure.com/msazure/AzureRedHatOpenShift/_workitems/edit/14282641
What this PR does / why we need it:
Removes all Azure Pipelines code that interacts with prod, leaving just PR CI & E2E. There are some OneBranch files used by the OneBranch pipelines still, these also remain. The replacement of the rest tracks with the releases being moved to EV2/OneBranch.
Note: The pipelines that reference this will need to be deleted as well.
Test plan for issue:
This PR should work :)
Is there any documentation that needs to be updated for this PR?
Release documentation is already deprecated, so should be fine.

/azp run ci

@cadenmarchese I believe there's now ARO.Pipelines ones for that.

Mirror imaging is being kept in because it does not currently run in EV2 public cloud (only INT and FF), but the rest can go.


UI polish

Before/afer pics: https://imgur.com/a/f8JAy
Nothing major, mostly some organization and consistency:

more consistent header (left blue column) width
content area consistent bg color
use entry status colors on entry list
and probably the only contentious change is putting the schema editor above the slug/preview url opts (I spend more time using the schema editor when on this page)

@ctcleary - Would you mind verifying your most recent features? LMK if I broke anything.
Another change (not part of this PR yet) would be to change the schema edit page title to something like "Edit Schema" instead of "Edit Metadata".

I wonder if the schema editor/metadata stuff should be tabbed? With big schemas putting anything under it is going to get awkward to actually use.
Not a pressing issue because it changes relatively infrequently, but still worth considering.

Also :+1: to standardizing terminology and styling. If that's something you're willing to tackle @kevinkace I would be thrilled to merge it!

I'll give it a shot after this pr!

WRT tabs, that sounds like a good idea. I'll try to include that in the next PR as well.

Went over the recent changes with @ctcleary and looks like nothing has broken.


Support TLS1.2

TLS 1.2 is not supported.
From stunnel4 logs:
2015.03.03 19:07:10 LOG7[747]: Service [transmission] accepted (FD=3) from <IP_ADDRESS>:50665
2015.03.03 19:07:10 LOG7[13429]: Service [transmission] finished (0 left)
2015.03.03 19:07:10 LOG7[13430]: Service [transmission] started
2015.03.03 19:07:10 LOG5[13430]: Service [transmission] accepted connection from <IP_ADDRESS>:50665
2015.03.03 19:07:10 LOG7[13430]: SSL state (accept): before/accept initialization
2015.03.03 19:07:10 LOG3[13430]: SSL_accept: 140760FC: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
2015.03.03 19:07:10 LOG5[13430]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket
2015.03.03 19:07:10 LOG7[13430]: Local socket (FD=3) closed
2015.03.03 19:07:10 LOG7[13430]: Service [transmission] finished (0 left)

Works for me on Android 5.0.

Still on 4.4.2 here. Maybe it's an issue with the Java libs bundled with Android. I'll see if I can install 5.0 or newer and try again.

Since TLS 1.2 works for Android 5.+, I'll close this issue. Still, if someone feels like providing a patch for <5.+, that would be appreciated.


PowerBIActions UpdateParameters returns InvalidRequest

We've been working on implementing the UpdateParameters task and it returns InvalidRequest. So either we are configuring it incorrectly or there is a bug in it. Can anyone help?
Below you can see our yaml definition:
- task: PowerBIActions@5
    inputs:
      PowerBIServiceEndpoint: 'bcea-dp-svcPowerBI-dev'
      Action: 'UpdateParameters'
      WorkspaceName: '$(workspace_dev)'
      DatasetName: 'Value and Volume monitor'
      ParameterInput: "[{'name':'server_host_name', 'newValue':'adb1'}]"

When we run the task, we get the following after enabling system.debug=true and obfuscating the group and dataset ID.
Trying to update the dataset parameters
Getting Power BI Workspace properties; Payment Insights DEV
##[debug]1:55:36 PM - Get-PowerBIWorkspace begin processing with ParameterSet Name.
##[debug]1:55:36 PM - Cmdlet version: 1.0.896.0
##[debug]Request Uri: https://api.powerbi.com/v1.0/myorg/groups?$filter=tolower(name) eq 'payment insights dev'&$top=100
##[debug]Status Code: OK (200)
##[debug]1:55:36 PM - Get-PowerBIWorkspace end processing.
##[debug]Processed: ##vso[task.setvariable variable=PowerBIActions.WorkspaceId]<value-obfuscated>
##[debug]1:55:36 PM - Get-PowerBIAccessToken begin processing with ParameterSet __AllParameterSets.
##[debug]1:55:36 PM - Cmdlet version: 1.0.896.0
##[debug]1:55:36 PM - Get-PowerBIAccessToken end processing.
##[debug]Trying to invoke api: https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets
##[debug]GET https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets with 0-byte payload
##[debug]received -1-byte response of content type application/json; odata.metadata=minimal; odata.streaming=true
##[debug]Trying to find dataset 'Value and Volume monitor'
Processing dataset - Value and Volume monitor
##[debug]1:55:37 PM - Get-PowerBIAccessToken begin processing with ParameterSet __AllParameterSets.
##[debug]1:55:37 PM - Cmdlet version: 1.0.896.0
##[debug]1:55:37 PM - Get-PowerBIAccessToken end processing.
##[debug]Trying to invoke api: https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets/<value-obfuscated>/parameters
##[debug]GET https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets/<value-obfuscated>/parameters with 0-byte payload
##[debug]received -1-byte response of content type application/json; odata.metadata=minimal; odata.streaming=true
##[debug]1:55:37 PM - Get-PowerBIAccessToken begin processing with ParameterSet __AllParameterSets.
##[debug]1:55:37 PM - Cmdlet version: 1.0.896.0
##[debug]1:55:37 PM - Get-PowerBIAccessToken end processing.
##[debug]Trying to invoke api: https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets/<value-obfuscated>/Default.UpdateParameters
##[debug]POST https://api.powerbi.com/v1.0/myorg/groups/<value-obfuscated>/datasets/<value-obfuscated>/Default.UpdateParameters with -1-byte payload
Done processing Power BI Actions
##[debug]Caught exception from task script.
##[debug]Error record:
##[debug]Invoke-API : InvalidRequest
##[debug]At D:\a\_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.25\ps_modules\PowerBI\PowerBI.psm1:238 char:9
##[debug]+         Invoke-API -Url $url -Method "Post" -Body $body -ContentType  ...
##[debug]+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
##[debug]    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
##[debug]    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-API
##[debug]
##[debug]Script stack trace:
##[debug]at Invoke-API, D:\a\_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.25\ps_modules\PowerBI\PowerBI.psm1: line 307
##[debug]at Update-PowerBIDatasetParameter, D:\a\_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.25\ps_modules\PowerBI\PowerBI.psm1: line 238
##[debug]at Update-PowerBIDatasetParameters, D:\a\_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.25\ps_modules\PowerBI\PowerBI.psm1: line 261
##[debug]at <ScriptBlock><Process>, D:\a\_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.25\run.ps1: line 196
##[debug]at <ScriptBlock>, <No file>: line 1
##[debug]at <ScriptBlock>, <No file>: line 22
##[debug]at <ScriptBlock>, <No file>: line 18
##[debug]at <ScriptBlock>, <No file>: line 1
##[debug]Exception:
##[debug]Microsoft.PowerShell.Commands.WriteErrorException: InvalidRequest
##[error]InvalidRequest
##[debug]Processed: ##vso[task.logissue type=error]InvalidRequest
##[debug]Processed: ##vso[task.complete result=Failed]

If we take the same json payload and run on the PowerBI REST API documentation page, it succeeds with return code 200:
Link: https://docs.microsoft.com/en-us/rest/api/power-bi/datasets/update-parameters-in-group

And then the parameter is updated:

Hi,
The extension it self has some checks on existing parameters and then extends it. Could you tell me with what you are doing the action via the task en manually.
Besides that are you running on a hosted agent?

Hi,
Our flow looks like:

Upload the PowerBI report using the Publish action
Update existing parameters which can be empty or might have some values already. But the parameters are predefined on the dataset.

We are running on a hosted agent (windows-latest).

Is it done my a service principal or user account

We are using a service principal. We've followed the instructions from Azure docs to set it up: https://docs.microsoft.com/en-us/power-bi/admin/service-premium-service-principal

The test with what account did you perform that?

I used my own account to test from https://docs.microsoft.com/en-us/rest/api/power-bi/datasets/update-parameters-in-group

No, I haven't.
I'll give it a go and write back tomorrow.

I managed to run the code locally after a few edits in the scripts and now it fails at the step before doing the POST to Default.UpdateParameters. The GET on .../parameters fails with InvalidRequest.

@romosandarius I had the same issue and wanted to comment here to get an answer as well. But I figured it out in the meantime.
Two issues blocked it for me:

The Service Principal not having ownershop of the dataset,
The Parameter was a list value.

Providing Ownership of the datasets in the workspace to the service principal + changing the parameter to a text value without any lists behind it made it work for me.

@TimEllens, thank you for sharing the info! It actually worked as you suggested where I managed to update the parameters with the following two actions:
             - task: PowerBIActions@5                 displayName: 'Taking dataset ownership'                 inputs:                   PowerBIServiceEndpoint: 'bcea-dp-svcPowerBI-dev'                   Action: 'TakeOwnership'                   WorkspaceName: '$(workspace_dev)'                   DatasetName: 'Client Value and Volume'               - task: PowerBIActions@5                 displayName: 'Updating parameters for Client Value and Volumne'                 inputs:                   PowerBIServiceEndpoint: 'bcea-dp-svcPowerBI-dev'                   Action: 'UpdateParameters'                   WorkspaceName: '$(workspace_dev)'                   DatasetName: "Client Value and Volume"                   ParameterInput: "{'name':'server_host_name', 'newValue':'adb2'}"
The challenge is though that we have another ongoing issue where we need a normal Active Directory user (irrespective of MFA setup) to own the dataset, otherwise we're hit by the below error:

@maikvandergaag, do you have any ideas why we cannot update the parameters even though the service principal is Admin on the dataset's workspace?

Not sure, then we would have to dive deeper into your specific request. @mattias-de-coninck: do you have an idea

@romosandarius could you perhaps show us what the Show Details link points to?

@mattias-de-coninck , it points to the front page of the PowerBI service so there's no useful information, unfortunately.


Unable to implement MonthScrollListener in java

I have almost implemented it in java but having issue with the MonthScrollListener can u give an example for this. Only need help putting setMonthScrollListener not the inside code.

calendarView.setMonthScrollListener(new Function1<CalendarMonth, Unit>() {
in this line what is Unit and how to use it in java

Issue already resolved


<EMAIL_ADDRESS> Causes the Element-Plus button to have no color

button, [type='button'], [type='reset'], [type='submit'] {
-webkit-appearance: button;
background-color: transparent;
background-image: none;
}

You don't need the reset when using with component lib

@antfu without the reset, rings, active state, etc don't work. Is it possible to have a scoped reset?

@antfu without the reset, rings, active state, etc don't work. Is it possible to have a scoped reset?

Related to #2127, we will soon have in #2128. You can review or comment at #2128.


Update EFA, Nvidia Driver, NCCL and AWS-OFI-NCCL version

Should this be closed after PR #125 was merged?