text:
🐛 [firebase_crashlytics] causing the macOS to not build in flutter

Bug report
Describe the bug
When using firebase_crashlytics the app will not build
Steps to reproduce
Steps to reproduce the behavior:

Create a new flutter project using flutter create
Add the firebase_core and firebase_crashlytics
Use the FlutterFire CLI to automate adding Firebase project
Try to run the project

/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'PromisesSwift' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'GoogleDataTransport' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'abseil' from project 'Pods')
warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'abseil' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'GoogleUtilities' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'GTMAppAuth' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'gRPC-Core' from project 'Pods')
warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-Core' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'gRPC-C++-gRPCCertificates-Cpp' from project 'Pods')
/Users/ahmedhnewa/development/projects/fresh_notes/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (in target 'gRPC-C++' from project 'Pods')
warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')
warning: Run script build phase '[firebase_crashlytics] Crashlytics Upload Symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
** BUILD FAILED **

Exception: Build process failed

See error or incorrect behavior

Expected behavior
It would be nice if we were able to run the app and build it successfully
Sample project
A example GitHub repo
Clone it and use FlutterFire to add the project and try to run it

Additional context

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 3.16.3, on macOS 14.1.2 23B92 darwin-arm64, locale en-IQ)
    • Flutter version 3.16.3 on channel stable at /Users/ahmedhnewa/development/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0366e0a3f (33 hours ago), 2023-12-05 19:46:39 -0800
    • Engine revision 54a7145303
    • Dart version 3.2.3
    • DevTools version 2.28.4

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/ahmedhnewa/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_SDK_ROOT = /Users/ahmedhnewa/Library/Android/sdk
    • Java binary at: /Users/ahmedhnewa/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/ahmedhnewa/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Community Edition (version 2023.3)
    • IntelliJ at /Users/ahmedhnewa/Applications/IntelliJ IDEA Community Edition.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 233.11799.172

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.1.2 23B92 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 110.0.5481.177
    ! Error: Browsing on the local area network for Ahmed’s iPhone. Ensure the device is unlocked and attached with a cable or
      associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

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

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Resolving dependencies...
Got dependencies.
Dart SDK 3.2.3
Flutter SDK 3.16.3
fresh_notes 0.0.1+1

dependencies:
- auto_size_text 3.0.0 [flutter]
- bloc 8.1.2 [meta]
- cached_network_image 3.3.0 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- cloud_firestore 4.13.3 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- connectivity_plus 5.0.2 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- cupertino_icons 1.0.6
- equatable 2.0.5 [collection meta]
- firebase_analytics 10.7.2 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_app_check 0.2.1+6 [firebase_app_check_platform_interface firebase_app_check_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.15.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.24.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_storage 11.5.3 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
- flutter_bloc 8.1.3 [bloc flutter provider]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math web]
- flutter_quill 9.0.0-dev-7 [flutter flutter_localizations intl collection flutter_colorpicker quiver characters diff_match_patch equatable meta url_launcher flutter_keyboard_visibility device_info_plus super_clipboard]
- flutter_quill_extensions 9.0.0-dev-7 [flutter http path meta universal_html cross_file flutter_quill photo_view video_player youtube_player_flutter url_launcher super_clipboard gal gal_linux image_picker]
- flutter_staggered_grid_view 0.7.0 [flutter]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- fresh_base_package 0.0.1 [flutter]
- gal 2.2.0 [flutter]
- go_router 12.1.1 [collection flutter flutter_web_plugins logging meta]
- google_sign_in 6.1.6 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- hydrated_bloc 9.1.2 [bloc hive meta synchronized]
- image_picker 1.0.4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- image_picker_android 0.8.8+2 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- intl 0.18.1 [clock meta path]
- json_annotation 4.8.1 [meta]
- logging 1.2.0
- lottie 2.7.0 [archive flutter path vector_math]
- meta 1.10.0
- path 1.8.3
- path_provider 2.1.1 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- share_plus 7.2.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- smooth_page_indicator 1.1.0 [flutter]
- sqflite 2.3.0 [flutter sqflite_common path]

dev dependencies:
- auto_screenshot 0.0.2 [checked_yaml collection flutter_test integration_test json_annotation path yaml]
- build_runner 2.4.7 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_gen_runner 5.3.2 [flutter_gen_core build collection crypto glob path]
- flutter_lints 3.0.1 [lints]
- flutter_quill_test 9.0.0-dev-7 [flutter flutter_quill flutter_test]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]
- freezed 2.4.5 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- icons_launcher 2.1.6 [args image path universal_io yaml]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- test 1.24.9 [analyzer async boolean_selector collection coverage http_multi_server io js matcher node_preamble package_config path pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel test_api test_core typed_data web_socket_channel webkit_inspection_protocol yaml]

dependency overrides:
- flutter_quill 9.0.0-dev-7 [flutter flutter_localizations intl collection flutter_colorpicker quiver characters diff_match_patch equatable meta url_launcher flutter_keyboard_visibility device_info_plus super_clipboard]
- flutter_quill_extensions 9.0.0-dev-7 [flutter http path meta universal_html cross_file flutter_quill photo_view video_player youtube_player_flutter url_launcher super_clipboard gal gal_linux image_picker]
- flutter_quill_test 9.0.0-dev-7 [flutter flutter_quill flutter_test]

transitive dependencies:
- _fe_analyzer_shared 64.0.0 [meta]
- _flutterfire_internals 1.3.14 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 6.2.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.4.9 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.1 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.1 [built_collection built_value crypto http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.4.1 [analyzer async build collection convert crypto graphs logging package_config path pool pub_semver stream_transform yaml]
- build_runner_core 7.2.11 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.8.0 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 3.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.0 [cached_network_image_platform_interface flutter flutter_cache_manager]
- characters 1.3.0
- charcode 1.3.1
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- clock 1.1.1
- cloud_firestore_platform_interface 6.0.7 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.8.7 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.8.0 [built_collection built_value collection matcher meta]
- collection 1.18.0
- color 3.0.0
- connectivity_plus_platform_interface 1.2.4 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- coverage 1.6.4 [args logging package_config path source_maps stack_trace vm_service]
- cross_file 0.3.3+8 [meta web]
- crypto 3.0.3 [typed_data]
- csslib 1.0.0 [source_span]
- dart_style 2.3.4 [analyzer args collection path pub_semver source_span]
- dartx 1.2.0 [characters collection crypto meta path time]
- dbus 0.7.10 [args ffi meta xml]
- device_info_plus 9.1.1 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32 win32_registry]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- diff_match_patch 0.4.1
- fake_async 1.3.1 [clock collection]
- ffi 2.1.0
- file 6.1.4 [meta path]
- file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.1 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- firebase_analytics_platform_interface 3.8.2 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.5+9 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_app_check_platform_interface 0.1.0+8 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_app_check_web 0.1.0+8 [_flutterfire_internals firebase_app_check_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 7.0.6 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.8.9 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.9.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_storage_platform_interface 5.1.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.6.15 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.1.0
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_colorpicker 1.0.3 [flutter]
- flutter_driver 0.0.0 [file flutter flutter_test fuchsia_remote_debug_protocol path meta vm_service webdriver async boolean_selector characters clock collection matcher material_color_utilities platform process source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api vector_math web]
- flutter_gen_core 5.3.2 [path yaml mime xml dartx color collection json_annotation glob dart_style args pub_semver]
- flutter_inappwebview 5.8.0 [flutter]
- flutter_keyboard_visibility 5.4.1 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_linux flutter_keyboard_visibility_macos flutter_keyboard_visibility_web flutter_keyboard_visibility_windows flutter]
- flutter_keyboard_visibility_linux 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_macos 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_keyboard_visibility_windows 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_plugin_android_lifecycle 2.0.17 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
- frontend_server_client 3.2.0 [async path]
- fuchsia_remote_debug_protocol 0.0.0 [process vm_service file meta path platform]
- gal_linux 0.0.1-dev-3 [flutter gal path]
- glob 2.1.2 [async collection file path string_scanner]
- google_identity_services_web 0.2.2 [js meta]
- google_sign_in_android 6.1.20 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.6.3 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.4.2 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.12.2+1 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http js]
- graphs 2.3.1 [collection]
- hive 2.2.3 [meta crypto]
- html 0.15.4 [csslib source_span]
- http 1.1.2 [async http_parser meta web]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.1.3 [archive meta xml]
- image_picker_for_web 3.0.1 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.8+4 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.1 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- integration_test 0.0.0 [flutter flutter_driver flutter_test path vm_service async boolean_selector characters clock collection fake_async file matcher material_color_utilities meta source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api vector_math web webdriver]
- io 1.0.4 [meta path string_scanner]
- irondash_engine_context 0.4.0 [flutter plugin_platform_interface]
- irondash_message_channel 0.3.1 [flutter ffi]
- js 0.6.7 [meta]
- lints 3.0.0
- matcher 0.12.16 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.5.0 [collection]
- mime 1.0.4
- nested 1.0.0 [flutter]
- nm 0.5.0 [dbus]
- node_preamble 2.0.2
- octo_image 2.0.0 [flutter]
- package_config 2.1.0 [path]
- path_provider_android 2.2.1 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.1 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.1 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- petitparser 6.0.2 [meta]
- photo_view 0.14.0 [flutter]
- pixel_snap 0.1.4 [flutter]
- platform 3.1.2
- plugin_platform_interface 2.1.7 [meta]
- pointycastle 3.7.3 [collection convert js]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 6.1.1 [collection flutter nested]
- pub_semver 2.1.4 [collection meta]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- rxdart 0.27.7
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 3.0.2 [path shelf shelf_static]
- shelf_static 1.1.2 [convert http_parser mime path shelf]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- sky_engine 0.0.99
- source_gen 1.4.0 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_map_stack_trace 2.1.1 [path source_maps stack_trace]
- source_maps 0.10.12 [source_span]
- source_span 1.10.0 [collection path term_glyph]
- sprintf 7.0.0
- sqflite_common 2.5.0+2 [synchronized path meta]
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- super_clipboard 0.7.3 [flutter collection meta super_native_extensions]
- super_native_extensions 0.7.3 [flutter flutter_web_plugins meta ffi collection js path uuid irondash_engine_context irondash_message_channel device_info_plus pixel_snap]
- sync_http 0.3.1
- synchronized 3.1.0
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- test_core 0.5.9 [analyzer args async boolean_selector collection coverage frontend_server_client glob io meta package_config path pool source_map_stack_trace source_maps source_span stack_trace stream_channel test_api vm_service yaml]
- time 2.1.3 [clock]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- universal_html 2.2.4 [async csslib charcode collection html meta source_span typed_data universal_io]
- universal_io 2.2.2 [collection meta typed_data]
- url_launcher 6.2.1 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- url_launcher_android 6.2.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.2.1 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.2.0 [flutter plugin_platform_interface]
- url_launcher_web 2.2.1 [flutter flutter_web_plugins url_launcher_platform_interface web]
- url_launcher_windows 3.1.0 [flutter url_launcher_platform_interface]
- uuid 4.2.1 [crypto sprintf meta]
- vector_math 2.1.4
- video_player 2.8.1 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]
- video_player_android 2.4.10 [flutter video_player_platform_interface]
- video_player_avfoundation 2.5.2 [flutter video_player_platform_interface]
- video_player_platform_interface 6.2.1 [flutter plugin_platform_interface]
- video_player_web 2.1.2 [flutter flutter_web_plugins video_player_platform_interface]
- vm_service 11.10.0
- watcher 1.1.0 [async path]
- web 0.3.0
- web_socket_channel 2.4.0 [async crypto stream_channel]
- webdriver 3.0.2 [matcher path stack_trace sync_http]
- webkit_inspection_protocol 1.2.1 [logging]
- win32 5.1.1 [ffi]
- win32_registry 1.1.2 [ffi win32]
- xdg_directories 1.0.3 [meta path]
- xml 6.5.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]
- youtube_player_flutter 8.1.2 [flutter flutter_inappwebview]

