🔧react-native-vision-camera:buildCMakeRelWithDebInfo FAILED - 'fbjni/fbjni.h' file not found

How were you trying to build the app?
Originally, the build ran well, but when I tried to build the app in my Android studio, I suddenly encountered a build error.
It can't seem to find the file 'fbjni/fbjni.h', what should I do?
Full build logs
> Task :react-native-vision-camera:buildCMakeRelWithDebInfo FAILED
w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vision-camera:buildCMakeRelWithDebInfo'.
> Build command failed.
  Error while executing process /Users/jinheui/Library/Android/sdk/cmake/<IP_ADDRESS>88404/bin/ninja with arguments {-C /Users/jinheui/hjh/success/tpay/node_modules/react-native-vision-camera/android/.cxx/RelWithDebInfo/6l211t5t/armeabi-v7a VisionCamera}
  ninja: Entering directory `/Users/jinheui/hjh/success/tpay/node_modules/react-native-vision-camera/android/.cxx/RelWithDebInfo/6l211t5t/armeabi-v7a'
  [1/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o -c ../../../../src/main/cpp/java-bindings/JImageProxy.cpp
  In file included from ../../../../src/main/cpp/java-bindings/JImageProxy.cpp:5:
  ../../../../src/main/cpp/java-bindings/JImageProxy.h:8:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [2/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o -c ../../../../src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp
  In file included from ../../../../src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp:5:
  ../../../../src/main/cpp/java-bindings/JFrameProcessorPlugin.h:8:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [3/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/FrameHostObject.cpp.o -c ../../../../src/main/cpp/FrameHostObject.cpp
  In file included from ../../../../src/main/cpp/FrameHostObject.cpp:5:
  ../../../../src/main/cpp/FrameHostObject.h:9:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [4/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o -c ../../../../src/main/cpp/VisionCameraScheduler.cpp
  In file included from ../../../../src/main/cpp/VisionCameraScheduler.cpp:5:
  In file included from ../../../../src/main/cpp/VisionCameraScheduler.h:8:
  /Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni/ReactCommon/CallInvokerHolder.h:11:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [5/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o -c ../../../../src/main/cpp/CameraView.cpp
  In file included from ../../../../src/main/cpp/CameraView.cpp:5:
  ../../../../src/main/cpp/CameraView.h:8:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [6/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -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
  ../../../../src/main/cpp/VisionCamera.cpp:2:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [7/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o -c ../../../../src/main/cpp/JSIJNIConversion.cpp
  In file included from ../../../../src/main/cpp/JSIJNIConversion.cpp:5:
  ../../../../src/main/cpp/JSIJNIConversion.h:9:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  [8/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
  FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
  /Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64 --sysroot=/Users/jinheui/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/sysroot  -DVisionCamera_EXPORTS -I../../../../build/fbjni-0.5.1-headers.jar -I../../../../build/third-party-ndk/boost -I../../../../build/third-party-ndk/double-conversion -I../../../../build/third-party-ndk/folly -I../../../../build/third-party-ndk/glog -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/React/Base -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/jni -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/callinvoker -I/Users/jinheui/hjh/success/tpay/node_modules/react-native/ReactCommon/jsi -I/Users/jinheui/hjh/success/tpay/node_modules/hermes-engine/android/include -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/AnimatedSensor -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Tools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SpecTools -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/SharedItems -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/Registries -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/headers/LayoutAnimations -I/Users/jinheui/hjh/success/tpay/node_modules/react-native-reanimated/Common/cpp/hidden_headers -I../../../../src/main/cpp -DFOLLY_NO_CONFIG=1 -DFOLLY_HAVE_CLOCK_GETTIME=1 -DFOLLY_HAVE_MEMRCHR=1 -DFOLLY_USE_LIBCPP=1 -DFOLLY_MOBILE=1 -DON_ANDROID -DONANDROID -DFOR_HERMES=false -O2 -g -DNDEBUG -fPIC   -std=gnu++14 -MD -MT CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o -MF CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o.d -o CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o -c ../../../../src/main/cpp/FrameProcessorRuntimeManager.cpp
  In file included from ../../../../src/main/cpp/FrameProcessorRuntimeManager.cpp:5:
  ../../../../src/main/cpp/FrameProcessorRuntimeManager.h:7:10: fatal error: 'fbjni/fbjni.h' file not found
  #include <fbjni/fbjni.h>
           ^~~~~~~~~~~~~~~
  1 error generated.
  ninja: build stopped: subcommand failed.

* 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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 7 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 4m 33s
608 actionable tasks: 602 executed, 6 up-to-date

Project dependencies
"dependencies": {
    "@actbase/react-daum-postcode": "^1.0.1",
    "@adrianso/react-native-device-brightness": "^1.2.7",
    "@react-native-async-storage/async-storage": "^1.15.5",
    "@react-native-community/masked-view": "^0.1.10",
    "@react-native-community/netinfo": "^8.3.0",
    "@react-native-firebase/app": "^14.7.0",
    "@react-native-firebase/messaging": "^14.7.0",
    "@react-native-picker/picker": "^2.1.0",
    "@react-navigation/bottom-tabs": "^6.0.9",
    "@react-navigation/devtools": "^6.0.4",
    "@react-navigation/native": "^6.0.6",
    "@react-navigation/stack": "^6.0.11",
    "@reduxjs/toolkit": "^1.6.2",
    "appcenter": "^4.4.4",
    "appcenter-analytics": "^4.4.4",
    "appcenter-crashes": "^4.4.4",
    "axios": "^0.21.4",
    "babel-plugin-root-import": "^6.6.0",
    "date-fns": "^2.23.0",
    "iamport-react-native": "^1.6.3",
    "lodash-es": "^4.17.21",
    "react": "17.0.2",
    "react-hook-form": "^7.0.4",
    "react-native": "^0.68.2",
    "react-native-calendars": "^1.1258.0",
    "react-native-code-push": "^7.0.4",
    "react-native-config": "^1.4.2",
    "react-native-dashed-line": "^1.1.0",
    "react-native-device-info": "^8.7.0",
    "react-native-dropdownalert": "^4.5.1",
    "react-native-flipper": "^0.122.0",
    "react-native-gesture-handler": "^1.10.3",
    "react-native-image-picker": "^4.7.1",
    "react-native-input-scroll-view": "^1.11.0",
    "react-native-iphone-x-helper": "^1.3.1",
    "react-native-keyboard-aware-scroll-view": "^0.9.5",
    "react-native-modal": "^13.0.0",
    "react-native-month-year-picker": "^1.8.1",
    "react-native-orientation-locker": "^1.4.0",
    "react-native-permissions": "^3.1.0",
    "react-native-print": "^0.11.0",
    "react-native-qrcode-svg": "^6.2.0",
    "react-native-reanimated": "^2.8.0",
    "react-native-safe-area-context": "^3.2.0",
    "react-native-scalable-image": "^1.1.0",
    "react-native-screens": "^3.10.1",
    "react-native-share": "^7.8.0",
    "react-native-signature-canvas": "^4.5.0",
    "react-native-sound": "^0.11.1",
    "react-native-splash-screen": "^3.2.0",
    "react-native-status-bar-height": "^2.6.0",
    "react-native-svg": "^13.10.0",
    "react-native-table-component": "^1.2.1",
    "react-native-version-check": "^3.4.3",
    "react-native-viewport-units": "0.0.5",
    "react-native-vision-camera": "^2.13.5",
    "react-native-walkthrough-tooltip": "^1.4.0",
    "react-native-webview": "^11.22.7",
    "react-query": "^3.31.0",
    "react-redux": "^7.2.4",
    "react-spring": "^9.3.2",
    "redux": "^4.1.0",
    "redux-actions": "^2.6.5",
    "redux-flipper": "^2.0.1",
    "redux-persist": "^6.0.0",
    "rn-fetch-blob": "^0.12.0",
    "styled-components": "^5.2.3",
    "victory-native": "^36.6.8",
    "vision-camera-code-scanner": "^0.2.0",
    "vision-camera-ocr": "^1.0.0"
  },
  "devDependencies": {
    "@babel/core": "^7.18.5",
    "@babel/runtime": "^7.18.3",
    "@react-native-community/eslint-config": "^3.0.2",
    "@types/iamport-react-native": "^1.5.2",
    "@types/jest": "^26.0.22",
    "@types/lodash-es": "^4.17.5",
    "@types/react": "^17.0.3",
    "@types/react-native": "^0.64.2",
    "@types/react-native-calendars": "^1.505.3",
    "@types/react-native-version-check": "^3.4.4",
    "@types/react-test-renderer": "^17.0.1",
    "@types/redux-actions": "^2.6.1",
    "@types/styled-components": "^5.1.14",
    "@types/styled-components-react-native": "^5.1.1",
    "babel-jest": "^28.1.1",
    "babel-loader": "^8.2.2",
    "babel-plugin-module-resolver": "^4.1.0",
    "eslint": "^8.17.0",
    "jest": "^28.1.1",
    "metro-react-native-babel-preset": "^0.71.1",
    "react-dom": "17.0.1",
    "react-native-codegen": "^0.0.8",
    "react-query-native-devtools": "^3.0.1",
    "react-test-renderer": "17.0.2",
    "typescript": "^4.2.4"
  },

VisionCamera Version
2.13.5
Target platforms
Android
Operating system
MacOS
Can you build the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
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.

Did you clear your cache?

@Noma98 try adding these scripts to your package.json:
"clean": "rm -rf $TMPDIR/react-* && watchman watch-del-all && npm cache clean --force",
"clean:android": "cd android && ./gradlew clean",

@Noma98 try adding these scripts to your package.json:
"clean": "rm -rf $TMPDIR/react-* && watchman watch-del-all && npm cache clean --force",
"clean:android": "cd android && ./gradlew clean",

here is my package json
"react-native": "0.68.2",
"react-native-vision-camera": "^2.15.2",

and i do rm -rf node_module with https://github.com/mrousavy/react-native-vision-camera/issues/2514#issuecomment-1945341441 and now its works.


fix powershell command to install 'Application-Server' role

Hi there, under point 7 in the section "Join Windows Server 2016 to your domain" the installation command ist faulty.
You can't install the 'Application-Server' role anymore.
Please fix that in the documentation.
best regards
Thorsten
[Enter feedback here]

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

ID: ba9d25f8-acca-35b0-202b-f83a0a8c1e45
Version Independent ID: bc769b6d-0c19-2590-a834-743620172fe9
Content: Configure Windows Server 2016 or later versions for MIM 2016 SP2
Content Source: MIMDocs/prepare-server-ws2016.md
Product: microsoft-identity-manager
GitHub Login: @billmath
Microsoft Alias: billmath

Thank for submitting this. I have created a work item for it and will reviewing this in the coming weeks. I am not sure what the timeline will be, so I am going to close this for now. But once I have an update I will drop it in here and let you know.
Thank you!
Bill
#please-close


#940: Add Aqara H1 Wireless Remote Double Rocker Version WRS-R02, variant 3

With no model info
endpoint 1 declared as color dimmer (261)
No input/output declared

Big hack line 304: MODELS_INFO: [(LUMI, "lumi.remote.b28ac1"), (None, None)],
But, how can I do otherwise when I receive manufacturer=None and model=None ...
In the plugin-zigbee, I change into lumi.remote.b28ac1.json logical ids with
"logicalId": "1::18::0" and "logicalId": "2::18::0"

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.727%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5150

Relevant Lines:
7180

💛  - Coveralls

Codecov Report

Merging #1676 (903d47d) into dev (57a68a2) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #1676   +/-   ##
=======================================
  Coverage   71.72%   71.72%
=======================================
  Files         236      236
  Lines        7180     7180
=======================================
  Hits         5150     5150
  Misses       2030     2030

Impacted Files
Coverage Δ

zhaquirks/xiaomi/aqara/remote_h1.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

I have had to pair some devices several times because they did not report the manufacturer or model correctly.
Have you tried pairing the device again? Make sure to keep your device awake. You can usually do this by briefly pressing the button while the pairing is taking place.

none for these values is from a failed pairing. We will not add that to quirks

Closing for now. The device should be picked up as one of the other variants already.
Make sure you're running the somewhat up-to-date firmware on your coordinator (for Aqara manufacturer codes) and try re-pairing the device multiple times while pressing buttons on it.
A pairing with manufacturer=None, model=None, and no clusters reported is a failed or incomplete pairing.


Which license applies to cdm.json files?

The legal notice states the following:

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

What license do the cdm.json files, e.g. Contact.cdm.json, fall under, the CCA license or MIT?

Alan, thanks for your question.  JSON files in this repository are covered under the LICENSE file, i.e. https://github.com/Microsoft/CDM/blob/master/LICENSE


Is there a plan for 32 bit UWP apps to support WebView 2 in the future?

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

ID: a41e6607-2207-13a3-e637-464e3504e0d4
Version Independent ID: a41e6607-2207-13a3-e637-464e3504e0d4
Content: Publish a UWP WebView2 app to the Microsoft Store - Microsoft Edge Development
Content Source: microsoft-edge/webview2/how-to/publish-uwp-app-store.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thank you for your question. Can you please ask it again on this support/feedback repository for WebView2: https://github.com/MicrosoftEdge/WebView2Feedback
The current repo is about docs changes only. You'll get more support on the WebView2Feedback repository. Thanks for your understanding.


[SignalR/Java] JCenter version information not synchronized with Maven Central

A version of SignalR appears as a listing on Bintray's JCenter. However it is very out of date and missing some important fixes. The latest version that appears there is v1.0.0-preview3-35501
I do realise that I can just pull from central, but it was quite misleading seeing the package present in JCenter (I actually set up a private CD pipeline to publish Signal R to our maven before I realised it was in central).  It would probably be a good idea to either pull the listing, or ensure it's synchronized with Maven Central.

I believe jcenter automatically mirrors Maven Central, you just need to be patient. We only pushed to Maven a few hours ago.

Yeah, like Brennan said, jCenter should mirror Maven Central, I guess it just takes a little longer to index the new items. It should be there soon.

Oh apologies. I was struggling to see when this version was published.
Didn't realize it was yesterday.
On Wed, 5 Dec 2018, 01:09 Mikael Mengistu<EMAIL_ADDRESS>wrote:

Yeah, like Brennan said, jCenter should mirror Maven Central, I guess it
just takes a little longer to index the new items. It should be there soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/AspNetCore/issues/4387#issuecomment-444294794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AISSWSGD_NAlARpgVU2xN3uvg5i9HMu4ks5u1wC6gaJpZM4ZAV68
.

It appears that the package information still hasn't updated

I'll take a look

JCenter has the package now https://bintray.com/bintray/jcenter/com.microsoft.signalr%3Asignalr/1.0.0

So I guess for future reference this takes about a month to update? Kind of unfortunate.


Add custom-job.yaml, RAPIDS_BASE_BRANCH, Codecov support

This PR adds features needed for cuDF GitHub Actions workflows:

A workflow called custom-job.yaml has been added that can be used for an arbitrary job (build, test, ...) that is not a full matrix build like typical C++ or Python builds/tests. This is needed for Java tests and notebook tests, which are only run on one arch/version combination and thus can't use the existing C++/Python testing workflows.

"Get PR Info" steps inject RAPIDS_BASE_BRANCH into the CI environment (needed for copyright style checks).

Codecov support.

Just want to add another note based on offline discussions. We opted to include custom-job.yaml to this repository to keep the environment variable standardization snippet below in the same place as the other workflows which use similar standardization. This way if we need to update that logic in the future, it can all be done in this single repository.

https://github.com/rapidsai/shared-action-workflows/blob/3546a5fedd6a098321061e1d02243f4d80cbbeba/.github/workflows/custom-job.yaml#L52-L56


Questions about the data proportion of each task

The OFA pre-training phase uses many different types of data, such as caption, VQA, and VG. In each epoch, is there any deliberate adjustment of the proportion of these data? I have the following two specific questions:

From the code,  I see that the sampling frequency of MLM and Image Infilling has been reduced to 1/8. This is reasonable because the tsv file of the visual language task contains multiple tasks. But I still wonder if the ratio of 1/8 has been specially adjusted by experimental verification.
For the VL tsv, I cannot know the proportion of each task. In my opinion, CC12M has too many data. It seems unreasonable to shuffle directly with other tasks. Do you have any experience in the proportion of data in each task?

Thank you!

@zzhanghub

We haven‘t experimentally tested this ratio. The ratio 1/8 was chosen based on a trade-off between effectiveness and efficiency.
Although the caption data is larger than others, their proportions are not very disparate, so for convenience, we directly shuffle all the VL data.

I found that you have raised a lot of questions in our repo and sometimes I can't reply to you in time, would you mind sending me an email so we can communicate via email? (or other


Handle handLeft and handRight in itemTypes.js

Most hand wearables look fine in both hands, but some (like the REKT sign) only looks good in the left hand. So we should handle left and right hands separately when adding the items.

I added handLeft and handRight to the itemTypes.js file.   I set the REKT sign wearable to handLeft.   Are there other wearables we should set to handLeft or handRight ?

Yes so far I believe REKT sign is the only one. The DAO Egg will probably also be a single hand wearable. Closed for now.


Unable to load list of branches and unable to switch to other branches

When I open private repository (I have write access in this repository), I am unable to switch branch.
Regardless of being in "code" or "commits" tab, when I tap on branch name, I always see information that loading branch lists resulted in an error.
It seems that this issue doesn't exists on public repositories.

Do you have a lot of branches and tags? Just tested on a private repository and had no problems.

15 active branches (26 total).
Maybe this is related with old Android version (4.3)?

I also have access to repository mentioned by @kedziorm and it ends up with the same error (Android 5.1).

@Meisolsson @piaseckim Issue exists on Android 6.0 phone as well.
I thought that it is caused by "_" and "-" characters in branches names and tags, so I created repository with such characters: https://github.com/kedziorm/This_is_just_for_testing
but it seems this is not the case.
I've tried to debug PocketHub (please note, I have zero experience in debugging Android soft), so I downloaded Android Studio.
Unfortunately, even though I set in gradle-wrapper.properties, pockethub_github_client and two other settings, each time when I try to run, I see:

You won't be able to login, because the oauth client or secret isn't set
Read the README.md: https://github.com/pockethub/PocketHub#setup-environment

and it is correct - I am unable to authenticate and as a result I am unable to debug.

@kedziorm The properties doesn't belong into the gradle-wrapper.properties file.
See here for the possible ways of setting the properties: https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_properties_and_system_properties
I suggest to use the grade.properties file in your gradle user home directory

Okay, now I'm receiving different error (when trying to log in in Pocket Hub):
E/AndroidRuntime: FATAL EXCEPTION: main
                  Process: com.github.pockethub.android, PID: 3182
                  java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=0, result=-1, data=Intent { dat=https://github.com/... }} to activity {com.github.pockethub.android/com.github.pockethub.android.accounts.LoginActivity}: java.lang.IllegalStateException: Missing required properties: code
                      at android.app.ActivityThread.deliverResults(ActivityThread.java:3699)
                      at android.app.ActivityThread.handleSendResult(ActivityThread.java:3742)
                      at android.app.ActivityThread.-wrap16(ActivityThread.java)
                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1393)
                      at android.os.Handler.dispatchMessage(Handler.java:102)
                      at android.os.Looper.loop(Looper.java:148)
                      at android.app.ActivityThread.main(ActivityThread.java:5417)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
                   Caused by: java.lang.IllegalStateException: Missing required properties: code
                      at com.meisolsson.githubsdk.model.request.$$AutoValue_RequestToken$Builder.build($$AutoValue_RequestToken.java:147)
                      at com.github.pockethub.android.accounts.LoginActivity.onUserLoggedIn(LoginActivity.java:143)
                      at com.github.pockethub.android.accounts.LoginActivity.onActivityResult(LoginActivity.java:210)
                      at android.app.Activity.dispatchActivityResult(Activity.java:6428)
                      at android.app.ActivityThread.deliverResults(ActivityThread.java:3695)
                      at android.app.ActivityThread.handleSendResult(ActivityThread.java:3742)
                      at android.app.ActivityThread.-wrap16(ActivityThread.java)
                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1393)
                      at android.os.Handler.dispatchMessage(Handler.java:102)
                      at android.os.Looper.loop(Looper.java:148)
                      at android.app.ActivityThread.main(ActivityThread.java:5417)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

I guess that those values are caused by incorrect Callback URL or other settings that I provided when registering new app.
Could you be so kind and prepare sample configuration in the readme file for this repo, please?
To be honest, I'm really confused why I need to register application to debug Android app and I have completely no idea how callback URL should look like. You're saying that it should be your_schema://whatever_you_want, but what is your_schema?

This seems to be solved.

@Meisolsson, @piaseckim This issue still exists on my phone although currently I use Android 6.0 phone. Will it be possible to re-open it? How can I help to reproduce it?

@kedziorm Are you using the version on the Play Store or the version in master?

@Meisolsson I use version from the Play Store.

I think we fixed it in the master version here but I've haven't had the time to upload the current version.


Lucky Explorer can't be applied.

Version: dungeons_gear-1.16.5-3.1.15-beta.jar
Forge: 1.16.5 36.2.39
Currently running DG in a modpack and the enchantment "Lucky Explorer" can't be applied to anything except the set it comes on. If you get it on a book, it's unusable.

did you remove it from the enchantment blacklist in the config? Lucky explorer is sealed away by default to prevent cries of imbalance.

Jackiecrazy already answereed this. You should also no longer be getting it on a book if all is well.


StyleTags lack sourceURL

Repro steps:

Check out Polymer tutorial: http://www.polymer-project.org/docs/start/tutorial/step-1.html.
Download it and open the 'finished/index.html'
Open devtools, try to edit styles for the small "heart" icon.

Styles sidebar panel is missing urls / lines against the CSS rules.

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Invalid warning and errors notifications showing up

With the new skills workflow if the "Composer Local" endpoint is chosen we dont need to check for an empty endpoint url in the settings.
Missing skill manifest should not be a warning shown on the Root Bot
A warning for missing MsAppID is shown. This warning is not required. An MSAppID or AppPassword is no longer required to call skills

I already fixed the 2rd item.
2. Missing skill manifest should not be a warning shown on the Root Bot

Will sync with @lei9444 see how to address them all.


CLI --react results in 400 error

This is a blocker!
npx @hilla/cli init --react --auth react-with-auth
Creating application 'react-with-auth'
Unable to create project: 400

Trying to create React-based Hilla app results in a 400 error.

Hi, thanks for reporting. Sadly the --auth option in combination with React is not supported yet. Does it work without --auth for you?

@platosha Yes it works without --auth. A better error message would be great!


IRI-design

This information about our ID/IRI-policy has still to be integrated in the documentation.:
IRIs of the vocabulary
The general IRI of the vocabulary (the SKOS-file) will have the following form:
https://w3id.org/nfdi4cat/[IDSPACE]/releases/YYYY-MM-DD/[IDSPACE].ttl
or
https://w3id.org/nfdi4cat/[IDSPACE].ttl

The latest released version will be accessible at the root level https://w3id.org/nfdi4cat/. All that is also older releases are accessible under https://w3id.org/nfdi4cat/[IDSPACE]/releases/. Releases use the release date in iso-format as version specifier.
The [IDSPACE]-key for this vocabulary is "voc4cat". The IDSPACE-key is what distinguishes it from other vocabularies. The term IDSPACE is taken from obofoundry.
IRIs of elements in the vocabulary
The general IRI for a concrete element is
https://w3id.org/nfdi4cat/[IDSPACE]/releases/YYYY-MM-DD/[IDSPACE]_[ID]
or
https://w3id.org/nfdi4cat/[IDSPACE]_[ID]

[ID] stands for the ID of the concept/collection in the vocabulary. In  voc4cat it is an integer that is left-padded with zeros to a total length of seven digits. For example, the IRI for a concept with the ID of 123 is
https://w3id.org/nfdi4cat/voc4cat_0000123
Compact IRI notation (CURIE)
The preferred CURIE notation is to use the IDRANGE as prefix. For example, the IRI
https://w3id.org/nfdi4cat/voc4cat_0000123
would be written in CURIE-form as
voc4cat:0000123.
Here the prefix voc4cat stands for https://w3id.org/nfdi4cat/voc4cat_.
This style matches OBOs, where for example http://purl.obolibrary.org/obo/RO_0002202 is typically written as CURIE "RO:0002202", see https://obofoundry.org/id-policy.html

Documentation about the general IRI design in vo4cat-template based vocabularies has been added in https://github.com/nfdi4cat/voc4cat-template/pull/31


How to make an optional property with a default value?

Hello, first of all, thank for this awesome library, it is making wonders in my user-data interactions.
I want to define an schema for user input that has an optional field with a default value. However, it is being impossible for me to make the runtime behaviour match the type, maybe I'm getting something wrong.
What I want, is the field to be optional, and when not provided, or provided as undefined, use the default value. If I want to have this behaviour I can't have the field optional in the generated type, and if I manage to make it optional in the generated type, then it will not get a default value during runtime.
Let me explain it with code:
import { Timestamp } from 'firebase/firestore';
import { z } from 'zod';

export const someSchema = z.object({
  id: z.string(),
  timestamp: z.instanceof(Timestamp),
  type: z.enum(['fever', 'constipation']),
  notes: z.string().optional().default(''),
});

export const someInput = someSchema
  .omit({ id: true })
  .merge(
    z.object({
      timestamp: z
        .date()
        .optional()
        .default(() => new Date()),
    }),
  )
  .partial({
    notes: true,
  });

export const schemaArray = z.array(someSchema);

export type Schema = z.infer<typeof someSchema>;
export type SchemaInput = z.infer<typeof someInput>; // <- Here I expect timestamp to be optional, but it is required

function a({ type, timestamp, notes}: SchemaInput){
  someInput.parse({
  type, timestamp, notes
  })
}

a({type: 'fever'}) <- Error, timestamp is required

I see you're using z.infer, have you tried to check what z.input and z.output looks like? Are they both the same as z.infer? It looks like it's working as you expect on my machine:

z.input and z.output are briefly mentioned in the docs in the type inference-section.

Oh, yeah, that looks exactly like what I need.
I remember reading it and thought: "this will came handy sometime". However
I think I associated it with the function implementation to type function
inputs.
I'll give it a try and close the issue if it works. Many thanks
El lun., 27 jun. 2022 13:37, Torleif Berger @.***>
escribió:

I see you're using z.infer, have you tried to check what z.input and
z.output looks like? Are they both the same as z.infer? It looks like
it's working as you expect on my machine:
[image: image]
https://user-images.githubusercontent.com/142162/175932453-1e498529-626a-45a2-b50d-4dedf24d432b.png
z.input and z.output are briefly mentioned in the docs in the type
inference https://zod.dev/?id=type-inference-section.
—
Reply to this email directly, view it on GitHub
https://github.com/colinhacks/zod/issues/1230#issuecomment-1167244200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARKJWJG26RYQT4T6NEMKQTVRGHA7ANCNFSM5Z3ZQ5BQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

That worked out perfectly, thanks!


fix: if prscd can not connect to zipper when creating, do not cache it

This is not the best solution, but makes service way better, at least prscd will try to reconnect zipper next time.

Use yomo.WithSourceReConnect() and yomo.WithSfnReConnect() to make it continuously connect until it succeeds.

@woorui updated, please review.


About us page is not looking professional

Redesign the about us page and make it more user friendly it is not looking professional it is looking like we have using some template about us page should create a good user impact

@Sawan-Kushwah work on it


wasm demo multi-lingual screen reader accessibility

Need reasonable behavior for screen reader and keyboard navigation with wasm demo.
Goals:

Use wasm demo as proof of concept check for fundamental design flaws that might interfere with accessibility.
When using ime-engine to compose a multi-lingual phrase like, "字 and 词 are similar, but こんにちは means something else", allow for screen reader and browser text-to-speech API to select appropriate voice for each word. (open questions: Is unicode encoding sufficient for voice selection? Do words not in primary language need metadata annotation of language?)
Prove that ime-engine's use of tab, space, return, etc. for text composition is compatible with using keyboard navigation in accessible web app with chat window UI.

Considerations:

[ ] Any of (keyboard | mouse | touch) should work for focusing on the input element for composing text
[ ] Consider IME text composition keyboard shortcuts (tab, space) ... how should they interact with keyboard navigation ???
[x] When text is appended to the log, only newly added lines should be read
[ ] Multi-lingual sentences should use correct voice to match language of each word [appears not possible]
[ ] Consider homophone picking UI showing hanzi suggestions ... how should it interact with screen reader ???
[ ] Consider possible text to speech chat command, like /say 词, intended for non-assisted use ... how would it behave with screen reader ???

related: #18 (guided tutorial dialog for wasm demo)

Web Content Accessibility Guidelines WAI-ARIA Overview: https://www.w3.org/WAI/standards-guidelines/aria/
https://www.intercom.com/blog/messenger-accessibility/ (onClick/onKeyDown/tabIndex/role, aria-label, aria-live)
https://www.nomensa.com/blog/2010/7-tips-for-multi-lingual-website-accessibility (lang="..." attribute)
https://accessibility.psu.edu/foreignlanguages/langtaghtml/ (language codes for use with lang)

An overview of accessible web applications and widgets: https://developer.mozilla.org/en-US/docs/Web/Accessibility/An_overview_of_accessible_web_applications_and_widgets
Keyboard-navigable JavaScript widgets: https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets
ARIA live regions: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions
Using the aria-label attribute: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute

Screen reader testing notes:

ChromeVox does okay for English, but silently skips over Latin letters with diacritics and Unicode CJK characters.
VoiceOver does better with more diacritics, but it says "...ideograph" instead of reading CJK characters.
VoiceOver with Safari seems okay. But, VoiceOver with Chrome is very glitchy. Seems to be known issue.

WebAIM survey about popular screen readers:
https://webaim.org/projects/screenreadersurvey8/#browsercombos

IETF BCP 47 on the use of lang="zh-CN" vs lang="zh-cmn" or lang="cmn":
https://tools.ietf.org/html/bcp47#section-4.1.2
Also, related pages from W3C:

Language tags in HTML and XML: https://www.w3.org/International/articles/language-tags/
Choosing a Language Tag (FAQ page): https://www.w3.org/International/questions/qa-choosing-language-tags#langsubtag

Summary:

lang="zh-CH" is the old code for Mainland Simplified Chinese (still okay to use)
lang="cmn" is the new, more correct code


Material UI Warning

When a test need a mount
    Invariant Violation: Expected onBeforeMountComponent() parent and onSetChildren() to be consistent (5 has parents 0 and 4).```

