Could not find com.facebook.react:react-native-gradle-plugin:.

New Version
0.71.11
Old Version
0.67.5
Build Target(s)
While building for Android
Output of react-native info
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
    Memory: 106.58 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v14.20.0/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.17 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: 0.71.11 => 0.71.11
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Issue and Reproduction Steps
While building the app for Android after upgrading React Native I'm getting this error
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'App'.
> Could not determine the dependencies of null.
   > Could not resolve all task dependencies for configuration ':classpath'.
      > Could not find com.facebook.react:react-native-gradle-plugin:.
        Required by:
            project :

Thing's I've tried

Clearing gradle cache
Clearing build cache for android
Reseting cache using --reset-cache
Tried other solution listed on similar issues from GitHub and StackOverflow

Files -
package.json
{
  "name": "App",
  "version": "1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint .",
    "clean": "cd android && ./gradlew clean && cd ..",
    "build": "cd android && ./gradlew clean && ./gradlew bundleRelease && cd .. && react-native run-android --variant=release",
    "build:prod": "cd android && ./gradlew clean && ./gradlew app:bundleRelease"
  },
  "dependencies": {
    "@datadog/mobile-react-native": "^1.0.0-rc5",
    "@datadog/mobile-react-navigation": "^1.0.0-rc5",
    "@invertase/react-native-apple-authentication": "^2.2.2",
    "@ptomasroos/react-native-multi-slider": "^2.2.0",
    "@react-native-clipboard/clipboard": "^1.8.5",
    "@react-native-community/art": "^1.2.0",
    "@react-native-community/async-storage": "^1.8.1",
    "@react-native-community/datetimepicker": "^6.1.3",
    "@react-native-community/masked-view": "^0.1.7",
    "@react-native-community/push-notification-ios": "^1.10.1",
    "@react-native-firebase/analytics": "^14.4.0",
    "@react-native-firebase/app": "^14.4.0",
    "@react-native-firebase/crashlytics": "^14.4.0",
    "@react-native-firebase/dynamic-links": "^14.4.0",
    "@react-native-firebase/messaging": "^14.4.0",
    "@react-navigation/native": "^5.0.9",
    "@react-navigation/stack": "^5.1.1",
    "@shopify/flash-list": "^1.4.0",
    "algoliasearch": "3.32.0",
    "axios": "^0.19.1",
    "babel-plugin-transform-remove-console": "^6.9.4",
    "color": "^3.1.2",
    "dayjs": "^1.8.25",
    "eventemitter3": "^4.0.0",
    "formik": "^2.1.4",
    "imagekit-javascript": "^1.4.0",
    "jwt-decode": "^3.1.2",
    "lodash.isequal": "^4.5.0",
    "prop-types": "^15.7.2",
    "react": "18.2.0",
    "react-native": "0.71.11",
    "react-native-animatable": "^1.3.3",
    "react-native-check-box": "^2.1.7",
    "react-native-code-push": "^6.3.0",
    "react-native-fast-image": "^8.6.3",
    "react-native-fbsdk": "^1.1.2",
    "react-native-gesture-handler": "^1.4.1",
    "react-native-google-signin": "^2.1.1",
    "react-native-image-crop-picker": "^0.36.0",
    "react-native-image-zoom-viewer": "^2.2.27",
    "react-native-inappbrowser-reborn": "^3.7.0",
    "react-native-keyboard-aware-scroll-view": "^0.9.1",
    "react-native-linear-gradient": "^2.5.6",
    "react-native-modal": "^11.5.6",
    "react-native-otp-inputs": "^7.1.1",
    "react-native-permissions": "^3.6.0",
    "react-native-radio-buttons-group": "^1.0.7",
    "react-native-raw-bottom-sheet": "^2.0.6",
    "react-native-reanimated": "^1.3.0",
    "react-native-safe-area-context": "^0.7.3",
    "react-native-screens": "^3.12.0",
    "react-native-share": "^8.0.0",
    "react-native-size-matters": "^0.3.0",
    "react-native-splash-screen": "^3.2.0",
    "react-native-status-bar-height": "^2.5.0",
    "react-native-svg": "^11.0.1",
    "react-native-svg-transformer": "^0.14.3",
    "react-native-swiper": "^1.6.0-nightly.5",
    "react-native-tab-view": "^2.14.0",
    "react-native-toast-message": "^2.1.5",
    "react-native-video": "^5.1.1",
    "react-native-webengage": "^1.2.12",
    "react-native-webview": "^9.4.0",
    "react-redux": "^7.1.3",
    "recyclerlistview": "^3.0.0",
    "redux": "^4.0.5",
    "redux-logger": "^3.0.6",
    "redux-thunk": "^2.3.0",
    "reselect": "^4.0.0",
    "yup": "^0.28.3"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@babel/runtime": "^7.20.0",
    "@react-native-community/eslint-config": "^3.2.0",
    "babel-jest": "^29.2.1",
    "eslint": "^8.19.0",
    "jest": "^29.2.1",
    "metro-react-native-babel-preset": "0.73.10",
    "prettier": "^2.4.1",
    "react-test-renderer": "18.2.0",
    "babel-loader": "^8.0.6",
    "babel-plugin-module-resolver": "^4.0.0",
    "eslint-config-airbnb": "^19.0.4",
    "eslint-plugin-import": "^2.26.0",
    "eslint-plugin-jsx-a11y": "^6.6.0",
    "eslint-plugin-react": "^7.30.1",
    "eslint-plugin-react-hooks": "^4.6.0",
    "eslint-plugin-react-native": "^4.0.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

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

buildscript {
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 21
        compileSdkVersion = 33
        targetSdkVersion = 33

        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"
        kotlinVersion = "1.8.0"
        androidXBrowser = "1.4.0"
    }
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath("com.android.tools.build:gradle:7.3.1")
        classpath("com.facebook.react:react-native-gradle-plugin")
        classpath("com.google.gms:google-services:4.3.5")
        classpath("com.google.firebase:firebase-crashlytics-gradle:2.8.1")
    }
}

android/app/build.gradle
apply plugin: "com.android.application"
apply plugin: "com.facebook.react"

apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'

import com.android.build.OutputFile

/**
 * This is the configuration block to customize your React Native Android app.
 * By default you don't need to apply any configuration, just uncomment the lines you need.
 */
react {
    /* Folders */
    //   The root of your project, i.e. where "package.json" lives. Default is '..'
    // root = file("../")
    //   The folder where the react-native NPM package is. Default is ../node_modules/react-native
    // reactNativeDir = file("../node_modules/react-native")
    //   The folder where the react-native Codegen package is. Default is ../node_modules/react-native-codegen
    // codegenDir = file("../node_modules/react-native-codegen")
    //   The cli.js file which is the React Native CLI entrypoint. Default is ../node_modules/react-native/cli.js
    // cliFile = file("../node_modules/react-native/cli.js")

    /* Variants */
    //   The list of variants to that are debuggable. For those we're going to
    //   skip the bundling of the JS bundle and the assets. By default is just 'debug'.
    //   If you add flavors like lite, prod, etc. you'll have to list your debuggableVariants.
    // debuggableVariants = ["liteDebug", "prodDebug"]

    /* Bundling */
    //   A list containing the node command and its flags. Default is just 'node'.
    // nodeExecutableAndArgs = ["node"]
    //
    //   The command to run when bundling. By default is 'bundle'
    // bundleCommand = "ram-bundle"
    //
    //   The path to the CLI configuration file. Default is empty.
    // bundleConfig = file(../rn-cli.config.js)
    //
    //   The name of the generated asset file containing your JS bundle
    // bundleAssetName = "MyApplication.android.bundle"
    //
    //   The entry file for bundle generation. Default is 'index.android.js' or 'index.js'
    // entryFile = file("../js/MyApplication.android.js")
    //
    //   A list of extra flags to pass to the 'bundle' commands.
    //   See https://github.com/react-native-community/cli/blob/main/docs/commands.md#bundle
    // extraPackagerArgs = []

    /* Hermes Commands */
    //   The hermes compiler command to run. By default it is 'hermesc'
    // hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
    //
    //   The list of flags to pass to the Hermes compiler. By default is "-O", "-output-source-map"
    // hermesFlags = ["-O", "-output-source-map"]
}

/**
 * Set this to true to create four separate APKs instead of one,
 * one for each native architecture. This is useful if you don't
 * use App Bundles (https://developer.android.com/guide/app-bundle/)
 * and want to have separate APKs to upload to the Play Store.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Set this to true to Run Proguard on Release builds to minify the Java bytecode.
 */
def enableProguardInReleaseBuilds = false

/**
 * The preferred build flavor of JavaScriptCore (JSC)
 *
 * For example, to use the international variant, you can use:
 * `def jscFlavor = 'org.webkit:android-jsc-intl:+'`
 *
 * The international variant includes ICU i18n library and necessary data
 * allowing to use e.g. `Date.toLocaleString` and `String.localeCompare` that
 * give correct results when using with locales other than en-US. Note that
 * this variant is about 6MiB larger per architecture than default.
 */
def jscFlavor = 'org.webkit:android-jsc:+'

/**
 * Private function to get the list of Native Architectures you want to build.
 * This reads the value from reactNativeArchitectures in your gradle.properties
 * file and works together with the --active-arch-only flag of react-native run-android.
 */
def reactNativeArchitectures() {
    def value = project.getProperties().get("reactNativeArchitectures")
    return value ? value.split(",") : ["armeabi-v7a", "x86", "x86_64", "arm64-v8a"]
}

android {
    ndkVersion rootProject.ext.ndkVersion

    compileSdkVersion rootProject.ext.compileSdkVersion

    namespace "com.app"
    defaultConfig {
        applicationId "com.app"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1"
        multiDexEnabled true
        vectorDrawables.useSupportLibrary = true
        resValue 'string', "CODE_PUSH_APK_BUILD_TIME", String.format("\"%d\"", System.currentTimeMillis())
    }

    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include (*reactNativeArchitectures())
        }
    }
    signingConfigs {
        debug {
            storeFile file('debug.keystore')
            storePassword 'android'
            keyAlias 'androiddebugkey'
            keyPassword 'android'
        }
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        debug {
            signingConfig signingConfigs.debug
        }
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://reactnative.dev/docs/signed-apk-android.
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // https://developer.android.com/studio/build/configure-apk-splits.html
            def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        defaultConfig.versionCode * 1000 + versionCodes.get(abi)
            }

        }
    }
}

