feat: C++ Functions Framework example

FWIW, I tested the "deploy" button and it successfully created the image, though my project does not allow unauthenticated Cloud Run calls, so that failed.
/FYI: @devjgm

Cool. I'm not familiar with the world of C++ but it doesn't seem like our buildpacks support C++. Does this somehow use the .Net support?

Cool. I'm not familiar with the world of C++ but it doesn't seem like our buildpacks support C++.

There is explicit support for the C++ functions framework in the GCP buildpacks:
https://github.com/GoogleCloudPlatform/buildpacks/tree/main/cmd/cpp/functions_framework
https://github.com/GoogleCloudPlatform/buildpacks/tree/main/builders/testdata/cpp/functions/test_function

Oh cool! Just didn't see that documented yet :)

I got an error when trying to build this:
Downloaded sources for package boost-logic[core]:x64-linux
Elapsed time for package boost-logic:x64-linux: 996.2 ms
Starting package 64/74: boost-mp11:x64-linux
Building package boost-mp11[core]:x64-linux...
-- Downloading https://github.com/boostorg/mp11/archive/boost-1.76.0.tar.gz -> boostorg-mp11-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-mp11-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-mp11/src/ost-1.76.0-1ae0cc0b52.clean
CMake Error at ports/boost-mp11/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-mp11[core]:x64-linux
Elapsed time for package boost-mp11:x64-linux: 1.115 s
Starting package 65/74: boost-beast:x64-linux
Building package boost-beast[core]:x64-linux...
-- Downloading https://github.com/boostorg/beast/archive/boost-1.76.0.tar.gz -> boostorg-beast-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-beast-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-beast/src/ost-1.76.0-e8a2a4b32a.clean
CMake Error at ports/boost-beast/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-beast[core]:x64-linux
Elapsed time for package boost-beast:x64-linux: 1.237 s
Starting package 66/74: boost-foreach:x64-linux
Building package boost-foreach[core]:x64-linux...
-- Downloading https://github.com/boostorg/foreach/archive/boost-1.76.0.tar.gz -> boostorg-foreach-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-foreach-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-foreach/src/ost-1.76.0-805aa46795.clean
CMake Error at ports/boost-foreach/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-foreach[core]:x64-linux
Elapsed time for package boost-foreach:x64-linux: 682.5 ms
Starting package 67/74: boost-proto:x64-linux
Building package boost-proto[core]:x64-linux...
-- Downloading https://github.com/boostorg/proto/archive/boost-1.76.0.tar.gz -> boostorg-proto-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-proto-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-proto/src/ost-1.76.0-8dd4271590.clean
CMake Error at ports/boost-proto/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-proto[core]:x64-linux
Elapsed time for package boost-proto:x64-linux: 1.087 s
Starting package 68/74: boost-phoenix:x64-linux
Building package boost-phoenix[core]:x64-linux...
-- Downloading https://github.com/boostorg/phoenix/archive/boost-1.76.0.tar.gz -> boostorg-phoenix-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-phoenix-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-phoenix/src/ost-1.76.0-8c7cf1ccc5.clean
CMake Error at ports/boost-phoenix/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-phoenix[core]:x64-linux
Elapsed time for package boost-phoenix:x64-linux: 927.6 ms
Starting package 69/74: boost-program-options:x64-linux
Building package boost-program-options[core]:x64-linux...
-- Downloading https://github.com/boostorg/program_options/archive/boost-1.76.0.tar.gz -> boostorg-program_options-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-program_options-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-program-options/src/ost-1.76.0-56c682e6a5.clean
CMake Error at ports/boost-program-options/portfile.cmake:14 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-build/boost-modular-build.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-program-options[core]:x64-linux
Elapsed time for package boost-program-options:x64-linux: 888.4 ms
Starting package 70/74: boost-variant:x64-linux
Building package boost-variant[core]:x64-linux...
-- Downloading https://github.com/boostorg/variant/archive/boost-1.76.0.tar.gz -> boostorg-variant-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-variant-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-variant/src/ost-1.76.0-f1f81b9f70.clean
CMake Error at ports/boost-variant/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-variant[core]:x64-linux
Elapsed time for package boost-variant:x64-linux: 1.232 s
Starting package 71/74: boost-spirit:x64-linux
Building package boost-spirit[core]:x64-linux...
-- Downloading https://github.com/boostorg/spirit/archive/boost-1.76.0.tar.gz -> boostorg-spirit-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-spirit-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-spirit/src/ost-1.76.0-2e27ba2c5b.clean
CMake Error at ports/boost-spirit/portfile.cmake:11 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-vcpkg-helpers/boost-modular-headers.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-spirit[core]:x64-linux
Elapsed time for package boost-spirit:x64-linux: 1.41 s
Starting package 72/74: boost-serialization:x64-linux
Building package boost-serialization[core]:x64-linux...
-- Downloading https://github.com/boostorg/serialization/archive/boost-1.76.0.tar.gz -> boostorg-serialization-boost-1.76.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-serialization-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-serialization/src/ost-1.76.0-bb7021b407.clean
CMake Error at ports/boost-serialization/portfile.cmake:14 (include):
  include could not find requested file:

    /layers/google.cpp.functions-framework/vcpkg/installed/x64-linux/share/boost-build/boost-modular-build.cmake
Call Stack (most recent call first):
  scripts/ports.cmake:140 (include)

Downloaded sources for package boost-serialization[core]:x64-linux
Elapsed time for package boost-serialization:x64-linux: 1.327 s
Starting package 73/74: nlohmann-json:x64-linux
Building package nlohmann-json[core]:x64-linux...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/CMakeLists.txt -> nlohmann-json-v3.9.1/CMakeLists.txt...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/LICENSE.MIT -> nlohmann-json-v3.9.1/LICENSE.MIT...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/nlohmann_json.natvis -> nlohmann-json-v3.9.1/nlohmann_json.natvis...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/config.cmake.in -> nlohmann-json-v3.9.1/cmake/config.cmake.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/pkg-config.pc.in -> nlohmann-json-v3.9.1/cmake/pkg-config.pc.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in -> nlohmann-json-v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in...
-- Downloading https://github.com/nlohmann/json/releases/download/v3.9.1/include.zip -> nlohmann-json-v3.9.1-include.zip...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/nlohmann-json-v3.9.1-include.zip
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/nlohmann-json/3.9.1-74ced61d52.clean
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
  This command cannot be executed in Download Mode.

  Halting portfile execution.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:369 (vcpkg_execute_required_process)
  ports/nlohmann-json/portfile.cmake:37 (vcpkg_configure_cmake)
  scripts/ports.cmake:140 (include)

Downloaded sources for package nlohmann-json[core]:x64-linux
Elapsed time for package nlohmann-json:x64-linux: 9.537 s
Starting package 74/74: functions-framework-cpp:x64-linux
Building package functions-framework-cpp[core]:x64-linux...
-- Downloading https://github.com/GoogleCloudPlatform/functions-framework-cpp/archive/v0.6.0.tar.gz -> GoogleCloudPlatform-functions-framework-cpp-v0.6.0.tar.gz...
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/GoogleCloudPlatform-functions-framework-cpp-v0.6.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/functions-framework-cpp/src/v0.6.0-de540fa2f8.clean
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
  This command cannot be executed in Download Mode.

  Halting portfile execution.

 (3m46.557505848s)
