[CRASH] Android 6.0.1 crashes with java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so

I uploaded a RN0.60.4 release build to Google Play and they ran automated tests leading to a lot of crashes coming in with the following stack trace:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 738(SoLoader.java:738)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName + 591(SoLoader.java:591)
       at com.facebook.soloader.SoLoader.loadLibrary + 529(SoLoader.java:529)
       at com.facebook.soloader.SoLoader.loadLibrary + 484(SoLoader.java:484)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> + 20(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create + 27(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run + 949(ReactInstanceManager.java:949)
       at java.lang.Thread.run + 818(Thread.java:818)

Affected OS is always 6.0.1. Interestingly Hermes is not even enabled in my build.gradle:
project.ext.react = [
  entryFile: "index.android.js",
  enableHermes: false,  // clean and rebuild if changing
  bundleInDebug: false,
  bundleInRelease: true,
  root: "../../",
 ]
...
def enableHermes = project.ext.react.get("enableHermes", false);
...
// Hermes config
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }

I looked into the app bundle and extracted the apk for the device type that is crashing. It contains the libjsc.so file but not the libhermes.so. Imho this is correct because my gradle is configured to not include it. The big question is why does it want to load it if it not enabled? What also surprised me is that I found libhermes-executor-release.so and libhermes-executor-debug.so in it too.  I guess, they should be excluded?

I filed a report with the Hermes project here but they referred me to here.
React Native version:

System:
    OS: macOS 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 88.63 MB / 32.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
    Android SDK:
      API Levels: 23, 26, 27, 28
      Build Tools: 23.0.1, 25.0.0, 26.0.3, 27.0.3, 28.0.1, 28.0.2, 28.0.3
      System Images: android-24 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
    Xcode: 10.3/10G8 - /usr/bin/xcodebuild
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-native: ^0.60.4 => 0.60.4
  npmGlobalPackages:
    eslint-plugin-react-native: 3.5.0
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

Steps To Reproduce

Upload an RN0.60.4 app bundle with crash reporting to Playstore
check the crash reports

Describe what you expected to happen:

The Google Play devices should not crash.
Hermes library should not be loaded if disabled.
libhermes-executor-release.so and libhermes-executor-debug.so should not get bundled

I think this is related to my issue I posted on the Hermes repo.
https://github.com/facebook/hermes/issues/80

I am not so sure, because I did not even have Hermes activated because I was experiences issues even building it. However, the devices that run the app crash because they try to load it but it is not bundled (as configured).

I'm having occasional crashes like this in production with hermes disabled also on 0.60.4

I am also having similar crashes as described here but WITH having hermes enabled as  described wtihin https://github.com/facebook/hermes/issues/76 .
Any idea why that might be happening?

Having this issue too, when hermes disabled.
Device
Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.3 GB
Disk free: 2.06 GB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 738(SoLoader.java:738)        at com.facebook.soloader.SoLoader.loadLibraryBySoName + 591(SoLoader.java:591)        at com.facebook.soloader.SoLoader.loadLibrary + 529(SoLoader.java:529)        at com.facebook.soloader.SoLoader.loadLibrary + 484(SoLoader.java:484)        at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> + 20(HermesExecutor.java:20)        at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create + 27(HermesExecutorFactory.java:27)        at com.facebook.react.ReactInstanceManager$5.run + 949(ReactInstanceManager.java:949)        at java.lang.Thread.run + 818(Thread.java:818)

Having this issue too, when hermes disabled.
RN: 0.60.4
Device
Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.3 GB
Disk free: 2.06 GB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 738(SoLoader.java:738) at com.facebook.soloader.SoLoader.loadLibraryBySoName + 591(SoLoader.java:591) at com.facebook.soloader.SoLoader.loadLibrary + 529(SoLoader.java:529) at com.facebook.soloader.SoLoader.loadLibrary + 484(SoLoader.java:484) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> + 20(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create + 27(HermesExecutorFactory.java:27) at com.facebook.react.ReactInstanceManager$5.run + 949(ReactInstanceManager.java:949) at java.lang.Thread.run + 818(Thread.java:818)

这个如何解决?

same problem in 5.1.1

anyone fixed it?

issue
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
use version 0.60.0

I got the same problem if I integrate my react-native-app to an existing android-app. I use react-native-version 0.60.4.

Having the same issue, the project works fine on my local emulator but it gives the exact same error
with @wsdt , any solutions yet?

How is react 60 stable I don't understand.
I have had crashes for
Device
Brand: LGE
Model: Nexus 5X
React Native Version: 0.60.3
Android Version: 6.0.1
I had created android app bundle( .aab file ) with hermes enabled. I have only debug and release variant. release variant has this problem.
Issue is opened on Aug 3 and it's been so many days, not a single working fix is available. Really frustrating.

Hey @arjun-livquik you will need to build apk if you plan to have hermes enabled as its not currently compatible with app bundles.
https://github.com/facebook/react-native/issues/25927#issuecomment-534650110

Thanks @owinter86
Could be that app might work just fine with APKs, because I have submitted APKs for staging build and had never seen this crash.
Sure will use APKs instead.

Hello.
Have you tried with the latest release of Hermes?
https://github.com/facebook/react-native/issues/25646#issuecomment-527116145
Of course, the "sdk<=19" problem does not apply to you, but there were lots of other fixes to Hermes too.
BTW, I built and submitted .aab release builds with hermes to the Play Store, and they haven't had any problems.
Also, be sure to clean the android build folders (I usually build with "./gradlew clean assembleRelease bundleRelease", just in case) if you change the "hermes enabled/disabled" setting.
Cheers!

@jsaraiva Ofcourse I run ./gradlew clean bundleRelease everytime for creating .aab file. I have now rolled out to Alpha with all the APKs along with universal apk for now.

"couldn't find DSO to load: libhermes.so "
React Native Version: 0.61.2
enableHermes: false
Still facing this issue

received from crashlytics
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java)
       at java.lang.Thread.run(Thread.java:760)

Brand: Xiaomi
Model: Redmi 4X
Orientation: Portrait
RAM free: 1.49 GB
Disk free: 18.04 GB
Version: 7.1.2
Orientation: Portrait
Rooted: No

I'm seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, only on android 6 LGE devices.

I am also seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, on google nexus 5x
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
       at java.lang.Thread.run(Thread.java:818)

Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.12 GB
Disk free: 218.66 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes

I was able to resolve it with a ./gradlew clean in the /android folder.

I am also seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, on google nexus 5x
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
       at java.lang.Thread.run(Thread.java:818)

Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.12 GB
Disk free: 218.66 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes

I have the same issue with the same version of android.
My Crashlytics report:

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
at com.facebook.hermes.reactexecutor.HermesExecutor.(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
at java.lang.Thread.run(Thread.java:818)

Device
Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.18 GB
Disk free: 495.84 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes
Crash
Date: Nov 5, 2019, 5:05:00 PM
App version: 2.3.2 (2320)

Same issues on Android 6.0.1
Any solution?

Any workaround for this issue, I'm trying to run a beta release on Google play and this crash shows in Crashlytics

I met the same issue and solved by this .

@Symous I have same config in the answer and the maven repo but still I have the issue.
I have React-native 0.60.5 and I'm not migrating from other versions, it's a new project.
Btw hermes is disabled in my build.gradle but still got this error.

Same issue as well, RN 0.61.2, hermes disabled, seeing the same crashes reported for Nexus 5X 6.0.1 after uploading the app bundle to Play Store alpha track. Interestingly enough, Robo tests on Firebase Test lab are successful for Nexus 5 (physical device with android 6.0.1) and Nexus 5X (virtual device with android 6.0.1). Has anybody managed to reproduce this on any physical device?

The real crash is
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: cannot locate symbol "__cxa_bad_typeid" referenced by "libjsc.so"...
111-15 17:31:41.427 372-372/com.**.** W/System.err: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: cannot locate symbol "__cxa_bad_typeid" referenced by "libjsc.so"...
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.**.**.MainActivity$4.getJavaScriptExecutorFactory(MainActivity.java:879)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:73)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:41)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.**.**.MainActivity.initReactNative(MainActivity.java:951)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.**.**.MainActivity.onCreate(MainActivity.java:2737)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.Activity.performCreate(Activity.java:6186)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1109)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2388)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2508)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.ActivityThread.access$900(ActivityThread.java:165)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1413)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.os.Handler.dispatchMessage(Handler.java:102)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.os.Looper.loop(Looper.java:179)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at android.app.ActivityThread.main(ActivityThread.java:5509)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at java.lang.reflect.Method.invoke(Native Method)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at java.lang.reflect.Method.invoke(Method.java:372)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:961)
11-15 17:31:41.427 372-372/com.**.** W/System.err:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:756)

You guys may find this https://github.com/facebook/react-native/issues/25986#issuecomment-520424504 relevant.

@woshi82 that probably may be related with https://github.com/android/ndk/issues/408

Try with https://react-native-community.github.io/upgrade-helper steps

Keep getting the same error in spite of disabling Hermes. My react-native version is 0.61.2

same here, react-native 0.61.4

