Crashing on launch when updating Android Gradle Plugin to 4.0.0 using  app bundle

It's always crashing when updating the Android Gradle Plugin to 4.0.0. No matter if it's the latest ImagePicker version or not.
Steps to Reproduce
Currently, no idea why it doesn't crash on the emulator (maybe it's something related to R8 because the emulator doesn't have release build mode).
Here my steps:

Create an app bundle of an app with ImagePicker plugin added
Install it on the device
Just run the app

Logs
Fatal Exception: java.lang.NoClassDefFoundError: Failed resolution of: Lio/flutter/plugins/imagepicker/ImagePickerPlugin$LifeCycleObserver;
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

Fatal Exception: java.lang.IllegalAccessError: io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java)

Hi @arturogutierrez
Can you build apk with 4.0.0? https://github.com/flutter/flutter/issues/58247
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample.
Thank you"

Oh, interesting. It builds the app bundle without problems but it fails when creating the APK
* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.
   > Failed to transform libs.jar to match attributes {artifactType=processed-jar, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JetifyTransform: /build/app/intermediates/flutter/debug/libs.jar.
         > Failed to transform '/build/app/intermediates/flutter/debug/libs.jar' using Jetifier. Reason: FileNotFoundException, message: /build/app/intermediates/flutter/debug/libs.jar (No such file or directory). (Run with --stacktrace for more details.)
           Please file a bug at http://issuetracker.google.com/issues/new?component=460323.

So, it seems it's the same issue as #58247. I detected when uploading the app bundle to the Play Store and distribute it through an internal track.

I think this error is by the same issue?
java.lang.IllegalAccessError: Interface androidx.lifecycle.b implemented by class io.flutter.plugins.googlemaps.GoogleMapsPlugin is inaccessible (declaration of 'io.flutter.plugins.googlemaps.GoogleMapsPlugin' appears in /data/app/ae.ucg.alyameen-apuM7Q8bFQjyO2OwJ37ULg==/base.apk)

This is after the application was minified

labelling the issue since app bundle not throwing error but APK does from comment

The exact same thing is happening to me but with the Google Maps Flutter plugin. In debug, the app launches properly, but when I build for release, it crashes on launch with the stacktrace:
time:<PHONE_NUMBER>780
msg: java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.googlemaps.GoogleMapsPlugin is inaccessible (declaration of 'io.flutter.plugins.googlemaps.GoogleMapsPlugin' appears in base.apk)
stacktrace: java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.googlemaps.GoogleMapsPlugin is inaccessible (declaration of 'io.flutter.plugins.googlemaps.GoogleMapsPlugin' appears in base.apk)
	at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(Unknown Source:0)
	at com.example.app.MainActivity.onCreate(Unknown Source:3)
	at android.app.Activity.performCreate(Activity.java:7824)
	at android.app.Activity.performCreate(Activity.java:7813)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1307)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3409)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
	at android.os.Handler.dispatchMessage(Handler.java:107)
	at android.os.Looper.loop(Looper.java:214)
	at android.app.ActivityThread.main(ActivityThread.java:7356)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:915)

Flutter Doctor:
$ flutter doctor -v
[✓] Flutter (Channel master, 1.19.0-2.0.pre, on Mac OS X 10.15.5 19F101, locale en-PH)
    • Flutter version 1.19.0-2.0.pre at /Users/hakuflou/Developer/flutter
    • Framework revision eb1a6efe16 (3 days ago), 2020-05-30 21:58:02 -0400
    • Engine revision 923687f0e7
    • Dart version 2.9.0 (build 2.9.0-11.0.dev 6489a0c68d)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/hakuflou/Library/Android/sdk
    • Platform android-R, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (1 available)
    • Mi 9T • dd7068e6 • android-arm64 • Android 10 (API 29)

• No issues found!

Any news on this, facing white screen when testing release build. Get error of image picker

Downgrade back to 3.6.2

Thanks @arturogutierrez that fixed it. I hope team comes up with solution for 4.0 as well

Downgrade back the Android Gradle Plugin in your build.gradle file to 3.6.2

Running into the same issue but I don't understand what your comments means... can you give me step by step .

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

To pass this error, add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.** { *; }

Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.

To pass this error, add bellow line to app/build.gradle
    lintOptions {
        checkReleaseBuilds false
    }

Downgrade back the Android Gradle Plugin in your build.gradle file to 3.6.2

Running into the same issue but I don't understand what your comments means... can you give me step by step .

I did downgrade to 3.6.2 and it did the trick for me:

update android/build.gradle
replaced:

    dependencies {
        classpath 'com.android.tools.build:gradle:4.0.0'

with
    dependencies {
        classpath 'com.android.tools.build:gradle:3.6.2'

flutter clean
flutter build appbundle --release

Proposed solution
As the issue is fixed in flutter_plugin_android_lifecycle 1.0.4, make image_picker depend on
flutter_plugin_android_lifecycle:  #^1.0.4
https://github.com/flutter/flutter/issues/48906

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

To pass this error, add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.** { *; }

And
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.

To pass this error, add bellow line to app/build.gradle
    lintOptions {
        checkReleaseBuilds false
    }

use this solution fix error

I've stuck to the latest Android Studio Gradle plugin from the 3.x series (3.6.4) paired with an up-to-date Gradle version (Android Studio Gradle plugin 3.6.4 + Gradle 6.6 yields no error for me).

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

To pass this error, add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.** { *; }

And
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.

To pass this error, add bellow line to app/build.gradle
    lintOptions {
        checkReleaseBuilds false
    }

proguard-rules.pro does not exist in my project. Is it possible to add the required line by creating the file first and then adding it?

@SametSahin10
You add file proguard-rules.pro under app then add line -keep class androidx.lifecycle.** { *; } to the file.

follow this https://github.com/flutter/flutter/issues/58479#issuecomment-647827484, work properly

The dependency on androidx.lifecycle is ultimately coming from flutter_plugin_android_lifecycle, which imports androidx.lifecycle.Lifecycle (FlutterLifecycleAdapter.java) but does not list it as a dependency in its build.gradle (build.gradle). It used to, but the dependency was removed because its already included in Flutter itself now (https://github.com/flutter/plugins/pull/2467). Maybe the missing dependency is the cause of R8 shrinking away androidx.lifecycle, just a theory which I haven't tested.

This error is not limited to Image Picker plugin. Shared Preference also doesn't work with Android Gradle plugin 4.., so I have to downgrade android gradle plugin to 3.6.*. Only difference here is that App doesn't crash on launch but instead Shared Preference read/write operations don't work. They silently fail with exception
Non-fatal Exception: java.lang.Exception: MissingPluginException(No implementation found for method getAll on channel plugins.flutter.io/shared_preferences)

Downgrade back the Android Gradle Plugin in your build.gradle file to 3.6.2

Running into the same issue but I don't understand what your comments means... can you give me step by step .

I did downgrade to 3.6.2 and it did the trick for me:

update android/build.gradle
replaced:

    dependencies {
        classpath 'com.android.tools.build:gradle:4.0.0'

with
    dependencies {
        classpath 'com.android.tools.build:gradle:3.6.2'

flutter clean
flutter build appbundle --release

This works but I really don't understand why do we have to downgrade something (oftenly downgrade gradle version for Android) in such scenarios, The maintainers for these plugins should provide a decent compatibility over the resources, especially when the plugin itself is officially supported by Flutter. Is it that hard to refactor the codebase and improve compatibility?

Adding my error here so that the other can google that. Occurred with image_picker:

W/FlutterActivity( 7692): Tried to automatically register plugins with FlutterEngine (io.flutter.embedding.engine.FlutterEngine@894cff8) but could not find and invoke the GeneratedPluginRegistrant.

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

To pass this error, add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.** { *; }

And
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.

To pass this error, add bellow line to app/build.gradle
    lintOptions {
        checkReleaseBuilds false
    }

This did the fix for me. Initially, if you don't have the app/proguard-rules.pro then create the proguard-rules.pro file under app first then add the line.

https://github.com/flutter/flutter/issues/49438 is required to support AGP 4.0.0

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
-keep class androidx.lifecycle.DefaultLifecycleObserver

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

Thanks a lot ! it works perfect to me !
in my case case, the problem was:

MissingPluginException(No implementation found for method initialize on channel dexterous.com/flutter/local_notifications)
MissingPluginException(No implementation found for method getInitialLink on channel uni_links/messages)
MissingPluginException(No implementation found for method getApplicationDocumentsDirectory on channel plugins.flutter.io/path_provider)

Putting here for future searching ....

I have the same problem, I tried everything and there is no way:
java.lang.IllegalAccessError: Interface androidx.lifecycle.b implemented by class io.flutter.plugins.googlemaps.GoogleMapsPlugin is inaccessible (declaration of 'io.flutter.plugins.googlemaps.GoogleMapsPlugin' appears in /data/app/com.ingeniaweb.viveloapp-H9mXh_lbxlJZ51iq8XAcjw==/base.apk) 	at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(Unknown Source:0) 	at com.example.vivelo_app.MainActivity.w(Unknown Source:5) 	at io.flutter.embedding.android.e.g(Unknown Source:64) 	at io.flutter.embedding.android.d.onCreate(Unknown Source:20) 	at android.app.Activity.performCreate(Activity.java:7893) 	at android.app.Activity.performCreate(Activity.java:7880) 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1307) 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3283) 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3457) 	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83) 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135) 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95) 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2044) 	at android.os.Handler.dispatchMessage(Handler.java:107) 	at android.os.Looper.loop(Looper.java:224) 	at android.app.ActivityThread.main(ActivityThread.java:7562) 	at java.lang.reflect.Method.invoke(Native Method) 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539) 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)

