Android build fails

react-native 0.63.4
react-native-mmkv-storage 0.6.3
* What went wrong:
Execution failed for task ':react-native-mmkv-storage:externalNativeBuildRelease'.
> Build command failed.
  Error while executing process /usr/local/lib/android/sdk/cmake/<IP_ADDRESS>88404/bin/ninja with arguments ***-C /home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/.cxx/cmake/release/armeabi-v7a rnmmkv***
  ninja: Entering directory `/home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/.cxx/cmake/release/armeabi-v7a'
...
[37/37] Linking CXX shared library /home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/release/obj/armeabi-v7a/librnmmkv.so
  FAILED: /home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/release/obj/armeabi-v7a/librnmmkv.so
  : && /usr/local/lib/android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ --target=armv7-none-linux-androideabi21 --gcc-toolchain=/usr/local/lib/android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64 --sysroot=/usr/local/lib/android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64/sysroot -fPIC -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -march=armv7-a -mthumb -Wformat -Werror=format-security  -fexceptions -frtti -std=c++1y -DONANDROID -Oz -DNDEBUG  -Wl,--exclude-libs,libgcc.a -Wl,--exclude-libs,libgcc_real.a -Wl,--exclude-libs,libatomic.a -Wl,--build-id=sha1 -Wl,--no-rosegment -Wl,--fatal-warnings -Wl,--exclude-libs,libunwind.a -Wl,--no-undefined -Qunused-arguments -shared -Wl,-soname,librnmmkv.so -o /home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/release/obj/armeabi-v7a/librnmmkv.so CMakeFiles/rnmmkv.dir/rnmmkv-adapter.cpp.o  /usr/local/lib/android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/arm-linux-androideabi/21/liblog.so /home/runner/work/reactnative-app/reactnative-app/node_modules/react-native-mmkv-storage/android/build/react-native-0.63.4.aar/jni/armeabi-v7a/libreactnativejni.so core/libcore.a -landroid /usr/local/lib/android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/arm-linux-androideabi/libz.a -latomic -lm && :
  ld: error: undefined symbol: facebook::jsi::Value::~Value()
  >>> referenced by jsi-inl.h:112 (/home/runner/work/reactnative-app/reactnative-app/android/../node_modules/react-native/ReactCommon/jsi/jsi/jsi-inl.h:112)

try using older ndk, maybe 21.x

Cmake.txt error on my build for Android as well.
Cause: executing external native build for cmake /node_modules/react-native-mmkv-storage/android/src/main/rnmmkv/CMakeLists.txt
Could not solve it with NDK version or anything.
@ammarahm-ed can you check it please?

@WrathChaos  can you share complete build error log?

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-mmkv-storage:generateJsonModelDebug'.
> Build command failed.
  Error while executing process /Users/kurayogun/Library/Android/sdk/cmake/3.6.4111459/bin/cmake with arguments {-H/Users/.../node_modules/react-native-mmkv-storage/android/src/main/rnmmkv -B/Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a -DANDROID_ABI=armeabi-v7a -DANDROID_PLATFORM=android-21 -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/.../node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/debug/obj/armeabi-v7a -DCMAKE_BUILD_TYPE=Debug -DANDROID_NDK=/Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670 -DCMAKE_CXX_FLAGS=-fexceptions -frtti -std=c++1y -DONANDROID -DCMAKE_TOOLCHAIN_FILE=/Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake -DCMAKE_MAKE_PROGRAM=/Users/kurayogun/Library/Android/sdk/cmake/3.6.4111459/bin/ninja -GAndroid Gradle - Ninja -DANDROID_STL=c++_shared -DNODE_MODULES_DIR=/Users/.../android/../node_modules}
  -- Check for working C compiler: /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang
  -- Check for working C compiler: /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++
  -- Check for working CXX compiler: /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring incomplete, errors occurred!
  See also "/Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeOutput.log".

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/kurayogun/Library/Android/sdk/cmake/3.6.4111459/share/cmake-3.6/Modules/CMakeDetermineSystem.cmake:98 (include)
    CMakeLists.txt

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Warning at /Users/kurayogun/Library/Android/sdk/ndk/22.1.7171670/build/cmake/android.toolchain.cmake:449 (message):
    An old version of CMake is being used that cannot automatically detect
    compiler attributes.  Compiler identification is being bypassed.  Some
    values may be wrong or missing.  Update to CMake 3.19 or newer to use
    CMake's built-in compiler identification.
  Call Stack (most recent call first):
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/3.6.0-rc2/CMakeSystem.cmake:6 (include)
    /Users/.../node_modules/react-native-mmkv-storage/android/.cxx/cmake/debug/armeabi-v7a/CMakeFiles/CMakeTmp/CMakeLists.txt:2 (project)

  CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
    CMake 3.8.0 or higher is required.  You are running version 3.6.0-rc2

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

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

BUILD FAILED in 20s

    at makeError (/Users/.../node_modules/execa/index.js:174:9)
    ```

Here is the full log.

React Native `0.64.1`
I tried with both `0.6.0` and `0.6.1` with the library version both not working with the Android build. iOS is just fine.

React Native 0.64.1
I tried with both 0.6.0 and 0.6.1 with the library version both not working with the Android build. iOS is just fine.

The issue is obvious. You are using cmake 3.6 while you should be using 3.10.2 at least. You can update it inside Android Studio Sdk Manager.

@ammarahm-ed Can you tell me where to upgrade it?

@ammarahm-ed Can you tell me where to upgrade it?

Uncheck cmake 3.6.x

Done it now it says:

Done it now it says:

Run cd android && ./gradlew clean
Run yarn/npm install
Then try to build

Nope, unfortunately nothing changed. It still trying to locate 3.6 version :S Do you have any idea?

Nope, unfortunately nothing changed. It still trying to locate 3.6 version :S Do you have any idea?

Maybe restarting your pc will help. Did you remove node_modules folder before running npm install again?

Nope, unfortunately nothing changed. It still trying to locate 3.6 version :S Do you have any idea?

Maybe restarting your pc will help. Did you remove node_modules folder before running npm install again?

Also update the library to 0.6.4

I tried to restart the pc.
Removed node_modules, package-lock.json
Re-install node_modules.
Even set the cmake version manually with:
https://stackoverflow.com/a/51472416/2247055
Upgrade the library to 0.6.4

Still this silly error:

Could not even build on Android Studio:
Cause: executing external native build for cmake /Users/.../node_modules/react-native-mmkv-storage/android/src/main/rnmmkv/CMakeLists.txt

Could not even build on Android Studio:
Cause: executing external native build for cmake /Users/.../node_modules/react-native-mmkv-storage/android/src/main/rnmmkv/CMakeLists.txt

Try navigating to users/username/Android/sdk/cmake/ and delete the 3.6.x folder if it exists

Could not even build on Android Studio:
Cause: executing external native build for cmake /Users/.../node_modules/react-native-mmkv-storage/android/src/main/rnmmkv/CMakeLists.txt

Try navigating to users/username/Android/sdk/cmake/ and delete the 3.6.x folder if it exists

Tried it and there is no 3.6.x version in the folder.

I don't know why but now it says:

I don't know why but now it says:

Go to Android sdk manager and deselect cmake 3.18.1 also.

Okay,
I found it. It simply does not work with lower  and higher than <IP_ADDRESS>88404 CMake version.
Also, in the local.properties file, I had to define cmake path:
cmake.dir=/Users/username/Library/Android/sdk/cmake/<IP_ADDRESS>88404

Thank you so much for the live help and the support for the library @ammarahm-ed  :)

Shouldn't it work with the higher versions as well? @ammarahm-ed

It should work. Maybe something greater than 3.18 would work fine.