--------------------------------------------------------------------------------
Running "/layers/google.cpp.functions-framework/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/bin/cmake -GNinja -DMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=g++-8 -DCMAKE_C_COMPILER=gcc-8 -DCMAKE_MAKE_PROGRAM=/layers/google.cpp.functions-framework/vcpkg/downloads/tools/ninja-1.10.2-linux/ninja -S /layers/google.cpp.functions-framework/main -B /layers/google.cpp.functions-framework/build -DCNB_APP_DIR=/workspace -DCMAKE_INSTALL_PREFIX=/layers/google.cpp.functions-framework/cpp -DVCPKG_TARGET_TRIPLET=x64-linux-nodebug -DCMAKE_TOOLCHAIN_FILE=/layers/google.cpp.functions-framework/vcpkg/scripts/buildsystems/vcpkg.cmake (VCPKG_DEFAULT_BINARY_CACHE=/layers/google.cpp.functions-framework/vcpkg-binary-cache)"
-- Running vcpkg install
Detecting compiler hash for triplet x64-linux-nodebug...
Detecting compiler hash for triplet x64-linux...
The following packages will be built and installed:
  * abseil[core]:x64-linux-nodebug -> 20210324.2
  * boost-algorithm[core]:x64-linux-nodebug -> 1.76.0
  * boost-align[core]:x64-linux-nodebug -> 1.76.0
  * boost-any[core]:x64-linux-nodebug -> 1.76.0
  * boost-array[core]:x64-linux-nodebug -> 1.76.0
  * boost-asio[core]:x64-linux-nodebug -> 1.76.0
  * boost-assert[core]:x64-linux-nodebug -> 1.76.0
  * boost-atomic[core]:x64-linux-nodebug -> 1.76.0
  * boost-beast[core]:x64-linux-nodebug -> 1.76.0
  * boost-bind[core]:x64-linux-nodebug -> 1.76.0
  * boost-build[core]:x64-linux -> 1.75.0
  * boost-chrono[core]:x64-linux-nodebug -> 1.76.0
  * boost-concept-check[core]:x64-linux-nodebug -> 1.76.0
  * boost-config[core]:x64-linux-nodebug -> 1.76.0
  * boost-container[core]:x64-linux-nodebug -> 1.76.0
  * boost-container-hash[core]:x64-linux-nodebug -> 1.76.0
  * boost-context[core]:x64-linux-nodebug -> 1.76.0
  * boost-conversion[core]:x64-linux-nodebug -> 1.76.0
  * boost-core[core]:x64-linux-nodebug -> 1.76.0
  * boost-coroutine[core]:x64-linux-nodebug -> 1.76.0
  * boost-date-time[core]:x64-linux-nodebug -> 1.76.0
  * boost-detail[core]:x64-linux-nodebug -> 1.76.0
  * boost-endian[core]:x64-linux-nodebug -> 1.76.0
  * boost-exception[core]:x64-linux-nodebug -> 1.76.0
  * boost-foreach[core]:x64-linux-nodebug -> 1.76.0
  * boost-function[core]:x64-linux-nodebug -> 1.76.0
  * boost-function-types[core]:x64-linux-nodebug -> 1.76.0
  * boost-functional[core]:x64-linux-nodebug -> 1.76.0
  * boost-fusion[core]:x64-linux-nodebug -> 1.76.0
  * boost-integer[core]:x64-linux-nodebug -> 1.76.0
  * boost-intrusive[core]:x64-linux-nodebug -> 1.76.0
  * boost-io[core]:x64-linux-nodebug -> 1.76.0
  * boost-iterator[core]:x64-linux-nodebug -> 1.76.0
  * boost-lambda[core]:x64-linux-nodebug -> 1.76.0
  * boost-lexical-cast[core]:x64-linux-nodebug -> 1.76.0
  * boost-logic[core]:x64-linux-nodebug -> 1.76.0
  * boost-math[core]:x64-linux-nodebug -> 1.76.0
  * boost-modular-build-helper[core]:x64-linux -> 1.76.0#1
  * boost-move[core]:x64-linux-nodebug -> 1.76.0
  * boost-mp11[core]:x64-linux-nodebug -> 1.76.0
  * boost-mpl[core]:x64-linux-nodebug -> 1.76.0
  * boost-numeric-conversion[core]:x64-linux-nodebug -> 1.76.0
  * boost-optional[core]:x64-linux-nodebug -> 1.76.0
  * boost-phoenix[core]:x64-linux-nodebug -> 1.76.0
  * boost-pool[core]:x64-linux-nodebug -> 1.76.0
  * boost-predef[core]:x64-linux-nodebug -> 1.76.0
  * boost-preprocessor[core]:x64-linux-nodebug -> 1.76.0
  * boost-program-options[core]:x64-linux-nodebug -> 1.76.0
  * boost-proto[core]:x64-linux-nodebug -> 1.76.0
  * boost-range[core]:x64-linux-nodebug -> 1.76.0
  * boost-ratio[core]:x64-linux-nodebug -> 1.76.0
  * boost-rational[core]:x64-linux-nodebug -> 1.76.0
  * boost-regex[core]:x64-linux-nodebug -> 1.76.0
  * boost-serialization[core]:x64-linux-nodebug -> 1.76.0
  * boost-smart-ptr[core]:x64-linux-nodebug -> 1.76.0
  * boost-spirit[core]:x64-linux-nodebug -> 1.76.0
  * boost-static-assert[core]:x64-linux-nodebug -> 1.76.0
  * boost-system[core]:x64-linux-nodebug -> 1.76.0
  * boost-thread[core]:x64-linux-nodebug -> 1.76.0
  * boost-throw-exception[core]:x64-linux-nodebug -> 1.76.0
  * boost-tokenizer[core]:x64-linux-nodebug -> 1.76.0
  * boost-tuple[core]:x64-linux-nodebug -> 1.76.0
  * boost-type-index[core]:x64-linux-nodebug -> 1.76.0
  * boost-type-traits[core]:x64-linux-nodebug -> 1.76.0
  * boost-typeof[core]:x64-linux-nodebug -> 1.76.0
  * boost-uninstall[core]:x64-linux-nodebug -> 1.75.0#1
  * boost-uninstall[core]:x64-linux -> 1.75.0#1
  * boost-unordered[core]:x64-linux-nodebug -> 1.76.0
  * boost-utility[core]:x64-linux-nodebug -> 1.76.0
  * boost-variant[core]:x64-linux-nodebug -> 1.76.0
  * boost-vcpkg-helpers[core]:x64-linux-nodebug -> 7#2
  * boost-winapi[core]:x64-linux-nodebug -> 1.76.0
    functions-framework-cpp[core]:x64-linux-nodebug -> 0.6.0
  * nlohmann-json[core]:x64-linux-nodebug -> 3.9.1
  * openssl[core]:x64-linux-nodebug -> 1.1.1l
Additional packages (*) will be modified to complete this operation.

-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/CMakeLists.txt -> nlohmann-json-v3.9.1/CMakeLists.txt...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/LICENSE.MIT -> nlohmann-json-v3.9.1/LICENSE.MIT...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/nlohmann_json.natvis -> nlohmann-json-v3.9.1/nlohmann_json.natvis...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/config.cmake.in -> nlohmann-json-v3.9.1/cmake/config.cmake.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/pkg-config.pc.in -> nlohmann-json-v3.9.1/cmake/pkg-config.pc.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in -> nlohmann-json-v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in...
-- Downloading https://github.com/nlohmann/json/releases/download/v3.9.1/include.zip -> nlohmann-json-v3.9.1-include.zip...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/nlohmann-json/3.9.1-74ced61d52.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/nlohmann-json-v3.9.1-include.zip
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/nlohmann-json/3.9.1-74ced61d52.clean
-- Configuring x64-linux-nodebug-rel
-- Building x64-linux-nodebug-rel
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/nlohmann-json_x64-linux-nodebug/share/nlohmann-json/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/eb/eb3f1a010d5758a6884c69cb07e06627998d9b504dc89d58ab85240bc801aa8f.zip
Building package nlohmann-json[core]:x64-linux-nodebug... done
Installing package nlohmann-json[core]:x64-linux-nodebug...
Installing package nlohmann-json[core]:x64-linux-nodebug... done
Elapsed time for package nlohmann-json:x64-linux-nodebug: 450.6 ms
Starting package 2/75: boost-uninstall:x64-linux-nodebug
Building package boost-uninstall[core]:x64-linux-nodebug...
--
Please use the following command when you need to remove all boost ports/components:
    "./vcpkg remove boost-uninstall:x64-linux-nodebug --recurse"