Do you have an error log? I'm facing same problem, maybe.
When I try to build I'm receiving this error:
'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (In target 'Flutter' from object 'Pods')

Do you have an error log? I'm facing same problem, maybe.
When I try to build I'm receiving this error:
'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (In target 'Flutter' from object 'Pods')

Try to use flutter run or build with -v modifier.

Hi. The error you are facing is easy to fix
You will have to increase the minimum version in podfile and Xcode project

Thanks for the report @freshtechtips
Can you take a look at this solution and check if it helps in your case to resolve the issue ?

When building using Xcode:

It doesn't show any errors at all and it's not related to the warrnings

I got below errors:

I got below errors:

Are you using the latest version of Xcode?? Because I didn't face that error

No, I am on 13.2.1

No, I am on 13.2.1

This project always uses the latest versions
If I'm unable to help you reproduce the error and you can't fix it
We can close it
I'm sure there will be another person that will report with more info

Closing the issue may not be an ideal solution and without any way of reproducing the issue, we can only assume it's a configuration issue. Can you try to run flutterfire CLI again using the latest dev release?
dart pub global activate flutterfire_cli 0.3.0-dev.18 --overwrite
flutterfire configure

Closing the issue may not be an ideal solution and without any way of reproducing the issue, we can only assume it's a configuration issue. Can you try to run flutterfire CLI again using the latest dev release?
dart pub global activate flutterfire_cli 0.3.0-dev.18 --overwrite
flutterfire configure

Sure thing, thank you for your understanding

Still getting the exact same build error

Please notice that after adding the firebase_crashlytics the macOS app will not build even after removing it, the only solution is to recreate the macOS project or remove anything related to firebase_crashlytics

@freshtechtips
From the original description error log you shared, I see below entries in it:
Pods/Pods.xcodeproj so want to confirm if you are opening Runner.xcworkspace or Runner.xcodeproj ?

@freshtechtips
From the original description error log you shared, I see below entries in it:
Pods/Pods.xcodeproj so want to confirm if you are opening Runner.xcworkspace or Runner.xcodeproj ?

No, I'm just running from Flutter Run directly
The unknown build error also happens when build in Xcode ane open using Xcworkspace
Do you want to use anydesk and debug it on my machine so you see more details about the bug?

I am unable to replicate the reported issue, but keeping this open for team's input / tracking.

I'm fairly sure it is a result of this problem that has been fixed and merged in the FlutterFire CLI: https://github.com/invertase/flutterfire_cli/pull/245
However, it has not been released yet. Please follow this channel https://github.com/invertase/flutterfire_cli/issues/14.
We will announce the latest FlutterFire version in that channel which you can use to configure your project that ought to fix your problem 👍

authors: burnermanx darshankawar freshtechtips russellwheatley

repo: firebase/flutterfire


text:
Firebase.auth appears as unresolved reference

I'll try to use the Firebase auth reference on my project, but it won't works.
https://github.com/firebase/snippets-android/blob/61b336de5aab6145f44fcaecde9f26366e0fff46/auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/CustomAuthActivity.kt#L28

Hi @clcmo
Make sure you're using the Firebase dependency suffixed with -ktx:
implementation 'com.google.firebase:firebase-auth-ktx'

You can also refer to our documentation on how to setup Firebase Auth on Android.

@clcmo It's been a while since this issue has opened, so I'm going to close it now.
Feel free to re-open if you're still facing this issue.

import com.google.firebase.auth.ktx.auth
import com.google.firebase.ktx.Firebase

Patch

source: gharchive/issue

authors: ChinoJones clcmo thatfiredev

repo: firebase/snippets-android

license_type: permissive

license_source: bigquery


text:
Dragging a layer displays a dashed border moving the image by one pixel

When you click on a layer within the page a dashed border is displayed. This border changes the position of the image by one pixel horizontally and vertically.
I suggest to use outline instead of border.
Sebastian

Nice tip, done, thanks.
Honza

authors: SebastianZ janodvarko

repo: firebug/pixel-perfect


text:
Add resource reservations for guaranteed instance capacity

Prevents issues where GCP may be oversubscribed

Plan:

[ ] Two types of instances: N2 and N4
[ ] 1 reservation on each continent for a Relay
[ ] Reservations and committed use discounts for portal infra

repo: firezone/firezone

license_source: github-api


text:
feat(gateway): resolve DNS in the background

When receiving a connection request for a DNS resource, the gateway will first resolve the domain name and only then respond with the ICE credentials needed by the client to establish the connection. This was necessary because prior to #4994, the response sent to the client included the resolved IPs for the domain name.
With #4994, the gateway only needs to resolve the domain name in order to correctly map the client's proxy IPs upon incoming traffic. As a result, we can remove the DNS resolution from the hot-path of connection setup and always directly accept a client's connection request.
Currently, if the DNS resolution fails, we never respond to the client, thus forcing it into a timeout to try and establish a new connection. By always accepting the connection, this case simply doesn't occur.
This change makes a particular edge-case more obvious although not necessarily worse in my opinion: If DNS resolution fails, the client is currently left hanging without a response and will eventually timeout the connection. With this change, the client has a connection but due to the failed DNS query, packets for this DNS resource will be dropped as unallowed packets. Packets to other DNS resources will send an allow-access request and resolved accordingly.
If DNS resolution on the gateway doesn't work reliably, almost nothing of firezone works. The only difference with this PR is that a failed connection (i.e. behaviour on main) is self-healing after ~20s whereas with this change the user would have to sign-out and in again in order to clear all connection state.

If DNS resolution on the gateway doesn't work reliably, almost nothing of firezone works. The only difference with this PR is that a failed connection (i.e. behaviour on main) is self-healing after ~20s whereas with this change the user would have to sign-out and in again in order to clear all connection state.

