[firebase_crashlytics] Android dependency 'com.crashlytics.sdk.android:crashlytics' has different version for the compile (2.9.3) and runtime (2.9.9) classpath. You should manually set the same version via DependencyResolution

Describe the bug
Changed package from flutter_crashlytics to firebase_crashlytics, tried to debug and it threw out an error
Launching lib/main.dart on ONEPLUS A6003 in debug mode...
Running Gradle task 'assembleDebug'...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:preDebugBuild'.
> Android dependency 'com.crashlytics.sdk.android:crashlytics' has different version for the compile (2.9.3) and runtime (2.9.9) classpath. You should manually set the same version via DependencyResolution

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

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

BUILD FAILED in 9s
Finished with error: Gradle task assembleDebug failed with exit code 1

To Reproduce
Steps to reproduce the behavior:

Add firebase_crashlytics: ^0.1.2+4 to dependencies
run flutter clean then debug in VSCode or Android Studio
See error or incorrect behavior

Expected behavior
To debug and run in the device successfully
Additional context
Tried this solution, adding the subprojects entry in buildscript
   buildscript {
    repositories {
        google()
        maven { url 'https://maven.fabric.io/public' }
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'
        classpath 'com.google.gms:google-services:4.3.0'
        // Add fabric classpath
        classpath 'io.fabric.tools:gradle:1.+'
    }
    subprojects {
        project.configurations.all {
            resolutionStrategy.eachDependency { details ->
                if (details.requested.group == 'com.crashlytics.sdk.android') {
                    details.useVersion "2.9.9"
                }
            }
        }
    }
}

But that also throws the following error
Launching lib/main.dart on ONEPLUS A6003 in debug mode...
Running Gradle task 'assembleDebug'...

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:preDebugBuild'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
     Required by:
         project :app > com.crashlytics.sdk.android:crashlytics:2.9.9
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com: Name or service not known
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com: Name or service not known
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > download.flutter.io: Name or service not known
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://maven.fabric.io/public/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://maven.fabric.io/public/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > maven.fabric.io: Name or service not known
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:beta:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/beta/2.9.9/beta-2.9.9.pom'.
               > jcenter.bintray.com
   > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
     Required by:
         project :app > com.crashlytics.sdk.android:crashlytics:2.9.9
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://maven.fabric.io/public/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://maven.fabric.io/public/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > maven.fabric.io
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:crashlytics-core:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/crashlytics-core/2.9.9/crashlytics-core-2.9.9.pom'.
               > jcenter.bintray.com
   > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
     Required by:
         project :app > com.crashlytics.sdk.android:crashlytics:2.9.9
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'http://download.flutter.io/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > download.flutter.io
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://maven.fabric.io/public/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://maven.fabric.io/public/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > maven.fabric.io
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > dl.google.com
      > Could not resolve com.crashlytics.sdk.android:answers:2.9.9.
         > Could not get resource 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/crashlytics/sdk/android/answers/2.9.9/answers-2.9.9.pom'.
               > jcenter.bintray.com

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

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

BUILD FAILED in 0s
Finished with error: Gradle task assembleDebug failed with exit code 1

Here is the flutter doctor output
➜ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.14.1, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.41.1)
[✓] Connected device (1 available)

• No issues found!

A new Crashlytics plugin has now landed on master which should solve this issue.
Checkout the migration guide to get started on upgrading to the new Crashlytics plugin: https://firebase.flutter.dev/docs/migration/


Question: How to do floor, plane, surface detection and tracking?

Is there any guidance as to how to do world tracking with this library? I see that in the Readme.md there is a reference to "World Tracking", but I don't see any examples that use it.
If this is a new feature that needs to be added, I would gladly look into it. I imagine we could use Tensorflow.js to try and accomplish this task.
Any guidance or input is much appreciated.
~ Cheers

This library doesn't provide any world tracking, but it's definitely something very interesting and useful to add.
Welcome any ideas/advices/contributions in this area.

Thanks for the quick response @hiukim. I'm looking to add something like this room / floor tracker that you see in the WayFair App. Are there any Tensorflow.js resources that someone in this community can point me to so I can build it out and try to add it to this library?
https://user-images.githubusercontent.com/14102289/151337911-8fefafd3-2bbf-40c5-bbbe-d6df2986f0c4.mp4

@S-Cardenas you can add it via webxr API for android only but it should be support in the futur by safari/ios as well.

I mean, once webxr is enabled by default on all browsers, mindarjs, arjs, etc will all become quickly obsolete. The edge that these libraries will hold for a while is being able to run on older devices, but as time goes on this will become less and less of a problem.

For me personally I'm looking at mind-ar-js as a way to match an iOS quicklook experience on Android. I'd like to have a way to have the (stationary) marker report its position while using webxr for the main tracking, so I update the 'anchor' of the scene sporadically with smoothed marker data.
On the broader questions, I think there will be a few years (at a minimum!) before there isn't a need for shim-like libraries to bridge these kinds of functionality. Chrome moves fast in WebXR, but some Chinese android browsers and webview configurations lag that progress.
Safari devs have shown interest, but only in HMD-related areas from what it seems (the original WebVR use-case). They've had half a decade to implement handheld WebXR but didn't, so it wouldn't be out of character to continue to ignore the use-case in favor of pushing a singular OS-spanning UX based around USDZs and their RealityOS.
All this is a long-winded way of asking if anyone has tried using this library in combination with WebXR, and adding a +1 to the idea of an android-only world-tracking feature that integrates with marker positions!

@hiukim Closed as completed? So mindar js supports surface detection and tracking?

@marcusx2 sorry, nope. I was just trying to clean up some old issues. It's been stale for a while and there is no plan for that at the moment.


Fix derivatives in CALPHADConcSolverBinary3Ph2Sl

Does not matter for AlCu since q=1, but incorrect/inconsistent in my opinion

I could have made an error, but I think that q should be there.
From here the ideal mixing term is defined as:

The q there becomes the q that goes as part of the RT coefficient:
https://github.com/ORNL/Thermo4PFM/blob/dc8be8caf06d670004b79a2b68904247f59fe28f/src/CALPHADFreeEnergyFunctionsBinary3Ph2Sl.cc#L155
Then that q makes it to the RHS.
Am I missing something? There are enough variable transforms, etc. that I wouldn't be surprised if I was.

Oh, I see. I had missed that q. I would actually put it in front of the function to make it more clear, although it is equivalent. We may need some comments so that we don't question these expressions every time we look at them ;-)

Agreed on the comments :)


StackOverflowException when initializing serializer

When creating a new instance of Serializer, CollectionSerializer, EnumerableSerializer, or DictionarySerializer, a StackOverflowException will inevitably be thrown.
This is due to the fact that the Specialized property in the Serializer class (which the other three inherit from) is an instance property, and also creates new instances of the other three upon initializing - leading to new instances being recursively created with no end.
This property originally used to be static, and was later changed to be an instance property.
Changing it back to a static property will fix the problem.

Closed with https://github.com/Carnagion/GDSerializer/commit/bb75ca6931b7c9ae8916d647b8e7701c4d3175e1.


Bump the properties timeout