I'm getting a similar error.
* What went wrong:
Execution failed for task ':react-native-mmkv-storage:externalNativeBuildRelease'.
> Build command failed.
  Error while executing process C:\Users\username\AppData\Local\Android\Sdk\cmake\<IP_ADDRESS>88404\bin\ninja.exe with arguments {-C C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\.cxx\cmake\release\armeabi-v7a rnmmkv}
  ninja: Entering directory `C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\.cxx\cmake\release\armeabi-v7a'
  [1/1] Linking CXX shared library C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\build\intermediates\cmake\release\obj\armeabi-v7a\librnmmkv.so
  FAILED: C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/release/obj/armeabi-v7a/librnmmkv.so
  cmd.exe /C "cd . && C:\Users\username\AppData\Local\Android\Sdk\ndk\21.4.7075529\toolchains\llvm\prebuilt\windows-x86_64\bin\clang++.exe --target=armv7-none-linux-androideabi16 --gcc-toolchain=C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64 --sysroot=C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64/sysroot -fPIC -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -march=armv7-a -mthumb -Wformat -Werror=format-security  -fexceptions -frtti -std=c++1y -DONANDROID -Oz -DNDEBUG  -Wl,--exclude-libs,libgcc.a -Wl,--exclude-libs,libgcc_real.a -Wl,--exclude-libs,libatomic.a -Wl,--build-id -Wl,--fatal-warnings -Wl,--exclude-libs,libunwind.a -Wl,--no-undefined -Qunused-arguments -shared -Wl,-soname,librnmmkv.so -o C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\build\intermediates\cmake\release\obj\armeabi-v7a\librnmmkv.so CMakeFiles/rnmmkv.dir/rnmmkv-adapter.cpp.o -LC:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/build/react-native-0.63.4.aar/jni/armeabi-v7a -llog -lreactnativejni core/libcore.a -landroid C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64/sysroot/usr/lib/arm-linux-androideabi/libz.a -latomic -lm && cd ."
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:112: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:112: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi.h:966: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi.h:961: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:205: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:205: error: undefined reference to 'facebook::jsi::Value::~Value()'
  clang++: error: linker command failed with exit code 1 (use -v to see invocation)
  ninja: build stopped: subcommand failed.

Using<EMAIL_ADDRESS><EMAIL_ADDRESS>CMake <IP_ADDRESS>88404, NDK 21.4.7075529, and the build.gradle change described here. No other JSI packages. I've tried deleting node_modules and running ./gradlew.bat clean, didn't change anything. However, downgrading to<EMAIL_ADDRESS>works.

I will test on older version of react native and see how to fix this.

I recently installed an update for Kotlin that Android Studio requested, and got this error as well.

Now running in a react-native (non-expo) project with gradle 7:
> Task :app:createDebugExpoConfig FAILED

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.2/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
39 actionable tasks: 3 executed, 36 up-to-date
D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\getConfig.js:39
    throw new Errors_1.ConfigError(`Failed to read config at: ${configPath}`, 'INVALID_CONFIG');
    ^

ConfigError: Failed to read config at: D:\Projects\Code\project\app.config.js
    at Object.getDynamicConfig (D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\getConfig.js:39:11)
    at getConfig (D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\Config.js:156:78)
    at Object.<anonymous> (D:\Projects\Code\project\node_modules\expo-constants\scripts\getAppConfig.js:16:17)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'INVALID_CONFIG',
  cause: undefined,
  isConfigError: true
}

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:createDebugExpoConfig'.
> Process 'command 'cmd'' finished with non-zero exit value 1

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

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

BUILD FAILED in 31s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\getConfig.js:39
    throw new Errors_1.ConfigError(`Failed to read config at: ${configPath}`, 'INVALID_CONFIG');
    ^

ConfigError: Failed to read config at: D:\Projects\Code\project\app.config.js
    at Object.getDynamicConfig (D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\getConfig.js:39:11)
    at getConfig (D:\Projects\Code\project\node_modules\expo-constants\node_modules\@expo\config\build\Config.js:156:78)
    at Object.<anonymous> (D:\Projects\Code\project\node_modules\expo-constants\scripts\getAppConfig.js:16:17)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'INVALID_CONFIG',
  cause: undefined,
  isConfigError: true
}

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:createDebugExpoConfig'.
> Process 'command 'cmd'' finished with non-zero exit value 1

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

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

BUILD FAILED in 31s

    at makeError (D:\Projects\Code\project\node_modules\execa\index.js:174:9)
    at D:\Projects\Code\project\node_modules\execa\index.js:278:16
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async runOnAllDevices (D:\Projects\Code\project\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:106:5)
    at async Command.handleAction (D:\Projects\Code\project\node_modules\@react-native-community\cli\build\index.js:192:9)

The library you are using is not this one. Its react-native-mmkv.

I'm getting a similar error.
* What went wrong:
Execution failed for task ':react-native-mmkv-storage:externalNativeBuildRelease'.
> Build command failed.
  Error while executing process C:\Users\username\AppData\Local\Android\Sdk\cmake\<IP_ADDRESS>88404\bin\ninja.exe with arguments {-C C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\.cxx\cmake\release\armeabi-v7a rnmmkv}
  ninja: Entering directory `C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\.cxx\cmake\release\armeabi-v7a'
  [1/1] Linking CXX shared library C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\build\intermediates\cmake\release\obj\armeabi-v7a\librnmmkv.so
  FAILED: C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/build/intermediates/cmake/release/obj/armeabi-v7a/librnmmkv.so
  cmd.exe /C "cd . && C:\Users\username\AppData\Local\Android\Sdk\ndk\21.4.7075529\toolchains\llvm\prebuilt\windows-x86_64\bin\clang++.exe --target=armv7-none-linux-androideabi16 --gcc-toolchain=C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64 --sysroot=C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64/sysroot -fPIC -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -march=armv7-a -mthumb -Wformat -Werror=format-security  -fexceptions -frtti -std=c++1y -DONANDROID -Oz -DNDEBUG  -Wl,--exclude-libs,libgcc.a -Wl,--exclude-libs,libgcc_real.a -Wl,--exclude-libs,libatomic.a -Wl,--build-id -Wl,--fatal-warnings -Wl,--exclude-libs,libunwind.a -Wl,--no-undefined -Qunused-arguments -shared -Wl,-soname,librnmmkv.so -o C:\Users\username\Documents\Coding\ReactNative\appname\node_modules\react-native-mmkv-storage\android\build\intermediates\cmake\release\obj\armeabi-v7a\librnmmkv.so CMakeFiles/rnmmkv.dir/rnmmkv-adapter.cpp.o -LC:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/build/react-native-0.63.4.aar/jni/armeabi-v7a -llog -lreactnativejni core/libcore.a -landroid C:/Users/username/AppData/Local/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/windows-x86_64/sysroot/usr/lib/arm-linux-androideabi/libz.a -latomic -lm && cd ."
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:112: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:112: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi.h:966: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi.h:961: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:205: error: undefined reference to 'facebook::jsi::Value::~Value()'
  C:/Users/username/Documents/Coding/ReactNative/appname/node_modules/react-native-mmkv-storage/android/../../../node_modules/react-native/ReactCommon/jsi\jsi/jsi-inl.h:205: error: undefined reference to 'facebook::jsi::Value::~Value()'
  clang++: error: linker command failed with exit code 1 (use -v to see invocation)
  ninja: build stopped: subcommand failed.

Using<EMAIL_ADDRESS><EMAIL_ADDRESS>CMake <IP_ADDRESS>88404, NDK 21.4.7075529, and the build.gradle change described here. No other JSI packages. I've tried deleting node_modules and running ./gradlew.bat clean, didn't change anything. However, downgrading to<EMAIL_ADDRESS>works.

I second that downgrading to 0.6.0 seems to solve the build error.

to fix that, create android/local.properties/local.properties
and set you cmake.dir like that : cmake.dir=/home/<username>/Android/Sdk/cmake
make sure that you install a new version of cmake from your android studio sdk manager and remove the old one.
clean ./gradlew clean
and run again
you may need to upgrade gradle from build.gradle like that classpath("com.android.tools.build:gradle:4.0.1")

update to v0.6.6

I have same problem version 0.6.11 , with gradle 7.4.2 and tools 7.0.4 , I m trying to enable new architecture on react-native 0.68 , cmake version 3.10.2, ndk 21.4.x , I had tried all solutions above and no one works for me , any Idea?

I am also getting same problem ,I tried all solution above but not work for me ,any ldea for help me?
Execution failed for task ':app:configureCMakeDebug[arm64-v8a]'.
> [CXX1405] error when building with cmake using C:\project\flutter_ffi_example\android\CMakeLists.txt: Build command failed.


Inaccurate version bounds in  .cabal file

You know the drill, either fix the .cabal file or fix the code, thanks :-)
With base < 4.5:
[1 of 2] Compiling Control.Monad.Managed ( src/Control/Monad/Managed.hs, dist/dist-sandbox-7d13ef1c/build/Control/Monad/Managed.o )

src/Control/Monad/Managed.hs:131:10:
    Could not deduce (Eq (Managed a))
      arising from the superclasses of an instance declaration
    from the context (Num a)
      bound by the instance declaration
      at src/Control/Monad/Managed.hs:131:10-33
    Possible fix:
      add (Eq (Managed a)) to the context of the instance declaration
      or add an instance declaration for (Eq (Managed a))
    In the instance declaration for `Num (Managed a)'

src/Control/Monad/Managed.hs:131:10:
    Could not deduce (Show (Managed a))
      arising from the superclasses of an instance declaration
    from the context (Num a)
      bound by the instance declaration
      at src/Control/Monad/Managed.hs:131:10-33
    Possible fix:
      add (Show (Managed a)) to the context of the instance declaration
      or add an instance declaration for (Show (Managed a))
    In the instance declaration for `Num (Managed a)'