We can improve on this with some refactoring: The gateway already has functionality to refresh a DNS query if it sees packets for a proxy IP but no traffic for the translated IP. We can adopt this to also refresh the DNS query if we see traffic for a proxy IP and don't even have a real IP for this domain.

If DNS resolution on the gateway doesn't work reliably, almost nothing of firezone works. The only difference with this PR is that a failed connection (i.e. behaviour on main) is self-healing after ~20s whereas with this change the user would have to sign-out and in again in order to clear all connection state.

We can improve on this with some refactoring: The gateway already has functionality to refresh a DNS query if it sees packets for a proxy IP but no traffic for the translated IP. We can adopt this to also refresh the DNS query if we see traffic for a proxy IP and don't even have a real IP for this domain.

I just attempted to implement this, I think it is actually reasonably clean.

If we wait with this PR until the new clients are released, we can make it substantially simpler by not worrying about backwards-compatibility!

This is blocked on being able to remove the backwards-compatibility layer for clients < 1.1. We could theoretically ship it earlier but it is a lot simpler to just delay this until we are happy to no longer support < 1.1 clients on newer gateways.

Will essentially be replaced by https://github.com/firezone/firezone/pull/6732.

source: gharchive/pull-request


text:
fix(android): force-override no ANSI also for format

As far as I understand, this should not be necessary because with_ansi(false) should propagate to all sub-components of tracing_subscriber. Unfortunately, that doesn't seem to be the case as we are still getting italic field names in spans, even with with_ansi(false).

Doesn't fix it :(


text:
Set upper bound on jinja2 dependency

Describe the feature
At the time of this writing, jinja2 v3.0.0a1 is now available on PyPi. This version is not compatible with dbt.
We should either:

set the upper bound on the jinja2 dependency to be <3.0.0, or
make dbt compatible with version 3.0.0 when it is released (likely as a part of a future issue)

The proximate error here looks like:
No module named 'jinja2._compat'

as far as I can tell.

I am pretty sure that since we dropped python 2.x support, we don't need that call anymore.

authors: beckjake drewbanin

repo: fishtown-analytics/dbt


text:
Update to new character device interface

The sysfs interface for gpio in linux is deprecated, see here
THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO
Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED.

Are there any plans to port this library to the new interface?
Or maybe create a new library using  libgpiod?

There are currently no plans to port this library to the new interface. From a Node.js perspective using the libgpiod C library is more complex than using the GPIO sysfs interface as native bindings would be required to use libgpiod C library.

Would be nice to see libgpiod supported.
i've tried to write the node bindings myself with Nan to help with compatibility but no luck for the moment.
The maintainer of python-libgpiod commented something interesting on their codebase, he's trying to avoid to link with libgpiod directly, if i understood correctly, and trying a pure filesystem approach.
Maybe that's possible for onoff too.

I'll try to make a high-quality native addon that exposes the newer chardev interface.

I wish you the best of luck working on this.

... sysfs may still be required on old systems, or users may want to avoid native addons. So it's nice for them to be able to choose.

It won't be possible to fully avoid native addons with onoff as onoff depends on the epoll native addon for detecting the events generated by interrupt generating GPIO pins.

authors: fivdi markusr sombriks

repo: fivdi/onoff

license: mit


text:
feature/shopify-api-updates

PR Overview
This PR will address the following Issue/Feature: Issue #60 and Issue #67
This PR will result in the following new package version: v0.9.0

This is not technically a breaking change, but due to the upstream changes in the source, this is considered breaking.
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
These changes are made breaking due to changes in the source.

In June 2023 the Shopify connector received an update which upgraded the connector to be compatible with the new 2023-04 Shopify API. As a result, the following fields have been removed as they were deprecated in the API upgrade: (PR #70)

model
field removed

stg_shopify__customer
lifetime_duration

stg_shopify__order_line
fulfillment_service

stg_shopify__order_line
destination_location_* fields

stg_shopify__order_line
origin_location_* fields

stg_shopify__order
total_price_usd

stg_shopify__order
processing_method

Please be aware that the removal of the fields from the staging models results in the removal of the fields in the relevant downstream models:

model
field removed

shopify__customer
lifetime_duration

shopify__customer_emails
lifetime_duration

shopify__order_lines
fulfillment_service

shopify__order_lines
destination_location_* fields

shopify__order_lines
origin_location_* fields

shopify__orders
total_price_usd

shopify__orders
processing_method

Documentation Updates

The shopify_using_shop_metafields variable was added to the Adding Metafields of the README. It was erroneously omitted in a previous release.
Documentation provided in the README for how to connect sources when leveraging the union schema/database feature.
Removal of the current_total_price yml definition from the shopify__orders model as it was not being created in the model.

PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:

[X] dbt compile
[X] dbt run –full-refresh
[X] dbt run
[X] dbt test
[n/a] dbt run –vars (if applicable)

Before marking this PR as "ready for review" the following have been applied:

[X] The appropriate issue has been linked and tagged
[X] You are assigned to the corresponding issue and this PR
[x] BuildKite integration tests are passing

Detailed Validation
Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

[X] You have validated these changes and assure this PR will address the respective Issue/Feature.
[X] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
[X] You have provided details below around the validation steps performed to gain confidence in these changes.

Not much validation was needed for these changes. I used the release notes as the basis for what fields were being deprecated. I then removed these fields from the staging models, macros, and yml documentation from the source package and then made similar adjustments to this package. I then ran the models and confirmed the fields were no longer present and that no errors resulted from the removal of the upstream fields in the downstream models. No further validation was necessary per my opinion.
Standard Updates
Please acknowledge that your PR contains the following standard updates:

Package versioning has been appropriately indexed in the following locations:

[X] indexed within dbt_project.yml
[X] indexed within integration_tests/dbt_project.yml

[X] CHANGELOG has individual entries for each respective change in this PR

[X] README updates have been applied (if applicable)

[n/a] DECISIONLOG updates have been updated (if applicable)
[X] Appropriate yml documentation has been added (if applicable)

dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:

[X] docs were regenerated (unless this PR does not include any code or yml updates)

If you had to summarize this PR in an emoji, which would it be?

🛫

See notes in the shopify source PR

Also, we should removed variant_fulfillment_service from shopify__order_lines and shopify__inventory_levels , if that fulfillment_services field gets removed from the upstream product_variant model.

Finally, I'm noticing no models are showing up under files changed, for the ones with fields that are supposed to be removed. But I don't see the to-be removed fields in those models on this branch anyways... I must be missing something?

See notes in the shopify source PR

See my responses from the source PR

Also, should we  remove variant_fulfillment_service from shopify__order_lines and shopify__inventory_levels , if that fulfillment_services field gets removed from the upstream product_variant model.

We are still keeping the fullfilment_service from the product_variant table as it is still able to be synced from the endpoint and is not listed as deprecated per the connector release notes.

Finally, I'm noticing no models are showing up under files changed, for the ones with fields that are supposed to be removed. But I don't see the to-be removed fields in those models on this branch anyways... I must be missing something?

All the removed fields took place in the source package. They are removed from the end model because we are performing a select * in the respective models which now are returning less fields. As such, no models need to be changed but the ymls have been updated.

Thanks for explaining!
One last thing is I still don't see the shopify_using_shop_metafields bit in the readme

Thanks for explaining!
One last thing is I still don't see the shopify_using_shop_metafields bit in the readme

@fivetran-reneeli the metafield section is here

authors: fivetran-joemarkiewicz fivetran-reneeli


text:
Revamp Demo

It takes time to understand the current demo page. It should have message display in-page instead of console log.
Also should show the current key status, scope, etc.

Dead for three years, closing to clean up my Issues.

repo: fkeymaster/fkeymaster

license: MIT


text:
Animation of the player's sprite

When trying to create an animation of the player's sprite, it gives out an error. I restarted the Android Studio, updated the packages of Flame. The problem is not in links, but in the package of Flame. Created a new project and tried to make an animation, the result is the same. Flutter also does not see the package 'Package: Flame/images.dart', although on the site it is used as an example

Below is the problem with exporting

@ZagumennikovYaroslav  This doesn't look like a bug in flame. The code you are referring to is for standalone use of image cache. But in your code you probably just want to use the default image cache. Instead of image you need to use gameRef.image.

well, then why does he write in line 53 and 54 the indefinite name "assets" and "images"

well, then why does he write in line 53 and 54 the indefinite name "assets" and "images"

Your code is in Player.onLoad and at that place images and assets are not defined anywhere. To use an object, it should first be created somewhere and should be accessible at the place where you are writing your code.
images and assets are members of the Game class. So you access them you'll have to get hold of your game class.
https://github.com/flame-engine/flame/blob/c6827a45dfecf261d001518e5088d3c676f05ae6/packages/flame/lib/src/game/game.dart#L23
https://github.com/flame-engine/flame/blob/c6827a45dfecf261d001518e5088d3c676f05ae6/packages/flame/lib/src/game/game.dart#L28

authors: ZagumennikovYaroslav ufrshubham

repo: flame-engine/flame


text:
API getCollections returns response code: 500, message: Internal Server Error

Something went wrong
API getCollections returns response code: 500, message: Internal Server Error
Go to Setup.

can confirm, also getting this error.

`> chromadb-admin@0.1.0 start

next start

▲ Next.js 14.2.3

Local:        http://localhost:3000

✓ Starting...
✓ Ready in 203ms
An unexpected error occurred: TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async J.listCollections (/app/.next/server/chunks/322.js:12:76536)
at async o (/app/.next/server/app/api/collections/route.js:1:2283)
at async c (/app/.next/server/app/api/collections/route.js:1:1236)
at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920)
at async doRender (/app/node_modules/next/dist/server/base-server.js:1377:42)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1599:28) {
[cause]: Error: connect ECONNREFUSED 127.0.0.1:8000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 8000
}
}
⨯ TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async J.listCollections (/app/.next/server/chunks/322.js:12:76536)
at async o (/app/.next/server/app/api/collections/route.js:1:2283)
at async c (/app/.next/server/app/api/collections/route.js:1:1236)
at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920)
at async doRender (/app/node_modules/next/dist/server/base-server.js:1377:42)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1599:28) {
[cause]: Error: connect ECONNREFUSED 127.0.0.1:8000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 8000
}
}
An unexpected error occurred: TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async J.listCollections (/app/.next/server/chunks/322.js:12:76536)
at async o (/app/.next/server/app/api/collections/route.js:1:2283)
at async c (/app/.next/server/app/api/collections/route.js:1:1236)
at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920)
at async doRender (/app/node_modules/next/dist/server/base-server.js:1377:42)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1599:28) {
[cause]: Error: connect ECONNREFUSED 127.0.0.1:8000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 8000
}
}
⨯ TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async J.listCollections (/app/.next/server/chunks/322.js:12:76536)
at async o (/app/.next/server/app/api/collections/route.js:1:2283)
at async c (/app/.next/server/app/api/collections/route.js:1:1236)
at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920)
at async doRender (/app/node_modules/next/dist/server/base-server.js:1377:42)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1599:28) {
[cause]: Error: connect ECONNREFUSED 127.0.0.1:8000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 8000
}
}`

Ahh, I figured it out. Setting it to localhost didn't work. Setting instead to the hostname of the server worked fine.

authors: jarildson shanghaiyangming

repo: flanker/chromadb-admin


text:
This fixes the script

Coinmarketcap changed their website. This fixes it.

@flapjax how do you add PR to another PR ?

@skeith I think you'd have to make a fork of spithash:master and PR to that. But, I'm merging this now, so you can just make a new PR on my repo if you want :)