dependencies {
    // The version of react-native is set by the React Native Gradle Plugin
    implementation("com.facebook.react:react-android")

    // Add the Firebase SDK for Google Analytics
    implementation("com.google.firebase:firebase-analytics:18.0.2")

    // Add the SDK for Firebase Cloud Messaging
    implementation("com.google.firebase:firebase-messaging:22.0.0")

    // For animated GIF support
    implementation("com.facebook.fresco:fresco:2.+")
    implementation("com.facebook.fresco:animated-gif:2.+")

    implementation("androidx.appcompat:appcompat:1.0.0")

    implementation("com.webengage:android-sdk:3.+")

    implementation("com.android.installreferrer:installreferrer:1.1.1")

    implementation("androidx.swiperefreshlayout:swiperefreshlayout:1.0.0")

    debugImplementation("com.facebook.flipper:flipper:${FLIPPER_VERSION}")
    debugImplementation("com.facebook.flipper:flipper-network-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.squareup.okhttp3', module:'okhttp'
    }
    debugImplementation("com.facebook.flipper:flipper-fresco-plugin:${FLIPPER_VERSION}")
    if (hermesEnabled.toBoolean()) {
        implementation("com.facebook.react:hermes-android")
    } else {
        implementation jscFlavor
    }
}

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

apply from: "../../node_modules/react-native-code-push/android/codepush.gradle"

settings.gradle
rootProject.name = 'App'
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':react-native-code-push'
project(':react-native-code-push').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-code-push/android/app')
include ':react-native-video'
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android-exoplayer')
include ':app'
includeBuild('../node_modules/react-native-gradle-plugin')

Screenshot

Have you yarn install afterwards?
Can you run ls -la node_modules/react-native-gradle-plugin and return the output?

Yes, I deleted node_modules folder and ran yarn install command after upgrading everything else.
 Unfortunately I can't help you further without a reproducer.

@cortinico not sure why this worked, but when I manually installed react-native-gradle-plugin, the issue got fixed. I know that it's not recommended as mentioned here, but this is the only thing that worked for me as of now. Any ideas what might be happening?

Any ideas what might be happening?

Sadly not. Can you try to remove the manual installation of react-native-gradle-plugin and then try to yarn why react-native-gradle-plugin and share the output? I'm wondering if there is something goign on with package dependencies.

I'm also experiencing this exact issue. What I simple did was to comment out.
I also discovered that this might be happening to those of us who aren't using fresh installation.
The react native upgrade helper shows that we need to reference react-native-gradle-plugin at some point.
https://react-native-community.github.io/upgrade-helper/?from=0.66.5&to=0.68.0#RnDiffApp-android-settings.gradle

I'm having the same problem with RN 0.71.10

What I simple did was to comment out.

Comment out what @Devmaleeq ?

I have the same issue. I can reproduce it by simply setting up a fresh project using as per the docs:
npx react-native@latest init RNTestApp

and then running:
npm run android

Leads to:
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not determine the dependencies of null.
   > Cannot query the value of this provider because it has no value available.

* 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

My react-native info

System:
  OS: macOS 13.2
  CPU: (10) arm64 Apple M1 Pro
  Memory: 1.18 GB / 32.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 18.12.1
    path: ~/.nvm/versions/node/v18.12.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.12.1/bin/yarn
  npm:
    version: 8.19.2
    path: ~/.nvm/versions/node/v18.12.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/daniel/.rvm/gems/ruby-3.0.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK:
    API Levels:
      - "26"
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
    Build Tools:
      - 28.0.3
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
    System Images:
      - android-31 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
    Android NDK: 23.1.7779620
IDEs:
  Android Studio: 2022.2 AI-222.4459.24.2221.10121639
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.1
    path: /usr/bin/javac
  Ruby:
    version: 3.0.0
    path: /Users/daniel/.rvm/rubies/ruby-3.0.0/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.0
    wanted: 0.72.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

I had this same issue which I'm pretty sure was due to incorrect java version (8). It resolved after switching java version to 11.
https://reactnative.dev/docs/next/environment-setup?platform=android#jdk

Make sure you you follow the upgrade steps in your android/build.gradle
https://react-native-community.github.io/upgrade-helper/?from=0.70.11&to=0.71.12#RnDiffApp-android-build.gradle

I'm facing the same issue, no news? =( this is really sad

Closing as @nikit-psl is unresponsive.
This issue is most likely caused from a wrong settings.gradle file in your project.
Specifically, if you're on React Native 0.72+, that file should look as follows:
https://github.com/facebook/react-native/blob/79c4ec1a9a27dc0fd76c1a65ebcb77257d3d4095/packages/react-native/template/android/settings.gradle#L2-L4
If you're on React Native <= 0.71, it should look as follows:
https://github.com/facebook/react-native/blob/7636e4c10209ab26b0d9f79ca34d08e874635dd1/template/android/settings.gradle#L2-L4

this error may caused by incorrect jdk version in android studio

i had to reinstall react-native-gradle-plugin

Closing as @nikit-psl is unresponsive.
This issue is most likely caused from a wrong settings.gradle file in your project.
Specifically, if you're on React Native 0.72+, that file should look as follows:
https://github.com/facebook/react-native/blob/79c4ec1a9a27dc0fd76c1a65ebcb77257d3d4095/packages/react-native/template/android/settings.gradle#L2-L4
If you're on React Native <= 0.71, it should look as follows:
https://github.com/facebook/react-native/blob/7636e4c10209ab26b0d9f79ca34d08e874635dd1/template/android/settings.gradle#L2-L4

this worked for me.

@cortinico  Thankyou

peterchukwu@chijiokes-MacBook-Pro loda-driver %  ls -la node_modules/react-native-gradle-plugin
total 56
drwxr-xr-x   10 peterchukwu  staff    320 Nov 22 21:30 .
drwxr-xr-x  610 peterchukwu  staff  19520 Nov 22 21:30 ..
-rw-r--r--    1 peterchukwu  staff    488 Nov 22 21:30 README.md
-rw-r--r--    1 peterchukwu  staff   1657 Nov 22 21:30 build.gradle.kts
drwxr-xr-x    3 peterchukwu  staff     96 Nov 22 21:30 gradle
-rwxr-xr-x    1 peterchukwu  staff   8070 Nov 22 21:30 gradlew
-rw-r--r--    1 peterchukwu  staff   2763 Nov 22 21:30 gradlew.bat
-rw-r--r--    1 peterchukwu  staff    711 Nov 22 21:30 package.json
-rw-r--r--    1 peterchukwu  staff    339 Nov 22 21:30 settings.gradle.kts
drwxr-xr-x    3 peterchukwu  staff     96 Nov 22 21:30 src

Closing as @nikit-psl is unresponsive.
This issue is most likely caused from a wrong settings.gradle file in your project.
Specifically, if you're on React Native 0.72+, that file should look as follows:
https://github.com/facebook/react-native/blob/79c4ec1a9a27dc0fd76c1a65ebcb77257d3d4095/packages/react-native/template/android/settings.gradle#L2-L4
If you're on React Native <= 0.71, it should look as follows:
https://github.com/facebook/react-native/blob/7636e4c10209ab26b0d9f79ca34d08e874635dd1/template/android/settings.gradle#L2-L4

This does NOT work when you have set the combination:
settings.gradle:
includeBuild('../node_modules/@react-native/gradle-plugin')
build.gradle:
classpath("com.facebook.react:react-native-gradle-plugin")
app/build.gradle:
apply plugin: "com.facebook.react"

I had same configuration as @dimisus above and got it resolved by doing npm i react-native-gradle-plugin - which installed   "react-native-gradle-plugin": "^0.71.19" .

The plugin is already configured for new projects created using npx react-native init. You don't need to do any extra steps to install it if you created your app with this command.
https://reactnative.dev/docs/react-native-gradle-plugin

My guess is when you run the build somewhere other than where you did react-native init ; like on git CI VM ; the package doesnt exist anywhere.
error before doing npm i react-native-gradle-plugin in the project.
Run cd android && ./gradlew assembleDebug --no-daemon
Downloading https://services.gradle.org/distributions/gradle-[8](https://github.com/daskabe/abc-reactNative-typescript-mobile/actions/runs/7110134331/job/19356153804#step:11:9).0.1-all.zip
...............10%................20%................30%................40%................50%................60%................70%................80%................[9](https://github.com/daskabe/abc-reactNative-typescript-mobile/actions/runs/7110134331/job/19356153804#step:11:10)0%................[10](https://github.com/daskabe/abc-reactNative-typescript-mobile/actions/runs/7110134331/job/19356153804#step:11:11)0%

Welcome to Gradle 8.0.1!

Here are the highlights of this release:
 - Improvements to the Kotlin DSL
 - Fine-grained parallelism from the first build with configuration cache
 - Configurable Gradle user home cache cleanup

For more details see https://docs.gradle.org/8.0.1/release-notes.html

To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/8.0.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'abc_rn_ts_mobile'.
> Could not determine the dependencies of null.
   > Could not resolve all task dependencies for configuration ':classpath'.
      > Could not resolve com.facebook.react:react-native-gradle-plugin.
        Required by:
            project :
         > Module version 'com.facebook.react:react-native-gradle-plugin' is not unique in composite: can be provided by [project :gradle-plugin, project :react-native-gradle-plugin].

* 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 1m [25](https://github.com/daskabe/abc-reactNative-typescript-mobile/actions/runs/7110134331/job/19356153804#step:11:26)s

settings.gradle
rootProject.name = 'abc_rn_ts_mobile'
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/@react-native/gradle-plugin')

build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 21
        compileSdkVersion = 33
        targetSdkVersion = 33

        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"
    }
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath("com.android.tools.build:gradle:7.3.1")
        classpath("com.facebook.react:react-native-gradle-plugin")
    }
}

allprojects {
  repositories {
    google()
    jcenter()
  }
}