Summary
We started seeing too many requests to upstream. Increasing the timeout
might alleviate that as long as we're requesting the same properties.
Change Type

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
N/A
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.287%. remained the same
when pulling db5be63dcee3bdeb1668057b54777027c403b31f on jhrozek:bump_timeout
into f6bff2f9df7e7dbcdb3755dafaf0e3c5fa1bcb1c on stacklok:main.


Plonk implementation with updates to Algebra

This commits the Plonk implementation for review.
This PR is for the review of Plonk implementation that has the following:

Plonk with pairing-based commitment schema supporting polynomial splitting.
Plonk with dlog-based commitment schema supporting polynomial splitting. This implementation, in order to use polysplitting together with the linearization optimization, adds additional polyevaluation (for the quotient polynomial) to the proof. Alternative implementation, not using the linearization optimization, has been committed (with commit b51ffa113234db7324c6576f46b645f2ed32d353) into "plonk" branch. The alternative implementation has proof size larger than the proof size of this implementation.
Unit tests for both Plonk implementations.

Hi, is this standard plonk or turboPlonk?
Implementing turboplonk in it's most general form requires ripping out the foundations of the circuit builder, I think.


Update the Zabbix local development environment tooling

This updates the local development scripts to use the current oc syntax
and secrets format. It also updates the lib_zabbix Ansible module and
the zbxapi Python module for Python 3.

prod still uses python 2 so


Syntra Digital Agency UI

Project title
Syntra Digital Agency UI
(Write project title over here)
Project Description
a fully responsive UI of the Syntra Digital Agency webpage
(Describe the project over here)
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] CSS
[x] ReactJS

/assign


changed personal name; hide former names

I my tree I have persons who changed their name (several reasons).
I want to set a restriction to the former names, but
1 NAME John /Doe/
1 NAME Peter /Doe/
2 RESN CONFIDENTIAL
2 TYPE BIRTH
is not valid in Gedcom 7.0.14
Best regards,
Marianne van Harten

This was proposed in issue #245.
The proposal was accepted for the next minor release - i.e. 7.1

Discussed in GEDCOM Steering Committee 3 SEP 2024:
Agreed this is a duplicate of issue #245, so closing this issue.
Please continue any discussion in that issue.
Thanks!


Why resize to (256, 256) ?

In deploy.prototxt, the input_param is { shape: { dim: 1 dim: 3 dim: 224 dim: 224 } } but in classify_nsfw.py, images are resized to (256, 256).

@Mohanson  check the closed issue, i already asked the exactly same question.
In training phase, the image size is 256256, then random crop size 224224 to do data augmentation
While in test size, center cropping is uesd to test the image
In this situation, image are resized to 256256, but caffe only process the center part 224224

Very thanks and sorry for I didn't take a look in closed issues.


⚠ Bofrost.de has degraded performance

In 03e01af, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1783 ms

Resolved: Bofrost.de performance has improved in f7c71e2 after 9 minutes.


heap-buffer-overflow when sse enabled

Steps to reproduce:

Build with Address Sanitizer enabled (add -fsanitize=address -fno-omit-frame-pointer flags to compiler and linker):
https://gist.github.com/supercoolgreatcoder/11b5deccd1f500bd19c84cdf11f2c2a9
run sift1B test:
https://gist.github.com/supercoolgreatcoder/764ca0f196bee8a28b629e9e3c56f945
Culprit line: https://github.com/nmslib/hnswlib/blob/d0716d9962ec4ba100a5de551f07c2067e835785/hnswlib/hnswalg.h#L199
Disabling SSE does not trigger heap buffer overflow.

Hi @supercoolgreatcoder,
Thank you! What sort of problems it might create?
Actually, I thought _mm_prefetch is immune to wrong addresses.

@yurymalkov, __mm_prefetch is trying to read chunk of memory in heap that might not have been allocated, e.g. int* a = new int[100]; std::cout << a[100]. In the worst case it might end up with a segfault. I believe, it should be fixed relatively easy by fixing number of bytes that has to be prefetched.

This issue is still persisting and the root cause is the following expression: *(datal + j + 1)
The issue is that for datal we already account for the size at the beginning of the buffer here:
                size_t size = getListCount((linklistsizeint*)data);
                tableint *datal = (tableint *) (data + 1);

So adding the extra 1 in the loop is incorrect and on the last iteration we are de-referencing a out of bounds value.
The following fixes the issue and does not cause any heap buffer overflow
                    _mm_prefetch((char *) (visited_array + *(datal + j)), _MM_HINT_T0);
                    _mm_prefetch(getDataByInternalId(*(datal + j)), _MM_HINT_T0);


Combining FCS_TLSS_EXT.3.1 and FCS_TLSS_EXT.3.2 into one SFR (3.1)

Combining FCS_TLSS_EXT.3.1 and FCS_TLSS_EXT.3.2 into one SFR (3.1) and updating FCS_TLSS_EXT.3 to say "secure renegotiation".  Updated text to explain why.

@mclearn Do these changes resolve your comments on FCS_TLSS_EXT.3.1 and FCS_TLSS_EXT.3.2? Comments are in issues https://github.com/ND-iTC/Documents/issues/16 and https://github.com/ND-iTC/Documents/issues/17?


License

Please add license to enable documentation:
https://pkg.go.dev/github.com/timoknapp/soundcloud-cli/pkg/soundcloud

workaround:
https://godocs.io/github.com/timoknapp/soundcloud-cli

@timoknapp can you please reply?

Hi @89z ,
What do you exactly mean by "adding license"? Is it sufficient for you to add the "LICENSE.md" file to the repo?
Regards Timo

yes, something like this:
https://github.com/golang/go/blob/master/LICENSE

Okay but whats the reason behind this? So whats the benefit of having it for you?

@89z : I finally managed to add the license. Hope this helps you

thank you sir


Unhandled exception when processing invalid uri

Describe the bug
An unhandled exception occurs when processing an invalid URI in DownloadProgress.cs line 87.
Steps to reproduce

Enter any invalid web address into the download box on the main form
Click download
See unhandled exception

Expected behaviour
Exception is caught and handled.
Download Manager Version
<IP_ADDRESS>
Windows Version
Windows 11 Pro Insider Preview 22H2 25267.1000
Comments
No response

Fixed in bd32244


adds support for pod id lookup for filter

Resolves issue: #1546
After pull request output:
mike@mike-VirtualBox:~/go/src/crictl-test$ sudo crictl ps -all -p a3
CONTAINER           IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
8b74f21338a65       busybox             10 days ago         Running             busybox             0                   a3c9b2d234556
mike@mike-VirtualBox:~/go/src/crictl-test$ sudo crictl ps -all -p a4
CONTAINER           IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
mike@mike-VirtualBox:~/go/src/crictl-test$ sudo crictl ps -all -p a3c9b2d234556
CONTAINER           IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
8b74f21338a65       busybox             10 days ago         Running             busybox             0                   a3c9b2d234556

Signed-off-by: Mike Brown<EMAIL_ADDRESS>

/test pull-cri-containerd-node-e2e


Cargo login issues

When trying to use cargo login in preparation of publishing to crates.io the token is not passed a cargo login argument and then the command hangs indefinitely waiting for input.
Example task:
- name: Login to crates.io
  uses: actions-rs/cargo@v1
  with:
    toolchain: nightly
    command: login
    arguments: ${{ secrets.CRATES_TOKEN }}

I'm new to GitHub actions so I'm not sure if maybe I'm misusing this and I need to pass the argument in another way.