I did, it was just aiohttp stuff, so I just rebase my PR and apply again? sorry, not git gud yet

Yes I see your new PR now. I'm checking it out. I can probably merge that one with no problems.

authors: flapjax skeith spithash

repo: flapjax/FlapJack-Cogs


text:
pytorch 2.4 support

Checklist

[x] add pytorch 2.4 and cuda 12.4 to release wheel matrix (#398 )
[ ] torch.compile compatibility, use new custom operator api

torch.compile compatibility: https://github.com/flashinfer-ai/flashinfer/pull/554

About vLLM support:
hello, there! I am trying to use FlashInfer with vLLM (Torch 2.4.0, CUDA 12.6) self-compiled. vLLM complains about .../torch/_library/infer_schema.py
ValueError: infer_schema(func): Parameter bitorder has an unsupported default value (we only support int, float, bool, None). Please file an issue on GitHub so we can prioritize this. Got func with signature (x: torch.Tensor, bitorder: str = 'big') -> torch.Tensor)

Does it relate to this issue? Thanks.

Hi @DefinitlyEvil
Thanks for raising this issue.

Can you try the main branch of FlashInfer?
After you installed the main branch, try FLASHINFER_TEST_TORCH_COMPILE=1 pytest -svx ./tests/test_quantization.py
If that doesn't work, can you try install PyTorch nightly?
If that doesn't work, can you please provide full logs of the following command: TORCHDYNAMO_REPRO_AFTER="dynamo" TORCH_COMPILE_DEBUG=1 TORCH_LOGS="+dynamo,+inductor" FLASHINFER_TEST_TORCH_COMPILE=1 pytest -svx ./tests/test_quantization.py

Hi @DefinitlyEvil
Thanks for raising this issue.
1. Can you try the main branch of FlashInfer?

2. After you installed the main branch, try `FLASHINFER_TEST_TORCH_COMPILE=1 pytest -svx ./tests/test_quantization.py`

3. If that doesn't work, can you try install PyTorch nightly?

4. If that doesn't work, can you please provide full logs of the following command: `TORCHDYNAMO_REPRO_AFTER="dynamo" TORCH_COMPILE_DEBUG=1 TORCH_LOGS="+dynamo,+inductor" FLASHINFER_TEST_TORCH_COMPILE=1 pytest -svx ./tests/test_quantization.py`

Hi, thanks for investivating it. My server was deployed on a production environment, I had to quickly revert to vLLM 0.6.2 and disable FlashInfer.
I couldn't answer all questions for now (I apologize), I did use main branch, all compilations are good.
As for question 2:
ImportError while loading conftest '/root/flashinfer/tests/conftest.py'.
tests/conftest.py:4: in <module>
    import flashinfer