This works for me. Thx all!
(RN 73.5, gradle 8.4, android gradle 8.3.0)
package.json
"@react-native/gradle-plugin": "^0.73.4",
android/build.gradle
buildscript {
ext {
kotlin_version = '1.9.22'
buildToolsVersion = "34.0.0"
minSdkVersion = 30
compileSdkVersion = 34
targetSdkVersion = 34
}

...
dependencies {
classpath("com.android.tools.build:gradle:8.3.0")
classpath("com.facebook.react:react-native-gradle-plugin")
classpath "de.undercouch:gradle-download-task:5.4.0"
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}
settings.gradle
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/@react-native/gradle-plugin')

Have you yarn install afterwards? Can you run ls -la node_modules/react-native-gradle-plugin and return the output?

I ran across this same issue/error today and I found this github issue from google... I followed @cortinico suggestion to output the react-native-gradle-plugin folder and this is what I saw:
total 8
drwxr-xr-x    4 davidpaul  staff    128 Mar  9 09:19 .
drwxr-xr-x@ 675 davidpaul  staff  21600 Mar  9 09:19 ..
-rw-r--r--    1 davidpaul  staff    933 Mar  9 09:19 .project
drwxr-xr-x    3 davidpaul  staff     96 Mar  9 09:19 bin

This was after multiple rm -rf node_modules && npm i... For some reason that package wasn't fully downloading, so I manually added it via npm i react-native-gradle-plugin, et voila!
total 56
drwxr-xr-x@  11 davidpaul  staff    352 Mar  9 09:28 .
drwxr-xr-x@ 675 davidpaul  staff  21600 Mar  9 09:28 ..
-rw-r--r--@   1 davidpaul  staff    488 Mar  9 09:28 README.md
drwxr-xr-x   10 davidpaul  staff    320 Mar  9 09:28 bin
-rw-r--r--@   1 davidpaul  staff   1657 Mar  9 09:28 build.gradle.kts
drwxr-xr-x@   3 davidpaul  staff     96 Mar  9 09:28 gradle
-rwxr-xr-x@   1 davidpaul  staff   8070 Mar  9 09:28 gradlew
-rw-r--r--@   1 davidpaul  staff   2763 Mar  9 09:28 gradlew.bat
-rw-r--r--@   1 davidpaul  staff    711 Mar  9 09:28 package.json
-rw-r--r--@   1 davidpaul  staff    339 Mar  9 09:28 settings.gradle.kts
drwxr-xr-x@   3 davidpaul  staff     96 Mar  9 09:28 src

For some reason the entire package was not being pulled from NPM, so I had to manually do it. Everything works now.
RN 0.70.6

so I manually added it via npm i react-native-gradle-plugin, et voila!

Doing npm i react-native-gradle-plugin is not correct and will break your project the next time you update react native

running npm i -g fixes it

IN MY CASE I RESTARTED WATCHMAN

In my case the issue was because of react-native-screens.
Result of yarn why react-native-gradle-plugin
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "react-native-screens" depends on it
   - Hoisted from "react-native-screens#react-native-gradle-plugin"
info Disk size without dependencies: "472KB"
info Disk size with unique dependencies: "2.18MB"
info Disk size with transitive dependencies: "27.36MB"
info Number of shared dependencies: 85
=> Found<EMAIL_ADDRESS>info This module exists because "react-native" depends on it.
info Disk size without dependencies: "260KB"
info Disk size with unique dependencies: "260KB"
info Disk size with transitive dependencies: "260KB"
info Number of shared dependencies: 0

i wasn't using it so simply uninstall the library fixed the problem for me

make sure node_modules/@react-native/gradle-plugin is exist, in my case this file is not exist and  re install package use npm install


Enhance auth0 setup part 4 : rule

Hello,
I try to setup an auth0 multitenant but end up with an error Cannot read property 'map' of undefined after a successful login
After some research look like something is wrong in my rule asked by the last point in auth0 setup.
From the link I found this rule :
function (user, context, callback) {
  var namespace = 'http://yourdomain/claims/'; // You can set your own namespace, but do not use an Auth0 domain

  // Add the namespaced tokens. Remove any which is not necessary for your scenario
  context.idToken[namespace + "permissions"] = user.permissions;
  context.idToken[namespace + "groups"] = user.groups;
  context.idToken[namespace + "roles"] = user.roles;

  callback(null, user, context);
}

Note:

Link https://auth0.com/docs/extensions/authorization-extension#controlling-application-access
Then I jump to Add Functionality and Use the Authorization Extension's Data in Rules

This rule make me got (user1)
{ 'http://yourdomain/claims/groups': [ 'tenant1' ],
  'http://yourdomain/claims/roles': [ 'Tenant User' ] }

But the application want "groups" not an url, so inside of the rule I removed the namespace but doesn't help, I got nothing in return.

Did I take the wrong rule (didn't see other one) ? Documentation from the given link has been updated ?

Thanks

@Manawasp the problem is this code doesn't account for namespaces in the claim.  I've pushed a change that fixes this.  This will require a couple tweaks in your setup.
First, your rule uses the namespace http://yourdomain/claims/.  In my code I am expecting: https://{process.env.ROOT_DOMAINt}/claims/....  The {ROOT_DOMAIN} piece should be the same value your configured in your .env file.
Here is how I configured my rule:
function (user, context, callback) {
  var namespace = 'http://yourcompany.com/claims/'; // You can set your own namespace, but do not use an Auth0 domain

  // Add the namespaced tokens. Remove any which is not necessary for your scenario
  context.idToken[namespace + "permissions"] = user.permissions;
  context.idToken[namespace + "groups"] = user.groups;
  context.idToken[namespace + "roles"] = user.roles;

  return callback(null, user, context);
}

This morning I went a head and update those steps to include the rule.  The previous link is gone.  Now the rule is embedded in the instructions.

Hi @sgmeyer, thanks for the update, I tried and noticed 2 missing update which use the old way to get groups from the payload :

routes/user.js l.15 in router.get('/', ...., function(req, res) {...
lib/tenant.js l.10 in getAuthorizedTenants


Rose repositories can be deleted by users in the access group

resolution_wontfix   |    by ibc599

Users in the access group can execute "rm -rf /home/access-svn/roses_au_svn" because they have write/execution permission.
They need write/execution permissions for creating and writing files/directories in the repository.

Issue migrated from trac:12 at 2024-01-31 17:08:23 +1100

<EMAIL_ADDRESS>commented

Possible alternative is to set up something like gitolite, and have people always accessing through svn+ssh://svn@accessdev/repo
We set up an 'svn' user with no shell access (so they can't delete anything), then add to it's authorised_keys file for each user:
command="svnserve -t --tunnel-user=harry" TYPE1 KEY1<EMAIL_ADDRESS>command="svnserve -t --tunnel-user=sally" TYPE2 KEY2<EMAIL_ADDRESS>
http://svnbook.red-bean.com/en/1.6/svn.serverconfig.svnserve.html (at the bottom of the page)
As far as I'm aware this is how repos.nci.org.au works as well.

<EMAIL_ADDRESS>commented

A program called 'svnstsw' is included in subversion's contrib directory - http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/svnstsw/README. This is intended to wrap svnserve, it's a setuid program so anyone running it gets promoted to the subversion user, however they can only do subversion operations with it & can't delete the repository.
I'd suggest we create the repository with the default permissions as a new user 'svn', then once the wrapper has been set up instruct people to access the repository using the svn+ssh protocol.

<EMAIL_ADDRESS>changed milestone from Future to accessdev v1.0

<EMAIL_ADDRESS>commented

This needs to be resolved before a public release

<EMAIL_ADDRESS>changed status from new to accepted

<EMAIL_ADDRESS>commented

Urgh - and again we're at the problem where local system accounts can't access the NFS mounts, so we can't set up a 'svn' user on accessdev & still have things stored on /home or /projects.
Maybe it would be worthwhile to get NCI to set us up some system accounts on their NFS server for stuff like svn, git, apache & rose. Or maybe it will get worked out in the upgrade to the new cloud, who knows.

<EMAIL_ADDRESS>changed owner from `` to saw562

<EMAIL_ADDRESS>commented

Not a problem, I think I'm just about there with a new subversion::server module that will serve over svn+ssh & allow for adding multiple hooks.

ibc599 changed reviews which not transferred by tractive

<EMAIL_ADDRESS>commented

I've set up a Puppet module to install the svnstsw wrapper, available at https://github.com/ScottWales/puppet-svnserve.
This allows people to access the repository with e.g. svn+ssh://accessdev.nci.org.au/svn/repo, however the repository itself is writeable only for the subversion user (through the magic of setgid). This means users can't go through the filesystem & break stuff.

<EMAIL_ADDRESS>removed milestone (was accessdev v1.0)

ibc599 commented

I’ve being trying your svnserve module but I'm unsure how to set the username and group.
Normally I add the lines into the rose module,
 include svnserve::svnstsw
 svnserve::repo { "${repos_dir}/${repos_name}": }

but this tries to use ‘svn’ for user and group.  How can  we set the user and group to ju7_svn and ju7?
Also could the prerequisites be added to svnserve to ensure svnserve is built correctly. Simply adding svnserve into the node produces errors because of missing prerequisites.

<EMAIL_ADDRESS>commented

Milestone accessdev v1.0 deleted

<EMAIL_ADDRESS>commented

This will be resolved by the shared repository

<EMAIL_ADDRESS>changed status from accepted to closed

<EMAIL_ADDRESS>changed resolution from `` to wontfix


Feature/1996 empty application fields

What's included?
The logic for whether '(not asked)' displays will depend upon the way the exercise is configured and where we are in the timeline rather than what's been completed in the individual applications.

Add a helper function isApplicationPartAsked to check if an application part is asked in the current stage
Add a helper function isCharacterChecksAsked to check if character checks of an application are sent

e.g. if an exercise only asks for personal details during initial registration and that's where we are in the timeline then the application should have '(not asked)' against every field apart from the personal details fields. The personal details fields should say 'no information' until the candidate has entered data into the field.
e.g.2. if everything is asked for in the application form and the application window has just closed (ie character checks and IAs have not been requested yet) then most fields should have values or display 'no information' however fields that are specific to character checks (e.g. current address, previous address) should have '(not asked)'.
Closes #1996
Note:

In Personal details the following fields are asked during Character Checks:

Place of birth
Current Address
Has lived at this address for more than 5 years
Previous Addresses
VAT registration number

Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?

Go to an application of an exercise.
Check if No information (not asked) shows properly on the full information according to the exercise configuration and the current timeline.

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Screenshot:

Related permissions
Have permissions been considered for this functionality?

No permission changes required

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

just noticed this in UT  we might want to consdier removing the banner as i think this work potentially makes it a bit redundant

No information (not asked), as expected


Add a "required" option for the Labels tag

Is your feature request related to a problem? Please describe.
It is not possible to enforce that the <Labels> tag is used at least once in an annotation.
Describe the solution you'd like
It would be great if there were a "required" option for <Labels>, like some of the other tags (eg <Choices>), so that I can enforce usage of <Labels>.
Describe alternatives you've considered
I can set "enable_empty_annotation" to true in the project config which does technically enforce use of the <Labels> tag but this only works if <Labels> is the only Control Tag in the annotation config, which is often not the case in real projects.
Additional context
There is currently a "maxUsages" option for <Labels>, perhaps a "minUsages" would be easy to add.  It would also be more general-purpose than a "required" option because you could enforce a precise number of usages, eg 1, 2, 3, etc.

That would be huge!

@matthewdixon-weloc, thanks for your issue request. I'll be bringing it to the team this week to determine feasibility and next steps.


Improve _measured_source_path_matches speed

This patch speeds up from 45 minutes to 30 seconds with 36 jacoco.xml and 51 src root.

Thanks for the PR! Ill do the release asap and report in the issue


error when starting traefik

I was trying to deploy a web gateway combination of etcd, coredns and traefik.
Everything works ok until I tried to start the traefik service and got this error:
In [29]: print(t.eco.trace)
Traceback (most recent call last):
  File "/opt/code/github/threefoldtech/0-robot/zerorobot/task/task.py", line 78, in execute
    self._result = self._func()
  File "/opt/code/github/threefoldtech/0-templates/templates/traefik/traefik.py", line 82, in start
    self._traefik_sal.start()
  File "/opt/code/github/threefoldtech/jumpscale_lib/JumpscaleLib/sal_zos/traefik/Traefik.py", line 101, in start
    self.create_config()
  File "/opt/code/github/threefoldtech/jumpscale_lib/JumpscaleLib/sal_zos/traefik/Traefik.py", line 74, in create_config
    config = self._config_as_text()
  File "/opt/code/github/threefoldtech/jumpscale_lib/JumpscaleLib/sal_zos/traefik/Traefik.py", line 86, in _config_as_text
    client.put("traefik/acme/account", "")
  File "/opt/code/github/threefoldtech/jumpscale_lib/JumpscaleLib/clients/etcd/EtcdClient.py", line 55, in put
    self.api.put(key, value)
  File "/opt/code/github/threefoldtech/jumpscale_lib/JumpscaleLib/clients/etcd/EtcdClient.py", line 46, in api
    self._api = etcd3.client(**kwargs)
  File "/usr/local/lib/python3.5/dist-packages/etcd3/client.py", line 987, in client
    grpc_options=grpc_options)
  File "/usr/local/lib/python3.5/dist-packages/etcd3/client.py", line 147, in __init__
    resp = self.auth_stub.Authenticate(auth_request, self.timeout)
  File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 532, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 466, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
	status = StatusCode.UNAVAILABLE
	details = "Connect Failed"
	debug_error_string = "{"created":"@1539960647.343920310","description":"Failed to create subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":2636,"referenced_errors":[{"created":"@1539960647.343913293","description":"Pick Cancelled","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":241,"referenced_errors":[{"created":"@1539960647.343680238","description":"Connect Failed","file":"src/core/ext/filters/client_channel/subchannel.cc","file_line":663,"grpc_status":14,"referenced_errors":[{"created":"@1539960647.343673248","description":"connect failed: [Errno 9] File descriptor was closed in another greenlet","file":"./src/core/lib/iomgr/gevent_util.h","file_line":33,"grpc_status":14}]}]}]}"

Here is my deploy script:
    def deploy(self, node_id):
        robot = j.clients.zrobot.get_by_id(node_id)

        logger.info("install zerotier client")
        zt = robot.services.find_or_create('zerotier_client', 'zt', data={'token': self._zt_token})

        tasks = []
        logger.info("install etcd")
        etcd = robot.services.find_or_create('etcd', 'etcd_'+self.name, data={
            'nics': [{'name': 'zerotier', 'type': 'zerotier', 'ztClient': 'zt', 'id': self._zt_id}],
            'token': 'cluster_%s' % self.name,
        })

        tasks.append(etcd.schedule_action("install").wait(die=True))
        tasks.append(etcd.schedule_action("start").wait(die=True))

        logger.info("install coredns")
        coredns = robot.services.find_or_create('coredns', 'coredns_'+self.name, data={
            'nics': [{'name': 'zerotier', 'type': 'zerotier', 'ztClient': 'zt', 'id': self._zt_id}],
            'etcd': etcd.name
        })

        tasks.append(coredns.schedule_action("install"))
        tasks.append(coredns.schedule_action("start"))

        logger.info("install traefik")
        traefik = robot.services.find_or_create('traefik', 'traefik_'+self.name, data={
            'nics': [{'name': 'zerotier', 'type': 'zerotier', 'ztClient': 'zt', 'id': self._zt_id}],
            'etcd': etcd.name
        })

        tasks.append(traefik.schedule_action("install"))
        tasks.append(traefik.schedule_action("start"))
        return tasks

@zaibon  now i think we should close this issue ?

let's wait to confirm out fixes indeed solve it completly


Test building of redirects

This is currently broken in master. Before looking further into it myself, I wonder if anyone else who is more familiar with the codebase can take a quick look, and see if it is something obvious?
Regarding my implementation of the test, I noticed that while the redirect feature makes use of the step
And a file named "config.rb" with:
"""
redirect "hello.html", to: "world.html"
"""

It seems impossible to make use of this when building an an app, so I created a new fixture. Given that I have this fixture, does it make sense to convert the rest of the scenarios to use it (i.e., is a using fixtures preferred over using the  a file named "config.rb" with: step)?

I managed to fix this issue. I think it occurred any time that a Middleman::Sitemap::Resource was inherited and had a custom render method defined. Builder assumed any resource that was not binary? or static_file? had a file_descriptor. However, this was not the case for a Redirect, nor and EndpointResource.
To be honest, I didn't totally understand the intention of the FileVertex, but it seemed like the vertex tracking might not apply in this case, and so my PR bypasses it when there is no file_descriptor. All the tests pass, so I guess it isn't introducing any new bugs, but perhaps there's a more elegant way of handling it.

Excellent. Thank you for digging in. The vertex stuff is part of the incremental build system. It is admittedly quite obtuse.

The question here is whether a change to a file on disc could possibly require regenerating the redirect file. I don't think so. Only a data file or config change would do that and those are handled elsewhere.


x srv!SrvComputerName cannot work in Windows 10.

x srv!SrvComputerName cannot work in Windows 10. But I found a great article by SNoone to fix this issue. It introduces "r @$t0 = @@masm(mrxsmb!SmbCeContext); dx (nt!_UNICODE_STRING[4])(@$t0)" or "dpu mrxsmb!SmbCeContext" to get computer name.
The original article is here:
https://www.osr.com/blog/2018/06/22/finding-computer-name-crash-dump-2018-edition/
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2a09232d-fbb3-2766-29d7-a742f0bde3c0
Version Independent ID: 5f34f241-dcf4-569c-fdfe-4647103ee379
Content: Extracting Information from a Dump File - Windows drivers
Content Source: windows-driver-docs-pr/debugger/extracting-information-from-a-dump-file.md
Product: windows-hardware
GitHub Login: @DOMARS
Microsoft Alias: domars

@wayyt - Thanks for the pointer to Scott's article. Looks like this topic needs updating.
In my limited testing, with Windows desktop 1809, I was able to display mrxsmb!SmbCeContext, but it did not contain any of the expected information - just empty strings, so wondering if this tip is still valid. Is there a pre-requisite step or specific type of dump that this is valid with? Do you need to be in a specific context?
Another technique here is to do a raw memory search, but in addition to determining the range, you need a valid target string.

@wayyt - Thanks again for this feedback on validating / updating this topic and the pointer to the OSR article. I have created and internal work tracking item, so closing this issue. Good luck with your Windows debugging.


Generate channel documentation?

Having to duplicate Go docs and manual docs for channel types is a pain. This PR attempts to generate channel documentation from the actual Go types and source code. To get comments, I think I had to parse Go sources (via the parser package). Clumsy for sure.
The results are in doc, and those chan_*.md where generated via make chan-docs (and also from make all).
Dunno if this approach is a good idea, but at least it gets Go docs and the manual in sync.

I don't know what to do about the build failure (from the action). The module in question isn't on github.com/Comcast/plax yet. I vaguely recall a fix.

Should fix #26.


consider making this CPM compliant

https://github.com/TheLartians/CPM.cmake
It allows developers to include your project by simply adding the following to their CMakeLists.tzt
CPMAddPackage(
        NAME libpopcnt
        GITHUB_REPOSITORY kimwalisch/libpopcnt
        VERSION 2.3
)
target_link_libraries(MyProgram PUBLIC libpopcnt)

I might support CPM once it is widely used or there is an important project using libpopcnt which requires this feature.


Add a setting to hide status bar breadcrumbs

First of all, thanks for developing this plugin, it makes a great difference when navigating folder trees.
Because I have my ‘title bar’ disabled, QE is sitting at the bottom left of the status bar. Since I use the 'Hider' plugin to hide the app ribbon, it makes it so that QE's breadcrumbs bar ends up under the app ribbon upon hovering (Hider makes the ribbon appear on hover at the bottom left of the window). Additionally, QE elongates the status bar into the main window resulting in less reading area at the bottom. My suggestion would be to have an option that disables the breadcrumbs bar (especially now that you can get persistent breadcrumbs through activating ‘tab title bar’), while still allowing you to trigger the floating folder.
I use v.0.16.3 with Minimal and 'hidden' window style frame.

This will be added to the style settings in the next release, along with support for using the 0.16.3 title bar breadcrumbs to access QE menus.

0.2.0 is now out with this feature and if you turn off the status bar crumbs it will use the tab titlebar ones if they are visible for the active pane.

This is brilliant, thank you so much! I noticed that if you choose the setting to hide QE the explorer shows up in the middle of the screen as opposed to on the left (see screenshot). I was able to correct that with a CSS snippet (see below) but was wandering if there is a more elegant way.
Snippet
div.menu.qe-popup-menu {   left:  9.688px !important;   top:  52px !important; }

I guess you're not currently showing the tab title bar?  The new mode is intended to work with the tab title bar. (Settings > Appearance > Advanced > Show tab title bar).

I do have it on, it's behind QE's explorer. This note is on root, that's why you can't see the path. I tried disabling the title bar and then QE's explorer shows on the left. Is as if it was linked to the title bar.

Yes, that's how it works if you don't have the status bar or main title bar available.  QE uses its own breadcrumbs first (if visible), or else the breadcrumbs in the title bar of the active tab.
That does mean that it will tend to end up in the middle of the screen, if you only have one tab group and don't align the header breadcrumbs to the left.  (Obsidian centers them by default.)

Gotcha! Thanks for the explanation.


TypeError: Input 'y' of 'Sub' Op has type int32 that does not match type float32 of argument 'x'.

System information

Have I written custom code: [posted below]
Done on Google Colab using TF 2.5

I have done with building model but these some problem when training.  The errors are not clear enough I have no idea about which causes these errors.
Traceback is:
Epoch 1/5
/usr/local/lib/python3.7/dist-packages/tensorflow/python/autograph/impl/api.py:376: UserWarning: CRF decoding models have serialization issues in TF >=2.5 . Please see isse #2476
  return py_builtins.overload_of(f)(*args)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-27-1b7e06547f26> in <module>()
      1 history = MODEL.fit(X_tr, np.array(y_tr), batch_size=BATCH_SIZE, epochs=EPOCHS,
----> 2                     validation_split=0.1, verbose=2)

9 frames
/usr/local/lib/python3.7/dist-packages/tensorflow/python/framework/func_graph.py in wrapper(*args, **kwargs)
    984           except Exception as e:  # pylint:disable=broad-except
    985             if hasattr(e, "ag_error_metadata"):
--> 986               raise e.ag_error_metadata.to_exception(e)
    987             else:
    988               raise

TypeError: in user code:

    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/training.py:855 train_function  *
        return step_function(self, iterator)
    /usr/local/lib/python3.7/dist-packages/keras/losses.py:142 __call__  *
        losses = call_fn(y_true, y_pred)
    <ipython-input-25-f9adc600d49b>:7 call  *
        mse = tf.math.reduce_mean(tf.square(y_true - y_pred))
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/math_ops.py:1250 binary_op_wrapper
        raise e
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/math_ops.py:1234 binary_op_wrapper
        return func(x, y, name=name)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/util/dispatch.py:206 wrapper
        return target(*args, **kwargs)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/math_ops.py:548 subtract
        return gen_math_ops.sub(x, y, name)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/gen_math_ops.py:10562 sub
        "Sub", x=x, y=y, name=name)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/framework/op_def_library.py:558 _apply_op_helper
        inferred_from[input_arg.type_attr]))

    TypeError: Input 'y' of 'Sub' Op has type int32 that does not match type float32 of argument 'x'.

Link to colab: https://colab.research.google.com/drive/1eRN8yxM4TyQ7JmO-hxjM76dIQz2_Hpga?usp=sharing
Link to dataset: https://drive.google.com/file/d/1cVRPolctpCgcQontLDm8OmNHUMBM1KSp/view?usp=sharing
Please help me with fixing this bug.

Hi @tranduchuy682
In the custom loss function that you are using y_pred is of data type tf.int32 whereas 0.5 is is tf,float32. To subtract two eager tensor both should be of same data type and hence you have to cast y_pred to float32 as well in  the regularizing parameter.

Thank you
I've fixed the data type as you said and having new problem as below:
ValueError                                Traceback (most recent call last)
<ipython-input-75-9037a2d0e778> in <module>()
      1 history = MODEL.fit(X_tr, y_tr, batch_size=BATCH_SIZE, epochs=EPOCHS,
----> 2                     validation_split=0.1, verbose=2)

4 frames
/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/data_adapter.py in _check_data_cardinality(data)
   1628           label, ", ".join(str(i.shape[0]) for i in nest.flatten(single_data)))
   1629     msg += "Make sure all arrays contain the same number of samples."