I'm having similar difficulties, and I'm wondering whether anyone has managed to figure this out using gradle build above 4.0.0? My project needs to use firebase crashlytics and analytics, as well as firebase messaging and they require the 4.* gradle versions. Going absolutely insane here trying to make these things work together!
The following procedures did not work for me without downgrading the gradle too.

Caused by java.lang.IllegalAccessError: Interface androidx.lifecycle.c implemented by class io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver is inaccessible (declaration of 'io.flutter.plugins.imagepicker.ImagePickerPlugin$LifeCycleObserver' appears in /data/app/com.arturogutierrez.acnhcompanion-9Qila6WPNT5CzI3jOOnXHg==/base.apk)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.setup(ImagePickerPlugin.java:22)
       at io.flutter.plugins.imagepicker.ImagePickerPlugin.onAttachedToActivity(ImagePickerPlugin.java:27)
       at io.flutter.embedding.engine.FlutterEnginePluginRegistry.add(FlutterEnginePluginRegistry.java:106)
       at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:56)
       at com.arturogutierrez.acnhcompanion.MainActivity.configureFlutterEngine(MainActivity.java:5)
       at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:64)
       at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:20)

To pass this error, add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.** { *; }

And
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:debugRuntimeClasspath'.

To pass this error, add bellow line to app/build.gradle
    lintOptions {
        checkReleaseBuilds false
    }

use this solution fix error

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

This worked for me. This was the issue i faced.

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

Unfortunately this don't work for me..
My issue:
java.lang.IllegalAccessError:
at io.flutter.plugins.imagepicker.ImagePickerPlugin.registerWith (ImagePickerPlugin.java)
at io.flutter.plugins.GeneratedPluginRegistrant.registerWith (GeneratedPluginRegistrant.java:49)
at br.com.boticario.voluncheersgb.MainActivity.onCreate (MainActivity.java:3)
at android.app.Activity.performCreate (Activity.java:7963)
at android.app.Activity.performCreate (Activity.java:7952)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1307)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3629)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3806)
at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2267)
at android.os.Handler.dispatchMessage (Handler.java:107)
at android.os.Looper.loop (Looper.java:237)
at android.app.ActivityThread.main (ActivityThread.java:8167)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:496)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1100)

Silly question - doesn't this problem ultimately lie with the library developer? Specifically, why does this only seem to be a problem in one(?) or a small handful of libraries, and not a sweeping problem? Or is Gradle over-employing optimizations?
#genuinequestion

Silly question - doesn't this problem ultimately lie with the library developer? Specifically, why does this only seem to be a problem in one(?) or a small handful of libraries, and not a sweeping problem? Or is Gradle over-employing optimizations?
#genuinequestion

I don't think it is always simply an issue with a plugin. I've had a situation when a plugin would work well in one but simply refuse to work in another almost similar app. I suspect gradle.

Well, anything with a name like Gradle has to be suspect ;)
I've had numerous issues with the ImagePicker flutter plugin in particular over the last year or so that always seem to trigger, exacerbate, uncover, poorly-interact-with, etc., the entire Flutter<->Gradle<->Android-build chain.
From the limited-in-the-overall-universe-of-flutter interactions I've had, they all come down being a big(ger?) problem when I use that one, or in some cases Firebase Auth.
Surely a full audit of that (those?) plugin(s) is due...?

So only solution is to put back grandle to 3.6.2?
-keep class androidx.lifecycle.DefaultLifecycleObserver, this does not work for me.

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

This worked for me, but got another crash when tapping on text field, Solved using this issue

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

This worked for me, but got another crash when tapping on text field, Solved using this issue

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

Thanks a lot, this worked for me too

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

Thanks a lot, this worked for me too

hi any luck on this, I am also facing the same issue and not able to resolve.
here is the error log:
java.lang.IllegalAccessError:
at io.flutter.plugins.GeneratedPluginRegistrant.registerWith (GeneratedPluginRegistrant.java:108)
at com.aleo.daksh_app.MainActivity.configureFlutterEngine (MainActivity.java)
at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach (FlutterActivityAndFragmentDelegate.java:58)
at io.flutter.embedding.android.FlutterActivity.onCreate (FlutterActivity.java:13)
at android.app.Activity.performCreate (Activity.java:7458)
at android.app.Activity.performCreate (Activity.java:7448)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1286)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3409)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3614)
at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:86)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2199)
at android.os.Handler.dispatchMessage (Handler.java:112)
at android.os.Looper.loop (Looper.java:216)
at android.app.ActivityThread.main (ActivityThread.java:7625)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:987)

hi any luck on this, I am also facing the same issue and not able to resolve.
here is the error log:
java.lang.IllegalAccessError:
at io.flutter.plugins.GeneratedPluginRegistrant.registerWith (GeneratedPluginRegistrant.java:108)
at com.aleo.daksh_app.MainActivity.configureFlutterEngine (MainActivity.java)
at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach (FlutterActivityAndFragmentDelegate.java:58)
at io.flutter.embedding.android.FlutterActivity.onCreate (FlutterActivity.java:13)
at android.app.Activity.performCreate (Activity.java:7458)
at android.app.Activity.performCreate (Activity.java:7448)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1286)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3409)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3614)
at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:86)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2199)
at android.os.Handler.dispatchMessage (Handler.java:112)
at android.os.Looper.loop (Looper.java:216)
at android.app.ActivityThread.main (ActivityThread.java:7625)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:987)

Just a side comment: the worst thing is I am not able to upload a working release on playstore, as the last working code also rendered the same error on publishing.

Just a side comment: the worst thing is I am not able to upload a working release on playstore, as the last working code also rendered the same error on publishing.

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
Going back to the issue.. DefaultLifecycleObserver is required, so that's the only class I refrain from changing in my proguard rules:

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

While my Gradle config was having an error immediately I noticed my proguard rules behaved as they were caching, or that was what seemed to happen, so I moved those lines of code to the top and things started to work.

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
Going back to the issue.. DefaultLifecycleObserver is required, so that's the only class I refrain from changing in my proguard rules:

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

While my Gradle config was having an error immediately I noticed my proguard rules behaved as they were caching, or that was what seemed to happen, so I moved those lines of code to the top and things started to work.

Faced the same issue. App will freeze on the splash screen. When sending feedback to report the error, it says:
Crash
Exception class name
java.lang.NullPointerException
Source class
io.flutter.plugins.imagepicker.ImagePickerPlugin

To replicate:
image_picker: ^0.6.7+21
classpath 'com.android.tools.build:gradle:4.1.1'
Run flutter build appbundle

Had to downgrade to gradle 3.6.2 to solve the issue.
P.S.
I had gradle 4.1.1 in the first place since Android Studio recommends to upgrade to it. smh

Faced the same issue. App will freeze on the splash screen. When sending feedback to report the error, it says:
Crash
Exception class name
java.lang.NullPointerException
Source class
io.flutter.plugins.imagepicker.ImagePickerPlugin

To replicate:
image_picker: ^0.6.7+21
classpath 'com.android.tools.build:gradle:4.1.1'
Run flutter build appbundle

Had to downgrade to gradle 3.6.2 to solve the issue.
P.S.
I had gradle 4.1.1 in the first place since Android Studio recommends to upgrade to it. smh

Same problem here!

Same problem here!

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
I find all plugin packages in my proguard not to be modified.. -keep class io.flutter.plugin.** { *; }
Where as DefaultLifecycleObserver cannot be found as it got renamed, so therefore it must be kept without changing it.

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

So this is a description to a solution which can come back to us in another plugin as well, or in native development.

Man, I've trying many things, and your answer save my life..

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
I find all plugin packages in my proguard not to be modified.. -keep class io.flutter.plugin.** { *; }
Where as DefaultLifecycleObserver cannot be found as it got renamed, so therefore it must be kept without changing it.

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

So this is a description to a solution which can come back to us in another plugin as well, or in native development.

Man, I've trying many things, and your answer save my life..

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
I find all plugin packages in my proguard not to be modified.. -keep class io.flutter.plugin.** { *; }
Where as DefaultLifecycleObserver cannot be found as it got renamed, so therefore it must be kept without changing it.

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

So this is a description to a solution which can come back to us in another plugin as well, or in native development.

Man, I've trying many things, and your answer save my life..

You don't have to create a debugMini build type when you are in a rush just by replacing the values for minifiedEnable, useProguard, and making sure proguardFiles line is added. This trick of mocking saves you from having to first make a release build and then keep staring at the logcat.

when working with Proguard, always try to test the app thoroughly. There can be edge cases where minifying and uglyfing the code would raise errors at runtime. Here is a good thing to do so you don't have to test out proguard only in release mode.
Make another build type to mock release
buildTypes {
  debugMini {
    initWith debug
    minifyEnabled true
    useProguard true
    pproguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    matchingFallbacks = ['debug']
  }
}

see more here: https://medium.com/androiddevelopers/practical-proguard-rules-examples-5640a3907dc9
I find all plugin packages in my proguard not to be modified.. -keep class io.flutter.plugin.** { *; }
Where as DefaultLifecycleObserver cannot be found as it got renamed, so therefore it must be kept without changing it.

#keep this class for ImagePickerPlugin
-keep class androidx.lifecycle.DefaultLifecycleObserver

So this is a description to a solution which can come back to us in another plugin as well, or in native development.

Man, I've trying many things, and your answer save my life..

You don't have to create a debugMini build type when you are in a rush just by replacing the values for minifiedEnable, useProguard, and making sure proguardFiles line is added. This trick of mocking saves you from having to first make a release build and then keep staring at the logcat.