Fixed since we have rewritten tests.

What was the fix? I know this isn't StackOverflow, but this is literally the only reference to this issue I've been able to find.

We use this fix https://github.com/callemall/material-ui/issues/5078


How to make

I want to import css from file and make in to

Please follow the issue template and post questions on https://spectrum.chat/next-js.


Run 'cargo fmt --all'

r? @ehuss
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! 😄
@bors r+

:pushpin: Commit 63a9c7aa6d54ff0580288f1a01795a29b3ea1c75 has been approved by ehuss

:hourglass: Testing commit 63a9c7aa6d54ff0580288f1a01795a29b3ea1c75 with merge ba5aac51e149a8ad29cef75b550f28c00f3cf3a4...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: ehuss
Pushing ba5aac51e149a8ad29cef75b550f28c00f3cf3a4 to master...


Toggling Section title

is there a way to hide the section title ?

@ghatighorias
There is no way to hide the section title.
But you can use a section header height instead of hiding.
please try like the following code:
<sv:SettingsView>
    <sv:Section HeaderHeight="0">
        <sv:LabelCell Title="Label" ValueText="value" />
    </sv:Section>
</sv:SettingsView>

Thank you.

i had to do some minor changes for this in the code but your suggestion is mostly working :).
thanks


Fix VoiceHandler memory access out of bounds on WebGL