flashinfer-aot/flashinfer/__init__.py:22: in <module>
    from .cascade import (
flashinfer-aot/flashinfer/cascade.py:21: in <module>
    from .decode import (
flashinfer-aot/flashinfer/decode.py:33: in <module>
    from .prefill import get_batch_prefill_module, get_single_prefill_module
flashinfer-aot/flashinfer/prefill.py:34: in <module>
    from .quantization import packbits, segment_packbits
flashinfer-aot/flashinfer/quantization.py:45: in <module>
    @register_custom_op("flashinfer::packbits", mutates_args=())
/opt/miniconda3/envs/vllm/lib/python3.12/site-packages/torch/_library/custom_ops.py:119: in inner
    schema_str = torch._custom_op.impl.infer_schema(fn, mutates_args)
/opt/miniconda3/envs/vllm/lib/python3.12/site-packages/torch/_library/infer_schema.py:61: in infer_schema
    error_fn(
/opt/miniconda3/envs/vllm/lib/python3.12/site-packages/torch/_library/infer_schema.py:21: in error_fn
    raise ValueError(
E   ValueError: infer_schema(func): Parameter bitorder has an unsupported default value (we only support int, float, bool, None). Please file an issue on GitHub so we can prioritize this. Got func with signature (x: torch.Tensor, bitorder: str = 'big') -> torch.Tensor)

As for 3, I just installed PyTorch 2.6.0 dev version, but is there a make clean command so I can recompile them?

repo: flashinfer-ai/flashinfer


text:
equinixmetal: use metro instead of facility

Follow up of: https://github.com/flatcar-linux/mantle/pull/281
Signed-off-by: Mathieu Tortuyaux mtortuyaux@microsoft.com

[ ] Not sure if it's require a changelog entry ? Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)

Please cherry pick for all active release maintenance branches

(No changelog for our release notes needed, it's an internal detail where the test ran)

cherry-picked to:

flatcar-3033
flatcar-3066
flatcar-3127
flatcar-lts-2605

repo: flatcar-linux/scripts


text:
Azure images are out-of-date

Description
Microsoft Azure Market place has out of date versions of Flatcar.
Impact
Running into an ignition error with 3510.2.3 when trying to deploy an Azure Gen2 VM with multiple disks.  Thinking this might be fixed in the latest stable version as my butane configuration works on Proxmox with EFI bios.
Environment and steps to reproduce
Log into Azure
List available images from Kinvolk:
az vm image list --all -p kinvolk -f flatcar -s stable
Latest image for stable is out of date - 3510.2.3 from Jun 21, 2023
{
"architecture": "x64",
"offer": "flatcar_pro",
"publisher": "kinvolk",
"sku": "stable-gen2",
"urn": "kinvolk:flatcar_pro:stable-gen2:3510.2.3",
"version": "3510.2.3"
}
Expected behavior
Latest stable 3602.2.0 should be available.
Additional information

https://github.com/flatcar/Flatcar/issues/1196

After conversation with Azure Marketplace team for multiple weeks, we finally published marketplace images of Alpha 3732.0.0, Beta 3602.1.6, Stable 3510.2.8. (https://github.com/flatcar/Flatcar/issues/1181)
We are now able to start publishing next versions, including Stable 3602.2.0.

@bignay2000 Just a question, are you still using Flatcar Pro. All the features of Flatcar Pro has been moved to the base image Flatcar, and we do intend to deprecate the offer over the next few days. Will it be possible for you to move your deployments to one of the other offers? If you need help, do let us know.

Just checked and very happy to see the lastest stable.
az vm image list --all -p kinvolk -f flatcar -s stable
{
"architecture": "x64",
"offer": "flatcar-container-linux-free",
"publisher": "kinvolk",
"sku": "stable-gen2",
"urn": "kinvolk:flatcar-container-linux-free:stable-gen2:3602.2.1",
"version": "3602.2.1"
},

@bignay2000 Just a question, are you still using Flatcar Pro. All the features of Flatcar Pro has been moved to the base image Flatcar, and we do intend to deprecate the offer over the next few days. Will it be possible for you to move your deployments to one of the other offers? If you need help, do let us know.

I am using "flatcar-container-linux-free" so I think this is not "Flatcar Pro"

@bignay2000 Just a question, are you still using Flatcar Pro. All the features of Flatcar Pro has been moved to the base image Flatcar, and we do intend to deprecate the offer over the next few days. Will it be possible for you to move your deployments to one of the other offers? If you need help, do let us know.

I am using "flatcar-container-linux-free" so I think this is not "Flatcar Pro"

I am a bit confused @sayanchowdhury , should be using this URN instead?:
{
"architecture": "x64",
"offer": "flatcar-container-linux",
"publisher": "kinvolk",
"sku": "stable-gen2",
"urn": "kinvolk:flatcar-container-linux:stable-gen2:3602.2.1",
"version": "3602.2.1"
},

authors: bignay2000 dongsupark sayanchowdhury

repo: flatcar/Flatcar


text:
metainfo: Check that launchable value matches appid

from lxml import etree

# curl -sL https://hub.flathub.org/repo/appstream/x86_64/appstream.xml.gz | gunzip -- > appstream.xml
components = etree.parse("appstream.xml").getroot()
for component in components.iterchildren(tag="component"):
   if component.attrib.get("type") not in ("desktop","desktop-application"):
        continue
   flathub_id = component.find("bundle").text.split("/")[1]
   launchable = component.xpath("launchable[@type='desktop-id']/text()")
   if launchable:
      l_value = str(launchable[0])
      if l_value != flathub_id + ".desktop":
        print(flathub_id)

These 5 are need to be notified, some of them have multiple launchables defined which is discouraged in the spec.
cat.xtec.clic.JClic
com.github.debauchee.barrier
com.sigmyne.crush
io.itch.tx00100xt.SeriousSamClassic-VK
io.itch.tx00100xt.SeriousSamClassic
net.openra.OpenRA

Issues:

https://github.com/flathub/com.sigmyne.crush/issues/5
https://github.com/flathub/io.itch.tx00100xt.SeriousSamClassic/issues/3
https://github.com/flathub/io.itch.tx00100xt.SeriousSamClassic-VK/issues/5
https://github.com/flathub/com.github.debauchee.barrier/issues/33
https://github.com/flathub/net.openra.OpenRA/issues/71
https://github.com/flathub/cat.xtec.clic.JClic/issues/8

repo: flathub-infra/flatpak-builder-lint


text:
Add license attribute

https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

Thank you for your contribution, but closing this due to age. This project is formally deprecated. Will be adding a notice soon.

authors: indexzero pdehaan

repo: flatiron/union


text:
Merge pull request #1 from flatironinstitute/main

boundary augmentation changes

boundary augmentation

repo: flatironinstitute/neutorch


text:
Switch height/width properties are not working

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
I am trying to resize the switch control. But it seems like width/height property isn't working.
https://flet.dev/docs/controls/switch . Even if I try to adjust the size of the parent element, switch stays to its default size.

Code sample
Logs
import flet as ft

def main(page):
    def button_clicked(e):
        t.value = (
            f"Switch values are:  {c1.value}, {c2.value}, {c3.value}, {c4.value}."
        )
        page.update()

    t = ft.Text()
    c1 = ft.Switch(label="Unchecked switch", value=False, height=5, width=5)
    c2 = ft.Switch(label="Checked switch", value=True)
    c3 = ft.Switch(label="Disabled switch", disabled=True)
    c4 = ft.Switch(
        label="Switch with rendered label_position='left'", label_position=ft.LabelPosition.LEFT
    )
    b = ft.ElevatedButton(text="Submit", on_click=button_clicked)
    page.add(c1, c2, c3, c4, b, t)

ft.app(target=main, view=ft.AppView.WEB_BROWSER)

To reproduce
Run the code attached
Expected behavior
Expected to see a smaller switch
Screenshots / Videos

Screenshots / Video demonstration
[Upload media here]

Operating System
Windows
Operating system details
Windows 11 (OS build: 22631.3880)
Flet version
Version: 0.23.2
Regression
I'm not sure / I don't know
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
No response

Solution: https://stackoverflow.com/a/52572288

Issue has been fixed.
Give it a try by installing the latest Flet prerelease: pip install flet --pre (https://pypi.org/project/flet/#history)
Report if the issue persists.

authors: Sifat-Ahmed ndonkoHenri

repo: flet-dev/flet


text:
GoogleNavigationBar control

TestCode:
import flet as ft

def main(page: ft.Page):
    page.theme_mode = ft.ThemeMode.DARK
    page.title = "GoogleNavigationBar Example"
    page.navigation_bar = ft.GoogleNavigationBar(
        alignment=ft.MainAxisAlignment.CENTER,
        color=ft.colors.GREY_700,
        icon_active_color=ft.colors.WHITE,
        active_color=ft.colors.WHITE,
        bg_active_color=ft.colors.GREY_800,
        border_radius=80,
        # active_border=ft.border.all(1, ft.colors.BLUE_200),
        on_change=lambda e: print("Selected tab:", e.control.selected_index),
        destinations=[
            ft.NavigationDestination(icon=ft.icons.HOME_OUTLINED, label="Home"),
            ft.NavigationDestination(icon=ft.icons.SEARCH_OUTLINED, label="Search"),
            ft.NavigationDestination(icon=ft.icons.BOOKMARK_OUTLINE, label="Bookmark"),
            ft.NavigationDestination(icon=ft.icons.PERSON_OUTLINED, label="Person"),
        ],
    )
    page.add(ft.SafeArea(ft.Text("Hello World!")))

ft.app(target=main)

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant isaffathir


text:
Question:Setting up powermatcher on a raspberry pi

Can anyone give e a simple run down of how to get power matcher running on a raspberry pi?

What is it you want to achieve exactly? PowerMatcher is a smart grid coordination mechanism. It doesn't do anything on its own, needs to be connected to smart devices (or simulated devices).
If you just want to see it working, you can try the demo distribution based on EF-Pi, which also includes PowerMatcher. The zip archive contains a small manual. It can also run on a Raspberry Pi (with Java installed).
Let me know if you need more help!

Hi Wilco,
Thanks for your email.  What I am ultimately hoping to do is build a
virtual power plant!  As you may or may not be aware the Australian energy
market is undergoing a rapid transition to renewable distributed energy.
It's estimated about 7000 batteries were installed last year and more than
20 percent of households have solar pv systems.  Several energy retailers
have virtual power plant system trials operating but none are as elegant as
powermatcher.  A business I have a share in, foxfirelouvers.com already has
installed control systems in many large commercial buildings and
multi-dwelling residential developments.  We have already installed the
hardware (essentially a ruggedized raspberry pi) and our software allows us
to monitor and control devices  via an api, all that is needed is a
coordination mechanism and we will have either a virtual power plant or
distributed energy market.   There may be some potential for some
collaboration here with your organisation if I can get a basic "proof of
concept" demonstration going here in Australia (not sure what form that
would take but am open to suggestions).
My thought was that all I would need to do is classify the devices already
connected to our system into the various categories: time shifter, buffer,
uncontrolled and unconstrained and write some code to connect powermatcher
to our api.
I installed eclipse on a raspberry pi and tried following the instructions
but have been having some issues
For example, I installed eclipse on the pi but wasn't able to get Felix
installed last time I attempted it as the suggested.   Do I really need the
EF-Pi or can I just use Power-matcher?  I am fairly busy this week but will
have another try later in the week.
Would you mind if I sent you some questions if I get stuck?  I don't want
to take up much of you time but it would be helpful to have someone who
understands the technical details to ask a few questions.
Thanks and
Best regards,
Sean Hutton.
On Mar 14, 2017 3:57 AM, "Wilco Wijbrandi" notifications@github.com wrote:

What is it you want to achieve exactly? PowerMatcher is a smart grid
coordination mechanism. It doesn't do anything on its own, needs to be
connected to smart devices (or simulated devices).
If you just want to see it working, you can try the demo distribution
https://github.com/flexiblepower/fpai-apps/releases/download/v15.05/fpai-apps-runtime-release-15-05.zip
based on EF-Pi, which also includes PowerMatcher. The zip archive contains
a small manual. It can also run on a Raspberry Pi (with Java installed).
Let me know if you need more help!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flexiblepower/powermatcher/issues/214#issuecomment-286171326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFb18wTSJ6UD9NgUvNR0pEwi7tkkkItXks5rlXWTgaJpZM4MaHbF
.

Hi Sean,
Good to hear you are looking into PowerMatcher! Reading your story I would advice you to use EF-Pi. Unless you want to integrate PowerMatcher into an existing product, EF-Pi should make your live a lot easier. Especially when you want to make use of the four EFI categories (timeshifter, buffer, uncontrolled and unconstrained) and PowerMatcher, since the logic for that is implemented on top of EF-Pi. The best way to get started is to for the fpai-apps repository, this one contains the PowerMatcher logic for the four categories.
I would advice against doing the actual development on the Raspberry Pi itself, since Eclipse is quite resource intensive. If you want to run EF-Pi (with PowerMatcher) on a Raspberry Pi, you only need to install Java (sudo apt-get install openjdk-8-jdk-headless, assuming you are using Raspbian), unzip the archive and run the run script (./run.sh from within the EF-Pi directory). This should start a webserver on port 8080.
Let's have a separate conversation about possible collaborations. Could you contact me at wilco dot wijbrandi at tno dot nl?
Best regards,
Wilco

authors: seanhutton wilcowijbrandi

repo: flexiblepower/powermatcher


text:
Buttons in the app do not work

When I press the Resize/Emojis/Sounds/Gestures buttons in the app, nothing happens.

I believe you are currently using the iteration 2 of the application. The keys were dummy and will not work. This has been fixed in the iteration 3.
Iteration 3 is currently available on google play store only, and hopefully f-droid will pick up the update soon.

authors: Soupstraw flide


text:
MGMT-18708: Add single CLI command to obtain enrollment cert

~Needs some cleanup but comments welcome in the meantime.~
I'm not too opinionated on the name of the command, the flags, etc. - we could change it to certificate request - though I thought it could be helpful to introduce the user to the concept that they are doing pre-enrollment or registration.

I'm not too opinionated on the name of the command, the flags, etc. - we could change it to certificate request - though I thought it could be helpful to introduce the user to the concept that they are doing pre-enrollment or registration.

The command doesn't register / pre-enroll a device, though, no? I mean, it requests a certificate from the service and returns that, but isn't tied to any device, doesn't tell the service anything about a device, and may even be shared between devices?

The command doesn't register / pre-enroll a device, though, no? I mean, it requests a certificate from the service and returns that, but isn't tied to any device, doesn't tell the service anything about a device, and may even be shared between devices?

I think it will make sense to consider "user requests an enrollment cert" as a specific step in the device lifecycle, rather than outside of the lifecycle. And it would almost certainly be the pre-enrollment step, or part of that step.
The way I had understood it, the eventual vision for the "pre-enrollment" step is it should let the FC service know that a device is expected to enroll, without any guaranteed data available about that device (this relates to the UUID we need to add as a primary key, which isn't in this PR). IMO it makes sense to do this when the user requests an enrollment cert because they are essentially declaring that one or more devices will enroll.
I also wasn't sure whether we will keep supporting sharing the cert between devices long-term, for security reasons, but it should still be possible at the moment until there is a policy-based server-side check on whether the enrollment cert has been used before.
If we want to get this merged ASAP, I can just change the name of the command. But it will be good to sync up on design shortly as I'm trying to also lay the groundwork for the updated pre-enrollment process.

Okay, as discussed, this command can just get a certificate without registering a device, to support legacy onboarding where the user does not know anything about the devices or how many devices will be enrolled. Later on with registration-based onboarding the user can get this same cert with a registration command when registering a device. I've updated the command name to certificate request.

New version incoming that parses expiration in the suggested format. Please hold.

@mangelajo @fzdarsky I've pushed a new version.
Highlights:

The user inputs the desired cert expiration in the format Xd where X is a number of days
I realized if the user uses the enrollmentconfig API (or whatever it morphs into) to retrieve the agent config later, then the agent config will have the encrypted version of the key embedded and other parts of the system won't know what to do with this - so I fixed that in crypto/key.go by checking if the key needs to be decrypted

@fzdarsky Not sure why I can't reply inline to your comment about the component output encryption so I'll do it here - you have a good point about this. I'd prefer encrypting the key to be opt-out but I can add an option for that.

This new version removes the signername option because there is only one valid signer for this enrollment - so we just generate it for the user. It also does not write anything to a file, instead writing to stdout. We can discuss more tomorrow if needed.

Highlights in the new version:

The output formats are called reference and embedded.  Both print an agent config to stdout. The reference format includes the file paths (can be chosen by the user, default bin/agent/etc/flightctl/certs/) to the agent key and cert, while the embedded format includes that material in the config itself.
The reference type also outputs the key, cert, and ca as files. The embedded type does not write out to files.
-The reference output type can opt in to use encryption for the key saved on disk. The password is read from an env var FCPASS or if this env var is not set it will prompt the user.

This is what the output looks like for a default reference output type:
[lily@fedora flightctl]$ bin/flightctl certificate request -n nameichose
this operation will generate a new ecdsa key pair
creating new key pair...
writing private key to: bin/agent/etc/flightctl/certs/nameichose.key...
submitting CSR to flightctl service...
201 Created: nameichose
checking for certificate...
...
certificate is ready
writing data to bin/agent/etc/flightctl/certs/nameichose.crt...
writing data to bin/agent/etc/flightctl/certs/nameichose-ca-data.crt...
enrollment-service:
  authentication:
    client-certificate-data: bin/agent/etc/flightctl/certs/nameichose.crt
    client-key-data: bin/agent/etc/flightctl/certs/nameichose.key
  enrollment-ui-endpoint: http://localhost:9000
  service:
    certificate-authority-data: LS0tL...
    server: https://agent-api.192.168.0.12.nip.io:7443/
grpc-management-endpoint: grpcs://agent-grpc.192.168.0.12.nip.io:7444

Re: opt-in encryption of the key, as a reference kubernetes does the same as stated here https://kubernetes.io/docs/concepts/configuration/secret/ :
Kubernetes Secrets are, by default, stored unencrypted in the API server's underlying data store (etcd). Anyone with API access can retrieve or modify a Secret, and so can anyone with access to etcd.

However I think it will be good to get some kind of integration with Vault or similar on the roadmap for this purpose.

@lkatalin there is progress!,
although there is something weird... it gets stuck waiting for the csr:
https://github.com/flightctl/flightctl/actions/runs/11162417791/job/31027018516#step:7:1161

An update, the CI keeps failing once I change prepare_agent_config.sh to use the new certificate request command as the output of certificate request uses the enrollmentconfig API structs and these do not match the devicesimulator's Config and AuthInfo structs... for example the API has no field ClientKey, only ClientKeyData. I have to think through how to get these to agree, in order to make this CI change.

Looks like this works, please take a look @mangelajo @fzdarsky

CI was passing until I rebased on main a few times, so I believe the failure is unrelated to this PR.

CI was passing until I rebased on main a few times, so I believe the failure is unrelated to this PR.

I confirm it's unrelated to your change, seems to be in the console, but I cannot see the root cause.

There is something with the E2E console, could be indirectly related, I am running locally to gather more details.
i.e. may be the TLS cert or config obtained from this does not connect correctly to the console grpc endpoint?

🥳

authors: fzdarsky lkatalin mangelajo

repo: flightctl/flightctl


text:
added support for redis connection pools

To solve this issue https://github.com/flippercloud/flipper/issues/609 in a DRY way I simply wrap all the public methods in the existing redis adapter

@jnunemaker could you rerun the failed test?

@j-castellanos Thanks for the PR!
In https://github.com/flippercloud/flipper/pull/826#pullrequestreview-1832444441 I offered a couple suggestions of how I think we should approach connection pool support. I don't really love having different adapters Redis depending on if you're using the client directly or a connection pool. I'd rather see Redis and RedisCache updated to work directly with a client or a pool internally, or add a generic ConnectionPool adapter as attempted in #835.
I don't feel strongly between those two approaches, but I would like to make sure we add connection pool support to both Redis and RedisCache at the same time.
Thoughts?

@bkeepers how is this?

@jnunemaker @bkeepers thoughts on this one?

I don't want to add more methods to Flipper::Adapter. I think I'd just make redis and redis cache work with a client or a pool. That seems like easiest way.
def client(&block)
  # if client, then yield that, if connection pool then call with and yield client
end

# then change all methods that use @client to use client { |c| c.blah... }

We could just abstract a method for getting a client and if adapter was initialized with pool it will use with and a block. If initialize with a client the client would just be used.
I'll make a note to whip something together or anyone else is free to try sooner.

@jnunemaker this wouldn't be adding more methods it just overrides existing ones to set the client if a pool was used to initialize.
However I think solution works as well, are you planning on implementing or would you like me to? The only issue I see is when client gets called multiple times, the pool would continue requesting new clients each time so more refactoring might be needed to ensure that a single method doesn't need multiple connections

authors: bkeepers j-castellanos jnunemaker

repo: flippercloud/flipper


text:
refactor: rename retry policy related property names in config.json

Description:

Testing done:

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

Is this a breaking change?

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2047ed7) 48.32% compared to head (beb429f) 48.33%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff                @@
##           release/v1.2     #107      +/-   ##
================================================
+ Coverage         48.32%   48.33%   +0.01%
================================================
  Files               194      194
  Lines             14667    14667
================================================
+ Hits               7088     7090       +2
+ Misses             7535     7533       -2
  Partials             44       44

Flag
Coverage Δ

unittests
48.33% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter reaver-flomesh

repo: flomesh-io/fsm


text:
fix: virtual machine monitor.

Description:
fix virtual machine monitor.

Testing done:
Done

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Is this a breaking change? no

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)? no

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 12.50000% with 7 lines in your changes missing coverage. Please review.

Please upload report for BASE (release/v1.4@9a19c3e). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

pkg/k8s/client.go
12.50%
7 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff               @@
##             release/v1.4     #602   +/-   ##
===============================================
  Coverage                ?   14.16%
===============================================
  Files                   ?      820
  Lines                   ?    65280
  Branches                ?        0
===============================================
  Hits                    ?     9245
  Misses                  ?    55860
  Partials                ?      175

Flag
Coverage Δ

unittests
14.16% <12.50%> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/lgtm

authors: codecov-commenter cybwan reaver-flomesh


text:
ruby-jmeter doesn't add query parameter in URL when forming Http Post with some raw_body

In jmeter we can't have parameters & body both at same time , instead we can have query parameters in URL path and request body in body field . So it would be like
URL : http://{host}?param1=val1&param2=val2
Body will be of xml/json
I tried to replicate this in ruby-jmeter through following ruby-jmeter snippet
endPoint = "http://google.com?name=sameer&surname=jethvani"
submit name: 'mypostRequest', url: endPoint ,connect_timeout: '400000' ,raw_body: rawJsonBody, response_timeout: '400000' do
header mycustomHeaderArray
end

PS : 'submit' is alias for http post in ruby-jmeter
When I am compiling above snippet in ruby-jmeter , it generates jmeter file & it shows query parameter concatenated with request body & not in URL (which is wrong).
Have a look at generated jmeter scenario

PS : I checked that this is happening when my post request has raw_body & url has query parameters

@90kts this seems to be an issue. parser.rb may require a fix for this . Let me know if you guys need any other information

Not sure if this is related, but the parser does not do json body parsing properly.
https://github.com/flood-io/ruby-jmeter/blob/91d3cad535ac95930c3698e844647f744caa58b6/lib/ruby-jmeter/helpers/parser.rb#L80
From a jmeter generated jmx, the double quotes in a json body should be transform into ".
params[:raw_body].encode(:xml => :text).gsub(/\"/, '"')

This should handle double quotes.

authors: Daniel-ltw sjethvani

repo: flood-io/ruby-jmeter


text:
Support rack-style array params in query strings

Commonly in rack applications, array-like structures will be represented in query param pairs by a repeated name suffixed with square brackets e.g. p[]=a&p[]=b.
ruby-jmeter in its current implementation will only allow the last query param pair of an array set to be added to the resulting jmx file i.e. in the case of e.g. p[]=a&p[]=b, only p[]=b is added as an argument.
My PR modifies the parser to support multiple query param pairs with the same name to be added to the jmx, supporting rack endpoints that require an array structure with multiple values.

Great thanks :+1:

Pushed ruby-jmeter 2.13.3 to rubygems.org.

@90kts You're welcome! Your prompt uploading of the gem is very much appreciated! :dancers:

No worries. Have specs will push :)


text:
Render Problem

I'm getting the following error!
because of which I'm not able to see the preview in Android Studio, but the output can be seen when run on an Android device.
java.lang.IllegalArgumentException: Underflow in restoreToCount - more restores than saves
at android.graphics.Canvas.restoreToCount(Canvas.java:599)
at com.github.florent37.diagonallayout.DiagonalLayout.dispatchDraw(DiagonalLayout.java:295)
at android.view.View.draw(View.java:19024)
at android.view.ViewGroup.drawChild_Original(ViewGroup.java:4256)
at android.view.ViewGroup_Delegate.drawChild(ViewGroup_Delegate.java:63)
at android.view.ViewGroup.drawChild(ViewGroup.java:4256)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4042)
at android.view.View.draw(View.java:19159)
at android.view.View.draw(View.java:19026)
at android.view.ViewGroup.drawChild_Original(ViewGroup.java:4256)
at android.view.ViewGroup_Delegate.drawChild(ViewGroup_Delegate.java:63)
at android.view.ViewGroup.drawChild(ViewGroup.java:4256)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4042)
at android.view.View.draw(View.java:19024)
at android.view.ViewGroup.drawChild_Original(ViewGroup.java:4256)
at android.view.ViewGroup_Delegate.drawChild(ViewGroup_Delegate.java:63)
at android.view.ViewGroup.drawChild(ViewGroup.java:4256)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4042)
at android.view.View.draw(View.java:19159)
at com.android.layoutlib.bridge.impl.RenderSessionImpl.renderAndBuildResult(RenderSessionImpl.java:403)
at com.android.layoutlib.bridge.impl.RenderSessionImpl.renderAndBuildResult(RenderSessionImpl.java:550)
at com.android.layoutlib.bridge.impl.RenderSessionImpl.render(RenderSessionImpl.java:424)
at com.android.layoutlib.bridge.BridgeRenderSession.render(BridgeRenderSession.java:108)
at com.android.ide.common.rendering.api.RenderSession.render(RenderSession.java:154)
at com.android.ide.common.rendering.api.RenderSession.render(RenderSession.java:136)
at com.android.tools.idea.rendering.RenderTask.lambda$renderInner$5(RenderTask.java:760)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Exact same problem. Any solution ?

try with the 1.0.9
compile 'com.github.florent37:diagonallayout:1.0.9'


text:
Sketch missing sections: discussion/outlook

So far we have a drafted introduction and some potential examples on how to use the dataset in teaching.
But there's no discussion/conclusion/outlook section to wrap up.

I added a sketch of this section, needs some editing/reading but that will be a separate issue.


text:
PyPi/Versioning

Can you version this library, or add aa beta tag to the repository so I can addd this as a dependency without risk of it breaking when you develop?
Questions about the libraries timeline.

When will this library be published to PyPI?
When will you start versioning the project?

You can use the commit as a pin. :eyes:

It's up, now! https://pypi.org/project/httpx-sse/0.1.0

authors: Kludex florimondmanca wudstrand

repo: florimondmanca/httpx-sse


text:
Generic highway scenario

Pull request information

Status: Ready to merge
Kind of changes: New scenario & example
Related PR or issue: This branch is created from #666 😈(which fixes a bug with inflows in case they dispatch vehicles that choose their routes non-deterministically)

Description

A new generic highway scenario, with an arbitrary number of on-ramps and off-ramps (it is a more general version of the merge, no-ramp highway or triangle scenarios); and an associated example to run the scenario.
For instance:

The customizable network parameters are as follows:
# lengths
additional_net_params["highway_length"] = 600
additional_net_params["on_ramps_length"] = 65
additional_net_params["off_ramps_length"] = 65

# number of lanes
additional_net_params["highway_lanes"] = 4
additional_net_params["on_ramps_lanes"] = 1
additional_net_params["off_ramps_lanes"] = 1

# speed limits
additional_net_params["highway_speed"] = 15
additional_net_params["on_ramps_speed"] = 10
additional_net_params["off_ramps_speed"] = 10

# ramps
additional_net_params["on_ramps_pos"] = [200, 400]
additional_net_params["off_ramps_pos"] = [300, 500]

# probability of exiting at the next off-ramp
additional_net_params["next_off_ramp_proba"] = 0.05

# inflow rates in vehs/hour
HIGHWAY_INFLOW_RATE = 1000
ON_RAMPS_INFLOW_RATE = 200

(as well as the angle of the ramps which I didn't add yet)
Works nicely, except there's a lot of collisions that interrupt the simulation. It doesn't happen a lot with a one-lane highway and a reduced inflow though. I have no idea how to fix this for the moment, any ideas welcome -- especially specify_connections: did I do it right? (I get warnings "Target lane is already connected...").

Pull Request Test Coverage Report for Build 4071

0 of 115 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.1%) to 90.737%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

examples/sumo/highway_ramps.py
0
35
0.0%

flow/scenarios/highway_ramps.py
0
80
0.0%

Totals

Change from base Build 4067:
-1.1%

Covered Lines:
8669

Relevant Lines:
9554

💛  - Coveralls

authors: coveralls nathanlct

repo: flow-project/flow


text:
Rename platform.counts.projects.suspended to platform.counts.projectsByState.suspended

Fixes #22
Description
Renames the column so that it maps to a JSON structure.

This change has been deployed to the live collector. The field won't get any real data until 1.7 is released and deployed.

repo: flowforge/usage-ping-collector


text:
Two-step upload: how to pick a file first, display the information about it and upload it in the second step?

All the examples demonstrate one-step process for file upload - you pick the file, it starts uploading. I want to implement two-step upload:

user clicks Upload file button and picks the file he wants to upload
system shows the information of the file
3.1) if user is satisfied he clicks Confirm button and the upload to the server starts
3.2) if user picked the wrong file, he clicks Cancel button and the system will not upload anything to the server
3.3) if the file is not valid (e.g. too big size, wrong filename or extension etc), system will not upload it.

