🐛 [firebase_crashlytics] I have upgraded the plugin to 0.2.0 but crash are not been getting reported to firebase console

Bug report
Describe the bug
I have upgraded the plugin to 0.2.0 but crash are not been getting reported to firebase console
it shows this E/AndroidRuntime(22056): io.flutter.plugins.firebase.crashlytics.FirebaseCrashlyticsTestCrash: This is a test crash caused by calling .crash() in Dart.
but error are not getting reported to console
Steps to reproduce
Steps to reproduce the behavior:
1.i have follow the document but the error are not been reported to console
Expected behavior
the error crash or log show get reported to console

Additional context
this issue issue is been occurred after I have upgraded to 0.2.0 before this the report we caught by console but after upgrade its not

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 1.20.4, on Microsoft Windows [Version 10.0.18362.1082], locale en-IN)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 4.0)
[√] VS Code, 64-bit edition (version 1.49.1)
[√] Connected device (1 available)

• No issues found!

flutter doctor -v
D:\daq-dynamic>flutter doctor -v
[√] Flutter (Channel stable, 1.20.4, on Microsoft Windows [Version 10.0.18362.1082], locale en-IN)
    • Flutter version 1.20.4 at C:\flutter
    • Framework revision fba99f6cf9 (10 days ago), 2020-09-14 15:32:52 -0700
    • Engine revision d1bc06f032
    • Dart version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\jk\AppData\Local\Sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = C:\Users\jk\AppData\Local\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 64-bit edition (version 1.49.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.14.1

[√] Connected device (1 available)
    • ONEPLUS A3003 (mobile) • <IP_ADDRESS>:5555 • android-arm64 • Android 9 (API 28)

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
D:\daq-dynamic>flutter pub deps -- --style=compact
Dart SDK 2.9.2
Flutter SDK 1.20.4
daq_flutter 3.0.5+6

dependencies:
- amazon_s3_cognito 0.2.4 [flutter]
- auto_size_text 2.1.0 [flutter]
- autocomplete_textfield 1.7.3 [flutter]
- camera 0.5.8+5 [flutter]
- connectivity 0.4.6+2 [flutter meta]
- cupertino_icons 0.1.3
- custom_radio_grouped_button 1.0.0 [flutter]
- datetime_picker_formfield 1.0.0 [flutter intl]
- dio 3.0.8 [http_parser path]
- dio_retry 0.1.9-beta [meta logging dio]
- draggable_scrollbar 0.0.4 [flutter]
- dropdown_menu 1.1.1 [flutter]
- email_validator 1.0.4
- firebase_core 0.5.0 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.2.0 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_image_compress 0.6.5+1 [flutter]
- flutter_launcher_icons 0.7.4 [image args yaml]
- flutter_local_notifications 1.4.1 [flutter platform flutter_local_notifications_platform_interface]
- flutter_screenutil 2.3.1 [flutter]
- flutter_typeahead 1.8.0 [flutter flutter_keyboard_visibility]
- fluttertoast 4.0.1 [flutter flutter_web_plugins]
- gallery_saver 1.0.7 [flutter path_provider http path]
- geocoder 0.2.0 [meta flutter]
- google_map_location_picker 3.3.5 [flutter flutter_localizations intl intl_translation google_maps_flutter geolocator android_intent provider http stack_trace package_info]
- image_picker 0.6.7+4 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- intl 0.16.1 [path]
- list_tile_switch 0.0.2 [flutter]
- location 2.3.5 [flutter]
- mobile_popup 1.2.0 [flutter]
- month_picker_dialog 0.3.2 [flutter flutter_localizations intl flutter_cupertino_localizations rxdart]
- notifier 1.0.2 [flutter synchronized]
- path_provider 1.5.1 [flutter platform meta]
- pull_to_refresh 1.5.8 [flutter]
- scoped_model 1.0.1 [flutter]
- shared_preferences 0.5.10 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web]
- sliding_up_panel 0.3.6 [flutter]
- slugify 1.0.0
- sqflite 1.1.0 [flutter synchronized path]
- video_compress 2.0.0 [flutter]
- video_player 0.10.12+2 [meta video_player_platform_interface video_player_web flutter]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- _fe_analyzer_shared 2.1.0 [meta]
- analyzer 0.39.6 [_fe_analyzer_shared args charcode collection convert crypto glob html meta package_config path pub_semver source_span watcher yaml]- android_intent 0.3.7+3 [flutter platform meta]
- archive 2.0.13 [crypto args path]
- args 1.6.0
- async 2.4.2 [collection]
- boolean_selector 2.0.0 [source_span string_scanner]
- characters 1.0.0
- charcode 1.1.3
- clock 1.0.1 [meta]
- collection 1.14.13
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.4 [collection convert typed_data]
- csslib 0.16.1 [source_span]
- dart_style 1.3.4 [analyzer args path source_span]
- equatable 1.1.1 [collection meta]
- fake_async 1.1.0 [clock collection]
- file 5.2.1 [intl meta path]
- firebase 7.3.0 [http http_parser js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.0 [firebase firebase_core_platform_interface flutter flutter_web_plugins meta js]
- firebase_crashlytics_platform_interface 1.0.0 [flutter meta collection firebase_core plugin_platform_interface]
- flutter_cupertino_localizations 1.0.1 [flutter flutter_localizations]
- flutter_keyboard_visibility 0.7.0 [flutter]
- flutter_local_notifications_platform_interface 1.0.1 [flutter plugin_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- flutter_plugin_android_lifecycle 1.0.4 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- geolocator 5.3.2+2 [flutter meta equatable google_api_availability location_permissions vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- google_api_availability 2.0.4 [flutter]
- google_maps_flutter 0.5.32 [flutter flutter_plugin_android_lifecycle google_maps_flutter_platform_interface]
- google_maps_flutter_platform_interface 1.0.4 [flutter meta plugin_platform_interface stream_transform]
- html 0.14.0+3 [csslib source_span]
- http 0.12.2 [http_parser path pedantic]
- http_parser 3.1.3 [charcode collection source_span string_scanner typed_data]
- image 2.1.12 [archive xml]
- image_picker_platform_interface 1.1.0 [flutter meta http plugin_platform_interface]
- intl_translation 0.17.9 [analyzer args dart_style intl path petitparser]
- js 0.6.1+1
- location_permissions 3.0.0+1 [flutter meta]
- logging 0.11.4
- matcher 0.12.8 [stack_trace]
- meta 1.1.8
- nested 0.0.4 [flutter]
- node_interop 1.0.3 [js]
- node_io 1.0.1+2 [node_interop path]
- package_config 1.9.3 [path charcode]
- package_info 0.4.0+16 [flutter]
- path 1.7.0
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_platform_interface 1.0.3 [flutter meta platform plugin_platform_interface]
- pedantic 1.8.0+1
- petitparser 2.4.0 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.2 [meta]
- process 3.0.13 [file intl meta path platform]
- provider 4.3.2+2 [flutter nested collection]
- pub_semver 1.4.4 [collection]
- quiver 2.1.3 [matcher meta]
- rxdart 0.24.1
- shared_preferences_linux 0.0.2+2 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 0.0.1+3 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 1.0.1 [meta flutter]
- shared_preferences_web 0.1.2+2 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- sky_engine 0.0.99
- source_span 1.7.0 [charcode collection meta path term_glyph]
- stack_trace 1.9.5 [path]
- stream_channel 2.0.0 [async]
- stream_transform 1.2.0
- string_scanner 1.0.5 [charcode meta source_span]
- synchronized 1.5.3+2
- term_glyph 1.1.0
- test_api 0.2.17 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.2.0 [collection]
- vector_math 2.0.8
- video_player_platform_interface 2.1.0 [flutter meta]
- video_player_web 0.1.3+2 [flutter flutter_web_plugins meta video_player_platform_interface]
- watcher 0.9.7+14 [async path pedantic]
- xdg_directories 0.1.0 [path process flutter]
- xml 3.6.1 [collection convert meta petitparser]
- yaml 2.2.0 [charcode collection string_scanner source_span]

** And Please read this issue its on new release version that on 0.2.0 **
so I have follow all the procedures which are required but its has been more than 48 hrs the crash is not yet reflected on firebase crashlytics dashboard
Also i have seen the reference given on  #3534
My issue is different from that issue so please check the issue also please dont directly close this issue.
Kindly requested to see into this issue asap!
Thank you,

It should be fixed now, otherwise you may try one of the solutions mentioned in #3669.

It should be fixed now, otherwise you may try one of the solutions mentioned in #3669.

@akyjoe the reference you have give there is no solution on it. I think its still under processing

I have followed all of the installation steps and still don't see any crashes showing up. I have tried everything I can think of including the suggestions above, clean & rebuild, etc. and still nothing. Any other suggestions on how we can go about debugging what is wrong? Is there some kind of additional logging that can be turned on to see what is happening?

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

I have followed all of the installation steps and still don't see any crashes showing up. I have tried everything I can think of including the suggestions above, clean & rebuild, etc. and still nothing. Any other suggestions on how we can go about debugging what is wrong? Is there some kind of additional logging that can be turned on to see what is happening?

Yes, when you initialise the Crashlytics code, it will through an exception as mentioned in #3669
@jk-hub Did you force crash the App and rerun it again?

Yes, when you initialise the Crashlytics code, it will through an exception as mentioned in #3669

Yeah, I have seen this in Android Logcat now. I posted more info on my findings above.

I have followed all of the installation steps and still don't see any crashes showing up. I have tried everything I can think of including the suggestions above, clean & rebuild, etc. and still nothing. Any other suggestions on how we can go about debugging what is wrong? Is there some kind of additional logging that can be turned on to see what is happening?

Yes, when you initialise the Crashlytics code, it will through an exception as mentioned in #3669
@jk-hub Did you force crash the App and rerun it again?

yes @akyjoe I have tired for crash sending log also tried to the send unsend reports but its have been on than 72hrs now but no report is generated or send to the firebase crashlytics dashboard

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

yes i'm using the latest version of firebase Sdk with the recommended firebase analytics and crashlytics code
also I have ensure Initialization before run(Myapp)
This is used in android level build gradle
classpath 'com.google.gms:google-services:4.3.3'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
This is used in android/app level build gradle
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
Hoping this issue will get resolved.
Thank you.

I'm facing a similar issue, both under iOS and Android: Crashlytics seems to be working (or at least, it's not erroring out), but test crashes generated via crash() don't show up in the console, though I'm getting some more detailed exceptions in Logcat when Crashlytics is attempting to check previous crashes:
E/FirebaseCrashlytics( 8810): HTTP request failed.
E/FirebaseCrashlytics( 8810): java.io.InterruptedIOException: timeout
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.timeoutExit(RealCall.java:107)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.execute(RealCall.java:96)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.network.HttpRequest.execute(com.google.firebase:firebase-crashlytics@@17.0.0:129)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.settings.network.AbstractAppSpiCall.invoke(com.google.firebase:firebase-crashlytics@@17.0.0:68)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.settings.network.UpdateAppSpiCall.invoke(com.google.firebase:firebase-crashlytics@@17.0.0:21)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.performUpdateApp(com.google.firebase:firebase-crashlytics@@17.0.0:217)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.performAutoConfigure(com.google.firebase:firebase-crashlytics@@17.0.0:198)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.access$000(com.google.firebase:firebase-crashlytics@@17.0.0:40)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding$1.then(com.google.firebase:firebase-crashlytics@@17.0.0:124)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding$1.then(com.google.firebase:firebase-crashlytics@@17.0.0:117)
E/FirebaseCrashlytics( 8810): 	at com.google.android.gms.tasks.zzp.run(Unknown Source:2)
E/FirebaseCrashlytics( 8810): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/FirebaseCrashlytics( 8810): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.common.ExecutorUtils$1$1.onRun(com.google.firebase:firebase-crashlytics@@17.0.0:60)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.common.BackgroundPriorityRunnable.run(com.google.firebase:firebase-crashlytics@@17.0.0:27)
E/FirebaseCrashlytics( 8810): 	at java.lang.Thread.run(Thread.java:919)
E/FirebaseCrashlytics( 8810): Caused by: java.io.IOException: Canceled
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:254)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.execute(RealCall.java:92)
E/FirebaseCrashlytics( 8810): 	... 14 more
E/FirebaseCrashlytics( 8810): Error performing auto configuration.
E/FirebaseCrashlytics( 8810): java.lang.RuntimeException: java.io.InterruptedIOException: timeout
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.settings.network.AbstractAppSpiCall.invoke(com.google.firebase:firebase-crashlytics@@17.0.0:80)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.settings.network.UpdateAppSpiCall.invoke(com.google.firebase:firebase-crashlytics@@17.0.0:21)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.performUpdateApp(com.google.firebase:firebase-crashlytics@@17.0.0:217)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.performAutoConfigure(com.google.firebase:firebase-crashlytics@@17.0.0:198)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding.access$000(com.google.firebase:firebase-crashlytics@@17.0.0:40)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding$1.then(com.google.firebase:firebase-crashlytics@@17.0.0:124)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.Onboarding$1.then(com.google.firebase:firebase-crashlytics@@17.0.0:117)
E/FirebaseCrashlytics( 8810): 	at com.google.android.gms.tasks.zzp.run(Unknown Source:2)
E/FirebaseCrashlytics( 8810): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/FirebaseCrashlytics( 8810): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.common.ExecutorUtils$1$1.onRun(com.google.firebase:firebase-crashlytics@@17.0.0:60)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.common.BackgroundPriorityRunnable.run(com.google.firebase:firebase-crashlytics@@17.0.0:27)
E/FirebaseCrashlytics( 8810): 	at java.lang.Thread.run(Thread.java:919)
E/FirebaseCrashlytics( 8810): Caused by: java.io.InterruptedIOException: timeout
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.timeoutExit(RealCall.java:107)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.execute(RealCall.java:96)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.network.HttpRequest.execute(com.google.firebase:firebase-crashlytics@@17.0.0:129)
E/FirebaseCrashlytics( 8810): 	at com.google.firebase.crashlytics.internal.settings.network.AbstractAppSpiCall.invoke(com.google.firebase:firebase-crashlytics@@17.0.0:68)
E/FirebaseCrashlytics( 8810): 	... 12 more
E/FirebaseCrashlytics( 8810): Caused by: java.io.IOException: Canceled
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
E/FirebaseCrashlytics( 8810): 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:254)
E/FirebaseCrashlytics( 8810): 	at okhttp3.RealCall.execute(RealCall.java:92)
E/FirebaseCrashlytics( 8810): 	... 14 more

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