Same issue:
React Native: 0.61.5
Brand: LGE
Model: Nexus 5X
SO: 6.0.1
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so
com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java)
com.facebook.soloader.SoLoader.assertInitialized (SoLoader.java)
com.facebook.soloader.SoLoader.assertInitialized (SoLoader.java)
com.facebook.soloader.SoLoader.assertInitialized (SoLoader.java)
com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> (HermesExecutor.java)
com.facebook.hermes.reactexecutor.HermesExecutorFactory.create (HermesExecutorFactory.java)
com.facebook.react.ReactInstanceManager$5.run (ReactInstanceManager.java)
java.lang.Thread.run (Thread.java:818)

Android build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 28
    }
    repositories {
        google()
        jcenter()

        maven {
           url 'https://maven.fabric.io/public'
        }
    }
    dependencies {
        classpath("com.android.tools.build:gradle:3.4.2")
        classpath 'com.google.gms:google-services:4.3.3'

        // Add dependency
        classpath 'io.fabric.tools:gradle:1.31.2'  // Crashlytics plugin

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenLocal()
        google()
        jcenter()
        maven { url 'https://jitpack.io' }
    }
}

android/app/build.gradle
apply plugin: "com.android.application"
apply plugin: 'io.fabric'

crashlytics {
  enableNdk true
}

import com.android.build.OutputFile

project.ext.react = [
    entryFile: "index.js",
    enableHermes: true,  // clean and rebuild if changing
]

apply from: "../../node_modules/react-native/react.gradle"

def enableSeparateBuildPerCPUArchitecture = true
def enableProguardInReleaseBuilds = true
def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);

def keystorePropertiesFile = rootProject.file("keystore.properties")
def keystoreProperties = new Properties()
keystoreProperties.load(new FileInputStream(keystorePropertiesFile))

android {
    compileSdkVersion rootProject.ext.compileSdkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    defaultConfig {
        applicationId "com.myapp"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 5
        versionName "1.0.2"
        missingDimensionStrategy 'react-native-camera', 'general'
        multiDexEnabled true
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
    signingConfigs {
        debug {
            storeFile file(rootDir.getCanonicalPath() + '/' + keystoreProperties['debugKeyStore'])
            storePassword keystoreProperties['debugStorePassword']
            keyAlias keystoreProperties['debugKeyAlias']
            keyPassword keystoreProperties['debugKeyPassword']
        }
        release {
            keyAlias keystoreProperties['releaseKeyAlias']
            keyPassword keystoreProperties['releaseKeyPassword']
            storeFile file(rootDir.getCanonicalPath() + '/' + keystoreProperties['releaseKeyStore'])
            storePassword keystoreProperties['releaseStorePassword']
        }
    }
    buildTypes {
        debug {
            signingConfig signingConfigs.debug
        }
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://facebook.github.io/react-native/docs/signed-apk-android.
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // https://developer.android.com/studio/build/configure-apk-splits.html
            def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }

        }
    }
}

dependencies {
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.facebook.react:react-native:+"  // From node_modules

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)
apply from: "../../node_modules/react-native-vector-icons/fonts.gradle"
apply plugin: 'com.google.gms.google-services'

+1
RN Version: 0.60.4
Release Method: signed Bundle
Rolled back to signed APK now.

Still happening to production users randomly on 0.61.5 with Hermes disabled building as a bundle.

For me rolled back to APK works but because I was dissatisfied with it, decided to investigate.
I "solved" (not sure but the error didn't pop during googleplay pre-launch reports) the issue by forcing a specific version of soLoader
in build.gradle
android {
    defaultConfig {
      // let your old config
        ndk {
            abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
       }
    }
}

I also made a  stackoverflow question , maybe we can get more help from the community.

I had the same issue and was because I forget to update the (app/android)/buld.gradle, as say the documentation, I checked the changes with https://react-native-community.github.io/upgrade-helper/?from=0.59.10&to=0.61.5 and updated those files, also check the other files, but the important part is
dependencies {
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.facebook.react:react-native:+"  // From node_modules

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
}

apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)

We are getting this error everytime we want to do a --variant=release build after doing a debug one. Doing /gradlew clean fixes it.

Just to make sure this does not confuse anyone - our error was actually java.io.UncheckedIOException: java.io.FileNotFoundException: .../android/app/build/intermediates/transforms/stripDebugSymbol/release/0/lib/x86_64/libhermes-executor-release.so (No such file or directory), not exactly the one that is mentioned in the subject. We believe it might have been solved after deleting the /android/.gradle folder and re-building but need to do more tests.

/android/gradlew clean told me clean was undefined for some reason. Manually deleting the /android/.gradle folder and rebuilding fixed it for me.

Fixed with changing SoLoader version to 0.8.2 according to 0.62 react-native configuration.
https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties
    configurations.all {
        resolutionStrategy {
            force "com.facebook.soloader:soloader:0.8.2"
        }
    }

I added this in project gradle:
allprojects {
repositories {
google()
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
maven {
url 'https://maven.google.com'
}
}
}

same for me

Fixed with changing SoLoader version to 0.8.2 according to 0.62 react-native configuration.
https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties
    configurations.all {
        resolutionStrategy {
            force "com.facebook.soloader:soloader:0.8.2"
        }
    }

Awesome. This fixed it for us 💪
But sadly this isn't in React Native 0.62.2 as I discovered the issue after upgrading to it.
The v0.63.0-rc.1 however already contains it , so I guess it will come soon.
As it is in the master here already I guess it is considered safe to upgrade the soloader to 0.8.2.
Did anyone experience any issue because of it so far?

Fixed with changing SoLoader version to 0.8.2 according to 0.62 react-native configuration.
https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties
    configurations.all {
        resolutionStrategy {
            force "com.facebook.soloader:soloader:0.8.2"
        }
    }

In which file do you apply this edit?

Fixed with changing SoLoader version to 0.8.2 according to 0.62 react-native configuration.
https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties
    configurations.all {
        resolutionStrategy {
            force "com.facebook.soloader:soloader:0.8.2"
        }
    }

In which file do you apply this edit?

I've added it somewhere in the middle of the large android block of the android/app/build.gradle

same here, react-native 0.62.2

Upgraded my react native version to the 63 rc1 and forced soloader 8.2. I checked the package version number of the SoLoader.java:825 and see that its correctly 8.2. Still getting the issue :/

Upgraded my react native version to the 63 rc1 and forced soloader 8.2. I checked the package version number of the SoLoader.java:825 and see that its correctly 8.2. Still getting the issue :/

With 8.2 I was getting crashes on Android 4 and, if I remember correctly, Android 5. I updated to 9.0 and most of these crashes are gone, however I still experience a minimal amount of crashes related to soloader.

For me this issue was due to SoLoader.loadLibrary("jscexecutor");
Debugging more into it i found its due to couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libgnustl_shared.so" not found
Finally i arrived at below solution which fixed my issue.
replacing implementation jscFlavor with implementation "org.webkit:android-jsc:r245459"  where jscFlavor=org.webkit:android-jsc:+ in app's gradle file

Important info if you use Hermes
I updated from 61.5 to 62.2 and got cash on android:
couldn't find DSO to load: libhermes-executor-debug.so
I fixed it by adding following string to android/app/build.gradle:
implementation "org.webkit:android-jsc:+"

Important info if you use Hermes
I updated from 61.5 to 62.2 and got a crash on android:
couldn't find DSO to load: libhermes-executor-debug.so
I fixed it by adding following string to android/app/build.gradle:
implementation "org.webkit:android-jsc:+"

can confirm this make my app apk size increase 10+MB and crash on all the devices