moved the question here https://github.com/flowjs/ng-flow/issues/256 because it's really an angular question.


text:
Upload duplicate file with different content

Hi,
I have a problem uploading file with the same name but different content,
it is possible to process file based on filename, extension and filesize not only on filename?
thanks.

It already takes file size into account, or you can generate file id with your own custom function for generateUniqueIdentifier:
https://github.com/flowjs/flow.js/blob/master/src/flow.js#L275

alright!,
It works, we just need to change the file output in the backend.
Thanks :)

repo: flowjs/ng-flow


text:
Add support for listing and downloading web lectures

I based this PR off fluminus, and verified that it works locally.
I'm pretty new to Rust, so let me know if there are better ways of doing anything.
Ref. #60.

From inspecting the network traffic on the LumiNUS frontend, this seems like the easiest way to download web lectures. Interacting with the lti/Launch/panopto endpoint allows us to construct a request to negotiate authentication with Panopto, then we can search for the video URL using the OpenGraph meta tag. If the desire is to download the 2 streams in web lectures separately, I think there's another API we can query after authenticating into Panopto to get the stream URLs, but I didn't do that since that was too much work.

Thanks for the feedback, I think I need to take a more detailed look at the API for Option and Iterator to write more idiomatic code. Will look through this and update in a bit.