Use this before using SharedPref
SharedPreferences.setMockInitialValues;

just keep androidx.lifecycle.DefaultLifecycleObserver is enough.
add bellow line to app/proguard-rules.pro
-keep class androidx.lifecycle.DefaultLifecycleObserver

This worked for me. Thanks a lot.

The provided combined solutions solved it for me on android. How can we solve this in ios ?

The provided combined solutions solved it for me on android. How can we solve this in ios ?

You don't use Gradle to compile for iOS, so i don't know what you're asking about. This is an Android issue

This should now be solved by the newly published https://pub.dev/packages/flutter_plugin_android_lifecycle version 2.0.1 (which some plugins such depend on transitively). Doing a flutter pub upgrade and looking for a > flutter_plugin_android_lifecycle 2.0.1 line should resolve the issue.

Thanks @xster!

This should now be solved by the newly published https://pub.dev/packages/flutter_plugin_android_lifecycle version 2.0.1 (which some plugins such depend on transitively). Doing a flutter pub upgrade and looking for a > flutter_plugin_android_lifecycle 2.0.1 line should resolve the issue.

I have a lot of dependencies not updated to null-safety yet so in my case it's still incompatible. but thanks for the info


Write a PHP program to find sum of numbers by recursion

Description
Write a PHP program to find sum of numbers by recursion
Input  : 1 2 3 4 5
Output : 15

How to contribute

Save the solution in program/find_sum_of_numbers_by_recursion.php file
Add find_sum_of_numbers_by_recursion.php file in find-sum-of-numbers-by-recursion folder

!assign

Hey @K1118,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign


Various fix

Everything looks great @liutianlin0121! I added some fixes. Feel free to submit @liutianlin0121 :)
CC @liutianlin0121 @lvwerra

added some missing outputs
annonymized dataset here: https://huggingface.co/datasets/de6l1cu2/lm-human-preferences
made a new repo: https://anonymous.4open.science/r/lm-human-preference-details-temp-8CDD/README.md

removed Costa Huang in pyproject.toml
removed the wandb links in the readme

Awesome, thanks!!

Thank you @liutianlin0121! I did a quick pass over our blog post and it looks great!


[APIM 4] Broken Links - GraphQL Static Query Analyzer

Description:
Following links in [1] are not working.

Query Depth Limitation
Query Complexity Limitation

[1] https://apim.docs.wso2.com/en/latest/design/rate-limiting/graphql-api/overview-query-limits-for-graphql/#static-query-analyzer
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This is fixed now.


Add float function to parse string to floating point value

Please add a float function so that we can convert a string into a floating point number, analogous to the int function for integers.
This will allow us to pass named floating point arguments from a shortcode.
For my use-case, this is to pass a non-integer "aspect ratio" value.  My current workaround is to supply this as a rational two-integer tuple and to perform the division in the template, but is only an approximation when the value is irrational.

Agreed, the addition of a float function would be very useful and also allow a single string (frontmatter) to contain multiple float values using a separator for later expansion/manipulation (template).
Is something similar already on the roadmap?
Many thanks in advance.

Hi from a Hacktoberfestler 👋 I'd like to give implementing this a try!

@x3ro great; it should live in the tpl/cast package; see ToInt for inspiration.
/cc @moorereason


Copy in a way that's supported on Windows.

Your patch that introduced "cp" breaks AppRTC for win development.

LGTM


Support latest websocket transport

This PR Assumes this
https://github.com/apollographql/subscriptions-transport-ws/pull/239
will be merged and realsed as version 0.8.2.
This PR adds support for latest subscription-transport client,
which also adds the option to query / mutate over websocket.
so incase fallbackFetcher is undefined, all operations should go through this interface.

Not relevant when
https://github.com/apollographql/subscriptions-transport-ws/pull/242
get's merged.


v32.5.0