Description
This should fix issue #323, where for some AudioClip lengths the GetAmplitude method tried to read data from the clip even if the remaining samples were 0.
How to Test

add VoiceHandler component on an avatar
set build target to webGL and run the built application
let the AudioSource referenced by the VoiceHandler reproduce AudioClips with various lengths

Checklist

[ ] Tests written or updated for the changes.
[ ] Documentation is updated.
[ ] Changelog is updated.

@mennetorelli Thanks for yor effort! I tested this locally, and I noticed that there is still a small percentage to error, but I cant reliably reproduce it (it errors now like 1 in 100 audio files).
But this is already a huge improvement.


onSuccess fixes

Related to #375  #374

Description
This PR will introduce these fixes:

fix set success to true in paymentDialog
fix calling onSuccess when no amount set
Set amount to number in onSuccess callback

Test plan
Open the project, run yarn build  and test if onSuccess function is called and if it returns the amount properly
@lissavxo

Why is removing the big number lib necessary here? What was wrong with it?

Why is removing the big number lib necessary here? What was wrong with it?

We removed BigNumber from form the Amount param that was being sent in Onsucces function. Now we are returning a number instead.
BigNumber  returns a object so we changed it to be a number instead to have only the amount sent.
we can also adjust to try to extract the number from the BigNumber object, so it matches the value we are showing in the toast.