Oh, I'm sorry, there is a typo in the README example, could you replace arguments input with the args and try again?
- name: Login to crates.io
  uses: actions-rs/cargo@v1
  with:
    toolchain: nightly
    command: login
    args: ${{ secrets.CRATES_TOKEN }}

Fixed typo in the 2c42f22fe4080ef98db93b9cbec4f18c722e0890

Also, I tested a login command with the following workflow, works great:
on: [push]

name: Test login

jobs:
  login:
    runs-on: ubuntu-latest
    steps:
      - uses: actions-rs/cargo@v1
        with:
          command: login
          args: ${{ secrets.CRATES_TOKEN }}

##[debug]Evaluating condition for step: 'Run actions-rs/cargo@v1'
##[debug]Parsing expression: <success()>
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Run actions-rs/cargo@v1
##[debug]Loading inputs
##[debug]Evaluating: secrets.CRATES_TOKEN
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'CRATES_TOKEN'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Loading env
Run actions-rs/cargo@v1
/usr/share/rust/.cargo/bin/cargo login ***
       Login token for `crates.io` saved
##[debug]Finishing: Run actions-rs/cargo@v1

Thanks! Will replace it in my workflows now.

Thanks again for the quick help!  The login action already passed successfully. This would also explain why I had problems packaging the product of cargo build --release because the --release flag was probably not being passed and I was looking in the wrong folder :)

@zbrox great! You can also join the gitter chat if you have any questions left or need a help

mine get stuck, without any github actions


2.0.0-beta infer lib

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.cryoco seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix(web-components): open ic-dialog during initialisation using the open prop

Summary of the changes
A new open prop has recently been added to the IcDialog component, which replaces the deprecated showDialog and hideDialog methods.
The trouble is, when an instance of an IcDialog component is initialised using the new open prop, with open="true", the dialog remains hidden. This is because the dialog is only made visible when the value of the open prop changes, i.e. when it is assigned a different value after the component has been initialised (which happens in the watchOpenHandler method).
In particular, this causes a problem for testing IcDialog based components using Cypress component tests, as it is currently not possible to instantiate a component using a prop of open="true" and then to just go ahead and running assertions in Cypress, as a change of state is needed for the open prop to make the dialog visible in the tests, which involves some hacky and unreliable workarounds to get it working.
The small change in this PR fixes the issue. Now, if users of the IcDialog component pass in open="true", then the dialog is made visible during initialisation within the componentDidLoad function, reusing the existing code that executes whenever the watchOpenHandler is executed.
Related issue
N/A
Checklist

[x] Relevant unit tests and visual regression tests added.
[x] Visual testing against Figma component specification completed.
[x] All acceptance criteria reviewed and met.
[x] Accessibility Insights FastPass performed.
[x] A11y unit test added and yields no issues.
[x] A11y plug-in on Storybook yields no issues.
[x] Manual screen reader testing performed using NVDA and VoiceOver.
[x] Page can be zoomed to 400% with no loss of content.
[x] Screen magnifier used with no issues.
[x] Text resized to 200% with no loss of content.
[x] Text spacing increased as per the WCAG 1.4.12 success criterion with no loss of content.
[x] Browser setting 'prefers reduced motion' tested. No animations or motion visible whilst this setting is on.
[x] Windows High Contrast mode tested with no loss of content.
[x] System light and dark mode tested with no loss of content.
[x] Manual keyboard testing for keyboard controls and logical focus order.
[x] Min/max content examples tested with no loss of content or overflow.
[x] Browser support tested (Chrome, Safari, Firefox and Edge).
[x] Correct roles used and ARIA attributes used correctly where required.
[x] Logical heading structure is maintained, and the HTML elements used for headings can be changed to fit within the wider page structure.
[x] All prop combinations work without issue.
[x] Changes to docs package checked and committed.

Nice addition to the dialog component. Thanks for the contribution. 🚀 A few things:

Could you please create the 'Auto Open' story for the Web Components storybook

The commits need to be separated based on the update to the package so for example:

The web component commit scope should only contain the update to dialog.tsx and the new web component story
Docs commit for the update to docs.json
React commit for React storybook

Hopefully this helps: https://github.com/mi6/ic-ui-kit/blob/main/CONTRIBUTING.md#git-commit
Thanks.

Apologies, I missed the fact that there are 2 different storybooks to update! I will make sure that the "Auto opening" (as well as the "Hidden close button" story that I recently added) appears in both storybooks.
I will also look into making the changes in separate commits, as suggested.

All comments addressed - ready for re-review.


Hash for Native _DRAW_3D_BOX missing. [Update NativeHashes.hpp]

No hash for GRAPHICS::_DRAW_3D_BOX
_START_SCREEN_EFFECT & _STOP_SCREEN_EFFECT are missing too.
Maybe add a way to call functions without the Hash enum?

Since NativeDB is updated continuously, we can't ensure our file is always up-to-date.
In your case, the functions are not named in the file, you need use their hash:

@JohnnyCrazy true!

Have you got an automated script to convert them to an enum?

Would be cool if we have one in the repo, will see what I can do

Did it with a simple regex, so yeah, shouldn't be much of an issue to make a quick script out of it.

When you add new hashes to the enum, will you remove the raw hashes for them?
Because this will break any compiled DLL's that use the raw hashes, won't it?

No, because functions can be called using the raw hash.

@Nacorpio I think he means functions, which are named now. Since they have names now, you can't use their old direct hash anymore

For example, in 0.9 the build, Hash._SET_BLACKOUT doesn't exist, so you have to call Hash._0x1268615ACE24D504 instead.
But if you add _SET_BLACKOUT to the hashes enum, and remove _0x1268615ACE24D504 then my compiled dll will break.
I only ask because no named hashes have their raw hashes in the enum as well.

... You can use 'Function.Call((Hash)0x1268615ACE24D504)' to call the raw hash.

Ohh, that's cool, I didn't know that :D
But it would still break my compiled DLL if you removed the raw hash for _SET_BLACKOUT

Yeah it would, so best idea is that in your code you only use the enum for functions that have their original function name, and use Raw for any user named or unknown ones. It's tedious, but if you just want it to work with most future versions, thats the way to go.

That makes sense.
It would be stupid to have both the raw and named hashes in the enum, considering none of the existing named ones have their raw ones.

Can someone have a look at helper/NativeGenerator?
It's downloading the natives.json, parsing the JSON into the object NativeFile. Then it will just go through all namespaces and write their functions into NativeHashes.hpp
Pro:

We could add the function's params/result to the inline docs
nativeTemplate.txt can be updated if there is any new license
Totally dynamic, no need to change anything for a while (forever? :D )

Con:

JSON .NET Nuget package dependency

@JohnnyCrazy But i guess it means someone has to run it manually sometimes and commit?

@JohnnyCrazy ,
if (File.Exists("NativeHashes.hpp"))
	File.Delete("NativeHashes.hpp");
File.AppendAllText("NativeHashes.hpp", string.Format(nativeTemplate, resultBuilder));

it can be done using one method: File.WriteAllText

@Frede1012 , app veyor can do this, before build.

@IncoCode Oh, cool!

But do we really want this? This means we could have different hashes on every build. This would maybe also break a lot of builts, since the file gets updated AFTER you submit it

Thats true, that might be problematic.