yes i'm using the latest version of firebase Sdk with the recommended firebase analytics and crashlytics code
also I have ensure Initialization before run(Myapp)
This is used in android level build gradle
classpath 'com.google.gms:google-services:4.3.3'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
This is used in android/app level build gradle
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
Hoping this issue will get resolved.
Thank you.

Also try moving apply plugin: 'com.google.firebase.crashlytics' after the dependencies of android/app level gradle, just like in the bottom image.

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

yes i'm using the latest version of firebase Sdk with the recommended firebase analytics and crashlytics code
also I have ensure Initialization before run(Myapp)
This is used in android level build gradle
classpath 'com.google.gms:google-services:4.3.3'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
This is used in android/app level build gradle
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
Hoping this issue will get resolved.
Thank you.

Also try moving apply plugin: 'com.google.firebase.crashlytics' after the dependencies of android/app level gradle, just like in the bottom image.

@akyjoe  its like that only I have applied the plugin in the bottom after dependence

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

I tried adding implementation 'com.google.firebase:firebase-analytics:17.5.0' to my app level gradle and I still get the same exception: java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443. From the error, it looks like it is supposed to be substituting values into the url, but those values are missing. I am guessing this has something to do with what I mentioned about having google-services.json files per environment. Is this supported for the crashlytics package?

I am getting the same error yet I have one google-services.json file in root.

Doing a bit more debugging, the error mentioned in linked issue above (java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443) is happening before await Firebase.initializeApp(); is called. I am guessing this means that there is a problem at the underlying Android code of the firebase_crashlytics plugin.
Also, not sure if it matters, but I have multiple google-services.json files setup using the environment file paths -- i.e. android/app/src/debug/google-services.json & android/app/src/release/google-services.json. This works just fine with the other firebase packages I use (cloud_firestore, firebase_auth, firebase_analytics) so I wouldn't think that would be an issue with firebase_crashlytics, but thought I would mention it.

When I was installing Firebase Crashlytics two days ago, #3669 was the problem, but didn't have the Firebase Analytics in the App. So, I included that next day and dis the crash, reopen the app so crash report is generated onFlutterError and it worked.
Just check the SDK docs once again as it requires Firebase Analytics 17.5.0 in app level gradle as an implementation. This part isn't mentioned in the FlutterFire docs. So, just make sure that latest firebase gradle build is available to the App.
@jk-hub There's definitely some issue in Crashlytics for people using older version. Two quick questions:

Are you using latest Firebase SDK with recommended Firebase Analytics and Crashlytics code or migrating from the Fabric Version?
Did you initialise the Crashlytics code before run(MyApp)?