API use case

i think the OpenAPIEndpointChain doesn't use OpenAI functions / is different from get_openapi_chain

i think the OpenAPIEndpointChain doesn't use OpenAI functions / is different from get_openapi_chain

i see, ok. it is from here.
Maybe this pre-dates functions? In which case, we may simple opt to exclude it.


compile error with gcc 7.1.0

the latest git version makes compile error with gcc 7.1.0 as follows:
gcc/7.1.0/include/c++/7.1.0/utility:147:12: error: partial specialization of 'struct std::__is_tuple_like_impl<std::pair<_T1, _T2> >' after instantiation of 'struct std::__is_tuple_like_impl<std::pair<unsigned int, unsigned int> >' [-fpermissive]
struct __is_tuple_like_impl<std::pair<_T1, _T2>> : true_type
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cpptoo: partition_snapshooter.cpp
cpptoo: graph_partitioner.cpp
cpptoo: wcycle_partitioner.cpp
Any idea?

I will issue a fix soon, can you in the meanwhile use an older version of gcc?
Best
Christian

Hi,
I just tried to reproduce the error, however, everything works fine with gcc-7.1.0 on my machine. Can you try the latest state of the git hub repository and tell me if you still get the error?
Thanks
Christian

I pulled the repository and tried again to get the following error:
In file included from /opt/HPC/Compilers/gcc/7.1.0/include/c++/7.1.0/algorithm:60:0,
                 from interface/../lib/partition/uncoarsening/separator/area_bfs.h:8,
                 from interface/kaHIP_interface.cpp:32:
/opt/HPC/Compilers/gcc/7.1.0/include/c++/7.1.0/utility:147:12: error: partial specialization of 'struct std::__is_tuple_like_impl<std::pair<_T1, _T2> >' after instantiation of 'struct std::__is_tuple_like_impl<std::pair<unsigned int, unsigned int> >' [-fpermissive]
     struct __is_tuple_like_impl<std::pair<_T1, _T2>> : true_type
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    cpptoo: size_constraint_label_propagation.cpp
    cpptoo: initial_partitioning.cpp
    cpptoo: initial_partitioner.cpp

I am compiling this library for OpenFOAM-plus. Also I found that kahip is compiled with scon but OpenFOAM-plus provide its own compile script, makeKAHIP. But, I am not sure if those scripts make difference cause I am not familiar with scon. FYI, I uploaded the building script.
makeKAHIP.tar.gz
.

can you try to clone the repository and run ./compile.sh?
does that work for you?

I installed scons and tried compile.sh. It works. So, I guess the problem is in the building script, makeKAHIP.

thanks! Can you help with this @olesenm?

Yes, sure. I made an issue on openfoam.com

Issue resolved - https://develop.openfoam.com/Development/OpenFOAM-plus/issues/744
Newer gcc seems to require -fpermissive to compile using its own STL files.


Is cargo fmt no longer working properly

Which part is this question about
Code formatter.
Describe your question
I've noticed recently that running cargo fmt while I'm editing files doesn't always seem to catch problems. Running rustfmt directly will work. For instance, running cargo fmt on the parquet crate yields no output.
% cargo +stable fmt -p parquet -v -- --check
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/arrow_reader.rs"
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/arrow_statistics.rs"
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/arrow_writer.rs"
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/compression.rs"
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/encoding.rs"
[bench (2021)] "/Users/seidl/src/arrow-rs/parquet/benches/metadata.rs"
[example (2021)] "/Users/seidl/src/arrow-rs/parquet/examples/async_read_parquet.rs"
[example (2021)] "/Users/seidl/src/arrow-rs/parquet/examples/read_parquet.rs"
[example (2021)] "/Users/seidl/src/arrow-rs/parquet/examples/read_with_rowgroup.rs"
[example (2021)] "/Users/seidl/src/arrow-rs/parquet/examples/write_parquet.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-concat.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-fromcsv.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-index.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-layout.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-read.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rewrite.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rowcount.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-schema.rs"
[bin (2021)] "/Users/seidl/src/arrow-rs/parquet/src/bin/parquet-show-bloom-filter.rs"
[lib (2021)] "/Users/seidl/src/arrow-rs/parquet/src/lib.rs"
[test (2021)] "/Users/seidl/src/arrow-rs/parquet/tests/arrow_reader/mod.rs"
[test (2021)] "/Users/seidl/src/arrow-rs/parquet/tests/arrow_writer_layout.rs"
rustfmt --edition 2021 --check /Users/seidl/src/arrow-rs/parquet/benches/arrow_reader.rs /Users/seidl/src/arrow-rs/parquet/benches/arrow_statistics.rs /Users/seidl/src/arrow-rs/parquet/benches/arrow_writer.rs /Users/seidl/src/arrow-rs/parquet/benches/compression.rs /Users/seidl/src/arrow-rs/parquet/benches/encoding.rs /Users/seidl/src/arrow-rs/parquet/benches/metadata.rs /Users/seidl/src/arrow-rs/parquet/examples/async_read_parquet.rs /Users/seidl/src/arrow-rs/parquet/examples/read_parquet.rs /Users/seidl/src/arrow-rs/parquet/examples/read_with_rowgroup.rs /Users/seidl/src/arrow-rs/parquet/examples/write_parquet.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-concat.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-fromcsv.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-index.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-layout.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-read.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rewrite.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rowcount.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-schema.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-show-bloom-filter.rs /Users/seidl/src/arrow-rs/parquet/src/lib.rs /Users/seidl/src/arrow-rs/parquet/tests/arrow_reader/mod.rs /Users/seidl/src/arrow-rs/parquet/tests/arrow_writer_layout.rs
%

But there are files that when run manually do (running the rustfmt command line above with the addition of parquet/src/compression.rs):
% rustfmt --edition 2021 --check /Users/seidl/src/arrow-rs/parquet/benches/arrow_reader.rs /Users/seidl/src/arrow-rs/parquet/benches/arrow_statistics.rs /Users/seidl/src/arrow-rs/parquet/benches/arrow_writer.rs /Users/seidl/src/arrow-rs/parquet/benches/compression.rs /Users/seidl/src/arrow-rs/parquet/benches/encoding.rs /Users/seidl/src/arrow-rs/parquet/benches/metadata.rs /Users/seidl/src/arrow-rs/parquet/examples/async_read_parquet.rs /Users/seidl/src/arrow-rs/parquet/examples/read_parquet.rs /Users/seidl/src/arrow-rs/parquet/examples/read_with_rowgroup.rs /Users/seidl/src/arrow-rs/parquet/examples/write_parquet.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-concat.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-fromcsv.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-index.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-layout.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-read.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rewrite.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-rowcount.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-schema.rs /Users/seidl/src/arrow-rs/parquet/src/bin/parquet-show-bloom-filter.rs /Users/seidl/src/arrow-rs/parquet/src/lib.rs /Users/seidl/src/arrow-rs/parquet/tests/arrow_reader/mod.rs /Users/seidl/src/arrow-rs/parquet/tests/arrow_writer_layout.rs /Users/seidl/src/arrow-rs/parquet/src/compression.rs
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 150:
         CodecType::BROTLI(level) => {
             #[cfg(any(feature = "brotli", test))]
             return Ok(Some(Box::new(BrotliCodec::new(level))));
-            Err(ParquetError::General("Disabled feature at compile time: brotli".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: brotli".into(),
+            ))
+        }
         CodecType::GZIP(level) => {
             #[cfg(any(feature = "flate2", test))]
             return Ok(Some(Box::new(GZipCodec::new(level))));
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 158:
-            Err(ParquetError::General("Disabled feature at compile time: flate2".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: flate2".into(),
+            ))
+        }
         CodecType::SNAPPY => {
             #[cfg(any(feature = "snap", test))]
             return Ok(Some(Box::new(SnappyCodec::new())));
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 163:
-            Err(ParquetError::General("Disabled feature at compile time: snap".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: snap".into(),
+            ))
+        }
         CodecType::LZ4 => {
             #[cfg(any(feature = "lz4", test))]
             return Ok(Some(Box::new(LZ4HadoopCodec::new(
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 168:
                 _options.backward_compatible_lz4,
             ))));
-            Err(ParquetError::General("Disabled feature at compile time: lz4".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: lz4".into(),
+            ))
+        }
         CodecType::ZSTD(level) => {
             #[cfg(any(feature = "zstd", test))]
             return Ok(Some(Box::new(ZSTDCodec::new(level))));
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 175:
-            Err(ParquetError::General("Disabled feature at compile time: zstd".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: zstd".into(),
+            ))
+        }
         CodecType::LZ4_RAW => {
             #[cfg(any(feature = "lz4", test))]
             return Ok(Some(Box::new(LZ4RawCodec::new())));
Diff in /Users/seidl/src/arrow-rs/parquet/src/compression.rs at line 180:
-            Err(ParquetError::General("Disabled feature at compile time: lz4".into()))
-        },
+            Err(ParquetError::General(
+                "Disabled feature at compile time: lz4".into(),
+            ))
+        }
         CodecType::UNCOMPRESSED => Ok(None),
         _ => Err(nyi_err!("The codec type {} is not supported yet", codec)),
     }