Upgraded to RN 0.62.2 and have the below crash in production
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
at com.facebook.hermes.reactexecutor.HermesExecutor.(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:29)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:997)
at java.lang.Thread.run(Thread.java:818)
Brand: Xiaomi
Model: Mi 9X
Orientation: Portrait
RAM free: 19.19 GB
Disk free: 14.78 GB
Operating System
Version: 5.1
Orientation: Portrait
Rooted: Yes
Date: Jun 22, 2020, 10:44:00 PM
Have this in my android/build.gradle
maven {             // Android JSC is installed from npm             url("$rootDir/../node_modules/jsc-android/dist") }
Any help on this would he really helpull.

How is react 60 stable I don't understand.
I have had crashes for
Device
Brand: LGE
Model: Nexus 5X
React Native Version: 0.60.3
Android Version: 6.0.1
I had created android app bundle( .aab file ) with hermes enabled. I have only debug and release variant. release variant has this problem.
Issue is opened on Aug 3 and it's been so many days, not a single working fix is available. Really frustrating.

Were you able to solve the issue. I'm also facing the same issue in version 0.61.5

Same issue none of the above solutions worked for me still a crash on Nexus5 6.0.1

It worked for me in RN version 0.62.2 by adding to android/app/build.gradle:
implementation 'com.facebook.soloader: soloader: 0.9.0+'

I can confirm I'm still having this issue with React-Native 0.62.2 though I haven't tried making any changes to my build.gradle yet.
What I can offer is this stack overflow that appears to show how to reproduce the issue: https://stackoverflow.com/questions/61544046/android-java-lang-unsatisfiedlinkerror-couldnt-find-dso-to-load
I'm uncertain at the moment which of the many fixes proposed above seems to be best. There are also many fixes presented on a similar issue here: https://github.com/facebook/SoLoader/issues/55.
Has anyone found a solution that reliably works for everyone (running /gradlew clean does not seem to work for everyone).

I can confirm I'm still having this issue with React-Native 0.62.2 though I haven't tried making any changes to my build.gradle yet.
What I can offer is this stack overflow that appears to show how to reproduce the issue: https://stackoverflow.com/questions/61544046/android-java-lang-unsatisfiedlinkerror-couldnt-find-dso-to-load
I'm uncertain at the moment which of the many fixes proposed above seems to be best. There are also many fixes presented on a similar issue here: facebook/SoLoader#55.
Has anyone found a solution that reliably works for everyone (running /gradlew clean does not seem to work for everyone).

Personally, I never found a solution so I changed my minimum requirement version.  At the time we had 10 people (testers) on the app at this time, none of them reported a crash, so I have a feeling it is google running an automated test when they put it through review. The version of android that is crashing is so old, I really felt it was not worth supporting in the end (after spending 2 days trying to fix it).

@hannahcx do you think they could have also tried this on multiple other versions? I'm having crashes on versions from 7 - 10 but it's only for 4 users total.

@jimmyceroneii After trying many, many solutions from around github/SO, the link you provided is what solved it for me.
https://stackoverflow.com/questions/61544046/android-java-lang-unsatisfiedlinkerror-couldnt-find-dso-to-load

For me rolled back to APK works but because I was dissatisfied with it, decided to investigate.
I "solved" (not sure but the error didn't pop during googleplay pre-launch reports) the issue by forcing a specific version of soLoader
in build.gradle
android {
    defaultConfig {
      // let your old config
        ndk {
            abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
       }
    }
}

I also made a  stackoverflow question , maybe we can get more help from the community.

For me adding this piece of code and also executing "./gradlew clean" command in android folder combinedly fixed the issue

Fixed with changing SoLoader version to 0.8.2 according to 0.62 react-native configuration.
https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties
    configurations.all {
        resolutionStrategy {
            force "com.facebook.soloader:soloader:0.8.2"
        }
    }

For me adding this piece of code and also executing "./gradlew clean" command in android folder combinedly fixed the issue.

RN 0.62.2 here. For me adding
configurations.all {     resolutionStrategy {         force "com.facebook.soloader:soloader:0.8.2"     } }
to my top-level build.gradle and
implementation "com.facebook.soloader:soloader:0.8.2"
as well as
ndk {     abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64" }
to my app-level build.gradle did the trick. I think that especially the latter made the difference as before both apk's and aab's showed an additional lib folder armeabi which did not contain all lib files, in particular not libhermes.so.

Hello,
I have the same worries, I've been going around in circles for several weeks because of hermes, I'm depressed: /
SoLoader: couldn't find DSO to load: libhermes-inspector.so caused by: dlopen failed: cannot locate symbol "_ZTIN8facebook6hermes8debugger13EventObserverE" referenced by "/data/data/com.test/lib-main/libhermes-inspector.so". .. result: 0
2020-11-03 11: 09: 53.512 16167-16270 / com.test E / SoLoader: couldn't find DSO to load: libhermes-executor-debug.so caused by: couldn't find DSO to load: libhermes-inspector .so caused by: dlopen failed: cannot locate symbol "_ZTIN8facebook6hermes8debugger13EventObserverE" referenced by "/data/data/com.test/lib-main/libhermes-inspector.so" ... result: 0 result: 0
2020-11-03 11: 09: 53.558 16167-16272 / com.test A / libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xffffffff in tid 16272 (mqt_js), pid 16167 (com.test )
Can somebody help me please ?

this problem occurred while I upgrading from 0.59.4 to 0.61.0
in android/app/build.gradle
I've added
project.ext.react = [
    //...
    enableHermes: true
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);

and
dependencies {
    //...
    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
    //...
}

and it works :)
hope this solution is useful for someone

This is because SOLoader is absent.
Ensure
implementation'com.facebook.soloader:soloader:0.9.0+'
is added under dependencies in android/app/build.gradlle
clean your build
cd android
./gradlew clean
Try bundling
./gradlew bundleRelease
Exit android folder
cd ../
Try running
npx react-native run-android --variant=release

@Michaelvons nice one 👍  ... but did you know why ? i have this probleme just with the last Android sdk 11 (Level 30)

Hello, could someone explain this error to me and tell me how to resolve it please?
DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I use the react-native-jitsi-meet library
Thank you

Hello, could someone explain this error to me and tell me how to resolve it please?
DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I use the react-native-jitsi-meet library
Thank you

Update packagingOptions as per mention in url:
https://github.com/react-native-community/jsc-android-buildscripts/issues/80

Four types of JS Engine, choose as mention in this article:

JSC (v241213.1.0),
new JSC(v245459.0.0),
Hermes and
react-native-v8 (BEST ONE)

Article Link https://medium.com/walmartglobaltech/react-native-memory-profiling-jsc-vs-v8-vs-hermes-1626949a653b

@Michaelvons nice one 👍 ... but did you know why ? i have this probleme just with the last Android sdk 11 (Level 30)

Same issue for me with Level 30. Please let me know the solution.

has same issue on android 4 when hermes is disabled

has same issue on android 4 when hermes is disabled

I hope this get fixed soon. Android 6.0.1 is not working in the Play Store and I am unable to reproduce this error. Is there any emulator where I can check this is failing?

I hope this get fixed soon. Android 6.0.1 is not working in the Play Store and I am unable to reproduce this error. Is there any emulator where I can check this is failing?

@napsta32 at least you should be able to reproduce error at android 4.4 emulator. Not sure about android 6

@napsta32 at least you should be able to reproduce error at android 4.4 emulator. Not sure about android 6

Any suggestion on how to verify a given solution fixes this problem?

Google Play testing always reports fatal exception on Android 6.0.1, Nexus 5X devices.
I tried copying APK to AVD ( Nexus 5, Android 6.0, API 23 ) but cannot reproduce.

Current Verification Procedure:

Search StackOverflow, GitHub, etc. and make a suggested change to a build.gradle
Upload AAB to Google Play
Wait many hours until Google Play testing triggers a Firebase Crashlytics report email notification to developer.
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
Repeat at Step #1

I have tried enableHermes: false and various versions of  resolution strategies for "com.facebook.soloader:soloader:0.9.0+ without success.

RN 0.62.2 here with hermes enabled. For me adding
configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.8.2" } }
to my top-level build.gradle and
implementation "com.facebook.soloader:soloader:0.8.2"
as well as
ndk { abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64" }
to my app-level build.gradle did the trick. I think that especially the latter made the difference as before both apk's and aab's showed an additional (fifth) lib folder armeabi which did not contain all lib files, in particular not libhermes.so.

Did this fix issue for you? I've been trying to find a solution for this problem. I too have RN version 62.2

I still have the same issue with this config:
package.json
"react": "16.13.1",
"react-native": "^0.63.4",
"@react-native-firebase/app": "^11.1.2",
"@react-native-firebase/crashlytics": "^11.1.2",

Most crashes device
Nexus 5X
Android 6.0.1

Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com

ext {
        buildToolsVersion = "29.0.2"
        minSdkVersion = 17
        compileSdkVersion = 29
        targetSdkVersion = 29
    }

Is there any difference for hermes on/off, app-bundle or APK?

any solutions?

@JmStefanAndroid Add configurations.all section  to android > build.gradle > allprojects . This solved the issue for me. Plus, I run cd android ./gradlew clean before each release.
allprojects {
    repositories {
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }

        configurations.all {
            resolutionStrategy {
                // use 0.9.0 to fix crash on Android 11
                force "com.facebook.soloader:soloader:0.9.0+"
			}
		}

        google()
        jcenter()
        maven { url 'https://www.jitpack.io' }
    }
}

In my case I needed to add hermes path for each android flavour
    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each flavour.

I'm having this same issue with the following conditions:
-RN v0.63.4
-Hermes NOT enabled -> Using JSC
-Latest SoLoader (0.10.1)
-Using app bundle
-Run gradle clean before bundleRelease
-Issue only happens to certain devices on production (multiple Android versions and manufacturers)
After digging for a while I found this PR which mentions the "cause" of this issue when considering the previously mentioned conditions.
The PR author does a really good job explaining how this problem occurs.
In short, it's not related to Hermes at all, but the real error is being discarded and Hermes is being loaded instead as a fallback, which in turn fails since it's not enabled.
That PR solves the "error swallowing" problem so the real error can be propagated when the app crashes.
Please do merge that PR so we can figure out the real cause of this problem.

In my case I needed to add hermes path for each android flavour
    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each flavour.

Thanks! This worked for us, had to add the staging flavor.

I've tried all of the above, and the result is still a failure

I'm using hermes and RN 0.64.2 and android  flavors
this combination works for me
android > build.gradle > allprojects
allprojects {
    repositories {
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }

        configurations.all {
            resolutionStrategy {
                // use 0.9.0 to fix crash on Android 11
                force "com.facebook.soloader:soloader:0.9.0+"
			}
		}

        google()
        jcenter()
        maven { url 'https://www.jitpack.io' }
    }
}

 if (enableHermes) {         def hermesPath = "../../node_modules/hermes-engine/android/";         debugImplementation files(hermesPath + "hermes-debug.aar")         releaseImplementation files(hermesPath + "hermes-release.aar")         devImplementation files(hermesPath + "hermes-release.aar")         prodImplementation files(hermesPath + "hermes-release.aar")     } else {         implementation jscFlavor     }
then
cd android
./gradlew clean
and  build again

In my case I needed to add hermes path for each android build type
    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each build type.

Thanks!

configurations.all {
resolutionStrategy {
force "com.facebook.soloader:soloader:0.8.2"
}
}

hey, for me worked when i commented also everything related to flipper :)