Oh, you might need to rebase it since I merged your other PR.

I'll test this tomorrow; sorry—a bit bogged down at the moment...

authors: angelsl bnjmnt4n btzy

repo: fluminurs/fluminurs


text:
Support for Swift Package Manager (PM)

This Feature Request is About
Please choose the closest item by replacing [ ] with [x].

[X ] Integration
[ ] Analytics
[ ] Ads
[ ] Messaging/Push
[ ] IAP
[ ] Flurry Website/Dashboard
[ ] Other

Platform
Please choose the related platform by replace [ ] with [x].

[ X] iOS
[X ] tvOS
[X ] WatchOS

Describe the solution you'd like
With Xcode 11 having integrated support for the Swift Package manager it would make integrating Flurry much easier on Apple platforms if Swift PM was supported.
Describe alternatives you've considered
CocoaPods are a hack and worked ok before Swift PM was integrated natively into Xcode. It is clear that SwiftPM is the future. Will Flurry support it?
Additional context
A "how to" guide on Publishing a Swift Package in Xcode.

@calkinsc3 Thank you for using Flurry Analytics and filing this feature request. We are open to supporting Flurry via Swift Package Manager but currently SPM does not provide support for distributing binary libraries. There is also a recurring request from the wider developer community for Swift to support binary libraries but there is no plan/communication from Swift on when/if binary libraries will be supported.