-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/57/573fd3a753228465a36efcb5de84e419671ba4cea29dbaa9789cb924fba09726.zip
Building package boost-uninstall[core]:x64-linux-nodebug... done
Installing package boost-uninstall[core]:x64-linux-nodebug...
Installing package boost-uninstall[core]:x64-linux-nodebug... done
Elapsed time for package boost-uninstall:x64-linux-nodebug: 29.59 ms
Starting package 3/75: boost-vcpkg-helpers:x64-linux-nodebug
Building package boost-vcpkg-helpers[core]:x64-linux-nodebug...
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/11/11360bc79519b19abd2dec8e6b79a9891baf9398f136244af7c601fae381943e.zip
Building package boost-vcpkg-helpers[core]:x64-linux-nodebug... done
Installing package boost-vcpkg-helpers[core]:x64-linux-nodebug...
Installing package boost-vcpkg-helpers[core]:x64-linux-nodebug... done
Elapsed time for package boost-vcpkg-helpers:x64-linux-nodebug: 26.85 ms
Starting package 4/75: boost-preprocessor:x64-linux-nodebug
Building package boost-preprocessor[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/preprocessor/archive/boost-1.76.0.tar.gz -> boostorg-preprocessor-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-preprocessor/src/ost-1.76.0-8bf83e94ba.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-preprocessor-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-preprocessor/src/ost-1.76.0-8bf83e94ba.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-preprocessor_x64-linux-nodebug/share/boost-preprocessor/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-preprocessor_x64-linux-nodebug/share/boost-preprocessor/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/1c/1cf0f65693354ba920614f1acb08c5cdd6b906f9f43f9adbefa050f6c4cf9c7e.zip
Building package boost-preprocessor[core]:x64-linux-nodebug... done
Installing package boost-preprocessor[core]:x64-linux-nodebug...
Installing package boost-preprocessor[core]:x64-linux-nodebug... done
Elapsed time for package boost-preprocessor:x64-linux-nodebug: 392.9 ms
Starting package 5/75: boost-config:x64-linux-nodebug
Building package boost-config[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/config/archive/boost-1.76.0.tar.gz -> boostorg-config-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-config/src/ost-1.76.0-c5d6f64586.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-config-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-config/src/ost-1.76.0-c5d6f64586.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-config_x64-linux-nodebug/share/boost-config/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-config_x64-linux-nodebug/share/boost-config/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/bd/bd3ed559b4be580cdf9b92a73ba5f35ffc77ff3e58a5f977d74dd7788ddbbbb2.zip
Building package boost-config[core]:x64-linux-nodebug... done
Installing package boost-config[core]:x64-linux-nodebug...
Installing package boost-config[core]:x64-linux-nodebug... done
Elapsed time for package boost-config:x64-linux-nodebug: 197.6 ms
Starting package 6/75: boost-detail:x64-linux-nodebug
Building package boost-detail[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/detail/archive/boost-1.76.0.tar.gz -> boostorg-detail-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-detail/src/ost-1.76.0-1c74e313c4.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-detail-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-detail/src/ost-1.76.0-1c74e313c4.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-detail_x64-linux-nodebug/share/boost-detail/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-detail_x64-linux-nodebug/share/boost-detail/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/38/384b9fe37d35db26378e6ac1fd14fdffea92a923ce14116cadbcf99ffce54995.zip
Building package boost-detail[core]:x64-linux-nodebug... done
Installing package boost-detail[core]:x64-linux-nodebug...
Installing package boost-detail[core]:x64-linux-nodebug... done
Elapsed time for package boost-detail:x64-linux-nodebug: 55.24 ms
Starting package 7/75: boost-static-assert:x64-linux-nodebug
Building package boost-static-assert[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/static_assert/archive/boost-1.76.0.tar.gz -> boostorg-static_assert-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-static-assert/src/ost-1.76.0-62256f0e2f.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-static_assert-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-static-assert/src/ost-1.76.0-62256f0e2f.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-static-assert_x64-linux-nodebug/share/boost-static-assert/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-static-assert_x64-linux-nodebug/share/boost-static-assert/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/21/213ddd94c947a2ca4cd0ce3dd1f1e0daef2403d02c369ec899954562f5a75e55.zip
Building package boost-static-assert[core]:x64-linux-nodebug... done
Installing package boost-static-assert[core]:x64-linux-nodebug...
Installing package boost-static-assert[core]:x64-linux-nodebug... done
Elapsed time for package boost-static-assert:x64-linux-nodebug: 40.77 ms
Starting package 8/75: boost-type-traits:x64-linux-nodebug
Building package boost-type-traits[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/type_traits/archive/boost-1.76.0.tar.gz -> boostorg-type_traits-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-type-traits/src/ost-1.76.0-1e20915b2e.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-type_traits-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-type-traits/src/ost-1.76.0-1e20915b2e.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-type-traits_x64-linux-nodebug/share/boost-type-traits/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-type-traits_x64-linux-nodebug/share/boost-type-traits/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/b1/b1708915d5a0a26a7c6913d2c082ac595599050d1619bbadea1b73cdd519ad25.zip
Building package boost-type-traits[core]:x64-linux-nodebug... done
Installing package boost-type-traits[core]:x64-linux-nodebug...
Installing package boost-type-traits[core]:x64-linux-nodebug... done
Elapsed time for package boost-type-traits:x64-linux-nodebug: 173.8 ms
Starting package 9/75: boost-assert:x64-linux-nodebug
Building package boost-assert[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/assert/archive/boost-1.76.0.tar.gz -> boostorg-assert-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-assert/src/ost-1.76.0-3660031126.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-assert-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-assert/src/ost-1.76.0-3660031126.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-assert_x64-linux-nodebug/share/boost-assert/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-assert_x64-linux-nodebug/share/boost-assert/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/84/8407d5aab65094aa259b4980ca955080cb2587b5250e8a57f3845af899b77679.zip
Building package boost-assert[core]:x64-linux-nodebug... done
Installing package boost-assert[core]:x64-linux-nodebug...
Installing package boost-assert[core]:x64-linux-nodebug... done
Elapsed time for package boost-assert:x64-linux-nodebug: 42.29 ms
Starting package 10/75: boost-throw-exception:x64-linux-nodebug
Building package boost-throw-exception[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/throw_exception/archive/boost-1.76.0.tar.gz -> boostorg-throw_exception-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-throw-exception/src/ost-1.76.0-bf1d723805.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-throw_exception-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-throw-exception/src/ost-1.76.0-bf1d723805.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-throw-exception_x64-linux-nodebug/share/boost-throw-exception/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-throw-exception_x64-linux-nodebug/share/boost-throw-exception/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/05/05e3556fb29b926a824b8c9445f6f2da0e7b7890dc9c0c6d7d5b5e0d7ba4a9fd.zip
Building package boost-throw-exception[core]:x64-linux-nodebug... done
Installing package boost-throw-exception[core]:x64-linux-nodebug...
Installing package boost-throw-exception[core]:x64-linux-nodebug... done
Elapsed time for package boost-throw-exception:x64-linux-nodebug: 43.03 ms
Starting package 11/75: boost-io:x64-linux-nodebug
Building package boost-io[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/io/archive/boost-1.76.0.tar.gz -> boostorg-io-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-io/src/ost-1.76.0-6c61f76e7e.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-io-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-io/src/ost-1.76.0-6c61f76e7e.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-io_x64-linux-nodebug/share/boost-io/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-io_x64-linux-nodebug/share/boost-io/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/ba/bad124d01a72f999c66d31d3671cb55ce98a3ee4809db7b6738eef4ebab720c5.zip
Building package boost-io[core]:x64-linux-nodebug... done
Installing package boost-io[core]:x64-linux-nodebug...
Installing package boost-io[core]:x64-linux-nodebug... done
Elapsed time for package boost-io:x64-linux-nodebug: 43.63 ms
Starting package 12/75: boost-core:x64-linux-nodebug
Building package boost-core[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/core/archive/boost-1.76.0.tar.gz -> boostorg-core-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-core/src/ost-1.76.0-d69dc12516.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-core-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-core/src/ost-1.76.0-d69dc12516.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-core_x64-linux-nodebug/share/boost-core/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-core_x64-linux-nodebug/share/boost-core/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/d4/d4641d154f83e6c4648adf7f74217856a43b21bb9807579cbc6eab0fab961556.zip
Building package boost-core[core]:x64-linux-nodebug... done
Installing package boost-core[core]:x64-linux-nodebug...
Installing package boost-core[core]:x64-linux-nodebug... done
Elapsed time for package boost-core:x64-linux-nodebug: 74.93 ms
Starting package 13/75: boost-integer:x64-linux-nodebug
Building package boost-integer[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/integer/archive/boost-1.76.0.tar.gz -> boostorg-integer-boost-1.76.0.tar.gz...
-- Cleaning sources at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-integer/src/ost-1.76.0-4b34786212.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-integer-boost-1.76.0.tar.gz
-- Using source at /layers/google.cpp.functions-framework/vcpkg/buildtrees/boost-integer/src/ost-1.76.0-4b34786212.clean
-- Packaging headers
-- Packaging headers done
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.74.0/LICENSE_1_0.txt -> boost_LICENSE_1_0.txt...
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-integer_x64-linux-nodebug/share/boost-integer/usage
-- Installing: /layers/google.cpp.functions-framework/vcpkg/packages/boost-integer_x64-linux-nodebug/share/boost-integer/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /layers/google.cpp.functions-framework/vcpkg-binary-cache/e6/e648d848246c386aab554182b1fd886ef27108d094bec46ddd42652ee0f82187.zip
Building package boost-integer[core]:x64-linux-nodebug... done
Installing package boost-integer[core]:x64-linux-nodebug...
Installing package boost-integer[core]:x64-linux-nodebug... done
Elapsed time for package boost-integer:x64-linux-nodebug: 49.65 ms
Starting package 14/75: boost-container-hash:x64-linux-nodebug
Building package boost-container-hash[core]:x64-linux-nodebug...
-- Downloading https://github.com/boostorg/container_hash/archive/boost-1.76.0.tar.gz -> boostorg-container_hash-boost-1.76.0.tar.gz...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] popen(curl --fail -L https://github.com/boostorg/container_hash/archive/boost-1.76.0.tar.gz --create-dirs --output /layers/google.cpp.functions-framework/vcpkg/downloads/boostorg-container_hash-boost-1.76.0.tar.gz.1944.part 2>&1)
[DEBUG] cmd_execute_and_stream_data() returned 1792 after 130848305 us
Error: Failed to download from mirror set:
https://github.com/boostorg/container_hash/archive/boost-1.76.0.tar.gz:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:02:10 --:--:--     0curl: (7) Failed to connect to github.com port 443: Connection timed out

[DEBUG] /layers/google.cpp.functions-framework/vcpkg/buildtrees/_vcpkg/src/vcpkg-tool-2021-08-12/src/vcpkg/base/downloads.cpp(626)
[DEBUG] Exiting after 130849854 us (130848590 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:83 (message):

      Failed to download file with error: 1
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:274 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:173 (vcpkg_download_distfile)
  ports/boost-container-hash/portfile.cmake:3 (vcpkg_from_github)
  scripts/ports.cmake:140 (include)

Error: Building package boost-container-hash:x64-linux-nodebug failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-container-hash:x64-linux-nodebug
  Vcpkg version: 2021-08-12-unknownhash

Additionally, attach any relevant sections from the log files above.
-- Running vcpkg install - failed
CMake Error at /layers/google.cpp.functions-framework/vcpkg/scripts/buildsystems/vcpkg.cmake:827 (message):
  vcpkg install failed.  See logs for more information:
  /layers/google.cpp.functions-framework/build/vcpkg-manifest-install.log
Call Stack (most recent call first):
  /layers/google.cpp.functions-framework/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeDetermineSystem.cmake:124 (include)
  CMakeLists.txt:17 (project)

-- Configuring incomplete, errors occurred!
Done "/layers/google.cpp.functions-framework/vcpkg/downloads/tools..." (2m14.127235272s)
Failure: (ID: c7e26906) ...:02:10 --:--:--     0curl: (7) Failed to connect to github.com port 443: Connection timed out

[DEBUG] /layers/google.cpp.functions-framework/vcpkg/buildtrees/_vcpkg/src/vcpkg-tool-2021-08-12/src/vcpkg/base/downloads.cpp(626)
[DEBUG] Exiting after 130849854 us (130848590 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:83 (message):

      Failed to download file with error: 1
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:274 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:173 (vcpkg_download_distfile)
  ports/boost-container-hash/portfile.cmake:3 (vcpkg_from_github)
  scripts/ports.cmake:140 (include)

Error: Building package boost-container-hash:x64-linux-nodebug failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-container-hash:x64-linux-nodebug
  Vcpkg version: 2021-08-12-unknownhash

Additionally, attach any relevant sections from the log files above.
-- Running vcpkg install - failed
CMake Error at /layers/google.cpp.functions-framework/vcpkg/scripts/buildsystems/vcpkg.cmake:827 (message):
  vcpkg install failed.  See logs for more information:
  /layers/google.cpp.functions-framework/build/vcpkg-manifest-install.log
Call Stack (most recent call first):
  /layers/google.cpp.functions-framework/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeDetermineSystem.cmake:124 (include)
  CMakeLists.txt:17 (project)

-- Configuring incomplete, errors occurred!
--------------------------------------------------------------------------------
Sorry your project couldn't be built.
Our documentation explains ways to configure Buildpacks to better recognise your project:
 -> https://github.com/GoogleCloudPlatform/buildpacks/blob/main/README.md
If you think you've found an issue, please report it:
 -> https://github.com/GoogleCloudPlatform/buildpacks/issues/new
--------------------------------------------------------------------------------
ERROR: failed to build: executing lifecycle: failed with status code: 145

Looks like maybe this was transient.  I'll try again.

worked on second try.

Thanks!  If there are other places where you think it would be useful to advertise the C++ functions framework and support in the builder please do let me know, I want to close those gaps too.


Huge tree

Short description explaining the high-level reason for the pull request
Changes
The import_xml command now constructs a parser with the huge_tree=True argument in order to be able to load large files such as those that come from Reg Z. This addresses issue #37.
Also, timeline.html is changed to display the correct timeline in landing mode.
Testing
Try loading a regulation instance from Reg Z; it should succeed without reporting that the tree is too large.
Review

@chosak

Preview this PR without the whitespace changes
Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Ok, wow, I had never seen markers like that. That's actually a mistake, which I will now investigate. Markers should never have such a form, which leads me to think something went wrong there.

Yeah, I tracked it down to a broken copy/paste in an earlier notice. I'll fix the source. Markers should never be over 25, as they're basically either of the form (x) or x. (with the x being at most a few characters).


Change this on new update

currently loop method has integer right so it hard to understand so i suggest
disableloop = loop: 'none'
trackloop = loop: 'track'
queueloop loop: 'queue'
change integer and add it string option

0 = none
1 = track
2 = queue
isn't hard to understand
Also integer take less ram compare to string

Ok


Creating and Saving Multiple HTML Files

Everytime I create a new InteractiveHTMLBom it replaces the previous html file with the new one. How can I get it so the name of the html file created is different so I can save multiple boards as htmls?

You can accomplish that with the command line argument --name-format (wiki documentation)


rc3 broken for tags with hyphen

New error with rc3:
Error: tag validation failed: tag may only include the following characters: abcdefghijklmnopqrstuvwxyz0123456789_
Seems like there was some tag validation added to rc3 (or possibly rc2 - I'm not sure I had a successful run of this project on rc2) that is breaking any tags I try to add that contain -. In previous versions, this worked fine and in proxmox, tags with - work fine as well. Can the allowed characters for tags be expanded to include -?

Seems like this may have actually been introduced in rc2. The error seems to come from here I think https://github.com/Telmate/terraform-provider-proxmox/pull/1007/files#diff-d218b4c62dacc2f3bc02d11e0e732aa1cf57acc61262d17aef194629e36d0d78R43

@cmmarslender created the issue upstream in the Proxmox SDK https://github.com/Telmate/proxmox-api-go/issues/340

Fixed in main


Lock checkoutComplete, create order from adyen notification

refactor checkoutComplete mutation
extract whole checkoutComplete logic to separate file
use checkout_complete logic to create order from Adyen notification
apply lock for handling the adyen notifciation and mutation checkoutComplete

Are the schema changes intentional?

Are the schema changes intentional?
@patrys , I didn't add any changes for schema. Not sure why it raises the error. I assume that I need to update my branch with master

13 new database queries, that's a lot.

13 new database queries, that's a lot.

@patrys, I will doube check them

@patrys About the number of queries. After I've updated the benchmark tests, master has 145 queries for checkout complete. Here we have 119
test name                             left count      right count     duplicate count
complete checkout                                 145             119                  25

@korycins Was this branch rebased after the test change that increased the number of queries on master? Trying to make sure we're not comparing apples to oranges here.

@patrys Yes. I did that to get the current number of queries. - commit 3b9cafa


Type of colors is Generic thus autocomplete does not work

https://github.com/gregberge/xstyled/blob/b4ef5494b98bc1db93e2ebf630c398ecb95075a7/packages/system/src/defaultTheme.ts#L319
The typeof colors being Record<string, string> does not trigger the autocomplete for properties that rely on it (color, bg etc).
I will send a PR soon to improve this, so, I'm just creating this ticket to document it here. :)

In fact the return type of generateHexAlphaVariants is where the type of colors object is changed.
Maybe we can infer its type to get the right return.

In fact the return type of generateHexAlphaVariants is where the type of colors object is changed.
Maybe we can infer its type to get the right return.

Alright, I think I got it:

Alright, I think I got it:

Just to document here: https://github.com/formium/tsdx/issues/952
The current tsdx version uses ts v3, and I had to use the template literal to achieve the right type as shown before.
Template literal is available on ts v4.1, so I had to add a resolutions field on pkg.json as follows:
  "resolutions": {
    "**/typescript": "^4.1.3"
  }

Just to document here: https://github.com/formium/tsdx/issues/952
The current tsdx version uses ts v3, and I had to use the template literal to achieve the right type as shown before.
Template literal is available on ts v4.1, so I had to add a resolutions field on pkg.json as follows:
  "resolutions": {
    "**/typescript": "^4.1.3"
  }

I'm with an issue of the size of the type being generated by ts being too large.
Let's see if I can fix that in some way >_<.

I'm with an issue of the size of the type being generated by ts being too large.
Let's see if I can fix that in some way >_<.

It seems that the d.ts generated after build is already invalid on emotion/x.d.ts.

(Sorry for spamming here, I just want to keep the development in sync)

It seems that the d.ts generated after build is already invalid on emotion/x.d.ts.

(Sorry for spamming here, I just want to keep the development in sync)

Fixed in #174

Fixed in #174


Feature: Update to use SurrealDB 2.0

Is your feature request related to a problem?
Not current
Describe the solution
Update it
Alternative methods
None
SurrealDB version
na
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

@nickchomey it seems to be done here: https://github.com/surrealdb/surrealdb.wasm/compare/v1.0.0-beta.19...v1.0.0-beta.20
But I still wonder where the stable versions (1.0.0) of surrealdb, @surrealdb/node and @surrealdb/wasm are.

For context, the latest pre release is used in Surrealist 3.0, however we intend to stabilize this SDK as well as other SDKs this coming week 🙂


Update unicode-standard.md

The Low Surrogate of character(𓅡) is U+DD61 instead of U+DC61.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

globalization/encoding/unicode-standard.md
76
59
78
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

@DevinJohw -- Good catch! Thank you!


virtcontainers: inherit parent's CPU constraint

Don't set a default CPU constraint if period and quota are not specified, that
way the container will inherit the CPU constraint from its parent. Container
creation won't fail if the parent CPU constraint is smaller than the default
number of vCPUs.
fixes #1521
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

/test

@egernst @sboeuf  @bergwolf  please take a look ready to merge

cc @mocolic

@teawater Can you please also backport this to 1.6 stable since it has also been back ported to 1.5?
CC @mocolic

@egernst Can you please help with this as well?

@egernst @teawater Can you please help with port of this fix to stable 1.6? Service Fabric resource governance with Kata is broken without this change.


feat: adds output definition to config file

Coverage remained the same at 100.0% when pulling 6e01755feb7b063f91675069867d41cdb96afbe8 on config-output-def into df015afb29023e8d7d752f296923a9dd251ff763 on master.

#29


Wrong use Path2D fill

In src/tag/path.js
line 15 - if (fill) ctx.fill(); - this is wrong. For filling Path2D in method fill need pass current instance Path2D

Thanks for reporting, this is now fixed


[WIP] exit_sendmail: rework sendmail plugin to use information from koji

PDC part is removed, instead we'll use the following recepients:

If always_notify param is set it will be used an email address
If to_koji_submitter is set, the plugin will query Koji for kerberos
principal of the user, who initiated the task. The kerberos principal would be
used as an email address
If to_koji_pkgowner is set, the plugin will query Koji for build info
and include owners of the package-tags combinations in the notification

If no recepients are found, the plugin will send an error notification to people,
specified in error_addresses
TODO:

[x] Sort out submitter param - its best be renamed to always_notify or similar
[x] Add tests to cover exceptions when fetching koji submitter / package owner
[x] Introduce email_domain and construct email addresses if Koji instance doesn't use kerberos
Signed-off-by: Vadim Rutkovsky<EMAIL_ADDRESS>

+1

Marking this as WIP as at the moment Koji integration is broken, so I'll be pushing commits to make integration tests pass - and squash them when those are ready for review


Fix rare exception in webview on Android

Rendering some messages (very rarely, but consistently) throw an error on Android.

It seems the error happens when we send some html messages to the phone (when transitioning from 'loading' to 'some messages loaded' state).
When the messages already exist, they are rendered properly.

@borisyankov says this issue may be related to #2505 and #2558.

Fixed in 787c4a53b (from #2854) a couple of weeks ago, along with #2505 and #2558.


UnstructuredLoader from langchain-unstructured is not calling custom API URLs

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
loader = UnstructuredLoader(
        file_path=str(local_path),
        api_key=os.getenv('UNSTRUCTURED_API_KEY')
        url=os.getenv('UNSTRUCTURED_URL'),
    )
documents = loader.load()

Error Message and Stack Trace (if applicable)
ImportError: partition_md() is not available because one or more dependencies are not installed. Use: pip install "unstructured[md]" (including quotes) to install the required dependencies
Description
I am trying to harness the UnstructuredLoader from langchain-unstructured to call my unstructured container running locally. The UnstructuredLoader instead of calling my local API using the URL and API_KEY that I specify, it tries to use the unstructured library to execute the entire processing within the context of the app. I need the contents of the document to be parsed by unstructured-api container.
System Info
System Information

OS:  Darwin
OS Version:  Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
Python Version:  3.12.7 (main, Oct 10 2024, 14:19:49) [Clang 16.0.0 (clang-16<IP_ADDRESS>)]

Package Information

langchain_core: 0.3.14
langchain: 0.3.6
langchain_community: 0.3.4
langsmith: 0.1.138
langchain_aws: 0.2.5
langchain_experimental: 0.3.2
langchain_openai: 0.2.4
langchain_text_splitters: 0.3.1
langchain_unstructured: 0.1.5
langgraph: 0.2.41

Optional packages not installed

langserve

Other Dependencies

aiohttp: 3.10.10
async-timeout: Installed. No version info available.
boto3: 1.35.52
dataclasses-json: 0.6.7
httpx: 0.27.2
httpx-sse: 0.4.0
jsonpatch: 1.33
langgraph-checkpoint: 2.0.2
langgraph-sdk: 0.1.35
numpy: 1.26.4
openai: 1.53.0
orjson: 3.10.10
packaging: 24.1
pydantic: 2.9.2
pydantic-settings: 2.6.0
PyYAML: 6.0.2
requests: 2.32.3
requests-toolbelt: 1.0.0
SQLAlchemy: 2.0.36
tenacity: 8.5.0
tiktoken: 0.8.0
typing-extensions: 4.12.2
unstructured-client: 0.25.9
unstructured[all-docs]: Installed. No version info available

unstructured requires multiple dependent modules to be installed. please follow this documentation about installation: https://docs.unstructured.io/open-source/installation/full-installation


Spyder Dev Tools: Signal Tracer

From<EMAIL_ADDRESS>on 2011-12-13T06:40:11Z
What steps will reproduce the problem?

No way to debug how Qt signals really behave in Spyder
No way trace signals as they are fired in real-time What is the expected output? What do you see instead? While inspecting Spyder signals, static analysis (i.e. looking at the code) is time consuming and therefore doesn't always end successfully. It will be much more convenient to have a development widget that will serve as entrypoint for debugging signals and handlers.

I'm looking for something that will help me to track signals at run-time (dynamically) by listing all available signals, and help other people understand what's going on (intuitive visualization) by tracking in real-time when fired and handled.
This widget/API should allow:

get the list of all signals
get the list of all subscribes given signal name
receive notification when a new subscriber appears (and vanishes)
receive notification when a new signal type appears (and removes)
receive notification when a signal fires, in which order subscribers are called

Questions:

Does Qt/PySide provide some useful API?
Can subscriber cancel signal processing by further subscribers?

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=881

From pierre.raybaut on 2012-03-18T14:07:16Z
Labels: -Type-Enhancement Type-Enh

Closing as duplicate of #1421


⚠ AGEG website (redirect) has degraded performance

In c78012f, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2472 ms

Resolved: AGEG website (redirect) performance has improved in 3977e2e after 10 minutes.


fix: gradle component analsyis duplicates artifacts in sbom

Description
For gradle component analysis, if in manifest an artifact is specified twice, once with version and second time without version, then it's generated like that in the sbom , which is a duplicate ( the fix filtering out the artifact that doesn't contain version)
Checklist

[x] I have followed this repository's contributing guidelines.
[x] I will adhere to the project's code of conduct.

Additional information
build.gradle:
dependencies {
    implementation "log4j:log4j:1.2.17"
    implementation group: 'log4j', name: 'log4j'
}

generated sbom
{

     {
            "group": "log4j",
            "name": "log4j",
            "version": "1.2.17",
            "purl"<EMAIL_ADDRESS>            "type": "library",
            "bom-ref"<EMAIL_ADDRESS>       },
       {
            "group": "log4j",
            "name": "log4j",
            "purl": "pkg:maven/log4j/log4j",
            "type": "library",
            "bom-ref": "pkg:maven/log4j/log4j"
       }
}

the generated sbom for component analysis should only contain the log4j with the version, and with subjected fix it becomes as required:
{

     {
            "group": "log4j",
            "name": "log4j",
            "version": "1.2.17",
            "purl"<EMAIL_ADDRESS>            "type": "library",
            "bom-ref"<EMAIL_ADDRESS>       }
 }

skipped IT for golang and approve this PR , as they are temporary not working due to an issue in EXHORT Backend ( regardless of which packages are in the go.mod manifest ( vulnerable or not), exhort doesn't returns vulnerability data.


Authorizations are not applied correctly

First of all: I'm not sure if this is a problem with the app or with Paperless-ngx, but the permissions of the documents are not taken into account when they are displayed in the app.
If I log in with my normal user without admin rights, who should only have access to his documents, I am still shown documents that are explicitly assigned to only one other person as the owner. Everything is displayed correctly in the browser.
Is this a bug within the app or should I also open an issue with Paperless-ngx because the rights are apparently not assigned so robustly that the behavior can occur?
Addendum: The whole thing occurs under iOS 17.3.1, both under the last stable version and in the version currently published by TestFlight.
@shamoon: FYI

I wouldn't preclude the app not doing exactly the right thing, but at the end of the day, the API should not return documents that shouldn't be visible to logged in user, I would argue.
That being said, I have not thoroughly tested the app with multiple users and permissions, simply because I don't personally use these features.

Not imminently, but it is on my roadmap!

Closing this in favor of #45.


v5.0.1 does't support laravel 5.6.x

because laravel/helpers:^1.1.0 need "illuminate/support": "~5.8.0|^6.0|^7.0"

You can still use v4.x of this package!


pull request for e2e test at 02/04/2017 05:45:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: lnurl scheme parsing

Describe the changes you have made in this PR
In #2927, I noticed that links that start with lnurl open the Alby extension. This means that even links to content unrelated to lightning like lnurlpay_comments.mp4 open the Alby extension.
I looked up what schemes are meant to be parsed and I found LUD-17.
So I think only the following link prefixes should open the Alby extension:
lightning:, lnurlc:, lnurlw:, lnurlp:
Link this PR to an issue [optional]
Fixes #2927
Type of change

fix: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes [optional]

video
https://github.com/getAlby/lightning-browser-extension/assets/27162016/ad269ac5-994f-4a4a-a81c-4a91f2e104ce

How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[x] Self-review of changed code
[x] Manual testing
[ ] Added automated tests where applicable
[ ] Update Docs & Guides
For UI-related changes
[ ] Darkmode
[ ] Responsive layout

had a round of tests. LGTM cc @rolznz  the error is just because we use more generalised matcher which can cause such error with relative links having lnurl inlcuded in the link


Add files via upload

@JEBBandit First stage of verification passed, official domain is exe-coll.ac.uk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@JEBBandit Thank you for your patience while waiting for a review and processing your request. Pull request merged.

Great, thanks!


(clicked) not working with direction right

(clicked) doesn't seem to work with direction right

I too have experienced odd behaviour when [direction] is set to 'right'.

Notice that the item selected is always the third one with direction right


Implement a channel mode

default to a passive client mode (eventually server can instigate requests)
add a channel mode

n.b. I'm not getting server output in the client, not sure why...
cc @lexs

Not sure of the clean way to create CancellableSubscriberImpl

n.b. I'm not getting server output in the client, not sure why...

Actually CLI never sends a request-channel request to the server as the input source never ends (System.in). Here is the culprit:
https://github.com/ReactiveSocket/reactivesocket-cli/blob/master/src/main/java/io/reactivesocket/cli/ObservableIO.java#L37
I can send a PR to convert it into a live stream if you like!

@NiteshKant Thanks


helm and tls communication Error: remote error: tls: bad certificate

Output of helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Kubernetes Installation on Azure VMs (Not using AKS)
Issue:
I am getting below error while running helm ls
$ helm ls --tls
Error: remote error: tls: bad certificate

I have the issue resolved now. Due to caching and a running replica set tiller-pod would come back up with old certs. I got rid of all old tiller replica sets/services/deployments/pods and created new ones.
It is working fine now. Thanks!


fix: fix python versions

IPython is not supporting python 3.7

Yes, I think even 3.8 is close to losing support in some packages... Thanks

I happened to be reading the GitHub Actions log and noticed this, I think the step to set up poetry is too clever for this use case.
Probably better to check it some other way.
https://github.com/PRQL/pyprql/pull/164/checks#step:5:14
The currently activated Python version 3.7.16 is not supported by the project (^3.8).
Trying to find and use a compatible version.
Using python3.10 (3.10.6)
Creating virtualenv pyprql-2JuVSC4c-py3.10 in /home/runner/.cache/pypoetry/virtualenvs
Installing dependencies from lock file

Hmmm. I had tried to make it simple — it used to rely on nox.
I think we should only have that problem when it's an incompatible version, which is rare...
But ofc open to any changes!

BTW it's also fine to cut out the "middle" version if we want to reduce the testing burden. It's extremely unlikely that something would fail on 3.9 if it passes on 3.8 & 3.10...

BTW it's also fine to cut out the "middle" version if we want to reduce the testing burden. It's extremely unlikely that something would fail on 3.9 if it passes on 3.8 & 3.10...

Definitely!
Perhaps one number for the minimal version (e.g. 3.8) and something like 3.x will suffice.
https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#matrix-testing


More scalable Redis cache tags

This PR implements @oprypkhantc's solution for more performant / scalable cache tags when using Redis. Namely, it solves the problem of orphan reference keys in the cache which can accumulate to take up significant space and can't be purged efficiently.
This solution stores the list of keys for a given tag in a sorted set where the expiration time is the score. Then, references may be easily removed using that score + a scheduled command (scheduled command not included in this PR at the moment).
Have removed existing Redis cache tag tests which were heavily mocked and will be adding integration tests for this feature.

I'm not able to figure out why my testIncrementedTagEntriesProperlyTurnStale fails.
When I run the code locally on Redis 6.2.1 and use Predis, nothing is left in the Redis database after running that code. However, on phpredis on GitHub actions I'm getting this failure.
@oprypkhantc I added the GT stuff to increment and decrement to try to correct a behavior in your implementation where if a value was incremented it automatically essentially became a "forever" cached item in the sorted set with a score of -1, even if it was put originally with an expiration timestamp.

From what I can tell, it seems the GT flag is being totally ignored on phpredis, even on Redis 7 and the latest phpredis extension (5.3.7).

Created phpredis issue here: https://github.com/phpredis/phpredis/issues/2319

Switched to using NX flag in the mean time which does seem to be respected and still gives me the behavior I want from increment and decrement I believe.
/cc @oprypkhantc

NX should do the job just fine I think. We don't use cache increments/decrements with tags, so there are possibly other bugs with them too I haven't noticed, although I can't think of any.

Yes, all of them leave stale tags behind, unfortunately. Thankfully there's now proper implementation for Redis - which seems to be the most scalable solution (now that AWS has MemoryDB) either way.

@clemblanco in Memcached this wasn't as much of a concern because Memcached doesn't grow indefinitely. Once you reach your configured memory size it will start pruning entries based on last access time. Redis has no such mechanism (afaik) so it just grew indefinitely.

Command committed here: https://github.com/laravel/framework/commit/16e9f0e9e47bf00aa317568f2d6ee78bfb2afdd4


Georgia not updating

Georgia does not seem to have updated Friday or today.

It does not appear anything has updated in more than a week.

Thanks both, updates are back now.


Translated MoveToPoint and CoerceToDouble into ios code

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


stream: open files - if file opening fails then in some cases (zipped, cdf) usbLogger error messages are displayed

Affects version 0.3.4. Check later

Issue solved in 94e4e39244169006bb0419d0eb4b7fff9a0706d2
Was related to non-recognizable data formats.
Closing #58


Adding a filter for black&white(Grayscale)

Requested feature from a user to create a Grayscale image and keep that filter to be easy to use.
Reference to the article is attached below
https://medium.com/@samarth_agarwal/turn-images-to-grayscale-in-flutter-the-colorfiltered-widget-16de44cf8045

Can I be assigned with this?

Assigned for 3 days

I would like to work on this if its still pending

Go ahead @Atharv-Joshi

can you please tell me what is the name of the filter screen?
I cannot find it

image_view check that cause we have merged screens to make it more efficient. Also, there's a plugin used for that photofilters which is present in that I think. Want to move the black and white filters ahead so that anyone could select the important ones only and remove the unused filters present there.
https://pub.dev/packages/photofilters
Feel free to replace this code in case u want with custom filter code here

thanks !
will check it out


[Feature Modifier to see/hide node gains/losses

Hi. As the title says I would like to suggest a modifier (toggle or hold) to show/hide the bonuses you gain/lose by allocating a node on the tree.
I find it can get in the way if you just want to read the node.
See image or image2 as an example. If you just want to quickly read the node you're assaulted with a screen-full of other text.
Any thoughts on the idea?
((Also, the deep blue colors of node power is hard to distinguish. Maybe a change of hue?))

As of the next update, Ctrl+D will toggle the stat difference display.
Also, I've added an Options screen, and one of the options allows you to change the colour scheme of the node power display; you can choose from Red+Blue, Red+Green, Green+Blue.


First class functions

Codecov Report

Merging #189 into lablua will increase coverage by 0.3%.
The diff coverage is 98.44%.

Impacted Files
Coverage Δ

titan-compiler/global_upvalues.lua
92.06% <100%> (+0.26%)
:arrow_up:

titan-compiler/checker.lua
93.29% <100%> (+0.24%)
:arrow_up:

titan-compiler/coder.lua
89.19% <98.07%> (+0.7%)
:arrow_up:

titan-compiler/types.lua
85.91% <0%> (+1.4%)
:arrow_up:

Continue to review full report at Codecov.

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


Implement Client side paging feature

Implement client side paging similar to functionality in 2.x, but better :)
@cbsm1th  has started work on this feature

Pagination has been implemented for some time, closing.


Snippet Editor fails to open after closing any file tab

Version and Platform (required):

Binary Ninja Version: 3.1.3592-dev
OS: Windows
OS Version: 11
CPU Architecture: x64

Bug Description:
The Snippet Editor window will not open if any file tabs have been closed.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

Open any number of files for analysis
Close a file tab
Attempt to open the Snippet Editor
See error in log

Expected Behavior:
I expected Snippet Editor to open regardless of what tabs have been closed.
Screenshots:
If applicable, please add screenshots here to help explain your problem.
Additional Information:
After closing any tab and attempting to open Snippets, the following output can be seen in the log:
Traceback (most recent call last):
  File "C:\Users\<USER>\AppData\Roaming\Binary Ninja\plugins\snippets-master\__init__.py", line 707, in launchPlugin
    snippets.show()
RuntimeError: Internal C++ object (Snippets) already deleted.

Restarting Binary Ninja is required to open the Snippet Editor again.

This is a dupe but on another repo that I'm about to migrate it to. Appreciate the heads up, it's unfortunately a side effect of a change a while ago that made snippets non-modal which was nice to be able to flip back and forth but it wasn't designed for that and this is the side effect of it.


Add shortcut for tag reference #333

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues
#333

👍


Rework PostUpdate hooks

Codecov Report

Merging #18 (28e65b8) into master (2809119) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

:exclamation: Current head 28e65b8 differs from pull request most recent head c22600c. Consider uploading reports for the commit c22600c to get more accurate results

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
- Coverage   74.80%   74.69%   -0.12%
==========================================
  Files          17       17
  Lines         655      652       -3
==========================================
- Hits          490      487       -3
  Misses         87       87
  Partials       78       78

Flag
Coverage Δ

unittests
74.69% <100.00%> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/updater/updater.go
73.91% <100.00%> (-1.09%)
:arrow_down:

Continue to review full report at Codecov.

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


Show warning during transaction retries

Summary:

Add a retry log for non-gRPC errors
Change retry log level to warning
Fix build failing due to depending on unstable master branch of jabel plugin
Fix using verbose multi-line logs and printing a stacktrace

Details:
When the SDK is retrying a failed transaction, there is no logging by default to indicate there is an issue. With the default maxAttempts, that could mean up to almost a minute (~48s) could go by without any feedback to the user that something is wrong. They could increase the log levels to trace, but then the logs would become too verbose with request and response objects being printed.
It looks like the logs used to print at error level until very recently, most likely because they were too verbose due to using both a multi-line format and including a stacktrace. I think using multi-line logs should be avoided if at all possible as it's too verbose, harder to read logs next to it and difficult to parse by log collectors like Loki. Stacktrace should not be printed until the final attempt fails.

Changes look good, but this does require a rebase since I fixed the Jabel issues on master; I didn't realize you fixed it here as well.


[Replaced] Single-column login form design with OSF-themed style

PR replaced by https://github.com/CenterForOpenScience/osf-cas/pull/7

PR replaced and closed


SCOPE VALUE "CLOUDFRONT" only can use at us-east-1

CloudFormation reports error when creating stack:
Resource handler returned message: "Error reason: The scope is not valid., field: SCOPE_VALUE, parameter: CLOUDFRONT (Service: Wafv2, Status Code: 400, Request ID: xxxxxxxx-9735-4e3e-xxxxxx-a97f284xxxxxxxx)" (RequestToken: 9xxxxxxxxxx-7a78-1f06-0938-cxxxxxx54563, HandlerErrorCode: InvalidRequest)
Any help?
I use IAM user with admin AWS managed policy. The error is caused by creating WAF IPsets resource.

The reason is that due to the particularity of the global (CloudFront) resource
WAF IPsets can only be created in the US-east-1 Virginia region.


Adding additional Quartz.NET integration docs

Expanding documentation on how to connect MassTransit to an internal Quartz.NET instance.
As suggested here:
https://github.com/MassTransit/MassTransit/discussions/2873

Awesome, thank you. It would be cool to see the Quartz.NET configuration as well, much as you posted in your code and which packages it uses from NuGet to integrate with MSDI.
Thank yoU!


Deep copy of request in copy_current_request_context function?

Desiring a deep copy of session RequestContext data is present as a separate issue and pull request.  This issue is focused on desiring a deep copy of the request RequestContext data for use in a separate thread.  To pursue this, it is necessary to copy the environ data in a new function or the same copy_current_request_context function with a boolean argument to enable the deep copy.
Expected Behavior
For using a thread with a copy of a request, it is advantageous to have the functionality present in copy_current_request_context, though the request needs a deep copy instead of a shallow copy.  Based on the code comment of the RequestContext copy function, the intent of the function was a shallow copy, due to "Because the actual request object is the same this cannot be used to move a request context to a different thread unless access to the request object is locked.".
For having a copy of a request for a separate thread, I found it necessary to modify the flask.copy_current_request_context function to be:
def _copy_current_request_context(function):
    top = _request_ctx_stack.top
    if top is None:
        raise RuntimeError('This decorator can only be used at local scopes '
                           'when a request context is on the stack.  '
                           'For instance within view functions.')
    reqctx = top.copy()
    # environ is used by headers too, so only a copy of environ is necessary
    reqctx.request.environ = reqctx.request.environ.copy()
    def wrapper(*args, **kwargs):
        with reqctx:
            return function(*args, **kwargs)
    return update_wrapper(wrapper, function)

If the request environ is not copied, it is possible with flask 1.0.2 to have older requests in a separate thread read the environ data from newer requests with methods like request.method, which is not desirable at all.  I am not suggesting modifying flask.copy_current_request_context to be like the source code above (1 line change), but rather suggesting the RequestContext copy function could be modified to create a deep copy of a request by providing an environ.copy() to the RequestContext class to create a new request object.  The deep copy could occur based on a boolean keyword argument added to flask.copy_current_request_context.
However, if you want that functionality for threads, you also need to be able to copy the current_app context:
def _copy_current_app_context(function):
    app_context = _app_ctx_stack.top
    def current_app_context_decorator(*args, **kwargs):
        with app_context:
            return function(*args, **kwargs)
    return current_app_context_decorator

Then you would want to use them together with a single decorator:
def bind_context(function):
    function = _copy_current_request_context(function)
    function = _copy_current_app_context(function)
    return function

Actual Behavior
flask.copy_current_request_context will only do a shallow copy and the copy_current_app_context decorator is not provided, nor is the bind_context decorator.  That makes development with threads require more custom source code and be more error-prone than it needs to be.
Environment

Python version: 2.7.9
Flask version: 1.0.2
Werkzeug version: 0.14.1

Just for clarity @okeuday, a deepcopy of the session is not the purpose of #2936 (as mentioned in my last comment there). This issue here should encapsulate deepcopying of the request and session.

@dchevell Ok, thanks for the clarification!

As the docs say, if you want to use the copy between multiple threads, you need to synchronize that.
As to copying the app context, the context knows what app created it, and pushing the copied request context will also push an app context.
I think this is getting uncommon enough that if a project needs it, they can implement it. The Flask object can be subclassed to override request_context and app_context, which could return subclassed context classes that do what you want.

It is unfortunate that the flask source code considers threaded use uncommon and not worthy of development or testing because that avoids providing a single solution for threaded use that is capable of being well-tested.

I don't consider threads uncommon, what I consider uncommon is what's being asked for in this issue, when extension points to support if if needed already exist, as explained in my previous comment.


[py27] Fixing a bug with bad conditions

These changes fix a condition for python 2.7 only.
Python 3 and python 2.7 behave differently during our key handling.
With python 3, in the case where the key is empty and where the key is not a
bytes object the concatenation [1] will fail and the execution will be stoped
with the raise of a TypeError exception.
With python 2 the concatenation is not a problem and so the execution
isn't stoped and that lead us to a problematic condition few line below [2].
Here we execute a condition with a boolean logic and an or operator.
That mean that if the first condition doesn't return True we will
execute the second condition, in this case we will compare an index of a
previous split with our original key. The problem here is that if our
key is empty then we will try to retrieve the index 0 which will lead
us to an IndexError (empty list).
This error is allowed with python 2.7 because the previous concatenation
doesn't fail. The execution can continue.
These changes ensure that the list is not empty before trying to
retrieve an index. This is possible by using an and operator in the
second logic expression. This one will stop the execution and will
ignore the index part if the list is empty.
These changes also add few unittest to check more directly this
function.
The empty key lead to a specific concatenation behaviour which
depends-on the version of python used and lead us to the part bug with
the condition.
[1] https://github.com/pinterest/pymemcache/blob/master/pymemcache/client/base.py#L110
[2] https://github.com/pinterest/pymemcache/blob/master/pymemcache/client/base.py#L116

My unit tests doesn't really reflect this bug but if you want I can implement conditional tests that will reflect the problem.
I think that the problem is enough explicit to be understood by reading the condition.
The tricky part is more the concatenation part of the issue, that isn't evident at first glance.
Up to you.

I added tests with d4930ed to highlight the difference between python 2 and python 3.

Another way to observe that is to execute:
$ python2.7 -c "print('' + b'')"

$ python3.7 -c "print('' + b'')"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: can only concatenate str (not "bytes") to str
$ python3.6 -c "print('' + b'')"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: must be str, not bytes
$ python3.5 -c "print('' + b'')"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: Can't convert 'bytes' object to str implicitly

Done


bundle: Add initialization-resource annotation in the csv

Add a annotation with the default storage system to create a storage
system exactly after installing the operator.
Signed-off-by: Nitin Goyal<EMAIL_ADDRESS>https://bugzilla.redhat.com/show_bug.cgi?id=1995009

Tested this out and it worked

For some reason you're not being redirected to the right URL.
Can you share the URL of the page you are getting redirected to?

/override ci/prow/odf-operator-bundle-e2e-aws

For some reason you're not being redirected to the right URL.
Can you share the URL of the page you are getting redirected to?

Actually, I have tested this on a 4.8 cluster

For some reason you're not being redirected to the right URL.
Can you share the URL of the page you are getting redirected to?

Actually, I have tested this on a 4.8 cluster

Ah okay!
/lgtm

@bipuladh It looks like there is a bug in the openshift-ci as you are also able to give /lgtm as your name is not in the owner's file. @jarrpa am I missing something here?

Lgtm tags can be provided by anyone. I however cannot approve PRs


[Question] pip install gymnasium-robotics[mujoco-py]

Hi!
When I use this command pip install gymnasium-robotics[mujoco-py],
no matches found: gymnasium-robotics[mujoco-py] is displayed.
Is this installation correct and still available?
Thanks!

try pip install 'gymnasium-robotics[mujoco_py]'


Configuration Cache Miss due to idea.io.use.nio2 system property change

Current Behavior
Given a Gradle project where one of the components (incorrectly) calls System.getProperties(), if we populate the configuration cache with a simple help, the subsequent build cannot reuse the cache entry because:
Calculating task graph as configuration cache cannot be reused because system property 'idea.io.use.nio2' has changed.

The third build hits the configuration cache correctly.
Initially, we thought this issue might be related to working in local environments when switching between the IDE and command-line. However, we were able to reproduce this issue in CI ephemeral agents where the build is only executed through the command line.
Upon checking the Kotlin GitHub repository, we observed that the property is set here: Kotlin GitHub Link. This function has various references in the repository, as seen here: Search Results for setIdeaIoUseFallback in Kotlin.
Additionally, we noticed that this function is called within Gradle code: Search Results for setIdeaIoUseFallback in Gradle.
It’s unclear if this is happening during the compilation of the Kotlin scripts.
Expected Behavior
The second build hits the configuration cache
Context (optional)
No response
Steps to Reproduce

Download https://github.com/cdsap/IdeaIoUseNio2Issue
Stop gradle daemon/kill gradle processes
Execute ./gradlew :help --configuration-cache
Execute again ./gradlew :help --configuration-cache

Gradle version
8.9
Build scan URL (optional)
https://ge.solutions-team.gradle.com/s/at7gzw5arneok/console-log?page=1#L0
Your Environment (optional)
No response

The issue is in the backlog of the relevant team and is prioritized by them.

This probably happens because Gradle modifies the property in a way that bypasses CC sysprop change detection.


Documentation-specific issue and pull request template

Expected Behaviour
It would be really helpful if there were standard ISSUE_TEMPLATE.md and PULL_REQUEST_TEMPLATE.md files which were useful for documentation-only projects.
Actual Behaviour
These don't exist :(

Agreed. I'll put something together

FWIW, I took a stab here:
https://github.com/AdobeDocs/cloudmanager-api-docs/blob/master/PULL_REQUEST_TEMPLATE.md
https://github.com/AdobeDocs/cloudmanager-api-docs/blob/master/ISSUE_TEMPLATE.md
The pull request one was simple since it is just a reduction of the normal one. I honestly don't have enough experience with docs issues to figure out what would make a good template.

okk thanx for the response 🙂
On Sat, Apr 4, 2020, 12:39 AM Fil Maj<EMAIL_ADDRESS>wrote:

I am no longer at Adobe and don't have the powers to close issues but
perhaps @macdonst https://github.com/macdonst does
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adobe/starter-repo/issues/2#issuecomment-608610621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIETYZMF5AWJ4B4F4RNBQU3RKYX6LANCNFSM4F3BD6LA
.

@justinedelson please close this issue if it solves


feat: add ability to add and parse empty namespaced shares

Description
We need to be able to easily add "namespaced padding" in order to have non-interactive defaults. This PR adds that. Finally felt confident enough in the current non-interactive defaults implementation to mark this portion ready for review, as the rest depends on it.
Closes: #XXX

will be incorporating the feedback provided here into a different PR in the app, as this code needs to be moved to the app for non-interactive defaults

closing in favor of https://github.com/celestiaorg/celestia-app/pull/637
please see this commit for the incorporation of the remaining feedback here :purple_heart:


Error: The following dependencies are imported but could not be resolved: virtual:generated-pages

Hi everyone! I have the next stack on my project: Vue 3, Vite, Typescript, Vite plugin pages for simplifying routing. And I needed to add a Storybook (https://storybook.js.org/blog/storybook-for-vite/) for my project.
After installing a Storybook I tried to start(npm run storybook) and got the error:
info @storybook/vue3 v6.4.0-alpha.19 info info => Loading presets info => Using prebuilt manager ERR! Error: The following dependencies are imported but could not be resolved: ERR! ERR!   virtual:generated-pages (imported by C:/Users/Dell/Desktop/projects/VTest/candidate-app-v2/src/main.ts) ERR! ERR! Are they installed? ERR!     at optimizeDeps (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\vite\dist\node\chunks\dep-0ed4fbc0.js:66527:15) ERR!     at processTicksAndRejections (internal/process/task_queues.js:97:5) ERR!     at async runOptimize (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\vite\dist\node\chunks\dep-0ed4fbc0.js:70343:48) ERR!     at async createServer (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\vite\dist\node\chunks\dep-0ed4fbc0.js:70372:9) ERR!     at async Object.start (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\storybook-builder-vite\index.js:33:20) ERR!     at async Promise.all (index 0) ERR!     at async storybookDevServer (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\@storybook\core-server\dist\cjs\dev-server.js:123:28) ERR!     at async buildDevStandalone (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\@storybook\core-server\dist\cjs\build-dev.js:112:31) ERR!     at async buildDev (C:\Users\Dell\Desktop\projects\VTest\candidate-app-v2\node_modules\@storybook\core-server\dist\cjs\build-dev.js:154:5)
Does someone know how to fix it?

@VsevolodKurochka I was actually looking to use a similar tech stack as well, and I have been able to get things running in an application I was testing out. I am still running into some issues with the components not loading but I was able to resolve the issue with the virtual:generated-pages not being resolved.
The key thing I found was that in the storybook-builder-vite docs they mention that "The builder will not read your vite.config.js file by default." So what I did was take all of the plugins that I was using in my vite.vonfig.js file and added them to my .storybook/main.js vite config.
This is what that config file looks like:
const path = require('path')
const { default: vuePlugin } = require('@vitejs/plugin-vue')
const { default: pagesPlugin } = require('vite-plugin-pages/dist')
const { default: layoutPlugin } = require('vite-plugin-vue-layouts')
const { default: componentsPlugin } = require('vite-plugin-components')

module.exports = {
  async viteFinal(config, { configType }) {
    // customize the Vite config here
    config.resolve.alias['@/'] = `${path.resolve(__dirname, 'src')}/`
    config.plugins.push([
      vuePlugin({include: [/\.vue$/],}),
      pagesPlugin({extensions: ['vue'],}),
      layoutPlugin({}),
      componentsPlugin({extensions: ['vue'],})
    ])

    // return the customized config
    return config;
  },
  "stories": [
    "../src/**/*.stories.mdx",
    "../src/**/*.stories.@(js|jsx|ts|tsx)"
  ],
  "addons": [
    "@storybook/addon-links",
    "@storybook/addon-essentials",
  ],
  "core": {
    "builder": "storybook-builder-vite"
  }
}

This ended up resolving the loading issue and I was able to successfully build storybook after setting these configurations. I think whatever plugins you have set in your vite.config.js it needs to be matched exactly in the storybook config to work as expected.


JoyDance crashing after attempt

So after like two tries on connecting the joycon to the game (jd 2017 pc), the cmd prompt just crashes
{'pairing_method': 'old', 'host_ip_addr': '<IP_ADDRESS>', 'console_ip_addr': '<IP_ADDRESS>', 'pairing_code': '', 'joycon_serial': '64b5c6d8616d'} 64b5c6d8616d PairingState.CONNECTING Traceback (most recent call last):   File "C:\Users\cerda\Downloads\joydance-0.5.2\joydance-0.5.2\joydance\__init__.py", line 416, in connect_ws     async with websockets.connect(   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\site-packages\websockets\client.py", line 517, in __aenter__     return await self            ^^^^^^^^^^   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\site-packages\websockets\client.py", line 535, in __await_impl__     transport, protocol = await self._create_connection()                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 1098, in create_connection     transport, protocol = await self._create_connection_transport(                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 1118, in _create_connection_transport     protocol = protocol_factory()                ^^^^^^^^^^^^^^^^^^   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\site-packages\websockets\client.py", line 69, in __init__     super().__init__(**kwargs)   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\site-packages\websockets\protocol.py", line 235, in __init__     self._drain_lock = asyncio.Lock(                        ^^^^^^^^^^^^^ TypeError: Lock.__init__() got an unexpected keyword argument 'loop' 64b5c6d8616d PairingState.ERROR_CONSOLE_CONNECTION disconnected Exception in thread Thread-107 (_update_input_report): Traceback (most recent call last):   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 1038, in _bootstrap_inner     self.run()   File "C:\Users\cerda\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 975, in run     self._target(*self._args, **self._kwargs)   File "C:\Users\cerda\Downloads\joydance-0.5.2\joydance-0.5.2\pycon\joycon.py", line 121, in _update_input_report     while report[0] != 0x30:           ~~~~~~^^^ TypeError: 'NoneType' object is not subscriptable {'pairing_method': 'old', 'host_ip_addr': '<IP_ADDRESS>', 'console_ip_addr': '<IP_ADDRESS>', 'pairing_code': '', 'joycon_serial': '64b5c6d8616d'}
Thanks to this i can't get to connect the controller help pls

Have you tried connecting to a game that isn't 2017 PC edition?

Have you tried connecting to a game that isn't 2017 PC edition?

yes, i just tried it on just dance 2020 edition on nintendo switch and when i press connect it says invalid pairing code even though it is correct

Have you tried connecting to a game that isn't 2017 PC edition?

yes, i just tried it on just dance 2020 edition on nintendo switch and when i press connect it says invalid pairing code even though it is correct

Huh. I really don't know what would be causing this.
You might have luck if you try on a different device, but otherwise I don't know how to fix this (though a solution probably exists that I don't know about, if you keep searching).


A list of supported operating systems under Prerequisites in Azure VM Agent overview document

Can we have make list of supported operating systems for Azure VM Agent?
The following Azure VM agent prerequisites does not indicate full list of supported operating systems:
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#prerequisites
Example, something like below:
https://docs.microsoft.com/en-us/azure/azure-monitor/agents/agents-overview#supported-operating-systems

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

ID: ab75f449-661d-bd1e-3ebd-61e2384a911a
Version Independent ID: e7c93a31-6076-26b8-a53d-d36df01ec6bc
Content: Azure Virtual Machine Agent Overview - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/agent-windows.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @amjads1
Microsoft Alias: amjads

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#reassign @MsGabsta

I am looking into this.

@samadara-msft this has been added, a more detailed table will be setup once we support ARM64 also.
From the edited page:
Prerequisites
The Azure Windows VM Agent supports the x64 architecture for these Windows operating systems:
Windows 10
Windows 11
Windows Server 2008 SP2
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016 Core
Windows Server 2019
Windows Server 2019 Core
Windows Server 2022
Windows Server 2022 Core

@cynthn this can be closed now.