This and all the "couldn't find DSO to load" bugs have been fixed in React Native 0.71.
The issue on previous versions was a "too aggressive" clean-up logic in the react.gradle file. In 0.71 the clean-up logic has been rewritten to be more Android friendly and is now living inside the React Native Gradle Plugin.
I'm closing this, please update to 0.71 and open a new issue if the "couldn't find DSO to load" crash is still happening on 0.71+.


requirements install sklearn

In the requirements.txt it says sklearn should this not be scikit-learn?

Good catch! Fixed now.
https://github.com/iterative/example-pokemon-classifier/commit/3ca943df5044af5342c45b8dcd597b9415333926


[Question] Extending entity module on registration time

So, I was sooo happy when #535 was merged and with v0.35 came the possibility to register models at run time. Then I started to use this feature to be able to split my models into chunks, and import only models required by the component on screen.
Then I realized (through a bunch of nice error messages) that I use vuex-orm plugins that extend the module of entities with state, getters, mutations and actions. These plugins rely on the fact that every entity is already registered and extend modules by iterating through database.entities. Now, if I register my model in-the-fly, it won't get the module extension and will crash.
Re-reading the docs a bit I found that I could use the static state () method to add state and the static commit () method to modify it. Not my favorite, though. I find that Model.commit() is not really debug-friendly, and anyway, I would prefer to keep getters and actions too, to remain as clean in code as possible.
Another idea of mine was to extend Database from within my plugin. I could, then, extend the method register to add the required vuex-parts after executing its original task. But Database is not extendable by plugins.
Questions:

Is it intentional that Database is not extendable? Is it due to some security issue?
Or, is there any other possibility to achieve my goal?

@kiaking what do you think?
Thanks in advance!

@SzNagyMisu Actually there's no reason why Database shouldn't be extended. I just didn't thought through about the use case. But yea we should include the Database class to the plugin argument 👍
And I think to achieve your use case, extending Database might be the fastest way. In the future, maybe it's better for Vuex ORM to have some hooks that would be called when a new entity is added. Not sure.
Either way, I think Database should be included to plugins, so let's do that...!

Truly sorry, I must be really tired...
Of course, I will use Model.state() and extend Getters, RootGetters, Actions, RootActions and RootMutations to have a clean code...
So my use case seems to be irrelevant. Thanks for the feedback, though.
@kiaking feel free to close this issue.

Ah OK. Though I still think we should add Database to plugin, so I'll rename the title and keep it open!
I'm happy to hear you found a solution! Thanks for the feedback anyway 😃

This will be available in 1.0.0

This feature is now added to Vuex ORM 0.36.0 🎉
https://github.com/vuex-orm/vuex-orm/releases/tag/v0.36.0


invalid_api_key Incorrect API key provided: undefined. You can find your API key at https://platform.openai.com/account/api-keys.

Describe the bug
在npm和Vercel都尝试可以部署，但相同的openai_api_key用来部署Netlify显示部署不成功，并且报错提醒openai_api_key失效，麻烦请帮忙看看什么问题！

Reproduction
创建Netlify部署
System Info
invalid_api_key
Incorrect API key provided: undefined. You can find your API key at https://platform.openai.com/account/api-keys.

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Duplicate of #297


Missing comma in setup.py

Requirement string in install_requires in setup.py should be 'numpy>=1,<2'. Pip ignores it but I had an issue while trying to manage dependencies with conda.

Thanks, I've fixed this now


Suggestions on the "Import library" fixes from dart analysis server