%

Additional context
There are many reports of fmt silently failing, one such is https://github.com/rust-lang/rustfmt/issues/3008.
Has anyone else noticed this or is it something to do with my setup.
%  cargo --version
cargo 1.80.0 (376290515 2024-07-16)
% rustfmt --version
rustfmt 1.7.0-stable (05147895 2024-07-21)

Fascinatingly, I am seeing the same thing
For example I deliberately introduced a formatting issue:
andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$ git diff
diff --git a/parquet/src/compression.rs b/parquet/src/compression.rs
index 10560210e4e..119af7e156f 100644
--- a/parquet/src/compression.rs
+++ b/parquet/src/compression.rs
@@ -15,6 +15,10 @@
 // specific language governing permissions and limitations
 // under the License.

+
+
+
+
 //! Contains codec interface and supported codec implementations.
 //!
 //! See [`Compression`](crate::basic::Compression) enum for all available compression

And then when I ran fmt it didn't seem to fix it
andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$ cargo fmt
andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$ git diff
diff --git a/parquet/src/compression.rs b/parquet/src/compression.rs
index 10560210e4e..119af7e156f 100644
--- a/parquet/src/compression.rs
+++ b/parquet/src/compression.rs
@@ -15,6 +15,10 @@
 // specific language governing permissions and limitations
 // under the License.

+
+
+
+
 //! Contains codec interface and supported codec implementations.
 //!
 //! See [`Compression`](crate::basic::Compression) enum for all available compression

andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$ cargo --version
cargo 1.80.0 (376290515 2024-07-16)
andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$ rustfmt --version
rustfmt 1.7.0-stable (05147895 2024-07-21)
andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs$

Interestingly I found that removing this line:
https://github.com/apache/arrow-rs/blob/b72098fee551086b2b4eb4b131aeaf920cf7e4b3/parquet/src/lib.rs#L121
Make cargo fmt come back
Though it looks like (I) added that line 3 months ago: https://github.com/apache/arrow-rs/commit/98784bd059653cdc316454380ac93a34d53089fd 🤔

It's the first time for me to know #[rustfmt::skip] :laughing:

I tried reverting #5727 and still no output :(

Still tracking this. Here's a list of non-compliant files in the parquet source (format.rs is expected).
% rustfmt --check -l `find . -name "*.rs"` |sort|uniq
/Users/seidl2/src/arrow-rs/parquet/src/arrow/array_reader/empty_array.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/array_reader/fixed_size_list_array.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/array_reader/list_array.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/array_reader/map_array.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/array_reader/struct_array.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/schema/complex.rs
/Users/seidl2/src/arrow-rs/parquet/src/arrow/schema/mod.rs
/Users/seidl2/src/arrow-rs/parquet/src/compression.rs
/Users/seidl2/src/arrow-rs/parquet/src/encodings/encoding/dict_encoder.rs
/Users/seidl2/src/arrow-rs/parquet/src/encodings/levels.rs
/Users/seidl2/src/arrow-rs/parquet/src/encodings/rle.rs
/Users/seidl2/src/arrow-rs/parquet/src/format.rs
/Users/seidl2/src/arrow-rs/parquet/src/util/bit_util.rs
/Users/seidl2/src/arrow-rs/parquet/src/util/interner.rs
/Users/seidl2/src/arrow-rs/parquet/src/util/test_common/file_util.rs
/Users/seidl2/src/arrow-rs/parquet/src/util/test_common/mod.rs
/Users/seidl2/src/arrow-rs/parquet/src/util/test_common/rand_gen.rs

Ah, so apparently rustfmt will not format modules that are declared in macros, such as those in the experimental! macro https://github.com/apache/arrow-rs/blob/a937869f892dc12c4730189e216bf3bd48c2561d/parquet/src/lib.rs#L132-L137
There is an open issue for this https://github.com/rust-lang/rustfmt/issues/3253
One workaround is to tack a list of files to format to the end of the commandline
cargo +stable fmt --all --check -- `find parquet -name "*.rs" \! -name format.rs`

Perhaps something like this could be added to .github/workflows/rust.yml


Integration Account SKU name enumeration does not accept Basic SKU

Hi all,
I've been trying to create an Integration Account with Basic Tier, but it is always returning a deserialization error.
Reviewing the code I've detected a bug related to the SKU name enumeration.
This is the class enum:
[JsonConverter(typeof(StringEnumConverter))]
public enum IntegrationAccountSkuName
{
[EnumMember(Value = "NotSpecified")]
NotSpecified,
[EnumMember(Value = "Free")]
Free,
[EnumMember(Value = "Standard")]
Standard
}
As you can see, no Basic Sku name is supported.
Please, can you fix it?
Many thanks.

@ohawari what version of SDK are you referencing?
Give the full name of the SDK and it's version you are using.

Hi, good morning.
I'm using Microsoft Azure Libraries for .NET version 2.9.
It's not working event in the Host VS2017 generic build agent in VSTS online.
In my first post of this thread, is the specific lines that are not correct because no EnumMember Basic is supported in the enumeration.
Many thanks,
Best regards.


Generate k8s deployment yaml file for cloud service

Closes #149

What has been done to verify that this works as intended?

pytest to check yaml file can correctly generated
manually check yaml file items (lack of resources to apply the deployment)

Why is this the best possible solution? Were any other approaches considered?
Dynamic generation of cloud service deployment yaml file can help users to easier launch the service into their k8s cluster with correct container settings and dependencies. Verifications of technical details:

Jinja2: Simplify the parsing of template
Retrieval of model from cloud storage: Unlike docker, it's hard for k8s pod to bind with physical storage. Pulling model from cloud storage and attach it to the pod is a common methodology.

How to: Pull model through init-container using pre-defined image.
Possible other approaches: Provide interface to user to build image with model embedded. Launch k8s pod directly with new image.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Minimum influences to users. As the changes only help generate a deployment file.
However, users are required to provide cloud storage details and other configurations through config file.
Does this change require updates to documentation?
Yes. Sample config file is necessary.
Before submitting this PR, please make sure you have:

[x] run python -m pytest tests/ and confirmed all checks still pass.
[x] verified that any code or assets from external sources are properly credited.

Thanks for the PR. We will review it soon.

Please resolve the conflicts


Remove early return for workspace new

Details
Whenever we use "transition", we use dismissModal() here because /transition is in our route history. If our exitTo points to a modal like "bank-account". When the user closes the modal, we go back to our last route which is "transition". So we used dismissModal() mainly for this method navigateBackToRootDrawer() which points to the first route in our history.
However, we don't want to navigate to exitTo for workspace/new. We create the policy in AuthScreens and navigate to the workspace from there. The issue is that we don't run dismissModal() and we return early. This means the home screen/ back ground is pointing to the last route which is "transition".
So my fix is:

