An old version of CMake is being used that cannot automatically detect  compiler attributes🔧

How were you trying to build the app?
I tried running the app with nx but it utilizes yarn to start the app
Full build logs
CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  CMake Warning at C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    C:/Users/username/AppData/Local/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
    .cxx/Debug/5x615p1k/arm64-v8a/CMakeFiles/3.18.1-g262b901-dirty/CMakeSystem.cmake:6 (include)
    CMakeLists.txt:1 (project)

  CMake Warning at CMakeLists.txt:250 (message):
    VisionCamera linking: FOR_HERMES=true

  ninja: error: manifest 'build.ninja' still dirty after 100 tries

* Try:
    at makeError (C:\Users\username\Documents\Projects\project\node_modules\execa\index.js:174:9)
    at C:\Users\username\Documents\Projects\project\node_modules\execa\index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (C:\Users\username\Documents\Projects\project\node_modules\react-native\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:82:7)
    at async Command.handleAction (C:\Users\username\Documents\Projects\project\node_modules\react-native\node_modules\@react-native-community\cli\build\index.js:108:9)

Project dependencies
"@azure/communication-email": "^1.0.0",
    "@azure/functions": "^3.0.0",
    "@azure/identity": "^3.2.3",
    "@azure/storage-blob": "^12.15.0",
    "@hookform/resolvers": "3.1.0",
    "@invertase/react-native-apple-authentication": "^2.2.2",
    "@react-native-community/netinfo": "^9.4.1",
    "@react-native-firebase/app": "^18.3.0",
    "@react-native-firebase/app-distribution": "^18.3.0",
    "@react-native-firebase/crashlytics": "^18.3.0",
    "@react-native-firebase/messaging": "^18.3.0",
    "@react-native-google-signin/google-signin": "^10.0.1",
    "@react-spring/native": "^9.7.3",
    "@realm/react": "^0.5.1",
    "@sayem314/react-native-keep-awake": "^1.2.2",
    "@stripe/stripe-react-native": "^0.29.0",
    "@tanstack/react-query": "^4.26.1",
    "@trpc/client": "10.32.0",
    "@trpc/react-query": "10.32.0",
    "@trpc/server": "10.32.0",
    "@turf/turf": "^6.5.0",
<EMAIL_ADDRESS>"^1.5.1",
    "@uppy/core": "^3.2.0",
    "@uppy/dashboard": "^3.4.0",
    "@uppy/drag-drop": "^3.0.2",
    "@uppy/file-input": "^3.0.2",
    "@uppy/progress-bar": "^3.0.2",
    "@uppy/react": "^3.1.2",
    "antd": "^5.8.4",
    "axios": "^1.4.0",
    "base-64": "^1.0.0",
    "bcryptjs": "^2.4.3",
    "buffer": "^6.0.3",
    "busboy": "^1.6.0",
    "chart.js": "^4.3.3",
    "cross-fetch": "^3.1.5",
    "dayjs": "^1.11.7",
    "exceljs": "^4.3.0",
    "fast-text-encoding": "^1.0.6",
    "fido2-lib": "3.4.0",
    "firebase-admin": "^11.10.1",
    "framer-motion": "^10.9.1",
    "google-auth-library": "^8.8.0",
    "jose": "^4.14.4",
    "jsonwebtoken": "^9.0.0",
    "knex": "^2.4.2",
    "leaflet": "^1.9.4",
    "leaflet-geosearch": "^3.8.0",
    "leaflet.markercluster": "^1.5.3",
    "mjml": "^4.14.1",
    "mysql2": "^3.2.0",
    "patch-package": "^8.0.0",
    "postinstall-postinstall": "^2.1.0",
    "react": "18.2.0",
    "react-chartjs-2": "^5.2.0",
    "react-checkbox-tree": "^1.8.0",
    "react-datepicker": "^4.10.0",
    "react-dom": "18.2.0",
    "react-dropdown-tree-select": "^2.8.0",
    "react-hook-form": "^7.43.8",
    "react-icons": "^4.8.0",
    "react-is": "18.2.0",
    "react-loading-skeleton": "^3.2.0",
    "react-native": "0.71.8",
    "react-native-biometrics": "^3.0.1",
    "react-native-date-picker": "^4.2.13",
    "react-native-device-info": "^10.6.0",
    "react-native-dotenv": "^3.4.8",
    "react-native-flipper": "0.203.0",
    "react-native-get-location": "^3.0.1",
    "react-native-get-random-values": "^1.9.0",
    "react-native-image-picker": "^5.6.0",
    "react-native-keychain": "^8.1.2",
    "react-native-map-clustering": "^3.4.2",
    "react-native-maps": "^1.7.1",
    "react-native-nfc-manager": "^3.14.6",
    "react-native-permissions": "^3.8.0",
    "react-native-reanimated": "^2.14.4",
    "react-native-simple-toast": "^3.0.1",
    "react-native-svg": "13.13.0",
    "react-native-toast-message": "^2.1.6",
    "react-native-vector-icons": "^9.2.0",
    "react-native-vision-camera": "2.15.5",
    "react-router-dom": "^6.9.0",
    "react-router-native": "^6.10.0",
    "react-select": "^5.7.2",
    "react-spinners": "0.13.8",
    "react-tabs": "^6.0.1",
    "react-tooltip": "^5.14.0",
    "react-virtualized": "^9.22.5",
    "realm": "^11.10.1",
    "realm-flipper-plugin-device": "1.1.0",
    "stripe": "^12.16.0",
    "styled-components": "5.3.6",
    "sweetalert2": "^11.7.3",
    "tsconfig-paths": "^4.1.2",
    "tslib": "^2.3.0",
    "use-debounce": "^9.0.3",
    "util": "^0.12.5",
    "uuidv4": "^6.2.13",
    "vision-camera-code-scanner": "^0.2.0",
    "zod": "^3.21.4"

Target platforms
iOS, Android
Operating system
Windows
Can you build the VisionCamera Example app?

[ ] I can build the VisionCamera Example app.

Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