(originally filed at Dart-Code/Dart-Code#320)
The "Import library" code fix is useful, but could be improved in a few ways.

If the import declarations are already sorted, insert the new import in the right place. For now I have to import and then sort as a two step process.
If the file being imported is in the current package, please consider offering the relative path import as an option.
Also please consider offering an option to import the desired library with show Foo at the end. For instance, we do import 'dart:convert' show JSON; a lot in our project.

The first two items are now implemented.
The third is tracked at https://github.com/dart-lang/sdk/issues/32234.


Fix find_end algorithm

I've found out what's wrong in the find_end algorithm. Using uninitialized memory (from the end of matching_indices) was causing undefined behaviour. It was uninitialized because search_kernel does not initialize the last <pattern_size> - 1 elements of matching_indices as the pattern can not start there. Now it's fixed.

Coverage increased (+0.005%) to 88.796% when pulling 701d6078d84656d121c8e1dcc069d5b3fb847b8f on haahh:pr_fix_find_end into 48217d2918d64ac84c13822384c67c4edcad5481 on boostorg:develop.

Thanks for fixing this!


Return COM interface from Unmanaged Export?

I am trying to implement a factory method that returns a COM compatible interface:
Steinberg::IPluginFactory* __stdcall GetPluginFactory()

I have implemented a decorated managed representation of the IPluginFactory interface and have a C++/CLI project working with this interface. The goal was to get rid of the C++/CLI interop assembly and hopefully make this work cross-platform.
I am currently getting a CS8894 error saying that the return type cannot be used. I understand it's not blittable.
Is there any chance of getting this scenario (COM interface) working?
https://github.com/obiwanjacobi/vst.net/tree/master/Source3/Code

The goal was to get rid of the C++/CLI interop assembly and hopefully make this work cross-platform.

@obiwanjacobi Laudable goal and one I fully support. The key here is to recognize that the runtime isn't going to do anything automatically for you when using DNNE. This library is a low level tool that could be coupled with a source generation mechanism that would perform the manual tasks for you though.
The manual part that needs to happen is the following:
[UnmanagedCallersOnly]
public static IntPtr GetPluginFactory()
{
    var factory = new PluginFactory();

    // Ask the runtime to create a CCW.
    IntPtr pUnk = Marshal.GetIUnknownForObject(factory);

    // Request the default interface - IPluginFactory
    var iid =  typeof(IPluginFactory).GUID;
    int hr = Marshal.QueryInterface(null, ref iid, out IntPtr pFact);
    Debug.Assert(hr == 0);

    // Release the IUnknown
    Marshal.Release(pUnk);
    return pFact;
}

Ah - of course (I knew that!) Thanks very much.
I'm getting CA1416 warnings on the Marshal calls. Any hints or tips on how to get that cross-platform? - a bit off-topic perhaps...

@obiwanjacobi That is great to hear. ComWrappers was made cross-platform in .NET 6. For .NET 5, it is only supported on Windows. The Marshal calls are potentially still marked for Windows-only on .NET 6. There are some rough edges in this due to the long history of support. Once more people are on .NET 6 I am anticipate we will get a large number of requests to fix the various CA1416 issues.


[READY] Pass unversioned key to set method

Problem
The key had the version number added to it before trying to retrieve content from the cache, then this versioned key was passed along to the set method where it was versioned again - meaning the cached version was never retrievable.
Solution
Pass the unversioned key to the set method.

:cake:

Minor release this time :wink:


Find part using lsblk instead of assume name

Fixes #155

Codecov Report

Merging #157 into development will increase coverage by 0.59%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #157      +/-   ##
===============================================
+ Coverage        23.83%   24.43%   +0.59%
===============================================
  Files               48       48
  Lines             4220     4310      +90
===============================================
+ Hits              1006     1053      +47
- Misses            3128     3171      +43
  Partials            86       86

Impacted Files
Coverage Δ

apps/plugins/base/disk/disk.go
11.49% <0%> (+2.84%)
:arrow_up:

apps/plugins/base/info/dmi.go
72.34% <0%> (+9.4%)
:arrow_up:

Continue to review full report at Codecov.

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


pytest warnings

Looks like lates pytest shows some warning
============================================================================= warnings summary =============================================================================
dask/array/tests/test_reductions.py::test_nan_object[min]
dask/array/tests/test_reductions.py::test_nan_object[min]
dask/array/tests/test_reductions.py::test_nan_object[min]
dask/array/tests/test_reductions.py::test_nan_object[max]
dask/array/tests/test_reductions.py::test_nan_object[max]
dask/array/tests/test_reductions.py::test_nan_object[max]
  /usr/lib64/python3.8/site-packages/numpy/core/fromnumeric.py:86: RuntimeWarning: invalid value encountered in reduce
    return ufunc.reduce(obj, axis, dtype, out, **passkwargs)

dask/dataframe/io/tests/test_csv.py: 52 warnings
dask/dataframe/io/tests/test_sql.py: 32 warnings
dask/dataframe/tests/test_categorical.py: 36 warnings
dask/dataframe/tests/test_dataframe.py: 10 warnings
dask/dataframe/tests/test_groupby.py: 862 warnings
dask/dataframe/tests/test_merge_column_and_index.py: 8028 warnings
dask/dataframe/tests/test_multi.py: 3514 warnings
dask/dataframe/tests/test_shuffle.py: 8874 warnings
dask/dataframe/tseries/tests/test_resample.py: 8 warnings
  /usr/lib/python3.8/site-packages/partd/pandas.py:113: DeprecationWarning: The Index._get_attributes_dict method is deprecated, and will be removed in a future version
    header = (type(ind), ind._get_attributes_dict(), values.dtype, cat)

dask/dataframe/tests/test_multi.py: 8 warnings
dask/dataframe/tests/test_ufunc.py: 974 warnings
  /usr/lib/python3.8/site-packages/_pytest/python.py:198: PytestRemovedIn8Warning: Passing None has been deprecated.
  See https://docs.pytest.org/en/latest/how-to/capture-warnings.html#additional-use-cases-of-warnings-in-tests for alternatives in common use cases.
    result = testfunction(**testargs)

dask/tests/test_base.py::test_tokenize_dense_sparse_array[dia]
  /usr/lib64/python3.8/site-packages/scipy/sparse/_coo.py:427: SparseEfficiencyWarning: Constructing a DIA matrix with 960 diagonals is inefficient
    warn("Constructing a DIA matrix with %d diagonals "

dask/tests/test_base.py::test_tokenize_dense_sparse_array[dia]
  /usr/lib64/python3.8/site-packages/scipy/sparse/_coo.py:427: SparseEfficiencyWarning: Constructing a DIA matrix with 959 diagonals is inefficient
    warn("Constructing a DIA matrix with %d diagonals "

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

@kloczek Thanks for reporting!

[x] PytestRemovedIn8Warning has been fixed: #8673
[ ] SparseEfficiencyWarning needs to be handled (looks like we removed the code to silence this warning in #8718)
numpy's RuntimeWarning -- Not sure if we should silence this. It seems to be warning only on ubuntu builds. Note that it was updated in #5140, and we seem to be explicitly displaying the warning
partd's DeprecationWarning -- Need to look into it further, xref: https://github.com/dask/partd/issues/58

Thanks @kloczek. Would you mind opening a separate issue for this as it's separate from warnings being emitted? Also, how is you environment set up? We're not seeing consistent failures on main

Done https://github.com/dask/dask/issues/9690

Loks like thi sticket can be closed.
Closing.
Thank you 👍


Test against multiple OTel version - Issue #1963

Signed-off-by: Krishna Kondaka<EMAIL_ADDRESS>Description
Added e2e test workflows with different otel client library versions for testing with older opentelemetry client version and newer version.
Issues Resolved
Resolves #1963
Check List

[ X] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2154 (7c4f84b) into main (9009741) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #2154      +/-   ##
============================================
+ Coverage     93.99%   94.01%   +0.02%
  Complexity     1633     1633
============================================
  Files           204      204
  Lines          4729     4729
  Branches        378      378
============================================
+ Hits           4445     4446       +1
  Misses          194      194
+ Partials         90       89       -1

Impacted Files
Coverage Δ

...opensearch/dataprepper/pipeline/ProcessWorker.java
90.38% <0.00%> (+1.92%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add transient include directories to library

This assigns the transient include directories and link libraries to namespaced targets for down stream use.  The desired down stream use is to do something like
add_executable(myapp ...)
target_link_libraries(myapp FFTW::Double)

and let CMake deal with setting the appropriate linker flags and include directories.  The double colon is the namespacing mechanism commonly employed by newer CMake projects.
This creates the following aliases:
FLOAT_LIB               ->  FFTW::Float
DOUBLE_LIB              ->  FFTW::Double
LONGDOUBLE_LIB          ->  FFTW::LongDouble
FLOAT_THREADS_LIB       ->  FFTW::FloatThreads
DOUBLE_THREADS_LIB      ->  FFTW::DoubleThreads
LONGDOUBLE_THREADS_LIB  ->  FFTW::LongDoubleThreads
FLOAT_OPENMP_LIB        ->  FFTW::FloatOpenMP
DOUBLE_OPENMP_LIB       ->  FFTW::DoubleOpenMP
LONGDOUBLE_OPENMP_LIB   ->  FFTW::LongDoubleOpenMP

This is great, thanks! I guess it would be nice to change the many similar lines of definitions to a macro by now, but I'll leave that for some other time.


Add exception handling while downloading stuff

If a download fails in youtube-dl due to some error like
youtube_dl.utils.DownloadError: ERROR: XFfXixHrjcY: YouTube said: Unable to extract video data
then the downloads should continue from the next one,

resolved with the latest release


Login without oidc.web3-login.net domain

thanks for your project, pretty cool... what if in the future you will not renew the domain, or something happens with your hosting, and all our logins will break. is there a way to host oidc.web3-login.net stuff on our end?

Thank you for your question. It is a good question and one that definitely warrants further documentation.
The web3-login is an OpenID Connect (OIDC) server, which means that anyone can host it on their own servers. This means that if the domain for the current server were to expire, the OIDC server could be hosted on a different domain and configured to work with the same client.
In order to do this, the new domain would need to be configured in the OpenID Connect client. This would typically involve updating the client's configuration to point to the new server's domain.
Overall, the ability to host the OIDC server on your own servers gives you more control over the authentication process and can help ensure that your login process remains stable and reliable.
The Authorize URI on this example config has to be replaced by the servers domain. https://web3-login.net/#/config

@ddon added your question to the faqs https://github.com/web3-login/web3-login#frequently-asked-questions-faqs


[Tidy] Remove automatic label provision

Description
Went through the repository, and it seems that this was the only place where a label was automatically added. Removed that logic to be consistent with out current label system.
Screenshot
Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
I have not referenced individuals, products or companies in any commits, directly or indirectly.
I have not added data or restricted code in any commits, directly or indirectly.

Other labels are automatically added in these templates, no? https://github.com/mckinsey/vizro/tree/main/.github/ISSUE_TEMPLATE

Other labels are automatically added in these templates, no? https://github.com/mckinsey/vizro/tree/main/.github/ISSUE_TEMPLATE

But these are the ones we would like to keep! 😄 It's when someone raises a bug report, feature request or general question


Failing "Update kotlin" builds/actions for kotlin 2.0.0

These actions failed after updating kotlin to 2.0.0:
https://github.com/android/architecture-templates/actions/runs/9899323193
https://github.com/android/architecture-templates/actions/runs/9899323188
https://github.com/android/architecture-templates/actions/runs/9899311922
https://github.com/android/architecture-templates/actions/runs/9899311918
relevant logs:
https://github.com/android/architecture-templates/actions/runs/9899323193/job/27347996856#step:5:185
e: This version (1.5.14) of the Compose Compiler requires Kotlin version 1.9.24 but you appear to be using Kotlin version 2.0.0 which is not known to be compatible.  Please consult the Compose-Kotlin compatibility map located at https://developer.android.com/jetpack/androidx/releases/compose-kotlin to choose a compatible version pair (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).
https://github.com/android/architecture-templates/actions/runs/9899323193/job/27347996856#step:5:211
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':core-ui:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> 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./

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':core-ui:compileDebugKotlin'.

From: https://developer.android.com/jetpack/androidx/releases/compose-kotlin

Compose Compiler Version
Compatible Kotlin Version

Use the Compose Compiler Gradle plugin to enable Compose.
2.0.0+

So the Compose Compiler should be replaced with the Compose Compiler Gradle plugin

Thanks @jsytal1!


Recaptcha V3?

Does this plugin support recaptcha v3?

Hey @gofish543, thanks for opening up this issue — someone else asked this earlier in the previous version of this addon for Statamic 2: https://github.com/aryehraber/statamic-recaptcha/issues/5
I am honestly not sure/convinced that Recaptcha V3 is useful, or even possible, as an easy-to-use captcha system for Statamic, but am curious to hear about other people's use cases/ideas... I asked a series of Qs in the earlier GH issue, but will copy those here and hope you (and others) can chime on the issue. Thanks!

Basically, what is it about Recaptcha V3 that you are waiting for that V2 can't already do?
In my research so far it seems like it's a worse experience on both sides (users and admins) for regular websites, depending on implementation:

The user's submission is blocked because they were marked "risky" by Google and their score is below the allowed threshold. This would mean they literally can't submit the form, or it silently fails and submissions never arrive in an admin's inbox.

We store all "risky" submissions in a spam folder and stop auto-emails from being triggered, but now the burden is put on the admin to go and check spam everyday and mark Google's incorrect "risky" submissions as not spam (triggering auto-emails, etc). Also worth noting that Statamic doesn't natively support a spam folder so this solution would be a much larger undertaking since that needs to be built and integrated, instead of the current solution which simply makes use of existing core features.

I can see V3's usefulness in larger applications where the score can lead users to an additional security flow before being allowed to take a certain action, but I just don't see that being a good solution for normal forms on a regular website.
To reiterate, I'm completely open to the idea but am currently not convinced about it in a Statamic context. For more complex Statamic projects it could be useful, but at that stage you probably want to control the actions that are taken for low/high scores meaning a generic solution like this addon wouldn't really be possible/useful.
Please share your ideas and vision for use cases, I'll happily change my mind!

I'm not convinced Recaptcha V3 is useful either. However, I was asked by my manager to add recaptcha to some Statamic forms; upon showing them the results they were disappointed to see that it wasn't Recaptcha V3.
Why? Because the captcha wasn't "invisible". I personally am against the invisible recaptcha for the same reasons you are.

Right ok, fair enough, thanks for sharing!
For now, I do not have plans (or time) to add support for Recaptcha V3 but am open to further discussion from others who are able to answer some of the key questions in my above comment — will leave this issue open for the time being.


Documentation of modular multiplication

This relates to #150 and #283.
In the discussion of #150 it is mentioned that modular multiplication is possible via Residue.
However, I did not find an example that shows how Residue is used correctly and it also wasn't immediately apparent to me.
After a bit of searching, I found the macro const_residue, which seems to allow the creation of a Residue object.
https://github.com/RustCrypto/crypto-bigint/blob/ef32e28146dc904fc33e7b773402aa129310df49/src/uint/modular/constant_mod/macros.rs#L50-L53
However, there are several issues with the example residue!(U256::from(105u64), MyModulus);:

The macro is called const_residue (and not residue).
Usage of U256::from(105u64) is not a valid argument to the macro. (no rules expected the token `::`)
MyModulus needs to be defined before, which is not evident by the example itself.

Because of these things, it cost me a bit of time to get modular multiplication working. For reference, this is a minimal working example:
use crypto_bigint::{const_residue, impl_modulus, modular::constant_mod::ResidueParams, U256};

impl_modulus!(
    F11,
    U256,
    "000000000000000000000000000000000000000000000000000000000000000B"
);

fn mul_mod(a: U256, b: U256) -> U256 {
    let a = const_residue!(a, F11);
    let b = const_residue!(b, F11);
    a.mul(&b).retrieve()
}

fn main() {
    let a = U256::from(3u8);
    let b = U256::from(4u8);
    let c = mul_mod(a, b);
    println!("{a} * {b} % {} = {c}", F11::MODULUS);
}

I think it would be nice if a more explicit (and correct) example would be included in the documentation.

#313 provides a simpler API for dynamic moduli (via the MulMod trait)

Where does this currently stand? If we were to produce docs on this, where should they live? Modular powers is another area that might need attention as well.

We could use some more examples in the toplevel documentation of the modular module: https://docs.rs/crypto-bigint/0.6.0-pre.10/crypto_bigint/modular/index.html

is the approach taken above by @matthiasgeihs sufficient in this case for mul mod or is there something more optimal

That sort of example seems fine if you'd like to add it to the rustdoc, although the macro names will need to be updated, e.g. to const_monty_form!

See #562. Realizing that in ~v0.6, mul_mod is quite easily and naturally accessed. Accessing mod_pow-like functionality was observed to be somewhat elusive, so 562 attempts to highlight the modular module to a degree

Accessing mod_pow-like functionality was observed to be somewhat elusive

How so?

Accessing mod_pow-like functionality was observed to be somewhat elusive

How so?

Had to dig around through the unit tests to see how it was being used. In the most recent version though it was really nice and seamless, very easy to use

Feel free to close this issue if you think it is solved. Haven’t had time to look into this recently.


PHP 5.3 compatibility

Hi,
Before doing any test, I need to use this SDK for one of my client who is using an old PHP version (5.3)
Apparently PHP 5.4 is required but does anybody managed to make this SDK work with PHP 5.3 ?
Rgds

Hi @GillesChila,
5.4 PHP version is the oldest one we decided to support now (hard choice to defined an older version ;) )
If somebody there could give you some information and propose some PR with quickfixes needed to support 5.3 PHP version, she/he will be very welcome !
Mickaël

If somebody there could give you some information and propose some PR with quickfixes needed to support 5.3 PHP version, she/he will be very welcome

Oh god please no. PHP 5.3 has been dead for years now, it's time to move on. Please don't encourage people to submit pull requests to keep the thing alive. Just put it out of its misery. Thanks.


[ACR] Add configuration for dataplane python sdk

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

I should have placed a do not merge here, but I guess this is okay?
cc: @yugangw-msft


Feedback from Russell

Hi @yufeimichelle ,
I've updated all of my feedback.
The topic of monetary policy and exchange rates is continually brought up. The choice of the SVAR model is the strongest point in macroeconomic analysis because the SVAR model, by incorporating economic theory to identify the structural relationships between variables, enables researchers to understand deeper about the causal relationships among economic variables.
I think you could include more explanatory text in the report. For instance, in the Preliminary Results section, after completing the ACF test, you could add some interpretation: "GDP and CPI have non-zero autocorrelations for at least 10 lags," and what does this indicate?
Additionally, I have some suggestions the following adjustments:

Capitalization Updated: The initial letters of the words in the article's title and headings should be capitalized, except for prepositions. Therefore, I've updated your title from “Effects of monetary policy shocks on exchange rate: Evidence from Australia” to “Effects of Monetary Policy Shocks on Exchange Rate: Evidence from Australia.” 287cdf823c81d2cf98d73adbeffd022938a2fbfc
Quantitative Error: In the Data section, "The first variable is the key variable in the analysis of the research, and the other 5 variables are the key monetary variables to identify the monetary shocks in Australia." As you introduced a total of five variables, after the first, the latter part should use "the other 4 variables."
4fb3eb05ef4a6eb43f555207188e93890a30085d
Simplify ADF Test: As shown in "Part 6: Submitting a Pull Request", there could be a way to simplify the loop of the ADF test.

Hope these are useful!
Best,
Russell

Hi @russellyang728
Thank you for your feedback on the report and your comments is very useful.
Following your feedback on 'more explanatory text in the report', I commit changes and add more explanations in the Preliminary Results section, as in commit 8cc4cefdd23fda217bd09a85ba0811d74dd4f472 and 6ba00fa2a0b50673e640f04f484fa4702846b164
For the changes your made, I merged the adjustments commits into pmd file and update my website.  As in commit 6ac05807bcdc73027285737453b200f60ca3bb3e
Good luck!
Yufei


chore: update to subject listing mv 2

Description

Connects mv subject listing 2
fixes missing unit variant programme factors on subject listing page

Issue(s)
Fixes #LESQ-88
How to test

Go to subject listing (2023) click on history - should take you to programme listing page not unit listing

:tada: This PR is included in version 1.203.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Need some free space

The amount of free space in the standard image is very small. Look into expanding the filesystem to fill the remaining space on the SD card.

Working on a script that will run on first boot that will expand the file system to fill the SD card. For SD cards 16GB or larger, will also create a 1GB swap partition.


Optional literal eval on native environments

I would like jinja2's NativeEnvironment to support rendering without passing string results through ast.literal_eval.
I ran into the unexpected behavior described in https://github.com/pallets/jinja/issues/1403, which was explained away as:

Note that the nativetypes functionality is effectively just literal_eval (docs).

Native types' functionality is much more different than just literal eval:
import pydantic
from jinja2 import Environment
from jinja2.nativetypes import NativeEnvironment

normal_env = Environment()
native_env = NativeEnvironment()

class MyModel(pydantic.BaseModel):
    foo: str

context = {
    "model": MyModel(foo="bar"),
    "num": 2,
    "string_num": "2",
}

# native returns non-stringified values
model = "{{ model }}"
print(type(normal_env.from_string(model).render(context)))  # <class 'str'>
print(type(native_env.from_string(model).render(context)))  # <class '__main__.MyModel'>

# native returns Undefined for missing keys
missing = "{{ nope }}"
print(type(normal_env.from_string(missing).render(context)))  # <class 'str'>
print(type(native_env.from_string(missing).render(context)))  # <class 'jinja2.runtime.Undefined'>

# native returns None for lone failed if block
empty = "{% if nope %}{{ nope }}{% endif %}"
print(type(normal_env.from_string(empty).render(context)))  # <class 'str'>
print(type(native_env.from_string(empty).render(context)))  # <class 'NoneType'>

# native returns int for the `num`
num = "{{ num }}"
print(type(normal_env.from_string(num).render(context)))  # <class 'str'>
print(type(native_env.from_string(num).render(context)))  # <class 'int'>

# native CASTS `string_num` to an int
string_num = "{{ string_num }}"
print(type(normal_env.from_string(string_num).render(context)))  # <class 'str'>
print(type(native_env.from_string(string_num).render(context)))  # <class 'int'>

Coming from ordinary jinja environments, it feels like NativeEnvironment respects the types of the objects in the context. Except for the literal_eval call at the end.
It would be great if this was somehow optional, e.g., toggleable via a kwarg.

For completeness, here's the workaround I'm relying on in place of this

from itertools import islice, chain
from types import GeneratorType

import jinja2.nativetypes
import typing as t

def custom_native_concat(values: t.Iterable[t.Any]) -> t.Optional[t.Any]:
    """
    An amended jinja2.nativetypes.native_concat that doesn't try to parse the output as a Python literal.
    """
    head = list(islice(values, 2))

    if not head:
        return None

    if len(head) == 1:
        raw = head[0]
        if not isinstance(raw, str):
            return raw
    else:
        if isinstance(values, GeneratorType):
            values = chain(head, values)
        raw = "".join([str(v) for v in values])

    # try:
    #     return literal_eval(
    #         # In Python 3.10+ ast.literal_eval removes leading spaces/tabs
    #         # from the given string. For backwards compatibility we need to
    #         # parse the string ourselves without removing leading spaces/tabs.
    #         parse(raw, mode="eval")
    #     )
    # except (ValueError, SyntaxError, MemoryError):
    #     return raw
    return raw

class NativeEnvironment(jinja2.nativetypes.NativeEnvironment):
    concat = staticmethod(custom_native_concat)

class NativeTemplate(jinja2.nativetypes.NativeTemplate):
    environment_class = NativeEnvironment

NativeEnvironment.template_class = NativeTemplate

here's the workaround I'm relying on

Using subclassing to achieve the behavior you want isn't a "workaround", it's a standard way to extend the behavior. I don't plan to change native environment at this time, and you can already accomplish what you need with the API available to you.


Sync Labels

Please sync all labels from
https://github.com/orgs/octoposprime/discussions/14
Names and Colors

You have to sync all names, colors, and descriptions.
https://github.com/orgs/octoposprime/discussions/14#discussioncomment-9026048

all labels are synced


Option to limit max NACKs per lost packet

Currently the NACK generator interceptor has no limit on the number of NACKs produced for the same lost packet. If the remote takes a while to resend the packet (e.g. if the RTT is larger than the NACK generator interval), this can result in the remote resending a NACKed packet an unlimited number of times (or at least until sufficient later packets are received that the NACK receive log wraps around). If there's congestion on the link, this will make the congestion even worse. Also, after a certain amount of time, receiving a lost packet is no longer useful (e.g. beyond the length of the jitter buffer on the receive side).
This PR adds a new generator option to limit the maximum number of times a given lost packet is NACKed. So for example, if this option is set to 4, a lost packet is NACKed at most 4 times (so e.g. if the generator interval is 100ms, packets will not be NACKed more than 400ms after first presumed missing). Option default is 0, which is the current behaviour (no NACK limit).

@boks1971 - here is one scenario we have seen happen. For 'internet' reasons, for several seconds we get significant congestion/loss/delay on the downlink (i.e. from remote sender to us), but everything was OK on the uplink (i.e. from us to the remote). The packet sequence we get is something like 100, 101, 102, 204 then nothing for a couple of seconds. So the NACK interceptor starts sending NACKs for packets 103 to 203 over and over and over. A couple of seconds later we receive dozens of repeated retransmissions of these hundreds of packets. This then causes additional congestion/loss and so we NACK even more packets. Everything settles down eventually (10+s later) but the whole situation can be avoided with a sensible NACK resend limit.
(NB, we actually originally patched the NACK generator to immediately mark missing packets as received, so that at most one NACK is sent per missing packet - this 'solved' the problem but we really wanted to implement this properly and 1 is probably not the right limit for most use cases)

Got it Adrian. Yeah, multi second brown out can happen and cause that flooding. Thank you for explaining. I think this looks good. Will bonk it. But, might be good to get another pair of 👀 . I will tag @davidzhao also to check if he is available to review.

OK, absent any further comments I will merge this in a couple of days' time.


Add window name to on_window_change event

Include window name in the metadata that can be used to differentiate windows (i.e. in addition to window class).
The per-app config looks the same as before if the window name is not needed:
[gnome-terminal]

meta_mac.c = C-S-c

However, a pipe (|) can be appended, with window name after that to further differentiate windows within an app:
[gnome-terminal|find]

meta_mac.a = C-a

Note: I have not tested the Gnome or Sway versions of this code (although I did my best to modify it as needed).
In particular, it would be helpful if someone on Gnome 41 could test that this does what is expected:
global.display.focus_window.get_wm_name()

Thanks, I will need some time to test this. I considered doing something similar but couldn't think of a case in which matching by title would be useful given that windows either tend to have very distinct names (e.g article names in a browser) or are else sufficiently generic that they correspond to their class names. Do you have a real use case?

Do you have a real use case?

Yes, the example I gave is real: the gnome-terminal "Find" pop-up window is part of gnome-terminal wm_class (and so it inherits the "change M-c to C-S-c" expression for copy) but when you want to "copy" from the find window, C-S-c is incorrect and won't work (it needs to be C-c again).

I've merged this and made some changes so it works properly across the different platforms. I've also added support for wildcards.


Incorrect module url?

It's not possible to install rsyslog_exporter since the go.mod are referring to "github.com/aleroyer/rsyslog_exporter"
go install<EMAIL_ADDRESS>go: downloading github.com/prometheus-community/rsyslog_exporter v1.1.0
go<EMAIL_ADDRESS>version constraints conflict:
<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/aleroyer/rsyslog_exporter
	        but was required as: github.com/prometheus-community/rsyslog_exporter

Maybe the path needs to be updated in go.mod to "github.com/prometheus-community/rsyslog_exporter"?

Good catch. It was not change after moving the project under prometheus-community!


Feature request: when searching consumables with firearms bring up ammunition.

i would like to see it that when you search for consumables and you select the firearm search terms for the ammunition to be easy to find. as this is what happens when you do so.

Those do exactly what they say they do: filter for weapons


Format colors

Example:
docker ps --format '{{ .Blue (.Underline .ID) }}'

Any idea what this means?
17:20:48 ---> Making bundle: validate-vendor (in bundles/1.12.0-dev/validate-vendor)
19:05:26 Username for 'https://github.com': Build timed out (after 120 minutes). Marking the build as failed.
19:05:26 Build timed out (after 120 minutes). Marking the build as aborted.

(in https://jenkins.dockerproject.org/job/Docker-PRs-vendor/683/console)

I'll restart the vendor CI, it happens sometimes, although it looks a bit like a configuration issue in Jenkins.
This may be a flaky test, noting here, I may make a separate issue for tracking;
https://jenkins.dockerproject.org/job/Docker-PRs/26588/console
17:35:40 ----------------------------------------------------------------------
17:35:40 FAIL: docker_cli_run_unix_test.go:783: DockerSuite.TestRunSeccompProfileDenyUnshare
17:35:40
17:35:40 docker_cli_run_unix_test.go:806:
17:35:40     c.Fatalf("expected unshare with seccomp profile denied to fail, got %s", out)
17:35:40 ... Error: expected unshare with seccomp profile denied to fail, got /go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/../binary/docker: Error response from daemon: Untar re-exec error: exit status 1: output: no such file or directory.
17:35:40 See '/go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/../binary/docker run --help'.
17:35:40

I've fixed the validate-vendor error.

Works for me, moving to code review!

Ping @calavera @jfrazelle: thoughts?

SGTM:)
On Wed, May 11, 2016 at 3:30 PM -0700, "Arnaud Porterie"<EMAIL_ADDRESS>wrote:
Ping @calavera @jfrazelle: thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Nice. I see a _test.go in the colors library, I'm almost sure the vendoring should have removed it, can you double check?
vendor/src/github.com/fatih/color/color_test.go
Otherwise code LGTM

Hum indeed seems weird that vendor did not remove a _test.go...
Otherwise code LGTM too, just wonder if we can/could add some tests ? :angel:

I'm a bit "-1" on this feature; it feels a bit "because we can" without a clear use case, but perhaps it's just me (sorry!)
This PR will need changes to the documentation though, so if you can update https://github.com/docker/docker/blob/master/docs/admin/formatting.md to include the new coloring options (and some examples).

Ok I'm glad you said it because I was trying to point out its a lot more to maintain for what? Colors? Sure it's pretty and I'm a huge TUI fan but is it worth it. Just didn't want to be Debbie downer.

Let's move this back to design review for now

Sorry @samoht, we discussed this, and we don't think we really need this, so closing, thanks!!

No pb, thanks for having looked at it!


[FEATURE] Allow to disable worker_threads usage in worker section.

Duplicate issue

[X] I've searched for any related issues and avoided creating a duplicate issue.

Description
The simulator is designed as a multithreaded application so evaluate the feasibility of using worker_threads on configuration demand first:

Replace worker_threads IPC?
Stateless worker usage in the charging station code?

Attachments
No response

The work needed to make the simulator run mono and multi threaded does not worth the gain.


Unable to access LLaMA weights to build Vicuna-7B

Dear Team,
Thank you for sharing your work for the community.
I am trying to setup the inference model for videochat but I am having difficulties in downloading the official LLaMA 7b weights as they are not officially available from meta.
The provided links in below instruction do not provide for LLaMA 1 models. We can only download llama 2 models from below links.
LLAMA: Download it from the original repo or hugging face.
Could you upload the llama 7b and llama 13b weights so we can directly utilize it?
Thank you in advance!
Kind regards,
Muhammad Uzair

Bittorrent (magnet:?xt=urn:btih:b8287ebfa04f879b048d4d4404108cf3e8014352&dn=LLaMA).

Thank you !

Bittorrent (magnet:?xt=urn:btih:b8287ebfa04f879b048d4d4404108cf3e8014352&dn=LLaMA

what is this?

@kuaileqipaoshui you can download the weights directly using the above magnet link via a torrent downloader software.
Alternatively, you can use this repository to download LLaMA model weights.

@kuaileqipaoshui you can download the weights directly using the above magnet link via a torrent downloader software.
Alternatively, you can use this repository to download LLaMA model weights.

thank you!


Have problems with Navigator.popUntil() function

Steps to Reproduce
code example
https://gist.github.com/AndreiNikitin/f496bc3fecf1c97f347d7259e1a3106e

I have several routes. The initial one is Routes.HOME
From initial route I navigate to Routes.ADD_DEVICE_STEP_ONE => Routes.ADD_DEVICE_STEP_TWO => Routes.ADD_DEVICE_STEP_THREE
On step three I show a dialog to user (cancel confirmation) when he presses cancel button
If user pressed "OK" button in dialog I execute funtion

Navigator.of(context).popUntil(ModalRoute.withName(Routes.HOME))

And every time I get an exception "Bad state: Future already completed" and "Failed assertion: line 2106 pos 12: '!_debugLocked': is not true."

What is the problem with this function. Is it a bug or does this error happens because of inappropriate use of function?
P.S. This only happened if "onGenerateRoute" table used. If "routes" is used - everything works fine
Logs
I/flutter (16589): ══╡ EXCEPTION CAUGHT BY GESTURE ╞═══════════════════════════════════════════════════════════════════
I/flutter (16589): The following StateError was thrown while handling a gesture:
I/flutter (16589): Bad state: Future already completed
I/flutter (16589):
I/flutter (16589): When the exception was thrown, this was the stack:
I/flutter (16589): #1      Route.didComplete (package:flutter/src/widgets/navigator.dart:187:19)
I/flutter (16589): #2      Route.didPop (package:flutter/src/widgets/navigator.dart:175:5)
I/flutter (16589): #3      OverlayRoute.didPop (package:flutter/src/widgets/routes.dart:61:36)
I/flutter (16589): #4      TransitionRoute.didPop (package:flutter/src/widgets/routes.dart:211:18)
I/flutter (16589): #5      _ModalRoute&TransitionRoute&LocalHistoryRoute.didPop (package:flutter/src/widgets/routes.dart:527:18)
I/flutter (16589): #6      NavigatorState.pop (package:flutter/src/widgets/navigator.dart:1935:15)
I/flutter (16589): #7      NavigatorState.popUntil (package:flutter/src/widgets/navigator.dart:1975:7)
I/flutter (16589): #8      BodyWidgetState._showCancelDialog.<anonymous closure>.<anonymous closure> (package:SmartLED/src/presentation/main/device_add/step_3/body_widget.dart:188:37)
I/flutter (16589): #9      AppDialog.build.<anonymous closure> (package:SmartLED/src/presentation/common/dialogs.dart:44:34)
I/flutter (16589): #10     _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:513:14)
I/flutter (16589): #11     _InkResponseState.build.<anonymous closure> (package:flutter/src/material/ink_well.dart:568:30)
I/flutter (16589): #12     GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:120:24)
I/flutter (16589): #13     TapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:242:9)
I/flutter (16589): #14     TapGestureRecognizer.handlePrimaryPointer (package:flutter/src/gestures/tap.dart:175:7)
I/flutter (16589): #15     PrimaryPointerGestureRecognizer.handleEvent (package:flutter/src/gestures/recognizer.dart:369:9)
I/flutter (16589): #16     PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:73:12)
I/flutter (16589): #17     PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:101:11)
I/flutter (16589): #18     _WidgetsFlutterBinding&BindingBase&GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:214:19)
I/flutter (16589): #19     _WidgetsFlutterBinding&BindingBase&GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:192:22)
I/flutter (16589): #20     _WidgetsFlutterBinding&BindingBase&GestureBinding._handlePointerEvent (package:flutter/src/gestures/binding.dart:149:7)
I/flutter (16589): #21     _WidgetsFlutterBinding&BindingBase&GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:101:7)
I/flutter (16589): #22     _WidgetsFlutterBinding&BindingBase&GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:85:7)
I/flutter (16589): #26     _invoke1 (dart:ui/hooks.dart:223:10)
I/flutter (16589): #27     _dispatchPointerDataPacket (dart:ui/hooks.dart:144:5)
I/flutter (16589): (elided 4 frames from package dart:async)
I/flutter (16589):
I/flutter (16589): Handler: onTap
I/flutter (16589): Recognizer:
I/flutter (16589):   TapGestureRecognizer#e61f2(debugOwner: GestureDetector, state: accepted, won arena, finalPosition:
I/flutter (16589):   Offset(277.1, 399.1), sent tap down)
I/flutter (16589): ════════════════════════════════════════════════════════════════════════════════════════════════════
I/flutter (16589): Another exception was thrown: 'package:flutter/src/widgets/navigator.dart': Failed assertion: line 2106 pos 12: '!_debugLocked': is not true.

flutter analyze

   info - The class 'Future' was not exported from 'dart:core' until version 2.1, but this code is required to be able
          to run on earlier versions - lib\src\data\database\database.dart:16:3 - sdk_version_async_exported_from_core
   info - The class 'Future' was not exported from 'dart:core' until version 2.1, but this code is required to be able
          to run on earlier versions - lib\src\data\database\migration.dart:3:1 - sdk_version_async_exported_from_core

2 issues found. (ran in 10.9s)

flutter doctor
[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [Version 10.0.17134.648], locale ru-RU)
    • Flutter version 1.2.1 at E:\flutter
    • Framework revision 8661d8aecd (4 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at E:\AndroidSDK
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = E:\AndroidSDK
    • Java binary at: E:\AndroidStudio_3_3_canary_10\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.3)
    • Android Studio at E:\AndroidStudio_3_3_canary_10\android-studio
    • Flutter plugin version 31.1.3
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[!] VS Code (version 1.27.1)
    • VS Code at C:\Users\ANDRE\AppData\Local\Programs\Microsoft VS Code
    X Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (1 available)
    • Redmi Note 4 • 4937c6e19904 • android-arm64 • Android 7.0 (API 24)

! Doctor found issues in 1 category.

Just figured it out. If you use custom PageRouteBuilder and named routes you have to pass RouteSettings to constructor. And it works!


[Bug] [ xAxis.axisLine. onZero],This configuration does not work

Version
5.4.0
Link to Minimal Reproduction
https://codesandbox.io/s/wandering-monad-dtlyws
Steps to Reproduce
add the config，xAxis.axisLine. onZero，series.data include negative number
Current Behavior
I have negative data to display, but I want to pan down the x-axis and start displaying from the negative numbers up.

As in the picture, I want the effect of the picture below, but in reality it is like the picture above.
Expected Behavior
The same 3D bar chart has this problem, I need the z-axis to start with a negative number.

Like in the picture, the Z-axis is displayed from negative numbers upwards
Environment
- OS:windows10
- Browser:Chrome108
- Framework:js

Any additional comments?
No response

Would this solve the problem ? Demo Code 2D  Demo Code 3D  ... following "fake it till you make it" strategy 🛠

Great!!! This method solved my problem. Thank you very much for your method!


[BUG]: toggling muted prop causes full rerender on RN 0.76.0

Version
6.7.0
What platforms are you having the problem on?
Android TV
System Version
12
On what device are you experiencing the issue?
Simulator
Architecture
New architecture with interop layer
What happened?
Toggling the muted prop causes the whole component to rerender and start the video again.
Downgrading RN back to 0.75.2 resolves the issue.
Reproduction Link
No response
Reproduction
Toggle the muted prop

Thanks for report, it's probably Interop Layer stuff - I am little busy right now but will you know once I check it

+1, subscribing

I just noticed a certain pattern regarding component rendering. It happens when any property coming from a state is modified (e.g.: paused, rate, selectedTextTrack, muted...)

@evoactivity any solution?

@felipegmg I've just downgraded back to 0.75. If I get some time before @KrzysztofMoch has a chance, I'll dig into the problem more indepth but I feel like it might need proper support for the new architecture.

@evoactivity, for me it is impossible to downgrade. As I use the paused, muted, rate properties, I will use the ref object and other third-party libraries to manipulate these values. Anyway, thanks for the answer. Good job!

@felipegmg I don't understand why using those properties would stop you downgrading react native? Or trying without new architecture?

@evoactivity @felipegmg can you confirm that you use bufferConfig prop ? Just to confirm something on my side

YEEES! And when I remove those props, the refresh not happen! Any solution/workaround to use bufferConfig and avoid this refresh? Thanks!

This patch shall be OK for a quick workaround if you don't use cache on android.
In fact I already identify these lines as problematic and tracked the change to do here: https://github.com/TheWidlarzGroup/react-native-video/issues/2693
BufferConfig is the last remaining one...
diff --git a/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java b/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
index 1246d9fd..7d4c55b8 100644
--- a/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
+++ b/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
@@ -2373,8 +2373,6 @@ public class ReactExoplayerView extends FrameLayout implements
         } else {
             useCache = false;
         }
-        releasePlayer();
-        initializePlayer();
     }

     @Override

I finally provide the good patch ...