xcabal: Error: some packages failed to install:
managed-1.0.1 failed during the building phase. The exception was:
ExitFailure 1

Fixed by 157ec61a18f1021203b5fae9acbea34422c43078 and uploaded to Hackage as managed-1.0.2


I'm Using your library now !

I Just added your library to my app ( Shake detection to be exact ) and it's working flawlessly ! already included the library name in my app as well.
Get Off Your Phone - Play Store
Thanks so much for such an excellent library mate ! Keep it up.
If you need more information please tell me :)

Hi @Alikaraki95, thanks you😺
I will add your app under my readme too 😄
If you find any issues, please open up an issue and I would try my best to resolve it asap.
P.S: A brand new version of Sensey should be live in the new year 2018, so keep a look out for it. A lot of things coming to it.


Allow passing modifiers to react-popper's Popper component

Use case
We have some Popovers targets in overflow: auto parent elements. By default, popper.js' preventOverflow modifier restricts the popper to boundariesElement: scrollParent. This leads to unwanted placement of the popper. To fix it, I would like to set the boundariesElement to viewport, which is not possible on a Popover right now.
I am happy to help with a PR if the general approach of passing modifiers to react-popper's Popper component is approved by the maintainers.

Yeah, it should accept modifiers and spread them on top of the modifiers we end up creating based on some of the other props. It should be known that passing certain modifiers will override the ones created be certain props.
Yes, a PR would be awesome.
PopperContent needs to accept and use the modifiers. Tooltip and Popover need to explicitly pass modifiers to PopperContent (as it currently gets spread on top another element). Don't forget tests and documentation :wink:

Awesome, I created a PR: #710 Looking forward to some feedback :)

Would also love to have this. ❤❤


Trash handles deletes of files already existing in trash correctly.

@chavdar simple PR for fix of deleting files already existing in trash.

LGTM


how to use this as a filter?

Hi, any way to use this as a filter - vapoursynth?

You can use this filter to interpolate frames during real-time video playback.
NVIDIA GeForce RTX 3070 Ti allows you to double the frames without downscaling (scale=1.0) for 720p video files: https://www.svp-team.com/forum/viewtopic.php?pid=79315#p79315
NVIDIA GeForce RTX 4090 will be over 2x more powerful than NVIDIA GeForce RTX 3090, so you can expect real-time interpolation for 1080p files.


Fix memory leak when removing layers from ol.layer.Group

Fixes #3479

I've added a few minor comments. I'd also recommend adding unit-tests to check that that logic is correct and avoid regressions in the future.

@elemoine you're right; units tests must be added.

More unit tests added

+1


installing node-red-node-email from palette manager fails

Trying to install node-red-node-email from the palette manager and it fails. Here is the log. I have been able to install other nodes without issue.
2020-11-10T16:15:30.158Z Install : node-red-node-email 1.8.2
2020-11-10T16:15:30.189Z C:\Users\user\AppData\Local\Programs\node-red-desktop\resources\app.asar\node_modules\npm\bin\npm-cli.js install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production<EMAIL_ADDRESS>2020-11-10T16:15:32.859Z [err] npm WARN lifecycle npm is using C:\Users\user\AppData\Local\Programs\node-red-desktop\Node-RED-Desktop.exe but there is no node binary in the current PATH. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.
2020-11-10T16:15:32.859Z [out]
2020-11-10T16:15:32.859Z [out] ><EMAIL_ADDRESS>postinstall C:\Users\user.Node-RED-Desktop\node_modules\mailparser\node_modules\nodemailer
2020-11-10T16:15:32.859Z [out] > node -e "try{require('./postinstall')}catch(e){}"
2020-11-10T16:15:32.859Z [out]
2020-11-10T16:15:32.909Z [err] 'node' is not recognized as an internal or external command,
2020-11-10T16:15:32.909Z [err] operable program or batch file.
2020-11-10T16:15:32.990Z [err] npm ERR! code ELIFECYCLE
2020-11-10T16:15:32.990Z [err] npm ERR! errno 1
2020-11-10T16:15:32.993Z [err] npm ERR<EMAIL_ADDRESS>postinstall: node -e "try{require('./postinstall')}catch(e){}"
2020-11-10T16:15:32.993Z [err] npm ERR! Exit status 1
2020-11-10T16:15:32.993Z [err] npm ERR!
2020-11-10T16:15:32.993Z [err] npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
2020-11-10T16:15:32.993Z [err] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-11-10T16:15:33.025Z [err]
2020-11-10T16:15:33.025Z [err] npm ERR!      C:\Users\user\AppData\Roaming\npm-cache_logs\2020-11-10T16_15_32_994Z-debug.log
2020-11-10T16:15:33.043Z rc=1

Hi
It looks node-red-node-email requires node command for post install.
So you need to install node.js v12.x in your PC before installing node-red-node-email.
Regards

Thank you for the response. I have that node installed on a different computer and it didn't have any issues, but now I see that they have updated that node to a newer version and that must be causing the issue that you pointed out. Thanks again.


all missing or missing lots of entries in many modules

This also leads to missing documentation for these functions and classes not included in __all__

Fixed in #1686


error in metrics scores for naive QA

Hi,
I tried to run the naive QA datasets like NQ, but get this error when generating metric scores.
Error in em!
list indices must be integers or slices, not str
Error in f1!
list indices must be integers or slices, not str
Error in acc!
list indices must be integers or slices, not str
Error in precision!
list indices must be integers or slices, not str
Error in recall!
list indices must be integers or slices, not str
{}

updates: I think self.choices is a list of empty lists right now.
Can you take a look? Thank you in advance!

Sorry, there is a small issue here that we have fixed.


softplus for dirichlet

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2ead8fe) 95.15% compared to head (7b0dad7) 95.15%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #721   +/-   ##
=======================================
  Coverage   95.15%   95.15%
=======================================
  Files         124      124
  Lines        4854     4855    +1
=======================================
+ Hits         4619     4620    +1
  Misses        235      235

Flag
Coverage Δ

unittests
95.15% <100.00%> (+<0.01%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Quota Exceeded errors from setItem() when running on Heroku

We have an ionic web app running on Heroku (Node.JS/express), which uses ng-token-auth.  Occasionally Heroku is reporting a Quota Exceeded error, and we believe that's if someone is in private mode on their browser.  We have token-auth configured to use localStorage, which seems to be the problem.  Has anyone experienced this?  Is there a different configuration that would work in our case?

I think this was fixed by setting storage to 'cookies' on heroku


Scheduled Tasks

Have a feature request?
I would like to have scheduled tasks.

See #35 - this has been requested many times, PRs are more than welcome though


Script halted when creating root site collection in SP2019

When installing SP2019 single server the script is failing when creating site collection. This does not occur with SP2016.
Creating Site Collection "http://"
Script halted!
Exception
Microsoft. SharePoint. SPException: Provisioning did not succeed. Details: The site template was
not provisioned successfully. Delete this site collection in Central Administration, and then
create a new site collection. OriginalException: Provisioning did not succeed. Details: Failed
to create the 'Cache Profiles' list. OriginalException: Invalid field name.
{d8f18167-7cff-4c4e-bdbe-e7bØfØ1678f3} /Cache Profiles

Hi! The same happened to me. I tried to created manually a Publishing Portal from Central Admin, which finished successfully. Then I launched AutoSPInstaller again and this time it could complete the site collection creation without problems.

Another way to resolve this is reboot machine and restart script if you don't want to create manually.

I just faced this issue on a new SharePoint 2019 Installation on Windows Server 2019 Std. It was not possible to create a Publishing Portal. I can confirm that rebooting the server is resolving the issue.

Had the same problem with a SharePoint 2016 installation. In my case I just restarted the script, no reboot needed.
Debugging:
I tried to restart all possible services before New-SPSite (with pause in the script), nothing worked.
I tried to wait for a long time, but it's not a timing issue.
The problem also occurs if you just start the script again in the same PowerShell window.
But, if you restart the script (close PowerShell and open a new one), the error does not appear.
Further, if you restart the script just after New-SPConfigurationDatabase the error does not appear. If you restart the script before, the error appears.
It seems as PowerShell does cache something, which has a bad impact on the New-SPSite. But New-SPSite does not use a previous variable or so, created by New-SPConfigurationDatabase.
This is very awkward, I have no idea what PowerShell or SharePoint is doing here. Couldn't figure it out. Just stick to the workaround. It should only be a problem in some new installations.
In my forked project I added some simple error handling.

I added code to perform IISReset immediately after the self-signed certificate completes binding. The binding causes the STS to crash repeatedly (not only on the first time) with an 8306 error. This was with a subscription edition installed on Windows Server 2022.


[UI] Support for Edge

Describe the bug
This issue is to be addressed later, not now. Currently, the web app doesn't load properly in Edge. See screenshot.
To reproduce
Steps to reproduce the behavior:
For UI issues:

Open up Edge
Navigate to the covasim app in the browser

Expected behavior
Web app loads without issues in Edge
Screenshots or outputs

Platform (please complete the following information):

Covasim version: 0.28.5
OS: Windows
Browser: Edge

Seems like Vue is just not rendering at all...

@mfisher-idmod Are there any console errors? Does Edge have a console? :stuck_out_tongue:

If it's not a quick fix, would suggest a user agent check and then "Please use Chrome or Firefox to use the Covasim app".

@cliffckerr Console errors from Edge for target _top: sim

For "SCRIPT1028: SCRIPT1028: Expected identifier, string or number". Looks like it's this issue: https://github.com/vuetifyjs/vuetify/issues/8279
I'd be ok with the user agent check and message, if we were to deal with Edge later for government employees who still use IE/Edge.

This is a one line fix.


General: Replace websocket connection alerts with connection lost indicator

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context

If the websocket connection fails, the client currently displays a permanent alert, blocking access to the underlying components of the navbar.

Description

This PR introduces a red indicator (wifi symbol) and a popover that belongs to it to notify the user about the connection interruption. The old notification alerts have been removed. This does not cover anything anymore, and shows the warning (in form of the animated symbol) even if the popover is clicked away.
As the new component needs access to the connection state, this PR additionally reworks how the websocket connection state is distributed in the application. Currently, the websocket service maintained arrays of connect and disconnect listeners, which are populated by calls to the bind() method of the service. This is not the best approach to this problem, and ignores the fact that we generally encourage the use of RxJs for usecases like this.
Therefore, the state of the websocket is now distributed using a RxJs behavior subject and comes with additional state information: connected, hasEverBeenConnected, intendedDisconnect.
All code that previously relied on connection events have been updated accordingly.
Lastly, I've updated the breakpoints and responsive mechanism of the navbar a bit as the new icon takes a bit more space (if it's rendered) and in general, currently, the navbar does not behave very well when it's scaled down (e.g. "Course Management" gets a line break etc). It will just switch to the collapsed navbar earlier than before.
Steps for Testing