Make sure all arrays contain the same number of samples.

I don't know which causes this error because both x and y have the same length.

@tranduchuy682
Could you please move this to closed status, if it is resolved.Thanks


Ignore groups with include_examples in LetBeforeExamples

fixes #1392
Moving let above include_examples that defines the same variable may break the spec.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[-] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

It would be nice if we can conditionally mark the auto-correct as unsafe / run some auto-corrections only if rubocop was run with unsafe corrections enabled (so it would output N more could be corrected if you run with -A

N more could be corrected if you run with -A

Great idea! I'd use that.

@Darhazer I've started filing a RuboCop ticket and found that if you run rubocop -a, you get this:
1 file inspected, 1 offense detected, 1 more offense can be corrected with `rubocop -A`


Add shared folder to docker container

The FEniCS docker container makes it really easy to use a shared folder between the host and container. How did they do this? Start here: http://fenics-containers.readthedocs.io/en/latest/introduction.html#running-fenics-in-docker

It turns out that nothing needs to be done with the Dockerfile. This already works. I updated the README to show how to mount a shared folder to the Docker container. Unfortunately if you don't specify a valid path from the container's perspective, docker will just go ahead and enter the container without a shared folder.

For the record, from the current README:
"
Or run the container with access to a shared folder (shared between the host and the container)
docker run -ti -v $(pwd):/home/dealii/shared zimmerman/peclet:latest
"


Readme and Ubuntu Support

install.sh not suport Ubuntu .
install.sh 不支持 Ubuntu。
error :
sudo: yum: command not found
Failed to  + install expect

After 1.0, it does not depend on expect anymore


add displayName to React.createClass()

From @fkchang on November 10, 2015 21:9
and now we can use chrome react devtools and see what our components are...
Copied from original issue: zetachang/react.rb/pull/76

From @ajjahn on November 16, 2015 18:44
Merged.


Make it easier to run multiple pages in parallel

I'm working on a Grunt task that opens one or more pages/urls up (e.g. the demo pages) in phantomjs and does various performance and integration tests (no uncaught exceptions or 404 errors etc.).
The way the events are emitted makes it difficult to keep context, so one is basically required to, when inside a multitask, attach the event handlers in the outer scope.
However when using something like async.forEachLimit to iterate through the pages, it's near impossible to deal with the events.
In theory I could move require( 'grunt-lib-phantomjs' ).init( grunt ); and the event handlers to inside the main work loop. However this still poses issues with the output.
Abstract example:
module.exports = function ( grunt ) {
    var phantomjs = require( 'grunt-lib-phantomjs' ).init( grunt );
    ...

    phantomjs.on( 'onInitialized', function () {
        grunt.log.write( '...' );
    } );

    phantomjs.on( 'error.onError', function ( msg, stackTrace ) {
        phantomjs.halt();
        grunt.log.writeln();
        grunt.log.error( 'PhantomJS>\nUncaught ' + msg );
        console.dir( stackTrace );
        failures++;
    });

    phantomjs.on( 'fail.timeout', function () {
        phantomjs.halt();
        grunt.log.writeln();
        grunt.log.error('PhantomJS timed out.');
        failures++;
    } );

    ...

    grunt.registerMultiTask( 'phantomcheck', function () {
        var done = this.async(),
            urls = options.urls.concat( this.filesSrc );

        grunt.util.async.forEachSeries( urls, function ( url, next ) {
            grunt.log.write( 'Checking ' + url );
            phantomjs.spawn(url, {
                options: options,
                done: function ( err ) {
                    ran++;
                    if ( err ) {
                        next( err ); // Abort
                    } else {
                        next(); // Done
                    }
                }
            });
        // Async loop finished
        }, function ( err ) {
            if ( failure ) {
                grunt.log.error( failures + ' pages failed.' );
                done( false );
            } else {
                grunt.log.ok( ran + ' pages checked.' );
                done();
            }
        } );
    } );
};

It would cut down the execution time a lot if I could use async.forEachLimit( urls, 3, .. so that we'd run three of them in parallel. I'm curious if other people have run into this.
I'm considering to do it and solve the output issue by buffering it in a wrapper object instead of using the grunt.log methods directly (e.g. mylog =  { text: '', error: '', ok: '', dirobjects: [] }) and pass it on to the grunt.log methods at the end of each iteration.

Switched to Karma.


Custom Templates

My idea of creating custom templates is having a user define their own main.tex and structure.tex files, and this would be done like the following:
% custom_templates.texcreate

\begin{MAIN}
% main body contents
\end{MAIN}

\begin{STRUCTURE}
% structure body contents
\end{STRUCTURE}

This would then involve texc_config::Config.template to become an Option<String> and add in a new field custom_template. With an added error checking, this means that either a config.toml accepts a custom template or a normal template, but not both.
An added interpreter module will also be needed, and should be added inside texc_config using Regex &  lazy_static.

Changes to proposed, closing issue with a post to explain the additions


Map domains of older websites.

v0.fvcproductions.com - Wordpress.com
v1.fvcproductions.com - Jekyll
v2.fvcproductions.com - Hugo v1
v3.fvcproductions.com (Current) - Hugo v2

✅ By submitting this issue, I have verified the following

[x] Checked to see if the issue has already been discussed before 🤔
[x] If proposing new content to be added, enough details were provided 🔍

Not worth - lol


join should allow longer lines and retain original quotes

Describe the bug
For some mysterious reason, the join command seems to hate long lines so it splits them into multiple shorter lines and inserts >- to indicate how newlines should be handled. Plus it strips off needed quotation marks. Here is an example of a "long" line before the join command:
  - name: Terms
    description: An Accounts Payable term is a rule that a vendor establishes for extending credit to your company. Terms can be associated with transactions or with specific vendors.

and after:
- name: Terms
    description: >-
      An Accounts Payable term is a rule that a vendor establishes for extending
      credit to your company. Terms can be associated with transactions or with
      specific vendors.

You'd be right if you thought, "That original line doesn't look very long at all!" Yes, there is no reason that I can think of for join to do anything to that line.
I'm opening this bug because turning single lines into multiple lines can cause problems for some other tools that need to parse the files produced by join. Also, when this happens with keywords other than description it can cause the schema to be invalid. For example:
    $ref: >-
      #/components/schemas/cash-management-payment-provider-bank-account

The reference needs to be in quotes. It was in quotes in the original file, but join stripped them out when it thought the line was too long. Other (shorter) references still have their quotes after join.
To Reproduce
Run redocly join on a couple of OpenAPI YAML files that have some lines that are longer than 80 characters.
Expected behavior
For long lines, the output should be exactly what the input was. There was nothing wrong with the original lines, and there is no benefit to breaking them into shorter lines. There is certainly no benefit to removing needed quotation marks-- I'd call that a bug.
Redocly Version(s)
1.10.5
Node.js Version(s)
18.7.0
Additional context
The join command is incredibly useful-- thank you! Just need to fix the little bugs that show up.

For long lines, the output should be exactly what the input was.

Unfortunately that's not possible. There is only one good yaml parser in JS out there and it doesn't preserve original formatting (it also looses comments, etc). Adding support for this is complex (I already tried) as the YAML spec is pretty complex and the parser is sophisticated.
Why would you edit the result of the join command? Just to clarify, the resulting file despite differences in formatting will parse to exactly same data structure. You can try to format the output with prettier. Maybe it produces a better result.

Thanks @steve-nay-sage , this is good info! Like @RomanHotsiy says, keeping things identical is difficult because we're parsing it in, making a new structure, and writing it back out. We should only be adjusting the lines for markdown fields though, that $ref example doesn't look correct.  I think the quotes could do with another look as well.

Why would I edit the results of the join command? In this case I needed to add the quotes back that join (or the parser) removed from $ref lines that it thought were too long. So I modified my script that was calling join to do some cleanup after join finished.

Oh, I see but I'm confused a bit.
The result of parsing this yaml:
$ref: >-
  #/components/schemas/cash-management-payment-provider-bank-account

is exactly same as this yaml:
$ref: "#/components/schemas/cash-management-payment-provider-bank-account"

According to the yaml spec and I just tried a few online YAML to JSON convertors to confirm that.
Which tooling you use? Is it some tooling that doesn't parse yaml but works on raw strings?


Downgraded Python version to 3.12.3

Temporarily fixes #2330
Consistent with #885

3.12.3 might be better https://github.com/pydantic/pydantic/issues/9609#issuecomment-2155832461

Consistent with #885

For non-docker method, we are currently using 3.11 only.

In my recollection, we were using 3.12, when eventually we found out too many users were running into an issue with a Chroma dependency on 3.12, and we have downgraded for that reason, temporarily.
I would personally favor keeping 3.12 as much as we can, and go the other way around: hope to fix issues that prevent the upgrade, rather than continue downgrading.
That said ... it is a bit weird at this time. 😅

If 3.12.3 solves the problem I generally prefer going with newer versions of things myself.

My fault for the confusion. I did think our mix of python versions was a bit too funny. But this is the full app image that people run, and it works as it is.
This is only an issue with building it, and there's a PR on pydantic so it will be fixed upstream.
If we're okay with trying 3.12.3, this is a successful test for the edits suggested:
https://github.com/enyst/OpenDevin/actions/runs/9431038477/job/25979245963?pr=6

https://github.com/OpenDevin/OpenDevin/pull/1664#discussion_r1632159141


Batch Configuration - broken?

Related to
Somewhat similar to #770
Short Background
I have webserver app where I build an mxnet-model-server docker container and archive a particular .mar file that contains a number of non-mxnet things. I launch an ec2, build my docker-container and .mar file on that ec2 and then push docker-container is pushed to ECR and the .mar file is saved to s3. A launch configuration/autoscaling/load-balancer architecture is used to then serve requests to the given singular model from that ECR image and s3-saved .mar file.
Problem
Registering models via API instead of model-archiver with -mms-config properties is not ideal for dockerized pipelines:

A few weird problems that I found in trying to get this pipeline set up: It looks like any call to update the config.parameters via PUT resets all non-called parameters? Unless I'm doing something entirely wrong.
Based on searching through issues, #770, and source-code, it looks like mxnet-model-server can't update batch_size unless the model is registered with it from the API call and NOT at startup when the given model is located in the model-server directory (unless I'm mistaken)? That seems like such a non-user intuitive flow, no? I found a work-around, but it's cumbersome. So I have to ask: am I doing something incorrectly with the config.properties on initial startup with the '--mms-config' parameter for it not to have the batch_size be be greater than 1 (as indicated in the config.properties file I provided to mms)?
Considering my pipeline, it would be great if I didn't have to update batch_size/queue_size/max_delay via the API every single time the load balancer spins up a new instance -  and instead would "simply" work with the config.properties file provided.

Examples
docker-config.properties
model_store=/opt/ml/model
load_models=ALL
inference_address=http://<IP_ADDRESS>:8080
management_address=http://<IP_ADDRESS>:8081
default_workers_per_model=2
job_queue_size=1000
async_logging=true
number_of_netty_threads=32
batch_size=8
max_batch_delay=60
# max_workers=0
# job_queue_size=100
# number_of_gpu=1
# cors_allowed_origin
# cors_allowed_methods
# cors_allowed_headers
# keystore=src/test/resources/keystore.p12
# keystore_pass=changeit
# keystore_type=PKCS12
# private_key_file=src/test/resources/key.pem
# certificate_file=src/test/resources/certs.pem
# blacklist_env_vars= H@I2ga1T8

start model server
$ mxnet-model-server --start --mms-config docker-config.properties --model-store /home/mkrzus/projects/TESTme/TEST_recognition_service/service-stubs/

look at output
MMS Home: /home/mkrzus/.conda/envs/mlp3/lib/python3.6/site-packages
Current directory: /home/mkrzus/projects/TESTme/TEST_recognition_service
Temp directory: /tmp
Number of GPUs: 1
Number of CPUs: 12
Max heap size: 128 M
Python executable: /home/mkrzus/.conda/envs/mlp3/bin/python
Config file: docker-config.properties
Inference address: http://<IP_ADDRESS>:8080
Management address: http://<IP_ADDRESS>:8081
Model Store: /home/mkrzus/projects/TESTme/TEST_recognition_service/service-stubs
Initial Models: ALL
Log dir: /home/mkrzus/projects/TESTme/TEST_recognition_service/logs
Metrics dir: /home/mkrzus/projects/TESTme/TEST_recognition_service/logs
Netty threads: 32
Netty client threads: 0
Default workers per model: 2
Blacklist Regex: N/A
Maximum Response Size: 6553500
Maximum Request Size: 6553500
2019-05-11 11:51:08,395 [DEBUG] main com.amazonaws.ml.mms.ModelServer - Loading models from model store: batchshufflenet.mar
2019-05-11 11:51:41,980 [INFO ] main com.amazonaws.ml.mms.archive.ModelArchive - model folder already exists: 3797e2bbb61188fa83d63a73dea9d716b7b47ab6
2019-05-11 11:51:41,992 [INFO ] main com.amazonaws.ml.mms.wlm.ModelManager - Model batchshufflenet loaded.
2019-05-11 11:51:41,992 [DEBUG] main com.amazonaws.ml.mms.wlm.ModelManager - updateModel: batchshufflenet, count: 2
2019-05-11 11:51:42,012 [INFO ] main com.amazonaws.ml.mms.ModelServer - Initialize Inference server with: EpollServerSocketChannel.
2019-05-11 11:51:42,073 [INFO ] main com.amazonaws.ml.mms.ModelServer - Inference API bind to: http://<IP_ADDRESS>:8080
2019-05-11 11:51:42,073 [INFO ] main com.amazonaws.ml.mms.ModelServer - Initialize Management server with: EpollServerSocketChannel.
2019-05-11 11:51:42,074 [INFO ] main com.amazonaws.ml.mms.ModelServer - Management API bind to: http://<IP_ADDRESS>:8081
Model server started.
2019-05-11 11:51:42,076 [WARN ] pool-2-thread-1 com.amazonaws.ml.mms.metrics.MetricCollector - worker pid is not available yet.
2019-05-11 11:51:42,111 [INFO ] W-9000-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Listening on port: /tmp/.mms.sock.9000
2019-05-11 11:51:42,111 [INFO ] W-9000-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - [PID]16750
2019-05-11 11:51:42,111 [INFO ] W-9000-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - MXNet worker started.
2019-05-11 11:51:42,111 [INFO ] W-9000-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Python runtime: 3.6.8
2019-05-11 11:51:42,111 [INFO ] W-9001-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Listening on port: /tmp/.mms.sock.9001
2019-05-11 11:51:42,112 [INFO ] W-9001-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - [PID]16751
2019-05-11 11:51:42,112 [INFO ] W-9001-batchshufflenet-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - MXNet worker started.
2019-05-11 11:51:42,112 [DEBUG] W-9000-batchshufflenet com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-batchshufflenet State change null -> WORKER_STARTED
2019-05-11 11:51:42,112 [DEBUG] W-9001-batchshufflenet com.amazonaws.ml.mms.wlm.WorkerThread - W-9001-batchshufflenet State change null -> WORKER_STARTED

validate config file
curl localhost:8081/models/batchshufflenet

output
{
  "modelName": "batchshufflenet",
  "modelUrl": "batchshufflenet.mar",
  "runtime": "python",
  "minWorkers": 2,
  "maxWorkers": 2,
  "batchSize": 1,
  "maxBatchDelay": 100,
  "loadedAtStartup": true,
  "workers": [
    {
      "id": "9000",
      "startTime": "2019-05-11T11:51:42.006Z",
      "status": "READY",
      "gpu": true,
      "memoryUsage": 0
    },
    {
      "id": "9001",
      "startTime": "2019-05-11T11:51:42.010Z",
      "status": "READY",
      "gpu": true,
      "memoryUsage": 0
    }
  ]
}

log personal thoughts
hmm. that's weird batch_size should be set at 8 and max_batch_delay at 50
attempt to change settings via PUT
curl -X PUT "localhost:8081/models/batchshufflenet?batch_size=8&job_queue_size=1000&max_batch_delay=50&number_of_netty_threads=32"

output
{
  "status": "Processing worker updates..."
}

check logs
2019-05-11 11:52:14,681 [INFO ] epollEventLoopGroup-3-1 ACCESS_LOG - /<IP_ADDRESS>:60044 "GET /models/batchshufflenet HTTP/1.1" 200 10
2019-05-11 11:52:14,681 [INFO ] epollEventLoopGroup-3-1 MMS_METRICS - Requests2XX.Count:1|#Level:Host|#hostname:mkrzus,timestamp:null
2019-05-11 11:52:42,167 [INFO ] pool-2-thread-1 MMS_METRICS - CPUUtilization.Percent:0.0|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,167 [INFO ] pool-2-thread-1 MMS_METRICS - DiskAvailable.Gigabytes:40.7806510925293|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,168 [INFO ] pool-2-thread-1 MMS_METRICS - DiskUsage.Gigabytes:374.4116554260254|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,168 [INFO ] pool-2-thread-1 MMS_METRICS - DiskUtilization.Percent:90.2|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,168 [INFO ] pool-2-thread-1 MMS_METRICS - MemoryAvailable.Megabytes:8703.640625|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,168 [INFO ] pool-2-thread-1 MMS_METRICS - MemoryUsed.Megabytes:22426.27734375|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:42,168 [INFO ] pool-2-thread-1 MMS_METRICS - MemoryUtilization.Percent:72.9|#Level:Host|#hostname:mkrzus,timestamp:1557593562
2019-05-11 11:52:44,556 [DEBUG] epollEventLoopGroup-3-2 com.amazonaws.ml.mms.wlm.ModelManager - updateModel: batchshufflenet, count: 1
2019-05-11 11:52:44,557 [DEBUG] epollEventLoopGroup-3-2 com.amazonaws.ml.mms.wlm.WorkerThread - W-9001-batchshufflenet State change WORKER_MODEL_LOADED -> WORKER_SCALED_DOWN
2019-05-11 11:52:44,558 [DEBUG] W-9001-batchshufflenet com.amazonaws.ml.mms.wlm.WorkerThread - Shutting down the thread .. Scaling down.
2019-05-11 11:52:44,558 [DEBUG] W-9001-batchshufflenet com.amazonaws.ml.mms.wlm.WorkerThread - W-9001-batchshufflenet State change WORKER_SCALED_DOWN -> WORKER_STOPPED
2019-05-11 11:52:44,558 [INFO ] epollEventLoopGroup-4-2 com.amazonaws.ml.mms.wlm.WorkerThread - 9001 Worker disconnected. WORKER_SCALED_DOWN
2019-05-11 11:52:44,558 [DEBUG] W-9001-batchshufflenet com.amazonaws.ml.mms.wlm.WorkerThread - Worker terminated due to scale-down call.
2019-05-11 11:52:44,559 [INFO ] epollEventLoopGroup-3-2 ACCESS_LOG - /<IP_ADDRESS>:60046 "PUT /models/batchshufflenet?batch_size=8&job_queue_size=1000&max_batch_delay=50&number_of_netty_threads=32 HTTP/1.1" 202 3
2019-05-11 11:52:44,559 [INFO ] epollEventLoopGroup-3-2 MMS_METRICS - Requests2XX.Count:1|#Level:Host|#hostname:mkrzus,timestamp:null

weird. why would it scale down?
curl localhost:8081/models/batchshufflenet

output
{
  "modelName": "batchshufflenet",
  "modelUrl": "batchshufflenet.mar",
  "runtime": "python",
  "minWorkers": 1,
  "maxWorkers": 1,
  "batchSize": 1,
  "maxBatchDelay": 100,
  "loadedAtStartup": true,
  "workers": [
    {
      "id": "9000",
      "startTime": "2019-05-11T11:51:42.006Z",
      "status": "READY",
      "gpu": true,
      "memoryUsage":<PHONE_NUMBER>
    }
  ]
}

Hacky work-around
move file so it's not auto-registered
mv models/batchshufflenet.mar /other-directory

start model server
mxnet-model-server --start

mv other-directory/batchshufflenet.mar models/batchshufflenet.mar

call api and register model:
 curl -X POST "localhost:8081/models?url=batchshufflenet.mar&default_workers_per_model=2&job_queue_size=1000&async_logging=true&number_of_netty_threads=32&batch_size=8&max_batch_delay=60"

output
{
  "status": "Model \"batchshufflenet\" registered"
}

quick verification that my config was accepted:
curl localhost:8081/models/batchshufflenet

output:
{
  "modelName": "batchshufflenet",
  "modelUrl": "batchshufflenet.mar",
  "runtime": "python",
  "minWorkers": 0,
  "maxWorkers": 0,
  "batchSize": 8,
  "maxBatchDelay": 60,
  "loadedAtStartup": false,
  "workers": []
}

still weird that it didn't listen to the other commands, but at least the batch_size changed.
I guess I have to redo this?
curl -X PUT "localhost:8081/models/batchshufflenet?&default_workers_per_model=2&job_queue_size=1000&async_logging=true&number_of_netty_threads=32&batch_size=8&max_batch_delay=60"

curl localhost:8081/models/batchshufflenet

look at output
{
  "modelName": "batchshufflenet",
  "modelUrl": "batchshufflenet.mar",
  "runtime": "python",
  "minWorkers": 1,
  "maxWorkers": 1,
  "batchSize": 8,
  "maxBatchDelay": 30,
  "loadedAtStartup": false,
  "workers": [
    {
      "id": "9000",
      "startTime": "2019-05-11T11:10:49.776Z",
      "status": "READY",
      "gpu": true,
      "memoryUsage":<PHONE_NUMBER>
    }
  ]
}

This works, but seems such a hack that could be cleaned up, no?

@KayneWest : The question is very detailed, thanks for the detail. Looking at the question I feel, it may be better to interact on MMS Slack channel for quicker solution. Some things that you have to note are:

Not all config.properties options are a part of Management API. Also, there is a stark difference between "POST" and "PUT" method options. For a list of management API options (POST /models and PUT /models) please refer this document.
Currently the only way the batch configuration comes in is through "POST /models" API, which is an management API. As you have seen in #770, we are working on making this configuration come through MANIFEST.json in the .mar file. So, you wouldn't be able to configure these parameters through config.properties.

I agree, your solution/work around is hacky and there is discussion in progress to make these configurations come through other means.


Transfer ownership for package "ABBA"

Hi, I uploaded the package ABBA under a PyPI account Steve.Howard registered to my email at my previous company. I have long since lost access to that email account. I do have control of the GitHub repository under this GitHub account (gostevehoward). Can you transfer ownership of the "ABBA" package to my new PyPI username gostevehoward? A user posted a message to our repo about Python 3 incompatibility and I wanted to put an updated version on PyPI. Let me know if I can help, and sorry for the inconvenience.

Hi @gostevehoward, I will now contact the administators to transfer the project to your new PyPI user.
Btw, best project name ever 😄

Thank you so much for your help @yeraydiazdiaz !

Transfer complete.

Thank you @ewdurbin !


Notifications cannot run when packaged with electron-builder

This could be due to a different issue, but this is my best deduction. The windows simply do not show up, but I can tell they are trying to because I lose focus on the window when they attempt to create.
I have set up an example here: https://github.com/Slapbox/electron-notification-demo
In App\Components\Home.js I generate a notification at startup and then every 25 seconds.
ipcRenderer.send('reminders');

setInterval(function() {
  console.log("Attempting to create notification");
  ipcRenderer.send('reminders');
}, 25000)

in App\Main.development.js
  ipcMain.on('reminders', (event, arg) => {
    console.log("Attempting to create notification");
    notifier.notify("Test");
  });

Run in development with: npm run dev and you can see they run fine.
Run the exe release\win-unpacked\ElectronReact.exe to run a packaged version. On right click you can inspect element to view the developer tools, but I don't know of any way to debug the main process unfortunately.
Any ideas what may cause this? This is an excellent package. It's a real bummer that it's not working so far in a production build. Thanks for any insight you can provide.

I have no idea what could be causing this, thank you for reporting the issue!

Can you explain in 2-3 sentences how/where in the package notifications are generated? I will try to investigate further.

@Slapbox we create new browser windows in this file:
https://github.com/blainesch/electron-notifications/blob/master/lib/notifier.js

The newest version with Electron 1.6.1 and Electron-builder 12.3.1 does create windows. Huzzah!
Unfortunately they're empty white windows. I'm guessing that some required file is not being loaded.

Okay finally got an error message:
Not allowed to load local resource: file:///C:/Projects/MyApp/release/win-unpacked/resources/app.asar/assets/notification.html
Extracting the app.asar shows that this file is not being included by electron-builder so I will have to determine how to get it and the corresponding CSS file in the same directory included.

I have literally no idea how to remedy this..
I think that the HtmlWebpackPlugin is needed to import the notification.html but I can't find any working configuration, and if this is the right path, it would only be a first step in resolving the issue most likely.

@Slapbox do you have a repo case online I can download?
We don't currently compile with webpack, but we could try and compile it to include the html file inline. This could help, but we might have to change how this works.
It could also be useful to try and list all the files necessary in the package.json?
https://docs.npmjs.com/files/package.json#files

I did try a few things to bring the files in in the package.json and in my webpack.config files, but no luck. I have no doubt there is a way to do it, but I don't know what it is and help material/questions on this particular type of issue seem to be nearly impossible to find, though perhaps I simply don't know what to search for.
I've put together a repo to demonstrate the issue. You can view the repo here: https://github.com/Slapbox/electron-notification-demo
You can download just the contents of https://github.com/Slapbox/electron-notification-demo/tree/master/release/win-unpacked and run ElectronReact.exe. The application will create a notification window on startup. Developer tools should be available for both the main application and for the Electron-Notifications window that is created.
The notification is generated in the Home.js file around line 9. It should last for an hour before closing.
If you need to generate another notification window you can do so with notifier('reminders'); in the console.
Thanks very much for taking a look @blainesch!

React-Electron-Boilerplate works just fine with this repo. You must add the dependency to your SECOND package.json, located within the app folder.


The operation failed for an operation-specific reason

I Had the same issue with WEBSD when i switched to canary WEBsd Worked but WEBllm still gives the error frequently(Image attached)

While the smaller model (RedPajama-INCITE-Chat-3B-v1-q4f32_0) has been working smoothly for me, I'm observing similar errors as reported for Llama-2-7b-chat-hf-q4f32_1. I also tried vicuna-v1-7b-q4f32_0 which worked fine for a message or two until I opened another browser tab (the screen went black and then got "GPU connection lost", "OperationError: The operation failed for an operation-specific reason" and "DOMException: Device is lost") which makes me think that maybe my device cannot handle the needed memory for WebGPU that these bigger models demand. From some initial research about the errors, I also found comments that the browser throws them when it cannot allocate enough memory to WebGPU. Could this be the reason? Do you know of any potential way this could be solved?


Update TaskRun Step States After Cancellation or Timeout

Closes https://github.com/tektoncd/cli/issues/1095
Changes
In the event a TaskRun is timed out or cancelled, pipelines currently leaves the state of steps as Running or PodInitializing depending on how far the TaskRun has proceeded. This pull request adds a feature to update the status of steps to TaskRunTimeout or TaskRunCancelled. This will help with properly reporting step statuses through tkn to end users to avoid confusion.
The current approach only updates a step status if the step state is Running or Waiting. If a step has already completed, the status will be preserved.
I am open to suggestions on a different status that can be returned for steps other than the TaskRun reason.
Submitter Checklist

[x] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Update step statuses on TaskRun in event of cancellation or timeout

/kind feature

@pritidesai Looking into this a bit further, I think the status needs some time before it updates. I noticed the same issue you pointed out, but it eventually does update the statuses correctly:
$ tkn pr desc --last

Name:        pipelinerun-with-timeout
Namespace:   default
Timeout:     3s
Labels:
 tekton.dev/pipeline=pipelinerun-with-timeout

🌡  Status

STARTED         DURATION    STATUS
9 minutes ago   3 seconds   Failed(PipelineRunTimeout)

💌 Message

PipelineRun "pipelinerun-with-timeout" failed to finish within "3s" (TaskRun "pipelinerun-with-timeout-echo-good-morning-hkvjs" failed to finish within "30s")

📦 Resources

 No resources

⚓ Params

 No params

🗂  Taskruns

 NAME                                                 TASK NAME           STARTED         DURATION     STATUS
 ∙ pipelinerun-with-timeout-echo-good-morning-hkvjs   echo-good-morning   9 minutes ago   30 seconds   Failed(TaskRunTimeout)

$ tkn tr desc --last

Name:        pipelinerun-with-timeout-echo-good-morning-hkvjs
Namespace:   default
Timeout:     30s
Labels:
 app.kubernetes.io/managed-by=tekton-pipelines
 tekton.dev/pipeline=pipelinerun-with-timeout
 tekton.dev/pipelineRun=pipelinerun-with-timeout
 tekton.dev/pipelineTask=echo-good-morning

🌡  Status

STARTED          DURATION     STATUS
10 minutes ago   30 seconds   Failed(TaskRunTimeout)

Message

TaskRun "pipelinerun-with-timeout-echo-good-morning-hkvjs" failed to finish within "30s"

📨 Input Resources

 No input resources

📡 Output Resources

 No output resources

⚓ Params

 No params

🦶 Steps

 NAME     STATUS
 ∙ echo   TaskRunTimeout

🚗 Sidecars

No sidecars

Looking further into the issue, this looks like a case where the TaskRun is actually still Running and is not timed out despite the PipelineRun timeout. This is occurring in v0.15.2 with this same PipelineRun, so it might be related to issues around timeouts with pipelines. But I do think this is not related to the changes here.

Sounds good thanks @danielhelfand.
@bobcatfish was looking into timeout and we have an issue for it #3038.

/cc @vdemeester @bobcatfish @afrittoli

/lgtm


Strange issue with Fabric Copper and WTHIT

I've been running tests all morning trying to narrow down what is causing the error in the image.  It started after I put the new version of WTHIT in last night.

I have a very small mod pack of only 25 mods.  Have gone through adding each back into a test pack one by one.  And every time I add in your copper mod and WTHIT together, this error comes up.  Either one by themselves works just fine, but together there is something not working right.
This is the most recent log file I've got as well with the two in there, I can't seem to figure out where its going wrong.  Was wondering what it is.
latest.log
It doesn't give the error in creative mode, but seems to only happen in survival mode.
And this is the log file with only your copper mod and WTHIT.
latest.log
I'm stumped

Strange indeed! I will take a look, once I have the time. Thanks for reporting!

I took a first look, might be a compatibility issue

Hey no worries, I've tested it with your food mod only so far (as in with the food but not the copper) and it worked fine, no idea about any of your other ones, since i've not tried them all together.  but so far it just looks like something is odd between the copper and WTHIT pairing.
As it is your copper is the only one i've found updated and usable for 1.21.4 at this time, and was enjoying it a lot tell we added WTHIT last night.

I'm glad, you enjoyed it! It's most likely only an issue with Nemo's Copper, I'll take a look to make it compatible :D

Oh thank you very much, very apricated.  Copper tools/armor/weapons is one of my fav style of mods to be honest.

Oh nice :D
If you have any suggestion for copper stuff, feel free to share! (I still have many things in mind, which I'll add in the future

Exactly what's already planned :D

Tested it and it works. Will update it soon

Update 1.1.1 should fix it, please confirm and let me know

Sweet, tested it both with just WTHIT, and with all the other mods I was using.  Both came up just fine.

Great, will close this tickte then. Enjoy!


Error: Netlify CLI has terminated unexpectedly, when running netlify dev, Angular

Describe the bug
›   Error: Netlify CLI has terminated unexpectedly
This is a problem with the Netlify CLI, not with your application.
If you recently updated the CLI, consider reverting to an older version by running:
npm install -g netlify-cli@VERSION
You can use any version from https://ntl.fyi/cli-versions.
Please report this problem at https://ntl.fyi/cli-error including the error details below.
Request from ::ffff:<IP_ADDRESS>: GET /.netlify/functions/points
Response with status 200 in 560 ms.
TypeError: res.writeHead is not a function
at ProxyServer. (file:///Users/anvlkv/.npm-global/lib/node_modules/netlify-cli/src/utils/proxy.mjs:410:9)
at ProxyServer.emit (/Users/anvlkv/.npm-global/lib/node_modules/netlify-cli/node_modules/eventemitter3/index.js:204:33)
at Socket.onOutgoingError (/Users/anvlkv/.npm-global/lib/node_modules/netlify-cli/node_modules/http-proxy/lib/http-proxy/passes/ws-incoming.js:157:16)
at Socket.emit (node:events:529:35)
at Socket.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
System:
OS: macOS 12.7
CPU: (4) x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.8.1 - /usr/local/bin/npm
Browsers:
Chrome: 116.0.5845.187
Firefox: 117.0.1
Safari: 16.6.1
npmGlobalPackages:
netlify-cli: 16.4.2
Steps to reproduce
Not sure, I think this may be happening when saving multiple files one by one.
The command works, but fails regularly
Configuration
[functions]
directory = "api"
Environment
System:
OS: macOS 12.7
CPU: (4) x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
Memory: 884.27 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.8.1 - /usr/local/bin/npm
npmGlobalPackages:
netlify-cli: 16.4.2

And when saving same file multiple times quickly...


Fix crashed prometheus on a few clusters

Context
In https://github.com/2i2c-org/infrastructure/actions/runs/2501414407, we see the support chart has failed in two clusters - pangeo-hubs and meom-ige. Investigating, it's because the prometheus-server is crashing, possibly from out of memory errors.
Proposal
We should set better memory limits, or put other mechanisms in place to bring prometheus back up
Updates and actions
No response

I believe MEOM-IGE was fixed during the course of the below incident?

https://github.com/2i2c-org/infrastructure/issues/1423

I addressed the pangeo-hubs cluster here

https://github.com/2i2c-org/infrastructure/pull/1447

Both clusters were addressed, so closing here.
Thanks, @sgibson91!


Add test case for tracking memory layout of syntax node data

This is useful to estimate how much memory is required.

@swift-ci Please test

@swift-ci Please test


make it easier to set up secrets

creating secrets for the oCIS chart is a manual process currently. We should aim at making this easier.

Generating them from Helm, reading the old value via lookup, is limited. It will only work for what you can generate from Helm, e.g. random strings, not keys. In addition it won't work when using helm template because lookup will return null.
Another option is to create a Job that talks to the Kubernetes API via a service account to check the secret and possibly generate them. This will work with helm template and allows you to run any code you want (in the Job's container). You can also make it a post-install,post-upgrade chart hook to have it run first and re-run on updates.

Either way I think blaming Helm in your docs is inappropriate and should be removed. You are using Helm incorrectly and blaming them, and it's a bad look.
https://doc.owncloud.com/ocis/next/deployment/container/orchestration/orchestration.html

Helm does not support one-off generation of secrets out of the box. Certificates are also required which should expire and therefore need a certificate rotation from time to time, which is also not supported by Helm

Helm does not support one-off generation of configuration out of the box

Certificates are also required which should have an expiration date and therefore need a certificate rotation from time to time, which is also not supported by Helm

Certificates are also required which should expire and therefore need a certificate rotation from time to time, which is also not supported by Helm

All of this is supported by Helm. You just haven't written the Jobs and CronJobs that are the way to do it and works for everyone else.

If you don't actually rotate certificates, it looks like Helm might have all you need built-in , e.g. with genCA/genSelfSignedCert/genSignedCert
Here are a few I could find, I hope that helps:

GitLab's shared secrets: job template, script template (it's a shell script that calls kubectl and openssl), rbac
GitLab's nginx secrets: job template, role, rolebinding
Bitnami's Contour chart: job template, rbac (Bitnami seems to be using mostly lookup and initContainers)


Feature Request: Prominently Indicate When Provision Status Is Not Provisioned

Is your feature request related to a problem? Please describe.
When my revision does not get provisioned successfully, it is not immediately apparent, especially to unfamiliar users.
Describe the solution you'd like.
I would like to see a prominent banner or indicator, perhaps above the blade content. This indicator should have:

at least a message about the failed status, and/or
better, a link to Log Analytics and a suitable query (narrow to container name, etc.), if the Log Analytics Workspace was created with the Container App Environment, and/or
ideally analyze the issue (hello, OpenAI) and provide means of resolution

Describe alternatives you've considered.
See above. =)
Additional context.
N/A

Hi @simonkurtz-MSFT thanks for making this request! I'm working on a feature to clarify provisioning and status and include some running statuses. It looks like it will be available by June.

That's super, @SophCarp! Thank you. I love seeing ACA get better and better.

We've added a running status now also we're looking to make additional changes soonish.


Plotted region does not match bbox definition in risk assessment example notebook

Another problem I faced is with the risk script 'EXTREME_PRECIPITATION_Risk_Assessment_examples.ipynb'. At begin, I put my bbox (region) and in final all plots are from Catalonia region. Now I have all the necessary input data in this script because I was able to download and clip data on my region from previous hazard script.
Please, after solving with cdsapi, look at the risk script, change the bbox (region) and tell me what you get!
Thank you!
Originally posted by @flor187 in https://github.com/CLIMAAX/HEAVY_RAINFALL/issues/5#issuecomment-2527189392

Hello @flor187,
thanks for reporting this problem! I can confirm that I see the same behaviour in the workflow: changing the coordinates for the bounding box (variable bbox) still results in a plot for the Catalonia region in step 6 of the notebook.
The region that is plotted is determined from the geographic information in the RP_CAT_threshold_100mm.tiff file, which in the example is created for the Catalonia region - independent of the choice of the bounding box at the start. To change the plots, you'll have to provide a custom file with return periods for the critical threshold(s) you are interested in. The example notebook shows how this file was created for the Catalonia region based on data from their local meteorological service. If you have similar input data for your region of interest, you can use the notebook to create your own return periods file. In the meantime, you could, e.g., consider providing a file with a constant value across the entire region for testing purposes until you are able to refine the values for an improved analysis.
I'll have another look if and how we could improve the workflow in this aspect (e.g., by checking overlap of the bounding box and provided critical thresholds/return periods file and showing a warning if they do not match).

Thank you!


use PKCS#7 to avoid that zero data are unrevertable

@xmh0511 Hi, Nice work! Thanks for your taking time and making it more integrative as a library. Surely this would break the Rufendec project a little, but I can adjust that. I have reviewed your changes on a surface level. Some changes were cosmetic (possibly could have occurred due to your code editor formatting, and some were "Nice to Have" things like the String to &str, and use of Generic From Traits, but I liked how you took your time to fix the core problem with PKCS padding
I won't go through each and every piece but I will test the overall build and get back to you. Thanks a again.

@omkarium Hi, I have an idea for your library. Since its version is 0.2.0, it has time to refine the design, in the current, the data is saved in the structure, however, it's not necessary, we just need to design a struct Aes256Cryptor to save the key, and that struct has encrypt and decrypt methods, that's is sufficient, and under this design, we can send the cryptor to anywhere we want and the use it do en/decrypt any data.

@omkarium  I have created the new PR to refine the code, please see that PR, if you would appreciate the new version, then publish the latest one after merging the PR. Thanks.


April 21 Patch links not working

I am following
https://github.com/Xilinx/Vitis-AI/blob/master/docs/quick-start/install/Vitis AI 1.3.2 April 2021 Patch.md
to download the patch and links are not live neither returns any error.
Please advise?

Hi @FarhanAhmad4473
I can download the patches. Could you try to use another browser to download them?
Or you can use wget to download them, such as:
wget https://www.xilinx.com/bin/public/openDownload?filename=xnnc-1.3.2-py37_48.tar.bz2 -O xnnc-1.3.2-py37_48.tar.bz2

Hi @FarhanAhmad4473
Have you solved this issue? If you still can't download the patch, please let me know.
If it has been solved, please kindly close this issue. Thank you.