Thanks for the response. We really enjoy Flurry and the data it produces. I'm assuming we can still statically link to the binaries. I would like to avoid cocoapods if possible. I plan to integrate Flurry in a SwiftUI/Combine app. We'll see how it goes :) Thanks again for a great product!

@calkinsc3 Thank you for the amazing feedback. Let us know how your integration goes. I'll be closing out this ticket but feel free to reopen in case if you any other questions/comments/concerns.

Any chance to reopen this now that the status of the reason for closing has changed?
https://github.com/apple/swift-evolution/blob/master/proposals/0272-swiftpm-binary-dependencies.md

Hello @bainfu, Given Swift 5.3 has added support for distributing binary frameworks as Swift packages, we have actively started looking into providing support for Flurry via SPM. Stay tuned and we will provide an update on when to expect a beta release.

This will be great @rajkaur01 ! Flurry is the last dependancy before we are able to migrate our project to SPM. I hope we have some good news soon.

Can't wait! :)

@p-nicolaou @SocialKitLtd @bainfu @calkinsc3 We have added SPM support for Flurry SDK. Integration instructions for pulling in Flurry as a swift package can be found at https://github.com/flurry/FlurrySwiftPackage Please reach out if you run into any issues.

@rajkaur01 Doing so works, but when trying to access custom user properties (https://developer.yahoo.com/flurry/docs/analytics/userproperties/#swift) and importing FlurryAnlytics results in error:
Compiling for iOS 12.0, but module 'FlurryAds' has a minimum deployment target of iOS 14.0: .../Debug-iphoneos/FlurryAds.swiftmodule/arm64-apple-ios.swiftmodule
Does the package built against iOS 14 only?

@SocialKitLtd - Thanks for this report. I'll get a fix out asap.

The latest version of Flurry is now available as a Swift package here: https://github.com/flurry/FlurrySwiftPackage
This release fixes an issue where the package manifest included the wrong minimum OS version.
Please let us know if you have any issues.

The package runs and builds in the simulator but App Store Connect throws an absolute fit when I try to upload to TestFlight.
Is anyone else running into this?
Should I open an issue here or at https://github.com/flurry/FlurrySwiftPackage?

The package runs and builds in the simulator but App Store Connect throws an absolute fit when I try to upload to TestFlight.
Is anyone else running into this?
Should I open an issue here or at https://github.com/flurry/FlurrySwiftPackage?

@twhq Thank you for reporting the issue. We will look into this and get back to you shortly.

@twhq Thank you for reporting the issue. We will look into this and get back to you shortly.

@rajkaur01 In our case, we are using Flurry analytics only. For that reason, during installation, we did pick FlurryAnalyticsSPM. Doing so, I had to rename import Flurry_iOS_SDK to import FlurryAnalytics. However, now I see Cannot find 'Flurry' in scope. Is this step mandatory for the library to work, https://developer.yahoo.com/flurry/docs/integrateflurry/ios-manual/#swift-sdk-integration? Am I missing anything else?

@rajkaur01 In our case, we are using Flurry analytics only. For that reason, during installation, we did pick FlurryAnalyticsSPM. Doing so, I had to rename import Flurry_iOS_SDK to import FlurryAnalytics. However, now I see Cannot find 'Flurry' in scope. Is this step mandatory for the library to work, https://developer.yahoo.com/flurry/docs/integrateflurry/ios-manual/#swift-sdk-integration? Am I missing anything else?

Hello @p-nicolaou,
Yes you need to create a bridging header. It is a mandatory step.  Inside the bridging header you'll import Flurry.h
Check the Headers folder in the xframework for a list of all headers: https://github.com/flurry/FlurrySwiftPackage/tree/master/artifacts/Flurry.xcframework/ios-armv7_arm64/Headers

Hello @p-nicolaou,
Yes you need to create a bridging header. It is a mandatory step.  Inside the bridging header you'll import Flurry.h
Check the Headers folder in the xframework for a list of all headers: https://github.com/flurry/FlurrySwiftPackage/tree/master/artifacts/Flurry.xcframework/ios-armv7_arm64/Headers

@flurrydev @rajkaur01 https://github.com/flurry/FlurrySwiftPackage/issues/3
Any chance we can get a rebuild w/ the arm64 slice for M1 Macs to run simulators?

The latest release, 11.2.1, has support for M1 Macs and Mac Catalyst.

thanks so much @flurrydev !!

@flurrydev this appears to be broken still. Previous issue was the m1 Mac slice, however now it says it can't find FlurrySessionBuilder. FlurryAnalytics is imported, and the Flurry package is at 11.2.1.

@bsneed You need to create a bridging header and import Flurry.h
Then add SystemConfiguration to the build phases.
For help with the bridging header see here: https://developer.yahoo.com/flurry/docs/integrateflurry/ios-manual/#swift-sdk-integration

authors: SocialKitLtd bainfu bsneed calkinsc3 flurrydev hunterhays p-nicolaou rajkaur01 twhq

repo: flurry/flurry-ios-sdk


text:
Add Tizen 5.0 bindings

#5
Change the reference profile to Iot headed from wearable because the Iot headed profile has more common API set.
Add Tizen 5.0 bindings

import 'package:tizen_interop/5.0/tizen.dart';

Update README.md to provide the supported APIs table.
Cleanup scripts

@WonyoungChoi Yeah, creating a branch in the public repo is usually intended for collaboration, but I thought nobody would like to do so for this work.

@WonyoungChoi Yeah, creating a branch in the public repo is usually intended for collaboration, but I thought nobody would like to do so for this work.

:sob:

authors: WonyoungChoi bwikbs swift-kim