@JohnnyCrazy , nobody says that this file must be updated on every build. This tool could be useful for periodic hashes updates.

I agree the tool is useful, however are we going to just have someone update the hashes manually sometimes?

I don't know the exact plans and what @crosire has in mind. Let's just wait what he's suggesting

I think once in a while manually is probably a good idea.

While I like the idea to update it automatically each build (The NativeHashes.hpp would be removed from Git tracking and recreated during the build process), I understand it could be a problem. So periodic updates are probably the easiest solution.

Yea, but then every realease, in which NativeHashes are updated, is considered as a major release. (We implement new stuff which is not backwards compatible and breaks compiled scripts). So we should consider updating it not that often.

Updated to latest version in 5bdb1349e701d3a88cbe47443571a5b8252b88cf using the generator by @JohnnyCrazy.


.profile

Quite simply, a profile
(not so simple to code)
┆Issue is synchronized with this Trello card

➤ Nik Bran commented:
https://www.npmjs.com/package/canvas


Does not work on servers

I know right, It only works with single player or LAN hosted servers, it can't be fixed. Although i didn't test it on servers vanilla core, if you tested it and it kicks you, then let me know.


I'm unable to grab the item upon click...

Here's the full question.
https://stackoverflow.com/q/45993677/2403823

Is this a bug report?
(write your answer here)

Have you read the Contributing Guidelines?
(Write your answer here.)
Environment

react-native -v:
node -v:
npm -v:
yarn --version:

Then, specify:

Target Platform:

Development Operating System:

Build tools:

Steps to Reproduce

(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@facebook-github-bot no-template

@jpca999 i would suggest continuing to use stack-overflow for questions like these.


Updating link to new Azure-Samples path

Repo has been moved to Azure-Samples

#Sign-Off

@EdPrice-MSFT: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


undefined is not an object

Could you please help me
issue message:
undefined is not an object (evaluating '_react2.proptypes.func')

There is an issue with this library. In all the js files of this library you need to import prop types form the dedicated bundle instead of React. Like following:
import PropTypes from 'prop-types';
This will resolve the issue. Hope author fixes this. Also, Once this is fixed I don't see the animation though :/

Hello,
This is an old library, this was done before facebook thought to split proptype in an other library.
I don't really have time to update this, now.
I'm ok if someone can send a PR.
Btw I will use this animation for a side project, so I planned to update it for the next month I guess.

PropTypes updated.
@nitinsh99
For android bug, open another issue.


Disable New Relic when Swap

Figure out a way to disable New Relic when Swap blue-green containers.

you can set an environment variable and use it to enable/disable new relic

@andrewsmedina it will restart the application twice, witch is not desired.

One possible solution could be:
swap_newrelic=true
At tsuru-bluegreen.ini

#15 solves this.

Closed by https://github.com/emerleite/tsuru-bluegreen/commit/91dbbe2857cb3307837ff552b0bb348ace3cc5f8


Handling foreign structure pointers returned from a function call

First of all, thank you for starting this awesome project!
I'm currently working on a service using WebKitGTK+ (It's WebKit1 interface) and I faced with the problem of JavaScriptCore GTK bindings which simply do not exist. As there is gir file describing two foreign structures - JavaScriptCore.GlobalContext and JavaScriptCore.Value - I decided to try to use LuaJIT's FFI to operate with this structures directly.
So, I'm calling web_view:get_main_frame():get_global_context() to get JSGlobalContextRef but the returning pointer value is slightly different from the value returned by direct FFI call ffi.C.webkit_web_frame_get_global_context(web_view:get_main_frame()._native). It looks like JavaScriptCore.GlobalContext is boxed but I'm unable to find a proper way to unbox it. I've already tried some GValue magic but it seems I'm doing it wrong. Here is what I always get:
cdata<struct OpaqueJSContext *>: 0x7fb0dc1df9b0
lgi.rec 0x7ffc9c0d1bf0:JavaScriptCore.GlobalContext

What is the recommended way to handle foreign pointers in this case?

lgi normally uses _native to unbox both objects and records. Does web_view:get_main_frame():get_global_context()._native work?

Yes, it does. But if then I pass this pointer to JSEvaluateScript, I get a segfault. I'm currently using ffi.C.webkit_web_frame_get_global_context(web_view:get_main_frame()._native) for workaround.

https://gist.github.com/dannote/ec83a263188e04f84a9b


Show quick outline in vue component file

In larger files it would be nice to use "Show the quick outline (CTRL-SHIFT-O, ⌘-SHIFT-O)". especially to navigate between event handlers.
Currently quick outline only show html tags

I would love to see behavior like in js file

We can do that by implementing a js/ts symbolProvider.

I think this issue has already been implemented.

Now vetur includes all symbols from template, script and styles.


herbstluftwm: fix unable to be started in 23.11 release

Description of changes
After updating I could not start herbstluftwm since the X session would exit immediately. After a lot of trouble shooting I found that this commit caused the issue for me: https://github.com/NixOS/nixpkgs/commit/7cfeb768e5f2a160075d8736101444c10f1c5ea6
I am not sure why this change was introduced so I kept the changes and looked to how the implementation of other window manager modules, namely i3 handle this: https://github.com/NixOS/nixpkgs/blob/50aa30a13c4ab5e7ba282da460a3e3d44e9d0eb3/nixos/modules/services/x11/window-managers/i3.nix#L58-L65
So i did the same for herbstluftwm and now it works for me :)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Thanks.
Please run the tests, though.

I can confirm that this change fixes the issue and allows the test to pass.

I can confirm that this PR fixes both use-cases. Thank you!
desktopManager.xfce.enable = true;
windowManager.herbstluftwm.enable = true;

And then try to login with those sessions:

none+herbstluftwm
xfce+herbstluftwm

both work as expected.
It fixes the bug introduced in: https://github.com/NixOS/nixpkgs/pull/237364