If I upgrade to 3.0.0-rc10 or 3.0.0 I get the following
BUILD FAILED in 39s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
node_modules\vision-camera-code-scanner\android\src\main\java\com\visioncameracodescanner\VisionCameraCodeScannerPlugin.java:40: error: VisionCameraCodeScannerPlugin is not abstract and does not override abstract method callback(Frame,Map<String,Object>) in FrameProcessorPlugin
public class VisionCameraCodeScannerPlugin extends FrameProcessorPlugin {
^
node_modules\vision-camera-code-scanner\android\src\main\java\com\visioncameracodescanner\VisionCameraCodeScannerPlugin.java:62: error: method does not override or implement a method from a supertype
@Override
^
node_modules\vision-camera-code-scanner\android\src\main\java\com\visioncameracodescanner\VisionCameraCodeScannerPlugin.java:251: error: constructor FrameProcessorPlugin in class FrameProcessorPlugin cannot be applied to given types;
super("scanCodes");
^
required: no arguments
found: String
reason: actual and formal argument lists differ in length
node_modules\vision-camera-code-scanner\android\src\main\java\com\visioncameracodescanner\VisionCameraCodeScannerPluginPackage.java:19: error: cannot find symbol
FrameProcessorPlugin.register(new VisionCameraCodeScannerPlugin());
^
symbol:   method register(VisionCameraCodeScannerPlugin)
location: class FrameProcessorPlugin
4 errors
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':vision-camera-code-scanner:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
java.lang.StackOverflowError (no error message)

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

Get more help at https://help.gradle.org

BUILD FAILED in 39s
at makeError (C:\Users\piete\Documents\OpenVantage Projects\City-ev\node_modules\execa\index.js:174:9)
at node_modules\execa\index.js:278:16
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async runOnAllDevices (node_modules\react-native\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:82:7)
at async Command.handleAction (node_modules\react-native\node_modules\@react-native-community\cli\build\index.js:108:9)

info Run CLI with --verbose flag for more details.

You need to upgrade your CMake version to the same one I use in VisionCamera example (here)

I have 3.18 and the latest installed.

And If I uninstall 3.18 your react-native-vision-camera re-installs it

Getting the same issue here. I have both CMake 3.22.1 and 3.18.1

If I upgrade to 3.0.0-rc10 or 3.0.0 I get the following

Getting the same issue here. I have CMake 3.22.1.
"react-native": "0.72.5"
"react-native-vision-camera": "^3.1.0"

Any solution for this getting the same error

I have 3.18 and the latest installed.

And If I uninstall 3.18 your react-native-vision-camera re-installs it @mrousavy

getting Same Issue....Any Solution for resolving this ?

Same here, @mrousavy is the library still using old versions of CMake and you need to update the library so that it uses newer verons ? or is it independent of that, because this error seems still unsolvable

Even facing this CMAKE issue, even thought higher version is installed it forces 3.18 and reinstall if not present

Hi @mrousavy, seems like you forgot the link here:

You need to upgrade your CMake version to the same one I use in VisionCamera example (here)

So was there any solution for this? (i see it's closed) Still having some CMAKE build issue on android. Followed the troubleshooter and everything. Latest 3.22 installed from Android Studio.
Using the following:
react-native-vision-camera: 3.6.6
react-native: 0.69.12
It builds, runs and installs fine on iOS 17.1, however i'm not able to get it running on Android.
Error from ./gradlew assembleRelease:
> Task :react-native-vision-camera:buildCMakeRelWithDebInfo[arm64-v8a] FAILED
C/C++: ninja: Entering directory `/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native-vision-camera/android/.cxx/RelWithDebInfo/205o2y4k/arm64-v8a'
C/C++: In file included from ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp:5:
C/C++: ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.h:7:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found
C/C++: In file included from ../../../../src/main/cpp/VisionCamera.cpp:2:
C/C++: ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.h:7:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found
C/C++: In file included from ../../../../src/main/cpp/frameprocessor/VisionCameraProxy.cpp:5:
C/C++: In file included from ../../../../src/main/cpp/frameprocessor/VisionCameraProxy.h:9:
C/C++: ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.h:7:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found
w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions

FAILURE: Build completed with 2 failures.

Furthermore:
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':react-native-vision-camera:buildCMakeRelWithDebInfo[arm64-v8a]'.
> com.android.ide.common.process.ProcessException: ninja: Entering directory `/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native-vision-camera/android/.cxx/RelWithDebInfo/205o2y4k/arm64-v8a'
  [1/4] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o
  /Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=aarch64-none-linux-android26 --gcc-toolchain=/Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -DVISION_CAMERA_ENABLE_FRAME_PROCESSORS=false -DVisionCamera_EXPORTS -I../../../../../cpp -I../../../../src/main/cpp -I../../../../src/main/cpp/frameprocessor -I../../../../src/main/cpp/frameprocessor/java-bindings -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactCommon -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactCommon/callinvoker -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactAndroid/src/main/jni/react/turbomodule -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/44f87529cbf9f777306931dc59c5d740/transformed/jetified-react-android-0.73.0-rc.4-release/prefab/modules/jsi/include -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/44f87529cbf9f777306931dc59c5d740/transformed/jetified-react-android-0.73.0-rc.4-release/prefab/modules/reactnativejni/include -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/c7598e7d957f8ec4dcaab85973495b27/transformed/jetified-fbjni-0.5.1/prefab/modules/fbjni/include -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security  -O2 -frtti -fexceptions -Wall -Wno-unused-variable -fstack-protector-all -O2 -g -DNDEBUG -fPIC -std=gnu++17 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o -c ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp
  In file included from ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp:5:
  ../../../../src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.h:7:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found
  #include <ReactCommon/CallInvokerHolder.h>
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1 error generated.
  [2/4] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  /Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=aarch64-none-linux-android26 --gcc-toolchain=/Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/stianwiikinstebo/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -DVISION_CAMERA_ENABLE_FRAME_PROCESSORS=false -DVisionCamera_EXPORTS -I../../../../../cpp -I../../../../src/main/cpp -I../../../../src/main/cpp/frameprocessor -I../../../../src/main/cpp/frameprocessor/java-bindings -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactCommon -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactCommon/callinvoker -I/Users/stianwiikinstebo/Documents/Backup/YourProjectNameBak-RN096/node_modules/react-native/ReactAndroid/src/main/jni/react/turbomodule -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/44f87529cbf9f777306931dc59c5d740/transformed/jetified-react-android-0.73.0-rc.4-release/prefab/modules/jsi/include -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/44f87529cbf9f777306931dc59c5d740/transformed/jetified-react-android-0.73.0-rc.4-release/prefab/modules/reactnativejni/include -isystem /Users/stianwiikinstebo/.gradle/caches/transforms-3/c7598e7d957f8ec4dcaab85973495b27/transformed/jetified-fbjni-0.5.1/prefab/modules/fbjni/include -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security  -O2 -frtti -fexceptions -Wall -Wno-unused-variable -fstack-protector-all -O2 -g -DNDEBUG -fPIC -std=gnu++17 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o -c ../../../../src/main/cpp/VisionCamera.cpp

@mrousavy this issue still persists on RN 0.71.4. I have a C Make version of 3.22.1.
How can i get this resolved? @mrousavy

please stop tagging me - I don't know, when you just give me a version and no reproduction I cannot help you.
The example app builds fine, try comparing your versions with that.

@mrousavy please helpppp


Precipitation Types

This issue is a continuation of the discussion from this issue https://github.com/alexander0042/pirate-weather-ha/issues/78 and since the discussion about adding other precipitation types.
I know that DarkSky is pretty limited when it comes to precipitation types (as well as icons) and I am aware that you want to keep things compatible with DarkSky and using flags/API options instead of breaking things. I know that WeatherKit has added in more icons/precipitation types to their API so maybe it's worth breaking things in this case?
Maybe the following could be added as precipTypes:

freezingrain or ice
hail
mixed
unknown or precipitation

I thought about adding in thunderstorm but since it isn't a form of precipitation I decided to exclude it. I was thinking about thunderstorms today and it would be a nice addition to the API. I know there are ways to forecast using Lifted Index/CAPE/precipRate/wind speed/etc. and using the Blitzortung (#6) to show in the currently section.
I would show the icon only if precipType is rain and it would always come after the precipType so if we use today as an example it would show Freezing Rain and Thunderstorms.
EDIT: I might be misunderstanding the Categorical Ice/Rain/Snow/Sleet that HRRR offers. During precipitation only one of those four values will be 1 and the rest 0? If that's the case then maybe we can not bother adding in mixed as a precipType

This issue was probably missed so will bump for visibility. Probably more of a long-term issue here so adding the keep label would be useful.


Added custom-config folder in my.cnf

Signed-off-by: Md. Alif Biswas<EMAIL_ADDRESS>

General and custom-config e2e-test passed.


Add simple fixes to sim plugin

There is no problem with my test.

@rsetaluri Do you know what's the issue with travis test?

@joyliu37 not sure, trying it again

Ok passing. Merging.


Feature request: allow custom agentx socket address

The socket address is currently hardcoded to /var/agentx/master it would be nice if it were possible to specify a custom socket path (net-snmp allows alternate paths)

thx for the request, socket path is now configurable


workflows: add simple docker action

This fixes #53

This needs a little more work since for some reason the app exits 1 and not 0

Thanks. I've just setup a Docker Hub account and integrated the build that way. Any changes to the repo will kick off a build there. Is there any reason for this now?

Yeha my idea was that an action would be triggered on every PR, so people could easily see if their changes breaks things
this action would build the image and run it to be sure the building works and running as well

Ahh I'll see. Soo every PR regardless if I merge them in to main. Yeah that's pretty cool. I'll check this out.


docs(guides): amend doInvoke and advanced API guide

Update and rearrange some information in doInvoke and the advanced doInvoke guide

Shifted the drop of gas workaround into basic doInvoke
Renamed advanced doInvoke to be a more general API core functionality guide
Rewrote the advanced guide to reflect more functionality.

@jeroenptrs I amended your guides. Please review.

@jeroenptrs typoes are corrected! Thanks for proofreading! Anything else you wanna add?

@snowypowers nah looks good! It's a good read!


Add BinaryType to some shimmed expressions [databricks]

Fixes #6308.  Adds BinaryType to a few expressions that appear in shim code that was missed in #6298.

build

build


NameError on pod install

I'm trying to migrate from the post install script to the cocoapods-acknowledgements plugin. When I run pod install I get this error:
NameError - uninitialized constant Class::UI
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/sources_manager.rb:170:in `const_missing'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements/plist_generator.rb:69:in `license_text'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements/plist_generator.rb:21:in `block in generate'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements/plist_generator.rb:17:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements/plist_generator.rb:17:in `generate'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:66:in `block (4 levels) in <module:CocoaPodsAcknowledgements>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:63:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:63:in `block (3 levels) in <module:CocoaPodsAcknowledgements>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:60:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:60:in `block (2 levels) in <module:CocoaPodsAcknowledgements>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/user_interface.rb:63:in `section'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-acknowledgements-1.1.1/lib/cocoapods_acknowledgements.rb:52:in `block in <module:CocoaPodsAcknowledgements>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:109:in `call'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:109:in `block (3 levels) in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/user_interface.rb:141:in `message'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:103:in `block (2 levels) in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:101:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:101:in `block in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/user_interface.rb:141:in `message'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/hooks_manager.rb:100:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/installer.rb:473:in `run_plugins_post_install_hooks'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/installer.rb:454:in `perform_post_install_actions'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/installer.rb:121:in `install!'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/command/install.rb:37:in `run'
/Library/Ruby/Gems/2.0.0/gems/claide-1.0.0/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/lib/cocoapods/command.rb:50:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.1/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

My podfile looks like this:
source 'git@github.com:CocoaPods/Specs.git'

plugin 'cocoapods-acknowledgements', :settings_bundle => true

platform :ios,'9.0'
use_frameworks!
inhibit_all_warnings!

def shared_pods
    pod 'Kingfisher', '~> 2.4.1'
    pod 'SwiftyJSON', '~> 2.3'
    pod 'Locksmith', '~> 2.0.8'
    pod 'DTMarkdownParser', '~> 0.2.2'
    pod 'Changeset', '~> 1.0.5'
    pod 'ReachabilitySwift', '~> 2.3.3'
    pod 'IHKeyboardAvoiding', '~> 2.5'

    pod 'Crashlytics', '~> 3.7.0', :configurations => ['Debug', 'Testing']
end

target 'Target1' do
    shared_pods
end

target 'Target2' do
    shared_pods
end

It seems it may have something to do with reading one of the license files? Or?

Sorry for taking so long to look at this. It really seems that the plugin isn't able to read one of the licenses and it'd warn about it (https://github.com/CocoaPods/cocoapods-acknowledgements/blob/master/lib/cocoapods_acknowledgements/plist_generator.rb#L69), but it couldn't find the class responsible for logging.
So, we have at least one bug: the plugin is crashing when trying to warn in license_text.
We may have another bug if the license really exists. Can you try to make a small reproducible Podfile with the "culprit" dependency so we can check it it's really a bug?
Thanks for filling this.

I too apologize on the long response time. The upside is that I found out what caused the issue.
The pod Changeset in version 1.0.5 refers to a license file that doesn't exist. If this pod is included in the Podfile, cocoapods-acknowledgements fails. Here's a sample project:
https://www.dropbox.com/s/kllubwefk8805ar/cocoapods_issue.zip?dl=1


Update Blockscout API endpoint for xDai

Old:
curl 'https://blockscout.com/poa/dai/api?module=account&action=tokentx&address=<address>'

New:
curl 'https://blockscout.com/xdai/mainnet/api?module=account&action=tokentx&address=<address>'

So transactions aren't fetched anymore and we can't detect any tokens — ERC20, ERC721.

(interestingly, replacing the "dai" with "xdai" in the old URL would work too, but let's just use the newer version that the 301 response is including, i.e "/xdai/mainnet/api?")

thanks, got it.

Reopen to double check


The next version is V1 or V14.0, and How long will it take to post

Question
Description
Give more information about your doubt

Twitter: If it's just a quick question you can ping me on Twitter: https://twitter.com/pedronauck

@pedronauck

our project is urgent for the new version

Hi @HadeAs, the next version will be v1, but it's a pretty big release I need to be careful, so I'm making tests and write documentation, in couple weeks we'll release it :)

@pedronauck  ok thks


Question regarding molecule property scores

Hi, thanks for the nice paper+code.  according to your paper, I think you missed a lot of SOTA papers regarding molecule properties when comparing.  I can see that you're comparing pretrained methods with GIN. However, if you refer to the latest paper for instance https://github.com/HIM-AIM/BatmanNet, scores are way more higher than that in your papers.
for instance BBBP is 0.946 for batmannet and pretrained SMILES-BERT goes over 0.959 for AUC-ROC while the data in yours indicate near 0.8 maximum
Maybe i misunderstood how you compared the models, can you help me understand why there is such a huge gap between the scores?? It is clear that for geometric tasks such as QM9, 2D has low performance. But It's hard for me to understand how 2D + 3D considered representation has lower score compared to only 2D in predicting molecular property. maybe it is due to the dataset size(PCQM4Mv2)?

Hi @orgw,
Thank you for raising this question.
It's because we are comparing the pretraining modeling, while what you referred to is the backbone representation model.
In our paper, we highlighted that our proposed pretraining model (MoleculeSDE) is agnostic to the backbone model.

Thank you for the clarification!


Engine - Split Status and Phase events for publish

Currently the events publish to the event sink are for Status or Phase, however are all prefixed as StatusEvents

Determine if this is still needed. The event should just be an update to object regardless of phase or status


Support multi line commit

h3.Actual:
Jira key is not extracted from multi line commits.
h3.Expected:
Jira key should be extracted from multi line commits.

As I see, getChanges does not return with the full commit message:
https://docs.microsoft.com/en-us/rest/api/azure/devops/build/builds/get-build-changes?view=azure-devops-rest-6.0#change
The description of the change. This might be a commit message or changeset description.


1.4.4: TestTLSEnding.test_eof_received fails

Hi! When trying to package 1.4.4 for Arch Linux I ran into issues with TestTLSEnding.test_eof_received:
=================================== FAILURES ===================================
_______________________ TestTLSEnding.test_eof_received ________________________

self = <aiosmtpd.tests.test_starttls.TestTLSEnding object at 0x7fb7dec8bb20>
tls_controller = <aiosmtpd.controller.Controller object at 0x7fb7deb21720>
client = <smtplib.SMTP object at 0x7fb7deb231f0>

    @handler_data(class_=EOFingHandler)
    def test_eof_received(self, tls_controller, client):
        # I don't like this. It's too intimately involved with the innards of the SMTP
        # class. But for the life of me, I can't figure out why coverage there fail
        # intermittently.
        #
        # I suspect it's a race condition, but with what, and how to prevent that from
        # happening, that's ... a mystery.

        # Entering portion of code where hang is possible (upon assertion fail), so
        # we must wrap with "try..finally".
        try:
            code, mesg = client.ehlo("example.com")
            assert code == 250
            resp = client.starttls()
            assert resp == S.S220_READY_TLS
            # Need this to make SMTP update its internal session variable
            code, mesg = client.ehlo("example.com")
            assert code == 250
            sess: Sess_ = tls_controller.smtpd.session
>           assert sess.ssl_context is not None
E           AttributeError: 'Session' object has no attribute 'ssl_context'

aiosmtpd/tests/test_starttls.py:232: AttributeError
------------------------------ Captured log setup ------------------------------
INFO     mail.log:smtp.py:407 Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
INFO     mail.log:smtp.py:519 Peer: ('::1', 50290, 0, 0)
INFO     mail.log:smtp.py:601 ('::1', 50290, 0, 0) handling connection
DEBUG    mail.log:smtp.py:587 ('::1', 50290, 0, 0) << b'220 hmbx Python SMTP 1.4.4'
INFO     mail.log:smtp.py:539 ('::1', 50290, 0, 0) EOF received
INFO     mail.log:smtp.py:746 ('::1', 50290, 0, 0) Connection lost during _handle_client()
INFO     mail.log:smtp.py:525 ('::1', 50290, 0, 0) connection lost
INFO     mail.log:smtp.py:407 Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
INFO     mail.log:smtp.py:519 Peer: ('::1', 50292, 0, 0)
INFO     mail.log:smtp.py:601 ('::1', 50292, 0, 0) handling connection
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'220 hmbx Python SMTP 1.4.4'
------------------------------ Captured log call -------------------------------
DEBUG    mail.log:smtp.py:286 _handle_client readline: b'ehlo example.com\r\n'
INFO     mail.log:smtp.py:286 ('::1', 50292, 0, 0) >> b'ehlo example.com'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-hmbx'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-SIZE 33554432'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-SMTPUTF8'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-STARTTLS'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250 HELP'
DEBUG    mail.log:smtp.py:286 _handle_client readline: b'STARTTLS\r\n'
INFO     mail.log:smtp.py:286 ('::1', 50292, 0, 0) >> b'STARTTLS'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'220 Ready to start TLS'
DEBUG    mail.log:smtp.py:286 _handle_client readline: b'ehlo example.com\r\n'
INFO     mail.log:smtp.py:286 ('::1', 50292, 0, 0) >> b'ehlo example.com'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-hmbx'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-SIZE 33554432'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-SMTPUTF8'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250-AUTH LOGIN PLAIN'
DEBUG    mail.log:smtp.py:587 ('::1', 50292, 0, 0) << b'250 HELP'
INFO     mail.log:smtp.py:746 ('::1', 50292, 0, 0) Connection lost during _handle_client()
=========================== short test summary info ============================
FAILED aiosmtpd/tests/test_starttls.py::TestTLSEnding::test_eof_received - At...
======================== 1 failed, 555 passed in 53.08s ========================

python-aiosmtpd-1.4.4-1-x86_64-build.log
python-aiosmtpd-1.4.4-1-x86_64-check.log
This is a regression from 1.4.3, where the test does work!

Interesting.
GitHub Actions did not experience any failures, though: https://github.com/aio-libs/aiosmtpd/actions/runs/3938435294
And as can you see there, we have 56 jobs, using combinations of OS and Python versions.
What I did experience, though, sometimes out of those 56 jobs, up to 3 may fail mysteriously. But whenever I resubmit the failed jobs, usually they just run well and finished successfully.
For example, the above "run", it actually failed twice:

Attempt #1 (3 failures): https://github.com/aio-libs/aiosmtpd/actions/runs/3938435294/attempts/1
Attempt #2 (1 failure): https://github.com/aio-libs/aiosmtpd/actions/runs/3938435294/attempts/2
Attempt #3 (success): https://github.com/aio-libs/aiosmtpd/actions/runs/3938435294

There's no clear pattern on the cause of failures. At least, nothing that I can easily see...
Seems like a combination of external factors / hiccups.

Also to add: Since this affects only testing but does not affect usage, I will likely release a "post-release" version, e.g. 1.4.4.post1 rather than bumping it to 1.4.5.

SOLVED
Omigosh, apparently I made edits that I forgot to shelf before I create the release!
Totally my bad. I will release the 1.4.4.post1 today.

Okay, um, things happened accidentally.
So PyPI has 1.4.4.post1 currently. With fixed test. This one actually got released 'accidentally'.
I'll ... uh ... try to fix things in the proper way for 1.4.5


Extend .compiler_ir() to accept kwargs controlling IR emission.

As a user of this API, is important to have access to 'binary=', 'enable_debug_info=', and 'print_generic_op_form=' as different tasks and integrations call for different things (i.e. 'binary=' saves time/space on large programs, 'print_generic_op_form=' is more compatible with tooling to ensure compatibility, etc).
I debated just having it return a live Module object, but I think it is still wise for the moment to keep this API narrow, and that would be a large expansion.

I wasn't able to find formatting options. Let me know if there is an auto-formatter I should be using.

Closing in favor of https://github.com/google/jax/pull/9242


ModuleNotFoundError: No module named 'pyfury.lib.mmh3.mmh3'

Thank you for reporting the problem!
Please make sure what you are reporting is a bug with reproducible steps.
Describe the bug
A clear and concise description of what the bug is.
After pip install pyfury, import pyfury failed:
Python 3.9.18 (main, Aug 28 2023, 07:00:41)
[GCC 10.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyfury
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/codingl2k1/.pyenv/versions/3.9.18/lib/python3.9/site-packages/pyfury/__init__.py", line 15, in <module>
    from pyfury import lib  # noqa: F401 # pylint: disable=unused-import
  File "/home/codingl2k1/.pyenv/versions/3.9.18/lib/python3.9/site-packages/pyfury/lib/__init__.py", line 15, in <module>
    from pyfury.lib import mmh3  # noqa: F401 # pylint: disable=unused-import
  File "/home/codingl2k1/.pyenv/versions/3.9.18/lib/python3.9/site-packages/pyfury/lib/mmh3/__init__.py", line 15, in <module>
    from .mmh3 import *  # noqa: F401,F403 # pylint: disable=unused-import
ModuleNotFoundError: No module named 'pyfury.lib.mmh3.mmh3'

Expected behavior
A clear and concise description of what you expected to happen.
To Reproduce
Steps to reproduce the behavior.
Please try to provide a reproducible script.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Please specify the versions of Fury, OS, and others such as JDK/Python/Gcc/Clang/Go/NodeJS if they are used.

Which pyfury version are you using? I tested on my local machine, works fine:

@codingl2k1 Macos version included the mmh3 shared library, but linux version missed this file. Thanks for creating this issue, I'll release a new version to fix this.


Make NotImplementedToExpectedFailure work

It was trying to get the wrappee from the object that the wrapper is kept on, leading to a recursion error.

This turned a lot of tests into unexpected successes, and updating that is in progress.  PR will be updated.

Appears to be a duplicate of #541

Yeah, @PamelaM is a bajilion miles ahead of me.


Lupusec Online Status

Checks If Lupusec alarm system ist reachable with http request and by Ping!
Sent with GitHawk

supported in version 1.1.1


Request: Less features release and more stability

Hello!
I have been using yabai for a while now and I love it! That said, a non-issue that would be nice to address would be to have yabai releases less frequently, as it feels like there is not enough period for testing the new features before they are released.
The changelog has one-two changes per patch release right now. If we could have a bigger patch release planned after testing a little, chances are that we can test things a little easier.
Currently, I am having way too many upgrades in the last weeks. I noticed that after upgrading I had some bugs and after another one some things were a little better, then another upgrade that is buggy and one more stable.
Please, this is a minor request, yabai is a mazing and nice as it is :) I can easily fix it by using a pin in brew for yabai, but I wish these changes would still be tested for a longer time before being shipped.

I don't really have a set schedule for when I intend to spend time on development.
The last few weeks I have made some changes, and the reason why releases have been somewhat sporadic is that I didn't think I'd end up doing more work for another couple of months.
Obviously for whatever reason I felt like doing more things this time around, but don't get used to this level of activity.
So, when I actually make changes these days I release them fairly quickly afterwards. I do believe the only recent release that had a regression in terms of stability was 6.0.14.

I would suggest planning releases instead of pushing whatever feels ready.
That said, thank you for your work 🙏

I do understand where you're going with this, but planning is actually time consuming in itself. Anyway, there will be a major release coming up, and after that there will likely be very little changes for the rest of the year as per usual.


Travis isn’t passing on master

This is likely not an error on our side. The UMLS REST API is very unstable - I'll keep retrying the tests. Give it a day ;)
May be I should put try catch and if there are HTTP error allow the test to "fail"

Sounds good- can you restart the build in about 24 hours or so?
On Tue, May 29, 2018 at 15:29 Maria Isabel Restrepo <
<EMAIL_ADDRESS>wrote:

This is likely not an error on our side. The UMLS REST API is very
unstable - I'll keep retrying the tests. Give it a day ;)
May be I should put try catch and if there are HTTP error allow the test
to "fail"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcbi/BioMedQuery.jl/issues/24#issuecomment-392912298,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFXArYwYrhvbataSC724EkFDOklNwXAsks5t3aGQgaJpZM4URzMx
.

--
Dilum Aluthge
<EMAIL_ADDRESS><EMAIL_ADDRESS>https://www.aluthge.com https://www.aluthge.com

In case the tests still don't pass, here's the PR that ignores HTTP errors by default: PR #25

I removed BioMedQuery's dependency on EzXML, but it looks like BioServices depends on it, so we're still getting the error.

Is there any update on the EzXml bug?

EzXML owner said it would be worked on soon 17 days ago.

Is it worth looking into submitting a PR to BioServices to replace EzXML
with a different library, or no?
Dilum Aluthge
<EMAIL_ADDRESS><EMAIL_ADDRESS>https://www.aluthge.com https://www.aluthge.com
On Tue, Jun 19, 2018 at 4:22 PM, mcmcgrath13<EMAIL_ADDRESS>wrote:

EzXML owner said it would be worked on soon 17 days ago.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcbi/BioMedQuery.jl/issues/24#issuecomment-398532690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFXArU_LrmsnNpR13JhdGCcyS-neUUWFks5t-V2RgaJpZM4URzMx
.

Looks like the EzXML issue is fixed. Can we trigger another Travis build?
@mirestrepo @mcmcgrath13


Test error on SpatialPyramidPooling and fail on SpatialSameResponseNormalization

Hi, this is Jaehyun Lim.
I installed the recent version of inn (4c2dc1c147f94259da4beb928c188d616c4ce395), and I tried to run test/test_jacobian.lua.
I got following messages;
1/4 ROIPooling .......................................................... [PASS]
2/4 SpatialPyramidPooling ............................................... [ERROR]
3/4 SpatialStochasticPooling ............................................ [PASS]
4/4 SpatialSameResponseNormalization .................................... [FAIL]
Completed 11 asserts in 4 tests with 1 failure and 1 error
--------------------------------------------------------------------------------
SpatialPyramidPooling
 Function call failed
...hyun/github/torch/install/share/lua/5.1/nn/Container.lua:69:
In 1 module of inn.SpatialPyramidPooling:
In 3 module of nn.Sequential:
...yun/github/torch/install/share/lua/5.1/nn/Contiguous.lua:13: attempt to index local 'gradOutput' (a nil value)
stack traceback:
        ...yun/github/torch/install/share/lua/5.1/nn/Contiguous.lua:13: in function <...yun/github/torch/install/share/lua/5.1/nn/Contiguous.lua:12>
        [C]: in function 'xpcall'
        ...hyun/github/torch/install/share/lua/5.1/nn/Container.lua:65: in function 'rethrowErrors'
        ...yun/github/torch/install/share/lua/5.1/nn/Sequential.lua:55: in function <...yun/github/torch/install/share/lua/5.1/nn/Sequential.lua:50>
        [C]: in function 'xpcall'
        ...hyun/github/torch/install/share/lua/5.1/nn/Container.lua:65: in function 'rethrowErrors'
        ...jaehyun/github/torch/install/share/lua/5.1/nn/Concat.lua:37: in function 'updateGradInput'
        ...ehyun/github/torch/install/share/lua/5.1/nn/Jacobian.lua:21: in function 'backward'
        ...ehyun/github/torch/install/share/lua/5.1/nn/Jacobian.lua:233: in function 'testJacobian'
        test_jacobian.lua:62: in function <test_jacobian.lua:48>
        [C]: in function 'xpcall'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:476: in function '_pcall'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:436: in function '_run'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:354: in function 'run'
        test_jacobian.lua:157: in main chunk
        [C]: in function 'dofile'
        ...thub/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
        [C]: at 0x00406670

WARNING: If you see a stack trace below, it doesn't point to the place where this error occured. Please use only the one above.
stack traceback:
        [C]: in function 'error'
        ...hyun/github/torch/install/share/lua/5.1/nn/Container.lua:69: in function 'rethrowErrors'
        ...jaehyun/github/torch/install/share/lua/5.1/nn/Concat.lua:37: in function 'updateGradInput'
        ...ehyun/github/torch/install/share/lua/5.1/nn/Jacobian.lua:21: in function 'backward'
        ...ehyun/github/torch/install/share/lua/5.1/nn/Jacobian.lua:233: in function 'testJacobian'
        test_jacobian.lua:62: in function <test_jacobian.lua:48>
        [C]: in function 'xpcall'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:476: in function '_pcall'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:436: in function '_run'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:354: in function 'run'
        test_jacobian.lua:157: in main chunk
        [C]: in function 'dofile'
        ...thub/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
        [C]: at 0x00406670

--------------------------------------------------------------------------------
SpatialSameResponseNormalization
error on state
LT failed: nan >= 0.001
stack traceback:
        test_jacobian.lua:91: in function <test_jacobian.lua:82>
--------------------------------------------------------------------------------
SpatialSameResponseNormalization
error on state (Batch)
LT failed: nan >= 0.001
stack traceback:
        test_jacobian.lua:99: in function <test_jacobian.lua:82>
--------------------------------------------------------------------------------
/home/jaehyun/github/torch/install/bin/luajit: ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:362: An error was found while running tests!
stack traceback:
        [C]: in function 'assert'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:362: in function 'run'
        test_jacobian.lua:157: in main chunk
        [C]: in function 'dofile'
        ...thub/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
        [C]: at 0x00406670

Is there anyone who can help me to solve this problem? :)
Thanks
Best regards,
Jaehyun

hi, can't reproduce the error in SPP. The error in same map normalization is due to its high nonlinearity. Both modules are just containers for nn modules and safe to use

@szagoruyko
Thank you for response!
Then, it might be the problem of the configuration of torch in my system.
I will figure it out. Thank you again :)
Best regards,
Jaehyun

I reinstalled torch and solved the error in SPP.
However, the error for SpatialSameResponseNormalization is not resolved. I will just leave in this way for a while.
Anyway, thank you for your comment!
Running 4 tests
1/4 ROIPooling .......................................................... [PASS]
2/4 SpatialPyramidPooling ............................................... [PASS]
3/4 SpatialStochasticPooling ............................................ [PASS]
4/4 SpatialSameResponseNormalization .................................... [FAIL]
Completed 17 asserts in 4 tests with 1 failure and 0 errors
--------------------------------------------------------------------------------
SpatialSameResponseNormalization
error on state
LT failed: nan >= 0.001
stack traceback:
        test_jacobian.lua:91: in function <test_jacobian.lua:82>
--------------------------------------------------------------------------------
SpatialSameResponseNormalization
error on state (Batch)
LT failed: nan >= 0.001
stack traceback:
        test_jacobian.lua:99: in function <test_jacobian.lua:82>
--------------------------------------------------------------------------------
/home/jaehyun/github/torch/install/bin/luajit: ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:360: An error was found while running tests!
stack traceback:
        [C]: in function 'assert'
        ...hyun/github/torch/install/share/lua/5.1/torch/Tester.lua:360: in function 'run'
        test_jacobian.lua:157: in main chunk
        [C]: in function 'dofile'
        ...thub/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
        [C]: at 0x00406670

Best regards,
Jaehyun


crash erminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: sourceNode'

erminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: sourceNode'
*** First throw call stack:
(0x237ef7ef8 0x2370c5a40 0x237e0c06c 0x2388f83e0 0x2648684c8 0x2648668b0 0x264ad36a4 0x264ad93c8 0x264ad5314 0x264ad5248 0x264ad5018 0x26509aa1c 0x264916d50 0x2648528e0 0x26485534c 0x26484dee0 0x237e865b8 0x237e86538 0x237e85e1c 0x237e80ce8 0x237e805b8 0x23a0f4584 0x2648fb558 0x102c2fb88 0x237940b94)

This is not an issue with FLEX, that is a crash within your own app.


Custum Header

I am restyling your table. But I couldn't add a sort icon in the header.
Like:
| ___ Name ___ | ___ Age 🡱 ___ |
I tried to tie into the header like so:
<ReactTable columns={ [ { accessor: 'age', header: ( { column } ) => ??? } ] } />
But maybe there is an even better solution to create a template for all the column-headers to add a font-awesome icon like  in the end of the column (depending if it's sort ASC or DESC)
Any recommendations?

you need to add the header: () =>  Progress, as described in this section of the readme.

Yeah, I was aware of this, but I don't know the information which column is sorted and if ASC or DESC

Why don't you use CSS for that?
Here's what I use:
`div.-sort-asc::after {
content: "\25BC";
float: right;
}
div.-sort-desc::after {
content: "\25B2";
float: right;
}`

Both of those are perfectly fine examples.  To discuss implementation more, please join the slack organization  :)


GH Action: Make the systest-status more clear

Motivation

Make the systest-status job more explicit in how the variables were handle.
Helps to debug and prevent another systest pass when the test it-self failed.

Description
Makes the systest-status more clear.
Test Plan
Run the systest

bors merge


python-flask on linux: stack validate run and test fail cannot create requirements.txt: Permission denied

Describe the bug
Running BATS integration test with the latest stack and cli code via Jenkins to Ubuntu and RHEL VMs and both are failing on stack validate during the run and test steps with the error below...
[Container] /bin/sh: 1: cannot create requirements.txt: Permission denied
[Container] ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
[Container] [Error] FATAL error APPSODY_PREP command received an error.  The controller is exiting: exit status 1
[Debug] CLI exit error is:  exit status 1
[Error] Error in 'appsody test': exit status 1

Full log is here:
stack-validate-python-flask.log
To Reproduce
Steps to reproduce the behavior:

Go to stacks/incubator/python-flask
appsody stack validate

Environment Details (please complete the following information):

OS: [e.g. iOS] Ubuntu 18.0.4 and RHEL 7.7

If applicable please specify:

CLI version: latest dev
Stack you are using (including the version): python-flask

I can't replicate this locally on my Ubuntu vm (also 18.04) but the travis build for https://github.com/appsody/stacks/pull/660 is failing for the same reason. @henrynash have you seen this before?

I had not seen this before....but looks like you have a fix proposed....

@henrynash I added the APPSODY_USER_RUN_AS_LOCAL env var in https://github.com/appsody/stacks/pull/660 which seems to have fixed the problem. I think the userapp directory was created with a different owner to the user inside the container hence the permission denied.

@Kamran64 Can we close this then?


[AddSwift.cmake] Unbreak non-assertions build

Fails to build with "error: macro name must be an identifier" due to trying to pass -D-DNDEBUG as compiler argument.

@swift-ci smoke test

LGTHM


how to add a hook function before submit? just like onSubmitHook

i want to check the text password on the client side before i submit, is it possiable?

Q2: how to fetch the field value(e.g. username,password) inside onSubmitHook function?

@iclear if you're interested in validating fields' value lets have a look at Form Fields Configuration and the Custom validation subsection.

@splendido thanks for your reply.
But i find 'AccountsTemplates.addField' doesn't work in the login page where i want to validate the password.  is there a way to do this?

validations on login were removed by purpose to prevent possible attackers to see the rules you're enforcing for passwords and usernames!
This line and this one are those preventing validation on login: if you really want to enable it, just overwrite the two corresponding event handlers:
AccountsTemplates.atInputEvents["focusout input"] = function(event, t){
        var fieldId = this._id;
        var rawValue = this.getValue(t);
        var value = this.fixValue(rawValue);
        // Possibly updates the input value
        if (value !== rawValue) {
            this.setValue(t, value);
        }

        // Client-side only validation
        if (!this.validation)
            return;
        var parentData = Template.parentData();
        var state = (parentData && parentData.state) || AccountsTemplates.getState();
        // No validation during signIn
        // if (state === "signIn")
        //     return;
        // Special case for password confirmation
        if (value && fieldId === "password_again"){
            if (value !== $("#at-field-password").val())
                return this.setError(AccountsTemplates.texts.errors.pwdMismatch);
        }
        this.validate(value);
    };
AccountsTemplates.atInputEvents["keyup input"] = function(event, t){
        // Client-side only continuous validation
        if (!this.continuousValidation)
            return;
        var parentData = Template.parentData();
        var state = (parentData && parentData.state) || AccountsTemplates.getState();
        // No validation during signIn
        // if (state === "signIn")
        //     return;
        var fieldId = this._id;
        var rawValue = this.getValue(t);
        var value = this.fixValue(rawValue);
        // Possibly updates the input value
        if (value !== rawValue) {
            this.setValue(t, value);
        }
        // Special case for password confirmation
        if (value && fieldId === "password_again"){
            if (value !== $("#at-field-password").val())
                return this.setError(AccountsTemplates.texts.errors.pwdMismatch);
        }
        this.validate(value);
    };

...mmm, it might be that you have to do it directly on the templates, since at the time your code is loaded all templates' events handlers are already set up...
Lets try something like above but with:
Template.atInput.events({
  "focusout input": function() {...},
  "keyup input": function() {...}
})

@splendido  ok...thx.... this works!
i have another little question. how to define the placeholder in input fields on login page?

See [this oldexample


python310Packages.docplex: 2.24.232 -> 2.25.236

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.docplex is: "IBM Decision Optimization CPLEX Modeling for Python"
meta.homepage for python310Packages.docplex is: "https://onboarding-oaas.docloud.ibmcloud.com/software/analytics/docloud/"
meta.changelog for python310Packages.docplex is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.24.231 with grep in /nix/store/r5jqks2qddh39n9vp119jdilw09kyn7z-python3.10-docplex-2.24.231
found 2.24.231 in filename of file in /nix/store/r5jqks2qddh39n9vp119jdilw09kyn7z-python3.10-docplex-2.24.231

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.docplex
python310Packages.qiskit
python310Packages.qiskit-finance
python310Packages.qiskit-optimization
python39Packages.docplex
python39Packages.qiskit
python39Packages.qiskit-finance
python39Packages.qiskit-optimization

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r5jqks2qddh39n9vp119jdilw09kyn7z-python3.10-docplex-2.24.231 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.docplex https://github.com/r-ryantm/nixpkgs/archive/2166282651c21e328f1af58e916aa488291b3053.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r5jqks2qddh39n9vp119jdilw09kyn7z-python3.10-docplex-2.24.231
ls -la /nix/store/r5jqks2qddh39n9vp119jdilw09kyn7z-python3.10-docplex-2.24.231/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages marked as broken and skipped:

python310Packages.qiskit
python310Packages.qiskit-finance
python310Packages.qiskit-optimization
python39Packages.qiskit
python39Packages.qiskit-finance
python39Packages.qiskit-optimization

2 packages built:

python310Packages.docplex
python39Packages.docplex

Maintainer pings
cc @drewrisinger for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.docplex is: IBM Decision Optimization CPLEX Modeling for Python
meta.homepage for python310Packages.docplex is: https://onboarding-oaas.docloud.ibmcloud.com/software/analytics/docloud/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.25.236 with grep in /nix/store/j2hxqyb1w5kjh3jmdfifp9bin0666mai-python3.10-docplex-2.25.236
found 2.25.236 in filename of file in /nix/store/j2hxqyb1w5kjh3jmdfifp9bin0666mai-python3.10-docplex-2.25.236

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.docplex
python310Packages.qiskit
python310Packages.qiskit-finance
python310Packages.qiskit-optimization
python311Packages.docplex
python311Packages.qiskit-finance
python311Packages.qiskit-optimization

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j2hxqyb1w5kjh3jmdfifp9bin0666mai-python3.10-docplex-2.25.236 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.docplex https://github.com/r-ryantm/nixpkgs/archive/fa85c4f3a6403252862c995bcd264b38006e1ab9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j2hxqyb1w5kjh3jmdfifp9bin0666mai-python3.10-docplex-2.25.236
ls -la /nix/store/j2hxqyb1w5kjh3jmdfifp9bin0666mai-python3.10-docplex-2.25.236/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages marked as broken and skipped:

python310Packages.qiskit
python310Packages.qiskit-finance
python310Packages.qiskit-optimization
python311Packages.qiskit-finance
python311Packages.qiskit-optimization

2 packages built:

python310Packages.docplex
python311Packages.docplex

Maintainer pings
cc @drewrisinger for testing.


ci: change pipeline running value

hey,
it did not start to build the container and i changed the "on:" values because we also do it like that in one of our other repos.

Good catch. So far we used version tags without v* prefix on dumptruck (we only tagged 2 GH releases as well it seems).  The release process based on v* tagging is fine, works well to trigger GH releases from the GH UI, which also auto generates release notes based on merged PRs.
Note: I've also found a link to docker hub in the readme that needs to be replaced as well.


Add Declaration property to Type

Sorry for the delay in looking at this.
These APIs try to mirror the general Clang APIs where possible and to not deviate from that too much. In this case, the actual clang::Type doesn't define any such API and instead only defines a few semi-related APIs such as getAs*Decl (https://clang.llvm.org/doxygen/classclang_1_1Type.html), of which ClangSharp already exposes AsCXXRecordDecl.
I'd be fine with also exposing the others (AsRecordDecl, AsTagDecl, and PointeeCXXRecordDecl), but don't think we should expose just a Declaration` variable to avoid any potential conflicts with future directions that Clang itself may take.

Interesting, somewhat surprising that the Clang C API has a declaration getter for types (clang_getTypeDeclaration) but the C++ API does not. Exposing the other getAsXXX() methods like you suggested seems to be the way to go.
In my own project, I can write a helper method which can iterate through the different types to find a declaration, similar to how clangsharp_Type_getDeclaration works.


Update index.md

Minor.  1 identation.  2 empty link to Appendix

Picked this up during other edits, so closed here.


I hide the status bar when clicked on tools. But, the Title of tools is missing in iPhone X and above as it is overlapping with the notch.

@RakeshMudireddy Have you solved it?

This problem looks the same as #220.


[Bug]: Airtime Purchase Transaction Not Reflected in App

Description
The status of an airtime purchase transaction, whether successful or not, is not reflected in the app. Instead, the message "Waiting for MPESA confirmation" persists.
Steps to reproduce

Set phone to Do Not Disturb mode
Open the Stax app
Tap on "Buy airtime" for Safaricom
Select the recipient network
Enter the recipient number (self)
Enter the amount
Tap on "Continue"
Enter MPESA PIN

Expected result
Having purchased the airtime and allowed a sufficient time to elapse, the app should show whether the purchase was successful or not.
Actual result
Having purchased the airtime and allowed a sufficient time to elapse, the app indicates that it is still waiting for the MPESA confirmation. This is despite the fact that a confirmation message was received from MPESA indicating that the purchase was successful. (See included screenshots)
Link to screenshots/screen recordings
https://drive.google.com/drive/folders/1ykF0YDOaz_aXIOpMXYKs-lkekbrzVNrK?usp=sharing
Device name
Nokia 7 Plus
Android OS
12
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

Encountered the same bug on 20th October 2022.


Configuring WandB logger broken / can't easily configure?

When switching config from:  _component_: torchtune.utils.metric_logging.DisLogger
to:
  _component_: torchtune.utils.metric_logging.WandBLogger
I hit TypeError: WandBLogger.__init__() missing 1 required positional argument: 'project'.
I see that I probably need to add project the nested config, but as a user this does give me a little overhead as I need to go into the logger impl, find what project is, understand it, figure out the type, and add something to my config. I could also understand if this is reasonable to expect from users, but it seems more overhead than before when I could simply pass in an override --metric_logger=wandb and I'd get wandB logging out of the box.
We should discuss the UX here and figure out whether @RdoubleA 's work to improve config instantiation will help.

Closing it since there are no updates since March. If it is still an issue, please reopen it! thanks :)