General

Start the web application
Disable your internet connection
--> Verify that the warning symbol in the top left pops up and that the popover is displayed.
--> You should be able to dismiss the popover and bring it back by clicking on the button again.
--> The pulse should stop after 1 minute; the icon itself stays there.
--> The icon should vanish if you reenable your internet connection.

Exam Mode
Please verify that the disconnect icon doesn't show the pulse animation at all if you are on the exam participation view as a student. Additionally, check that the connection indicator on the bottom when doing an exam as a student still shows up and updates if you disable your internet connection.
Navbar
Please scale down your viewport horizontally and observe that the navbar is responsive and looks good on smaller screen sizes, and that the hamburger menu still works.
Review Progress

Code Review

[x] Review 1
[ ] Review 2

Manual Tests

[x] Test 1
[x] Test 2

Test Coverage

Class/File
Branch
Line

Screenshots

https://user-images.githubusercontent.com/23171488/160694426-cd238583-3b19-49df-bb55-f74502fbb359.mov

@b-fein Thank you for testing! :)
The notification overflow should be fixed in 66b886c.
The dropdown location actually doesn't show up correctly on develop either, but with c68c4d0, it now works.
Regarding the animation topic: I've got the current appearance approved by @krusche, but I think wether or not we animate it is something we can quickly vote on in tomorrow's meeting. :)

Latest changes after today's dev meeting:
We keep the animation, but try to make it less distractive, especially if:

The student is filling out an exam. The pulse animation should not be distracting from the exam.
The websocket keeps disconnected for a longer period of time. The pulse doesn't need to keep blinking for a very long time, therefore we disable it after 1 minute.

All changes added in fd90d0a.
@b-fein I'd be super happy if you could verify these new changes again! :)

@b-fein @Santia-go Just merged develop, nothing changed. :)


3.3?

Is the 3.3.0 docker image on the way?
I also notice that 3.2.6 isn't on Docker Hub yet either

Bump – changes in 3.3 look great, can't wait to try them.

Anybody out there? Looks like the source is already checked in here and just needs to be published?

It would be great to see 3.3 released on Docker Hub.

@spacecowboy any ETA on this?

Due to changes related to the commercial license for 3.3 we are a bit behind on publishing this. It will be published once we have resolved a few critical issues

This is now available!  https://hub.docker.com/_/neo4j/
Note: you now have to set another environment variable on enterprise to indicate your agreement with the license.
Example:
docker run --env=NEO4J_ACCEPT_LICENSE_AGREEMENT=yes neo4j:3.3.0-enterprise

Thanks Ryan!

Awesome, thanks!


invalid syntax in settings.py

I'm new to using the resin-sdk-python. I'm using python 2.7.11 and when I try to import the resin sdk, I get a syntax error:
Traceback (most recent call last):   File "<input>", line 1, in <module>   File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import     module = self._system_import(name, *args, **kwargs)   File "/usr/local/lib/python2.7/site-packages/resin/__init__.py", line 9, in <module>     from .base_request import BaseRequest   File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import     module = self._system_import(name, *args, **kwargs)   File "/usr/local/lib/python2.7/site-packages/resin/base_request.py", line 9, in <module>     from .settings import Settings   File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import     module = self._system_import(name, *args, **kwargs)   File "/usr/local/lib/python2.7/site-packages/resin/settings.py", line 56     print(Message.INVALID_SETTINGS.format(path=config_file_path), file=sys.stderr)
but if I change the file to:
 sys.stderr.write(Message.INVALID_SETTINGS.format(path=config_file_path))
then I don't get an invalid syntax.
Am I using the sdk wrong? or am I using it wrong?

Yeah, looks like it's in commit 38156a6d3d086a0d8a6151fce0118dc68e7570f9   -- we're getting it too.

@freddystban @EyePulp thanks for your report. This is our error since print to stderr using file=sys.stderr is not supported by python 2.x. Will have a fix for this soon


Secret references do not open correctly in desktop app

Your environment

op-vscode version: 1.0.4

VS Code version:

CLI version: 2.13.1

Desktop app version: 1Password for Mac 8.10.2 (81002004)
Steps to reproduce

Open an .env file
Add a secret reference for an API Credential, made up of of UUIDs for vault and item
Command-click on the secret reference

What happened?
1Password desktop opens, but the item is not selected
What did you expect to happen?
The item is selected (made visible)

I believe this issue still occurs, but possible not reliably. More investigation is required. It will be worth looking into how we construct and open URLs under the 1Password schema.

This will still occasionally happen, but in my most recent test it appears to be working correctly in macOS and Windows. I am going to close for now.


Use LevelHistogram throughout Parquet metadata

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Related to #6129. #6105 added a new LevelHistogram struct to represent histograms recently added to the spec. There remain places where this histogram data is still represented with a Vec<i64>.
Describe the solution you'd like
Replace the remaining bare vectors (in PageIndex and ColumnIndexBuilder with the new struct.
Describe alternatives you've considered
The vectors in ColumnIndexBuilder could be left as is since they are closer to the thrift representation, but I think it's cleaner for all level histograms outside actual thrift structs to share the same interface.
Additional context
See https://github.com/apache/arrow-rs/pull/6105#discussion_r1693378223

label_issue.py automatically added labels {'parquet'} from #6135


Multiple classes on level up negatively impacts spells known when used with Prestige Classes

Describe the bug
A caster class that picks spells at level up (like wizard) that also use multiple classes for prestigeclasses does not get the correct amount of spells.
As example the Wizard with Prestige Arcane Trickster: you can pick it at level 5. At level 4 you are casterlevel 4. Starting Arcane Trickster will push you to casterlevel 6. So far that is correct.
However you can still just select 2 spells. And when Wizard spellbook hits Caster level 20 (not class level) you won't be able to select more spells for Wizard.
That means there are 20 spells you can't learn (Arcane Trickster = 10 levels, meaning 10 caster levels). For a Wizard thats not the worst since that class can learn through scrolls, but other classes?
Crossblooded Sorcerer learns spells every 2 levels but if you multiclass into Dragon Disciple you need to look out when to take it as you can easily skip the caster levels when you gain new spells (on the flip side if you take it at the right moment you get new spells every character level)
Classes that give you the entire spellbook (like Cleric or Druid) don't have this problem. You just get acces to these spells sooner.
Expected behavior
Learning all the spells you are supposed to learn. Again Wizard as an example: since new spells per level seem to be based on caster level that would mean getting 4 new spells if you get 2 caster levels by leveling up. If your caster level goes up by 3 (because a second prestige class) you shoud get 6 spells.
Save Files
To help us reproduce your issue, please attach a named save file
Please zip it or GitHub will not accept it.
Manual_6_Ready_for_Level_up.zip
Settings
Settings.zip

I am also running into this but with a single class sylvan sorcerer leveling from 6->7 with 1 rank in mythic hero
Quick_6.zip
.

Just testet with wit ToyBox 1.3.18, did not fix the issue


bump Crash version to 0.23.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@62eeacc). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6684   +/-   ##
=========================================
  Coverage          ?   82.99%
  Complexity        ?    13379