Move dismissModal() to before our ealry return
Replace dismissModal() with the actual thing we need, navigateBackToRootDrawer()

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/188048
Tests/QA
For local tests, before you begin, you need ngrok running and new dot running locally (npm run web)

Create a new expensify account
Click "Get Started" on the first inbox task, which is the free plan

Verify that the homescreen/default convo with concierge loads in the background correctly, and the modal properly displays the new works pace settings

QA Steps

Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Okay, reverted the changes in the previous files and just added a Navigation.dismissModal() after we create the policy. What do yall think?

The changes look good to me, but remember it was initially removed because Chirag was experiencing something weird in this comment:
https://github.com/Expensify/App/pull/5921#pullrequestreview-807824271
And the response was that it was caused by the call to dismissModal()
https://github.com/Expensify/App/pull/5921#issuecomment-974719156
I can give this a test tomorrow to see if everything is working.

but remember it was initially removed because Chirag was experiencing something weird in this comment:

Yes. In that case, they removed the dismissModal() that was within Policy.js' navigateToPolicy() method. I placed it within  createAndGetPolicyList() which is only used in this flow within AuthScreens for now

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by @sketchydroide in version: 1.1.22-2 🚀

platform
result

🤖 android 🤖
cancelled 🔪

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
cancelled 🔪

🚀 Deployed to staging by @marcaaron in version: 1.1.22-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.1.23-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.1.23-1 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Gjoranv/allow stealing builtin handler bindings

Should status.html also be protected from stealing?
I didn't add an isHosted check before throwing when a reserved binding is used. If you try to steal a binding today, the built-in handler wins, but deployment does not fail.

Absolutely yes. It's the check we use from load balancers to see if the container is up and healthy (and transitively, if the content cluster is healthy enough that we should serve from that zone). It's important enough that I'm wondering if I don't understand the context here :-)

I think you do, I just can never remember who uses this vs. state/v1.


"Edit in settings.json" should add the key and default value

Issue Type: Feature Request
When in the settings ui some options only have an "Edit in settings.json" button. Clicking on it just brings you to settings.json, without any context or help. It would be great if it could at least add a default "key": value entry.
Or, even better, just have a free form text box to edit the key's value directly in the settings ui (like how the C/C++ extension settings ui works).
VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:22:05.899Z)
OS version: Windows_NT x64 10.0.18362

Duplicate of https://github.com/Microsoft/vscode/issues/67908. Thanks!


[BUG] Service Bus receiver client PeekMessageAsync causing exception (Unable to cast object of type 'System.Int64' to type 'System.DateTime'.)

Describe the bug
I am trying to Peek messages from a Service bus subscription using the  PeekMessageAsyc() method of ServiceBusReceiver.
This is causing an exception to be thrown, related to casting Int64 to DateTime.
Expected behavior
Expected behavior is that the first message in subscription is returned without any exception.
Actual behavior (include Exception or Stack Trace)
What is the actual behavior?
Actual behavior is an exception. Below is the stack trace:
Result: Failure Exception: System.AggregateException: One or more errors occurred. (Unable to cast object of type 'System.Int64' to type 'System.DateTime'.) ---> System.InvalidCastException: Unable to cast object of type 'System.Int64' to type 'System.DateTime'. at Azure.Messaging.ServiceBus.Amqp.AmqpMessageConverter.AmqpMessageToSBMessage(AmqpMessage amqpMessage, Boolean isPeeked) at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.PeekMessagesInternalAsync(Int64 sequenceNumber, Int32 messageCount, TimeSpan timeout, CancellationToken cancellationToken) at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.<>c__DisplayClass51_0.<b__0>d.MoveNext() --- End of stack trace from previous location --- at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation(Func2 operation, TransportConnectionScope scope, CancellationToken cancellationToken) at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation(Func2 operation, TransportConnectionScope scope, CancellationToken cancellationToken) at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.PeekMessagesAsync(Nullable1 sequenceNumber, Int32 messageCount, CancellationToken cancellationToken) at Azure.Messaging.ServiceBus.ServiceBusReceiver.PeekMessagesInternalAsync(Nullable1 sequenceNumber, Int32 maxMessages, CancellationToken cancellationToken) at Azure.Messaging.ServiceBus.ServiceBusReceiver.PeekMessageAsync(Nullable1 fromSequenceNumber, CancellationToken cancellationToken) at Watchdog.IngestionQueueMonitor.Run(TimerInfo myTimer) in /home/vsts/work/1/s/services/Watchdog/IngestionProgressMonitor.cs:line 76 at Microsoft.Azure.Functions.Worker.Invocation.VoidTaskMethodInvoker2.InvokeAsync(TReflected instance, Object[] arguments) in D:\a\1\s\src\DotNetWorker.Core\Invocation\VoidTaskMethodInvoker.cs:line 24 --- End of inner exception stack trace --- at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result() at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionInvoker2.<>c.<InvokeAsync>b__6_0(Task1 t) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionInvoker.cs:line 32 at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.Tasks.Task.<>c.<.cctor>b__277_0(Object obj) at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionExecutor.ExecuteAsync(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionExecutor.cs:line 45 at Microsoft.Azure.Functions.Worker.OutputBindings.OutputBindingsMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\1\s\src\DotNetWorker.Core\OutputBindings\OutputBindingsMiddleware.cs:line 16 at Microsoft.Azure.Functions.Worker.GrpcWorker.InvocationRequestHandlerAsync(InvocationRequest request, IFunctionsApplication application, IInvocationFeaturesFactory invocationFeaturesFactory, ObjectSerializer serializer, IOutputBindingsInfoProvider outputBindingsInfoProvider) in D:\a\1\s\src\DotNetWorker.Grpc\GrpcWorker.cs:line 166 Stack: at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result() at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionInvoker2.<>c.b__6_0(Task1 t) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionInvoker.cs:line 32 at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.Tasks.Task.<>c.<.cctor>b__277_0(Object obj) at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionExecutor.ExecuteAsync(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionExecutor.cs:line 45 at Microsoft.Azure.Functions.Worker.OutputBindings.OutputBindingsMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\1\s\src\DotNetWorker.Core\OutputBindings\OutputBindingsMiddleware.cs:line 16 at Microsoft.Azure.Functions.Worker.GrpcWorker.InvocationRequestHandlerAsync(InvocationRequest request, IFunctionsApplication application, IInvocationFeaturesFactory invocationFeaturesFactory, ObjectSerializer serializer, IOutputBindingsInfoProvider outputBindingsInfoProvider) in D:\a\1\s\src\DotNetWorker.Grpc\GrpcWorker.cs:line 166
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

Add messages to service bus susbcription.

Initialize ServiceBusClient from Azure.Messaging.ServiceBus package.

Try to peek the first message in the subscription using the following:
         var subscriptionReceiverClient = this.serviceBusClient.CreateReceiver(topicName, subscriptionName);

         // Get first message in subscription.
         var peekedMessage = await subscriptionReceiverClient.PeekMessageAsync();

Environment:

Azure.Messaging.ServiceBus version 7.5.0
Azure function app running .NET 5.0

@vikcher can you please share how you are creating and sending the message?

@JoshLove-msft , the message was created and sent using Python ServiceBusClient. We create JSON messages.
Here is a code snippet:
with ServiceBusClient(self.servicebus_fqns, client_credential) as client:                 with client.get_topic_sender(self.topic_name) as sender:                     for row in partition_data:                         message = {EventProperty.Id.value: str(uuid.uuid4()),                                    EventProperty.Type.value:                                        DocumentEventType.TimelineUpsert.value,                                    EventProperty.Version.value: self.version,                                    EventProperty.FileFormat.value:                                        self.file_format.value,                                    EventProperty.FileSystem.value:                                        self.container_name,                                    EventProperty.IndexName.value:                                        self.search_index,                                    EventProperty.FilePath.value: row.FilePath}                         sender.send_messages(                             ServiceBusMessage(                                 json.dumps(message).encode("utf-8")))                         yield ((row.FilePath,))

The ServiceBusClient package version is 7.4.0

Thanks @vikcher
Can you also include the actual JSON for the message so I can try to reproduce the issue?

Here is a sample JSON:
{"id": "3a592232-89c1-4fd8-96fe-95b3a4c4662b", "indexName": "index_name", "type": "TimelineUpsert", "version": "V1", "fileFormat": "PARQUET", "fileSystem": "document", "filePath": "/Redacted/file/path/tid-4831-00614aa6-7ee5-49eb-a019-e132b9238e84-3187-1-c000.samplePath.parquet"}

Interesting, @yunhaoling @swathipil, do you know how a JSON message like this would be sent when using the Python SDK? Are they put into the ApplicationProperties?

Hi @JoshLove-msft , @yunhaoling , @swathipil - is there any update on this?

@JoshLove-msft - Here, the ServiceBusMessage body attribute would be set to the sample JSON value.

We just tried a test where @swathipil sent a message containing the body you have included using the Python SDK and I received it and completed it using the .NET SDK, and everything worked.
Are you setting any other properties on the message, or are you only setting the body as in the code snippet you have provided?
The only way I can see this error occurring is if one of the reserved Service Bus properties was set when sending a message.


Passing urls to result worker without crawling

Can you explain how to send things to the resultworker without crawling it? Are you supposed to use a data_uri as in
self.crawl('data:;fake_url_%s' % i, save=i, callback=self.load_urls)
If so, can you explain how to use this and how it is processed. I have read the data uri wiki page but could not comprehend how to use it. I have overwritten the resultworker.
or perhaps some more detail to
def detail_page(self, response):
    for li in response.doc('li').items():
        self.send_message(self.project_name, {
            ...
        }, url=response.url+"#"+li('a.product-sku').text())

def on_message(self, project, msg):
    return msg

I want to put some urls in the database without passing them through the processor etc

@cryptocxeq I guess what you want to do is saving multiple results on one detail_page. You can try this:
def detail_page(self, response):
    for li in response.doc('li').items():
        yield {
            "url": response.url+"#"+li('a.product-sku').text())
        }

Yes, both self.send_message(self.project_name, {}, fake_url} and yield result work .

ok, so is there a way to give it a taskid and etc, or is it better just to replace the taskid duplicate checking with my own?

you can set the url for self.send_message.

can you explain in more detail, the doc is pretty dry and I don't really understand. wouldnt on_message only give one task id

The parameter url set in self.send_message will be used to generate taskid when you returning results in corresponding on_message.

seems that "yield result" could not save multi results on one detail_page, because base_handler.py just send every result to a queue to result work, but all results from same task, so actually only one result will be saved in db
            result = self._run_task(task, response)
            if inspect.isgenerator(result):
                for r in result:
                    self._run_func(self.on_result, r, response, task)


add option to use both title and path searching

If search_by is a table, it adds the option to search by both path and title, by concatenating properties separated by space

Thanks for this @lytex could you give an example where you may want to search by both path and title? Was causing you a problem to only search by title?

Thanks for this @lytex could you give an example where you may want to search by both path and title? Was it causing you a problem to only search by title or path?

Well, for example I manage my dotfiles with chezmoi, and sometimes I type chezmoi to match ~/.local/share/chezmoi and sometimes I type dotfiles to match the title.

Ah okay. I misunderstood you. I thought you meant to search both path and title at the same time. Makes sense. Thanks for adding this.


JFoenix Demo App - unable to resize or drag the main window

OS: Mac OS High Sierra 10.13.3
JVM:  1.8.0_161
The JFoenix Demo main window cannot be resized or dragged. There is no resize cursor over the window edges. The window cannot be dragged either. It works on Windows 10 (the same JVM) however.

Hello,
I was not able to reproduce this issue, can you provide more details? any exception on the console?

No exception is thrown on the console.
Observation:
This is a very simple example, which has the same problem:
public class Test1 extends Application {

    @Override
    public void start(Stage primaryStage) throws Exception {

        Button btn = new Button();
        btn.setText("Test");
        btn.setOnAction(event -> System.out.println("Hello!") ));

        StackPane root = new StackPane();
        root.getChildren().add(btn);

        JFXDecorator dec = new JFXDecorator(primaryStage, root, true, true, true);

        primaryStage.setTitle("JDecorator Test");
        primaryStage.setScene(new Scene(dec, 300, 250));
        primaryStage.show();
    }

    public static void main(String[] args) {
        launch(args);
    }
}

