crashlytics - error: cannot find symbol     FirebaseCrashlytics.getInstance().core.logFatalException(throwable);

Bug report
Describe the bug
Cannot compile on android duo to a problem with firebase crashlytics

Run Error
/Users/_/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_crashlytics-2.8.0/android/src/main/java/com/google/firebase/crashlytics/FlutterFirebaseCrashlyticsInternal.java:14: error: cannot find symbol
    FirebaseCrashlytics.getInstance().core.logFatalException(throwable);
                                          ^
  symbol:   method logFatalException(Throwable)
  location: variable core of type CrashlyticsCore
Note: /Users/_/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_crashlytics-2.8.0/android/src/main/java/io/flutter/plugins/firebase/crashlytics/FlutterFirebaseCrashlyticsPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error

FAILURE: Build failed with an exception.

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

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

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

BUILD FAILED in 5s
Exception: Gradle task assembleDebug failed with exit code 1

Flutter doctor
Click To Expand
[✓] Flutter (Channel stable, 3.0.0, on macOS 12.3.1 21E258 darwin-arm, locale
    en-EG)
[✓] Android toolchain - develop for Android devices (Android SDK version
    31.0.0-rc5)
[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.67.0)
[✓] Connected device (1 available)
    ! Error: nemr’s iphone is not connected. Xcode will continue when nemr’s
      iphone is connected. (code -13)
    ! Error: nemr’s iphone is not connected. Xcode will continue when nemr’s
      iphone is connected. (code -13)
    ! Error: neemmrr is not connected.

There're some conflicts between dependencies.
I fixed this after trying these commands:
flutter pub upgrade
flutter pub outdated
flutter pub upgrade --major-versions
flutter clean
flutter pub get

Hope this help.

Have anyone solved this problem ?

I downgrade flutter to v2.10.5 and flutter_crashlytics: 2.7.2, this work for me, while a bugfix is published

There're some conflicts between dependencies. I fixed this after trying these commands:
flutter pub upgrade
flutter pub outdated
flutter pub upgrade --major-versions
flutter clean
flutter pub get

Hope this help.

it didn't work, I already did it so no dependencies changed this time

It seems there's a new file added which has the said method:
https://github.com/firebase/flutterfire/pull/8540/files#diff-1dac17c2c0f9a9ae5277bf04809c41b54d3b0ca29976583173397af903bd010d
@nemr0 can you try by pulling master branch on FlutterFire project and see if you still get same error ?

clone FF repo.
Install melos
run melos boostrap from root of project which ensures you're using Crashlytics master branch code as dependencies.

Or another solution is to try this and see if it helps.

Hey @nemr0,  I've just ran the Crashlytics example as per this comment and it compiles without any problems. Could you provide a minimal, reproducible code sample/repo, please? 🙏

This has helped. I have basically iterated over every firebase_* dependency and upgraded it to the latest version.

I have downgraded the firebase crashlytics package to 2.7.0 but my flutter still references the package in version 2.8.0 when I do flutter run. wtf :(

flutter pub outdated

This worked for me👍🏼

Have anyone solved this problem ?

I downgrade flutter to v2.10.5 and flutter_crashlytics: 2.7.2, this work for me, while a bugfix is published

This worked for me👍🏼

My pubspec.lock was stuck on firebase_core: 1.14.1.  Upgrading to 1.17.0 fixed it.

Seems like firebase_crashlytics actually depends on higher version of firebase_core than specified in its pubspec.yaml.
I got the error after downgrading firebase_core to 1.13.1 because of #8444.
Had to also downgrade firebase_crashlytics to avoid this error.
firebase_core dependency of the crashlytics plugin should be upgraded.

not sure if can help, but i fixed by:

flutter upgrade (from 2.10.4 to  3.0.1)
flutter clean
flutter pub upgrade
pub get
flutterfire configure

In addition, i noticed some differences between
my app/build.gradle
and firebase_crashlytics-2.8.1/example/android/app/build.gradle
in particular i removed:
rootProject.ext {
    set('FlutterFire', [
            FirebaseSDKVersion: '29.0.0'
    ])
}

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

at the end of the file..
not sure what of those steps made the difference, but now it works!
i wasted too much time on this..hope to save it to someone else

FirebaseSDKVersion: '29.0.0'

this happens in IOS builds didn't test android ones
I updated all firebase dependencies in pubspec.yaml file
and updated dartSDK version to 2.17.3
then used the following commands:
flutter clean
flutter pub get
flutterfire configure
and it gave me this error
Xcode build done.                                           73.4s
Failed to build iOS app
Error output from Xcode build:
↳
    2022-06-08 15:48:33.690 xcodebuild[27810:283714] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    2022-06-08 15:48:33.690 xcodebuild[27810:283714] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    2022-06-08 15:48:52.386 xcodebuild[27810:285908]  DTDeviceKit: Failed to mount DDI from '<DVTFilePath:0x6000010e6d00:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.4/DeveloperDiskImage.dmg'>', error=-402652958: Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x600003246cd0 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 "The device is locked." UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    ), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}}, NSLocalizedRecoverySuggestion=Please unlock and reconnect the device., NSLocalizedFailure=The device is locked., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}
    2022-06-08 15:48:52.387 xcodebuild[27810:285908]  iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x600003246cd0 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 "The device is locked." UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    ), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}}, NSLocalizedRecoverySuggestion=Please unlock and reconnect the device., NSLocalizedFailure=The device is locked., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}) {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedDescription = "Failed to prepare device for development.";
        NSLocalizedFailure = "The device is locked.";
        NSLocalizedRecoverySuggestion = "Please unlock and reconnect the device.";
        NSUnderlyingError = "Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 \"The device is locked.\" UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768\n\t2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572\n\t3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20\n\t4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56\n\t5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148\n\t7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16\n\t8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364\n\t9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32\n\t10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20\n\t11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652\n\t12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584\n\t13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396\n\t14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164\n\t15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228\n\t16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8\n), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}";
    }
    2022-06-08 15:48:52.387 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> -- An error occurred whilst preparing device for development -- Failed to prepare device for development.
    Domain: com.apple.dtdevicekit
    Code: 806
    Recovery Suggestion: Please unlock and reconnect the device.
    User Info: {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedFailure = "The device is locked.";
    }
    --
    The device is locked.
    Domain: com.apple.dt.MobileDeviceErrorDomain
    Code: -402652958
    User Info: {
        DVTRadarComponentKey = 261622;
        MobileDeviceErrorCode = "(0xE80000E2)";
        "com.apple.dtdevicekit.stacktrace" = (
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    );
    }
    --
    2022-06-08 15:48:52.387 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> == Underlying device preparation errors ==
    2022-06-08 15:48:52.387 xcodebuild[27810:283714] [MT] iPhoneConnect: Failed to prepare device for development.
    Domain: com.apple.dtdevicekit
    Code: 806
    Recovery Suggestion: Please unlock and reconnect the device.
    User Info: {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedFailure = "The device is locked.";
    }
    --
    The device is locked.
    Domain: com.apple.dt.MobileDeviceErrorDomain
    Code: -402652958
    User Info: {
        DVTRadarComponentKey = 261622;
        MobileDeviceErrorCode = "(0xE80000E2)";
        "com.apple.dtdevicekit.stacktrace" = (
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    );
    }
    --
    2022-06-08 15:48:52.387 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> == END: Underlying device preparation errors ==
    2022-06-08 15:48:54.055 xcodebuild[27810:285909]  DTDeviceKit: Failed to mount DDI from '<DVTFilePath:0x6000010e6d00:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.4/DeveloperDiskImage.dmg'>', error=-402652958: Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x6000031a7f30 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 "The device is locked." UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    ), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}}, NSLocalizedRecoverySuggestion=Please unlock and reconnect the device., NSLocalizedFailure=The device is locked., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}
    2022-06-08 15:48:54.055 xcodebuild[27810:285909]  iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x6000031a7f30 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 "The device is locked." UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    ), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}}, NSLocalizedRecoverySuggestion=Please unlock and reconnect the device., NSLocalizedFailure=The device is locked., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}) {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedDescription = "Failed to prepare device for development.";
        NSLocalizedFailure = "The device is locked.";
        NSLocalizedRecoverySuggestion = "Please unlock and reconnect the device.";
        NSUnderlyingError = "Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402652958 \"The device is locked.\" UserInfo={MobileDeviceErrorCode=(0xE80000E2), com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768\n\t2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572\n\t3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20\n\t4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56\n\t5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148\n\t7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16\n\t8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364\n\t9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32\n\t10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20\n\t11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652\n\t12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584\n\t13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396\n\t14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164\n\t15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228\n\t16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8\n), DVTRadarComponentKey=261622, NSLocalizedDescription=The device is locked.}";
    }
    2022-06-08 15:48:54.056 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> -- An error occurred whilst preparing device for development -- Failed to prepare device for development.
    Domain: com.apple.dtdevicekit
    Code: 806
    Recovery Suggestion: Please unlock and reconnect the device.
    User Info: {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedFailure = "The device is locked.";
    }
    --
    The device is locked.
    Domain: com.apple.dt.MobileDeviceErrorDomain
    Code: -402652958
    User Info: {
        DVTRadarComponentKey = 261622;
        MobileDeviceErrorCode = "(0xE80000E2)";
        "com.apple.dtdevicekit.stacktrace" = (
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    );
    }
    --
    2022-06-08 15:48:54.056 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> == Underlying device preparation errors ==
    2022-06-08 15:48:54.056 xcodebuild[27810:283714] [MT] iPhoneConnect: Failed to prepare device for development.
    Domain: com.apple.dtdevicekit
    Code: 806
    Recovery Suggestion: Please unlock and reconnect the device.
    User Info: {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedFailure = "The device is locked.";
    }
    --
    The device is locked.
    Domain: com.apple.dt.MobileDeviceErrorDomain
    Code: -402652958
    User Info: {
        DVTRadarComponentKey = 261622;
        MobileDeviceErrorCode = "(0xE80000E2)";
        "com.apple.dtdevicekit.stacktrace" = (
    	0   DTDeviceKitBase                     0x0000000113709614 DTDKCreateNSErrorFromAMDErrorCode + 272
    	1   DTDeviceKitBase                     0x0000000113740bf0 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 768
    	2   DTDeviceKitBase                     0x00000001137416c4 __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 572
    	3   libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	4   libdispatch.dylib                   0x0000000184f1f414 _dispatch_lane_barrier_sync_invoke_and_complete + 56
    	5   DTDeviceKitBase                     0x000000011374142c -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
    	6   IDEiOSSupportCore                   0x00000001212c0e7c __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 148
    	7   DVTFoundation                       0x0000000106544f50 __DVT_CALLING_CLIENT_BLOCK__ + 16
    	8   DVTFoundation                       0x000000010654734c __DVTDispatchGroupAsync_block_invoke + 364
    	9   libdispatch.dylib                   0x0000000184f0e5f0 _dispatch_call_block_and_release + 32
    	10  libdispatch.dylib                   0x0000000184f101b4 _dispatch_client_callout + 20
    	11  libdispatch.dylib                   0x0000000184f13708 _dispatch_continuation_pop + 652
    	12  libdispatch.dylib                   0x0000000184f12cdc _dispatch_async_redirect_invoke + 584
    	13  libdispatch.dylib                   0x0000000184f218e8 _dispatch_root_queue_drain + 396
    	14  libdispatch.dylib                   0x0000000184f22104 _dispatch_worker_thread2 + 164
    	15  libsystem_pthread.dylib             0x00000001850d0324 _pthread_wqthread + 228
    	16  libsystem_pthread.dylib             0x00000001850cf080 start_wqthread + 8
    );
    }
    --
    2022-06-08 15:48:54.056 xcodebuild[27810:283714] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x136e2e4f0), nemr’s iphone, iPhone, 15.4.1 (19E258), 00008101-000E0916118B001E> == END: Underlying device preparation errors ==
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/lw/17kwyl0d2yd706_0dnpxtvbm0000gn/T/flutter_tools.cG4HIq/flutter_ios_build_temp_dirNdj1nu/temporary_xcresult_bundle

    /Users/omarelnemr/flutter/.pub-cache/hosted/pub.dartlang.org/geolocator_apple-2.1.4/ios/Classes/GeolocatorPlugin.m:179:21: warning: 'openURL:' is deprecated: first deprecated in iOS 10.0 [-Wdeprecated-declarations]
                        openURL:[NSURL URLWithString:UIApplicationOpenSettingsURLString]];
                        ^~~~~~~
                        openURL:options:completionHandler:
    In module 'UIKit' imported from /Users/omarelnemr/Documents/GitHub/authenticated/ios/Pods/Target Support Files/geolocator_apple/geolocator_apple-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.5.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:124:1: note: 'openURL:' has been explicitly marked deprecated here
    - (BOOL)openURL:(NSURL*)url API_DEPRECATED_WITH_REPLACEMENT("openURL:options:completionHandler:", ios(2.0, 10.0)) NS_EXTENSION_UNAVAILABLE_IOS("");
    ^
    1 warning generated.
    /Users/omarelnemr/flutter/.pub-cache/hosted/pub.dartlang.org/geolocator_apple-2.1.4/ios/Classes/GeolocatorPlugin.m:179:21: warning: 'openURL:' is deprecated: first deprecated in iOS 10.0 [-Wdeprecated-declarations]
                        openURL:[NSURL URLWithString:UIApplicationOpenSettingsURLString]];
                        ^~~~~~~
                        openURL:options:completionHandler:
    In module 'UIKit' imported from /Users/omarelnemr/Documents/GitHub/authenticated/ios/Pods/Target Support Files/geolocator_apple/geolocator_apple-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.5.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:124:1: note: 'openURL:' has been explicitly marked deprecated here
    - (BOOL)openURL:(NSURL*)url API_DEPRECATED_WITH_REPLACEMENT("openURL:options:completionHandler:", ios(2.0, 10.0)) NS_EXTENSION_UNAVAILABLE_IOS("");
    ^
    1 warning generated.
    error: No Google App ID or Google Services file provided
