Execution failed for task ':shared_preferences_android:compileDebugJavaWithJavac'.

Steps to reproduce
I am running on Mac mini
OS version: 15.0.1
Android Studio (version 2024.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
Actual results
Not able to build. The error is occurred !
Logs

Logs
Execution failed for task ':shared_preferences_android:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':shared_preferences_android:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: /Users/sicunetappdeveloper/Library/Android/sdk/platforms/android-34/core-for-system-modules.jar.
         > Error while executing process /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/jlink with arguments {--module-path /Users/sicunetappdeveloper/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/temp/jmod --add-modules java.base --output /Users/sicunetappdeveloper/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/jdkImage --disable-plugin system-modules}

Flutter Doctor output

Doctor output

[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-arm64, locale
    en-US)
    • Flutter version 3.24.3 on channel stable at
      /Users/sicunetappdeveloper/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (4 weeks ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/sicunetappdeveloper/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)

[✓] Connected device (4 available)
    • Android SDK built for arm64 (mobile) • emulator-5554         •
      android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)                      • macos                 •
      darwin-arm64   • macOS 15.0.1 24A348 darwin-arm64
    • Mac Designed for iPad (desktop)      • mac-designed-for-ipad • darwin
      • macOS 15.0.1 24A348 darwin-arm64
    • Chrome (web)                         • chrome                •
      web-javascript • Google Chrome 129.0.6668.90

[✓] Network resources
    • All expected network resources are available.

• No issues found!

I am having similar issues.
At first I receive gradle error even though i didn't touch any code,
`* What went wrong:
Execution failed for task ':gradle:compileGroovy'.

BUG! exception in phase 'semantic analysis' in source unit '/Users/hammizzang/Developer/development/flutter/packages/flutter_tools/gradle/src/main/groovy/app_plugin_loader.groovy' Unsupported class file major version 65

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 3s
┌─ Flutter Fix ───────────────────────────────────────────────────────────────────────────────────┐
│ [!] Your project's Gradle version is incompatible with the Java version that Flutter is using   │
│ for Gradle.                                                                                │
│                                                                                │
│ If you recently upgraded Android Studio, consult the migration guide at                         │
│ https://flutter.dev/to/to/java-gradle-incompatibility.                                          │
│                                                                                │
│ Otherwise, to fix this issue, first, check the Java version used by Flutter by running flutter │ │ doctor --verbose.                                                                              │
│                                                                                │
│ Then, update the Gradle version specified in                                                    │
│ /Users/myUserName/StudioProjects/myAppName/android/gradle/wrapper/gradle-wrapper.properties to  │
│ be compatible with that Java version. See the link below for more information on compatible     │
│ Java/Gradle versions:                                                                           │
│ https://docs.gradle.org/current/userguide/compatibility.html#java                               │
│                                                                                │
│                                                                                │
└─────────────────────────────────────────────────────────────────────────────────────────────────┘
Error: Gradle task assembleProdDebug failed with exit code 1
`
Once I upgrade my gradle version to match my java version which is 21(gradle version above 8.5),
I get the same issue as shimulxx but with different plugin and unable to build.

Yes, After downgrade jdk to 17 it started to work again. jdk 21 is creating the problem.

jdk 21 is creating the problem.

@shimulxx I think since you are on Android Studio (version 2024.2) which ships with Java sdk 21 could be the factor as why you are seeing this error.
Can you provide android/app/build.gradle, android/gradle/wrapper/gradle-wrapper.properties and android/settings.gradle.

@darshankawar  android/app/build.gradle
plugins {
id "com.android.application"
// START: FlutterFire Configuration
id 'com.google.gms.google-services'
// END: FlutterFire Configuration
id "kotlin-android"
// The Flutter Gradle Plugin must be applied after the Android and Kotlin Gradle plugins.
id "dev.flutter.flutter-gradle-plugin"
}
def localProperties = new Properties()
def localPropertiesFile = rootProject.file("local.properties")
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader("UTF-8") { reader ->
localProperties.load(reader)
}
}
def flutterVersionCode = localProperties.getProperty("flutter.versionCode")
if (flutterVersionCode == null) {
flutterVersionCode = "1"
}
def flutterVersionName = localProperties.getProperty("flutter.versionName")
if (flutterVersionName == null) {
flutterVersionName = "1.0"
}
android {
namespace = "com.example.shorts"
compileSdk = flutter.compileSdkVersion
ndkVersion = flutter.ndkVersion
compileOptions {
    sourceCompatibility = JavaVersion.VERSION_1_8
    targetCompatibility = JavaVersion.VERSION_1_8

}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId = "com.example.shorts"
    // You can update the following values to match your application needs.
    // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
    minSdk =  24
    targetSdk = flutter.targetSdkVersion
    versionCode = flutterVersionCode.toInteger()
    versionName = flutterVersionName
    multiDexEnabled true
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig = signingConfigs.debug
    }
}

}
flutter {
source = "../.."
}
my android/gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-8.10-all.zip
my settings.gradle
pluginManagement {
def flutterSdkPath = {
def properties = new Properties()
file("local.properties").withInputStream { properties.load(it) }
def flutterSdkPath = properties.getProperty("flutter.sdk")
assert flutterSdkPath != null, "flutter.sdk not set in local.properties"
return flutterSdkPath
}()
includeBuild("$flutterSdkPath/packages/flutter_tools/gradle")

repositories {
    google()
    mavenCentral()
    maven { url "https://maven.google.com/" }
    maven { url "https://plugins.gradle.org/m2/" }
    maven { url 'https://jitpack.io' }
    maven { url 'https://maven.otaliastudios.com/releases' }
    gradlePluginPortal()
}

}
plugins {
id "dev.flutter.flutter-plugin-loader" version "1.0.0"
id "com.android.application" version "7.3.0" apply false
// START: FlutterFire Configuration
id "com.google.gms.google-services" version "4.3.15" apply false
// END: FlutterFire Configuration
id "org.jetbrains.kotlin.android" version "1.7.10" apply false
}
include ":app"

download jdk-11 and install it
then you should see jdk-11 in your C:\Program Files\Java  directory
then in the flutter project tirminal run this command flutter config --jdk-dir "C:\Program Files\Java\jdk-11"
This command tells Flutter to use the specified JDK directory instead of relying on the JAVA_HOME environment variable.

For what it's worth, to help others unable to build now, these settings seem to work, at least for now:

JDK 11 from https://jdk.java.net/java-se-ri/11-MR3, flutter config --jdk-dir "where-you-copied-the-jdk-eg. c:\Program Files\Java\jdk-<IP_ADDRESS>" (no need to install, just unzip)

id "org.jetbrains.kotlin.android" version "1.9.22" apply false in settings.gradle

distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-all.zip in gradle-wrapper.properties

in app/build.gradle:
compileOptions {
sourceCompatibility JavaVersion.VERSION_17
targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
jvmTarget = "1.8"
}

and
dependencies {
  implementation "androidx.appcompat:appcompat:1.6.1"
  ...
}

Same issue here
https://github.com/flutter/flutter/issues/156337
Happened after latest android studio update.

#156337

Even if Android Studio ships with JDK21, I get the same issue using Terminal on the Mac. Intellij products will use embeded build tools only when you invoke them through the GUI.
https://github.com/flutter/flutter/issues/156337

I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This is settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this is gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work.)

I am getting the same issue :
errror:
> flutter run
Launching lib\main.dart on SM A037F in debug mode...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared_preferences_android:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':shared_preferences_android:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: C:\Users\sdvs1\AppData\Local\Android\sdk\platforms\android-34\core-for-system-modules.jar.
         > Error while executing process C:\Program Files\Android\Android Studio_2024_2_1_9\jbr\bin\jlink.exe with arguments {--module-path C:\Users\sdvs1\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\temp\jmod --add-modules java.base --output C:\Users\sdvs1\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\jdkImage --disable-plugin system-modules}