I tried adding implementation 'com.google.firebase:firebase-analytics:17.5.0' to my app level gradle and I still get the same exception: java.net.ConnectException: Failed to connect to firebase-settings.crashlytics.com/:::443. From the error, it looks like it is supposed to be substituting values into the url, but those values are missing. I am guessing this has something to do with what I mentioned about having google-services.json files per environment. Is this supported for the crashlytics package?

Actually google-services.json only prompts for the Analytics. Do you use Firebase Analytics in Flutter App?
If not then, I have a feeling that Firebase Crashlytics has some dependency with Firebase Analytics packages. So, may be try adding firebase_analytics package in the pubspec.yaml and do flutter pub get, flutter pub upgrade. Then rebuild the App and check for the above error, if it goes away, then force crash to enable Crashlytics in Firebase. There's a latency of crash being reported by 10 minutes in India and in stream view by 2 minutes. Hope this information helps.
If you do, then try to remove the local cache of all Firebase packages and do flutter pub get and flutter pub upgrade.

I share my project where I well enabled Firebase Crashlytics & Analytics with the last version of pub.dev.
https://github.com/EArminjon/flutter_base_project
I hope it will help you to  setup firebase :)

Same issue here with native and Flutter crashes both for iOS and Android. Here I'm testing the app with
FirebaseCrashlytics.instance.crash(); but this also doesn't work with FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterError;
I call final firebase = await Firebase.initializeApp(); at the beginning of the app execution and I see the analytics data of the app in the Firebase Console. However, the crash reports are not visible.
Logs from profile mode:
10:34:30.607171+0200	Runner	[Firebase/Crashlytics] Version 4.1.1
10:34:30.728046+0200	Runner	Read options: 0 -- URL: file:///var/mobile/Containers/Data/Application/3AFC66CD-9896-4A9D-B057-DE9FAC099344/Library/Application%20Support/Google/FIRApp/FIREBASE_DIAGNOSTICS_HEARTBEAT_DATE -- purposeID: BF422CBE-DCC6-4179-B8CA-89EAA7738E18 -- claimID: 65EA6307-D4B2-4075-BED2-27E079F683A5
10:34:30.728847+0200	Runner	6.26.0 - [Firebase/Core][I-COR000005] No app has been configured yet.
10:34:30.736944+0200	Runner	Read options: 0 -- URL: file:///var/mobile/Containers/Data/Application/3AFC66CD-9896-4A9D-B057-DE9FAC099344/Library/Application%20Support/Google/FIRApp/FIREBASE_DIAGNOSTICS_HEARTBEAT_DATE -- purposeID: BF422CBE-DCC6-4179-B8CA-89EAA7738E18 -- claimID: B053B817-B00E-40B9-B7F2-9E103AE14D7B
10:34:32.939203+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
10:34:32.940830+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
10:34:32.941406+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60600000 started
10:34:33.294441+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
10:34:47.481151+0200	Runner	*** Terminating app due to uncaught exception 'FirebaseCrashlyticsTestCrash', reason: 'This is a test crash caused by calling .crash() in Dart.'
*** First throw call stack:
(0x1807b4114 0x193fdacb4 0x10028a9f0 0x100ceedec 0x100735b3c 0x100a0fbc0 0x10073f0e4 0x100741810 0x180734a30 0x180734634 0x180733b14 0x18072deb0 0x18072d200 0x196828598 0x182ff3004 0x182ff85d8 0x100158e5c 0x18040c598)

now restarting the app:
10:34:51.393260+0200	Runner	[Firebase/Crashlytics] Version 4.1.1
10:34:59.447177+0200	Runner	6.26.0 - [Firebase/Core][I-COR000005] No app has been configured yet.
10:35:00.608338+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
10:35:00.608690+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
10:35:00.609252+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60600000 started
10:35:00.609747+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
10:35:01.211383+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
10:35:01.315371+0200	Runner	6.26.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled

doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, 1.22.0-12.3.pre, on Mac OS X 10.15.6 19G73, locale pl-PL)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (5 available)

dependencies:

- firebase_analytics 6.0.0 [meta flutter firebase_core firebase_analytics_web firebase_analytics_platform_interface]
- firebase_auth 0.18.0+1 [meta firebase_core firebase_core_platform_interface firebase_auth_platform_interface firebase_auth_web flutter]
- firebase_core 0.5.0 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.2.1 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]

Podfile.lock:
  - firebase_core (0.5.0):
    - Firebase/CoreOnly (~> 6.26.0)
    - Flutter
  - firebase_crashlytics (0.2.1):
    - Firebase/CoreOnly (~> 6.26.0)
    - Firebase/Crashlytics (~> 6.26.0)
    - firebase_core

" No app has been configured yet." Have you enable crashlytics on firebase ? Have you well insert google-service.json in android/app ?

Funny thing, between yesterday and now, I had zero chances to make any changes to the app, but the Java exception is now gone, and test crashes are showing fine on Android. Makes me wonder if it wasn't a Firebase internal transient issue.
The jury is still out on iOS, but I'm not sure that's working...

I think similar. In the morning I saw a lot of following messages in Crashlytics debugging log:
Send to Reports Endpoint disabled. Removing Reports Endpoint report
This was happening for apps like Revolut as well from what I see now

Funny thing, between yesterday and now, I had zero chances to make any changes to the app, but the Java exception is now gone, and test crashes are showing fine on Android. Makes me wonder if it wasn't a Firebase internal transient issue.
The jury is still out on iOS, but I'm not sure that's working...

New version on pub.dev is available, if your pubspec.yaml had ^0.2.0 since few hour your app will take automatically the version 0.2.1
Maybe it's that :)

your app will take automatically the version 0.2.1
Haven't even ran pub and my pubspec uses pinned versions wherever possible (I come from Maven-land, and I've had tons of bad experiences with defining version ranges in pub, only to be blindsided by a breaking change in a path version number change, in core modules no less!).

I'm leaning towards an internal problem right now...

I have figured out my issue. I run a network-wide ad blocker called Pi-hole. It must be blocking the ability for crashes to be reported. Maybe is has something to do with Crashlytics being tied to Analytics somehow? Once I turned off my Pi-hole to test is out, the Crashlytics dashboard reported that everything was installed correctly now. Note: I did not have to add any dependencies to my app\build.gradle. I was able to setup Crashlytics just like the docs say to once I disabled my Pi-hole.

I have figured out my issue. I run a network-wide ad blocker called Pi-hole. It must be blocking the ability for crashes to be reported. Maybe is has something to do with Crashlytics being tied to Analytics somehow? Once I turned off my Pi-hole to test is out, the Crashlytics dashboard reported that everything was installed correctly now. Note: I did not have to add any dependencies to my app\build.gradle. I was able to setup Crashlytics just like the docs say to once I disabled my Pi-hole.

How does pi-hole block the crash to get it reported to crashlytics I didn't understand this can anyone explain

I have figured out my issue. I run a network-wide ad blocker called Pi-hole. It must be blocking the ability for crashes to be reported. Maybe is has something to do with Crashlytics being tied to Analytics somehow? Once I turned off my Pi-hole to test is out, the Crashlytics dashboard reported that everything was installed correctly now. Note: I did not have to add any dependencies to my app\build.gradle. I was able to setup Crashlytics just like the docs say to once I disabled my Pi-hole.

How does pi-hole block the crash to get it reported to crashlytics I didn't understand this can anyone explain

I dug a little deeper on this and it seems like Pi-hole was only impacting some kind of initialization that Crashlytics does. I know Pi-hole blocks Google Analytics reporting, so maybe the Crashlytics plugin uses Google Analytics on initialization somehow (no idea here, just grasping at straws)? Once I re-enabled my Pi-hole, I am still seeing crash reporting coming in when I test. With that said, I am still confused on if we need the dependencies in app\build.gradle. I have tried removing them and then testing and then adding them back and then testing, but I am getting inconsistent results. Based on the Crashlytics docs we shouldn't need them, but with such inconsistency it is hard to tell for sure one way or the others.

Related https://github.com/FirebaseExtended/flutterfire/issues/3534

Just wanted to mention that I was still experiencing this issue in a new-to-me project even after upgrading to 0.2.1
Taking a closer look at the "settings" URL that it was connecting to, it looks like it was trying to use the debug/google-services.json while I was trying to set it up on the release/google-services.json.
After getting the google-services.json files straightened out and running a flutter clean, it began working for me

Hi, I also experienced the problem and don't see crashes in the console. I tested on iOS and noticed that in Podfile it's connected FirebaseCrashlytics (~> 4.1.1) and in the console is said to use minimum 4.3.0.
How can I update pods to use the 4.3.0?
In my pubspec.yml file I use the following versions
  firebase_auth: ^0.18.1
  firebase_core: ^0.5.0
  firebase_analytics: ^6.0.1
  firebase_messaging: ^7.0.1
  firebase_dynamic_links: ^0.6.0+1
  firebase_crashlytics: ^0.2.1
  cloud_functions: ^0.6.0+1
  firebase_remote_config: ^0.4.0+1