Could not build the application for the simulator.
Error launching application on iPhone 13 Pro.
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in dependency order

    Result bundle written to path:
    	/var/folders/lw/17kwyl0d2yd706_0dnpxtvbm0000gn/T/flutter_tools.cG4HIq/flutter_ios_build_temp_dirNdj1nu/temporary_xcresult_bundle

This is my flutter doctor output:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.4 21F79 darwin-arm, locale
    en-EG)
[✓] Android toolchain - develop for Android devices (Android SDK version
    31.0.0-rc5)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.67.2)
[✓] Connected device (1 available)
    ! Error: nemr’s iphone is not connected. Xcode will continue when nemr’s
      iphone is connected. (code -13)
    ! Error: neemmrr is not connected. Xcode will continue when neemmrr is
      connected. (code -13)
    ! Error: nemr’s iphone is not connected. Xcode will continue when nemr’s
      iphone is connected. (code -13)
[✓] HTTP Host Availability

• No issues found!

and my pubspec.yaml for this project:
name: authenticated
description: A new Flutter project.

publish_to: 'none'

version: 1.1.002+1

environment:
  sdk: ">=2.13.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  geolocator: ^8.0.0
  flutter_riverpod: ^1.0.2
  rounded_loading_button: ^2.0.9
  firebase_core: ^1.17.1
  firebase_auth: ^3.3.19
  cloud_firestore: ^3.1.17
  device_info_plus: ^3.1.1
  google_fonts: ^3.0.1
  sliding_up_panel: ^2.0.0+1
  pie_chart: ^5.1.0
  skeletons: ^0.0.3
  flutter_native_splash: ^2.1.1
  anitex: ^3.0.0
  http: ^0.13.4
  firebase_app_check: ^0.0.6+13
  shared_preferences: ^2.0.13
  mocktail: ^0.3.0
  pin_code_fields: ^7.4.0
  local_auth: ^2.1.0
  intl_phone_field: ^3.1.0
  ntp: ^2.0.0
  stop_watch_timer: ^1.4.0
  flutter_countdown_timer: ^4.1.0
  pull_down_button: ^0.1.0-beta.2
  cupertino_icons: ^1.0.4
  firebase_crashlytics: ^2.8.1

dev_dependencies:
  flutter_test:
    sdk: flutter
  integration_test:
    sdk: flutter

  flutter_lints: ^2.0.0

flutter:

  uses-material-design: true
  assets:
    - assets/

I only used crashlytics on app launch in the main function as shown right here:
/// Main (ENTRY POINT)
Future<void> main() async {
  /// Intializing binding before run App
  WidgetsFlutterBinding.ensureInitialized();

  ///Intializing Firebase App
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );

  /// Activate Firebase App Check
  await FirebaseAppCheck.instance
      .activate()
      .onError((error, stackTrace) => print);

  /// Setting Token Auto Refresh to true
  await FirebaseAppCheck.instance.setTokenAutoRefreshEnabled(true);

  /// Uncaught flutter exceptions to firebase
  FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;

  /// Setting Status & Navigation bars to dark color
  SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle.dark);
  SystemChrome.setPreferredOrientations(
      [DeviceOrientation.portraitUp, DeviceOrientation.portraitDown]);

  /// Running The App
  runApp(

      /// Provider Scope Widget to Ensure Riverpod state shared

      /// across the widget tree..

      const ProviderScope(
          child:

              /// Holds The Material App Widget to specify App Preferences
              MyApp()));
}