However, when I don't use JFXDecorator everything works.
public class Test1 extends Application {

    @Override
    public void start(Stage primaryStage) throws Exception {

        Button btn = new Button();
        btn.setText("Test");
        btn.setOnAction(event -> System.out.println("Hello!") ));

        StackPane root = new StackPane();
        root.getChildren().add(btn);

        //JFXDecorator dec = new JFXDecorator(primaryStage, root, true, true, true);

        primaryStage.setTitle("JDecorator Test");
        primaryStage.setScene(new Scene(root, 300, 250));
        primaryStage.show();
    }

    public static void main(String[] args) {
        launch(args);
    }
}

Ok, I checked this on earlier versions of JVM on MacOS.
It works on 1.8.0_144 but does not work on 1.8.0_161. I checked it on two MacOS machines.

.jfx-decorator .resize-border {
-fx-border-color: -fx-decorator-color;
-fx-border-width: 2 2 2 2;
}

I updated to JDK 1.8.0_161, however still not able to reproduce.

if you can debug it from your side, and tell what's causing the issue. we might be able to fix it.
Regards,

It seems the primary stage is maximized after stage.show() if a JFXDecorator is used. Debugging the startup shows a WindowEvent coming through forcing a stage maximized state. Any ideas where this may be coming from? Can debug further with a hint from your side.

BTW. Seems to be broken on JDK9 as well.

Hello,
there are only 2 ways to trigger this event. By either triggering action the maximize button or by calling the method setMaximized of JFXDecorator (which internally fires an action event to the max button).

@svenreimers can you track down the event source?

Hi. I run into the same issue (MacOS Sierra - Java 8_171). After some debugging i found out that in 'private void handleDragEventOnDecoratorPane(MouseEvent mouseEvent)', right at the beginning theres is an early exit check '(primaryStage.isFullScreen() || mouseEvent.isStillSincePress() || primaryStage.isMaximized() || maximized)' where 'primaryStage.isMaximized()' always returns true for some reason that i could not find out. Any suggestions for a work around?

@Krisso990 can you try to add change listener to maximized property? in order to tell which code is setting it to true, it could be a JavaFX issue.

This issue is still occurring. I found it in Ubuntu when using the latest versions of JFoenix and Java 1.8.0_191.
It's in the handleDragEventOnDecoratorPane(MouseEvent mouseEvent) method of the JFXDecorator. If the app was maximixed once, you can no longer drag, because "maximized" is still true. It looks like in Ubuntu for some reason the private maximized property is not being set to false when no longer full screen.
Works fine in Win 10.


Retiring toronto & montreal

Summary
Toronto & Montreal are being retired today
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 67.854%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3371

Relevant Lines:
4968

💛  - Coveralls


Don’t remove and add when child is already in place

Because.

Can there be events that get dispatched on removing or adding? If so, you would now be passing over those, which may or may not happen in flash.

@MSGhero AFAIK, no events are dispatched when you changed the display order of a DisplayObject on the same parent :smile:


Canada data incorrect

Great job on the map! Love it! It's so far the most visually user friendly map.
Only current issue is data for Canada. Previously it was showing amount recovered, but now it's showing that no one has recovered.
John Hopkins reports:
BC: 3 Recovered
Ontario: 4 Recovered
There is now also a case in Alberta, that also needs to show up.

Suggestion for new source:
https://bnonews.com/index.php/2020/02/the-latest-coronavirus-cases/

Thank you so much. Find a good source is hard. and we find that the official sources usually have some time lag.


Remove the hard coded version.

If you don't include a version, it just chooses the latest one.

Can you remember why it was hard-coded in the first place? I couldn't work it out from the commit messages.
I noticed that the version is hard-coded in a few other places: https://github.com/search?q=org%3Anationalarchives+taskDefinitionOverride&type=code Should we update all of them too?

Can you remember why it was hard-coded in the first place? I couldn't work it out from the commit messages.
I noticed that the version is hard-coded in a few other places: https://github.com/search?q=org%3Anationalarchives+taskDefinitionOverride&type=code Should we update all of them too?

I think it was hard coded because I didn't know you could just omit it and get the latest version. I'll put some PRs in to update the other ones as they should be done as well.

I think it was hard coded because I didn't know you could just omit it and get the latest version. I'll put some PRs in to update the other ones as they should be done as well.