@Den-Ree  :  are you able to catch crash using this statement inside main.dart file for any flutter framework related crash.
FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterError;
I have setup everything but this statement is not recording any crash.  Can you please help me into this.

@mehtahardikr I use in my code this statement
final originalOnError = FlutterError.onError;
    FlutterError.onError = (FlutterErrorDetails errorDetails) async {
      await FirebaseCrashlytics.instance.recordFlutterError(errorDetails);
      // Forward to original handler.
      originalOnError(errorDetails);
    };

and that  require runzoneguarded method to wrap run(myapp()) to catch flutter framework related crash ?

I have figured out my issue. I run a network-wide ad blocker called Pi-hole. It must be blocking the ability for crashes to be reported. Maybe is has something to do with Crashlytics being tied to Analytics somehow? Once I turned off my Pi-hole to test is out, the Crashlytics dashboard reported that everything was installed correctly now. Note: I did not have to add any dependencies to my app\build.gradle. I was able to setup Crashlytics just like the docs say to once I disabled my Pi-hole.

How does pi-hole block the crash to get it reported to crashlytics I didn't understand this can anyone explain

I dug a little deeper on this and it seems like Pi-hole was only impacting some kind of initialization that Crashlytics does. I know Pi-hole blocks Google Analytics reporting, so maybe the Crashlytics plugin uses Google Analytics on initialization somehow (no idea here, just grasping at straws)? Once I re-enabled my Pi-hole, I am still seeing crash reporting coming in when I test. With that said, I am still confused on if we need the dependencies in app\build.gradle. I have tried removing them and then testing and then adding them back and then testing, but I am getting inconsistent results. Based on the Crashlytics docs we shouldn't need them, but with such inconsistency it is hard to tell for sure one way or the others.

this worked out for me after i stopped the pi-hole and did force crash it got reported to firebase crashlytics.

I too run Pi-hole and overcame this issue by adding "crashlytics.com" to the Whitelist.

It appears the OPs issue has been resolved. On top of that, there has since been 2 crashlytics major versions released and a significant overhaul of documentation setup here. Please file a new issue if you encounter another bug. Thanks.


Update raycast-explorer extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

LGTM, @abnershang can you add it to the Prompt Explorer repo too? The extension will soon fetch the prompts directly from there.

Added. https://github.com/raycast/prompt-explorer/pull/19


[RxJS 5.0.x] Add bufferCount and bufferTime methods

Added annotations and tests for Rx.Observable methods bufferCount and bufferTime.

Surprised I didn't notice another PR that's already in for this! Closing.


mgmt: mcumgr: explore why UART interface is so slow (possible go application fault)

Is your enhancement proposal related to a problem? Please describe.
With the rework from https://github.com/zephyrproject-rtos/zephyr/pull/53558 - the fs_mgmt transfer speed for bluetooth has jumped up to about 13KBps, whilst the UART (note: via shell interface) is stuck on about 3KBps... What makes even less sense is that the UART speed does not increase with larger MTUs or faster baud rates, indeed with an MTU of 4KB and baud rate of 460800, the transfer speed is... 3KBps.
My suspicious are high that it's the go tool that is the culprit of the issues, to see no difference between 115200 baud with 2048 byte MTU and 460800 baud with 4096 byte MTU just seems absurd, regardless of the processing speed of the various layers in zephyr.
Describe the solution you'd like
MCUmgr transfer speeds via UART to not be such in the 1980s.
Describe alternatives you've considered
There are no alternatives, at 3KBps the system is just woefully inadequate.

Thanks for this patch. With fd00ebc, MCUmgr file transfer over USB CDC ACM has gotten significantly faster when used with this patch and this fix.
Uploading 32KB decreased from from 10.249s to 2.120s. Downloading 32KB decreased from 2.110s to 0.696s

Tested with custom tool, 896KB uploaded in 63 seconds = 14.2KBps, at 460800 baud, 512 byte MTU, therefore concurring that the fault is with the go application at the 3KBps limitation, which has an appalling design. At this point the only logical thing to do is dump it entirely.
However the problem is not entirely with the go application, I'm maxing out at about 15.5KBps over UART with 1Mbps baud and 2048 byte MTU, which is about 6% utilisation of the available baud rate - absolutely terrible. Might need to see about larger shell MCUmgr frames e.g. 1KB instead of 128 byte sizes and see if that helps improve throughput.
CC @de-nordic

No point keeping this open as the issue is with the go application, which now has a note that it is not recommended to be used.
Maximum transfer speeds for fs_mgmt observed with custom UART tool were ~18KBps write speed and ~23KBps read speed (external QSPI memory in high-speed mode on nRF52840 with QSPI operating at 32MHz)


Heat pump clim8zone™

I have installed a Balboa heat pump clim8zone™. Is it possible to integrate it as well?
The following messages appear in the log
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c2  contents: 00,e7,00,4b,00,f0,ff,f6,00,fa,02,bc,ff,e7,15,12,03,1c,37,25,4a,0b
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:18 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:18 AM] [Spa] Not understood a received spa message (nothing critical, but please do report this):ff,af,c5  contents: 01,11,02,28,07,00,00,00,00,
https://www.balboawatergroup.com/Clim8zone

Hi - I expect it is possible to integrate that, but it will at the least
require someone with the heat-pump to interpret what those different new
messages mean. You might be able to do that by observing how the messages
change as you adjust the settings of the heat-pump through the balboa
control panel.
Vince.
On Sat, 17 Sept 2022 at 10:52, nuiler @.***> wrote:

I have installed a Balboa heat pump clim8zone™. Is it possible to
integrate it as well?
The following messages appear in the log
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c2 contents:
00,e7,00,4b,00,f0,ff,f6,00,fa,02,bc,ff,e7,15,12,03,1c,37,25,4a,0b
[9/17/2022, 11:48:16 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:17 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:18 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,00,01,02,03
[9/17/2022, 11:48:18 AM] [Spa] Not understood a received spa message
(nothing critical, but please do report this):ff,af,c5 contents:
01,11,02,28,07,00,00,00,00,
https://www.balboawatergroup.com/Clim8zone http://url
—
Reply to this email directly, view it on GitHub
https://github.com/vincedarley/homebridge-plugin-bwaspa/issues/23, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGGHRYU32OLNYH445OAI2V3V6WIHFANCNFSM6AAAAAAQO6A4FM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Attached are a few pictures of the display and status messages, I hope this helps.
Whirlpool.txt

Does the data help or do they need more?

Do you still need data from me?
Can I support you and will the project continue?

Hi - this will really require someone who has such a heat pump to dive in to the code and start experimenting. The data you've given is useful.

I have such a heat pump installed in my pool and would very much like to be a tester.


npm run ingest error

Hello, there
i was wonderding why do i get this error ? i did everyhing right and set up new index on pincone. Can you help please?
btw: i have pdf file inside docs file
PS D:\Chatbot AI\gpt4-pdf-chatbot-langchain> npm run ingest

<EMAIL_ADDRESS>ingest
tsx -r dotenv/config scripts/ingest-data.ts

error [Error: ENOTDIR: not a directory, scandir 'D:\Chatbot AI\gpt4-pdf-chatbot-langchain\docs\tesla.pdf'] {
errno: -4052,
code: 'ENOTDIR',
syscall: 'scandir',
path: 'D:\Chatbot AI\gpt4-pdf-chatbot-langchain\docs\tesla.pdf'
}
d:\Chatbot AI\gpt4-pdf-chatbot-langchain\scripts\ingest-data.ts:46
throw new Error('Failed to ingest your data');
^
Error: Failed to ingest your data
at run (d:\Chatbot AI\gpt4-pdf-chatbot-langchain\scripts\ingest-data.ts:46:11)
at  (d:\Chatbot AI\gpt4-pdf-chatbot-langchain\scripts\ingest-data.ts:51:3)
Node.js v18.16.0

I think it may be that your file path is wrong. The file path should be the folder where the pdf file is stored instead of the file itself. Hope this helps


Installation issue for system cuda version 10.0 with wheels and source

📚 Installation
Hello,
I have been using torch_geometric with torch 1.4cu100 and wanted to use the torch_geo with torch 1.5  onwards.
First I installed the torch_geometric using the provided wheels for cu102 and torch 1.6.0.
This threw the error:
OSError: libcusparse.so.10: cannot open shared object file: No such file or directory

LD_LIBRARY_PATH is fine.
/usr/local/cuda/lib64/ has the libcusparse.so.10.0 and libcusparse.so
To overcome this I did to install by sources, this time in a venv for torch 1.5.1 with cu101
Then I got the following error:
Detected that pytorch and torch_{scatter, sprase, cluster ...} were compiled with different CUDA version. Pytorch has cuda version 10.1 and torch_{scatter, sparse, cluster ...} has cuda version 10.0

Environment

OS: Linux x86_64
Python version: 3.6.9
PyTorch version: Tried with 1.6.0 (installed the wheels) and 1.5.1(installed with sources)
CUDA/cuDNN version: 10.0
GCC version: 7.5.0
How did you try to install PyTorch Geometric and its extensions (wheel, source): Tried both
Any other relevant information:

Checklist

[ Yes ] I followed the installation guide.
[Yes ] I cannot find my error message in the FAQ.
[Nope ] I set up CUDA correctly and can compile CUDA code via nvcc. (Actually it is a remote cluster so only sysadmins have the authority to setup cuda )
[Nope ] I do have multiple CUDA versions on my machine.

Additional context
So right now I found a workaround and I am able to make my old cold (with torch 1.4.0+cu100) run in the  new env (torch1.5.1cu101 with torch_geo installed from sources) by  editing**:
if t_major != major or t_minor != minor:

to
if t_major!=major

In the init.py of all the torch_{scatter, sparse, cluster ....}
So that it doesn't check for the minor mismatch. Actually the old code is working so far, but I wonder what are the possible issues I will encounter in future? Is there a better way? Do I need to ask the sysadmins to ugrade the cuda version to atleast 10.1 to avoid this issue ?

I face the same problems on PaperSpace and GoogleCloud engine.
'libtorch_cpu.so: cannot open shared object file: No such file or directory'

Hey buddy, I am not sure if that could be considered same as this issue.
libtorch_cpu.so means you installed cpu version of pytorch.
But isn't libtorch_cpu.so available inside the python/site-packages/torch/lib/ ?

The workaround is okay as long as the results are as expected. You can also get around the problem by pointing your CUDA paths to the cudatoolkit==10.1 installed via miniconda.

Ahh, thanks I will bear this in mind.

@aGIToz yes you were right, the system couldn't recognise the correct Torch version. fixed.

@joc32 Hi, how you solve the 'libtorch_cpu.so' issue? Could you share with me in detail? Face the same problem :(

same here, there is same issue on CUDA version 10.0.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/urbanaccess-feedstock#5.


added descri. for ONE_CLICK_INSTALL_AND_RUN.sh

What was wrong in my script? It works very well brother. why you rejected the PR?

if you would like it can be pushed to a new branch

If possible please push it to not-Vercel-Server branch.


fix(es/codegen): Remove extra space of import decl

See: #1690

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.nuintun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Why did you close this?

@kdy1 Because you updated, I'll re PR later~

@kdy1 #1975


fix(askscript): fix tricky array expression

Closes #382

I like the example program :).
Pending discussion on https://github.com/xFAANG/askql/issues/382

@czerwinskilukasz1 can you explain how this is solved and what are the consequences of this change to the parser?


Splitdomains

We should find a way to allow 'split-domains', that is: some mails go to the local mailstore and some are rerouted to a relaydomain. Activating a 'splitdomain' should be an upgrade path from e.g. a local domain that doesn't require someone to delete or modify the existing domain.
Maybe running a local- and a relaydomain in parallel already does what we want. Check and see if this needs better visibility (tag) etc.

This issue was moved to modoboa/modoboa-admin-relaydomains#3


Fix template tests to run under any RDF_PIPELINE_DEV_DIR path.

Fix template tests to run under any RDF_PIPELINE_DEV_DIR path.
Also
1. fixed test 0037 to handle tmp dir correctly
2. added 1 sec delay so 0049 passes consistently
3. apply David's ordering changes
4. Clear system between tests

LGTM


Variable names has been modified.

New data types are defined.
cluster-new has been rewritten in typescript.

Route config and app.ts changes missing. Also test if cluster creation is working fine


support webview_flutter 4.0.x

project using webview_flutter 4.x can't use model_viewer_plus because version conflict.
please support webview_flutter 4.x

agree can't use  this plugin anymore

done


通过 DSN 设置 readTimeout 无法生效

Your Question
出发点是想设置全局的查询超时时间
看了 https://github.com/go-sql-driver/mysql#readtimeout 这里的介绍，我在 DSN 中参入了 &readTimeout=1ms&writeTimeout=6ms 来测试验证超时，但是经验证并没有生效。

The document you expected this should be explained

超过了 1ms 的查询，并没有出现查询超时异常
Expected answer

看了 gorm 的 mysql driver 依赖的是 github.com/go-sql-driver/mysql ，理论上应该是能生效才对，请问是不是有 bug？
或者说，gorm 有没有其他的方式来设置全局的查询超时时间？

The time of the log print is not the time of the actual query.
Each data queried by mysql will be returned immediately, all records are completed by waiting on the client side.

you can use DB.Raw("select sleep(1)") to test it.

DB.Raw("select sleep(1)")

I tried this and readTimeout didn't work.

DB.Raw("select sleep(1)")

I tried this and readTimeout didn't work.

DB.Raw("select sleep(1)").Scan(nil)

How to resolve it finally?


[tracking] Disable functional tests on CI

https://github.com/RedHatInsights/insights-results-aggregator-mock/issues/97

Not really needed as we already have simple functional tests prepared.


Add support for eth/66

PR description
Adds support for eth/66
Fixed Issue(s)
Fixes #223

LGTM. in some java files i wish it  was possible to use == in replace of equals like kotlin


test: Add tests and refactor/document structs

Closes #446

Apologies for the delay, was feeling a bit under the weather but should be rebased with all comments addressed now

@igamigo - since this is merged, we should be able to close a couple of related issues, right?


Operator projects using the removed APIs in k8s 1.22 requires changes.

Problem Description
Kubernetes has been deprecating API(s), which will be removed and are no longer available in 1.22. Operators projects using these APIs versions will not work on Kubernetes 1.22 or any cluster vendor using this Kubernetes version(1.22), such as OpenShift 4.9+. Following the APIs that are most likely your projects to be affected by:

apiextensions.k8s.io/v1beta1: (Used for CRDs and available since v1.16)
rbac.authorization.k8s.io/v1beta1: (Used for RBAC/rules and available since v1.8)
admissionregistration.k8s.io/v1beta1 (Used for Webhooks and available since v1.16)

Therefore, looks like this project distributes solutions in the repository and does not contain any version compatible with k8s 1.22/OCP 4.9. (More info). Following some findings by checking the distributions published:

prometheus-exporter-operator.v0.2.0: this distribution is using APIs which were deprecated and removed in v1.22. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22. Migrate the API(s) for CRD: (["prometheusexporters.monitoring.3scale.net"])
prometheus-exporter-operator.v0.2.4: this distribution is using APIs which were deprecated and removed in v1.22. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22. Migrate the API(s) for CRD: (["prometheusexporters.monitoring.3scale.net"])

NOTE: The above findings are only about the manifests shipped inside of the distribution. It is not checking the codebase.
How to solve
It would be very nice to see new distributions of this project that are no longer using these APIs and so they can work on Kubernetes 1.22 and newer and published in the community-operators collection. OpenShift 4.9, for example, will not ship operators anymore that do still use v1beta1 extension APIs.
Due to the number of options available to build Operators, it is hard to provide direct guidance on updating your operator to support Kubernetes 1.22. Recent versions of the OperatorSDK greater than 1.0.0 and Kubebuilder greater than 3.0.0 scaffold your project with the latest versions of these APIs (all that is generated by tools only). See the guides to upgrade your projects with OperatorSDK Golang, Ansible, Helm or the Kubebuilder one. For APIs other than the ones mentioned above, you will have to check your code for usage of removed API versions and upgrade to newer APIs. The details of this depend on your codebase.
If this projects only need to migrate the API for CRDs and it was built with OperatorSDK versions lower than 1.0.0 then, you maybe able to solve it with an OperatorSDK version >= v0.18.x < 1.0.0:

$ operator-sdk generate crds --crd-version=v1
INFO[0000] Running CRD generator.
INFO[0000] CRD generation complete.

Alternatively, you can try to upgrade your manifests with controller-gen (version >= v0.4.1) :
If this project does not use Webhooks:

$ controller-gen crd:trivialVersions=true,preserveUnknownFields=false rbac:roleName=manager-role  paths="./..."

If this project is using Webhooks:

Add the markers sideEffects and admissionReviewVersions to your webhook (Example with sideEffects=None and admissionReviewVersions={v1,v1beta1}: memcached-operator/api/v1alpha1/memcached_webhook.go):

Run the command:

$ controller-gen crd:trivialVersions=true,preserveUnknownFields=false rbac:roleName=manager-role webhook paths="./..."

For further information and tips see the comment.

/kind bug

/kind feature

Thanks for the Issue @camilamacedo86, we will look into it!
/priority important-soon
/label size/l

/assign

Is it possible to submit on a single PR with both changes?

Yes, it is. Feel free to ping me if you need help there to check your PR merged.


Always initalize output processor on construction.

This requires re-use in the (soon to be obsolete) SDFProcessElementInvoker,
but that's preferable to having it be an optional argument elsewhere just
to handle this rare case.
R: @chadrik Simplifies code at https://github.com/apache/beam/pull/10367 Happy to rebase this if that goes in quickly .

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

This looks like a great improvement from my perspective.


Executing child process with spaces leads to error

Whenever i try to run a game with spaces in the filename, install as well as executable, i receive an error that the file was not found:

(Translation: Executing of child process has failed: Execution of child process /mnt/Spiele/eXoDOS/eXo/eXoDOS/!dos/TheLostV/Lost has failed: File not found)
Im trying to play The Lost Vikings as an example here.
The original executable is called "Lost Vikings, The (1993).sh". If i rename it to just "Lost", it runs fine.

FyI: Version 0.9.6, which was linked in the eXoDOS docs, had this problem. Version 0.9.10 does not.


TypeError: Cannot read property 'split' of undefined

var splited = url.split('/');
^
TypeError: Cannot read property 'split' of undefined

你在这行之前插入console.log(socket.request.headers);

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook


support added for dynamic key mapping to child

Add support for dynamic key mapping to child attributes.
closes #13

@HassanAkbar can you update the README to reflect how to use the new features? Thanks.

@ronaldtse Sure, I'll update the readme and open a separate PR for that.


com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/auth/api/signin/internal/zzf;

Step 1: Describe your environment

Android device: Nexus 4 Emulator
Android OS version: 5.1
Google Play Services version: 10.0.84
Firebase/Play Services SDK version: 10.0.0
FirebaseUI version: 1.0.0

Step 3: Describe the problem:
gradle build errors out with exception com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/auth/api/signin/internal/zzf;
Steps to reproduce:

Create project with dependency as follows:

  compile rootProject.ext.libraries.firebaseCore
  compile rootProject.ext.libraries.firebaseCrash
  compile rootProject.ext.libraries.firebaseInvites
  compile rootProject.ext.libraries.firebaseMessaging
  compile rootProject.ext.libraries.firebaseAuthUI

Build project

Observed Results:
com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/auth/api/signin/internal/zzf;
I suspect that this is due to having firebase version mismatch between my project and firebaseui. (9.8 vs 10.0). Does it mean I'm not able to use firebase 10.0 until firebase-ui is updated to firebase 10.0?

Yes you are correct, however, there is an easy way to get around this by overriding the gradle dependencies. I highly recommend going through all the dependencies of your libraries (the deps of your deps) and overriding them to ensure you always have the latest version whether the library updates them or not. Here is a snippet of my gradle file that compiles and runs with play services v10:
// Firebase UI
compile 'com.firebaseui:firebase-ui-auth:1.0.0'
compile 'com.firebaseui:firebase-ui-database:1.0.0'
compile "com.google.firebase:firebase-auth:$playServicesVersion"
compile "com.google.android.gms:play-services-auth:$playServicesVersion"
compile "com.google.firebase:firebase-database:$playServicesVersion"
compile 'com.facebook.android:facebook-android-sdk:4.17.0'
compile("com.twitter.sdk.android:twitter:2.1.1@aar") { transitive = true }

You have to add firebase storage if you are using the full firebase-ui lib.

@GaborPeto just to clarify a little, we are always "chasing" the latest version of the Firebase libraries.  Because we want to develop FirebaseUI completely in the open (with the help of contributors like @SUPERCILEX) that means we generally lag by a few days.  My goal is to get out a version of FirebaseUI that depends on Firebase/Play Services 10.0.0 ASAP.

@samtstern awesome!

Version 1.0.1 released which depends on Firebase 10.0.0, so this should be fixed.


Add "TTS enabled"/"TTS disabled" messages

@kevmo314 this should be completed with this merge here correct?
https://github.com/muxable/rtchat/pull/1195


No need to escape question marks in Postgresql

I could find no reason for the original code, only problems caused by it.
Fixes #1764
Fixes #1507

I could find no reason for the original code, only problems caused by it.

I want to hear this phrase in a song by Radiohead.


Add defensive coding to support experimental object spread properties

In a file like this with experimental object spread properties syntax:
function lol(a, b, c) {
  return {...a, b, c};
}

The following rules were throwing an error because node.property is undefined in a property node of type ExperimentalSpreadProperty.
Not sure if this is the right approach, but at least it allows me to run eslint!

Thanks for the fix!


Fixed building using xbuild on linux (fix vscode osu building)

In vscode there is a task to build the project but it doesn't work (on linux) unless you have compiled it once in MonoDevelop before or ran nuget restore. This change automatically runs nuget restore before building. Source (slightly modified becuase it didn't work just like that and removed nuget downloading): http://www.cazzulino.com/ultimate-cross-platform-nuget-restore.html
Basically all it does is running nuget Restore $(SolutionPath) before building