@nemr0 From the log you shared above, it show different errors and warnings that you'll need to fix as indicated in it.
Recovery Suggestion: Please unlock and reconnect the device.
    User Info: {
        AssociatedMobileDeviceFunction = AMDeviceMountImage;
        DVTRadarComponentKey = 487927;
        NSLocalizedFailure = "The device is locked.";
    }
    --
    The device is locked.

Please keep your device unlocked while running the build.
geolocator_apple-2.1.4/ios/Classes/GeolocatorPlugin.m:179:21: warning: 'openURL:' is deprecated: first deprecated in iOS 10.0
Also, error: No Google App ID or Google Services file provided which probably means you'll need to explicitly provide the file if you are not using dart only initialization.
Also please check earlier comments which seemed to have worked / fixed the issue for others.

There're some conflicts between dependencies. I fixed this after trying these commands:
flutter pub upgrade
flutter pub outdated
flutter pub upgrade --major-versions
flutter clean
flutter pub get

Hope this help.

This worked for me...make sure you also do "Flutter upgrade" after

I know this comment doesn't answer your question, but why does every flutter firebase plugin upgrade break something? I just upgraded firebase_crashlytics from 2.5.0 to 2.8.4 and now I have to spend hours and hours fixing build issues.

Upgrading firebase_crashlytics to 2.8.4 gave the same compile error for me as well. Upgrading firebase_core version solved my issue.


[RDMA Share Plugin] supports direct configuration of configList[].devices parameters

What would you like to be added?

The RDMA Shared Device Plugin supports direct configuration of the device name, which is useful because I can precisely control which network card is used to assign it to the Pod.
Or, open parameter configuration items such as ifNames
Why is this needed?
No response
How to implement it (if possible)?
https://github.com/spidernet-io/spiderpool/blob/3ae7bf0ba20cad611db4e43cfc00ff9f2c7d18b4/charts/spiderpool/templates/rdma-shared-dp/rdma-shared-dp.yaml#L17-L27
Add more settings here.
Additional context
No response

thanks for the report! I'm surprised we don't have support for configuring the devices, it looks like it's missing, I'll fix that later.


KAFKA-14772: Add ConsumerGroupHeartbeat and ConsumerGroupDescribe API to AuthorizerIntegrationTest

The patch adds ConsumerGroupHeartbeat and ConsumerGroupDescribe API to AuthorizerIntegrationTest.

@dajac  PTAL when you get a chance.

@DL1231 Thanks for the patch. Could you please rebase to include https://github.com/apache/kafka/commit/9abb8d3b3cbc2bc862d894726cb0aca0b11fe518 and adapt your patch accordingly?


Screen size (resolution)

I usually use a 1366x768 screen resolution. I can't see the popup dialog properly.

You mean to say that you don't like the "scrolling" in the modal?

exactly that 🤣


Proteus nearshore benchmarks are now segfaulting in parallel

Due to something that landed in master in the last couple of days, I suspect.

Fixed in https://github.com/erdc-cm/proteus-mprans/pull/55


TypeError: getresponse() got an unexpected keyword argument 'buffering'

So I've been working on an update for my bot, and I've noticed a strange issue that I haven't seen before. Basically the client seems to open up multiple HTTP connections to reddit, which is something that I don't remember seeing before (it is possible that I just forgot). I am making use of username mentions to catch requests for the bot to reply, so I am scanning my bot's inbox continually for different types of requests. For example, I sent a request to change a user's default translation for my bot, and I get this crash log:
INFO:versebot:Connecting to reddit...
:0: UserWarning: The keyword `bot` in your user_agent may be problematic.
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): ssl.reddit.com
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): www.reddit.com
INFO:versebot:Successfully connected to reddit!
INFO:versebot:Connecting to database...
INFO:versebot:Successfully connected to database!
INFO:versebot:Updating translation list table...
INFO:versebot:Translation list update successful!
INFO:versebot:Cleaning old user translation entries...
INFO:versebot:User translation cleaning successful!
INFO:versebot:Beginning to scan for new inbox messages...
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (2): www.reddit.com
Traceback (most recent call last):
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 372, in _make_request
    httplib_response = conn.getresponse(buffering=True)
TypeError: getresponse() got an unexpected keyword argument 'buffering'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen
    body=body, headers=headers)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 374, in _make_request
    httplib_response = conn.getresponse()
  File "/home/matthieu/.pyenv/versions/3.4.2/lib/python3.4/http/client.py", line 1164, in getresponse
    raise ResponseNotReady(self.__state)
http.client.ResponseNotReady: Request-sent

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/adapters.py", line 370, in send
    timeout=timeout
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 597, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 245, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/packages/six.py", line 309, in reraise
    raise value.with_traceback(tb)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen
    body=body, headers=headers)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 374, in _make_request
    httplib_response = conn.getresponse()
  File "/home/matthieu/.pyenv/versions/3.4.2/lib/python3.4/http/client.py", line 1164, in getresponse
    raise ResponseNotReady(self.__state)
requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', ResponseNotReady('Request-sent',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "versebot.py", line 248, in <module>
    bot.main_loop()
  File "versebot.py", line 61, in main_loop
    self.respond_to_user_translation_request(message)
  File "versebot.py", line 207, in respond_to_user_translation_request
    message.reply("Your default translations have been updated successfully!")
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/objects.py", line 384, in reply
    response = self.reddit_session._add_comment(self.fullname, text)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/decorators.py", line 338, in wrapped
    return function(cls, *args, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/__init__.py", line 2173, in _add_comment
    retry_on_error=False)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/decorators.py", line 163, in wrapped
    return_value = function(reddit_session, *args, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/__init__.py", line 561, in request_json
    retry_on_error=retry_on_error)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/__init__.py", line 402, in _request
    response = handle_redirect()
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/__init__.py", line 375, in handle_redirect
    timeout=timeout, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/handlers.py", line 144, in wrapped
    result = function(cls, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/handlers.py", line 54, in wrapped
    return function(cls, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/praw/handlers.py", line 99, in request
    allow_redirects=False)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/home/matthieu/.pyenv/versions/versebot/lib/python3.4/site-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', ResponseNotReady('Request-sent',))
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=4, family=AddressFamily.AF_INET, type=2049, proto=6, laddr=('<IP_ADDRESS>', 45140), raddr=('<IP_ADDRESS>', 443)>
/home/matthieu/.pyenv/versions/3.4.2/lib/python3.4/importlib/_bootstrap.py:2150: ImportWarning: sys.meta_path is empty

I believe the most important part of this crash log is TypeError: getresponse() got an unexpected keyword argument 'buffering', as stated in the title. Any idea what could be causing this?

This appears to be the actual exception: requests.exceptions.ConnectionError: ('Connection aborted.', ResponseNotReady('Request-sent',))
The other exceptions are just part of python3's nested exception handling and is covered in far more detail at: https://github.com/kennethreitz/requests/issues/1915
I'm not sure why you are getting ResponseNotReady unless you are manually trying to re-use the HTTP connections for something else. I'm going to close this issue as I suspect it's not with PRAW.
Please reopen if you can minimally reproduce the issue along with the code to reproduce it. Thanks!

Thanks for the response, I wasn't aware of the nested exception handling, that's pretty cool! Now that I think about it it may be some strange issue with the network I am currently testing the bot on. I'll try a different network and see what happens.

I've seen a few other people report similar problems. Are you still experiencing these issues @matthieugrieger?

I haven't had the chance to test it out again. I'll make sure to respond
here when I try it out.
On Apr 28, 2015 10:05 PM, "Bryce Boe"<EMAIL_ADDRESS>wrote:

I've seen a few other people report similar problems. Are you still
experiencing these issues @matthieugrieger
https://github.com/matthieugrieger?
—
Reply to this email directly or view it on GitHub
https://github.com/praw-dev/praw/issues/405#issuecomment-97306028.

@bboe: Sorry about the late response, just got around to testing it out again. I am no longer experiencing the issue.

No worries. Thanks for checking!

@bboe: Unfortunately I spoke too soon. :(
Just experienced the issue again. I saw one post from someone on /r/redditdev experiencing this issue. Are there any others?

@matthieugrieger It's a fascinating 'coincidence' that the top hit I get for this same problem comes from you. Trust me, not digging at you at all. I'm thinking this is really helpful because we seem to be sharing the same problem. I'm going to see how much of our codebase is still in common. Thanks!

@konohitowa Very interesting indeed! I forgot about this issue, maybe this
was still causing some of the instability problems with the bot.
On Oct 25, 2015 9:10 PM, "konohitowa"<EMAIL_ADDRESS>wrote:

@matthieugrieger https://github.com/matthieugrieger It's a fascinating
'coincidence' that the top hit I get for this same problem comes from you.
Trust me, not digging at you at all. I'm thinking this is really helpful
because we seem to be sharing the same problem. I'm going to see how much
of our codebase is still in common. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/praw-dev/praw/issues/405#issuecomment-151019684.


Bad pointer arithmetic in header field parsing

https://github.com/nodejs/http-parser/blob/c5c45636b85e7598223adede6ba2d8cb8fe03ebe/http_parser.c#L1259-L1266
What that code calls limit is actually the number of remaining characters.
p+1 < data+limit must be wrong because data+limit is not fixed, it gets smaller as the p on line 1260 gets bigger.
Say, len == 8 and p == data + 5, then data + len - p == 3. Ergo, p+1 < data+limit is always false in that case.

Let's do some math:
len = 16000
p - data = 100
max_header_size = 8000
limit = 7900

It seems that there would be some p for which the condition is going to be false?

IIUC your example, limit gets clamped to 8000 because MIN(16000 - 100, 8000).


pre-processing about AudioSet (resample to 16kHz)

Hi! Yaun Gong, Thank you for providing good research and opensource code.
There is one problem with reproducing.
When i convert the AudioSet (my dataset is 32kHz) to 16kHz using sox (Based on ast/egs/esx50/prep_esc50.py), warning is happen.
The code I used are as below
os.system('sox ' + base_dir + '/audio/' + audio + ' -r 16000 ' + base_dir + '/audio_16k/' + audio)
This seems to be the cause of making the mean and std of the data different from what you wrote.
(our mean and std are -3.539583 and 3.4221482, which are not the same as -4.2677393, 4.5689974 in your code)
And the difference between these datasets seems to make the result value (mAP) different.

The results of the 5 epochs are:
0.408, 0.425, 0.434, 0.433, 0.433
Compare the results given in your source code:
4.153, 0.439, 0,448, 0.449, 0.449

So, in conclusion, my question is this.
Did you also have any warning signal in the process of resample AudioSet data? If so, I wonder how you solved it.
sox warn marks are shown below.
Thanks :)

sox WARN rate: rate clipped 5 samples; decrease volume?
sox WARN dither: dither clipped 5 samples; decrease volume?

hi there,
I get these warnings. These are safe and not the cause of the problem.
The problem is the dataset, have you downloaded the dataset from PANNs paper repo? If so, it is a known issue. I guess this version is somehow different from what we use.
0.433 and 0.449 is a huge difference on AudioSet. FYI, for getting video data purpose, we used another version which was downloaded independently with the AST used version after the AST work, which is noticeably smaller. But still, we get very similar results, so it is also unlikely to be the data size issue.
Can you reproduce our ESC-50 result?
-Yuan

Btw, what is the format of your AS data? We have .flac.

What if you use our best-pretrained model to infer your test set? (note please keep everything unchanged, including the std/mean).

hi,
I will need to follow up this later as I am working on a deadline.

The problem is the dataset, have you downloaded the dataset from PANNs paper repo?
Yes, I downloaded the dataset from PANNs paper repo. (for unbal set, 1.1TB)
https://github.com/qiuqiangkong/audioset_tagging_cnn
I got it from shell script file provided by PANNs repo. First, download wav file with 32kHz and then downsample to 16kHz.
https://github.com/qiuqiangkong/audioset_tagging_cnn/blob/master/scripts/1_download_dataset.sh
using yt-dlp & ffmpeg. (main code is as below). Is there no problem here? Should I download it to 16kHz directly?
os.system("yt-dlp --quiet -o '{}' -x https://www.youtube.com/watch?v={}".format(video_name, audio_id))
os.system("ffmpeg -loglevel panic -i {} -ac 1 -ar 32000 -ss {} -t 00:00:{} {} "format(video_path, str(datetime.timedelta(seconds=start_time)), duration, audio_path))
Is this the cause of the problem? I calculated the mean/std from "get_normal_stats.py" and changed it to a new value( -3.539583 3.4221482) because it is different from your mean/std.
btw, If the data is a problem, I will try to download it again through a different path. (Not PANNs repo method)
Is there any github repo that can help me download AudioSet data?

I am not the person download the dataset so don't know the details, but we used youtube-dl.

Model 0 /pretrained_models/audioset_10_10_0.4495.pth mAP: 0.449942, AUC: 0.974956, d-prime: 2.770742
Model 1 /pretrained_models/audioset_10_10_0.4483.pth mAP: 0.447466, AUC: 0.974261, d-prime: 2.754138
Model 2 /pretrained_models/audioset_10_10_0.4475.pth mAP: 0.446870, AUC: 0.973542, d-prime: 2.737371
Ensemble 3 Models mAP: 0.474453, AUC: 0.979376, d-prime: 2.886452

Thanks so much for providing this. It is much closer compared with "0.433 and 0.449", am I right? For the first model, your number is actually better? A bit off is understandable due to data pre-processing differences.
If so, it tells that the problem is not the data, but your training process, which could be e.g., data balancing etc. How did you do that?
-Yuan

Thank you for your specific answer.

If so, it tells that the problem is not the data, but your training process, which could be e.g., data balancing etc. How did you do that?

That's a totally sensible thing to say!
But I didn't change anything except dataset mean and std in the "run.sh " file.

bal=bal
lr=1e-5
epoch=5
lrscheduler_start=2
lrscheduler_step=1
lrscheduler_decay=0.5
wa_start=1
wa_end=5
freqm=48
timem=192
mixup=0.5
fstride=10
tstride=10
batch_size=12
dataset_mean=-3.539583
dataset_std=3.4221482
audio_length=1024
noise=False
metrics=mAP
loss=BCE
warmup=True
wa=True

So, one of my options is to re-download AudioSet directly to 16kHz flac format file and test it again.
Thanks :)

So, one of my options is to re-download AudioSet directly to 16kHz flac format file and test it again.

My guess is that won't help as we saw the data isn't the problem.
For data balancing, we give a weight to each sample. But due to the nature of AudioSet is not a "stable" set, we do not have identical sets, so your sample weight file need to be regenerated. Have you done so? How did you do that?

I meant this: https://github.com/YuanGongND/ast/blob/master/egs/audioset/gen_weight_file.py
A mistake in generating the sample weight could cause a pretty large performance drop. Please see our PSLA paper for the comparison.

My guess is that won't help as we saw the data isn't the problem.

It make sense. I think you're right.

For data balancing, we give a weight to each sample. But due to the nature of AudioSet is not a "stable" set, we do not have identical sets, so your sample weight file need to be regenerated. Have you done so? How did you do that?

Yes. According to PSLA repo Step2, I created a sample's weight file for the full set json file.
Are there any specific things I need to be cautious about while doing this?
Thanks

I am not sure what could be the problem. Since using our norm stats for inference is fine, maybe you could try to use our normalization stats for training? But still I feel it would not cause such a large performance difference.
I am working on a deadline so cannot follow up this further, will check back after a week. This is not the version we used to train AST, but we got similar result on this version: https://www.dropbox.com/s/18hoeq92juqsg2g/audioset_2m_cleaned.json?dl=1.
You can check if the labels of the training set is consistent with yours.
-Yuan

Thanks. I will try with a new labels and let you know the result.

When I train with mean and std written in your code(-4.2677393, 4.5689974), I get the following results.

0.412 0.436 0.444 0.447 0.448
wa_result : 0.457

This is a much better result.
However, if i run "get_normal_stats.py" to calculate the mean and std of that training data, the mean is -3.3275723 and the std is 3.8845778.
We can get similar result with the mean, std wriiten in your code, but I wonder what the problem is fundamentally.

hi there,
thanks so much for reporting this.
I am not sure about the reason, in my experiments, the results are not sensitive to the input stats and we use different values for different projects. But I guess for now you can just use our mean/std.
A paper from other groups reports some details about mean/std: https://arxiv.org/pdf/2203.13448.pdf
-Yuan


Swap Camera for Image Entity

This swaps the Camera entity to an Image entity.

It seems like there is text missing for "Enable Image"