@SuperSandro2000 you merged my previous PR (https://github.com/NixOS/nixpkgs/pull/237364), which introduced a bug. Could you please also merge this PR which fixes the bug?

I've tested this change locally, it fixes herbstluftwm for me


Bug when creating transformer pipeline in sample-apps/transformers

Describe the bug
Not a vespa related bug, however, the transformer pipeline cannot be created in sample-apps/transformers.
To Reproduce
Issue is here: https://github.com/vespa-engine/sample-apps/blob/master/transformers/src/python/setup-model.py#L16
Fix
pipeline = transformers.pipeline("text-classification", model=model_name)

Environment

OS: macOS 10.15.7
Python: 3.9.7

PyTorch: 1.10.1
Transformers: 4.15.0

CC @jobergum

Thanks, fixed by https://github.com/vespa-engine/sample-apps/pull/817

Yes, also saw some other tutorials following the same style of pipeline declaration that would also encounter the same error https://github.com/vespa-engine/sample-apps/search?q=transformers.Pipeline

The DPR model is pinned to a given transformer version, as it does not work with recent updates to the transformer library.

Thanks for reporting this @Brandhsu !

Yes @jobergum, also there is a similar issue with the pyvespa package, I encountered it when doing the stateless model serving.

@thigm85 please take a look at the pyvespa problem


HDR?

Help request
Your Environment

Netflix add-on version: Latest
Device model:  ShieldTV Pro
Used Operating system: Android TV 9
Kodi Version: 18

Describe your help request
Kodi is the only AndroidTV player that changes device refreah rate to match content frame rate. Netflix doesn't, so your add on seems like an ideal solution. Unfortunately, the add on doesn't appear to load HDR enabled streams. I've tried manually changing the streams, but none of the available options triggers my TV to change modes to any HDR format. Kodi plays local files in HDR just fine. Not sure if this is a Netflix restriction, an add on limitation, or an incorrect setting on my part.

Figured it out! In the expert settings.


Regression in information_schema.key_column_usage?

CrateDB version
crate/crate:nightly (still works on 5.0.1)
CrateDB setup information
docker pull crate/crate:nightly
docker run --rm -it --publish=4200:4200 crate/crate:nightly -Cdiscovery.type=single-node -Ccluster.routing.allocation.disk.threshold_enabled=false

vs.
docker run --rm -it --publish=4200:4200 crate/crate:5.0.1 -Cdiscovery.type=single-node -Ccluster.routing.allocation.disk.threshold_enabled=false

Steps to Reproduce
crash <<SQL
  CREATE TABLE testdrive ("id" TEXT PRIMARY KEY);
  SELECT column_name FROM information_schema.key_column_usage WHERE table_name = 'testdrive' AND table_catalog = 'doc';
SQL

Expected Result
cr> CREATE TABLE testdrive ("id" TEXT PRIMARY KEY);
CREATE OK, 1 row affected  (0.217 sec)
cr> SELECT column_name FROM information_schema.key_column_usage WHERE table_name = 'testdrive' AND table_catalog = 'doc';
+-------------+
| column_name |
+-------------+
| id          |
+-------------+
SELECT 1 row in set (0.006 sec)

Actual Result
cr> CREATE TABLE testdrive ("id" TEXT PRIMARY KEY);
CREATE OK, 1 row affected  (0.235 sec)
cr> SELECT column_name FROM information_schema.key_column_usage WHERE table_name = 'testdrive' AND table_catalog = 'doc';
+-------------+
| column_name |
+-------------+
+-------------+
SELECT 0 rows in set (0.080 sec)

My fault, the table_catalog was using the table_schema value until now, which was wrong and we fixed it recently. See the related breaking changes entry https://crate.io/docs/crate/reference/en/master/appendices/release-notes/unreleased.html#breaking-changes.

All right. The query is coming from initial introspection queries run by the dataset package, see https://github.com/crate/crate-python/issues/456. Chances are that it may break integration with other tools as well, when they are running similar introspection queries?

Ah right, seems like the query at our SQLAlchemy dialect for resolving the primary key constraint is wrong as it uses the table_catalog column with the schema argument. We must fix this query to use the table_schema column instead.
https://github.com/crate/crate-python/blob/master/src/crate/client/sqlalchemy/dialect.py#L270

Hi again,
this issue has been converged into a patch to the Python driver, see https://github.com/crate/crate-python/pull/459. As far as I can see, no other relevant/popular driver for CrateDB needs to be updated.
With kind regards,
Andreas.


Some of the 3.6 & 3.7 gate changes are causing issues

Add 3.6 params to make deploy script
Remove 3.6 params for gate script and use make deploy defaults
Change DOCKERHUB_USERNAME to DOCKERHUB_USER
Change DOCKERHUB_PASSWORD to DOCKERHUB_PASS

ACK

ACK

Gate is back to green


feat(test): bump autorest.testserver to 3.3.48

bump autorest.testserver to 3.3.48 and remove overwrite of typescript
regen test/sample
fix test case errors:

fix optional constant parameters not appearing in method signature
fix incorrect reference to api_version query parameter

resolve #3679
Description
Add your description here!
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

preview pr: https://github.com/Azure/azure-sdk-for-net/pull/38298

@archerzz, seems there are public APIs impacted by this change, could you check whether this is expected?

@archerzz, seems there are public APIs impacted by this change, could you check whether this is expected?

@lirenhe There is no change in the public API interfaces, as the SDK compatibility check bot said here.:

API changes are not detected in this pull request.

That class is internal: https://github.com/Azure/azure-sdk-for-net/blob/858b7ba9da51891ccb77b7aa88d94a44b9bffeb2/sdk/storage/Azure.Storage.Files.DataLake/src/Generated/FileSystemRestClient.cs#L21
We just need to contact Storage team to confirm the expected behavior.

@archerzz, seems there are public APIs impacted by this change, could you check whether this is expected?

@lirenhe There is no change in the public API interfaces, as the SDK compatibility check bot said here.:

API changes are not detected in this pull request.

That class is internal<EMAIL_ADDRESS>We just need to contact Storage team to confirm the expected behavior.

Confirm with storage team. They want to keep the existing behavior, which is easy since the public API is manually written.


⚠ Thumbnails API Endpoint has degraded performance

In 56bf232, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 5568 ms

Resolved: Thumbnails API Endpoint performance has improved in 499eafc.


IML 5.1 Manual Testing

IML Upgrade testing from <IP_ADDRESS> managed ldiskfs to 5.1
Manager Installation
Using https://wiki.whamcloud.com/display/DOC/IML+Manual+Testing as a guide, setup<EMAIL_ADDRESS>add servers, setup power control, create a filesystem, connect a client and add some files to generate metrics on the dashboard.

Install IML 4.0.10.x from copr:

vagrant provision adm --provision-with install-iml-4.0.10

Follow the steps to create a managed ldiskfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).
Download the 5.1 release from https://github.com/whamcloud/integrated-manager-for-lustre/releases/tag/v5.1.0 and move it up to the adm node.
Follow the upgrade instructions at: https://whamcloud.github.io/Online-Help/docs/Upgrade_Guide/upgrade_iml-4.0-el7_to_iml-5.0-el7.html and install<EMAIL_ADDRESS>as described.

Manager Upgrade:
expected:
After setting up a filesystem in IML <IP_ADDRESS> and creating a filesystem, IML was updated to<EMAIL_ADDRESS>without any issues.
actual:
...
Server Upgrade
Using the same document as a guide (https://whamcloud.github.io/Online-Help/docs/Upgrade_Guide/upgrade_iml-4.0-el7_to_iml-5.0-el7.html), upgrade each of the server nodes.
expected:
Each of the servers upgraded without any issues.
actual:
Failover
expected:
After halting OSS1 each of the targets on oss1 should have failed over to oss2. When oss1 was brought back online, I was able to fail back each of the targets that failed over and all alerts were removed.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:

IML Upgrade testing from 5.0.x managed ldiskfs to 5.1
Manager Installation
Follow the steps under https://wiki.whamcloud.com/display/DOC/Managed+Mode+Upgrade+Testing for managed ldiskfs upgrade testing.

Install IML 5.0.x from copr:

vagrant provision adm --provision-with install-iml-5

Follow the steps to create a managed ldiskfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).
Download the 5.1 release from https://github.com/whamcloud/integrated-manager-for-lustre/releases/tag/v5.1.0 and move it up to the adm node.
Install the new 5.1 release

Manager Upgrade:
expected:
After setting up a filesystem in IML 5.0.x and creating a filesystem, IML was updated to<EMAIL_ADDRESS>without any issues.
actual:
...
Server Upgrade
expected:
Each of the servers upgraded without any issues.
actual:
Failover
expected:
After halting OSS1 each of the targets on oss1 should have failed over to oss2. When oss1 was brought back online, I was able to fail back each of the targets that failed over and all alerts were removed.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:

IML 5.1 managed ldiskfs
Manager Installation
Follow the steps under https://wiki.whamcloud.com/display/DOC/IML+Manual+Testing for managed ldiskfs testing.

Install IML 5.1 from copr:

vagrant provision adm --provision-with install-iml-5.1

Follow the steps to create a managed ldiskfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).

Creating the Filesystem:
expected:
I was able to create a filesystem in<EMAIL_ADDRESS>write data to the client and see the data in the charts on the dashboard.
actual:
...
Failover
expected:
After halting OSS1 each of the targets on oss1 should have failed over to oss2. When oss1 was brought back online, I was able to fail back each of the targets that failed over and all alerts were removed.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:
IML 5.1 managed zfs
Manager Installation
Follow the steps under https://wiki.whamcloud.com/display/DOC/IML+Manual+Testing for managed zfs testing.

Install IML 5.1 from copr:

vagrant provision adm --provision-with install-iml-5.1

Follow the steps to create a managed zfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).

Creating the Filesystem:
expected:
I was able to create a filesystem in<EMAIL_ADDRESS>write data to the client and see the data in the charts on the dashboard.
actual:
...
Failover
expected:
After halting OSS1 each of the targets on oss1 should have failed over to oss2. When oss1 was brought back online, I was able to fail back each of the targets that failed over and all alerts were removed.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:

IML 5.1 monitored ldiskfs
Manager Installation
Follow the steps under https://wiki.whamcloud.com/display/DOC/IML+Manual+Testing for monitored ldiskfs testing.

Install IML 5.1 from copr:

vagrant provision adm --provision-with install-iml-5.1

Follow the steps to create a monitored ldiskfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).

Creating the Filesystem:
expected:
I was able to create a filesystem in<EMAIL_ADDRESS>write data to the client and see the data in the charts on the dashboard.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:

IML 5.1 monitored zfs
Manager Installation
Follow the steps under https://wiki.whamcloud.com/display/DOC/IML+Manual+Testing for monitored ldiskfs testing.

Install IML 5.1 from copr:

vagrant provision adm --provision-with install-iml-5.1