hm not really sure how to fix it on AppVeyor but I think it still works on windows without problems

Wanna hear something curious?
It doesn't

:-1: this isn't the correct way to go about this
Restore manually upfront, don't make xbuild do it.

if anything it shouldbe added to the vscode build script, not the csproj that is shared across other platforms.


[DBInstance] Needs namespace "crossplane-system" to store values in cache (version 0.42)

What happened?
After the upgrade for version 0.42 I am not able to create new RDS due to error:
    "Message: create failed: pre-create failed: cannot cache password: cannot create object: namespaces "crossplane-system" not found"

This is probably due to the refactor of the password cache ( https://github.com/crossplane-contrib/provider-aws/pull/1756 ) cc. @schroeder-paul / @MisterMX . It seems the Cache namespace is not fetching the namespace from "masterUserPasswordSecretRef", so the fix seems to be something simple.
I am using:
    masterUserPasswordSecretRef:
      key: password
      name: example-dbinstance
      namespace: default

So, I guess Crossplane should use that namespace for caching.
How can we reproduce it?
Here is the manifest applied
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
metadata:
  name: example-dbinstance
spec:
  forProvider:
    region: eu-central-1
    allocatedStorage: 20
    dbName: example
    engine: postgres
    engineVersion: "12.9"
    dbInstanceClass: db.t3.micro
    masterUsername: adminuser
    masterUserPasswordSecretRef:
      key: password
      name: example-dbinstance
      namespace: default
  writeConnectionSecretToRef:
    name: example-dbinstance-out
    namespace: default
  providerConfigRef:
    name: example

---
apiVersion: v1
kind: Secret
metadata:
  name: example-dbinstance
  namespace: default
type: Opaque
data:
  password: dGVzdFBhc3N3b3JkITEyMw== # testPassword!123

What environment did it happen in?
Crossplane version: 0.42
Thanks for the help! :)

@WolfGanGeRTech the masterUserPasswordSecretRef is optional and must not be provided when using the manageMasterUserPassword option.
So I guess the namespace for the password caching must be provided in another way.
I've worked around your problem by creating the artificial namespace crossplane-system in the target cluster as my Crossplane is installed in the crossplane ns.
Anyways it's a bug.

While it may seem trivial, this issue is not so easy to resolve as it may seem at first glance. Some heads-up thought:
masterUserPasswordSecretRef is indeed an optional field. The last used password is stored in a cache secret. It is not something that should be specified for MR individually since it is only provider internal. #1756 was written with the assumption that providers are always running in the crossplane-system namespace, so it got hardcoded.
However, it is not so easy to dynamically resolve the namespace to be used since controller-runtime's Client provides no direct way to get the default namespace from a config.
To solve this issue we need to lookup the target namespace manually. There are a bunch of possible locations to fetch it from:

POD_NAMESPACE env var
local kubeconfig context
--namespace CLI arg (we already have that one but it is used in a different way)

After we retrieved the namespace, we need to set it at the cache secret in the controller. It can be done directly via secret.SetNamespace or making it more abstract by using a client.NewNamespacedClient wrapper.

probably /var/run/secrets/kubernetes.io/serviceaccount/namespace  file is an option as well?