Shouldn't we change the state of the image to image_last_updated. So that we have a timestamp there instead of, the mower's state?

I've removed the 'HusqvarnaAutomowerStateMixin` class. Think, thats not relevant anymore. Is there a need to change the tests?

Look good. It feels like the image entity is faster than the camera entity.....
I've added some comments to the translations. I think there can be deleted some stuff. Can you have a look at this?
Further more I removed the HusqvarnaAutomowerStateMixin
I've you're okay with that, I think we can merge this. I assume, you have tested migration from the old to the new version? I didn't do that.

Look good. It feels like the image entity is faster than the camera entity..... I've added some comments to the translations. I think there can be deleted some stuff. Can you have a look at this? Further more I removed the HusqvarnaAutomowerStateMixin I've you're okay with that, I think we can merge this. I assume, you have tested migration from the old to the new version? I didn't do that.

I'll look this evening, I think the image entity is on average faster, but it seems to drag when using large images since we lose the ability to resize the image on the backend and that now has to be done in the front end.  I left the resize code in, hopefully that will get added back in HA and we can implement it.
I'm not certain about the state translations, thinking those should be removed in #511?  Will check to be sure.
I did test the migration, no issues found.
Didn't see any immediate concerns with 4dc8996 , but want to load it up in a codespace and just double check.

That are the state translation for the image. So they are not related to the other PR.

OK, this should be ready to merge now.

Hello @prairiesnpr @Thomas55555 ,
Thans for your update.
Before, I could take a snapshot, save it as JPG, and add the JPG to a notification.
Now that the camera entity doesn't exist anymore, I can't take a snapshot.
How can I attach a dynamic image to my notification now ?
Thanks in advance,

Hello @prairiesnpr @Thomas55555 , Thans for your update. Before, I could take a snapshot, save it as JPG, and add the JPG to a notification. Now that the camera entity doesn't exist anymore, I can't take a snapshot. How can I attach a dynamic image to my notification now ? Thanks in advance,

I'm using the same automation as before, just updated the camera entity to the image entity.
This is what I use now.
action:
  - variables:
      ha_url_var: !secret ha_url
      quest_update: '{{ states("sensor.aeinarr_error_quest_desc") }}'
  - service: notify.all_ios_devices
    data_template:
      message: '{{ state_attr("vacuum.aeinarr", "friendly_name") }} {{ quest_update }}'
      data:
        attachment:
          url: '{{ha_url_var}}{{ state_attr("image.aeinarr_map", "entity_picture") }}'
          content-type: jpg
          hide-thumbnail: false
  - service: notify.all_android_devices
    data_template:
      title: '{{ state_attr("vacuum.aeinarr", "friendly_name") }} Quest Update!'      message: '{{ state_attr("vacuum.aeinarr", "friendly_name") }} {{ quest_update }}'
      data:
        image: '{{ha_url_var}}{{ state_attr("image.aeinarr_map", "entity_picture") }}'

Hello @prairiesnpr ,
Thanks for sharing your code.
How do you manage !secret ha_url ?
I tested your code with the internal url of homeassistant and it works if I'm on the LAN
I tested with the external url and it works when I'm outside the LAN.
How to make it working as well if connected to the LAN than when I'm outside the LAN ?
Thanks,

In my setup, ha_url is just the external URL to my instance. I don't use the internal URL. That said, try DROPPING the URL, I don't think it's required.


npm run start.iosfailed, seems no link between nativescript and src/client folder?

npm run start.iosfailed, seems no link between nativescript and src/client folder?
app/app.ts(8,24): error TS2307: Cannot find module './app/frameworks/core/index'.

app/app.ts(19,27): error TS2307: Cannot find module './app/frameworks/sample/services/app-config'.

app/app.ts(20,37): error TS2307: Cannot find module './app/frameworks/i18n/services/multilingual.service'.

app/native.module.ts(16,65): error TS2307: Cannot find module './app/frameworks/core/index'.

app/native.module.ts(18,32): error TS2307: Cannot find module './app/components/about/about.component'.

app/native.module.ts(19,31): error TS2307: Cannot find module './app/components/home/home.component'.

app/native.module.ts(20,24): error TS2307: Cannot find module './app/components/app.routes'.

app/native.module.ts(23,28): error TS2307: Cannot find module './app/frameworks/core/core.module'.

app/native.module.ts(24,33): error TS2307: Cannot find module './app/frameworks/analytics/analytics.module'.

app/native.module.ts(25,36): error TS2307: Cannot find module './app/frameworks/i18n/multilingual.module'.

app/native.module.ts(26,30): error TS2307: Cannot find module './app/frameworks/sample/sample.module'.

app/pages/app/app.component.ts(9,30): error TS2307: Cannot find module '../../app/components/app.component'.
app/pages/app/app.component.ts(10,28): error TS2307: Cannot find module '../../app/frameworks/core/index'.
app/pages/app/app.component.ts(11,34): error TS2307: Cannot find module '../../app/frameworks/analytics/index'.
app/shared/core/services/window-native.service.ts(5,23): error TS2307: Cannot find module '../../../app/frameworks/core/interfaces/iwindow'.
app/shared/core/utils/actionbar.util.spec.ts(1,17): error TS2307: Cannot find module '../../../app/frameworks/test/index'.
app/shared/nativescript/index.ts(6,32): error TS2307: Cannot find module '../../app/frameworks/analytics/index'.

Several users encountered this in the workshop. I wonder what the workaround is? I feel it's a corrupted simlink

have you tried to grab a brand new clean seed and try it again?
/nativescript/app should be a simlink to /src/client/app, check /nativescript/app properties, that might give you a hint

Symlinks are created during the postinstall step, so running node tools/install.js again might help.

Closing as this appears to be an issue where post install did not run.
Rerunning npm i after cleaning should solve it.


Lambdat tagging

This PR adds tagging of lambda functions when using zappa deploy and update
zappa deploy --lambda-tags '{"alpha":"beta"}'
zappa update --lambda-tags '{"hash":"commithash"}'
Relevant tickets
https://github.com/Miserlou/Zappa/issues/1583
https://github.com/Miserlou/Zappa/issues/860
https://github.com/Miserlou/Zappa/issues/700

Is there a reason this makes more sense as a command line argument instead of living in the zappa_settings? Unless I'm missing something, it sounds like it should be the latter…

perhaps my lack of familiarity with the zappa way of doing things? I was looking for a way to tag functions and other aws assets when deploying or updating. I could preprocess a zappa_settings template add my tags and then then run zappa update or zappa deploy but to me it felt more sensible to tag them from the prompt. I don't really like the idea of littering my repository with settings files for each update.


Feature Request: Initiate multiple instances of same dag in parallel?

Request:  We'd love to be able to run the same dag in parallel with different input, preferably from an operator.  This would enable batch processing of content to be parallelized via the messaging/executor framework, while each manipulation of the data is its own operator and hence individually testable and recomposable (plus all other great features).
Something along the lines of:
class DagExecutingOperator():
  def execute(self, context):
    for item in somelist:
      dag.execute(params={'input':item})

Here's our use case, and what I think we would like to support it, but as a novice airflower (:dash::tulip:), any pointers in better directions would be greatly appreciated.
We have a reasonable chunk of data in a system that we want to migrate away from, but there are so many business processes associated with it, that will be a multi-year project. In order to convince our stakeholders of the correctness of any new solution, we're going to have to iterate over and over this dataset making incremental improvements (you all know how it is, I'm sure!).
We've been experimenting with two approaches, breadth-first and depth-first:

Breadth-first: The DAG does (say) 10 steps, where each step does one process on every record.  We can parallelize by partitioning the data and setting the first step of the DAG to check if there's a partition not being processed, but the resource contention is huge, as all of the same compute/IO resources are needed at the same time... for example, the last step of writing the merged record to a database means that we're blocked on IO while the rest of the system stands idle.

Depth-first: So we went back to depth-first where a single record flows all the way through the DAG before returning to the next one.  We tried various nasty tricks (have you tried setting the heartbeat configs to 0 with a schedule_interval of 1 second? :smile_cat: ) but at the end of the day, it seems like an iterator that kicks off DAGs would solve our issue in a way that we could use the scheduling code as it's intended.

Any advice or thoughts would be appreciated.

Are you trying to do stream processing with Airflow? Airflow is a batch workflow engine, not a stream processing engine. If the duration of most of your batch jobs is less than a few minutes, Airflow probably isn't the right system.
The schedule interval we use is usually 1 day, but have many hourly DAGs that work very well. As you get closer to 5 minutes scheduler intervals, you need to start thinking in terms of realtime / stream processing and use the systems designed to do that (storm, spark streaming, ...)
What is your unit of work? What's you pivot point, as in one dag per blank ? file?
btw you can generate dags dynamically, the same way that you can generate tasks dynamically, you just have to stamp it in the global namespace of your module. But I get a sense that you are bending Airflow in doing things it wasn't designed for, which is fine if it works for you.
business_units = ['CA01', 'US01', 'US02']
for bu in in business_units:
    globals()[bu] = DAG(dag_id=bu)
    ...

All of these would show up in the UI

Re-open if needed.


AppArmor fails to load with kernel 5.1.0

Issue description
Upgrading to kernel 5.1.0 from pkgs.linuxPackages_latest breaks apparmor, preventing it from loading. Furthermore, this also breaks nixos-rebuild switch, requiring a kernel downgrade to pkgs.linuxPackages_5_0 (kernel 5.0.13) to fix this.
The error is:
[sudo] password for william:
unpacking channels...
building Nix...
building the system configuration...
activating the configuration...
setting up /etc...
reloading user units for william...
setting up tmpfiles
the following new units were started: cpu-throttling.service
warning: the following units failed: apparmor.service

● apparmor.service
   Loaded: loaded (/nix/store/csxmp1iy3f5ijy8m0ajx6ch5n8milljc-unit-apparmor.service/apparmor.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-05-08 10:29:31 EDT; 17ms ago
  Process: 2996 ExecStart=/nix/store/5v3ysffjypsndwxkh16byzaa3g55lz4g-apparmor-parser-2.13.1/bin/apparmor_parser -rKv -I /nix/store/gj3zvpgbsnx85nbbrpb5s2kjz4y85w80-apparmor-profiles-2.13.1/etc/apparmor.d -I /nix/store/pmgymay0liaz5xy65z9n029v2qn6k79v-lxc-3.1.0/etc/apparmor.d /nix/store/pmgymay0liaz5xy65z9n029v2qn6k79v-lxc-3.1.0/etc/apparmor.d/usr.bin.lxc-start (code=exited, status=1/FAILURE)
 Main PID: 2996 (code=exited, status=1/FAILURE)

May 08 10:29:31 helium systemd[1]: Starting apparmor.service...
May 08 10:29:31 helium apparmor_parser[2996]: Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found
May 08 10:29:31 helium apparmor_parser[2996]: Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
May 08 10:29:31 helium apparmor_parser[2996]: Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
May 08 10:29:31 helium apparmor_parser[2996]: Use --subdomainfs to override.
May 08 10:29:31 helium systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
May 08 10:29:31 helium systemd[1]: apparmor.service: Failed with result 'exit-code'.
May 08 10:29:31 helium systemd[1]: Failed to start apparmor.service.
warning: error(s) occurred while switching to the new configuration

I believe the main issue is from this line here: apparmor_parser[2996]: Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Steps to reproduce
boot.kernelPackages = pkgs.linuxPackages_latest; and security.apparmor.enable = true; should be sufficient to reproduce the problem, although apparmor was already implicitly enabled on my system. I believe it's because of lxd.
Technical details
➜  ~ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.1.0, NixOS, 19.09pre178846.7defc47944f (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(root): `"nixos-19.09pre178846.7defc47944f, nixos-hardware"`
 - channels(william): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

It can alternatively be reproduced with boot.kernelPackages = pkgs.linuxPackages_latest; and virtualisation.lxd.enable = true;. I've removed the second part as a workaround.

I can reproduce the apparmor issue (on unstable-small 19.09pre179342.0fe5e0279fe), but I can keep rebuilding once apparmor.service fails. Not sure if I'm understanding that part right though...

Off the top of my head I'd guess that this is related to securityfs not being mounted; is it? (should be at /sys/kernel/security). I recently tweaked the ordering of the apparmor unit, so this could be fallout from that.

Hm, from my testing it seems that the selinux lsm is selected by the kernel at boot instead of apparmor for whatever reason under 5.1. I do note that linux_latest.configfile no longer explicitly sets the default security= boot parameter to "apparmor".
Can you check dmesg output? When apparmor is selected, you should see something like "apparmor filesystem initialized"; if that is missing, look for mentions of selinux.
Explicitly setting boot.kernelParameters = [  "security=apparmor" ]; fixes the issue on my end.

I believe this has been fixed. Please reopen if the problem persists.

This is a problem again. Would somebody please re-open this issue?

Hmmm, this seems to be fixed by a reboot. Is there some way to say "reboot required" from nixos-rebuild switch?

This should re-opened. I can reproduce this on nixos-unstable when enabling lxd.

Hmmm, this seems to be fixed by a reboot. Is there some way to say "reboot required" from nixos-rebuild switch?

I just had the same issue and reboot indeed fixed it, thanks a lot

Hmmm, this seems to be fixed by a reboot. Is there some way to say "reboot required" from nixos-rebuild switch?

Or better yet, make the reboot unnecessary :-) Either way the problem still exists and significantly impacts usability... any plans on addressing it?


Fix source declaration

Currently puppet runs on reports.service0.mad1.bwcom.net are failing with the message:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, assert_type(): expected a match for Pattern[/\A((hkp|http|https):\/\/)?([a-z\d])([a-z\d-]{0,61}\.)+[a-z\d]+(:\d{2,5})?$/], got 'https://apt.dockerproject.org/gpg/' at /etc/puppetlabs/code/environments/fix_puppet_docker_key_location/modules/apt/manifests/key.pp:23:5 at /etc/puppetlabs/code/environments/fix_puppet_docker_key_location/modules/apt/manifests/source.pp:94 on node reports.service0.mad1.bwcom.net
This is due to a typo in previous commit to use the new puppetlabs-apt syntax.
This fixes the issue (tested against my local branch)


SAK-41604 Add group support to rubrics

https://jira.sakaiproject.org/browse/SAK-41604

SAK-41604 #comment Test JIRA Comment

SAK-41604 #comment Test JIRA Comment

@ern Could you take another look at this? I removed that NONE enum


Styling improvements

We want some styling improvements

[ ] on the annotation pages, the upload-and-confirm buttons should be called "Save Annotation"
[ ] these buttons should also be grey when deactivated, consistent with the "Next Step" button style
[ ] all template cardnames (I am a header ...) should be replaced with something meaningful
[ ] cards on the annotation page should have some vertical spacing
[ ] all tables should use the striped-style
[ ] the tool name should be changed from "Origami ..." to "Metabagel (?) Annotation Tool"
[ ] color on the annotation tabs should match the category colors (optional)
[ ] check if we can make better use of whitespace in the annotation app to make things look "nice" (optional)

One note here while I work on this.

all tables should use the striped-style

Striped tables break the table painting on the categorization page. So this is a no-go there.

OK, could we just use them on the annotation page? If not, go with whatever is easiest here!

I believe all of these style improvements have now been addressed as of #108. @surchs Can you confirm?

Closing this issue as everything in it that will be addressed has been addressed.


Make before() hook compatible with apps which did not import main/preload scripts

Fixes #461

Thanks for the quick fix @gavvvr!


Bump rust version

rustc changes: https://github.com/rust-lang/rust/pull/98811
rustc issue: https://github.com/rust-lang/rust/issues/98922

@bors r+

:pushpin: Commit afb937ab25e17adc5f2b76fcdf64d8804bdd65b9 has been approved by oli-obk

:hourglass: Testing commit afb937ab25e17adc5f2b76fcdf64d8804bdd65b9 with merge 178e7f3f332bac8be6bc9c33ad1f811ddc5c4e39...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing 178e7f3f332bac8be6bc9c33ad1f811ddc5c4e39 to master...


Add extra time to the error reporting integration tests.

The tests started failing a few days ago, it looks like they are taking a little longer to get processed.

Thanks Jon!


Feature/filter by related data

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@65d0e3c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #41   +/-   ##
==========================================
  Coverage           ?   17.22%
==========================================
  Files              ?        4
  Lines              ?      267
  Branches           ?       81
==========================================
  Hits               ?       46
  Misses             ?      174
  Partials           ?       47

Flag
Coverage Δ

unittest
17.22% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 65d0e3c...c7bfccc. Read the comment docs.


Jeff Schaller: Watch ryouma.xyz

Jeff Schaller requests the watch of the watch_keyword ryouma\.xyz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ryouma\.xyz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by NobodyNada in Charcoal HQ


latex formatter with colored string background: spacing and box height

(Original issue 670 created by gnarly on 2011-06-03T13:39:08.569079+00:00)
If I use a style with colored string backgrounds, the formatted string will have a single excess space following the opening quotes and leading the closing quotes, respectively.
Let's say I have a file foo.c including the line
printf("\n");
And I pygmentize it
pygmentize -l c -O full,style=colorful -f latex -o bar.tex foo.c
The output will look like
printf("\n")
Furthermore, if the string, like the above, contains special characters, these will be put in a separate box with their own height. So the string background is not uniform and has small visible vertical white spaces.

(Original issue 670 last updated on 2011-06-21T20:23:01.835393+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2011-06-19T07:38:47.606378+00:00)
Should be fixed in <<changeset 9a979a93ce40>>. Thanks for the report.

(Original comment by gnarly on 2011-06-21T20:23:01.826085+00:00)
Thanks a lot. Looks fine now.


Monitoring fails to deploy with persistent storage

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Enable monitoring with persistent storage
Result:
prometheus-cluster-monitoring-0 fails to deploy with the error: Error while running "VolumeBinding" filter plugin for pod "prometheus-cluster-monitoring-0": could not find v1.PersistentVolume "pvc-5c905e4b-86ab-11e9-84af-005056a0ed7e"
Other details that may be helpful:
Tried different storage solutions: gluster longhorn
Environment information

Rancher version 2.3.4
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Rancher launched cluster

Machine type (cloud/VM/metal) and specifications (CPU/memory): VMWare

Kubernetes version (use kubectl version): 1.17.0

Docker version (use docker version): 19.3.5

I believe this is a duplicate of https://github.com/rancher/rancher/issues/17256

@jiaqiluo Can we verify if Monitoring 0.1.1 fixed this issue or not?

The bug is fixed in the latest chart v0.1.1
see this issue for more info: https://github.com/rancher/rancher/issues/26969
and this comment for the validation steps: https://github.com/rancher/rancher/issues/17256#issuecomment-643371125


Fixing markup

Hi!
Per this issue from September, markup doesn't seem to work in scrolllabels.
https://github.com/kivy/kivy/issues/3615
This pull request fixes that.  The test case in the pastebin linked in that old issue, as well as my own code, now render markup correctly (tested only with colors, but nothing at all was working before).
Thanks,
Vitorio

Thanks!


WIP: Adding ClearDisplay

Trying to add primitive so display may be cleared from Haskell.

This does not seem to be getting much activity and I have not checked whether it works, so closing this. Will open a new issue for this functionality though.


ARR Workflow: Add Ethics Reviewer Matching step

The EMNLP and ARR ethics chairs are proposing to make the following changes to the ethics reviewing period:

Add a new unavailability form for ethics reviewers, including the long-term unavailability logic for reviewers and area chairs
Send messages to ethics chairs when ethics reviews are submitted
Some kind of commenting for ethics chairs and ethics reviewers, either a separate invitation or modifying the ethics flag process function to add/remove ethics chairs to the official comment invitation

@celestemartinez can you work on items 2 and 3?

I think bullet 1 is fixed here: https://github.com/openreview/openreview-py/pull/2184

@haroldrubio I think this issue is fixed now, right?


Column names should all be lower initial

Currently, we have columns that mix case conventions. Should all be SQL style.

Now the table is as follows


Rename local sub command

Before
duci local

duci run

Pull Request Test Coverage Report for Build 1159

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.323%

Totals

Change from base Build 1155:
0.0%

Covered Lines:
1176

Relevant Lines:
1302

💛  - Coveralls


Only one type of contributes entry is displayed for Extension Details Contributions

VSCode Version: 1.7.0 insiders
OS Version: Windows 7

Steps to Reproduce:

Look at an extension (Go, Python) which has a number of different types of contributions (settings, commands, language).
Extension details view Contributions only shows Settings

This does not repro for 1.6.1 stable

Great catch.

@sandy081 This was broken by aa4efa36

@joaomoreno That was a very bad mistake. I should have swapped computation of && arguments. Your fix looks simple and nice.


feat: Use current script URL as base if not configured

Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
#201
Thanks for contributing!

@chicharr I removed the use of optional chaining


Create Elchemy organisation on GitHub

I'm not completely aware of what are the gains of moving a repo into an organisation, but it seems that our community is growing to the point of it being a good idea.
Is anyone familiar with what are the pros and cons of moving a repo into an organisation?
Repos that would be moved:
wende/elchemy
wende/elchemy-core
wende/elchemy-live
Baransu/elchemy-page
And with a confirmation from Bogdan Popa maybe Bogdanp/elm-ast as well, since it's being mostly developed by our contributors (68.6% commits and 71.7% LOC according to git-extra summary)
Here are pros and cons I can think of:
Pros

More convincing branding (People seem to trust organisations more than single developers)
Better incentive for contributors to be a part of the community
One common group for all of the Elchemy-related repositories
(???)

Cons

A lot of renaming in domains, articles, links etc
Changing a link will make a lot of mentions around the web point to 404 (after a while when Github stops redirecting)
(???)

Changing a link will make a lot of mentions around the web point to 404 (after a while when Github stops redirecting)

Can always set up this repo again as a bounce repo to point to the main one in that case.
Regardless, still better to do this early/now than later, even with a few occasionally broken links.  :-)

Yes, I agree with Overmind here.
The longer you wait, the more you break ;)

When you transfer from personal to org GitHub handles redirection, I would guess the mentions you're referring to would not result in 404s.

I currently have the github organization named 'elchemy' and I don't mind giving you the name - gratis.  (github.com/elchemy)
'Elchemy' is a name worthy of a full-featured Elixir web framework.   Any chance for Elchemy to develop  into a full-featured Elixir framework like Phoenix - with Channels,  etc ?
Maybe you could team up with Ace + Raxx (https://github.com/CrowdHailer/raxx)  for the back-end webserver and  Drab (https://tg.pl/drab) for responsive server-controlled pages...

@joelseagull Hi! That's so nice of you!
We have a plan to release a type safe wrapper around Phoenix, as a matter of fact there has been some attempts to do PoC around Plug.Conn. Currently, however the whole project is in a state of a hiccup because of destructive impact of Elm 0.19. We will be moving away from Elm's compiler, of which we were (and still are) using the type checker. It will be rewritten and thanks to that also possibly extended by some features (if the community decides something worth it). However, we always plan to keep to be a superset of Elm and allow to compile Elm's libraries. Given that now they don't allow calling Native it's going to be easier to control that
I didn't know about existence of neither Ace or Raxx. I'll definitely check them out

@joelseagull Drab looks amazing. Though I think it might get overshadowed by current developments of Phoenixe's LiveView
https://shift.infinite.red/phoenixs-liveview-client-side-elixir-at-last-2280716ae791

🎉 🎉 🎉
https://github.com/elchemy
🎉 🎉 🎉

Just for note, thus far everything stated about LiveView already exists in Drab.Live, and Drab has a lot more functionality than just that (including the shared commanders are amazing), in addition the other modules can be used to build real-time interop with other JS libraries instead of just 'owning' the entire thing like LiveView is expected to do.  LiveView is a minimal implementation to get going.


Use custom font

This PR consists of two parts:

Replace all occurrences of fontFamily = FontFamily("Roboto") with fontFamily = appFontFamily, where appFontFamily links to the CircularStd font.
Add a default typography to the Material Theme that overrides all font families with CircularStd

Old vs New:

Thank you! One issue I see is that on the new screenshot, all texts moved upwards somewhat. It's especially visible on menu item texts and search bar text which lost its vertical centering. I wonder if that can be fixed with any font setting without manually changing positionings all around the app?

I've been looking at it, but can't figure it out. Maybe you can help. What would cause the text to be aligned correctly in the first place? For example, if we look at the RoundedSearchBar it contains a Row which contains the image, a Spacer, and a Text. Why would the Text there be vertically aligned within the room that the image is taking? Is that a property of the Row?

I've done some more investigation, here are my findings:
On master, we can look at the Preview with and without the material theme applied. We see that the material version correctly aligns the text in the center, which seems to be coincidence since the non-material themed version has a smaller font which isn't aligned in the center.

When we just change the font size of the text in the search bar, we see the same effect:
Text("Search Pokemon, Move, Ability, etc",
                    style = MaterialTheme.typography().body1.copy(fontSize = 8.sp))

When we use a custom font, the height of this font will naturally be a bit different from the Roboto font. Since changing the height leads to issues with alignment when we didn't explicitly align the Text composable, we see that the custom font is not aligned well.
I would propose to fix this by explicitly aligning the text in the center of its parent. I'll give that a try next!

Search bar and menu item have been fixed to correctly align. For the Search bar, I used LineItem from Compose toolkit as a reference.
New screenshot:

Amazing job there @JolandaVerhoef, thanks for all your time and effort!


Auto switch between dark/light according to system wide setting

Currently we need to  manually switch between them.

This is not something that this theme controls, this is something which needs to baked into Gitea itself.
Looks like it will be available as of v1.16: https://github.com/go-gitea/gitea/pull/17051


⚠ Bofrost.be has degraded performance

In cf9691f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1104 ms

Resolved: Bofrost.be performance has improved in 733458e after 6 minutes.


Fixed asset pipeline issues with patternfly

The JS assets needs to be required ONLY in the application.js file,
and then this file is loaded by javascript_link_tag('application').
PatternFly needs to be included as a bower dependency if you want to
have its JS dependencies. Unfortunately there is no other way :(
I assume that angular will be used in this repo, so I changed the
bower dependecy to angular-patternfly-sass which also loads the
JS deps the same way as patternfly-sass.

Great!
Testing it


adding package's to the environment

sometimes I want to put rustPlatform.rustcSRC into RUST_SRC_PATH, so it will return the evaluated path.
maybe the implementation is like:
[env]
RUST_SRC_PATH="(rustPlatform.rustcSrc)"

I'm not sure it is possible in toml.

Yeah not sure how you'd do it in toml.
I don't see anything in the tests for the builtin that lets you nix from inside evaluate
https://github.com/NixOS/nix/blob/94f11d0a61bba15ff8a93f2de8d1883783c8c508/tests/lang/eval-okay-fromTOML.nix
This worked just using nix though:
{}:
# ...
{
  # ...
  env.RUST_SRC_PATH="${pkgs.rustPlatform.rustcSrc}";
}

Full shell.nix:
{ system ? builtins.currentSystem }:
let
  pkgs = import ./nix/nixpkgs.nix { inherit system; };
in
pkgs.mkDevShell {
  name = "something";
  motd = "otherthing";
  commands = [
    {
      name = "something";
      help = "this is help";
      command = "echo something";
    }
  ];
  env.RUST_SRC_PATH="${pkgs.rustPlatform.rustcSrc}";
  packages = [ ];
}

@06kellyjac yeah I manage to do that also. However, the case that I am facing is wrt to this:
  shellHook = ''
    export GO111MODULE=on
    unset GOPATH GOROOT
  '';

unset GOPATH and GOROOT is essential so that my VSCode's go plugin can work.

I think I am gonna use mkDevShell right now.


Fork(pty3) error when starting a terminal

When opening a terminal in VSCode on a RHEL7 box I receive the error "The terminal process failed to launch: A native exception occurred during launch (fork(pty3) failed.).". I receive the same while using the Remote-SSH extension from a Windows client to the RHEL7 box.
Locally

VSCode Version: 1.49.2
OS Version: RHEL7
Logs: "The terminal process failed to launch: A native exception occurred during launch (fork(pty3) failed.)."

Via Remote-SSH

VSCode Version: 1.67.2
Local OS Version: Windows 10 1607 LTS
Remote OS Version: RHEL7
Remote Extension/Connection Type: SSH
Logs: "The terminal process failed to launch: A native exception occurred during launch (fork(pty3) failed.)."

I cannot reproduce this issue on a similar RHEL8 box where all configurations (SSHD etc) and /dev/pt* permissions are the same

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

This issue has persisted several versions and methods, I doubt it would be version specific at all.

I cannot reproduce this issue on a similar RHEL8 box where all configurations (SSHD etc) and /dev/pt* permissions are the same

As you suggest, this is an issue w the linux variant, so don't think there's anything that can be done on our side about this

I was able to finally resolve this by changing the mount permissions of /dev/pts
https://www.linuxquestions.org/questions/linux-newbie-8/need-solution-to-failed-to-fork-pty-and-error-creating-the-child-process-problems-777130/
I copied from a working box and used
devpts /dev/pts devpts rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptxmode=000

Originally mount | grep pts showed no gid and mode=600 which I think was my issue. I have no clue how that configuration could have been put in place, as PTS was never in the fstab


🛣 Roadmap 🎯

The project probably need a kind of Roadmap.
Not necessary something very accurate but at least some hints for the community about the direction of the project.
You can have a look at what is done for Leshan even if this is probably not the better example.
I think this is probably linked in a way to those topics :

the future of the 1.0 version. (#487)
Defining supported compilers, architectures, language versions (#494)

Having a roadmap which leads to a Wakaama 2.0 (?) version would be very nice. We need to identify what is missing for LWM2M 1.0 and 1.1. and what we want to have in a future release. @qleisan you already started a list of supported features? Having a dedicated roadmap wiki page like the one at Leshan may help. Simultaneously, we can remove the TODO file from the repository.
However, features we consider supported should have at least some basic tests (which integrates with the CI), so we can be sure to not break thinks. Some work in this regard is ongoing #598.

I agree. Tests also help to clarify what is supported (partially or fully).

For any subsequent release:

definitely more testing than what we have currently
Proper developer documentation (neither the current README.md nor the GitHub-Bound Wiki is well-enough solution): #586
Copyright Headers: SPDX #584

For a 2.0 release:

A better API: #544
Switch to main :)
All findings by code analyzing tools dealt with (Clang static analyzer, SonarQube)

When will the next official version of wakaama be released?

Actually there is no release plan as features are implemented on a voluntary basis as needed. That said I think we should perhaps do a a new release since quite a few new features has been added since the last release. What do you think @rettichschnidi, @mlasch


Issue 138 Updated type checking on input to use IsAssignableFrom

Fixed issue #138, changed type checking to allow inheritance instead of a direct type check.

Codecov Report

Merging #146 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #146   +/-   ##
=======================================
  Coverage   77.07%   77.07%
=======================================
  Files         113      113
  Lines        3014     3014
  Branches      345      345
=======================================
  Hits         2323     2323
  Misses        633      633
  Partials       58       58

Impacted Files
Coverage Δ

src/SpecBind.CodedUI/CodedUIPage.cs
0% <0%> (ø)
:arrow_up:

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 d5bade1...033d351. Read the comment docs.


Understanding the paper

Could anyone please make me understand the difference between the first quantizer and acoustic prompt? As both of the Symbols looks to be same.
Atleast with respect to the code

The quantizer is the first layer Residual Quantizer (VQ-1) There are really two parts to this.

wavform is passed through the Encodec pretrained model to compress the wavform. ( about 75 frames/1 second of audio).  The residuals are computed for all 8 layers. This is used as the embedding space for the Transformer decoder model ( 12 layer 16 multi head attention layers). With an embedding space of 1024 ( number of codebook indices)

The transformer LM is trained within this embedding space in two parts ( AR and NAR).

The resulting approximation Matrix is then sent through the Decoder of the Encodec model and outcomes the reconstructed wav form

In the equation above. A prompt segmentation of the original audio is used ( I think they mention 3 seconds, or 10 seconds. Don't remember. But they do segment it. ) This is used as the prompt or input to the Transformer Decoder. The rest of it is used as the target ( to compute loss).
The equation above basically says "Given the phoneme sequence x, Prompt sequence C ( matrix as its time based), what is the probability of getting the target. The result is a response matrix which is compared against the target for loss.

"the first quantizer and acoustic prompt", they are different concept and thus can't be compared together.
I think you are talking about first quantize layer codes of the prompt audio and of the predicted continual audio.
As state in the paper, we do not distinguished these two segments when training AR, meaning there's no prompt at all, or you can say all preceding frames are prompt to the current frame.
At inference stage, given 3s or more initial audio segment, this 3s segment naturally becomes the prompt to all the future generated continual frames.


Create new release

Hi @LilithWittmann @wirthual, there have been a couple of changes since the last release end of 2022. Could please create a new release of the library?
Thanks in advance

Working on it. I will release 0.3.2 which will be the last release supporting 3.6 and maybe 3.7 since its EOL is in 2 weeks anyways.

Tag 0.3.2   just got released


changed background and color scheme & added a header.

Can someone review this and let me know if i should change anything!


Get recent version for pygalmesh for Windows on conda

pygalmesh is hosted on conda: https://anaconda.org/conda-forge/pygalmesh
However, the Windows version lags behind on the Linux / OSX versions. It would be nice if the Windows binaries would also be available, because pygalmesh is tricky to build on Windows otherwise for inexperienced users.

Depends on #5

No longer needed with #124


@broskoski: safeguard article thumbnail image

Noticed that not all articles have a thumbnail and the ones that didn't had broken pages. This adds a safeguard. I don't know if we would want to not show articles that don't have an image, but I figure this at least fixes the broken pages.

👍