Follow the steps to create a monitored zfs filesystem with power control setup (https://wiki.whamcloud.com/display/DOC/Managed+Ldiskfs).

Creating the Filesystem:
expected:
I was able to create a filesystem in<EMAIL_ADDRESS>write data to the client and see the data in the charts on the dashboard.
actual:
...
iml-diagnostics for:
adm:
mds1:
mds2:
oss1:
oss2:

i have issue with 4.0.10
web GUI not working for me - i have endless loop
iml-diagnostics
sosreport (version 3.7)

This command will collect diagnostic and configuration information from
this CentOS Linux system and installed applications.

An archive containing the collected information will be generated in
/var/tmp/sos.xT0nV5 and may be provided to a CentOS support
representative.

Any information provided to CentOS will be treated in accordance with
the published support policies at:

  https://wiki.centos.org/

The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.

No changes will be made to system configuration.

 Setting up archive ...
 Setting up plugins ...
 Running plugins. Please wait ...

  Starting 1/13  block           [Running: block]
  Starting 3/13  filesys         [Running: block filesys]
  Starting 2/13  corosync        [Running: block filesys corosync]
  Starting 4/13  iml             [Running: block filesys corosync iml]
  Starting 5/13  kernel          [Running: block filesys iml kernel]
  Starting 6/13  logs            [Running: filesys iml kernel logs]
  Starting 7/13  memory          [Running: iml kernel logs memory]
  Starting 8/13  multipath       [Running: iml kernel memory multipath]
  Starting 9/13  pacemaker       [Running: iml kernel pacemaker]
  Starting 10/13 pci             [Running: iml kernel pacemaker pci]
  Starting 11/13 processor       [Running: iml kernel pacemaker processor]
  Starting 12/13 system          [Running: iml kernel processor system]
  Finishing plugins              [Running: iml processor system]
  Starting 13/13 yum             [Running: iml processor system yum]
  Finishing plugins              [Running: iml processor yum]
  Finishing plugins              [Running: iml processor]
  Finishing plugins              [Running: iml]

  Finished running plugins

Creating compressed archive...

Your sosreport has been generated and saved in:
  /var/tmp/sosreport-adm-2019-09-25-wcseafe.tar.xz

The checksum is: f96c6f17a7980c579868c775b6d3d152

Please send this file to your support representative.

in 4010 in web console
warning Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.
and many errors Content Security Policy: The page’s settings blocked the loading of a resource at data:application/font-woff2;charset=utf-… (“font-src”).

add servers
mds[1,2], oss[1,2]

IML 5.1 managed ldiskfs - installation - check

IML 5.1 Managed ZFS testing completed without issues.

Closing in favor of #1316


Removal Reasons comes up when spamming a post

again?

IKR?

    <amici_ursi> agentlame: huh. i confirmed i on the front page of /r/underconstruction
    <agentlame> Oh.  I was in the mod queue.  That might be why we missed it.
    <creesch> can confirm, it only happens when on a subreddit frontpage or new
    <creesch> not when you are in the post or in the queue

Actually, it looks like the flat-list spam button is the cause.  It's just that no queues use that style.


[Extensibility Enhancements] Procedure CopyLineToDoc() in in page 5850 "Posted Sales Document Lines" should not be OnPrem

The procedure CopyLineToDoc() in page 5850 "Posted Sales Document Lines" is marked as OnPrem, but I cannot see a reason in the code as to why it should be.
Can the OnPrem tag be removed to make it available for cloud extensibility?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 51059.


Chapter 10 - AttributeError: module 'tensorflow' has no attribute 'keras'

Hello,
I am getting below error when I am running program in chapter 10.
AttributeError: module 'tensorflow' has no attribute 'keras'
~~ Getting error for this line ~~~
>>> (X_train, y_train), (X_test, y_test) = tf.keras.datasets.mnist.load_data()

Traceback (most recent call last):

  File "<ipython-input-9-ec8c1f97086d>", line 1, in <module>
    runfile('/root/Machine_Learning_Scikit_Tensorflow/Chapter10.py', wdir='/root/Machine_Learning_Scikit_Tensorflow')

  File "/root/anaconda3/lib/python3.6/site-packages/spyder_kernels/customize/spydercustomize.py", line 786, in runfile
    execfile(filename, namespace)

  File "/root/anaconda3/lib/python3.6/site-packages/spyder_kernels/customize/spydercustomize.py", line 110, in execfile
    exec(compile(f.read(), filename, 'exec'), namespace)

  File "/root/Machine_Learning_Scikit_Tensorflow/Chapter10.py", line 154, in <module>
    (X_train, y_train), (X_test, y_test) = tf.keras.datasets.mnist.load_data()

AttributeError: module 'tensorflow' has no attribute 'keras'

Python Version is 3.6
However, upon checking tensorflow version it shows error like below:
>>> tf.VERSION
Traceback (most recent call last):

  File "<ipython-input-10-2e1b684706ab>", line 1, in <module>
    tf.VERSION

AttributeError: module 'tensorflow' has no attribute 'VERSION'

>>> tf.__version__
Traceback (most recent call last):

  File "<ipython-input-11-65996cac02ec>", line 1, in <module>
    tf.__version__

AttributeError: module 'tensorflow' has no attribute '__version__'

I had installed Tensorflow 1.9 as below
conda install tensorflow=1.9
conda install tensorflow-gpu=1.9

I have also tried to install Keras
Regards,
Rahul Rathore

Closing it as with the same installation as yesterday it worked like a charm. The only thing I did today was to power on my laptop and run the program.

Hi @Rahul954 ,
Conda allows multiple virtual environments.  Perhaps you were using a different environment? After rebooting, Conda typically goes back to the base environment. This is the environment that conda itself is installed in, so usually you don't want to install anything else in this environment.
You can check which environments are available by running conda env list. There will be a * next to the active environment. To switch environment, you can try conda activate my_env (assuming you want to activate the environment named my_env). You can type conda activate base or simply conda activate to go back to the base environment.
Hope this helps.


Add ability to break file connection in objects

And use this option in __deepcopy__ and when handing objects to boost-histogram/hist. It should have the file_path and uuid, or at least for the latter set the object_path and cache_key in a permanent way.
@henryiii

Do they also have a __setstate__/__getstate__? I would expect to be able to pickle a Histogram from ROOT, too.

I'm planning on it, though that would definitely break the connection to the original file.

Fixed in scikit-hep/uproot4#58; with a short list of exceptions (things like TDirectory, TTree, TBranch...), objects from a ROOT file are now detached from the original file. Thus, it wouldn't be possible to use these objects to read more data (which is why TDirectory, TTree, etc. are exceptions). But this means that the detached objects can be pickled and don't contain any transients, like locks or threads.
You can even save an object from a ROOT file into a pickle file and read it back in a new Python process, even though that object's class was derived from data in the ROOT file. (We pickle enough derived quantities from the TStreamerInfo to reconstitute the class object.)

This is done; somehow forgot to close it.


Miniplayer buttons are active, but invisible.

OS:
Windows 10
Issue Descriptions:
The miniplayer button (play/pause, next track, etc.) are active, in that if I mouse over where they should be, they are functional. However, the actual buttons are invisible and don't pop up from autohide as intended.
Also, the miniplayer image will remain static and not progress to match the track until I hit the maximize button on the miniplayer. This causes the correct song to display.
Steps to Reproduce:
This issue happens probably 80% of the time when I just open GPMDP and enable the miniplayer. Occasionally it will work properly but not regularly.
I'm a user, no development experience, but attempting to use the preferred method of bug reporting.

Do you have system borders enabled or are you using the custom borders?

Confirmed. System border, win 10.

Yeah, for an unknown reason.  System borders breaks the mini player.
I think this comes back to the "let's redesign the mini player" thing I had going a while back

@notasmartman The current workaround is to enable the custom window borders in Desktop Settings.
This is an upstream issue being tracked here electron/electron/issues/6783

@MarshallOfSound @jostrander Yes, I was using system borders. Changing that has fixed my issue. Thanks!


Labminme/terraform random bucket 9

Accidently built the first part of this S3 bucket project in the wrong branch and synched it. Cloning to branch #11 to finish working there.

I will just copy the main.tf and README.md changes over and keep rolling.


Current Branch label at bottom left is showing old branch even if we created and switched to new branch

VS Code Version:
1.54.3

OS Version:
Version: 1.54.3 (system setup)
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T10:55:45.459Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

checkout a remote repo ( git checkout origin/main
create a new branch (git checkout -b feat-branch

Does this issue occur when all extensions are disabled?: Yes/No

@rvjalamy, are you able to reproduce this with the latest version of VS Code Insiders?
If you are, do not mind recording a gif using https://gifcap.dev to illustrate the issue? Thanks!


ActiveAdmin does not use limit in sql query

Strange ActiveAdmin behavior, it does not use pagination's limit and reads all records. Checked on DB with 20k+ records with blank model and very simple ActiveAdmin page.
Environment: Rails 3.2, ActiveAdmin 0.4.0

That's really weird. Active Admin does paginate the records it pulls from the database using the Kaminari gem. Are there other dependencies of your app that may be causing this issue? What SQL query is generated on the index page for you?

Tracking master.  Installed a base Rails 3.2.1 app with one model, task.name.  Here is the set of queries.
Started GET "/admin/tasks" for <IP_ADDRESS> at 2012-02-18 10:39:58 -0600
Processing by Admin::TasksController#index as HTML
AdminUser Load (0.2ms)  SELECT "admin_users".*  FROM "tasks" ORDER BY "tasks"."id" desc LIMIT 30 OFFSET 0
So, I backed down to 0.4.0 and got the same results as above.  Also tried changing @per_page and it worked appropriately. Is there somewhere else we are setting "paginations limit"?


Root Category issue while root setting from channel

Root Category issue while selecting the root category from the channel
Scenario 1:- select any new root except root(default) then subcategory is not displaying on the front end of the selected new root.

Scenario 2:- when we select the only Root(default) then It's subcategory is correct displaying on the front end

Test Environment:
Framework Version: 0.1.4
Fixed


Add getObject, writeObject to Block and BlockBuilder

Looks good, but make sure you address all the comments


Evaluation failed "Uncaught (in promise)" - Loading script failed (URL)

Description
We inject self hosted URL as script to the page and 99% it works but we have one case, which we don't know why it fails.
URL looks like this: http://localhost:5011/js/be/somenamehere/script.js and it is close to 7500 lines.
We see the following:

In here:

The URL we experience is 112 chars long (including http).
In general here is the exception
PuppeteerSharp.EvaluationFailedException: Evaluation failed: Event
at PuppeteerSharp.ExecutionContext.ExecuteEvaluationAsync(String method, Object args)
at PuppeteerSharp.ExecutionContext.EvaluateFunctionHandleAsync(String script, Object[] args)
at PuppeteerSharp.DOMWorld.g__AddScriptTagPrivate|29_0(String script, String urlOrContent, String type)
at PuppeteerSharp.DOMWorld.AddScriptTagAsync(AddTagOptions options)
Complete minimal example reproducing the issue
Here is how we run this:
        var chromiumLaunchOptions = new LaunchOptions
                                    {
                                        Headless       = false,
                                        Devtools       = TRUE,
                                        LogProcess     = true,
                                        Timeout        = 600000
                                    };

var browser = await Puppeteer.LaunchAsync(chromiumLaunchOptions);
var page    = await browser.NewPageAsync();
await  page.AddScriptTagAsync(new AddTagOptions {Url = scriptHostedLocalPath});
Expected behavior:
script to inject
Actual behavior:
exception
Versions
PuppeteerSharp 2.0.3
.NET Core 3.1
MacOs or Ubuntu

Corrected launch scenario
var chromiumLaunchOptions = new LaunchOptions
{
Headless       = false,
Devtools       = TRUE,
LogProcess     = true,
Timeout        = 600000
};
var browser = await Puppeteer.LaunchAsync(chromiumLaunchOptions);
var page = await browser.NewPageAsync();
await page.GoToAsync(url, new NavigationOptions {Timeout = 60000, WaitUntil = new[] {WaitUntilNavigation.DOMContentLoaded}});
await page.AddScriptTagAsync(new AddTagOptions {Url = scriptHostedLocalPath});

I found the issue leading to this.
Once I change the URL that starts the process in page.GoToAsync to shorter one "https://www.google.com/", injection worked.
So somehow we have an issue with long URL paths but I really need that long path, no other choice.

Correction here once again. It is not about the length of the URL but the page content.
Page content is making script injection fail. All other long URLs also work.
So far: The script itself is fine, long url is fine. But somethingin in the page fails this.

Here is the almost final verdict:
If page has appdynamics, then we have this issue.

Looking a way to block that content completely to bypass the issue.

Here is the final verdict:
While adding script to the page with the following content
   async function addScriptUrl(url, type) {
              const script = document.createElement('script');
              script.src = url;
              if(type)
                script.type = type;
              const promise = new Promise((res, rej) => {
                script.onload = res;
                script.onerror = rej;
              });
              document.head.appendChild(script);
              await promise;
              return script;
            }

We get the exception.
Adding the following piece of code, solved all my problems:
            await page.SetRequestInterceptionAsync(true);
            var blockDomains = new[] {"adobedtm.com", "ds-aksb-a.akamaihd.net", "ensighten.com", "go-mpulse.net", "appdynamics.com"};
            page.Request += async (sender, args) =>
                            {
                                if (blockDomains.Any(d => args.Request.Url.Contains(d)))
                                    await args.Request.AbortAsync();
                                else
                                    await args.Request.ContinueAsync();
                            };

@sseyalioglu what I think is that the script being injected is failing, and you are getting the javascript result of that. With that request filter, you might prevent the failing script from being loaded.

Closed due to inactivity. Feel free to reopen it if needed.


(format +onsave) and (go +lsp) conflicts with each other

What did you expect to happen?
I expected go buffers to be formatted and imports organized on save. Preferably by gopls. And expected there to be no errors.
What actually happened?
gofmt is run on save, which is fine. But then the .go file will have a persistent error that says expected declaration, found 'package'. After that it will start showing errors all around the files, that are not really errors. And sometimes the errors disappear. gopls logs are also filled with AST errors.
My guess is that gofmt and gopls sees different versions of the files as both are trying to touch it. As I also see errors from lsp-mode trying to apply edits and ending up in an error.
Sorry for the convoluted explanation, I haven't yet debugged this more.
Additional details:
I fixed the problem locally by disabling format-on-save for go-mode with:
(add-to-list '+format-on-save-enabled-modes 'go-mode t)

and using LSP formatters manually with:
(add-hook! 'go-mode-hook
  (add-hook 'before-save-hook #'lsp-format-buffer nil 'local)
  (add-hook 'before-save-hook #'lsp-organize-imports nil 'local))

If issue #1652 would be implemented then this would not be a problem.
Steps to reproduce:

Hard to come up with exact steps. As the problem is quite flaky.

System information:

emacs   version    27.0.60
        features   RSVG GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS JSON PDUMPER GMP
        build      Feb 10, 2020
        buildopts  (--prefix=/nix/store/jvd9gpf3r0lfpmd18aymx0ibcqrb08r4-emacs-27.0.50 --disable-build-details --with-modules --with-ns --disable-ns-self-contained 'CFLAGS=-O3 -DMAC_OS_X_VERSION_MAX_ALLOWED=101200')
        windowsys  ns
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop ae75326a4 2020-02-10 02:39:26 -0500
        dir        ~/.doom.d/
system  type       darwin
        config     x86_64-apple-darwin19.2.0
        shell      /run/current-system/sw/bin/bash
        uname      Darwin 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
        path       (~/.nix-profile/bin ~/.gimme/versions/go1.13.5.darwin.amd64/bin  /run/current-system/sw/bin /nix/var/nix/profiles/default/bin /usr/local/bin /usr/bin /usr/sbin /bin /sbin ~/go/bin /nix/store/jvd9gpf3r0lfpmd18aymx0ibcqrb08r4-emacs-27.0.50/libexec/emacs/27.0.60/x86_64-apple-darwin19.2.0/)
config  envfile    envvar-file
        elc-files  2
        modules    (:completion company ivy :ui doom doom-dashboard doom-quit hl-todo hydra indent-guides modeline nav-flash ophints (popup +all +defaults) treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors rotate-text snippets word-wrap :emacs dired electric ibuffer vc :term vterm :checkers syntax :tools direnv docker editorconfig (eval +overlay) (lookup +docsets) lsp macos magit make :lang data emacs-lisp (go +lsp) (javascript +lsp) markdown nix (org +dragndrop +present) (python +lsp) sh web :config (default +bindings +smartparens))
        packages   (n/a)
        elpa       (vterm)
        unpin      (n/a)

Sorry for the late response.

If issue #1652 would be implemented then this would not be a problem.

I'll consider this a duplicate of #1652 and move it (and my response) over there.


Update/remove all references to Diem in the Penumbra JMT implementation

So that we don't prepend hashes and so on with 'DIEM'.

Done as part ef #15


restclient-cpp can not resolve symbol

Describe the bug
1>main.obj : error LNK2019: 无法解析的外部符号 "struct RestClient::Response __cdecl RestClient::get(class std::basic_string<char,struct std::char_traits,class std::allocator > const &)" (?get@RestClient@@ya?AUResponse@1@AEBV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@z)，该符号在函数 main 中被引用
can not resolve symbol
Environment
OS: win10 x64
Compiler: msvc2017
To Reproduce
Steps to reproduce the behavior:
./vcpkg install restclient-cpp:x64
See error
Repro code when
Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
error LNK2019: 无法解析的外部符号 "struct RestClient::Response __cdecl RestClient::get(class std::basic_string<char,struct std::char_traits,class std::allocator > const &)" (?get@RestClient@@ya?AUResponse@1@AEBV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@z)，该符号在函数 main 中被引用
Additional context
Add any other context about the problem here.

Hi @how0723, thanks for reporting this issue.
I think this is a usage issue. Therefore, please provide a demo code.
Thanks.

my code :
#include "restclient-cpp/restclient.h"
int main()
{
RestClient::Response r = RestClient::get("http://url.com")
RestClient::Response r = RestClient::post("http://url.com/post", "application/json", "{"foo": "bla"}")
RestClient::Response r = RestClient::put("http://url.com/put", "application/json", "{"foo": "bla"}")
RestClient::Response r = RestClient::patch("http://url.com/patch", "application/json", "{"foo": "bla"}")
RestClient::Response r = RestClient::del("http://url.com/delete")
RestClient::Response r = RestClient::head("http://url.com")
RestClient::Response r = RestClient::options("http://url.com")
}

Confirmed, missing dlls and libs.

Hi @how0723, thanks for reporting this issue.
According to #110, restclient-cpp does not export any symbols, and I have not found any dllexports in its code.
If there is officially supported Windows in the future, we will upgrade this port.
Thanks.


User Switching and serving should use different ports

Today you can switch users with UI.   This means that each users data is stored on the same origin.
Instead serve each user on a specific port.  The user switching widget would then just open a new window when switching.
We can also do some really cool demos with multiple users running in iframes showing how the systems communicate.

we could do this if we map unique users to Cloud endpoints (user1.skarabrae.org vs user2.skarabrae.org) and serve the shell from each personal vm.

Un-assigning, but still a valid idea that would be nice to see, either using ports (for local development) or hostname prefixes with wildcard SSL (for cloud deployment)