feat(logger): Create @tsed/logger-file package

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 7 (100.0%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 92.336%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
409

Relevant Lines:
426

💛  - Coveralls

:tada: This PR is included in version 6.0.0 :tada:
The release is available on:

v6.0.0
GitHub release

Your semantic-release bot :package::rocket:


Insert new random brick?

This is just an idea, would like to generate a new brick picked randomly from all available ones (and possibly if the brick requires setup parameters they could be default or random as well).

This is an interesting idea. However, this won't make it into the cryptii project. There might be a use case for ciphereditor. See #129 for more.


Add earcut entry point

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13902/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13902/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13902/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13902/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13902/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13902/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13902/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13902/merge#BCU1XR#0


Write a makefile

Writing a makefile will make it easy to automate builds, and to test things out.

Done.


Fix warning "declaration is not a prototype"

The warning is due to some of the function declarations in C and ObjC uses
return_type func()

instead of
return_type func(void)

The two definitions are the same in C++ but not the same in C and Objective-C. Using the former generates an warning.
This PR resolves this problem by adding "void" to all function declarations like this.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

@adelez kokoro:force-run seems not working on this PR..

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Test failures:
Asan C++ - #13122
Basic Tests C++ Linux [opt] -  #13115 #13270
Basic Tests MacOS [opt] - #10539
Tsan C++ - #13478
Msan C - #13124


Add custom RHEL 8 dependency packages

Some package names have different names for RHEL 8 compared to RHEL/CentOS 9 (e.g. libguestfs-tools instead of guestfs-tools)
As a pull request owner and reviewers, I checked that:

[ x] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] README in the role
[ ] Content of the docs/source is reflecting the changes

We won't support el8 (nor cs8) as hypervisor. This was discussed directly with @rdiazcam


Add PHP 8.1 Support

This PR adds PHP 8.1 support to the run tests workflow, along with Laravel 8.x support.  It also bumps the dependency versions to their latest in composer.json and adds the update changelog workflow.
This repository needs its primary branch renamed from master to main.

Thanks!


WIP: Restart server in Client.completions

Fixes https://github.com/zchee/deoplete-jedi/issues/56.

@blueyed Thanks for some pull request.
At once, I summarized in this comment to all reply.
Sorry, now I have no sufficient time to do develop the deoplete-jedi, but will be back to develop. about 1 week...?(I think)
Therefore, I can't your pull request code review because restart, threading is naive(not means rough) implements a little. I must understand the effects on the other code.
Now tweekmonster(not mentioned) also busy.
So, could you wait code review until then?
===
FYI, tweekmonster(and I) were consider re-write the threading server implements.
It's really non-blocking and deferred(promise) design pattern like nodejs. It might be solved some problem.
We will be developed in parallel with the bug fixes.

@zchee
I see.
I recommend just giving https://github.com/zchee/deoplete-jedi/pull/63 a test drive then (for the Python code you edit during the next week).
It is really obvious that it helps from looking at the system calls (strace).
And while I have changed the reaper thread only just now, the other changes seem to be good (with much less CPU usage).
As for this PR, I've just tried to fix this issue I've started looking at yesterday.

I haven't caught up completely yet, but other than the line comment I don't see anything wrong with this PR.  It just needs to be updated.

by now i am using the fork from @blueyed (and works), but will be this pul request a real solution or another steps are needed?

Good question.
@tweekmonster
Should I (try to) rebase it?

@blueyed My only reservation was the one line mentioned above.  But, I don't think it should block this PR.  I'm happy with it if you are.

I should clarify: I'll merge it if you think it's done.

this merge will be ready to correct the problem or we wait until the refactor/rewrite is done to see if the problem remains ?
in any case, can we put this pull in another branch here that get updated from master?

@ysolis

in any case, can we put this pull in another branch here that get updated from master?

What do you mean?  Should I rebase it on master?
I am not convinced about this PR myself - it was a very quick patch, without having looked much at the code before.  But I believe @tweekmonster, and therefore will look at it later and rebase / clean it up / whatever.

Ok, it should be fine from my side.
Regarding https://github.com/zchee/deoplete-jedi/pull/65#discussion_r80388107 I think it's good to be loud for now in that case.

@tweekmonster
:sheep: :it: ?

🐑 🇮🇹 ?

LMAO!  Yes, sorry!


[flutter_tools] ensure x64 is built if target-platforms is not specified

Description
In the add-2-app case, users may not specify the android target platforms field, but this only defaults to arm builds. Add x64 to the default list.
Fixes https://github.com/flutter/flutter/issues/62095

LGTM. This can be checked in https://github.com/flutter/flutter/blob/9b35933b2b3b46bcccac0dc3313bc72f9e1d137d/dev/devicelab/bin/tasks/gradle_plugin_fat_apk_test.dart#L41-L57

Awesome, thanks for the pointer!


Self-healing nodepools - Extremely large values cause deleteNotReadyAfterSecs to overflow

rancher/rancher:master-head a4944746
Extremely large numbers can be passed to deleteNotReadyAfterSecs field on a nodepool, causing the value to overflow. The ranges should be limited or the values truncated.
Actual:

Create a cluster with a dedicated worker nodepool
Edit deleteNotReadyAfterSecs on nodepool to have an extremely large negative or positive number:

100000000000000000000
-19223372036854776000

deleteNotReadyAfterSecs overflows and the value is set to:

deleteNotReadyAfterSecs": -9223372036854776000

Expected:

Values below 0 truncated to 0 or the request denied
Values above a reasonable limit truncated or the request denied

Solved via:

values less than zero throw an error
values greater than maxInt64 throw an error (> 9,223,372,036,854,775,807)

rancher/rancher:master 17ecf7bf

Created cluster
Edited nodepool deleteNotReadyAfterSecs to a negative value
API presented an error for MinLimitExceeded
Edited nodepool deleteNotReadyAfterSecs to a value greater than maxInt64
API presented an error for MinLimitExceeded
Edited nodepool deleteNotReadyAfterSecs to a range of realistic values (minutes to days)
API requests succeeded
Edited nodepool deleteNotReadyAfterSecs to a few minutes, stopped a node, and saw a new node provisioned


[Operational Tooling] Add smoke tests for operational tool commands.

Motivation
Note: this PR is based on PR: https://github.com/libra/libra/pull/6386. As such, to review the PR, ignore the first 3 commits.
This PR adds missing smoke tests for the various commands offered by the operational tool. This should help to ensure that the operational tool is not silently broken or seeing regressions. The PR offers 7 commits, each of which adds a smoke test (or two) for the different commands being tested by the commit:

print-account
account-resource
extract-public-key
extract-private-key
validate-transaction
set-validator-config and validator-config
validator-set

Note, there's still a few remaining commands that are not yet tested. These will be tested in a follow up PR (to be submitted shortly!)
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
All tests pass locally.
Related PRs
This PR is based on PR: https://github.com/libra/libra/pull/6386. As such, PR https://github.com/libra/libra/pull/6386 needs to land first.

/land


BVAL-497 Take into account @Repeatable annotations in the spec

https://hibernate.atlassian.net/browse/BVAL-497

I've sent PR #111 based on this, thus closing this one. The wording in the spec is a bit different, I also pushed out the example into separate source files. @gsmet if it's good from your PoV, I'll refer the EG to the imminent change.


Does this plugin support Windows 10 Universal Apps?

I'm new to Cordova and have been working hard to come up to speed. I recently completed this tutorial from the Microsoft site (Azure Android Push Notifications) successfully, but I've been unable to figure out how to modify this for a Windows 10 Universal App.
The Microsoft site indicated that the plugin does not support this yet, but I see questions posted by other users that indicate that it may possible.
If the plugin does support this, can someone give me an outline of the steps involved? Any help would be appreciated.

The plugin does work with Windows 10 Universal apps. The thing I was missing was the windows store association. Thanks for bringing this plugin to market!


Auto battle not working on Nox

Hello all, Thanks for all the efforts put into this, It's really going to make my nerofest experience much less painful than last year if the next engine update doesn't affect this. Moving on, I have installed the script and auto FP rolling works, Auto battle on the other hand does not. Whenever I try to run the script it gives me an empty 'caution' message from nox followed by a pop up of my settings and nothing else happens. I am not really sure what's wrong here, Any help would be appreciated. I am on NA by the way.
Screenshots:

After that nothing happens at all.
EDIT: As of now, Only autosupport and autorepeat don't work, If you can point me towards what I am doing wrong with the script, It'd be appreciated. I even turned the support selection process to 'any' and still nothing. Here's the file
https://dl.dropbox.com/s/pz2kugnh75w6hkk/FGO_EN_REGULAR.lua

I am embarrassed to admit this but I also got the problem on using NOX when running the script. Doing the battle itself does not result in problem, but when I the script trying to choose support servant, it stop there. I already set the AutoSupportSelection to "first" so the picking process should have pick the first servant instead of staying still. Would like some tips on fixing this issue.

Have you made any adjustments on the FGO_NA_REGULAR.lua file? This is needed to use some of the more advanced features the script provides and might explain a reason why this isn't working as it should.