This pull request releases v32.5.0, which will resolve #5235

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] The PR targets the latest branch.
[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

Can one of the admins verify this patch?


Actively Sending Messages

Hi,
I'm currently trying to build an agent, that is supposed to actively send messages to a chat room when certain EC2 instances are running that shouldn't run.
Replying works fine (in the responders), but how can I send a message via the agent actively? I tried:
Hedwig.Robot.send(pid, %{text: "hello world"})
This crashes my agent with a match error.
Best,
Benedikt

Not sure if this question is related to hipchat at all, so I'll post it to the hedwig project as well.

Probably a better place! I responded there:
https://github.com/hedwig-im/hedwig/issues/34


Add config type Class

Two elements: One for a single class and one for a list of classes.

@nilshansen94 Can you please add support for class and class list in the UI.


Request for test dataset that works with QSI prep

Hi,
I would like to request the test dataset compatible with QSI Prep as I am experiencing difficulties with my current datasets while using QSI Prep. I am unsure if the problem lies with the software or the dataset itself. Therefore, I would appreciate if you could provide me with a test dataset to determine the source of the issue and ensure proper functionality with my system. Thank you.

Hi @LikithaBommasani, If you read through this script there are a couple locations where our testing data is downloaded from Box. There are a couple different test datasets available for you to try

Thank you for your reply. I have tested it with the dataset(DSDTI) you provided.
Even then I'm facing these errors. Could you let me know where the problem lies
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
result["result"] = node.run(updatehash=updatehash)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
result = self._run_interface(execute=True)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
return self._run_command(execute)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
raise NodeExecutionError(msg)
nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node synthstrip.
Cmdline:
mri_synthstrip -i /tmp/work/qsiprep_wf/single_subject_PNC_wf/anat_preproc_wf/pad_anat_reference_wf/resample_skulled_to_reference/sub-PNC_T1w_trans.nii.gz -o sub-PNC_T1w_trans_brain.nii.gz -m sub-PNC_T1w_trans_mask.nii.gz
Stdout:
Stderr:
Killed
Traceback:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/interfaces/base/core.py", line 397, in run
runtime = self._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/interfaces/freesurfer.py", line 605, in _run_interface
raise Exception("mri_synthstrip failed!")
Exception: mri_synthstrip failed!
QSIPrep failed: Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
result["result"] = node.run(updatehash=updatehash)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
result = self._run_interface(execute=True)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
return self._run_command(execute)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
raise NodeExecutionError(msg)
nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node synthstrip.
Cmdline:
mri_synthstrip -i /tmp/work/qsiprep_wf/single_subject_PNC_wf/anat_preproc_wf/pad_anat_reference_wf/resample_skulled_to_reference/sub-PNC_T1w_trans.nii.gz -o sub-PNC_T1w_trans_brain.nii.gz -m sub-PNC_T1w_trans_mask.nii.gz
Stdout:
Stderr:
Killed
Traceback:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/interfaces/base/core.py", line 397, in run
runtime = self._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/interfaces/freesurfer.py", line 605, in _run_interface
raise Exception("mri_synthstrip failed!")
Exception: mri_synthstrip failed!
Traceback (most recent call last):
File "/usr/local/miniconda/bin/qsiprep", line 8, in
sys.exit(main())
File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/cli/run.py", line 677, in main
qsiprep_wf.run(**plugin_settings)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/workflows.py", line 638, in run
runner.run(execgraph, updatehash=updatehash, config=self.config)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/base.py", line 178, in run
self._clean_queue(jobid, graph, result=result)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/base.py", line 256, in _clean_queue
raise RuntimeError("".join(result["traceback"]))
RuntimeError: Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
result["result"] = node.run(updatehash=updatehash)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
result = self._run_interface(execute=True)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
return self._run_command(execute)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
raise NodeExecutionError(msg)
nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node synthstrip.
Cmdline:
mri_synthstrip -i /tmp/work/qsiprep_wf/single_subject_PNC_wf/anat_preproc_wf/pad_anat_reference_wf/resample_skulled_to_reference/sub-PNC_T1w_trans.nii.gz -o sub-PNC_T1w_trans_brain.nii.gz -m sub-PNC_T1w_trans_mask.nii.gz
Stdout:
Stderr:
Killed
Traceback:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/interfaces/base/core.py", line 397, in run
runtime = self._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/interfaces/freesurfer.py", line 605, in _run_interface
raise Exception("mri_synthstrip failed!")
Exception: mri_synthstrip failed!
230612-19:47:57,436 nipype.workflow INFO:
[Node] Finished "topup", elapsed time 174.869838s.

this looks like you're running out of memory. What are the specs on the machine you're using and what is your exact qsiprep command?

The QSI prep command :  lbommasani5860$ docker run -i --rm \

-v /Users/lbommasani5860/Desktop/DSDTI:/data:ro
-v /Users/lbommasani5860/Desktop/DSDTI_processed:/out
-v /Users/lbommasani5860/Downloads/license.txt:/out/license.txt
pennbbl/qsiprep:latest /data /out participant
--output_resolution 3
--fs-license-file /out/license.txt
--freesurfer-input /out/sourcedata/freesurfer

I do have low storage space of about 30GB right now

by memory I mean RAM. If you're on a mac you may need to change the docker settings so at least 12GB is available

got it.

with only 8gb memory available you may want to reduce the number of cpus to 1 so multiple tasks don't run concurrently. Depending on your data 8gb may not be enough

Okay thank you I'll try

Could you try using pennbbl/qsiprep:0.18.0 as the image? I added those citations in the tagged version. This warning shouldn't affect your results other than the methods boilerplate in the html report


Snapkit 3.0.0 Release

This will be 3.0.0 of the Snapkit plugin and contains breaking changes for all lower versions, please follow the new README in this branch.
This version updates the native SnapSDK to 2.5.0 on iOS and 2.1.0 on Android.
Closes #6 as BitmojiKit was deprecated with SnapSDK 2.0.0
Fixes #41
Fixes #40 with an upgraded Android SnapSDK
Fixes #45

Quick update: I have updated the native Android side of things and the CreativeKit works great and adds sharing with video back to Android, however LoginKit isn't working at the moment for some unknown reason, I'm looking into it at the moment but Snapchat's error messages aren't exactly the most descriptive.


Custom font and very big result PDF on server

Hello,
I would like to use custom font in my PDF. First tried use base - locally (OSX) works perfectly, but it doesn't work on server (Ubuntu 16.04). Then changed url to hostname. It works fine now, but result PDF file is very big (30 MB). When I use the same code locally using base, file has only about 180 KB.

Hello,
I am also facing the same issue. The resulted pdf generated from windows works fine but when it is run from ubuntu it increases the size of font which makes it overflow the page. There is no provision to custom set the font size.

The file is huge because there is no text, but all pages as images.
But why... don't know.

I think I found solution - I installed fonts locally on server instead of using font-face with url in CSS and base on PDF settings. Now it's works very fast and file is real PDF with text.


Alternative integration method

Hi @entjos,
First of all: thank you for implementing the methods in the {JointFPM} package!
This PR add a second option for the numerical integration needed to predict the mean number of events (predict(, type = "mean_no")). This uses the rmutil::int function, which does vectorised Romberg integration.
Specifically, this adds an argument to the predict.JointFPM() function, named use_rmutil, which triggers the alternative integration method. Ideally, I would remove this and only use a single integration method but I find it useful for comparing between the two!
I haven't checked if this breaks some other stuff, but I run R CMD check and it did pass with no issues. Results are pretty much equivalent to the original implementation, but ~4 times faster (in my – admittedly – not very comprehensive testing), using the example from the README file:
library(JointFPM)
library(data.table) # For data preparations

# Load bladder cancer dataset from survival package
bldr_df <- as.data.table(survival::bladder1)
bldr_df <- bldr_df[, .(id, treatment, start, stop, status)]

# Define dataset for competing event times
bldr_ce <- bldr_df[, .SD[stop == max(stop)], by = id]

bldr_ce[, `:=`(
  ce = 1,
  re = 0,
  event = as.numeric(status %in% 2:3),
  start = 0
)]

# Define dataset for bladder cancer recurrences
bldr_re <- bldr_df[
  ,
  `:=`(
    ce = 0,
    re = 1,
    event = as.numeric(status == 1)
  )
]

# Combine datasets into one stacked dataset

bldr_stacked <- rbindlist(list(bldr_ce, bldr_re))

bldr_stacked[, `:=`(
  pyridoxine = as.numeric(treatment == "pyridoxine"),
  thiotepa = as.numeric(treatment == "thiotepa")
)]

bldr_stacked$stop[bldr_stacked$stop == 0] <- 1 # Add one day survival

# Print stacked dataset
head(bldr_stacked)
#>    id treatment start stop status ce re event pyridoxine thiotepa
#> 1:  1   placebo     0    1      3  1  0     1          0        0
#> 2:  2   placebo     0    1      3  1  0     1          0        0
#> 3:  3   placebo     0    4      0  1  0     0          0        0
#> 4:  4   placebo     0    7      0  1  0     0          0        0
#> 5:  5   placebo     0   10      3  1  0     1          0        0
#> 6:  6   placebo     0   10      3  1  0     1          0        0

bldr_model <- JointFPM(
  Surv(
    time = start,
    time2 = stop,
    event = event,
    type = "counting"
  ) ~ 1,
  re_model = ~ pyridoxine + thiotepa,
  ce_model = ~ pyridoxine + thiotepa,
  re_indicator = "re",
  ce_indicator = "ce",
  df_ce = 3,
  df_re = 3,
  tvc_ce_terms = list(
    pyridoxine = 2,
    thiotepa = 2
  ),
  tvc_re_terms = list(
    pyridoxine = 2,
    thiotepa = 2
  ),
  cluster = "id",
  data = bldr_stacked
)

t0 <- Sys.time()
predict(bldr_model,
  newdata = data.frame(
    pyridoxine = 1,
    thiotepa = 0
  ),
  t = c(10, 20, 50),
  use_rmutil = FALSE
)
#>   stop       fit       lci       uci
#> 1   10 0.6068153 0.2866777 0.9269529
#> 2   20 1.1156503 0.5334426 1.6978580
#> 3   50 2.3789320 1.0343114 3.7235526
t1 <- Sys.time()
t1 - t0
#> Time difference of 45.74832 secs

# Alternative:
t0 <- Sys.time()
predict(bldr_model,
  newdata = data.frame(
    pyridoxine = 1,
    thiotepa = 0
  ),
  t = c(10, 20, 50),
  use_rmutil = TRUE
)
#>   stop       fit       lci       uci
#> 1   10 0.6068452 0.2866913 0.9269992
#> 2   20 1.1157394 0.5335082 1.6979705
#> 3   50 2.3793386 1.0346551 3.7240220
t1 <- Sys.time()
t1 - t0
#> Time difference of 12.66111 secs

Created on 2023-07-13 with reprex v2.0.2
Happy to have a chat about this at some point if you think it'd be useful! 😄
Many thanks again,
Alessandro

Hi @ellessenne,
thank you for taking the time to look at the code and coming up with this great suggestion to use Romberg integration instead of Gaussian quadrature!
I just looked at your code and re-run a simulation study and some examples using Romberg integration instead of Gaussian quadrature. Using Romberg integration definitely comes with quite some improvements in computation time as it only requires 18 function evaluations instead of 100 evaluations which I set as the default for the Gaussian quadrature. The results of the simulation study and the example are kind of identical to the previous results using Gaussian quadrature for the integration. I, hence, think using Romberg integration makes a lot of sense.
However, when running the example, I realised that the rmutil::int function throws an error and stops proceeding if the lower bound of the integral is equal to the upper bound of the integral. This happened to me when I supplied a sequence of time points from 0 to 10  (including 0) to the t argument of the predict.JointFPM() function. I, therefore, added one commit that deals with this situation and adds a very small number to every 0 that is supplied to the t argument.
Additionally, I added a commit that deleted the use_rmutil switch and instead made the use of rmutil::int() the default.
I'm looking forward to discussing more about the project with you on Monday :)
Best,
Joshua


Add 5 Icons, Link 1

Description

Added 5 icons, linked 1.
Icons addition information
Added
Australia Post (au.com.auspost.android) - Round
BOM Weather (au.gov.bom.metview) - Round
Camera Assistant (com.samsung.android.app.cameraassistant) - Square
FlightStats (com.conducivetech.android.traveler) - Rectangle
PlaneFinder (com.pinkfroot.planefinderfree) - Square
Linked
Fossify Phone (org.fossify.phone → dialer.svg)
Contributor's checklist

[x] I have followed the Lawnicons Guidelines
[x] I have ensured that Lawnicons builds correctly
[x] I am willing to make changes to my icons if someone suggests changes

Thanks for all the feedback and help with these!
I hope they look a bit better now.


Exposing large data blobs (such as images) as URLs

Description

Current State *

LLMs such as OpenAI ChatGPT can show images with markdown links. LLMs can not work with binary data directly (images, videos, pdfs, excels..) as they are not short tokenized text.
For an action to return an image, that would be displayed by ChatGPT currently a third party hosting service is needed. This then can be used to generate a URL for an image:

This method adds another service into loop. This is a security concern when dealing with private data. I personally would be much more happy with just Action Server and OpenAI in the loop.
It is also inconvenience as that requires setting up account to that third party service and learning to use their APIs.
Describe the solution you'd like
I propose that actions and Action Server will provide an sdk to allow exposing large data blobs from actions as GET URL:s.
As working with "large" binary data is pretty common I would think this would be really useful.
from robocorp.actions import action, reference_url

@action
def make_an_image():
    image = ...
    url = reference_url(image)
    return f"Image is at {url}"

Describe alternatives you've considered
Alternative is the use of third party file sharing services or user themselves making their own methods.

This issue has been moved here, under Sema4AI/actions repository.


FreeBSD port

Get Keylime running on FreeBSD

a first proof of concept https://gist.github.com/nabilschear/4527fa3adf792085879dcbf4f0d30481


VertexAI PaLM2 does not support Authentication Credentials

VertexAI PaLM2 Chat https://docs.spring.io/spring-ai/reference/api/clients/vertexai-palm2-chat.html does not support authentication by gcloud (gcloud auth application-default login).
I get following error when not defining api-key:
java.lang.RuntimeException: 403 - ResponseError[error=Error[message=Method doesn't allow unregistered callers (callers without established identity). Please use API Key or other form of API consumer identity to call this API., code=403, status=PERMISSION_DENIED]]

As this is the same mechanism, I think it won't support GKE IAM authentication as well.
VertexAI Gemini Chat supports this authentication already:
https://docs.spring.io/spring-ai/reference/api/clients/vertexai-gemini-chat.html#_prerequisites
In documentation I see, that API for PaLM2 supports this method of authentication:
https://console.cloud.google.com/vertex-ai/publishers/google/model-garden/text-bison ("Setup the PaLM 2 Text Bison (curl)")

VertexAI PaLM2 is deprecated and it's being decommissioned by Google. Therefore, it's being removed from Spring AI as well (see https://github.com/spring-projects/spring-ai/issues/924).


Improve API usage of BitmapFont.from

Overview
This change is mostly about improving and streamlining ergonomics using the new BitmapFont.from API (#6600).
Also, did some minor code organization and documentation fixes.
Before
Previously you optionally defined the font name and no chars were set by default.
const font = BitmapFont.from({ chars: BitmapFont.ALPHANUMERIC }, {
    fill: "#808080",
    fontFamily: "Roboto-Black",
    fontSize: 33,
});
BitmapFont.available.TitleFont = font;

After
Now, font is installed, name is required, and chars are optional (defaults to ALPHANUMERIC).
BitmapFont.from("TitleFont", {
    fill: "#808080",
    fontFamily: "Roboto-Black",
    fontSize: 33,
});

Now, if you want to change something on the fly, regenerating the font is as easy as calling BitmapFont.from again with some new style options.
const style = new TextStyle({
    fill: "#808080",
    fontFamily: "Roboto-Black",
    fontSize: 33,
});
BitmapFont.from("TitleFont", style);
style.fontSize = 14;
BitmapFont.from("TitleFont", style); // rerenders font!

Demo
https://jsfiddle.net/bigtimebuddy/wt9szqp6/
Changed

Both these signatures are now supported BitmapFont.from(name, style) and BitmapFont.from(options, style)
Destroying a BitmapFont now also destroys the page textures, not just the glyph textures
Field name is required for BitmapFont.from for ease of use.
When calling BitmapFont.from, it will override any existing font by default with the same name, making it easier to regenerate the font.
Exposed default options via BitmapFont.defaultOptions in case users want to change this globally.
Moved utilities drawGlyph and processCharData to their own utilities. Still need a cleanup on generateFillStyle and drawGlyph with Text. Probably better for a follow-up PR.

Codecov Report

Merging #6640 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6640   +/-   ##
=======================================
  Coverage   82.34%   82.34%
=======================================
  Files          37       37
  Lines        1897     1897
=======================================
  Hits         1562     1562
  Misses        335      335

Continue to review full report at Codecov.

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

One other thing I discovered was the use of Array.prototype.find which is not supported in IE will need to replace that with something more compatible.

Good shout @themoonrate. Fixed.


Orphaned Database File

DBADASH does not track orphaned database files. When databases are detached sometimes DBAs forget to delete them later. This check should let DBA know that there are orphaned database files.

Thanks for the suggestion.  I don't think there is an easy way to detect orphaned files from T-SQL.  Scanning the file system for database files that are not attached is possible but quite expensive.  Not sure if this would be possible remotely or not.  I'm unlikely to add this feature.

Dbachecks powershell module has orphaned files check to do that
On Thu, Oct 10, 2024, 2:16 PM David Wiseman @.***>
wrote:

Thanks for the suggestion. I don't think there is an easy way to detect
orphaned files from T-SQL. Scanning the file system for database files that
are not attached is possible but quite expensive. Not sure if this would be
possible remotely or not. I'm unlikely to add this feature.
—
Reply to this email directly, view it on GitHub
https://github.com/trimble-oss/dba-dash/issues/1066#issuecomment-2406053099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGN5RXZTZPO6QHIPJNRXSPLZ23VELAVCNFSM6AAAAABPXEMEHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBWGA2TGMBZHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

It looks like that is using Find-DbaOrphanedFile.


NX Feat: Favorite Devices

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feat

What is the current behavior? (You can also link to an open issue here)
dojot/dojot#2412

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Is there any issue related to this PR in other repository? (such as dojot/dojot)

Other information:

It worked very well. I just want to say that we can (in a future PR) add something in device cards to indicate that is, in fact, a device card and not a link to a page as the other cards.


profile: cannot choose color that begins with 0

Describe the bug, optionally with screenshots
Neither updating my personal profile nor the group profile for a group to which I have admin rights works. After making changes and hitting save, it just hangs indefinitely.
To Reproduce
Steps to reproduce the behavior:

Go to profile
Make changes
Hit save
Wait
Verbose logs in dojo suggest that some agents received an update, but aren't doing anything with it apparently

Expected behavior
Changes to profile are updated and visible.
Additional context:

Ship type = planet, star
Instance type = self-hosted planet, VPS-hosted star
Chromium-based browser on Pop!_OS

Can't repro this one. Anyone else seeing this?

making admin changes to the group may be #1386.
i'm unable to reproduce the user profile part however.
please:

clear browser cache + refresh
shut down your ship + restart
try this again, and either copy/paste or send screenshots of both browser console and dojo

hmm – it appears contact-store isn't loading in properly if you can't see your own profile details at all, this is useful thank you

Update: my error is unlike @jyng and appears to actually be a sigil color-picker error. I think it's a parser error - I'm unable to pick any color which begins with a 0.

Just noticed this today, I can change profile color to anything that doesn't start with 0, but eg #0000FF turns into #FFFFFF

Able to repro, investigating

it looks like the frontend is sending the correct payload as per the previous screenshot; confirming that the agent state reflects the bogus value:

in the frontend, if a color value received in a subscription update is not valid, it is right-padded with F by normalizeUrbitColor; hence why we see a color "change" after saving it. in other words, poking { color: '00f0ff' } is saved in agent state as 0xf0ff, then "normalized" to 'f0ffff'


Enable External ADS1X15 ADC

Enabling external ADC instead of MCUs' internal ADCs. Indispensible for a great performance.

Tested on ESP32 with ADS1115 ADC. Displayed through HW I2C SSD1306, with an example code of mahjongAsst_U8X8.
Resistance measurements greatly improved.


Use ParseException::dump and MapParseException::dump in shims

Right now the shims construct their own error message when converting these exceptions, but there is an existing dump method that does the same. Need to make sure color is turned off before doing this.

done


repeated data element cannot be bound when alias is used

works

i.e data is accessible in the click handler

{{data.name}}

does't work

i.e data is NOT accessible in the click handler

{{item.name}}

By design. If you alias, the data property is discarded and not used.


LLVM 17.0.0.rc1

Still no new version of cctools: https://github.com/tpoechtrager/cctools-port/issues/134
Waiting for builds from https://github.com/conda-forge/clangdev-feedstock/pull/237

Seems that clang 16 (which is pulled in as we're unpinning the compilers on osx) is not compatible with MacOS 10.9 anymore - shocking. 😆

Seems that clang 16 (which is pulled in as we're unpinning the compilers on osx) is not compatible with MacOS 10.9 anymore - shocking. 😆

clang 16 and 17rc4 can both compile for MacOS 10.9, what error are you getting?

oh wait you probobly meant when compiling on-device


Use ThreadSafeChromeUtils.nondeterministicGetWeakMapKeys. Fixes #2416.

Components.utils.nondeterministicGetWeakMapKeys was removed:
https://hg.mozilla.org/mozilla-central/rev/7c22b95c0e29

This change is

Thanks!


QA: inserting "test" folder and moving files in src/ to src/test/

Signed-off-by: harishmunjulur<EMAIL_ADDRESS>

rhel 8 : http://pulpito.ceph.redhat.com/hmunjulu-2020-04-03_20:03:03-rbd:librbd-nautilus-distro-basic-argo/
rhel 7: http://pulpito.ceph.redhat.com/hmunjulu-2020-04-03_20:01:56-rbd:librbd-nautilus-distro-basic-argo/


How to make Django and Flask Microservices Work Together

Topic Suggestion
Writing sample(s):
https://www.section.io/engineering-education/authors/muhammed-ali/
Proposal Submission
Proposed title of article
How to Make Django and Flask Microservices Work Together
Proposed article introduction
This article will go through how the reader can potentially build microservices with Django and Flask and connect them with Docker and Redis. This will be a blog application that uses Django for its backend feature and Flask to Display the Data to the users.
ONLY viable topics to pick from:

API
Containers
Languages

Key takeaways

Build a microservice with Django
Build a microservice with Flask
Connect the two microservices with Redis and Docker

Article quality
This is a unique article

Thank you for your response and we thank you for submitting your topic. After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations as previously mentioned on your topic form by our content moderator.
We typically refrain from publishing content that is covered widely on the net or other blogs. As we're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
https://www.google.com/search?q=How+to+Make+Django+and+Flask+Microservices+Work+Together&oq=How+to+Make+Django+and+Flask+Microservices+Work+Together&aqs=chrome..69i57j69i61.284j0j9&sourceid=chrome&ie=UTF-8


cmd/compile: bad handling of closures in generic body

package main

//go:noinline
func f[T any]() {
	x := 5
	g := func() int { return x }
	g()
}

func main() {
	f[int]()
}

generates
$ go tool compile -G=3 tmp.go
panic: interface conversion: interface {} is nil, not *escape.location
goroutine 1 [running]:
cmd/compile/internal/escape.(*batch).oldLoc(...)
	/Users/khr/sandbox/ro/src/cmd/compile/internal/escape/escape.go:1311

A small debugging print in (*batch).oldLoc at that line number indicates the variable without a location is ~r0.
There's nothing directly related to generics going on here, just something I suspect triggered by the slightly different phase ordering when processing generic functions.
@dancsales

This appears to be because we're not copying the formal parameters of a closure. When we copy a closure, we're not making new formal parameters for the closure because its type doesn't have any generic parameters. But we do make a copy of the formal parameter when we encounter it in the body of the closure. Escape analysis treats these two Names as different, and one of them was never assigned a location.
I think we need to copy the type of the closure always, even when it doesn't have any type parameters. it's not that simple though, or I would have fixed it already :(. Still looking.


crypto/tls: Reject ECH on invalid encapsulated key

The ECH provider aborts if it gets an encapsulated key it's unable to parse, causing the ECH server to abort with an "internal_error" alert. This condition can be triggered by a client that generates a GREASE ECH extension with a config_id that happens to match a known config, but uses the incorrect KEM algorithm. This changes the server behavior so that it rejects instead.
The key text from the spec that tells us what to do here is in Section 7.1 (Client-facing Server Behavior): "If decryption fails, the server continues to the next candidate ECHConfig." Being unable to parse the KEM encapsulated key certainly counts as a decryption failure; and because we have exhausted our list of ECH configs, we must reject.

TODO(@cjpatton) Replace the CIRCL regression test with an ECH unit test for the following case: he client uses an invalid ECH config with a config_id matching a valid ECH config, but with a different KEM algorithm. The client-facing server should reject. (See https://github.com/cloudflare/go/pull/95#discussion_r672450095.)
I'll take care of this once #89 and #96 land.

Rebased.

Rebased and squashed.

Rebased.

Rebased and squashed, waiting on CI.

Rebased after merging https://github.com/cloudflare/go/pull/96, letting CI run one more time.


Index out of bounds at huffman_tree.rs line 252 when reading invalid data

When trying to decompress an invalid file, I get the following panic. I'll post the reproducing steps ASAP.
thread '<unnamed>' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deflate64-0.1.7/src/huffman_tree.rs:252:21:
index out of bounds: the len is 64 but the index is 64
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
==4066== ERROR: libFuzzer: deadly signal
    #0 0x561a8eb7d991  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x20a991) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #1 0x561a8eeb250e  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x53f50e) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #2 0x561a8eeba959  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x547959) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #3 0x7f2ecfa4251f  (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #4 0x7f2ecfa969fb  (/lib/x86_64-linux-gnu/libc.so.6+0x969fb) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #5 0x7f2ecfa42475  (/lib/x86_64-linux-gnu/libc.so.6+0x42475) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #6 0x7f2ecfa287f2  (/lib/x86_64-linux-gnu/libc.so.6+0x287f2) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #7 0x561a8ef58a06  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5e5a06) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #8 0x561a8ead97f6  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x1667f6) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #9 0x561a8ee9d014  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x52a014) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #10 0x561a8ef4daaf  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5daaaf) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #11 0x561a8ef4d7f1  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5da7f1) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #12 0x561a8ef4ada5  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5d7da5) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #13 0x561a8ef4d523  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5da523) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #14 0x561a8eadc184  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x169184) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #15 0x561a8eadc371  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x169371) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #16 0x561a8eddc3a4  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x4693a4) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #17 0x561a8eddab1b  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x467b1b) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #18 0x561a8ede4189  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x471189) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #19 0x561a8edde7da  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x46b7da) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #20 0x561a8edddb50  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x46ab50) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #21 0x561a8ec35c3a  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x2c2c3a) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #22 0x561a8ec53552  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x2e0552) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #23 0x561a8ec56f34  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x2e3f34) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #24 0x561a8ec5ebc9  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x2ebbc9) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #25 0x561a8ebb1bb4  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x23ebb4) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #26 0x561a8ebc5868  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x252868) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #27 0x561a8ebb3326  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x240326) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #28 0x561a8ebe3432  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x270432) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #29 0x561a8ebe4272  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x271272) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #30 0x561a8ebe3c50  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x270c50) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #31 0x561a8ee97fff  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x524fff) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #32 0x561a8ee9d227  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x52a227) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #33 0x561a8ee9c74b  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x52974b) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #34 0x561a8eebaea5  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x547ea5) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #35 0x561a8eec02c3  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x54d2c3) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #36 0x561a8eec12b8  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x54e2b8) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #37 0x561a8eec36a7  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x5506a7) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #38 0x561a8eeabf3f  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x538f3f) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #39 0x561a8eadc9b6  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x1699b6) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
    #40 0x7f2ecfa29d8f  (/lib/x86_64-linux-gnu/libc.so.6+0x29d8f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #41 0x7f2ecfa29e3f  (/lib/x86_64-linux-gnu/libc.so.6+0x29e3f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
    #42 0x561a8eadcb54  (/home/runner/work/zip-next/zip-next/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_read+0x169b54) (BuildId:<PHONE_NUMBER>e50016bf6b7ede80d99caa605d2588)
NOTE: libFuzzer has rudimentary signal handlers.
      Combine libFuzzer with AddressSanitizer or similar for better crash reports.
SUMMARY: libFuzzer: deadly signal

Could you show us example file that cuses this problem?

Still working on obtaining an example. At the time I filed this report, my CI workflow had two bugs, one that prevented it from uploading the failed test cases due to the workflow-level timeout and another that prevented me from relaunching it manually. Now that both bugs are fixed, I'll be repeating the CI run until the error recurs.

Update: Here's an example input to (Deflate64Decoder as Read)::read (still wrestling with RustRover's debugger to try to get it in a more usable format):
[0] = {u8} 69 [0x45]
[1] = {u8} 255 [0xff]
[2] = {u8} 255 [0xff]
[3] = {u8} 255 [0xff]
[4] = {u8} 255 [0xff]
[5] = {u8} 255 [0xff]
[6] = {u8} 255 [0xff]
[7] = {u8} 69 [0x45]
[8] = {u8} 69 [0x45]
[9] = {u8} 69 [0x45]
[10] = {u8} 69 [0x45]
[11] = {u8} 69 [0x45]
[12] = {u8} 69 [0x45]
[13] = {u8} 61 [0x3d]
[14] = {u8} 61 [0x3d]
[15] = {u8} 61 [0x3d]
[16] = {u8} 61 [0x3d]
[17] = {u8} 61 [0x3d]
[18] = {u8} 61 [0x3d]
[19] = {u8} 61 [0x3d]
[20] = {u8} 61 [0x3d]
[21] = {u8} 61 [0x3d]
[22] = {u8} 61 [0x3d]
[23] = {u8} 61 [0x3d]
[24] = {u8} 61 [0x3d]
[25] = {u8} 61 [0x3d]
[26] = {u8} 61 [0x3d]
[27] = {u8} 61 [0x3d]
[28] = {u8} 61 [0x3d]
[29] = {u8} 61 [0x3d]
[30] = {u8} 61 [0x3d]
[31] = {u8} 42 [0x2a]
[32] = {u8} 42 [0x2a]
[33] = {u8} 42 [0x2a]
[34] = {u8} 42 [0x2a]
[35] = {u8} 42 [0x2a]
[36] = {u8} 42 [0x2a]
[37] = {u8} 42 [0x2a]
[38] = {u8} 42 [0x2a]
[39] = {u8} 42 [0x2a]
[40] = {u8} 42 [0x2a]
[41] = {u8} 42 [0x2a]
[42] = {u8} 42 [0x2a]
[43] = {u8} 42 [0x2a]
[44] = {u8} 42 [0x2a]
[45] = {u8} 69 [0x45]
[46] = {u8} 69 [0x45]
[47] = {u8} 69 [0x45]
[48] = {u8} 69 [0x45]
[49] = {u8} 68 [0x44]
[50] = {u8} 69 [0x45]
[51] = {u8} 240 [0xf0]
[52] = {u8} 69 [0x45]
[53] = {u8} 69 [0x45]
[54] = {u8} 69 [0x45]
[55] = {u8} 69 [0x45]
[56] = {u8} 69 [0x45]
[57] = {u8} 69 [0x45]
[58] = {u8} 69 [0x45]
[59] = {u8} 69 [0x45]
[60] = {u8} 69 [0x45]
[61] = {u8} 69 [0x45]
[62] = {u8} 69 [0x45]
[63] = {u8} 69 [0x45]
[64] = {u8} 69 [0x45]
[65] = {u8} 69 [0x45]
[66] = {u8} 69 [0x45]
[67] = {u8} 69 [0x45]
[68] = {u8} 69 [0x45]
[69] = {u8} 6 [0x6]
[70] = {u8} 5 [0x5]
[71] = {u8} 75 [0x4b]
[72] = {u8} 80 [0x50]
[73] = {u8} 69 [0x45]
[74] = {u8} 69 [0x45]
[75] = {u8} 69 [0x45]
[76] = {u8} 69 [0x45]
[77] = {u8} 69 [0x45]
[78] = {u8} 69 [0x45]
[79] = {u8} 69 [0x45]
[80] = {u8} 69 [0x45]
[81] = {u8} 69 [0x45]
[82] = {u8} 69 [0x45]
[83] = {u8} 69 [0x45]
[84] = {u8} 69 [0x45]
[85] = {u8} 69 [0x45]
[86] = {u8} 69 [0x45]
[87] = {u8} 69 [0x45]
[88] = {u8} 69 [0x45]
[89] = {u8} 69 [0x45]
[90] = {u8} 69 [0x45]
[91] = {u8} 69 [0x45]
[92] = {u8} 69 [0x45]
[93] = {u8} 69 [0x45]
[94] = {u8} 69 [0x45]
[95] = {u8} 69 [0x45]
[96] = {u8} 69 [0x45]
[97] = {u8} 69 [0x45]
[98] = {u8} 69 [0x45]
[99] = {u8} 69 [0x45]
[100] = {u8} 69 [0x45]
[101] = {u8} 69 [0x45]
[102] = {u8} 69 [0x45]
[103] = {u8} 69 [0x45]
[104] = {u8} 69 [0x45]
[105] = {u8} 69 [0x45]
[106] = {u8} 69 [0x45]
[107] = {u8} 62 [0x3e]
[108] = {u8} 69 [0x45]
[109] = {u8} 69 [0x45]
[110] = {u8} 69 [0x45]
[111] = {u8} 69 [0x45]
[112] = {u8} 69 [0x45]
[113] = {u8} 69 [0x45]
[114] = {u8} 69 [0x45]
[115] = {u8} 1 [0x1]
[116] = {u8} 0 [0x0]
[117] = {u8} 0 [0x0]
[118] = {u8} 0 [0x0]
[119] = {u8} 0 [0x0]
[120] = {u8} 0 [0x0]
[121] = {u8} 0 [0x0]
[122] = {u8} 16 [0x10]
[123] = {u8} 69 [0x45]
[124] = {u8} 69 [0x45]
[125] = {u8} 69 [0x45]
[126] = {u8} 69 [0x45]
[127] = {u8} 69 [0x45]
[128] = {u8} 69 [0x45]
[129] = {u8} 69 [0x45]
[130] = {u8} 69 [0x45]
[131] = {u8} 69 [0x45]
[132] = {u8} 69 [0x45]
[133] = {u8} 69 [0x45]
[134] = {u8} 69 [0x45]
[135] = {u8} 236 [0xec]
[136] = {u8} 236 [0xec]
[137] = {u8} 236 [0xec]
[138] = {u8} 236 [0xec]
[139] = {u8} 236 [0xec]
[140] = {u8} 236 [0xec]
[141] = {u8} 236 [0xec]
[142] = {u8} 236 [0xec]
[143] = {u8} 236 [0xec]
[144] = {u8} 236 [0xec]
[145] = {u8} 236 [0xec]
[146] = {u8} 236 [0xec]
[147] = {u8} 236 [0xec]
[148] = {u8} 236 [0xec]
[149] = {u8} 236 [0xec]
[150] = {u8} 236 [0xec]
[151] = {u8} 236 [0xec]
[152] = {u8} 236 [0xec]
[153] = {u8} 236 [0xec]
[154] = {u8} 236 [0xec]
[155] = {u8} 236 [0xec]
[156] = {u8} 236 [0xec]
[157] = {u8} 236 [0xec]
[158] = {u8} 236 [0xec]
[159] = {u8} 236 [0xec]
[160] = {u8} 236 [0xec]
[161] = {u8} 236 [0xec]
[162] = {u8} 236 [0xec]
[163] = {u8} 236 [0xec]
[164] = {u8} 236 [0xec]
[165] = {u8} 236 [0xec]
[166] = {u8} 236 [0xec]
[167] = {u8} 236 [0xec]
[168] = {u8} 236 [0xec]
[169] = {u8} 236 [0xec]
[170] = {u8} 236 [0xec]
[171] = {u8} 236 [0xec]
[172] = {u8} 236 [0xec]
[173] = {u8} 236 [0xec]
[174] = {u8} 236 [0xec]
[175] = {u8} 236 [0xec]
[176] = {u8} 236 [0xec]
[177] = {u8} 236 [0xec]
[178] = {u8} 129 [0x81]
[179] = {u8} 129 [0x81]
[180] = {u8} 129 [0x81]
[181] = {u8} 129 [0x81]
[182] = {u8} 129 [0x81]
[183] = {u8} 129 [0x81]
[184] = {u8} 129 [0x81]
[185] = {u8} 129 [0x81]
[186] = {u8} 129 [0x81]
[187] = {u8} 129 [0x81]
[188] = {u8} 129 [0x81]
[189] = {u8} 129 [0x81]
[190] = {u8} 129 [0x81]
[191] = {u8} 129 [0x81]
[192] = {u8} 7 [0x7]
[193] = {u8} 5 [0x5]
[194] = {u8} 75 [0x4b]
[195] = {u8} 80 [0x50]
[196] = {u8} 129 [0x81]
[197] = {u8} 129 [0x81]
[198] = {u8} 129 [0x81]
[199] = {u8} 129 [0x81]
[200] = {u8} 129 [0x81]
[201] = {u8} 48 [0x30]
[202] = {u8} 1 [0x1]
[203] = {u8} 0 [0x0]
[204] = {u8} 0 [0x0]
[205] = {u8} 0 [0x0]
[206] = {u8} 0 [0x0]
[207] = {u8} 0 [0x0]
[208] = {u8} 0 [0x0]
[209] = {u8} 129 [0x81]
[210] = {u8} 129 [0x81]
[211] = {u8} 129 [0x81]
[212] = {u8} 129 [0x81]
[213] = {u8} 129 [0x81]
[214] = {u8} 129 [0x81]
[215] = {u8} 129 [0x81]
[216] = {u8} 129 [0x81]
[217] = {u8} 129 [0x81]
[218] = {u8} 129 [0x81]
[219] = {u8} 129 [0x81]
[220] = {u8} 129 [0x81]
[221] = {u8} 129 [0x81]
[222] = {u8} 129 [0x81]
[223] = {u8} 129 [0x81]
[224] = {u8} 129 [0x81]
[225] = {u8} 129 [0x81]
[226] = {u8} 129 [0x81]
[227] = {u8} 129 [0x81]
[228] = {u8} 129 [0x81]
[229] = {u8} 129 [0x81]
[230] = {u8} 129 [0x81]
[231] = {u8} 129 [0x81]
[232] = {u8} 129 [0x81]
[233] = {u8} 129 [0x81]
[234] = {u8} 0 [0x0]
[235] = {u8} 0 [0x0]
[236] = {u8} 0 [0x0]
[237] = {u8} 0 [0x0]
[238] = {u8} 0 [0x0]
[239] = {u8} 69 [0x45]
[240] = {u8} 69 [0x45]
[241] = {u8} 69 [0x45]
[242] = {u8} 69 [0x45]
[243] = {u8} 69 [0x45]
[244] = {u8} 69 [0x45]
[245] = {u8} 61 [0x3d]
[246] = {u8} 43 [0x2b]
[247] = {u8} 61 [0x3d]
[248] = {u8} 61 [0x3d]
[249] = {u8} 61 [0x3d]
[250] = {u8} 61 [0x3d]
[251] = {u8} 61 [0x3d]
[252] = {u8} 61 [0x3d]
[253] = {u8} 61 [0x3d]
[254] = {u8} 61 [0x3d]
[255] = {u8} 61 [0x3d]
[256] = {u8} 61 [0x3d]
[257] = {u8} 61 [0x3d]
[258] = {u8} 61 [0x3d]
[259] = {u8} 61 [0x3d]
[260] = {u8} 61 [0x3d]
[261] = {u8} 61 [0x3d]
[262] = {u8} 61 [0x3d]
[263] = {u8} 61 [0x3d]
[264] = {u8} 61 [0x3d]
[265] = {u8} 61 [0x3d]
[266] = {u8} 61 [0x3d]
[267] = {u8} 61 [0x3d]
[268] = {u8} 61 [0x3d]
[269] = {u8} 61 [0x3d]
[270] = {u8} 61 [0x3d]
[271] = {u8} 61 [0x3d]
[272] = {u8} 61 [0x3d]
[273] = {u8} 61 [0x3d]
[274] = {u8} 61 [0x3d]
[275] = {u8} 61 [0x3d]
[276] = {u8} 61 [0x3d]
[277] = {u8} 61 [0x3d]
[278] = {u8} 61 [0x3d]
[279] = {u8} 61 [0x3d]
[280] = {u8} 69 [0x45]
[281] = {u8} 69 [0x45]
[282] = {u8} 69 [0x45]
[283] = {u8} 69 [0x45]
[284] = {u8} 69 [0x45]
[285] = {u8} 69 [0x45]
[286] = {u8} 69 [0x45]
[287] = {u8} 69 [0x45]
[288] = {u8} 69 [0x45]
[289] = {u8} 69 [0x45]
[290] = {u8} 69 [0x45]
[291] = {u8} 69 [0x45]
[292] = {u8} 69 [0x45]
[293] = {u8} 69 [0x45]
[294] = {u8} 69 [0x45]
[295] = {u8} 69 [0x45]
[296] = {u8} 192 [0xc0]
[297] = {u8} 192 [0xc0]
[298] = {u8} 192 [0xc0]
[299] = {u8} 192 [0xc0]
[300] = {u8} 192 [0xc0]
[301] = {u8} 192 [0xc0]
[302] = {u8} 192 [0xc0]
[303] = {u8} 192 [0xc0]
[304] = {u8} 0 [0x0]
[305] = {u8} 35 [0x23]
[306] = {u8} 0 [0x0]
[307] = {u8} 0 [0x0]
[308] = {u8} 0 [0x0]
[309] = {u8} 0 [0x0]
[310] = {u8} 0 [0x0]
[311] = {u8} 0 [0x0]
[312] = {u8} 5 [0x5]
[313] = {u8} 6 [0x6]
[314] = {u8} 0 [0x0]
[315] = {u8} 0 [0x0]
[316] = {u8} 1 [0x1]
[317] = {u8} 0 [0x0]
[318] = {u8} 0 [0x0]
[319] = {u8} 0 [0x0]
[320] = {u8} 9 [0x9]
[321] = {u8} 4 [0x4]
[322] = {u8} 253 [0xfd]
[323] = {u8} 255 [0xff]
[324] = {u8} 6 [0x6]
[325] = {u8} 5 [0x5]
[326] = {u8} 75 [0x4b]
[327] = {u8} 80 [0x50]
[328] = {u8} 0 [0x0]
[329] = {u8} 0 [0x0]
[330] = {u8} 0 [0x0]
[331] = {u8} 2 [0x2]
[332] = {u8} 0 [0x0]
[333] = {u8} 132 [0x84]
[334] = {u8} 255 [0xff]
[335] = {u8} 255 [0xff]
[336] = {u8} 255 [0xff]
[337] = {u8} 107 [0x6b]
[338] = {u8} 1 [0x1]
[339] = {u8} 0 [0x0]
[340] = {u8} 0 [0x0]
[341] = {u8} 0 [0x0]
[342] = {u8} 0 [0x0]
[343] = {u8} 69 [0x45]
[344] = {u8} 129 [0x81]
[345] = {u8} 129 [0x81]
[346] = {u8} 129 [0x81]
[347] = {u8} 129 [0x81]
[348] = {u8} 129 [0x81]
[349] = {u8} 129 [0x81]
[350] = {u8} 73 [0x49]
[351] = {u8} 129 [0x81]
[352] = {u8} 129 [0x81]
[353] = {u8} 129 [0x81]
[354] = {u8} 129 [0x81]
[355] = {u8} 129 [0x81]
[356] = {u8} 129 [0x81]
[357] = {u8} 129 [0x81]
[358] = {u8} 129 [0x81]
[359] = {u8} 7 [0x7]
[360] = {u8} 5 [0x5]
[361] = {u8} 75 [0x4b]
[362] = {u8} 80 [0x50]
[363] = {u8} 129 [0x81]
[364] = {u8} 129 [0x81]
[365] = {u8} 129 [0x81]
[366] = {u8} 129 [0x81]
[367] = {u8} 129 [0x81]
[368] = {u8} 129 [0x81]
[369] = {u8} 129 [0x81]
[370] = {u8} 129 [0x81]
[371] = {u8} 129 [0x81]
[372] = {u8} 129 [0x81]
[373] = {u8} 129 [0x81]
[374] = {u8} 129 [0x81]
[375] = {u8} 74 [0x4a]
[376] = {u8} 129 [0x81]
[377] = {u8} 129 [0x81]
[378] = {u8} 129 [0x81]
[379] = {u8} 129 [0x81]
[380] = {u8} 129 [0x81]
[381] = {u8} 129 [0x81]
[382] = {u8} 129 [0x81]
[383] = {u8} 129 [0x81]
[384] = {u8} 129 [0x81]
[385] = {u8} 129 [0x81]
[386] = {u8} 129 [0x81]
[387] = {u8} 129 [0x81]
[388] = {u8} 129 [0x81]
[389] = {u8} 129 [0x81]
[390] = {u8} 129 [0x81]
[391] = {u8} 129 [0x81]
[392] = {u8} 129 [0x81]
[393] = {u8} 129 [0x81]
[394] = {u8} 129 [0x81]
[395] = {u8} 0 [0x0]
[396] = {u8} 0 [0x0]
[397] = {u8} 0 [0x0]
[398] = {u8} 0 [0x0]
[399] = {u8} 0 [0x0]
[400] = {u8} 69 [0x45]
[401] = {u8} 69 [0x45]
[402] = {u8} 69 [0x45]
[403] = {u8} 69 [0x45]
[404] = {u8} 69 [0x45]
[405] = {u8} 69 [0x45]
[406] = {u8} 61 [0x3d]
[407] = {u8} 61 [0x3d]
[408] = {u8} 1 [0x1]
[409] = {u8} 0 [0x0]
[410] = {u8} 0 [0x0]
[411] = {u8} 0 [0x0]
[412] = {u8} 0 [0x0]
[413] = {u8} 0 [0x0]
[414] = {u8} 0 [0x0]
[415] = {u8} 16 [0x10]
[416] = {u8} 61 [0x3d]
[417] = {u8} 61 [0x3d]
[418] = {u8} 61 [0x3d]
[419] = {u8} 61 [0x3d]
[420] = {u8} 255 [0xff]
[421] = {u8} 255 [0xff]
[422] = {u8} 255 [0xff]
[423] = {u8} 255 [0xff]
[424] = {u8} 255 [0xff]
[425] = {u8} 255 [0xff]
[426] = {u8} 61 [0x3d]
[427] = {u8} 61 [0x3d]
[428] = {u8} 61 [0x3d]
[429] = {u8} 61 [0x3d]
[430] = {u8} 61 [0x3d]
[431] = {u8} 61 [0x3d]
[432] = {u8} 61 [0x3d]
[433] = {u8} 61 [0x3d]
[434] = {u8} 61 [0x3d]
[435] = {u8} 61 [0x3d]
[436] = {u8} 61 [0x3d]
[437] = {u8} 61 [0x3d]
[438] = {u8} 61 [0x3d]
[439] = {u8} 61 [0x3d]
[440] = {u8} 61 [0x3d]
[441] = {u8} 80 [0x50]
[442] = {u8} 191 [0xbf]
[443] = {u8} 0 [0x0]

Update: here's the output in xxd format (obtained with the lldb command memory read -s1 -fy -c444 input[0]):
0x7fa098008200: 45 ff ff ff ff ff ff 45 45 45 45 45 45 3d 3d 3d
0x7fa098008210: 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 2a
0x7fa098008220: 2a 2a 2a 2a 2a 2a 2a 2a 2a 2a 2a 2a 2a 45 45 45
0x7fa098008230: 45 44 45 f0 45 45 45 45 45 45 45 45 45 45 45 45
0x7fa098008240: 45 45 45 45 45 06 05 4b 50 45 45 45 45 45 45 45
0x7fa098008250: 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45
0x7fa098008260: 45 45 45 45 45 45 45 45 45 45 45 3e 45 45 45 45
0x7fa098008270: 45 45 45 01 00 00 00 00 00 00 10 45 45 45 45 45
0x7fa098008280: 45 45 45 45 45 45 45 ec ec ec ec ec ec ec ec ec
0x7fa098008290: ec ec ec ec ec ec ec ec ec ec ec ec ec ec ec ec
0x7fa0980082a0: ec ec ec ec ec ec ec ec ec ec ec ec ec ec ec ec
0x7fa0980082b0: ec ec 81 81 81 81 81 81 81 81 81 81 81 81 81 81
0x7fa0980082c0: 07 05 4b 50 81 81 81 81 81 30 01 00 00 00 00 00
0x7fa0980082d0: 00 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81
0x7fa0980082e0: 81 81 81 81 81 81 81 81 81 81 00 00 00 00 00 45
0x7fa0980082f0: 45 45 45 45 45 3d 2b 3d 3d 3d 3d 3d 3d 3d 3d 3d
0x7fa098008300: 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d
0x7fa098008310: 3d 3d 3d 3d 3d 3d 3d 3d 45 45 45 45 45 45 45 45
0x7fa098008320: 45 45 45 45 45 45 45 45 c0 c0 c0 c0 c0 c0 c0 c0
0x7fa098008330: 00 23 00 00 00 00 00 00 05 06 00 00 01 00 00 00
0x7fa098008340: 09 04 fd ff 06 05 4b 50 00 00 00 02 00 84 ff ff
0x7fa098008350: ff 6b 01 00 00 00 00 45 81 81 81 81 81 81 49 81
0x7fa098008360: 81 81 81 81 81 81 81 07 05 4b 50 81 81 81 81 81
0x7fa098008370: 81 81 81 81 81 81 81 4a 81 81 81 81 81 81 81 81
0x7fa098008380: 81 81 81 81 81 81 81 81 81 81 81 00 00 00 00 00
0x7fa098008390: 45 45 45 45 45 45 3d 3d 01 00 00 00 00 00 00 10
0x7fa0980083a0: 3d 3d 3d 3d ff ff ff ff ff ff 3d 3d 3d 3d 3d 3d
0x7fa0980083b0: 3d 3d 3d 3d 3d 3d 3d 3d 3d 50 bf 00

In HuffmanTree::create_table, self is equal to (WIP):
HuffmanTree {
  code_lengths_length: 32,
  table: iter::once(-32).chain(iter::repeat(0).take(511)).collect(),
  left: iter::repeat(0).take(32).chain([-33, -39, -35, -36, -37, 0, 2, -40, -41, 3, -43, 5, 8, -46, -47, 10, 11, 13, -51, 16, 18, -54, 19, -56, -57, -58, -59, 21, 24, -62, 26, 27].into_iter()).chain(iter::repeat(0).take(512)).collect(),
  right: iter::repeat(0).take(32).chain([-55, -34, -45, -42, -38, 1, 4, -53, -48, 7, -44, 6, 9, -50, -49, 12, 15, 14, -52, 17, 20, -63, 23, 0, 0, -61, -60, 22, 25, -64, 28, 0].into_iter()).chain(iter::repeat(0).take(512)).collect(),
  code_length_array: iter::repeat([15, 15, 15, 14]).take(8).flatten().chain(iter::repeat(0).take(256)).collect(),
  code_array: [0x400, 0x4400, 0x2400, 0, 0x6400, 0x1400, 0x5400, 0x2000, /*...*/]
}

To reproduce this issue the exact same way I originally encountered it, run the unit test added in this commit: https://github.com/Pr0methean/zip-next/commit/aff3f8db9641cbb0b6183aac17bfdb75b32bb56f.

I tried to unzip the zip file with info-zip, windows 11, and 7zip and all of them fails to load zip file.
$ unzip file.zip
Archive:  file.zip
error [file.zip]:  NULL central directory offset
  (attempting to process anyway)
   skipping:                         need PK compat. v25.5 (can do v4.5)
error:  expected central file header signature not found (file #1).
  (please check that you have transferred or created the zipfile in the
  appropriate BINARY mode and that you have compiled UnZip properly)
$ unzip --version
caution:  both -n and -o specified; ignoring -o
UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.
(truncated)

Right -- these are intentionally invalid inputs, because the fuzz test is designed to ensure that attempting to unzip them returns an error result rather than panicking.

Here's a version with a valid CDR.
raw_deflate64_index_out_of_bounds.zip

Oh, sorry I missed "when reading invalid data" in the title.


Reorganise Makefile

This looks like good advice https://spin.atomicobject.com/2016/08/26/makefile-c-projects/

Another cross-reference for someone who works on this issue: https://github.com/k4rtik/concurrent-graph/blob/master/src/Makefile