* 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 3s
Running Gradle task 'assembleDebug'...                              4.5s
Error: Gradle task assembleDebug failed with exit code 1

android/build.gradle:
buildscript {
    ext.kotlin_version = '1.7.10'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.3.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

android/app/build.gradle:
plugins {
    id 'com.android.application'
    id 'kotlin-android'
    id 'dev.flutter.flutter-gradle-plugin'
}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new FileNotFoundException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

android {
    namespace "com.example.apc_bday_wisher"
    compileSdkVersion flutter.compileSdkVersion
    ndkVersion flutter.ndkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = '1.8'
    }

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    defaultConfig {
        applicationId "com.example.apc_bday_wisher"
        minSdkVersion flutter.minSdkVersion
        targetSdkVersion flutter.targetSdkVersion
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

    buildTypes {
        release {
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

Can anyone give solution for this ?

Please check this issue and description as how to fix using latest AS version. I think it is similar to what is provided by @deakjahn here.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work. I stopped at the first combination that worked.)

Thank you very much, it works now!!!

I am getting the same issue :
errror:
> flutter run
Launching lib\main.dart on SM A037F in debug mode...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared_preferences_android:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':shared_preferences_android:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: C:\Users\sdvs1\AppData\Local\Android\sdk\platforms\android-34\core-for-system-modules.jar.
         > Error while executing process C:\Program Files\Android\Android Studio_2024_2_1_9\jbr\bin\jlink.exe with arguments {--module-path C:\Users\sdvs1\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\temp\jmod --add-modules java.base --output C:\Users\sdvs1\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\jdkImage --disable-plugin system-modules}

* 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 3s
Running Gradle task 'assembleDebug'...                              4.5s
Error: Gradle task assembleDebug failed with exit code 1

android/build.gradle:
buildscript {
    ext.kotlin_version = '1.7.10'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.3.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

android/app/build.gradle:
plugins {
    id 'com.android.application'
    id 'kotlin-android'
    id 'dev.flutter.flutter-gradle-plugin'
}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new FileNotFoundException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

android {
    namespace "com.example.apc_bday_wisher"
    compileSdkVersion flutter.compileSdkVersion
    ndkVersion flutter.ndkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = '1.8'
    }

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    defaultConfig {
        applicationId "com.example.apc_bday_wisher"
        minSdkVersion flutter.minSdkVersion
        targetSdkVersion flutter.targetSdkVersion
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

    buildTypes {
        release {
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

Can anyone give solution for this ?

Hi  can you resolve it?

@zxj1989 Both my reply and the one darshankawar mentioned describes the solution. (And it would be good to get rid of the buildscript approach in yours, see https://docs.flutter.dev/release/breaking-changes/flutter-gradle-plugin-apply).

download jdk-11 and install it then you should see jdk-11 in your C:\Program Files\Java directory then in the flutter project tirminal run this command flutter config --jdk-dir "C:\Program Files\Java\jdk-11" This command tells Flutter to use the specified JDK directory instead of relying on the JAVA_HOME environment variable.

This worked for me

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work. I stopped at the first combination that worked.)

This works, plus, change ndkVersion to 25.1 as the compiler warning indicates:
android {
namespace = "com.example.untitled2"
compileSdk = flutter.compileSdkVersion
ndkVersion = "25.1.8937393"
}

Tried @deakjahn 's solution, now I don't get any error logs its just:
Running Gradle task 'assembleRelease'...                           897ms
Gradle task assembleRelease failed with exit code 1

@Hugfin Yep, that's true, I forgot to add that. I'll edit the original post because, as I can see, it got quite a few links from other issues.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

Bro thank you so much...been working on it for 2 days!!

download jdk-11 and install it then you should see jdk-11 in your C:\Program Files\Java directory then in the flutter project tirminal run this command flutter config --jdk-dir "C:\Program Files\Java\jdk-11" This command tells Flutter to use the specified JDK directory instead of relying on the JAVA_HOME environment variable.

Documents\MobileApps\FlutterApps\dbk_scan_app> --jdk-dir "C:\Program Files\Java\jdk-11"
At line:1 char:3

--jdk-dir "C:\Program Files\Java\jdk-11"
~
Missing expression after unary operator '--'.
At line:1 char:3
--jdk-dir "C:\Program Files\Java\jdk-11"

Unexpected token 'jdk-dir' in expression or statement.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpressionAfterOperator

@f22daniel flutter config --jdk-dir, you need a command, not just the parameter.
But, not just because I was the first to mention it here, you're probably better off using the current JDK bundled with AS instead of relying on an extra copy of an old one. :-)

I've faced similar issue and explained solution that worked for me in this post:
https://stackoverflow.com/a/79095064/7369590

@danagbemava-nc, it seems like this fix doesn't always work. In my case I still get the error:
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
warning: [options] source value 8 is obsolete and will be removed in a future release
warning: [options] target value 8 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
error: warnings found and -Werror specified
1 error
3 warnings

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':video_player_android:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --info option to get more log output.
> Run with --scan to get full insights.

BUILD FAILED in 17s
Running Gradle task 'assembleDebug'...                             17.4s
Error: Gradle task assembleDebug failed with exit code 1

So, I think, the issue wasn't solved, unfortunately.

The issue does seem to be solved, it is for many of us, but you didn't actually read your messages:
error: warnings found and -Werror specified
There are three warnings. They are benign, you can easily ignore them for now, the appropriate code will be removed or changed in the future for sure.
However, you have a -Werror switch in your build process that makes the compilation stop if a mere warning is encountered. Remove it, at least for now.

Remove it, at least for now.

I use the flutter run command. I didn't provide this option explicitly. Could you please tell me where I can disable this option?

It seems like I've found the missing piece: it is described in the "Changing the Java SDK" section here How to fix Android Compilation issues.
The steps that finally helped me:

Download and install JDK 17 from here;
Change the jdk path to the location of the installed JDK 17
flutter config --jdk-dir="/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home"
flutter doctor -v to check that there are no issues
flutter clean && flutter pub get  (this step might be unnecessary)
flutter run -d <your_android_device_id> → ✅

Yes, you can revert to JDK 17, but that remains an interim solution. However, the combination that I happened to suggest* allows you to move on to JDK 21, which is the current one, after all, and still be able to build. Right now, you get those warnings but as I said, you can safely ignore them for now. They will be fixed for sure in the future, in a coming Flutter version.

Actually, I simply visited various issues here in GitHub that referenced different fragments of the errors and messages we received, not just with this new LadyBug, but from earlier, and picked a version from here, another one from there, tried and tried lots of combinations, and when I finally got it working, I posted the results — nothing more spectacular than that. :-)

So, while you can use 17 or even 11 if nothing else helps. as the number of reactions show, many devs in the same shoes as you and me found the solution to be OK to move forward.

Routing to the Flutter Android team; this looks like a case where we need to have the flutter tool supplement the output with a clear and actionable error message (either by detecting this case in the output, or based on preconditions if we can concretely identify them—it looks like in this case maybe we can look at the Java version and the project's AGP version to predict issues?)
This is something we should consider for a hotfix once we have tooling to help, because the new AS release is causing a lot of people to end up on JDK 21 and hit this, and the raw error message is not helpful. We've seen a lot of dups of this, and the plugin developer community in general is seeing reports from confused clients as well (e.g., https://github.com/fluttercommunity/plus_plugins/issues/3303)

This worked for me:

Upgrade Gradle version:
To support JDK 21, you'll need at least Gradle 8.5. You can check the Java Compatibility for more details.
Just update your android/gradle/wrapper/gradle-wrapper.properties file like this:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-all.zip

Upgrade AGP version:
For more info, take a look at the AGP release notes.
Then, update your android/settings.gradle file like this:
plugins {
    id "com.android.application" version "8.3.0" apply false
}

Adapt to AGP 8.0:
You might need to make some changes for AGP 8.0. Check out the AGP 8.0 release notes or use the AGP Upgrade Assistant to help with the migration.

It looks likely that this is https://issuetracker.google.com/issues/294137077, which should be fixed in either AGP 8.2.1+, or 8.3+. Will test once I've downloaded the new Android Studio version, but the fact that @crasowas indicates and AGP upgrade fixed it for them also makes me think it is likely.

There should be clear messaging on how to handle this error on the master branch now. I'm going to file a cherry pick request to get it included in stable as well, but in the meantime the message is that upgrading to AGP 8.2.1 should fix this.

Had the exact same issue.
While trying to repair my android and build files with  |flutter create .| It gave me this message.
The configured version of Java detected may conflict with the Gradle version in your new Flutter app.

The configured version of Java detected may conflict with the Gradle version in your new Flutter app.
[RECOMMENDED] If so, to keep the default Gradle version 8.3, make
sure to download a compatible Java version
(Java 17 <= compatible Java version < Java 21).
You may configure this compatible Java version by running:
flutter config --jdk-dir=<JDK_DIRECTORY>
Note that this is a global configuration for Flutter.
Alternatively, to continue using your configured Java version, update the Gradle
version specified in the following file to a compatible Gradle version (compatible Gradle version
range: 8.4 - 8.7):
/home/USER/APP-DIRECTORY/android/gradle/wrapper/gradle-wrapper.properties
You may also update the Gradle version used by running
./gradlew wrapper --gradle-version=<COMPATIBLE_GRADLE_VERSION>.

Simply installing Java 17, which aligned with the gradle version and configuring flutter jdk-dir
flutter config --jdk-dir=<JAVA_DIRECTORY>
fixed the issue for me.

work

Had the exact same issue.
While trying to repair my android and build files with |flutter create .| It gave me this message. The configured version of Java detected may conflict with the Gradle version in your new Flutter app.

The configured version of Java detected may conflict with the Gradle version in your new Flutter app.
[RECOMMENDED] If so, to keep the default Gradle version 8.3, make
sure to download a compatible Java version
(Java 17 <= compatible Java version < Java 21).
You may configure this compatible Java version by running:
flutter config --jdk-dir=<JDK_DIRECTORY>
Note that this is a global configuration for Flutter.
Alternatively, to continue using your configured Java version, update the Gradle
version specified in the following file to a compatible Gradle version (compatible Gradle version
range: 8.4 - 8.7):
/home/USER/APP-DIRECTORY/android/gradle/wrapper/gradle-wrapper.properties
You may also update the Gradle version used by running
./gradlew wrapper --gradle-version=<COMPATIBLE_GRADLE_VERSION>.

Simply installing Java 17, which aligned with the gradle version and configuring flutter jdk-dir flutter config --jdk-dir=<JAVA_DIRECTORY> fixed the issue for me.

work for me , thanks

This worked for me:

Upgrade Gradle version:
To support JDK 21, you'll need at least Gradle 8.5. You can check the Java Compatibility for more details.
Update your android/gradle/wrapper/gradle-wrapper.properties file like this:distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-all.zip

Upgrade AGP version:
In my testing, to work with JDK 21 and Gradle 8.5, you'll need at least AGP 8.3.
Update your android/settings.gradle file like this:plugins {
    id "com.android.application" version "8.3.0" apply false
}

Adapt to AGP 8.0:
You might need to make some changes for AGP 8.0. Check out the AGP 8.0 release notes or use the AGP Upgrade Assistant to help with the migration.

Setting it up this way resolved the issue. Additionally, I had to add the following to the build.gradle file:
android {
    ndkVersion = "25.1.8937393"
    ...
}

I tried following the advices listed here, but I'm getting this. Any help?
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':flutter_compass'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

I tried following the advices listed here, but I'm getting this. Any help?
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':flutter_compass'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

This is an AGP error indicating that you haven't set the namespace attribute in the android{ ... } closure in your app level build.gradle file.
See the link in the error (https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant), but in short you'll probably want to remove package="<existing_value>" attribute from your AndroidManifest.xml, and move it to your app level build.gradle
i.e.
in your AndroidManifest.xml:
- <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-    package="com.example.dontcopythisexactly">
+ <manifest xmlns:android="http://schemas.android.com/apk/res/android">

in project_root/android/app/build.gradle:
android {
+    namespace="com.example.dontcopythisexactly"
    ...
}

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in :app\build.gradle
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in :settings.gradle
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in :gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

这个解决了我的问题，虽然我是在使用其他插件时遇到了问题

This worked for me:
1. **Upgrade Gradle version**:
   To support JDK 21, you'll need at least Gradle 8.5. You can check the [Java Compatibility](https://docs.gradle.org/current/userguide/compatibility.html#java_runtime) for more details.
   Update your `android/gradle/wrapper/gradle-wrapper.properties` file like this:
   ```ini
   distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-all.zip
   ```

2. **Upgrade AGP version**:
   In my testing, to work with JDK 21 and Gradle 8.5, you'll need at least AGP 8.3.
   Update your `android/settings.gradle` file like this:
   ```groovy
   plugins {
       id "com.android.application" version "8.3.0" apply false
   }
   ```

3. **Adapt to AGP 8.0**:
   You might need to make some changes for AGP 8.0. Check out the [AGP 8.0 release notes](https://developer.android.com/build/releases/past-releases/agp-8-0-0-release-notes#namespace-dsl) or use the [AGP Upgrade Assistant](https://developer.android.com/build/agp-upgrade-assistant) to help with the migration.

This worked perfectly.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work. I stopped at the first combination that worked.)

This works, plus, change ndkVersion to 25.1 as the compiler warning indicates: android { namespace = "com.example.untitled2" compileSdk = flutter.compileSdkVersion ndkVersion = "25.1.8937393" }

This works. But can anyone explain why?

@iwarifgha It was already explained in the replies above, eg. https://github.com/flutter/flutter/issues/156304#issuecomment-2420145224

This worked for me:

Upgrade Gradle version:
To support JDK 21, you'll need at least Gradle 8.5. You can check the Java Compatibility for more details.
Update your android/gradle/wrapper/gradle-wrapper.properties file like this:distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-all.zip

Upgrade AGP version:
In my testing, to work with JDK 21 and Gradle 8.5, you'll need at least AGP 8.3.
Update your android/settings.gradle file like this:plugins {
    id "com.android.application" version "8.3.0" apply false
}

Adapt to AGP 8.0:
You might need to make some changes for AGP 8.0. Check out the AGP 8.0 release notes or use the AGP Upgrade Assistant to help with the migration.

Thank you so much, It's working.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

than you. you saved my day.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work. I stopped at the first combination that worked.)

Thank you very much, it works now!!!

Thanks bro so much it worked finally after spending so much time for fixing it.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

Thank you very much!

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

This worked for me.

after applying the above solution #156304 https://github.com/flutter/flutter/issues/156304#issuecomment-2408839383 i got some new error please
`Your project is configured with Android NDK 23.1.7779620, but the following plugin(s) depend on a different Android NDK version:

file_picker requires Android NDK 25.1.8937393

firebase_analytics requires Android NDK 25.1.8937393

firebase_core requires Android NDK 25.1.8937393

firebase_messaging requires Android NDK 25.1.8937393

flutter_local_notifications requires Android NDK 25.1.8937393

flutter_plugin_android_lifecycle requires Android NDK 25.1.8937393

image_picker_android requires Android NDK 25.1.8937393

path_provider_android requires Android NDK 25.1.8937393

shared_preferences_android requires Android NDK 25.1.8937393

url_launcher_android requires Android NDK 25.1.8937393
Fix this issue by using the highest Android NDK version (they are backward compatible).
Add the following to /Users/priyansh/Developer/Projects/teacheron_production/android/app/build.gradle:
android {
ndkVersion = "25.1.8937393"
...
}

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
An issue was found when checking AAR metadata:

   1.  Dependency ':flutter_local_notifications' requires core library desugaring to be enabled
       for :app.

       See https://developer.android.com/studio/write/java8-support.html for more
       details.

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 1s
Error: Gradle task assembleDebug failed with exit code 1
`
` flutter doctor --verbose
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-arm64, locale en-IN)
• Flutter version 3.24.3 on channel stable at /Users/priyansh/Developer/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2663184aa7 (8 weeks ago), 2024-09-11 16:27:48 -0500
• Engine revision 36335019a8
• Dart version 3.5.3
• DevTools version 2.37.3
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/priyansh/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16A242d
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
[✓] VS Code (version 1.94.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.98.0
[✓] Connected device (5 available)
• sdk gphone64 arm64 (mobile)     • emulator-5554                        • android-arm64  • Android 15 (API 35) (emulator)
• iPhone 16 (mobile)              • 27A4EB5C-6B74-43EB-BEBC-B5F81CF1EDD3 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-18-0 (simulator)
• macOS (desktop)                 • macos                                • darwin-arm64   • macOS 15.0.1 24A348 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad                • darwin         • macOS 15.0.1 24A348 darwin-arm64
• Chrome (web)                    • chrome                               • web-javascript • Google Chrome 130.0.6723.92
[✓] Network resources
• All expected network resources are available.
• No issues found!
`

Yes, After downgrade jdk to 17 it started to work again. jdk 21 is creating the problem.

i downgraded to 17 but same issue

我也遇到了 按照上面方法解决了 感谢

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

It's working, thank you.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this is also dependent on plugins, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

(Slight variations in versions might also work. I stopped at the first combination that worked.)

Thank you very much, it works now!!!

This works on mac too. Select the default  JDK to JDK 21 (Android Studio > Settings > Build, Execution, Deployment > Build Tools >Gradle > Gradle JDK > JBR 21.0.3)
then follow the changes mentioned in the quoted reply

Hey!
I get this error, and I followed all the comments above:
A problem occurred evaluating root project 'android'.
> Could not find method android() for arguments [build_bi3sfgpbnnsc9vb8nimtw2blz$_run_closure1@2357e3f1] on root project 'android' of type org.gradle.api.Project.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

It's working for me too, tks!

Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

Finally i got my issue answer, It's working, thank you.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

this fixed my issue but namespace not found error occured. and the solution is https://stackoverflow.com/questions/76108428/how-do-i-fix-namespace-not-specified-error-in-android-studio

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

Thanks a lot, bro, it's working fine now you save us ...

@theandreibogdan

Hey!
I get this error, and I followed all the comments above:
A problem occurred evaluating root project 'android'.
> Could not find method android() for arguments [build_bi3sfgpbnnsc9vb8nimtw2blz$_run_closure1@2357e3f1] on root project 'android' of type org.gradle.api.Project.

I have the same issue, did you find a solution for this?

Re: android() — also checking out this very old QA on SO https://stackoverflow.com/questions/37250493/could-not-find-method-android-for-arguments it looks like you modified the wrong .gradle file. You need app\build.gradle, not the one above.

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

Bro thank you so much... I been working on it for 1 Week......!!

Update 2024 Solved!
flutter config --jdk-dir /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
running this solved my problem

@amirahmadadibi A few of us have already noted that yes, although this also solves the problem momentarily but it's not the right solution. You force yourself to keep using an older Java SDK. There's no need to do that because Flutter can actually work just fine with the new one if you update a few related other packages. No need to paint yourself into a corner and risk new incompatibilities in the future.

download jdk-11 and install it then you should see jdk-11 in your C:\Program Files\Java directory then in the flutter project tirminal run this command flutter config --jdk-dir "C:\Program Files\Java\jdk-11" This command tells Flutter to use the specified JDK directory instead of relying on the JAVA_HOME environment variable.

What went wrong:
An exception occurred applying plugin request [id: 'com.android.application']

Failed to apply plugin 'com.android.internal.application'.
Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
Your current JDK is located in C:\Program Files\Java\jdk-11
You can try some of the following options:
- changing the IDE settings.
- changing the JAVA_HOME environment variable.
- changing org.gradle.java.home in gradle.properties.

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 980ms
Error: Gradle task assembleDebug failed with exit code 1

@darshankawar I spent several hours trying all combinations, JDK 11, 17, the one from a Sandbox-installed AS Koala but finally I found that the new bundled JDK 21 can be made to work if all the other settings are correct (but this depends on plugins as well, so some of your dependent plugins might need fixing, too — the ones I rely on happened to be either all right or my own that I could fix).
Basically, you need this in app\build.gradle:
android {
  ndkVersion "25.1.8937393"

compileOptions {
  sourceCompatibility JavaVersion.VERSION_17
  targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
  jvmTarget = 17
}

This in settings.gradle:
id "com.android.application" version "8.3.2" apply false
id "org.jetbrains.kotlin.android" version "2.0.20" apply false

And this in gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

Slight differences in versions might also work. I stopped at the first combination that worked.
(Credit also to #156304 (comment))

This is Worked for me

I was able to get it failing with:
Font asset "MaterialIcons-Regular.otf" was tree-shaken, reducing it from 1645184 to 1384 bytes (99.9% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
ERROR: Missing classes detected while running R8. Please add the missing classes or apply additional keep rules that are generated in /home/arran/Documents/Projects/untitled2/build/app/outputs/mapping/release/missing_rules.txt.
ERROR: R8: Missing class com.google.errorprone.annotations.CanIgnoreReturnValue (referenced from: com.google.crypto.tink.KeysetManager com.google.crypto.tink.KeysetManager.add(com.google.crypto.tink.KeyTemplate) and 52 other contexts)
Missing class com.google.errorprone.annotations.CheckReturnValue (referenced from: com.google.crypto.tink.InsecureSecretKeyAccess and 1 other context)
Missing class com.google.errorprone.annotations.Immutable (referenced from: com.google.crypto.tink.InsecureSecretKeyAccess and 40 other contexts)
Missing class com.google.errorprone.annotations.RestrictedApi (referenced from: com.google.crypto.tink.aead.AesEaxKey$Builder com.google.crypto.tink.aead.AesEaxKey.builder() and 6 other contexts)
Missing class javax.annotation.Nullable (referenced from: java.lang.Object com.google.crypto.tink.PrimitiveSet$Entry.fullPrimitive and 86 other contexts)
Missing class javax.annotation.concurrent.GuardedBy (referenced from: com.google.crypto.tink.proto.Keyset$Builder com.google.crypto.tink.KeysetManager.keysetBuilder and 3 other contexts)

In a brand new project just by adding:
dependencies:
  flutter:
    sdk: flutter
  oauth2_client: ^3.3.0

All my other dependencies worked.
I had tried a fair amount of the solutions including upgrading and so forth.
plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0"
    id "com.android.application" version "8.1.0" apply false
    id "org.jetbrains.kotlin.android" version "1.8.22" apply false
}

distributionUrl=https\://services.gradle.org/distributions/gradle-8.3-all.zip

    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = JavaVersion.VERSION_1_8
    }

./build/app/outputs/mapping/release/missing_rules.txt
# Please add these rules to your existing keep rules in order to suppress warnings.
# This is generated automatically by the Android Gradle plugin.
-dontwarn com.google.errorprone.annotations.CanIgnoreReturnValue
-dontwarn com.google.errorprone.annotations.CheckReturnValue
-dontwarn com.google.errorprone.annotations.Immutable
-dontwarn com.google.errorprone.annotations.RestrictedApi
-dontwarn javax.annotation.Nullable
-dontwarn javax.annotation.concurrent.GuardedBy

When following the proguard.pro it just lead to more issues.
% java --version
openjdk 17.0.13 2024-10-15
OpenJDK Runtime Environment 17.0.13_p11 (build 17.0.13+11)
OpenJDK 64-Bit Server VM 17.0.13_p11 (build 17.0.13+11, mixed mode, sharing)
arran@arran-desktop:/home/arran/Documents/Projects/untitled2 34341
% flutter --version
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 17025dd882 (2 days ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2
arran@arran-desktop:/home/arran/Documents/Projects/untitled2 34342

I will look at what I can do about that dependency. This is just incase anyone else gets the same issue I had.
p.s. (Unrelated below)
I wish that SDK: here:

Was synonymous with flutter config --jdk-dir
Found out it did nothing.

Works for me , thanks ❤❤


flickering effect

Thank you for sharing the code!
I ran gmflow on some of the datasets from webvid-10M(https://maxbain.com/webvid-dataset/) using the pre-trained checkpoint named 'gmflow_sintel-0c07dcb3.pth'.
As we can see from the following videos, there are noticeable flickering artifacts.
https://github.com/haofeixu/gmflow/assets/36818801/f48738b3-1dba-4f25-91a1-e9dc25cf9e00
https://github.com/haofeixu/gmflow/assets/36818801/b3b021ce-e88a-47e7-a001-375822253f1a
https://github.com/haofeixu/gmflow/assets/36818801/292552c3-f7f2-4f34-a358-6652cb5f8405
Which pre-trained weight should I use for general videos such as webvid-10M?
And is there any suggested solution for the flickering effect?
Thank you in advance.

Maybe you can try this model: https://github.com/autonomousvision/unimatch/blob/master/scripts/gmflow_demo.sh#L7

Thank you for the prompt reply!
I tried to replace the pretrained weight using the weight that you mentioned, but the output results do not coincide with the input images.
So I cloned the unimatch repo and ran the code using the following arguments.
--resume pretrained/gmflow-scale2-regrefine6-mixdata-train320x576-4e7b215d.pth \
--output_path output/gmflow-scale2-regrefine6-davis \
--padding_factor 32 \
--upsample_factor 4 \
--num_scales 2 \
--attn_splits_list 2 8 \
--corr_radius_list -1 4 \
--prop_radius_list -1 1 \
--reg_refine \
--num_reg_refine 6

The output results seem more reasonable, but I was not able to escape from the flickering artifact.
https://github.com/haofeixu/gmflow/assets/36818801/abe8de41-fa35-4211-8b70-81ed35388b7e
https://github.com/haofeixu/gmflow/assets/36818801/73c3ecbe-ca79-4a75-9162-606055a0755b
https://github.com/haofeixu/gmflow/assets/36818801/f586fbd4-6b2a-456a-aeed-3a6e386cc4a4
Are there any arguments that relate to the flickering effect that I can try out?

Hi I guess the flickering results are somewhat expected since the model is trained with two frames only, without any temporal consistency constraints.

@haofeixu Thank you for your valuable opinion.
I was planning to utilize the results of the denseflow for the other task but did not know how it was supposed to behave.
I got a grasp of denseflow behavior thanks to you.
I'll close the issue.


add merge method to IntervalMetadata

is it neccessary? it is set internally and unchangable. isn't the test just
"white elephant"?
On Fri, Nov 11, 2016 at 11:45 AM, Jai Ram Rideout<EMAIL_ADDRESS>wrote:

@jairideout requested changes on this pull request.
@RNAer https://github.com/RNAer a comment about adding a unit test for
the new lower bound checking
In skbio/metadata/tests/test_interval.py
https://github.com/biocore/scikit-bio/pull/1451#pullrequestreview-8254877
:

@@ -494,6 +494,28 @@ def test_concat(self):
metadata={'gene': 'sagC'})
self.assertEqual(obs, exp)

def test_merge(self):

   # empty + empty

   im = IntervalMetadata(self.upper_bound)

   self.im_empty.merge(im)

   self.assertEqual(self.im_empty, im)

   # empty + non-empty

   self.im_empty.merge(self.im_1)

   self.assertEqual(self.im_empty, self.im_1)

   # non-empty + non-empty

   self.im_empty.merge(self.im_2)

   self.im_2.merge(self.im_1)

   self.assertEqual(self.im_empty, self.im_2)

def test_merge_unequal_upper_bounds(self):

Can you add a test for the lower bound case? Coverage will drop otherwise
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/scikit-bio/pull/1451#pullrequestreview-8254877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA9CeLbWmTrGPJXh6UT0Qv26UfmPm4BFks5q9MXIgaJpZM4Kv_Wl
.

better to leave the test for future use cases of lower_bound?

See my previous comment:

Coverage will drop otherwise

And in case the value changes in the future.

The coverage is only marginally dropped (0.01%)? And it is essentially tested in the current test, ie test no exception raised. If you have idea to test of exception raising, I'd be happy to add

To test this you could make a IntervalMetadata._lower_bound attribute that is returned by the lower_bound getter, and then modify that attribute in the unit test. Probably too much work for 1 line of coverage though.
Thanks for your work on this!

Thanks, @jairideout !


signal-desktop: 5.38.0 -> 5.39.0

Description of changes
New version released: https://github.com/signalapp/Signal-Desktop/releases/tag/v5.39.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 169333 run on x86_64-linux 1

1 package built:

signal-desktop


Add assertion on headers

This assertion works just like the smoke_assert_body, but matches headers.

Thank you for your contributions @matthiasr 👍


CI fails on macOS (late january 2023)

The CI on macOS is currently failing with the following error
-- The C compiler identification is AppleClang <IP_ADDRESS>00029
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00029
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Applications/Xcode_14.2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Applications/Xcode_14.2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found YARP: /Users/runner/work/bipedal-locomotion-framework/bipedal-locomotion-framework/install/deps/lib/cmake/YARP (found version "3.7.0")
CMake Error at /usr/local/Cellar/cmake/3.25.1/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Python3 (missing: Python3_EXECUTABLE Python3_INCLUDE_DIRS
-- Configuring incomplete, errors occurred!
  Python3_LIBRARIES Interpreter Development Development.Module
See also "/Users/runner/work/bipedal-locomotion-framework/bipedal-locomotion-framework/build/CMakeFiles/CMakeOutput.log".
  Development.Embed) (Required is at least version "3.6")
See also "/Users/runner/work/bipedal-locomotion-framework/bipedal-locomotion-framework/build/CMakeFiles/CMakeError.log".

      Reason given by package:
          Interpreter: Wrong version for the interpreter "/usr/local/bin/python"

Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.25.1/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
  cmake/FindPython/Support.cmake:2984 (find_package_handle_standard_args)
  cmake/FindPython3.cmake:[38](https://github.com/ami-iit/bipedal-locomotion-framework/actions/runs/4053623191/jobs/6974459708#step:19:39)9 (include)
  cmake/BipedalLocomotionFrameworkFindDependencies.cmake:56 (find_package)
  cmake/BipedalLocomotionFrameworkDependencies.cmake:[52](https://github.com/ami-iit/bipedal-locomotion-framework/actions/runs/4053623191/jobs/6974459708#step:19:53) (checkandset_dependency)
  CMakeLists.txt:21 (include)

Accordingly to this the python version installed is 3.11
https://github.com/ami-iit/bipedal-locomotion-framework/actions/runs/4053623191/jobs/6974459708#step:19:68
@traversaro do you have any hints?

On the specific problem, I think /usr/local/bin/python is the one installed by setup-python and not the one by homebrew, as in https://github.com/ami-iit/bipedal-locomotion-framework/blob/af219c6937d77c393348fe464ca4588690fbbe66/.github/workflows/ci.yml#L102 we do not delete it.
More in general, I do not think it is worth to spend time testing Homebrew in general, and more in particular Homebrew with Python, but this is my personal opinion.


This is genius!!!!!!

Wow, brilliant idea!! How can I help?

I'd love to write a web driver script to integrate this into pizza hut so I can automate those stuffed crust pizza! Maybe even add an Amazon button too!

@DanielBodnar do it!


[New Feature] Adding Toggle Buttons or Switches

Is your feature request related to a problem? Please describe.
I often encounter situations where I need to implement toggle buttons in user interfaces. These toggle buttons allow users to switch between two states or options, and they are commonly used in various applications and websites. Currently, the UI library I'm using does not provide built-in toggle buttons, which makes it more time-consuming and complex to implement them manually.
Describe the solution you'd like
I would like the UI library to include a set of toggle buttons as a built-in component. These toggle buttons should be customizable and easy to use, allowing developers to quickly add toggle functionality to their interfaces. Ideally, the toggle buttons should have options for different styles, sizes, and colors, so they can be easily adapted to match the overall design of the application.
Describe alternatives you've considered
As an alternative, I could create custom toggle buttons from scratch, this would require additional development time and effort.

@Rhishikesh12 Will you be able to implement this without using any external packages?

Yes I will try to make as many buttons as possible

Because we are not allowing  any use of 3-rd party packages .So, make changes to your code accordingly .

please assign me this issue

It is already done. Check the PR.


Frequency support

Any ETA on when you plan to expose frequency information, if ever?

There are plans to expose frequency, but not ETA on when it will happen

In the Readme, you have the following:
// Get the size of level 1 data cache on the fastest core in the processor (e.g. big core in big.LITTLE ARM systems):
const size_t l1_size = cpuinfo_get_processor(0)->cache.l1d->size;

Does that mean it's safe to assume that the first cluster will always be the faster cluster on big.LITTLE ARM systems? Basically, trying to get to the faster cores/processors w/o having frequency information.
Thanks!

@Diarrhio Yes, clusters are sorted by microarchitecture, then by frequency (if available). The first cluster is the most performance cluster.


Module/datafeed

The DataFeed module provides a way to feed data from the external world to the runtime.
This module is designed for a general data feed purpose, to make feeding data a
User-friendly service for those who do not have in-depth knowledge of the
off-chain worker. With this pallet, you can fetch the off-chain data and feed it
back onto the network and modify some specific runtime storage.

@AtenJin where is your setup for how you weighed this?

Thanks for your work, @AtenJin. Unfortunately, we won't go further with this at this time. However, especially since 2.0.0 has been released, you can now just develop and publish your own pallets on crates.io for anyone to use. No need to get all of them into our repo anymore :) . Maybe that is a path you'd like to take with this.

@hammeWang fyi on this...


Disable kured and skuba-update.timer during upgrade

waiting for kubelet works fine:
I0725 13:49:26.215286    7130 states.go:35] === applying state kubernetes.restart-services ===
I0725 13:49:26.376607    7130 ssh.go:167] running command: "sudo sh -c 'systemctl restart crio kubelet'"
I0725 13:49:57.761664    7130 states.go:40] === state kubernetes.restart-services applied successfully ===
I0725 13:49:57.761719    7130 states.go:35] === applying state kubernetes.wait-for-kubelet ===
I0725 13:49:58.248354    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:49:59.733059    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:01.218698    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:02.702622    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:04.187240    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:05.670931    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:07.154887    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:08.639162    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:10.122821    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:11.606767    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:13.091153    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:14.576023    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:16.059411    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:17.544084    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:19.030748    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:20.515000    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:21.998981    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:23.483410    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:24.967028    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:26.450791    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:27.935007    7130 kubernetes.go:121] failed to get node my-master-0, continuing...
I0725 13:50:29.803416    7130 states.go:40] === state kubernetes.wait-for-kubelet applied successfully ===

do you think you could fill the PR comment out. it is empty for me. Just a little "this is why we are doing this" would be great! thank you.

updated :+1:

We have to ensure a node that has been previously locked by the user doesn't end unlocked as a result of our actions.
The current code doesn't take that into account. We had similar issues in the past with v3 that was uncordoning nodes the user had manually cordoned.

it's addressed now, thanks for the hint


[Question] Expected output for IOCTL_BIOMETRIC_CONNECT_SECURE

Hello,
The SDCP wiki documentation indicates IOCTL_BIOMETRIC_CONNECT_SECURE will be added to WBF and the expected output is WINBIO_SECURE_CONNECTION_RESPONSE which nests WINBIO_SECURE_CONNECTION_DATA.
However, after updating WDK and looking at the updated winbio headers for RS4, there is no structure WINBIO_SECURE_CONNECTION_RESPONSE defined.
So, what does the framework really expects? WINBIO_SECURE_CONNECTION_RESPONSE or WINBIO_SECURE_CONNECTION_DATA?
If the later, as there is no WinBioHresult field, how to report a failure in case the request to the device was unsuccessful?
Thank you!
Regards,
Paul

Sharing my findings for other.
Default SensorAdapter in RS4/RS5 does not seems to implement SensorAdapterConnectSecure(), hence
IOCTL_BIOMETRIC_CONNECT_SECURE payload could be pretty much anything as long as SensorAdapterConnectSecure() returns WINBIO_SECURE_CONNECTION_DATA.

@pbesson-invn sorry for the radio silence! You're correct that the inbox sensor adapter does not support the new IOCTL yet, since the inbox adapter only supports basic sensors, not advanced sensors. We expect you to write your own sensor adapter here, in which case you just need to support the SensorAdapterConnectSecure function, and are free to use your own IOCTL (or whatever) to talk to your hardware.


PR to make changing auth notifications (VerifyEmail,  ResetPassword) easier

When extending the Auth notification templates (Illuminate\Auth\Notifications\ResetPassword, Illuminate\Auth\Notifications\VerifyEmails) to write your own messages but keep the original logic, you have to override the toMail methods.
Would a PR like the following have a chance to get accepted?
Old:
public function toMail($notifiable)
{
    if (static::$toMailCallback) {
        return call_user_func(static::$toMailCallback, $notifiable, $this->token);
    }

    if (static::$createUrlCallback) {
        $url = call_user_func(static::$createUrlCallback, $notifiable, $this->token);
    } else {
        $url = url(route('password.reset', [
            'token' => $this->token,
            'email' => $notifiable->getEmailForPasswordReset(),
        ], false));
    }

    return (new MailMessage)
        ->subject(Lang::get('Reset Password Notificationss'))
        ->line(Lang::get('You are receiving this email because we received a password reset request for your account.'))
        ->action(Lang::get('Reset Password'), $url)
        ->line(Lang::get('This password reset link will expire in :count minutes.', ['count' => config('auth.passwords.'.config('auth.defaults.passwords').'.expire')]))
        ->line(Lang::get('If you did not request a password reset, no further action is required.'));
}

New:
public function toMail($notifiable)
{
    if (static::$toMailCallback) {
        return call_user_func(static::$toMailCallback, $notifiable, $this->token);
    }

    if (static::$createUrlCallback) {
        $url = call_user_func(static::$createUrlCallback, $notifiable, $this->token);
    } else {
        $url = url(route('password.reset', [
            'token' => $this->token,
            'email' => $notifiable->getEmailForPasswordReset(),
        ], false));
    }

    return $this->getMailMessage($url);
}

protected function getMailMessage($url)
{
    return (new MailMessage)
        ->subject(Lang::get('Reset Password Notificationss'))
        ->line(Lang::get('You are receiving this email because we received a password reset request for your account.'))
        ->action(Lang::get('Reset Password'), $url)
        ->line(Lang::get('This password reset link will expire in :count minutes.', ['count' => config('auth.passwords.'.config('auth.defaults.passwords').'.expire')]))
        ->line(Lang::get('If you did not request a password reset, no further action is required.'));
}

This way I could just override the getMailMessage method in an own notification that extends the original one.
Just quickly checking here before submitting my first PR to Laravel - just want to make sure.
Thanks,
Sebastian

@SebastianSchoeps yes it can be expanded that way. But why should we need this?

The question is not if it could be done (technically), but if a PR would be accepted.
Possible use cases:

add a link to the privacy policy into the mail
use different texts in the body
use a different subject
remove the "this link will expire line" (for whatever reson)
use a saluation

@SebastianSchoeps The situations you mentioned for this can also be overridden directly "toMail".
Example : A new "toMail" can be written to the notification file created for a hello message, overriding "toMail" completely.
PR will not be accepted in my guess, but send it. So we can see what Taylor Otwell has to say about it.

That's what I do right now, overridding toMail. Which means I have to keep the logic e.g. for creating the URLs. That's exactly the reasoning for the PR.

That's what I do right now, overridding toMail. Which means I have to keep the logic e.g. for creating the URLs. That's exactly the reasoning for the PR.

I understand what you say. But Taylor Otwell is very sensitive about adding new things. He argues that the amount of code is important for the sustainability of the project. The PR you've applied doesn't exactly fix a problem. As I said, it is already working properly, so you may not accept it, try your luck. @taylorotwell

Best bet is probably just to make the PR and let us evaluate. You have already essentially written the code here.

@SebastianSchoeps also please see our issue templates before opening a feature request and use the ideas repo for these.

Yes, sorry, I only found the idea repo afterwards and thought „That‘s where I should have gone“...
Am 5. Nov. 2020, 13:21 +0100 schrieb Dries Vints<EMAIL_ADDRESS>@SebastianSchoepshttps://github.com/SebastianSchoeps also please see our issue templates before opening a feature request and use the ideas repo for these.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/laravel/framework/issues/35087#issuecomment-722344288, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKQSM2XSVNORCADTBDFDK5DSOKKFZANCNFSM4TJ5QO2A.


Replace dirAdd() calls with dirAppend() or dirInsert()

High Level Overview of Change
Just tidying up some unfinished business here: https://github.com/ripple/rippled/issues/2516
Calls to dirDelete() had been removed in a previous commit.  Now that the SortedDirectories amendment is unconditionally enabled, it's okay to remove the calls to dirAdd().  Once all dirAdd() calls are removed, then dirAdd() itself can be removed.  That's what we do here.
Type of Change

[x] Refactor (non-breaking change that only restructures code)

This change is purely a refactor and should have no effect on functionality.  So the change should not need any mention in the release notes.

@miguelportilla, thanks for the careful review.  I made your suggested changes in this commit: https://github.com/ripple/rippled/pull/3830/commits/c2a3b9f09fb94bba91ccc8c2ca5cefafb7b405f2  Let me know if you're good with those changes.  If you are, and the branch passes CI, then I'll squash and mark the pull request as passed.  Thanks.

@scottschurr Changes look great, thank you.


rendered_markdown: Approximate non-alpha dark mode table border color.

This removes the alpha channel from table borders in dark mode, eliminating points of "starlight" where borders intersect.
Other fixes like this have involved color-mix(), but that is a poor choice in this case because background colors in messages differ from place to place anyway. And calculating a proper color-mix for each variant is clearly way too much overhead for such a minor design feature (note that there already is no alpha channel in light mode, either).
One additional improvement with a non-alpha color here is that borders remain constant even over the darker background of table header rows.
CZO discussion

Screenshots and screen captures:

Before
After

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Looks great, merged, thanks @karlstolley!


[v0.6] /hain command does not return anything

When I first open up Hain it lists the /hain command as a way to see a list of commands, but it returns no results.
See screenshot:
http://puu.sh/tVOKo/b9be04c49f.png

Thanks for reporting issue.
This issue will be fixed very soon.
Thank you

this issue has been resolved with v0.6.x
now, /hain command shows available commands.


SSL handshake failures are not caught

In the request method, while attempting to send a request, only _SendFailed exceptions are caught and all others (such as a Failed SSL handshake, which may occur after too much time has elapsed between requests) are ignored. This then leads to recv or recv_into being run on an invalid connection, resulting in an exception and potentially a socket leak.
This was discovered while debugging adafruit/circuitpython#4061, but does not wholly fix the issue as the code will then run into issue #66. May be related to #63.

I fixed this for my example program by simply replacing except _sendFailed: with except: but I don't know if there's issues with that?

I fixed this for my example program by simply replacing except _sendFailed: with except: but I don't know if there's issues with that?

Ya, don't do except: because you'll catch absolutely everything. You can add a second except for the error type of "Failed SSL handshake" though.

@tannewt what's the issue with catching everything here? Is there an exception that's considered acceptable? All the step does is mark that the socket is not ready to receive data and close it, which seems like the right thing to do for any exception.

Alternatively I could add in an else: to actually raise exceptions that aren't of the two specified types.

@tannewt what's the issue with catching everything here? Is there an exception that's considered acceptable? All the step does is mark that the socket is not ready to receive data and close it, which seems like the right thing to do for any exception.

Catching everything is bad because you'll catch extra stuff. Reload, keyboard and deep sleep all use exceptions. Those things (or others) may be caught higher and the code will expect the socket to continue. So, always be explicit with catching exceptions.

Closed by #70


Move serialization decision from server to client

Enable the DriftServer to handle connections from clients independent of their serialization configuration.
Fixes #1593

Thanks!


[Question] Could we use wildcard urls?

Describe the bug
This is more a question than a bug.
On validateRelationship I want to use something like "*.example.com" because I need to send cookies to a subdomain. I found that I cannot use wildcard urls on this method, it always return result false and requestedOrigin " ".
I have "delegate_permission/common.use_as_origin"  on the root domain.
Root : example.com
Sub domain : app.example.com
Sub domain : ig.example.com
On the other hand I am using on the Manifest just in case:
<intent-filter android:autoVerify="true">
..
<data
                    android:host="*.example.com"
                    android:scheme="https" />
..

I am also using
<queries>
        <intent>
            <action android:name="android.support.customtabs.action.CustomTabsService" />
        </intent>
    </queries>

Nothing seems to work. I cannot see the cookies when I check on chrome inspect.

Describe the bug This is more a question than a bug. On validateRelationship I want to use something like "*.example.com" because I need to send cookies to a subdomain. I found that I cannot use wildcard urls on this method, it always return result false and requestedOrigin " ". I have "delegate_permission/common.use_as_origin"  on the root domain.
Root : example.com Sub domain : app.example.com Sub domain : ig.example.com
On the other hand I am using on the Manifest just in case:
<intent-filter android:autoVerify="true">
..
<data
                    android:host="*.example.com"
                    android:scheme="https" />
..

I am also using
<queries>
        <intent>
            <action android:name="android.support.customtabs.action.CustomTabsService" />
        </intent>
    </queries>

Nothing seems to work. I cannot see the cookies when I check on chrome inspect.

Interesting thing, when I send other headers that are nonwhitelisted other than cookies, they are all there in the request headers when I check chrome inspector, the only one that cannot be overridden is cookie, any ideas?

Cookies erased from the screenshot are the wrong ones, they are not the ones I'm sending, they are being overrides.

Update.
I am able to see now non-whitelisted headers but I'm only see bearer-token for example. Cookies are always override.
It feels like chrome custom tab is blocking our cookies sent with extra-headers.
I am using the example code, with our domain that is validating correctly the digital asset links for relation use as origin.

On requests headers I can see bearer-token correctly but cookie has other stuff and does not contain the ones I'm sending.


Support document filters in ETK

Add ability to filter out unwanted documents so that they don't appear in the KG in ES. The initial version will support simple filters based on regex. The filters will be specified in a JSON document with the following structure. At the top level, the filters are a dictionary based on TLD, so that it is easy to organize filters, and so that ETK can quickly find the filters relevant to a document.
{
  "tld1": [ ... ],
  "tld1": [ ... ],
  ...
}

Each of the arrays contains individual filters with the following format:
{
  "field": < any field in a CDR document, typically url, raw_content >,
  "regex": < a regular expression in Python syntax >,
  "action": < one of "keep", "discard" >
}

When a document comes in, ETK will find the array of rules for the TLD, if the TLD is not listed, the document is no_action.
ETK will then test each of the rules in the array sequentially, and will do the action of the first rule whose regex is satisfied. If none of the rules apply, the document is marked as no_action.
Results:, the outcome of rule execution is recorded in the attribute prefilter_filter_outcome, with values keep, discard or no_action.
We envision that more filtering may happen inside ETK, so that a document that the prefilter marks as no_action may eventually be discarded by further analysis. Downstream filters may even discard a document that the prefilter decides to keep.
Note: Upon ingesting the filter dictionary, ETK should compile the regexes for efficient execution.

We have a better way to do this in ETK2


[labs/eleventy-plugin-lit] Use file URLs for resolved module paths

Fixes #3059
Due to module file paths having C:\ for Windows, the imports fail due to unrecognized protocol. Converting them to file URLs fixes that.
Note:
This makes eleventy-plugin-lit now work in worker (default) mode for Windows users.
In vm mode, it still breaks due to an issue with ModuleLoader noted here https://github.com/lit/lit/issues/3202
I was also unable run the eleventy-plugin-lit package test suite in Windows as the testing rig has issues somewhere with the filesystem symlinking, writing, reading.
I did, however, manually test it by running the example eleventy project on a Windows machine and confirmed worker mode runs.

Maybe file an issue about testing in windows if there isn't one already?

Thanks! Filed https://github.com/lit/lit/issues/3205


Find out about web build collectable 2D sprite bug

May be related to:

https://github.com/godotengine/godot/issues/41270
https://github.com/godotengine/godot/pull/41314
https://github.com/godotengine/godot/pull/39867
https://github.com/godotengine/godot/pull/39604

Build actions:

https://github.com/jayypluss/BreezyWave/actions/runs/2425815227
https://github.com/jayypluss/BreezyWave/runs/6701741938?check_suite_focus=true

Evidences:
https://user-images.githubusercontent.com/17395606/171698978-7763a589-6220-4b95-b617-c55c711306b9.mp4
https://user-images.githubusercontent.com/17395606/171698971-06218b3b-2e46-4164-8491-ce34198c0194.mp4


Questions: sub-menus, 'help' in a submenu, and providing common commands to multiple submenus

This looks like a great library, and I started to try to use it for what will be a fairly a complex project.  We will have lots of commands, and want to allow our SQA group to use this to script things (and don't want to go the route of a full blown DSL).  I have two questions/hurdles that I've bumped into and would like to pick your brain before rummaging the code base.
The first hurdle I have right now is organizing all the commands, and it appeared that the sub-menu example would do the trick nicely.   To test this, I've setup two submenus (UsrMenu and DevMenu) and added a few commands to each.  I have my MainMenu and add the two subs to it.  Everything works great, except that I cannot get help about the commands within each of the submenus.
$ usr
user$ help
This gives help on the usr command itself, but doesn't list the commands which were added to that submenu.  Any idea if this should work?  Or how to accomplish it?  Do I need to maybe define my own 'help' command in each of the sub menus?
The second wrinkle I found is that I wanted to define a set of common commands to be available across all sub menus (we will eventually have many), and I thought to create a BaseMenu that would define them and have the submenus extend from BaseMenu to inherit them.  I've resorted to having the the BaseMenu expose an AddBaseCommands(CMenu targetMenu) operation and each child asks the base to add them directly.  This works, but it was a little surprise that 'inherited' menu items didn't just work.
Any help that you can give on the help on sub-menus topic would be welcomed.

Thank you for trying the library!
These are good questions, and I've just looked into the first issue you describe. I'm not sure, but I think I fixed something similar recently, but it is not yet in the latest release tag (0.7.1) which I suppose you're using. I've just added a new tag 0.8 preview, which include this fix.
To make sure I understood you correctly, can you have a look at the following code to see if it reflects your scenario? I've included the output, which seems fine to me, and is probably what you wanted.
var main = new CMenu ();
var m1 = new CMenu ("1");
var m2 = new CMenu ("2");
main.Add (m1);
main.Add (m2);
m1.Add ("a", "This is the help text of 'a'.");
m1.Add ("b", "This is the help text of 'b'.");
m2.Add ("x");
m2.Add ("y");
main.Run ();

$ help
Available commands:
      1
      2
h   | help
q   | quit
Type "help <command>" for individual command help.
$ 1
$ help
Available commands:
      a
      b
h   | help
q   | quit
Type "help <command>" for individual command help.
$ help a
This is the help text of 'a'.
$ quit
$ help 1
      a
      b
h   | help
q   | quit

I'm currently looking into your second issue and will write here again later.

Re your second issue, does this code reflect your scenario?
class BaseMenu : CMenu
{
	public BaseMenu ()
	{
		Add ("time", s => Console.WriteLine ("Shared command in BaseMenu: " + DateTime.Now));
	}
}

class InheritedMenu : BaseMenu
{
	public InheritedMenu ()
	{
		Selector = "inherited";
		Add ("foo", s => Console.WriteLine ("InheritedMenu: foo"));
		Add ("bar", s => Console.WriteLine ("InheritedMenu: bar"));
	}
}

class Test
{
	static void Main (string[] args)
	{
		var main = new BaseMenu ();
		main.Add (new InheritedMenu ());
		main.Run ();
	}
}

Using the 0.8 preview tag, I get this output:
$ time
Shared command in BaseMenu: 2016.07.31 19:24:06
$ inherited
$ time
Shared command in BaseMenu: 2016.07.31 19:24:15
$ bar
InheritedMenu: bar
$

If I misunderstood, could you show an example of how you tried it earlier when it did not work?

@JVolkar , I hope that solved your problem. I'll close this ticket in a few days, unless I can help further.


Tiger and Tigress

Run the code under /tiger/scratch/gpfs, move files to /tigress afterwards

Resolved.


Typo

Did you miss a 'd' in the Note section?
This is the query plan that is stored  in the plan cache.

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

ID: 0255e0c3-6f50-a3c5-4ef0-7d93d597e9c9
Version Independent ID: fd034f77-24f7-3455-5355-ddeb1ad38b21
Content: Execution Plans - SQL Server
Content Source: docs/relational-databases/performance/execution-plans.md
Product: sql
Technology: performance
GitHub Login: @pmasl
Microsoft Alias: pelopes

PR here: https://github.com/MicrosoftDocs/sql-docs/pull/4844

@hecongy -- cyhe, thank you for fixing this typo.  Your PR has been merged and the updated document will be live tomorrow.