I was testing if it'd work straight out of the box first and then I was planning to make the adjustment one by one to see if they'd break anything. I looked at the FGO_NA_REGULAR.lua file and I saw nothing that needed to be adjusted to pick waver with lunchtime as support for training grounds as a first try. I even thought it'd be okay if i could just get it to work in the battle itself then figure out how to get the auto support working, But no dice. I even tried installing a 7.1 version of nox and re-installing the game with a fresh account to try it on but still the same issue. Right now, I am suspecting the daemon process since I have installed the boot daemon upon launch, It might be affecting things but last time i tried to do the daemon manually, It didn't work so well. Can the boot daemon cause such an issue?

Yup, Seems like installing Daemon manually worked. Gonna have to do it everytime nox launches and the issue would be solved. I will keep this thread open if you guys don't mind until I edit everything in the FGO_NA_REGULAR.lua file and see if they work just so I don't clutter the issues tab with posts.

Okay, I have ran a script for the 40AP berserker training ground and most features seem to be working, A few polishing tweaks here and there now that I understand how its logic process works but two things seem to be not working as of now, Support selection and auto repeat. I will check the file again and update this thread.

Support selection and auto repeat?
The IsContinuing should be set as 0 for NA so make sure that is the case. As for Support Selection, make sure you have it set as "Preferred" and not "Manual" or "First"

Also, do you have a notch in your device? Examples of devices that have a Notch include S10 and Oneplus 6T. This has caused issues that I've had to solve manually for friends and people who have DMd me on Discord.

Okay, So for Auto repeat, IsContinuing is set to 0 in the regular.lua file but for some reason, The emulator seems to run slower when the script is running. So there's actually a 7 seconds-ish interval between when a quest is finished and when the bot should be trying to initiate a second quest. And it seems like the code has that interval at 2.5 seconds. At least that's how I am understanding it, I might be wrong. But everytime i try to modify the regular.lua file while having a backup, I get this error.

As for support, I honestly have no idea, I have set it to multiple settings, This is the last one, And still nothing.
--AutoSupportSelection Support_SelectionMode = "preferred" Support_SwipesPerUpdate = 10 Support_MaxUpdates = 6 Support_FallbackTo = "first" Support_FriendsOnly = 0 Support_PreferredServants = "waver4.png" Support_PreferredCEs = "*chaldea_lunchtime.png"
I suspect it might also be something that relates to longer interval times when running the script since loading the support screen takes less time when i am playing manually.

As for the notches, I am using Nox, But my model number is HUAWEI MLA-L12, Not sure if it'd matter though.

Changed the API to DirectX and the game seem to be working at normal speed with the script running but still no support selection or auto repeat.

Syntax error: unexpected symbol near '燎:
https://github.com/29988122/Fate-Grand-Order_Lua/blob/master/README.md#syntax-error-unexpected-symbol-near-燎
Em qua, 21 de ago de 2019 às 13:58, Nemesis6Ghoul<EMAIL_ADDRESS>escreveu:

Changed the API to DirectX and the game seem to be working at normal speed
with the script running but still no support selection or auto repeat.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/29988122/Fate-Grand-Order_Lua/issues/211?email_source=notifications&email_token=ABA5ZJSSC4YZ2LH6TPUVSITQFVX4XA5CNFSM4IMEJF6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42MECQ#issuecomment-523551242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABA5ZJVIR4Q7XGHFPEPUPT3QFVX4XANCNFSM4IMEJF6A
.

Oh I see! I had completely forgot about this in the readme. Thank you @potchy! Anyways, give that a change and try again. Let me know if anything else doesn't work as intended

Oh and once I finish with some new features I'm planning to implement a debug feature for specific scenario testing. Should help with some problem solving.

Everything seems to be working today for some reason. xD Running and repeating X-F reliably. I haven't tried auto refill yet because I am waiting on nerofest for that but thanks, Everything seems to be in order for now.

That's interesting. Post another issue if any other issues pop up.

Well, I think it may have been something related to the resolution or the DPI, I edited the file again to create a script for my bond farming and then auto repeat worked but support selection didn't. I tried to modify the DPI a bit but it still didn't work, I changed the resolution from the resolution of my monitor to 1920x1080 and now it worked, Made some custom pictures, Added them to the support selection and now everything running fine. Thanks for accommodating my problems, I just thought it's something you guys should keep in mind in case anyone runs into this problem again. My own screen resolution is 1366x768, So there might be something to look at there.

I think it has to do with how the scaling works. If the end product is even 1 pixel off, I think it'll cause tons of issues. Glad it worked out for you though.


Update dilithium submodule to latest changes

High Level Overview of Change
This change integrates the Dilithium library as a submodule within the external folder. It enhances the modularity of the API to support different types of Dilithium. The CMake configuration has been updated to utilize Dilithium alongside existing cryptographic libraries, and Dilithium2 has been added as a library in the conanfile.
Context of Change
The integration of Dilithium aims to improve the cryptographic capabilities of the project by providing modular support for various types of Dilithium. This change ensures that the project can leverage Dilithium in conjunction with other cryptographic libraries like secp256k1 and ed25519-donna.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[ ] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact

[x] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)

Looks good so far I would make the PR into your own develop branch  though or make this a draft as its not ready yet.

@dangell7 Yes youre right. It was by accident yesterday. I have created a fork of develop and created an upstream branch to push my changes.

@dangell7 Yes youre right. It was by accident yesterday. I have created a fork of develop and created an upstream branch to push my changes.

@Xtinc-T should this PR be closed?


Simplified geometry rendering failing in some cases

Using a model-driven map with very small polygonal features and clustering off, the features are initially drawn as the simplified points but are then replaced with their polygon renderings despite being very small (as much as a few pixels) at the current scale.

When clustering is not enabled, then there is no opportunity to transform a polygon or a line to a point.
As far as the geometry simplification performed on the server side, little improvement can be done. This is because the server can not predict the projection that the geometry will be displayed in.
The logic of transforming lines and polygons to points has to be performed on the client side. More particularly, it should be done in the NunaliitFeatureStrategy. Currently, the desired logic exists in the clustering process. The logic should be repeated for non-clustering overlays.

Thinking this over, we should probably remove the dynamic clustering of lines and polygons from the clustering process. It is now a duplication of the minimumSize process and would lead to confusion.
Also, minimumSize process should always be installed.


First part of ERC734

I'm not sure i understood the part with keys correctly. When function e.g. addKey is called i'm checking if the key is hash of the caller address, which i saw from the example from origin-playground.
EDIT:  After a little more research i saw here that key can be added on behalf of somebody else who signed this transaction(which is not implemented here). Other than that, is there any other way this key is going to be used?

@filiplazovic the addKeySigned method here is not part of the proposed ERC734 standard. I was just experimenting with that. It does not need to be implemented here.

@tyleryasaka  This can be reviewed

Hey @filiplazovic , this is looking really good!
To me, there are two approaches here:

Provide a single setKey method, and assume that conversion from bits to human-friendly integers will be handled externally (off-chain). I would expect this approach to be more efficient in terms of gas usage.

Provide separate addKey and removeKey methods, and convert from human-friendly integers to bitmask representations on-chain. (In this case, I don't think setKey is needed.) This is the approach you are taking here.

I personally lean toward the first approach. I don't think it is as important to have a clean solidity interface. I would rather optimize for gas. But if you prefer the second approach, I'm fine with that for now.

@filiplazovic I made a few tweaks so that the interface matches this interface as closely as possible.


Add initial default sorting for SelectableTable.

Add skeleton prop to StatusBox inside SelectableTable component.

/hold

/assign @GowthamShanmugam @bipuladh @SanjalKatiyar

/remove-hold

/lgtm
@bipuladh for approval as I can see there was a comment from his side on the PR...

/approve cancel


Improve instrumenter logging

Not finding all components that we can instrument in an application is normal. For example, we may find symbols related to http.Serve, but no symbols for gRPC. At the same time, it would be good to show what components (features) we managed to instrument in an application.

This PR changes few Warn messages to Debug, related to not finding certain symbol offsets.
This PR also prints which features we instrumented in a given application.

For example, on start we'd print this for our integration tests server with INFO logging:
time=2023-04-20T10:46:36.076-04:00 level=INFO msg="creating instrumentation pipeline"
time=2023-04-20T10:46:36.270-04:00 level=INFO msg="instrumented features ['go runtime','http server','grpc server']"
time=2023-04-20T10:46:36.271-04:00 level=INFO msg="Starting main node"

If we try to instrument our pingserver test application, we'll only print a subset, e.g no 'grpc server':
time=2023-04-20T10:46:36.076-04:00 level=INFO msg="creating instrumentation pipeline"
time=2023-04-20T10:46:36.270-04:00 level=INFO msg="instrumented features ['go runtime','http server']"
time=2023-04-20T10:46:36.271-04:00 level=INFO msg="Starting main node"

Thanks Mario!