=========================================
  Files             ?     1527
  Lines             ?    49693
  Branches          ?     5956
=========================================
  Hits              ?    41242
  Misses            ?     5617
  Partials          ?     2834

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 62eeacc...3f06574. Read the comment docs.


Add network frontend + fix some bugs

TODO:

output is not scrollable
if extension switch is not toggled default is extension (I'll fix it myself)
popup.html has error (i'll fix it myself)
needs disabling all buttons until extension ID is not selected from popup
click for details should open our devtools panel


[Feature Request] rewrite domain and http security when storing cookies.

Insomnia Version: 5.16.6
Shell 1.8.4
Node 8.2.1
V8 <IP_ADDRESS>
Architecture x64

libcurl/7.59.0 OpenSSL/1.1.0h zlib/1.2.11 nghttp2/1.31.1

Operating System: linux mint

Details
I often replace one or more of the components from a production setup with locally deployed services.
The ones in production returns cookies with production domain set but for me to be able to continue on to locally deployed versions I need to change the domain and the Secure-option to localhost and off, respectively, to be able to continue.
While this is possible do manually it would be create if it where easier. Either an option to always send all cookies, regardless of domain, or to use cookies for some domains even if the call is made to localhost (or other).
Thanks.

You can get around this by using the Cookie tag to get the cookie value from a different URL and setting the Cookie header manually.

Here's an example of how to fill out the tag details after clicking on it.

Great!
It didn't work exactly as in your screenshots (the cookie name was not automatically copied) but it works.

Yes, both the cookie name and URL must be typed by the user. Glad you got it working!


Procgen

Hello, is it still possible to use a procedural generation environment in some way? Is there an older version of this project available in which I can use procedural generation (procgen)  environments?
Thanks

Hi @daanA2003 , probably the highest likelihood of success is to checkout the commit from my Hugging Face models playing procgen environments. For example, https://huggingface.co/sgoodfriend/ppo-procgen-starpilot-hard-2xIMPALA uses https://github.com/sgoodfriend/rl-algo-impls/tree/227aa2fbde36e688a09d8ad309b0947721eef160. You can find all my procgen models on HuggingFace at https://huggingface.co/sgoodfriend?search_models=procgen.
Heads up, installing rl-algo-impls before poetry is a bit more challenging, especially because gym==0.21.0 even requires an old version of setuptools==65.5.0. https://github.com/sgoodfriend/rl-algo-impls/issues/33 has some pointers.

This works fine! Thanks!

@daanA2003, I believe you got what you were looking for. Is it good to close this issue?


Add support for CPU and memory limit for deployment

Thank you for contributing to kubernetes/charts. Before you submit this PR we'd like to
make sure you are aware of our technical requirements and best practices:

https://github.com/kubernetes/charts/blob/master/CONTRIBUTING.md#technical-requirements
https://github.com/kubernetes/helm/tree/master/docs/chart_best_practices

For a quick overview across what we will look at reviewing your PR, please read
our review guidelines:

https://github.com/kubernetes/charts/blob/master/REVIEW_GUIDELINES.md

Following our best practices right from the start will accelerate the review process and
help get your PR merged quicker.
When updates to your PR are requested, please add new commits and do not squash the
history. This will make it easier to identify new changes. The PR will be squashed
anyways when it is merged. Thanks.

/assign @scottrigby

/ok-to-test

/retest

/retest

/retest

We're moving all Charts to use a resources: {} instead of specific named resources, to allow for easier setting of requested resources and limits, without cluttering the values.yaml and the README. Can you modify this commit to make that change instead?

@timstoop I really think this is out of scope. Could we merge this and proceed with refactoring later?

I do not see why it is out of scope? As those variables are added by this patch, I'd rather see them added by following our best practises. What do you say, @scottrigby?

I have delayed this now for ages, but I realize I haven't got time for it, so I'm closing this PR.


Monospaced font NOT aligned in Windows

Consolas doesn't have the Japanese characters and so it is substituting from another font.
Can you try putting that block of text in a  tag in a html page and opening it in Chrome?  I suspect the layout there will also be misaligned.

Thanks.
May be look for some CJK Monospaced Fonts.
I got it.
https://github.com/be5invis/Iosevka

BTW: Sublime Text CJK Fonts Uniform Scale.


Does Reqnroll offer a compatible package to manage dynamic tables?

Related Documentation Page
No response
Type of the problem
Missing information
Problem Description
In our project, we utilize DynamicTableHelpers to create dynamic instances and sets for processing the data. Is there an equivalent package for Reqnroll?

If we are talking about this https://github.com/marcusoftnet/SpecFlow.Assist.Dynamic lib.
It can easily be ported to Reqnroll because the original GitHub repo looks abandoned.

This will help us migrate our projects with minimal changes.

I have successfully ported the package. you can get in nuget  ReqnrollExtra.Assist.Dynamic.
If Gáspár Nagy agrees maybe in future it can be published as Reqnroll.Assist.Dynamic  (since only owners of Reqnroll can create Reqnroll.* packages)
https://github.com/olegKoshmeliuk/Reqnroll.Assist.Dynamic source code
https://www.nuget.org/packages/ReqnrollExtra.Assist.Dynamic nuget package

I have successfully ported the package. you can get in nuget ReqnrollExtra.Assist.Dynamic. If Gáspár Nagy agrees maybe in future it can be published as Reqnroll.Assist.Dynamic (since only owners of Reqnroll can create Reqnroll.* packages) https://github.com/olegKoshmeliuk/Reqnroll.Assist.Dynamic source code https://www.nuget.org/packages/ReqnrollExtra.Assist.Dynamic nuget package

Thank you very much for your help


normalization: add normalization of the options

The options could be of different types:

string
boolean
number
enum
map
list
option

Here I've added an example for each one of them:

STRING:

option example_option = "hello world";

BOOLEAN:

option example_option = true;

NUMBER:

option example_option = 42;

ENUM:

enum ExampleEnum {
  OPTION_ONE = 1;
  OPTION_TWO = 2;
}

option example_option = OPTION_ONE;

MAP:

message ExampleMessage {
  map<string, int32> example_map = 1;
}

option (map_option) = {
  key: "key1"
  value: 42
};

LIST:

message ExampleMessage {
  repeated string example_list = 1;
}

option (list_option) = [
  "item1",
  "item2",
  "item3"
];

OPTION:

option (custom_option) = {
  string_option: "hello world",
  enum_option: OPTION_ONE,
  boolean_option: true
};

The goal of this pr its to start the process of normalization of the schemas initially just for the options in the protobuf types.
About this change - What it does
It changes how the protobuf schema gets normalized before being saved
Why this way
Seems that sorting alphabetically the options its a good way to provide an invariant over the order of the options.
For the reviewers: I'm not completely familiar with protobuf nor the normalizations, please read each line of documentation (of the code and of the pr) and if anything doesn't sound right or you found something that seems wrong please discuss about it!
I've added an example for each type of option just to make sure we are not loosing any important corner case. To me sounds reasonable to order those in any case. Additional normalizations could be added in another pr

Support for normalize flag is also needed in POST /subjects/<subject> which returns ID of schema if already registered.


Collect gitlab commits

NOTE: This is the part for "Commit" Collection from this ticket: https://github.com/merico-dev/lake/issues/309
TODO:

[x] Gather all fields we used to gather in the DB from the API response
[x] Upsert records instead of insert
[x] Add docs and comment code?

Key Points

[ ] This is a breaking change
[x] New or existing documentation is updated

Description
This code gathers the first page of commits from gitlab. (Paging handled here: https://github.com/merico-dev/lake/issues/316)
Configuration
In your .env file, you will need to set up
```
# Gitlab
GITLAB_ENDPOINT=https://gitlab.com/api/v4/
GITLAB_AUTH=<your access token>
```

You can get your access token from https://gitlab.com/-/profile/personal_access_tokens
Gathering Data with Gitlab
To collect data, you can make a POST request to /task
```
curl --location --request POST 'localhost:8080/task' \
--header 'Content-Type: application/json' \
--data-raw '{
    "Plugin": "gitlab",
    "Options": {
        "projectId": <Your gitlab project id>
    }
}'
```

Screenshots
Post request to trigger collection:

Logs output:

DB Records:

Important notes
We had to use Upsert here so we did not set duplicate records. This involved setting the primary key to:
GitlabId       string gorm:"primary_key"``
And doing this:
                 err = lakeModels.Db.Clauses(clause.OnConflict{
			UpdateAll: true,
		}).Create(&gitlabCommit).Error

		if err != nil {
			logger.Error("Could not upsert: ", err)
		}

Also, we modified the logger:
newLogger := logger.New(
		log.New(os.Stdout, "\r\n", log.LstdFlags), // io writer
		logger.Config{
			SlowThreshold:             time.Second, // Slow SQL threshold
			LogLevel:                  logger.Info, // Log level
			IgnoreRecordNotFoundError: true,        // Ignore ErrRecordNotFound error for logger
			Colorful:                  true,       // Disable color
		},
	)

you can set,
LogLevel:                  logger.Silent
If you want to suppress the DB statements


function to merge all CADD predictions to a HT

The function merged all downloadable and gnomAD historical CADD predictions (for v3) and recent run for v4 into one single HT.

This is a general thought on this script and an approach but depending on how many tools you have, it may be worth while to set up a dictionary config with variables that are used in more general scripts and then run a single join ht script that could accept the keys to that dictionary. This could be very similar to https://github.com/broadinstitute/gnomad_qc/pull/299/files which just makes it easy to add new tools. I don't have strong opinion here but I think it could save you a lot of time if you adopt something similar as you add in new tools since the main logic is just joins.

We will have 4-5 tools, but each is a bit different, here is just to combine all the data we had for CADD.

I wanted to separate the data preparation from making dictionaries. We will do something similar later on to make them a dictionaries. Right now we are still deciding which strategy we will apply on the other scores.

I'm thinking where to apply the test, for each predictor, we will have multiple files to be merged into one, should we use filter_intervals just before write?


add test:watch and clean up zarr loader

Re: #108. Tests seem to be faster now -- thanks! This PR adds test:watch which allows for on-save re-running of tests during development. I also cleaned up a couple lines in the loader that we had discussed in #113.

Looked at this when you first opened it :) Do you need a release?

Nope -- just a little cleaning!


Respect --disable-gpu command line option when terminal gpu acceleration set to auto

Close #200696
Base on workbench/contrib/terminal/browser/xterm/xtermTerminal.ts#L685
Checked webgl2 if enabled after invoke getMainDiagnostics from the gpuFeatureStatus object.
Not sure if I need to do more checking with the gpuFeatureStatus object.

Thanks for the PR but we don't actually need this anymore since the canvas renderer has been removed in v1.90. Previously that would still be used even if GPU acceleration was disabled which would result in it typically being slower than the DOM renderer due to falling back to CPU rendering. For webgl, it will attempt to create the context and throw which we should handle. Given that, I think what we have already is better than your change since we don't need to async check which could result in a flicker when starting up the terminal.


Wrong subtitles shown during silence

I run into a weird issue where I can't find the cause of it (using latest git version and model: large-v3).
I generate translated subtitles from a danish audio file. The word level timings are pretty accurate.
But in some cases, It creates/imagines a "first word" where it should be silent and this "first word" starts a new segment.
In the following example, it imagines "It's" for the time "00:00:09,180 --> 00:00:09,600". which started a new segment.
Then for the whole time of subtitle index 9, for the duration of "00:00:09,600 --> 00:01:31,480" it shows the subtitle without any highlighted word, the whole time, which is wrong.
so in sum:

the first "It's" should not exist.
there should be NO subtitle shown during: 00:00:09,600 --> 00:01:31,480
the next real voice starts at 00:01:31,480

how can i prevent this?
I experimented a lot with the VAD settings, but could not get this to get fixed. Any help is much appreciated!
8
00:00:09,180 --> 00:00:09,600
[zzz321] It's Jew, South Africa, Junk Jews.

9
00:00:09,600 --> 00:01:31,480
[zzz321] It's Jew, South Africa, Junk Jews.

10
00:01:31,480 --> 00:01:31,720
[zzz321] It's Jew, South Africa, Junk Jews.

result = model.transcribe_stable(filename, task="translate", language="da", word_timestamps=True, vad_filter=True, vad_parameters=dict(threshold=0.8, min_silence_duration_ms=800, min_speech_duration_ms=300), suppress_silence=True, best_of=10, beam_size=10, min_word_dur=0.1, no_speech_threshold=0.8, vad_threshold=0.8, condition_on_previous_text=False, suppress_tokens=[], regroup=False, use_word_position=True)

The "It's" is the result of the chosen model and settings. Changing the model or the settings (e.g. reducing beam_size and best_of) can produce overall different translation which will not have the first "It's". The other settings that affect the translation for Faster-Whisper models are vad_filter and vad_parameters. When vad_filter=True, Faster-Whisper will only translated the portions of the audio that contains voice as determined by the VAD. As a result, the vad_parameters will affect which portions of the audio gets translated and potentially produce different translations.
The audio is translated then the word timestamps are computed after the fact. With less reliable word timestamp of translations, we can end up with edge case: a word starts before the a silent section and ends before the silent section ends, and so the next word starts before the end of that silent section. This would cause use_word_position=True to fail because it treats the silent as if it was inbetween the two words instead of before the first word.
So something like this likely happened:
original timestamps of "It's": 00:00:09,180 --> 00:01:30,000
original timestamps of "Jew": 00:01:30,000 --> 00:01:31,720
silent section detected by VAD: 00:00:09,600 --> 00:01:31,480
That line is shown from 00:00:09,600 --> 00:01:31,480 because gaps are within a segment only causes words to be not highlighted during those gaps. Only gaps between segments are not shown, or else the small gaps between words will cause the whole segment to flicker in and out constantly. By default, segments with gaps larger than 0.5 second are split into smaller segments because regroup=True. However, you used regroup=False so the large gap from 00:00:09,600 to 00:01:31,480 did not cause "It's" to split off into its own segment. If you want to split at gaps like regroup=True, but do not want its other regrouping steps, you can use regroup="sg=0.5"

The split by gap helps with the issue point:

there should be NO subtitle shown during: 00:00:09,600 --> 00:01:31,480

But the "It's" is still on the wrong time, it should be part of "00:01:31,480 --> 00:01:31,720" and not before the long silence pause.
I have a similar second case. With split by gap set to 4 seconds, as everything below breaks basically every sentences apart, I get a result like this:
12
00:00:07,800 --> 00:00:08,260
[alexxxx] Are

13
00:01:13,540 --> 00:01:14,100
[alexxxx] we ready?

14
00:01:14,100 --> 00:01:14,300
[alexxxx] we ready?

so the main issue here, is the first "Are", which is again WAY off.
The person is saying "are we ready?" but he starts speaking this at aroound "00:01:13,540" and not "00:00:07,800 --> 00:00:08,260" which is totally wrong.
So there is some issue here, with the timestamp of the first word.
It only appears sometimes, but it happens.

I just run another test, now with
vad_filter=False

with disabled vad_filter, the subtitles are correct in time but with tons of hallucination.
the "Are" is not "way off" like before with vad_filter=True.
So there is an issue with positioning the first word starting a phrase before the detected VAD silence instead of correctly positioning the first word after the silence.
28
00:01:12,140 --> 00:01:12,340
[alexxxx] .org community Are we ready, Havaa?cze

29
00:01:12,340 --> 00:01:14,120
[alexxxx] .org community Are we ready, Havaa?cze

30
00:01:14,120 --> 00:01:14,300
[alexxxx] .org community Are we ready,

Word-level timing for translations are prone to these issues because the timestamp adjustment step requires reliable timestamps. I'd suggest disabling the adjustment step with suppress_silence=False or only work with segment-level timestamps with word_timestamps=False.

Using suppress_silence=False does not make any difference in this issue case with translate.
As long as vad_filter=True is set, splitted phrases like:
I
have it, I have it.
...
The
other one was B

will get produced instead of:
I have it, I have it.
...
The other one was B

I tested all kind of parameters and the only parameter which creates this issue case is vad_filter=True.
no matter what suppress_silence, suppress_word_ts, vad and use_word_position is set.
By enabling vad_filter, the time between "I" and "have" increases A LOT. I run into cases where 10-20 seconds getting in between, which produces:

way too early shown subtitles where subtitles are shown during silence and the first highlighted word which is set too early is completely wrong.

I also looked through the code, there is no real logic existing to prevent this case.
My usecase is:

translate non-english to english
file is around 1 hour long, so vad_filter should be used, otherwisethe processing time gets a lot longer.
reult should produce full sentences if possible, no splitting at comma.

right now i am using the following regrouping:
result.clamp_max()
result.split_by_punctuation(['.', '。', '?', '!', '？'])
result.split_by_gap(4.0)

I need a way to prevent this issue for the "translate" results.

31
00:04:28,740 --> 00:04:29,180
I

32
00:04:35,100 --> 00:04:37,240
have it, I have it.

nonspeech_sections printed for this time frame:
{'start': 253.0, 'end': 267.94}, {'start': 268.26, 'end': 268.34}, {'start': 268.52, 'end': 276.74},

I tested all kind of parameters and the only parameter which creates this issue case is vad_filter=True.
no matter what suppress_silence, suppress_word_ts, vad and use_word_position is set.

Then this seems to be an issue caused by Faster-Whisper's implementation of vad_filter. When suppress_silence=False, the timestamps remain mostly unaltered as return by faster_whisper.WhisperModel.transcribe().

so the "I" is located in the nonspeech_section for {'start': 268.52, 'end': 276.74},

The nonspeech_sections are only used for trimming the duration of words and segments after Faster-Whisper returns the timestamps (i.e. it won't extend the end of the "I" to start of "have"). So what has likely occurred is that Faster-Whisper returned "I" with timestamps that happened to overlap the nonspeech_sections computed by Stable-ts. You can confirm this by calling the faster_whisper.WhisperModel.transcribe() directly (which is just model.transcribe() instead of model.transcribe_stable() without the Stable-ts parameters) then checking the timestamps.
result_gen, info = model.transcribe('audio.wav', vad_filter=True, word_timestamps=True, task='translate')
segments = []
for segment in result_gen:
    segment = segment._asdict()
    segment['words'] = [w._asdict() for w in words]
    segments.append(segment)
result = stable_whisper.WhisperResult(segments)

If this is the case, you can try to change the default settings for vad_parameters for Faster-Whisper.
https://github.com/SYSTRAN/faster-whisper/blob/d57c5b40b06e59ec44240d93485a95799548af50/faster_whisper/vad.py#L25-L35
For example:
result = model.transcribe_stable(..., vad_parameters=dict(min_speech_duration_ms=1000))

If changing vad_parameters do not help, I'd suggest submitting an issue on Faster-Whisper's repo.


BUG Make template lookup use 'type' correctly

Dependency of https://github.com/silverstripe/silverstripe-cms/issues/1572
Rather than having classes (such as FormField) attempting to do its own path concatenation, pass in the 'type' property correctly to the template finder so that namespaced classes have the correct template paths.
Pulled out of an upcoming CMS namespace fix to resolve issue with namespaced templates.

Ok, tests should be finally running against the new code. :D

I've reverted the changes to the FormField.php template lookup; This is no longer a dependency of the cms namespace work, but I'd still like to get this merged anyway.


Problem with DelayedJob Psych gem when upgrading to Ruby 2.7.5

Hi Everyone,
I ran into a parsing error after upgrading to Ruby 2.7.5.
This is due to a bug in the Psych gem which affects DelayedJob in an unexpected way.  I explain my work-around (below), but I raise this issue, because I'm thinking that others might run into a problem like this, and that maybe the gem maintainers would like to prevent it in some way.
The error I saw was Last Error: invalid value for Integer(): "157653091864_1_"  and happening during object.to_yaml in the DelayedJob gem (full stack trace is below): https://github.com/collectiveidea/delayed_job/blob/master/lib/delayed/backend/base.rb#L68
      def payload_object=(object)
        @payload_object = object
        self.handler = object.to_yaml
      end

In my gemfile I had this:
gem 'delayed_job_active_record', '~> 4.1.4'
I upgraded to 4.1.6 but it did not solve the problem.
After some investigation, I found that<PHONE_NUMBER>64_1_ referred to the name of a user's profile photo uploaded with the paperclip gem.
In the database, this user record has an attribute of photo_file_name with a value of "157653091864_1_"  On that user record, when I change the file name to<PHONE_NUMBER>64_1_.jpg the error doesn't happen.
The error happens when I run my example my_method_goes_here for all users:
User.find_each do |user|
  user.delay(priority: 3).my_method_goes_here
end

I see that I can prevent the bug from affecting my application by rewriting the method and making the class the payload object instead of the individual user record like this:
User.find_each do |user|
  User.delay(priority: 3).my_method_goes_here(user_id)
end

This works because the user isn't passed in as an argument, so any JSON problems on the user record won't trigger any parsing errors.
What do you y'all think?
Full Stack Trace:
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/scalar_scanner.rb:104:in `Integer'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/scalar_scanner.rb:104:in `parse_int'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/scalar_scanner.rb:95:in `tokenize'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:279:in `visit_String'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:136:in `accept'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:523:in `block in emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `each'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:506:in `dump_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:134:in `accept'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:359:in `block in visit_Enumerator'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:359:in `each'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:359:in `visit_Enumerator'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:351:in `visit_Array'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:136:in `accept'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:523:in `block in emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `each'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:506:in `dump_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:134:in `accept'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:523:in `block in emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `each'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:521:in `emit_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:506:in `dump_coder'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:134:in `accept'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/visitors/yaml_tree.rb:118:in `push'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych.rb:513:in `dump'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/psych/core_ext.rb:13:in `to_yaml'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/backend/base.rb:68:in `payload_object='
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:51:in `public_send'
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:51:in `_assign_attribute'
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:44:in `block in _assign_attributes'
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:43:in `each'
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:43:in `_assign_attributes'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/attribute_assignment.rb:23:in `_assign_attributes'
/app/vendor/bundle/ruby/2.7.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_assignment.rb:35:in `assign_attributes'
/app/vendor/bundle/ruby/2.7.0/gems/attr_encrypted-3.1.0/lib/attr_encrypted/adapters/active_record.rb:28:in `perform_attribute_assignment'
/app/vendor/bundle/ruby/2.7.0/gems/attr_encrypted-3.1.0/lib/attr_encrypted/adapters/active_record.rb:36:in `assign_attributes'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/core.rb:315:in `initialize'
/app/vendor/bundle/ruby/2.7.0/gems/oink-0.10.1/lib/oink/instrumentation/active_record.rb:60:in `initialize'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/inheritance.rb:66:in `new'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/inheritance.rb:66:in `new'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/backend/base.rb:16:in `enqueue_job'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/backend/base.rb:12:in `enqueue'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/message_sending.rb:11:in `method_missing'
/app/app/models/asynchronous_action.rb:581:in `block in send_weekly_announcements'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:70:in `block (2 levels) in find_each'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:70:in `each'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:70:in `block in find_each'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:136:in `block in find_in_batches'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:238:in `block in in_batches'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:222:in `loop'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:222:in `in_batches'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:135:in `find_in_batches'
/app/vendor/bundle/ruby/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:69:in `find_each'
/app/app/models/asynchronous_action.rb:579:in `send_weekly_announcements'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/performable_method.rb:26:in `perform'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/backend/base.rb:81:in `block in invoke_job'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/backend/base.rb:78:in `invoke_job'
/app/vendor/bundle/ruby/2.7.0/gems/newrelic_rpm-<IP_ADDRESS>7/lib/new_relic/agent/instrumentation/delayed_job_instrumentation.rb:163:in `block in invoke_job'
/app/vendor/bundle/ruby/2.7.0/gems/newrelic_rpm-<IP_ADDRESS>7/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:376:in `perform_action_with_newrelic_trace'
/app/vendor/bundle/ruby/2.7.0/gems/newrelic_rpm-<IP_ADDRESS>7/lib/new_relic/agent/instrumentation/delayed_job_instrumentation.rb:162:in `invoke_job'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:230:in `block (2 levels) in run'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:230:in `block in run'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/benchmark.rb:308:in `realtime'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:229:in `run'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:312:in `block in reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:312:in `reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:213:in `block in work_off'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:212:in `times'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:212:in `work_off'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:175:in `block (4 levels) in start'
/app/vendor/ruby-2.7.5/lib/ruby/2.7.0/benchmark.rb:308:in `realtime'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:174:in `block (3 levels) in start'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:173:in `block (2 levels) in start'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:172:in `loop'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:172:in `block in start'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:79:in `block in add'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/worker.rb:171:in `start'
/app/vendor/bundle/ruby/2.7.0/gems/delayed_job-4.1.8/lib/delayed/tasks.rb:9:in `block (2 levels) in <top (required)>'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `synchronize'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
/app/vendor/bundle/ruby/2.7.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/app/vendor/bundle/ruby/2.7.0/bin/rake:23:in `load'
/app/vendor/bundle/ruby/2.7.0/bin/rake:23:in `<top (required)>'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli/exec.rb:63:in `load'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli/exec.rb:63:in `kernel_load'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli/exec.rb:28:in `run'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli.rb:474:in `exec'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli.rb:30:in `dispatch'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/cli.rb:24:in `start'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/exe/bundle:49:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/lib/bundler/friendly_errors.rb:128:in `with_friendly_errors'
/app/vendor/bundle/ruby/2.7.0/gems/bundler-2.2.21/exe/bundle:37:in `<top (required)>'
/app/bin/bundle:3:in `load'
/app/bin/bundle:3:in `<main>'	2021-12-27 11:27:24 -0500

this may solve your problem
https://github.com/paper-trail-gem/paper_trail/issues/1267#issuecomment-720432121

Thank you @houdl.  I solved the problem with a refactor.  I hope that your link solves the problem for other people.


Create kedro plugin structure

Goal: create project structure and empty plugin.
Project layout:
+-src/
|   |
|   +- kedro_dvc/
|       |
|       +- __init__.py      -- public exports
|       +- kedro_dvc.py -- core plugin
|       +- data.py
|       +- nodes.py
|       +- pipelines.py
|       +- experiments.py
|       +- cli.py
|
+-tests/
    |
    +- kedro_dvc/
     |  |
     |  +- test_....py
     +- data
     |  +- test_....py
     ...
     |
    +- fixtures/
        |
        ...

In src/kedro_dvc, no need to create anything but core kedro_dvc.py for the moment, but the above shows intended layout. The python modules for data, ..., can become sub-packages as necessary. In tests/ we can
recapitulate the structure for unit tests.

[x] Read about kedro plugins as well as enough of rest of documentation to understand.

[ ] create plugin for dvc, write test of plugin creation in conjunction with [https://github.com/FactFiber/kedro-dvc/issues/2]

(added initial project source layout to issue)

Note: the layout pictured doesn't all exist, but it needs content first.


Add inference code

Hello,
I wrote a demo code for inference, hope it helps.

Hi, sorry for the late reply.
I update my code with validation part. The test on the sequence 08(validation set) is done.
Here is the performance. I think it's no problem.
Result


Map

The player should have access to a map that allows them to view the surrounding area.

[ ] Implement a map menu which allows the player to view all of the surrounding area.
[ ] Implement detailed indicators that appear on the map and describe the map's contents

[ ] Ore
[ ] Enemies
[ ] Terrain (bodies of water, mountains, desert, grass, etc.)

Recommendation: Using a shortcut like "M" to access the map


failed to list *v1alpha1.ServersTransportTCP

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I got this error with k8scrd env with source code version 2.10
W0608 10:29:41.074101   91567 reflector.go:424] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope
E0608 10:29:41.074281   91567 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: Failed to watch *v1alpha1.ServersTransportTCP: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope

But I searched for previous versions, such as 2.9.10, and there was no code related to ServersTransportTCP.
So is this code added after version 2.10?
Based on the official website's RBAC configuration and other settings, after configuring the provider as k8scrd in the code, and configuring the endpoint, token, and certAuthFilePath, this error occurred upon starting up.
What did you see instead?
how can i resolve this?
What version of Traefik are you using?
2.10
What is your environment & configuration?
# (paste your configuration here)
#providers:
#  kubernetesCRD:
#    endpoint: "https://<IP_ADDRESS>:6443"
#    token: "eyJhbGciOiJSUzI1NiIsImtpZCI6InZYbmFDUVdFMlJwdjRKWi03aFdaRm9vSEExeFk1cVVrTHRIMWdYVEhpOVkifQ.eyJhdWQiOlsiaHR0cHM6Ly9rdWJlcm5ldGVzLmRlZmF1bHQuc3ZjLmNsdXN0ZXIubG9jYWwiXSwiZXhwIjoxNjg2MTExNDg0LCJpYXQiOjE2ODYxMDc4ODQsImlzcyI6Imh0dHBzOi8va3ViZXJuZXRlcy5kZWZhdWx0LnN2Yy5jbHVzdGVyLmxvY2FsIiwia3ViZXJuZXRlcy5pbyI6eyJuYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsInNlcnZpY2VhY2NvdW50Ijp7Im5hbWUiOiJhZG1pbi11c2VyIiwidWlkIjoiNTcxYjg1YjktMmMxNi00ZjM5LWI1NzEtNDI0MjliZWQ4MzBjIn19LCJuYmYiOjE2ODYxMDc4ODQsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlcm5ldGVzLWRhc2hib2FyZDphZG1pbi11c2VyIn0.l-O23a6_vFOX5gJ_02yPYyJUW-qzXn1ekkI2SDyBHBPw4NyougpYf0bDyKbo1nD5HrXLvNK8OWGBZZBOq3EaxUhhWMSqqiapxOjmMRZAzXxGdaJW0365Ou3yy5RgtnaNo6lXNKHzsp1TlJRwT__tf5IyI3qrrqX8qNHkppg3iHTI_qkJ4x6QHR1SkNa1ElmZ5gR2mjuULKlOnim1XLCP4rDQA2z_QSuX1qBOiN3kQXzlWDlUZTPOJF00oxfa3XH5p6Tn_uGaYVRhEZmtoGnUMto6X-D42JAgfQ8IB8za2ALIZatUdsig2vPBl54_4FBVwDeQiemhdE0zQZV3jBuHVA"
#    namespaces:
#      - "default"
#    certAuthFilePath: "/Users/user/develop/k8s-auth.crt"

Add more configuration information here.
If applicable, please paste the log output in DEBUG level
W0608 10:29:41.074101   91567 reflector.go:424] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope
E0608 10:29:41.074281   91567 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: Failed to watch *v1alpha1.ServersTransportTCP: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope
W0608 10:29:42.588000   91567 reflector.go:424] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope
E0608 10:29:42.588064   91567 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: Failed to watch *v1alpha1.ServersTransportTCP: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope
W0608 10:29:45.035382   91567 reflector.go:424] pkg/mod/k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.ServersTransportTCP: serverstransporttcps.traefik.io is forbidden: User "system:serviceaccount:kube-system:infra-dev" cannot list resource "serverstransporttcps" in API group "traefik.io" at the cluster scope

Hello @irwinai,
Thanks for your interest in Traefik,
In v2.10 a new CRDs APIVersion has been introduced, please check the migration guide.


Release 1.1 tracking: Verification, changelog entries

For a list of open issues, see the 1.1 milestone: https://github.com/readthedocs/sphinx_rtd_theme/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.1
This is a meta-level issue to track that new PRs for 1.1 have a little extra verification since CI tests have had difficulties

[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/967 and https://github.com/readthedocs/sphinx_rtd_theme/pull/1330 - ~check with html4 writer~ the writer works, but the theme doesn't respect it and emits an html5 doctype regardless of the html4_writer=True config value.
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1116 - ~how old versions of pip accept setup.cfg?~ Edit: it's setuptools that generates the release package that's responsible for reading it, which it can do since 2016
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1080 - changelog entry missing
[x] https://github.com/readthedocs/sphinx_rtd_theme/issues/1309 - changelog entry missing
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1215 - changelog entry missing
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1334 - changelog entry missing
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1084 - changelog entry missing
[x] https://github.com/readthedocs/sphinx_rtd_theme/pull/1345 - changelog entry missing

Updates incoming for every PR that needs verification + changelog entry.

Releaseed!


Fixed the result screen #80

Earlier the result screen was not visible clearly, now I have fixed that and it will appear as this.
Fixed issue number - #80

@Priyanshu2631 could you please add the labels to this PR as mentioned in issue #80 because it is not considered in the leaderboard without the labels.


SQLSTATE[HY000]: General error: 1525 Incorrect TIMESTAMP value: '%%'

DriverException in AbstractMySQLDriver.php line 106:
OR date LIKE '%%'
8.at call_user_func_array(object(Closure), array(object(Request))) in HttpKernel.php line 145
9.at HttpKernel->handleRaw(object(Request), '1') in HttpKernel.php line 66
10.at HttpKernel->handle(object(Request), '1', true) in Application.php line 586
11.at Application->handle(object(Request)) in Application.php line 563
12.at Application->run() in base.php line 32
13.at require_once('/var/www/html/fulldata/admingenerator/web/controllers/base.php') in index.php line 13

From my experience, this occurs when using MySQL-Server v8. Try downgrading your MySQL-Server version down to 5.7

This is a nice project but I think developer has stopped working on it. Please try this new project: https://github.com/Muhammadinaam/speed-admin


Cannot customize the search placeholder

The default text "Enter your search here..." is hardcoded

Great thanks but i think that you open the pull request on your own repo.

Woops ...
This should be better
https://github.com/KleeGroup/focus-components/pull/264