tool · inferred from evidence
Gradle
A build automation tool mentioned as the context for dependency resolution issues.
- Gradle 7 file watching in Alpine Docker container leads to JVM crash SIGSEGV
This was a Gradle bug in the native file-watching integration on Alpine (musl). It was fixed by PR #17055, which shipped in Gradle 7.0.1, upgrade to 7.0.1 or later to resolve the crash. If you are stuck on 7.0.0, you can work around it by d
- Gradle Problems reading data from Binary store error on dependency resolution
A Gradle maintainer confirmed this is not caused by the Gradle version itself: the corrupt serialized resolution result varies with the order dependencies are processed, which can change for many reasons. Run the build with --stacktrace to
- mem0 Python search() metadata filters return nothing (not implemented before 1.0.0)
The failure is caused by another process holding the temporary files open, on Windows this is almost always antivirus real-time scanning. Uninstall or disable the antivirus real-time scanner (reporters confirmed McAfee Endpoint / RAV endpoi
- flutter build appbundle fails: Unknown Kotlin JVM target: 21 (klippa_identity_verification_sdk)
The reporter fixed it by changing the JavaVersion setting in the Android build configuration so the Kotlin compiler targets a JVM version the SDK supports instead of defaulting to Java 21. Align the project's Java version (e.g. set sourceCo