🐛 Firebase/Auth: CocoaPods could not find compatible versions for pod "Firebase/Auth":

Bug report
Describe the bug
Build fails for iOS because of conflicting Pods
Steps to reproduce
Steps to reproduce the behavior:
Use the following dependencies in flutter´s pubspec.yaml
dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  firebase_storage: ^11.0.4
  firebase_auth: ^4.1.1
  cloud_firestore: ^4.0.4

Result: when typing pod install (even with pod repo update)
pod install
Analyzing dependencies
cloud_firestore: Using Firebase SDK version '10.0.0' defined in 'firebase_core'
firebase_auth: Using Firebase SDK version '10.0.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '10.0.0' defined in 'firebase_core'
firebase_storage: Using Firebase SDK version '10.0.0' defined in 'firebase_core'
[!] CocoaPods could not find compatible versions for pod "Firebase/Auth":
In snapshot (Podfile.lock):
Firebase/Auth (= 9.6.0)

In Podfile:
firebase_auth (from `.symlinks/plugins/firebase_auth/ios`) was resolved to 4.1.1, which depends on
Firebase/Auth (= 10.0.0)

You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* changed the constraints of dependency `Firebase/Auth` inside your development pod `firebase_auth`.
  You should run `pod update Firebase/Auth` to apply changes you've made.

Flutter doctor
Run flutter doctor and paste the output below:

doctor --verbose
[✓] Flutter (Channel stable, 3.3.7, on macOS 12.6 21G115 darwin-arm, locale de-DE)
• Flutter version 3.3.7 on channel stable at /Users/cw/dev/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision e99c9c7cd9 (8 days ago), 2022-11-01 16:59:00 -0700
• Engine revision 857bd6b74c
• Dart version 2.18.4
• DevTools version 2.15.0

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
• Android SDK at /Users/cw/Library/Android/sdk
✗ cmdline-tools component is missing
Run `path/to/sdkmanager --install "cmdline-tools;latest"`
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run `flutter doctor --android-licenses` to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 14B47b
• CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.3)
• Android Studio at /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 11.0.13+0-b1751.21-8125866)

[✓] Connected device (3 available)
• iPhone 14 Pro Max (mobile) • 8BDFFE4F-3D13-4EEC-A19B-183BD14881E5 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
• macOS (desktop)            • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
• Chrome (web)               • chrome                               • web-javascript • Google Chrome 107.0.5304.87

[✓] HTTP Host Availability
• All required HTTP hosts are available

! Doctor found issues in 1 category.
Process finished with exit code 0

I have the same error but with firebase database

@Terranic
As the error says:
firebase_auth (from `.symlinks/plugins/firebase_auth/ios`) was resolved to 4.1.1, which depends on
Firebase/Auth (= 10.0.0)

Since you are using firebase_auth 's latest version ie, 4.1.1, it requires iOS sdk version to be 10.0.0. Can you provide your pubspec.yaml ?
Also, try the solutions mentioned in the error message:
You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* changed the constraints of dependency `Firebase/Auth` inside your development pod `firebase_auth`.
  You should run `pod update Firebase/Auth` to apply changes you've made.

Thanks. pod repo update does not help. I think because of this SDK dependency conflict, it is not surprising
my pubspec.yaml
name: tool3
description: A new Flutter project.

# The following line prevents the package from being accidentally published to
# pub.dev using `flutter pub publish`. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 2.4.0+59

environment:
  sdk: ">=2.18.0 <3.0.0"

# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
  flutter:
    sdk: flutter
  flutter_localizations: # Add this line
    sdk: flutter         # Add this line
  google_fonts: ^3.0.1
  email_validator: ^2.1.17
  speech_to_text: ^6.1.0
  wakelock: ^0.6.2
  path_provider: ^2.0.11
  shared_preferences: ^2.0.15
  shimmer: ^2.0.0
  flutter_tts: ^3.6.0
  webfeed: any
  grouped_list: ^5.1.2
  lottie: ^2.0.0
  path: ^1.8.2

  share_plus: ^6.2.0

  json_annotation: ^4.7.0

  #cached_network_image: any

  url_launcher: any

  firebase_storage: ^11.0.4
  firebase_auth: ^4.1.1
  fluttertoast: ^8.1.1
  cloud_firestore: ^4.0.4
  screen_brightness: ^0.2.2

  mobile_scanner: ^2.0.0
  image_picker: ^0.8.6
  uuid: ^3.0.6
  intl: ^0.17.0
  dots_indicator: ^2.1.0
  camera: ^0.10.0+4
  video_player: ^2.4.7
  led_bulb_indicator: ^0.0.1
  fl_chart: ^0.55.2
  flutter_svg: any
  qr_flutter: ^4.0.0
  #font_awesome_flutter: ^10.2.1
  introduction_screen: ^3.0.2

  string_similarity: ^2.0.0
  flutter_typeahead: ^4.1.1
  collection: any

  http: ^0.13.5
  tuple: ^2.0.1
  page_transition: ^2.0.9

  #chewie: ^1.3.4
  geolocator: ^9.0.2
  flex_color_picker: ^2.6.1
  package_info_plus: ^3.0.1
  #assets_audio_player: ^3.0.5

  adaptive_theme: ^3.1.1
  video_compress: ^3.1.1
  geocoding: ^2.0.5
  animations: ^2.0.7

  timeago: ^3.3.0
  auto_size_text: ^3.0.0
  json_path: ^0.4.2
  modal_bottom_sheet: ^2.1.2
  pdf: any
  receive_sharing_intent: ^1.4.5
  google_mlkit_text_recognition: 0.3.0
  flutter_animate: ^2.0.1
  flutter_hooks: ^0.18.5+1
  font_awesome_flutter: ^10.2.1
  badges: ^2.0.3
  cached_network_image: ^3.2.2
  flutter_reaction_button: ^2.0.1+2
  showcaseview: ^2.0.0+1
  flutter_cache_manager: ^3.3.0
  image: ^3.1.3
  crypto: ^3.0.2
  gradient_widgets: ^0.6.0

  flutter_image_compress: ^1.1.3

dev_dependencies:
  flutter_test:
    sdk: flutter

  build_runner: ^2.3.2
  json_serializable: ^6.5.4
  flutter_launcher_icons: ^0.10.0

  pedantic: ^1.11.1
  # test: ^1.21.4

  # The "flutter_lints" package below contains a set of recommended lints to
  # encourage good coding practices. The lint set provided by the package is
  # activated in the `analysis_options.yaml` file located at the root of your
  # package. See that file for information about deactivating specific lint
  # rules and activating additional ones.
  flutter_lints: ^2.0.1

# For information on the generic Dart part of this file, see the
# following page: https://dart.dev/tools/pub/pubspec

# The following section is specific to Flutter packages.
flutter_icons:
  android: "launcher_icon"
  ios: true
  image_path: "assets/images/logo3.png"

flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - assets/images/
    - assets/data/
    - assets/urls/rssfeeds.json
    - assets/media/
    - assets/licenses/
  #  - assets/fonts/

  # An image asset can refer to one or more resolution-specific "variants", see
  # https://flutter.dev/assets-and-images/#resolution-aware

  # For details regarding adding assets from package dependencies, see
  # https://flutter.dev/assets-and-images/#from-packages

  # To add custom fonts to your application, add a fonts section here,
  # in this "flutter" section. Each entry in this list should have a
  # "family" key with the font family name, and a "fonts" key with a
  # list giving the asset and other descriptors for the font. For
  # example:
  fonts:
    - family: Brazilia
      fonts:
        - asset: assets/fonts/Brazilia_Three_CG_Regular.otf
  # fonts:
  #   - family: Schyler
  #     fonts:
  #       - asset: fonts/Schyler-Regular.ttf
  #       - asset: fonts/Schyler-Italic.ttf
  #         style: italic
  #   - family: Trajan Pro
  #     fonts:
  #       - asset: fonts/TrajanPro.ttf
  #       - asset: fonts/TrajanPro_Bold.ttf
  #         weight: 700
  #
  # For details regarding fonts from package dependencies,
  # see https://flutter.dev/custom-fonts/#from-packages

Same error for me, while the targeted ios platform in my Podfile is 13.0.

also flutter pub deps
Dart SDK 2.18.4
Flutter SDK 3.3.8
tool3 2.4.0+59
|-- adaptive_theme 3.1.1
|   |-- flutter...
|   '-- shared_preferences...
|-- animations 2.0.7
|   '-- flutter...
|-- auto_size_text 3.0.0
|   '-- flutter...
|-- badges 2.0.3
|   '-- flutter...
|-- build_runner 2.3.2
|   |-- analyzer 5.2.0
|   |   |-- _fe_analyzer_shared 50.0.0
|   |   |   '-- meta...
|   |   |-- collection...
|   |   |-- convert 3.1.1
|   |   |   '-- typed_data...
|   |   |-- crypto...
|   |   |-- glob...
|   |   |-- meta...
|   |   |-- package_config...
|   |   |-- path...
|   |   |-- pub_semver...
|   |   |-- source_span...
|   |   |-- watcher...
|   |   '-- yaml...
|   |-- args 2.3.1
|   |-- async...
|   |-- build 2.3.1
|   |   |-- analyzer...
|   |   |-- async...
|   |   |-- convert...
|   |   |-- crypto...
|   |   |-- glob...
|   |   |-- logging...
|   |   |-- meta...
|   |   '-- path...
|   |-- build_config 1.1.1
|   |   |-- checked_yaml...
|   |   |-- json_annotation...
|   |   |-- path...
|   |   |-- pubspec_parse...
|   |   '-- yaml...
|   |-- build_daemon 3.1.0
|   |   |-- built_collection 5.1.1
|   |   |-- built_value 8.4.2
|   |   |   |-- built_collection...
|   |   |   |-- collection...
|   |   |   |-- fixnum 1.0.1
|   |   |   '-- meta...
|   |   |-- http_multi_server...
|   |   |-- logging...
|   |   |-- path...
|   |   |-- pool...
|   |   |-- shelf...
|   |   |-- shelf_web_socket...
|   |   |-- stream_transform...
|   |   |-- watcher...
|   |   '-- web_socket_channel...
|   |-- build_resolvers 2.1.0
|   |   |-- analyzer...
|   |   |-- async...
|   |   |-- build...
|   |   |-- crypto...
|   |   |-- graphs...
|   |   |-- logging...
|   |   |-- package_config...
|   |   |-- path...
|   |   |-- pool...
|   |   |-- pub_semver...
|   |   |-- stream_transform...
|   |   '-- yaml...
|   |-- build_runner_core 7.2.7
|   |   |-- async...
|   |   |-- build...
|   |   |-- build_config...
|   |   |-- build_resolvers...
|   |   |-- collection...
|   |   |-- convert...
|   |   |-- crypto...
|   |   |-- glob...
|   |   |-- graphs...
|   |   |-- json_annotation...
|   |   |-- logging...
|   |   |-- meta...
|   |   |-- package_config...
|   |   |-- path...
|   |   |-- pool...
|   |   |-- timing...
|   |   |-- watcher...
|   |   '-- yaml...
|   |-- code_builder 4.3.0
|   |   |-- built_collection...
|   |   |-- built_value...
|   |   |-- collection...
|   |   |-- matcher...
|   |   '-- meta...
|   |-- collection...
|   |-- crypto...
|   |-- dart_style 2.2.4
|   |   |-- analyzer...
|   |   |-- args...
|   |   |-- path...
|   |   |-- pub_semver...
|   |   '-- source_span...
|   |-- frontend_server_client 3.1.0
|   |   |-- async...
|   |   '-- path...
|   |-- glob 2.1.0
|   |   |-- async...
|   |   |-- collection...
|   |   |-- file...
|   |   |-- path...
|   |   '-- string_scanner...
|   |-- graphs 2.2.0
|   |   '-- collection...
|   |-- http_multi_server 3.2.1
|   |   '-- async...
|   |-- io 1.0.3
|   |   |-- meta...
|   |   |-- path...
|   |   '-- string_scanner...
|   |-- js...
|   |-- logging 1.1.0
|   |-- meta...
|   |-- mime...
|   |-- package_config 2.1.0
|   |   '-- path...
|   |-- path...
|   |-- pool 1.5.1
|   |   |-- async...
|   |   '-- stack_trace...
|   |-- pub_semver 2.1.2
|   |   |-- collection...
|   |   '-- meta...
|   |-- pubspec_parse 1.2.1
|   |   |-- checked_yaml...
|   |   |-- collection...
|   |   |-- json_annotation...
|   |   |-- pub_semver...
|   |   '-- yaml...
|   |-- shelf 1.4.0
|   |   |-- async...
|   |   |-- collection...
|   |   |-- http_parser...
|   |   |-- path...
|   |   |-- stack_trace...
|   |   '-- stream_channel...
|   |-- shelf_web_socket 1.0.3
|   |   |-- shelf...
|   |   |-- stream_channel...
|   |   '-- web_socket_channel...
|   |-- stack_trace...
|   |-- stream_transform 2.1.0
|   |-- timing 1.0.0
|   |   '-- json_annotation...
|   |-- watcher 1.0.2
|   |   |-- async...
|   |   '-- path...
|   |-- web_socket_channel 2.2.0
|   |   |-- async...
|   |   |-- crypto...
|   |   '-- stream_channel...
|   '-- yaml 3.1.1
|       |-- collection...
|       |-- source_span...
|       '-- string_scanner...
|-- cached_network_image 3.2.2
|   |-- cached_network_image_platform_interface 2.0.0
|   |   |-- flutter...
|   |   '-- flutter_cache_manager...
|   |-- cached_network_image_web 1.0.2
|   |   |-- cached_network_image_platform_interface...
|   |   |-- flutter...
|   |   '-- flutter_cache_manager...
|   |-- flutter...
|   |-- flutter_cache_manager...
|   '-- octo_image 1.0.2
|       |-- flutter...
|       '-- flutter_blurhash 0.7.0
|           '-- flutter...
|-- camera 0.10.0+4
|   |-- camera_android 0.10.0+4
|   |   |-- camera_platform_interface...
|   |   |-- flutter...
|   |   |-- flutter_plugin_android_lifecycle...
|   |   '-- stream_transform...
|   |-- camera_avfoundation 0.9.8+6
|   |   |-- camera_platform_interface...
|   |   |-- flutter...
|   |   '-- stream_transform...
|   |-- camera_platform_interface 2.3.0
|   |   |-- cross_file...
|   |   |-- flutter...
|   |   |-- plugin_platform_interface...
|   |   '-- stream_transform...
|   |-- camera_web 0.3.0+1
|   |   |-- camera_platform_interface...
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- stream_transform...
|   |-- flutter...
|   |-- flutter_plugin_android_lifecycle 2.0.7
|   |   '-- flutter...
|   '-- quiver 3.1.0
|       '-- matcher...
|-- cloud_firestore 4.0.5
|   |-- cloud_firestore_platform_interface 5.8.5
|   |   |-- _flutterfire_internals...
|   |   |-- collection...
|   |   |-- firebase_core...
|   |   |-- flutter...
|   |   |-- meta...
|   |   '-- plugin_platform_interface...
|   |-- cloud_firestore_web 3.0.5
|   |   |-- _flutterfire_internals...
|   |   |-- cloud_firestore_platform_interface...
|   |   |-- collection...
|   |   |-- firebase_core...
|   |   |-- firebase_core_web...
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- js...
|   |-- collection...
|   |-- firebase_core...
|   |-- firebase_core_platform_interface...
|   |-- flutter...
|   '-- meta...
|-- collection 1.16.0
|-- crypto 3.0.2
|   '-- typed_data 1.3.1
|       '-- collection...
|-- dots_indicator 2.1.0
|   '-- flutter...
|-- email_validator 2.1.17
|-- firebase_auth 4.1.2
|   |-- firebase_auth_platform_interface 6.11.1
|   |   |-- _flutterfire_internals...
|   |   |-- collection...
|   |   |-- firebase_core...
|   |   |-- flutter...
|   |   |-- meta...
|   |   '-- plugin_platform_interface...
|   |-- firebase_auth_web 5.1.2
|   |   |-- firebase_auth_platform_interface...
|   |   |-- firebase_core...
|   |   |-- firebase_core_web...
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   |-- http_parser...
|   |   |-- intl...
|   |   |-- js...
|   |   '-- meta...
|   |-- firebase_core...
|   |-- firebase_core_platform_interface...
|   |-- flutter...
|   '-- meta...
|-- firebase_storage 11.0.5
|   |-- firebase_core 2.2.0
|   |   |-- firebase_core_platform_interface...
|   |   |-- firebase_core_web 2.0.1
|   |   |   |-- firebase_core_platform_interface...
|   |   |   |-- flutter...
|   |   |   |-- flutter_web_plugins...
|   |   |   |-- js...
|   |   |   '-- meta...
|   |   |-- flutter...
|   |   '-- meta...
|   |-- firebase_core_platform_interface 4.5.2
|   |   |-- collection...
|   |   |-- flutter...
|   |   |-- flutter_test...
|   |   |-- meta...
|   |   '-- plugin_platform_interface...
|   |-- firebase_storage_platform_interface 4.1.23
|   |   |-- collection...
|   |   |-- firebase_core...
|   |   |-- flutter...
|   |   |-- meta...
|   |   '-- plugin_platform_interface...
|   |-- firebase_storage_web 3.3.15
|   |   |-- _flutterfire_internals 1.0.8
|   |   |   |-- cloud_firestore_platform_interface...
|   |   |   |-- cloud_firestore_web...
|   |   |   |-- collection...
|   |   |   |-- firebase_core...
|   |   |   |-- firebase_core_platform_interface...
|   |   |   |-- flutter...
|   |   |   '-- meta...
|   |   |-- async...
|   |   |-- firebase_core...
|   |   |-- firebase_core_web...
|   |   |-- firebase_storage_platform_interface...
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   |-- http...
|   |   |-- js...
|   |   '-- meta...
|   '-- flutter...
|-- fl_chart 0.55.2
|   |-- equatable 2.0.5
|   |   |-- collection...
|   |   '-- meta...
|   '-- flutter...
|-- flex_color_picker 2.6.1
|   |-- flex_seed_scheme 1.0.1
|   |   |-- flutter...
|   |   |-- material_color_utilities...
|   |   '-- meta...
|   '-- flutter...
|-- flutter 0.0.0
|   |-- characters 1.2.1
|   |-- collection...
|   |-- material_color_utilities 0.1.5
|   |-- meta 1.8.0
|   |-- sky_engine 0.0.99
|   '-- vector_math 2.1.2
|-- flutter_animate 2.0.1
|   '-- flutter...
|-- flutter_cache_manager 3.3.0
|   |-- clock...
|   |-- collection...
|   |-- file...
|   |-- flutter...
|   |-- http...
|   |-- path...
|   |-- path_provider...
|   |-- pedantic...
|   |-- rxdart 0.27.5
|   |-- sqflite 2.2.0+3
|   |   |-- flutter...
|   |   |-- path...
|   |   '-- sqflite_common 2.4.0+2
|   |       |-- meta...
|   |       |-- path...
|   |       '-- synchronized 3.0.0+3
|   '-- uuid...
|-- flutter_hooks 0.18.5+1
|   '-- flutter...
|-- flutter_image_compress 1.1.3
|   '-- flutter...
|-- flutter_launcher_icons 0.10.0
|   |-- args...
|   |-- checked_yaml 2.0.1
|   |   |-- json_annotation...
|   |   |-- source_span...
|   |   '-- yaml...
|   |-- cli_util 0.3.5
|   |   |-- meta...
|   |   '-- path...
|   |-- image...
|   |-- json_annotation...
|   |-- path...
|   '-- yaml...
|-- flutter_lints 2.0.1
|   '-- lints 2.0.1
|-- flutter_localizations 0.0.0
|   |-- characters...
|   |-- clock 1.1.1
|   |-- collection...
|   |-- flutter...
|   |-- intl...
|   |-- material_color_utilities...
|   |-- meta...
|   |-- path...
|   '-- vector_math...
|-- flutter_reaction_button 2.0.1+2
|   '-- flutter...
|-- flutter_svg 0.23.0+1
|   |-- flutter...
|   |-- meta...
|   |-- path_drawing 0.5.1+1
|   |   |-- flutter...
|   |   |-- meta...
|   |   |-- path_parsing...
|   |   '-- vector_math...
|   |-- vector_math...
|   '-- xml...
|-- flutter_test 0.0.0
|   |-- async...
|   |-- boolean_selector 2.1.0
|   |   |-- source_span...
|   |   '-- string_scanner...
|   |-- characters...
|   |-- clock...
|   |-- collection...
|   |-- fake_async 1.3.1
|   |   |-- clock...
|   |   '-- collection...
|   |-- flutter...
|   |-- matcher 0.12.12
|   |   '-- stack_trace...
|   |-- material_color_utilities...
|   |-- meta...
|   |-- path...
|   |-- source_span 1.9.0
|   |   |-- collection...
|   |   |-- path...
|   |   '-- term_glyph...
|   |-- stack_trace 1.10.0
|   |   '-- path...
|   |-- stream_channel 2.1.0
|   |   '-- async...
|   |-- string_scanner 1.1.1
|   |   '-- source_span...
|   |-- term_glyph 1.2.1
|   |-- test_api 0.4.12
|   |   |-- async...
|   |   |-- boolean_selector...
|   |   |-- collection...
|   |   |-- matcher...
|   |   |-- meta...
|   |   |-- source_span...
|   |   |-- stack_trace...
|   |   |-- stream_channel...
|   |   |-- string_scanner...
|   |   '-- term_glyph...
|   '-- vector_math...
|-- flutter_tts 3.6.0
|   |-- flutter...
|   '-- flutter_web_plugins...
|-- flutter_typeahead 4.1.1
|   |-- flutter...
|   '-- flutter_keyboard_visibility 5.4.0
|       |-- flutter...
|       |-- flutter_keyboard_visibility_linux 1.0.0
|       |   |-- flutter...
|       |   '-- flutter_keyboard_visibility_platform_interface...
|       |-- flutter_keyboard_visibility_macos 1.0.0
|       |   |-- flutter...
|       |   '-- flutter_keyboard_visibility_platform_interface...
|       |-- flutter_keyboard_visibility_platform_interface 2.0.0
|       |   |-- flutter...
|       |   |-- meta...
|       |   '-- plugin_platform_interface...
|       |-- flutter_keyboard_visibility_web 2.0.0
|       |   |-- flutter...
|       |   |-- flutter_keyboard_visibility_platform_interface...
|       |   '-- flutter_web_plugins...
|       |-- flutter_keyboard_visibility_windows 1.0.0
|       |   |-- flutter...
|       |   '-- flutter_keyboard_visibility_platform_interface...
|       '-- meta...
|-- fluttertoast 8.1.1
|   |-- flutter...
|   '-- flutter_web_plugins...
|-- font_awesome_flutter 10.2.1
|   '-- flutter...
|-- geocoding 2.0.5
|   |-- flutter...
|   '-- geocoding_platform_interface 2.0.1
|       |-- flutter...
|       |-- meta...
|       '-- plugin_platform_interface...
|-- geolocator 9.0.2
|   |-- flutter...
|   |-- geolocator_android 4.1.4
|   |   |-- flutter...
|   |   '-- geolocator_platform_interface...
|   |-- geolocator_apple 2.2.3
|   |   |-- flutter...
|   |   '-- geolocator_platform_interface...
|   |-- geolocator_platform_interface 4.0.7
|   |   |-- flutter...
|   |   |-- meta...
|   |   |-- plugin_platform_interface...
|   |   '-- vector_math...
|   |-- geolocator_web 2.1.6
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- geolocator_platform_interface...
|   '-- geolocator_windows 0.1.1
|       |-- flutter...
|       '-- geolocator_platform_interface...
|-- google_fonts 3.0.1
|   |-- crypto...
|   |-- flutter...
|   |-- http...
|   '-- path_provider...
|-- google_mlkit_text_recognition 0.3.0
|   |-- flutter...
|   '-- google_mlkit_commons 0.2.0
|       '-- flutter...
|-- gradient_widgets 0.6.0
|   '-- flutter...
|-- grouped_list 5.1.2
|   '-- flutter...
|-- http 0.13.5
|   |-- async 2.9.0
|   |   |-- collection...
|   |   '-- meta...
|   |-- http_parser 4.0.2
|   |   |-- collection...
|   |   |-- source_span...
|   |   |-- string_scanner...
|   |   '-- typed_data...
|   |-- meta...
|   '-- path...
|-- image 3.1.3
|   |-- archive...
|   |-- meta...
|   '-- xml...
|-- image_picker 0.8.6
|   |-- flutter...
|   |-- image_picker_android 0.8.5+3
|   |   |-- flutter...
|   |   |-- flutter_plugin_android_lifecycle...
|   |   '-- image_picker_platform_interface...
|   |-- image_picker_for_web 2.1.10
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- image_picker_platform_interface...
|   |-- image_picker_ios 0.8.6+1
|   |   |-- flutter...
|   |   '-- image_picker_platform_interface...
|   '-- image_picker_platform_interface 2.6.2
|       |-- cross_file...
|       |-- flutter...
|       |-- http...
|       '-- plugin_platform_interface...
|-- intl 0.17.0
|   |-- clock...
|   '-- path...
|-- introduction_screen 3.0.2
|   |-- collection...
|   |-- dots_indicator...
|   '-- flutter...
|-- json_annotation 4.7.0
|   '-- meta...
|-- json_path 0.4.2
|   |-- petitparser 5.1.0
|   |   '-- meta...
|   '-- rfc_6901 0.1.1
|-- json_serializable 6.5.4
|   |-- analyzer...
|   |-- async...
|   |-- build...
|   |-- build_config...
|   |-- collection...
|   |-- json_annotation...
|   |-- meta...
|   |-- path...
|   |-- pub_semver...
|   |-- pubspec_parse...
|   |-- source_gen 1.2.6
|   |   |-- analyzer...
|   |   |-- async...
|   |   |-- build...
|   |   |-- dart_style...
|   |   |-- glob...
|   |   |-- meta...
|   |   |-- path...
|   |   |-- source_span...
|   |   '-- yaml...
|   '-- source_helper 1.3.3
|       |-- analyzer...
|       |-- collection...
|       '-- source_gen...
|-- led_bulb_indicator 0.0.1
|   '-- flutter...
|-- lottie 2.0.0
|   |-- archive 3.3.2
|   |   |-- crypto...
|   |   '-- path...
|   |-- flutter...
|   |-- path...
|   '-- vector_math...
|-- mobile_scanner 2.0.0
|   |-- flutter...
|   |-- flutter_web_plugins...
|   '-- js...
|-- modal_bottom_sheet 2.1.2
|   '-- flutter...
|-- package_info_plus 3.0.1
|   |-- ffi...
|   |-- flutter...
|   |-- flutter_web_plugins...
|   |-- http...
|   |-- meta...
|   |-- package_info_plus_platform_interface 2.0.1
|   |   |-- flutter...
|   |   |-- meta...
|   |   '-- plugin_platform_interface...
|   |-- path...
|   '-- win32...
|-- page_transition 2.0.9
|   '-- flutter...
|-- path 1.8.2
|-- path_provider 2.0.11
|   |-- flutter...
|   |-- path_provider_android 2.0.21
|   |   |-- flutter...
|   |   '-- path_provider_platform_interface...
|   |-- path_provider_ios 2.0.11
|   |   |-- flutter...
|   |   '-- path_provider_platform_interface...
|   |-- path_provider_linux 2.1.7
|   |   |-- ffi...
|   |   |-- flutter...
|   |   |-- path...
|   |   |-- path_provider_platform_interface...
|   |   '-- xdg_directories 0.2.0+2
|   |       |-- meta...
|   |       |-- path...
|   |       '-- process 4.2.4
|   |           |-- file...
|   |           |-- path...
|   |           '-- platform...
|   |-- path_provider_macos 2.0.6
|   |   |-- flutter...
|   |   '-- path_provider_platform_interface...
|   |-- path_provider_platform_interface 2.0.5
|   |   |-- flutter...
|   |   |-- platform 3.1.0
|   |   '-- plugin_platform_interface...
|   '-- path_provider_windows 2.1.3
|       |-- ffi...
|       |-- flutter...
|       |-- path...
|       |-- path_provider_platform_interface...
|       '-- win32...
|-- pdf 3.6.4
|   |-- archive...
|   |-- barcode 2.1.0
|   |   |-- meta...
|   |   '-- qr...
|   |-- crypto...
|   |-- image...
|   |-- meta...
|   |-- path_parsing 0.2.1
|   |   |-- meta...
|   |   '-- vector_math...
|   |-- vector_math...
|   '-- xml...
|-- pedantic 1.11.1
|-- qr_flutter 4.0.0
|   |-- flutter...
|   '-- qr 2.1.0
|       '-- meta...
|-- receive_sharing_intent 1.4.5
|   '-- flutter...
|-- screen_brightness 0.2.2
|   |-- flutter...
|   |-- screen_brightness_android 0.1.0
|   |   |-- flutter...
|   |   '-- screen_brightness_platform_interface...
|   |-- screen_brightness_ios 0.1.0
|   |   |-- flutter...
|   |   '-- screen_brightness_platform_interface...
|   |-- screen_brightness_macos 0.1.0+1
|   |   |-- flutter...
|   |   '-- screen_brightness_platform_interface...
|   |-- screen_brightness_platform_interface 0.1.0
|   |   |-- flutter...
|   |   '-- plugin_platform_interface...
|   '-- screen_brightness_windows 0.1.1
|       |-- flutter...
|       '-- screen_brightness_platform_interface...
|-- share_plus 6.2.0
|   |-- cross_file 0.3.3+2
|   |   |-- js...
|   |   '-- meta...
|   |-- ffi 2.0.1
|   |-- file 6.1.4
|   |   |-- meta...
|   |   '-- path...
|   |-- flutter...
|   |-- flutter_web_plugins...
|   |-- meta...
|   |-- mime 1.0.2
|   |-- share_plus_platform_interface 3.2.0
|   |   |-- cross_file...
|   |   |-- flutter...
|   |   |-- meta...
|   |   |-- mime...
|   |   |-- path_provider...
|   |   |-- plugin_platform_interface...
|   |   '-- uuid...
|   |-- url_launcher_linux 3.0.1
|   |   |-- flutter...
|   |   '-- url_launcher_platform_interface...
|   |-- url_launcher_platform_interface 2.1.1
|   |   |-- flutter...
|   |   '-- plugin_platform_interface...
|   |-- url_launcher_web 2.0.13
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- url_launcher_platform_interface...
|   |-- url_launcher_windows 3.0.1
|   |   |-- flutter...
|   |   '-- url_launcher_platform_interface...
|   '-- win32 3.1.1
|       '-- ffi...
|-- shared_preferences 2.0.15
|   |-- flutter...
|   |-- shared_preferences_android 2.0.14
|   |   |-- flutter...
|   |   '-- shared_preferences_platform_interface...
|   |-- shared_preferences_ios 2.1.1
|   |   |-- flutter...
|   |   '-- shared_preferences_platform_interface...
|   |-- shared_preferences_linux 2.1.1
|   |   |-- file...
|   |   |-- flutter...
|   |   |-- path...
|   |   |-- path_provider_linux...
|   |   |-- path_provider_platform_interface...
|   |   '-- shared_preferences_platform_interface...
|   |-- shared_preferences_macos 2.0.4
|   |   |-- flutter...
|   |   '-- shared_preferences_platform_interface...
|   |-- shared_preferences_platform_interface 2.1.0
|   |   |-- flutter...
|   |   '-- plugin_platform_interface...
|   |-- shared_preferences_web 2.0.4
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- shared_preferences_platform_interface...
|   '-- shared_preferences_windows 2.1.1
|       |-- file...
|       |-- flutter...
|       |-- path...
|       |-- path_provider_platform_interface...
|       |-- path_provider_windows...
|       '-- shared_preferences_platform_interface...
|-- shimmer 2.0.0
|   '-- flutter...
|-- showcaseview 2.0.0+1
|   '-- flutter...
|-- speech_to_text 6.1.0
|   |-- clock...
|   |-- flutter...
|   |-- flutter_web_plugins 0.0.0
|   |   |-- characters...
|   |   |-- collection...
|   |   |-- flutter...
|   |   |-- js...
|   |   |-- material_color_utilities...
|   |   |-- meta...
|   |   '-- vector_math...
|   |-- js 0.6.4
|   |-- json_annotation...
|   |-- meta...
|   |-- pedantic...
|   |-- speech_to_text_macos 1.0.2
|   |   |-- flutter...
|   |   |-- plugin_platform_interface...
|   |   '-- speech_to_text_platform_interface...
|   '-- speech_to_text_platform_interface 2.0.1
|       |-- flutter...
|       |-- meta...
|       '-- plugin_platform_interface 2.1.3
|           '-- meta...
|-- string_similarity 2.0.0
|-- timeago 3.3.0
|   '-- intl...
|-- tuple 2.0.1
|-- url_launcher 6.1.6
|   |-- flutter...
|   |-- url_launcher_android 6.0.21
|   |   |-- flutter...
|   |   '-- url_launcher_platform_interface...
|   |-- url_launcher_ios 6.0.17
|   |   |-- flutter...
|   |   '-- url_launcher_platform_interface...
|   |-- url_launcher_linux...
|   |-- url_launcher_macos 3.0.1
|   |   |-- flutter...
|   |   '-- url_launcher_platform_interface...
|   |-- url_launcher_platform_interface...
|   |-- url_launcher_web...
|   '-- url_launcher_windows...
|-- uuid 3.0.6
|   '-- crypto...
|-- video_compress 3.1.1
|   '-- flutter...
|-- video_player 2.4.7
|   |-- flutter...
|   |-- html 0.15.1
|   |   |-- csslib 0.17.2
|   |   |   '-- source_span...
|   |   '-- source_span...
|   |-- video_player_android 2.3.9
|   |   |-- flutter...
|   |   '-- video_player_platform_interface...
|   |-- video_player_avfoundation 2.3.7
|   |   |-- flutter...
|   |   '-- video_player_platform_interface...
|   |-- video_player_platform_interface 5.1.4
|   |   |-- flutter...
|   |   '-- plugin_platform_interface...
|   '-- video_player_web 2.0.12
|       |-- flutter...
|       |-- flutter_web_plugins...
|       '-- video_player_platform_interface...
|-- wakelock 0.6.2
|   |-- flutter...
|   |-- meta...
|   |-- wakelock_macos 0.4.0
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   '-- wakelock_platform_interface...
|   |-- wakelock_platform_interface 0.3.0
|   |   |-- flutter...
|   |   '-- meta...
|   |-- wakelock_web 0.4.0
|   |   |-- flutter...
|   |   |-- flutter_web_plugins...
|   |   |-- js...
|   |   '-- wakelock_platform_interface...
|   '-- wakelock_windows 0.2.1
|       |-- flutter...
|       |-- wakelock_platform_interface...
|       '-- win32...
'-- webfeed 0.7.0
    |-- intl...
    '-- xml 5.4.1
        |-- collection...
        |-- meta...
        '-- petitparser...

Thanks for the update. I think this could be happening due to a conflict with external library you are using that depends on firebase_auth. I suggest you to take one external library at a time, try to remove it and see which one could be conflicting.

shouldn´t this be visible when using  flutter pub deps?
When browsing through the dependency tree, there is not other dependency to firebase_auth...

Interestingly, I saw a similar error myself, but for firebase_messaging when after upgrading plugin version from 14.0.4 to 14.1.0, but running pod repo update fixed it for me.
You may try by deleting the podfile.lock if you have it, or recreate podfile itself.

i getting same error , how to fix it

@ajith-acumen in your pod file make sure you have the following https://github.com/firebase/flutterfire/issues/9976#issuecomment-1325534957

The best solution which works in most of these scenarios is the following step:

[x] flutter clean
[x] flutter pub get
[x] cd into the ios folder and then pod deintegrate.
[x] rm Podfile.lock
[x] pod install --repo-update
[x] In 99% of the above cases, the problem will be resolved.

Thank you, no, I already did this. But it did not help.
At some time, it suddenly worked without any change. Therefore I simply assume, the Firebase Core SDK 10 was not yet released as Pod.


Sanitise HTTP message logs

Problem Statement
Styx logs HTTP messages for access logs, errors, warnings and so on. The messages are constructed by toString method, which includes all HTTP fields in verbatim, including sensitive information like security tokens.
Styx needs a configurable mechanism to sanitise the HTTP messages before logging them.
Acceptance Criteria

Remove toString method from HttpRequest, HttpResponse, LiveHttpRequest, LiveHttpResponse, and any possible base classes. This is to prevent developers from logging them accidentally.

Add a "removeCookies" option, that is a list of cookie names, in styx server under request-logging section. Any cookie name in this list gets removed from the logged message output.

    request-logging:
      inbound:
          ...
      outbound:
          ...
      removeCookies:
         - sessionToken
         - anotherToken

TODO: do we need removeHeaders option. Similar to removeCookies above.

The new config is documented in styx end user manual.

The new config option is added to styx config validator, so that it can pick up any invalid configuration.

Hi @fantayeneh and @taer. Please check this bug.
@OwenLindsell could you look into this please?

I would add an option to redact headers and cookies. That will make debugging easy.

I would add an option to redact headers and cookies. That will make debugging easy.

Definitely something we will consider

Almost done on this story.  Will hopefully submit a PR tomorrow.

Fixed


autodoc / autoapi module table of contents is mixed up

When Sphinx autodoc / autoapi creates domentation, the table of contents should group the content by classes, attributes etc. For an unknown reason, when a module contains both classes and attributes, the classes are listed under attributes in the table of contents. This is the case in the current documentation of #88, the module eitprocessing.filters.butterworth_filters. When a module only contains classes, they are listed properly (eitprocessing.binreader or eitprocessing.filters).
This issue persists between themes.
This issue might be related to https://github.com/sphinx-doc/sphinx/issues/11180.

I fixed this with a new config parameter. Maybe this helps as well.
https://github.com/sphinx-doc/sphinx/issues/11180#issuecomment-2271845097


Support git-cmd.exe as git bash shell type in Windows

Context: https://github.com/microsoft/vscode-docs/pull/4066
Repro:
On windows create a keybinding with a when clause of terminalShellType == 'gitbash' and make sure it works when you set git bash as the default shell using the instructions added in https://github.com/microsoft/vscode-docs/pull/4066

Thanks @Tyriar ! Am I correct in my assumption that this will show up in the January 2021 stable release (probably in Feb / Mar 2021)?

Thanks @Tyriar ! Am I correct in my assumption that this will show up in the January 2021 stable release (probably in Feb / Mar 2021)?

@karlhorky yes this won't work until early the stable release that goes out in early Feb. Note that all this really does though is allows you to create git bash-specific keybindings using "when": "terminalShellType == 'gitbash'"

@karlhorky yes this won't work until early the stable release that goes out in early Feb. Note that all this really does though is allows you to create git bash-specific keybindings using "when": "terminalShellType == 'gitbash'"


How to integrate with Bot developed in  C#

🚨 The issue tracker is not for implementation questions 🚨
I am new to REACT App. I am not sure how can I integrate this module with Bot developed in c#. It would be helpful if steps are more detailed and clear, Thanks.

[Question]

The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for submitting bug fixes and feature requests.
That being said, if your bot is C#, then it is hosted either in Azure or On-Prem. The client (Web Chat in this case), does not have to be tied to the bot platform as the whole design of the bot framework is that it uses JSON messages across/between platforms. Please find more info here:
https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0&tabs=csharp
If that does not answer your question, please open an issue on Stack Overflow.


⚠ Bofrost.es has degraded performance

In ee98696, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1419 ms

Resolved: Bofrost.es performance has improved in f66bb9b after 6 minutes.


Consolidate flags into one place

Currently flags are spread about all over different source files. Consolidating in one place will make addition of flags more consistent & prevent accidentally reusing flag names, etc.
As an extra, can we consider switching to pflag (https://github.com/spf13/pflag/), drop in replacement for flag, but POSIX compliant flags & has shorthand flags, etc?

Could even consider viper (https://github.com/spf13/viper) so we can combine flags, env vars & config files into one runtime configuration. As we as more functionality, multiple sinks, events, etc, having a config file might be really useful, in addition to flags, etc.

I like this idea. Most of heapster can act as a library with this change. viper sounds pretty interesting. It should satisfy most of the deployment scenarios.

Think this is closeable note that sources & sinks flags are consolidated.


refactor: merge job-server-slurm to portal-web

This PR merges job-server-slurm back to portal-web for simpler code and deployment.

Codecov Report

Merging #149 (321b98f) into master (4985628) will increase coverage by 4.76%.
The diff coverage is 96.55%.

:exclamation: Current head 321b98f differs from pull request most recent head a6d0c1d. Consider uploading reports for the commit a6d0c1d to get more accurate results

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
+ Coverage   67.81%   72.57%   +4.76%
==========================================
  Files          89       86       -3
  Lines        2361     2166     -195
  Branches      259      241      -18
==========================================
- Hits         1601     1572      -29
+ Misses        727      560     -167
- Partials       33       34       +1

Impacted Files
Coverage Δ

...ps/portal-web/src/clusterops/slurm/bl/submitJob.ts
21.73% <ø> (ø)

apps/portal-web/src/utils/turbovnc.ts
86.20% <83.33%> (ø)

apps/portal-web/src/pages/api/file/copy.ts
78.57% <100.00%> (ø)

apps/portal-web/src/pages/api/file/createFile.ts
83.33% <100.00%> (ø)

apps/portal-web/src/pages/api/file/deleteDir.ts
78.57% <100.00%> (ø)

apps/portal-web/src/pages/api/file/deleteFile.ts
81.25% <100.00%> (ø)

apps/portal-web/src/pages/api/file/download.ts
81.08% <100.00%> (ø)

apps/portal-web/src/pages/api/file/list.ts
88.46% <100.00%> (ø)

apps/portal-web/src/pages/api/file/mkdir.ts
83.33% <100.00%> (ø)

apps/portal-web/src/pages/api/file/move.ts
81.25% <100.00%> (ø)

... and 8 more

Continue to review full report at Codecov.

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


adopt godotenv codebase as a compose-spec component to support .env file according to the spec

prefer PR from original author https://github.com/compose-spec/godotenv/pull/4


⚠ Bofrost.at has degraded performance

In 6957aef, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 977 ms

Resolved: Bofrost.at performance has improved in 1feefcc after 8 minutes.


brat dataset: allow split creation by file ids

Required for the aae2 dataset. This should also fix the sudirectory_mapping: it should map from split names to subdirs and not the other way around.

This is implemented, see https://huggingface.co/datasets/DFKI-SLT/brat/commit/e917db0e43948b9410e5ac209e6fe75066d809fd and https://huggingface.co/datasets/DFKI-SLT/brat/commit/052163d34b4429d81003981bc10674cef54aa0b8.


Add support for PMTiles

@bchapuis Thanks for the great work! Really looking forward to this feature. When will this be released?

In addition, is it possible that I use it directly with JTS geometries instead of always converting from existing vector tiles?

@bchapuis Thanks for the great work! Really looking forward to this feature. When will this be released?

I'd like to start the release process soon, so I hope to have a release by the end of january. Note that, while the demonstration works fine, some small issues remain. For instance, the number of tiles in the metadata does not match the number of actual tiles. If you have experience with this format, any help, like spotting or fixing issues in the codec is welcome (I have no prior experience with this format) 😅

In addition, is it possible that I use it directly with JTS geometries instead of always converting from existing vector tiles?

I'm not sure to fully understand this question. We do have an efficient reader for planet osm based on the Stream API that supports the xml, pbf, and osc formats. Optionnally, this reader can produce JTS geometries. We use it to import the data in postgresql, which is then used to produce the vector tiles. Are you thinking about accessing this Stream of geometries?


Fair end date

Flexibility to use a non-2100 end date for FaIR, which is taken from the last year of the suppled emissions dataframe.

[ ] Tests added
[x] Documentation added
[x] Example added (in the documentation, to an existing notebook, or in a new notebook)
[x] Description in CHANGELOG.rst added (single line such as: (`#XX <https://github.com/openscm/openscm-runner/pull/XX>`_) Added feature which does something)

can you rebase onto https://github.com/openscm/openscm-runner/pull/17 please so we use a more up to date backend (which is way faster)?

can you rebase onto #17 please so we use a more up to date backend (which is way faster)?

Was going to wait until merged into master - is this not imminent?

is this not imminent?

Kind of up to you, it depends on https://github.com/OMS-NetZero/FAIR/pull/83

is this not imminent?

Kind of up to you, #17 depends on OMS-NetZero/FAIR#83

Right that pull 83 is merged, I released as 1.6.0c3, do you want to merge #17 into master or should I rebase this?

Right that pull 83 is merged, I released as 1.6.0c3, do you want to merge #17 into master or should I rebase this?

Great. #17 is merged so please rebase onto master.

Ready to go

Sounds good
On Tue, 22 Sep 2020 at 7:38 pm, chrisroadmap<EMAIL_ADDRESS>wrote:

@chrisroadmap commented on this pull request.

In src/openscm_runner/adapters/fair_adapter/fair_adapter.py
https://github.com/openscm/openscm-runner/pull/18#discussion_r492602283:

@@ -48,17 +48,21 @@ def _make_full_cfgs(self, scenarios, cfgs):  # pylint: disable=R0201

         emissions_pi[8] = 3.8773253867471933

         emissions_pi[9] = 2.097770755

         emissions_pi[10] = 15.44766815

       emissions_pi[11] = 6.92769009144426

       nt = emissions.shape[0]

       # TODO: raise error if nt > 736

Actually let's just delete as an error will be thrown further down the
code and I don't want to complicate the possibility of running sub-yearly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openscm/openscm-runner/pull/18#discussion_r492602283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFUH5G36VEBELVTNWWU7XOLSHBWCFANCNFSM4RM3JC2Q
.


fix(hooks): #82 add hooks to package files

Description

In last update preinstall task added
"preinstall": "cp ./hooks/pre-commit ./.git/hooks/pre-commit",

But file was missing in npm package, so installation failed.

Related Issue

Fixes #82
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] All new and existing tests passed.

I would remove this preinstall, since it's for development only, we don't need npm test for users of this package, plus we don't know where .git is located when someone install this package.

https://github.com/Netcentric/fe-build/tree/main/.github/hooks exists


DELETE /api/user doesn't work according to the swagger documentation

DELETE /api/user doesn't work according to the swagger documentation. The following is the error message:

This is the more current error message:


preload WebView widget in K9.onCreate() to avoid loading time later on

During profiling of MessageViewFragment, I noticed there is a long delay when the first message is displayed since the WebView widget needs to load some native libraries. This must be done on the UI thread and takes more than 250ms on my Nexus 5, which is a quite noticable delay, especially since it interferes with the transition animation.
The rationale here is that when K9 is opened, the user will sooner rather than later view a message, so the time to load the library will be spent on the UI thread somewhere regardless. 250ms of app startup time are some more black screen time, which feels a lot less laggy to me than the same time spent in the transition when first viewing a message.
I realize that Application.onCreate is not a great position to introduce this delay either, so if anyone has a nicer idea where to place this I'd be happy to hear it. Maybe in MessageList?
It might also be a bad idea to do this in the first place, not sure.

The Application class is the wrong place to put this. There are plenty of situations where the Application class is instantiated without a message being displayed. Especially on low end devices it's possible the low-memory killer is regularly removing our process. The app is restarted the next time mail is checked in the background. Loading a WebView every time will make our already bad battery consumption even worse.
An easy fix would be to remove the WebView from the layout and dynamically add it after the transition animation has completed.

Sounds reasonable. I'll fiddle around with it some more and see if I can find a better place.


Activate / Deactivate Task

Hello!
How can I deactivate a Task? I can not find the property to do that.
Thank you for your help and for your work!
Originally posted: 2016-05-12T04:14:23

I don't totally understand what "deactivate " mean.
But Microsoft.Win32.TaskScheduler.Task has a property "Enable", and you can assign false to disable the task.
Is this helpful to solve you problem?
Originally posted: 2016-05-12T19:04:58

Yes! That was. Thank you very much!
Originally posted: 2016-05-13T03:33:42


Brackets 1.10 won't start on macOS Sierra (10.12.5)

Brackets 1.10 won't start on macOS Sierra (10.12.5)

done! this is because of brackets-shizimily-multiencoding,the extension cause that


Minor typo in Section 3.1 of the paper

In Eq. (1), the $H_i ∗ W_i$ terms emerge as the primary computational bottleneck [...]

is probably meant to use \cdot instead of *, i.e.

In Eq. (1), the $H_i \cdot W_i$ terms emerge as the primary computational bottleneck [...]

in Section 3.1 of the paper. Also, there's an

accross

later in the section that contains one superfluous "c".

Hi @chrisoffner, thank you for your interest in our work and for finding those typos! We will include the corrections in the next arXiv update.
Kind regards.


Consider renaming repo or splitting warehouse sub-repo

https://github.com/E3SM-Project/esgfpub/pull/97#issuecomment-1050262215

Another alternative is to separate the warehouse directory from the esgfpub repo in a new e3sm_warehouse repo. I recall Sterling saying like "it probably should be in its own repo but I added it here" or something to that effect.

https://github.com/E3SM-Project/esgfpub/pull/97#issuecomment-1050395831

I am also leaning towards starting a new repo called e3sm_warehouse. I can actually make a copy of this repo as the starting point of the e3sm_warehouse repo, and just delete the /esgfpub directory there. Then we can archive the esgfpub repo if it is no longer being used.
As Jill mentioned, I would make a branch in this repo and continue working as needed (please no more work on master!). There are ways to move branches between repositories: https://stackoverflow.com/questions/34384642/how-to-copy-a-branch-from-one-github-repository-to-another

Hey Tom, I'm in support of splitting warehouse, so that the new-repo, has a cleanly defined goal and more streamlined execution, devOps, structure and docs. Another possibility is to simply rename this repo and also make the structural changes here? The advantage to keep using this repo is that we get to retain all the repo history and issues/PR records. What do you think?

Hi Jill, that's another viable option that would minimize dev disruption and reduce effort compared to splitting repos.
What we can do if we follow this path:

Rename repository to e3sm_warehouse (warehouse is too generic for a Python package name)
Rename modules and directories to e3sm_warehouse
Remove esgfpub directory

This directory will still exist in the Git history, in case we ever need to restore or reference it

I'm thinking that your suggested path is the way forward, but I'll do a bit more research before we finalize this decision.
I'll also make sure to loop @TonyB9000 in.

I will totally agree with whatever you guys decide.  I only need to know when I need to change my routine.  If paths and environments change names, I imagine I will need to adjust.  I may/may-not need to "clone" a new (e3sm_)warehouse, etc.

Hey @rljacob, can you make me an admin for this repo?

Done.

Thanks @rljacob!


fixed flake8 issues

flake8 currently shows these three errors I have left them unchanged as I feel it is much more redable in the current condition...Do you want me to change it??
./test_gitpub.py:17:80: E501 line too long (84 > 79 characters)
./test_gitpub.py:41:80: E501 line too long (82 > 79 characters)
./test_gitpub.py:42:80: E501 line too long (84 > 79 characters)

Great work @ydjainopensource - I have reviewed your PR. Will require some minor changes I guess.

@ydjainopensource : Some places still need some edits. I have added my comments where I could find. Please look at other places too that I might have missed.
Also, change any return (output) to return(output)

@ydjainopensource - What is the update on this?

sorry have my semester exams going on.....couldn't reply earlier....
I have commit rest of the changes...It is however showing my earlier ID don't know why.
Hope this ssorts the issue out.

@ydjainopensource - The tests are still failing.

I havent changed anything in the code...Moreover if I run
cd tests && py.test -v
I get passed in both the tests

@ydjainopensource - Do a git show --pretty="" --name-only acc3016bea99757cc2b66a610bfafc9cb02a807a and you will see the list of files involved in that particular commit. There you will see that you've made changes in build/lib/gitpub/gitpub.py build/lib/samples/most_popular_repo.py and build/lib/samples/most_popular_repo.py
Please remove the changes you've made to these files. It isn't required.
Also, don't worry about travis, it will pass. Just remove your changes from the aforementioned files and I'll merge it right away.
P.S don't forget to pull.

I have reset all files in build/lib/* to commit 1e9c6c8 Hope this closes the issue. Can I give your name as mentor for mid term eval?
Also my registered github Id is ydjain I have confirmed with kwoc admin...sorry for changing it again

@ydjain - awesome job! Thank you for your patience.
And yeah sure, you can give my name as mentor.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

just learning


Create codeql-analysis.yml

Codecov Report

Merging #62 (d9fbdc9) into master (148ec77) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   75.13%   75.13%
=======================================
  Files          10       10
  Lines         370      370
=======================================
  Hits          278      278
  Misses         86       86
  Partials        6        6

Impacted Files
Coverage Δ

client/client.go
100.00% <ø> (ø)

common/ast.go
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


Fix bug in unix-server mode: thread_pool was closed, but task is still not

Task exception was never retrieved
future: <Task finished name='Task-9370' coro=<<async_generator_athrow without __name__>()> exception=AssertionError('not opened')>
Traceback (most recent call last):
  File "/home/user/src/p5/shelleport/_common/asynchronizer.py", line 36, in __aiter__
    try: yield await self.__executor(_next)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
GeneratorExit

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user/src/p5/shelleport/_common/asynchronizer.py", line 39, in __aiter__
    finally: await self.__executor(_generator.close)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/user/src/p5/shelleport/_common/thread_pool.py", line 28, in __call__
    _executor = self.__manipulator.context
                ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/user/src/p5/shelleport/_common/context_manipulator.py", line 14, in context
    assert self.__manager is not None, "not opened"
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: not opened

It happens because top-level generator may not always finished completely after awaiting for aclose. For example, generator might be in state like this: _data = await read(...) before yield _data.
Protecting exported generators with a context manager (_common.asynchronous_tools.generator_controller) will fix it.


NBMiner V39.7?

When will support < NBMiner v.39.7 >?
Thanks!!

I moved to GMiner instead

not support NBminer 40.1   one day 0 blocked.   :(

not support NBminer 40.1 one day 0 blocked. :(

+1


Revert "NH onboarding changes from feedback v3"

Reverts CDCgov/prime-reportstream#2201

No need to revert. Issue was DNS related.


[WIP] MGMT-19208: Use installer data from reconfig secret if present

In order to support IBBF IBIO needs to be able reuse the previously generated data when installing a "new" cluster.
This PR brings forward the crypto data as well as the cluster and infra IDs by reading that data from a saved secret if it exists.
For the IDs, this is done where we would previously have generated new IDs and saved them to the cluster metadata on the ImageClusterInstall. This is then passed down to the installer and used as input when generating the image based install config.
For the crypto data, we split the call to create the ISO into two parts. We now generate new manifest data, then overwrite the crypto fields in the manifest on the filesystem, then generate the final ISO which will now have both the correct IDs and crypto data.
Looking for an initial review, but leaving this as WIP since I still haven't actually tested it live.

/test e2e-ibio

/test e2e-ibio

/test e2e-ibio

/test e2e-ibio

/test e2e-ibio

/test e2e-ibio

Closing this as this approach won't actually work.
The initial run to generate the base reconfig structure will create new auth an a state file for the installer which will end up being used instead of our crypto.
It would be better to create the first seed reconfig using a temp work dir (ideally just in memory), overlay our crypto from the secret onto that, then write just what we need into the workdir (which won't include the image based, and install configs).
Because this is significantly different from the initial install flow I'm going to close this and make them completely different functions based on the existence of the crypto secrets (kubeconfig, kubeadminpassword, and reconfig).


isRemotePluginReferenceAllowed judges reference permission of plugin and referrer incorrectly

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
In the original specification, if a service A in namespace ns refers to plugin B in ns2, there should be a ReferenceGrant in ns2 to allow reference from namespace ns1 and group/kind of A to group/kind (and maybe name) of B: https://gateway-api.sigs.k8s.io/api-types/referencegrant/.
Actually, if we create a ReferenceGrant in namespace ns1 and allow reference from ns1 and group/kind of A to group/kind of B, the reference check in isRemotePluginReferenceAllowed passes. While we create it in ns2, the check fails.
Expected Behavior
The reference permission check should pass when the ReferenceGrant is created in the namespace of the plugin.
Steps To Reproduce
1. Create a service or an ingress in namespace foo:
apiVersion: v1
kind: Service
metadata:
  namespace: foo
  name: service-foo
  annotations:
    konghq.com/plugins: bar:plugin
...
2. Create a plugin in namespace bar:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  namespace: bar
  name: plugin-bar
...
3. Create a ReferenceGrant in namespace bar (plugin's namespace):
apiVersion: gateway.networking.k8s.io
kind: ReferenceGrant
metadata:
  name: bar
  namespace: bar
spec:
  from:
  - group: ""
    kind: Service
    namespace: foo
  to:
  - group: "configuration.konghq.com"
    kind: KongPlugin

The plugin cannot be attached to the service. If we create the ReferenceGrant in namespace foo, the plugin can be attached.

Kong Ingress Controller version
3.2.2

Kubernetes version
Not releavant

Anything else?
No response

Can be also reproduced by adding a unit test in internal/dataplane/kongstate/kongstate_test.go :
func TestIsRemotePluginReferenceAllowed(t *testing.T) {
	var (
		serviceTypeMeta = metav1.TypeMeta{
			Kind: "Service",
		}
	)

	testCases := []struct {
		name            string
		referrer        client.Object
		pluginNamespace string
		pluginName      string
		referenceGrants []*gatewayapi.ReferenceGrant
		shouldAllow     bool
	}{
		{
			name: "have reference grant",
			referrer: &corev1.Service{
				TypeMeta: serviceTypeMeta,
				ObjectMeta: metav1.ObjectMeta{
					Namespace: "foo",
					Name:      "service-foo",
				},
			},
			pluginNamespace: "bar",
			pluginName:      "plugin-bar",
			referenceGrants: []*gatewayapi.ReferenceGrant{
				{
					ObjectMeta: metav1.ObjectMeta{
						Namespace: "bar", // same namespace as plugin
						Name:      "grant-1",
					},
					Spec: gatewayapi.ReferenceGrantSpec{
						From: []gatewayapi.ReferenceGrantFrom{
							{
								Kind:      gatewayapi.Kind("Service"),
								Namespace: "foo",
							},
						},
						To: []gatewayapi.ReferenceGrantTo{
							{
								Group: gatewayapi.Group(kongv1.GroupVersion.Group),
								Kind:  gatewayapi.Kind("KongPlugin"),
							},
						},
					},
				},
			},
			shouldAllow: true,
		},
	}

	for _, tc := range testCases {
		t.Run(tc.name, func(t *testing.T) {
			s, err := store.NewFakeStore(store.FakeObjects{
				ReferenceGrants: tc.referenceGrants,
			})
			require.NoError(t, err)
			err = isRemotePluginReferenceAllowed(s, pluginReference{
				Referer:   tc.referrer,
				Namespace: tc.pluginNamespace,
				Name:      tc.pluginName,
			})
			if tc.shouldAllow {
				require.NoError(t, err)
			} else {
				require.Error(t, err)
			}
		})
	}
}

More cases about consumer:
If we change the To part of created ReferenceGrant in integration test case to TestPluginCrossNamespaceReference to the following:
					// Totally irrelevant to KongPlugin CRD
					Group: gatewayapi.Group("konghq.com"),
					Kind:  gatewayapi.Kind("Kong"),

The test case still passes while there  is no ReferenceGrant grants reference from KongConsumer to KongPlugin.
While if there is no ReferneceGrant about the Kongconsumer, the access to ingress returns 401 (Is this expected? @rainest )

AFAICT TestPluginCrossNamespaceReference just wasn't really testing the expected behavior with the grant in place. However, I wasn't investigating the details of the test itself--I was instead trying to use the test resources to build documentation and found that it wasn't doing what it should via manual testing of the same resources.
The 401 seems off though--that'd imply the credential isn't recognized, which shouldn't be change. The auth plugin should run regardless of the grant's presence or a functioning grant implementation--it's a traditional same-namespace plugin--and will execute before request-termination, so even if something added or removed the request-termination plugin from the configuration the auth plugin should return the same result.
Added some commentary in https://github.com/Kong/kubernetes-ingress-controller/pull/6295#issuecomment-2219295447 also.


Security concern about Windows binary (v2.23.0)

Describe the bug
Want to first clarify that I believe this is a false positive but still wanted to bring it to the attention of the maintainers. When I tried to download the archive for this via Firefox I got a warning which prompted me to run it through virustotal which is flagging it for a multiple reasons -- all of which I don't fully understand not being familiar with the code.
Here's the report: https://www.virustotal.com/gui/file/be1c45308c479db5d0ef6db49eefdbd41c2dbe543027807909e180b49fec2f0e
Edit: updated description
To Reproduce
NA
Expected behavior
NA
Screenshots
NA
Versions:

Version: 2.23.0
OS: NA
Shell Version: NA

Additional context
Here's what I tested
archive file:
Name: navi-v2.23.0-x86_64-pc-windows-gnu.zip
Size: 2611933 bytes (2550 KiB)
SHA256: 97539b0aa149c60dee1315d90e9339d84fb33ec80311b6d3c85aac07e5f22f22
executable:
Name: navi.exe
Size: 5172488 bytes (5051 KiB)
SHA256: be1c45308c479db5d0ef6db49eefdbd41c2dbe543027807909e180b49fec2f0e
VirusTotal report: https://www.virustotal.com/gui/file/be1c45308c479db5d0ef6db49eefdbd41c2dbe543027807909e180b49fec2f0e
I looked through the code base and build pipeline it looks like upx is being used to compress the binary: https://github.com/denisidoro/navi/actions/runs/7156992883/job/19487333651#step:5:208 and I'm thinking that might be making the bin more suspicious to scanners. I found a similar issue for another rust project: https://github.com/svenstaro/miniserve/issues/1210#issuecomment-1694579204 and even a pinned issue for upx itself: https://github.com/upx/upx/issues/437
These are pretty small binaries so I just wonder how much larger it would be without running it through upx and if that would remove some of the warnings?

I can disable upx for Windows :)

Here's a report from Hybrid Analysis for version 2.23.0.


skip and avoid-contracts seem to not be working.

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.0.2 (01f61ff 2024-05-11T00:24:53.177450000Z)
What command(s) is the bug in?
forge build
Operating System
macOS (Intel)
Describe the bug
forge init

Update Counter.t.sol to not be compileable. Maybe with something like this:
    function setUp() public {
        hello
    }

then, run this:
RUST_LOG=debug forge build --skip Counter.t.sol --zksync

It will incorrectly try to compile the contract we are skipping. Without the --zksync flag, it works fine.

@PatrickAlphaC I will look to reproduce, it seems to be working for me at first glance.

@PatrickAlphaC you will need to use the following command:
RUST_LOG=debug forge build --skip Counter.t.sol --avoid-contracts Counter.t.sol --zksync

We intend to consolidate skip and avoid-contracts in a future release.


Use u-boot recipe from meta-sunxi layer

Signed-off-by: Sebastian Panceac<EMAIL_ADDRESS>

@spanceac what is the reasoning for switching to the meta-sunxi uboot? It misses quiet a lot of the patches we would need for many of the H3 and H5 device types we would want to add.


[chore] Enable remaining lint rules and fix lots of bugs

Why
Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests.
How
How did you build this feature or fix this bug and why?
Test Plan
Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2510  👈
#2509
#2508
#2507
#2505 : 1 other dependent PR (#2506 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @wschurman and the rest of your teammates on  Graphite

Merge activity

Aug 21, 12:11 PM EDT: @wschurman started a stack merge that includes this pull request via Graphite.


How to reload Quartz?

I was wondering would it be possible to reload Quartz?
When I make a change on the file, Quartz automatically can reloads itself. Would it be possible to achieve this by simply calling a function, based on if I faced with an error?
I have found related solution but which was not helpful
__ http://stackoverflow.com/questions/27723287/reload-python-flask-server-by-function
__ https://gist.github.com/nguyenkims/ff0c0c52b6a15ddd16832c562f2cae1d

I found a simple solution, sorry open and close this issue.
How following in your Python code in order to kill the server,:
@app.route('/quit')
def _quit():
    os._exit(0)

When it triggers it kills the on-going process, which it will repeat itself in the while loop.
app_run.sh:
#!/bin/bash

while true
do
    hypercorn app_async:app -b <IP_ADDRESS>:5000 # --reload
    sleep 1
done


ci: Publishing and downloading flank scripts

Fixes #1347
flank-scripts is now published to JFrog Bintray [1], so instead of building flank-scripts each time when running some workflow on GitHub actions or when you need it, you could just download it using simple gradle task[2].
flank-scripts support now versioning, so there is a requirement to update its version each time you changed some files inside flank-scripts directory, otherwise, detekt task will fail[3].
Each GitHub actions workflow is updated to download latest version instead of building flank-scripts to save time and resources.[4]
Test Plan

How do we know the code works?

[1]

Run gradlew :flank-scripts:bintrayUpload (bintray account needed)
Flank scripts should be updated on bintray

[2]

Run gradlew :flank-scripts:download
flankScripts.jar should be downloaded to flank-scripts/bash

[3]

Change some files under flank-scripts
Run gradlew check or gradlew detekt
Gradle task should failed
Update version in flank-scripts/build.gradle.kts
Run gradlew check or gradlew detekt
Gradle task should succeed

[4]

Check if all workflows has replaced

- name: Gradle Build flankScripts and add it to PATH
        run: |
          ./flank-scripts/bash/buildFlankScripts.sh
          echo "./flank-scripts/bash" >> $GITHUB_PATH

to
- name: Download flankScripts and add it to PATH
        run: |
          ./gradlew :flank-scripts:download
          echo "./flank-scripts/bash" >> $GITHUB_PATH

Checklist

[x] Publish Flank-scripts to JFrog Bintray
[x] Create Github workflow which will make it after each push to master
[x] Create task to download latest version from JFrog Bintray
[x] Replace Github actions Workflow building to downloading flank-scripts
[ ] Add method to prevent merging flank-scripts without version update

Codecov Report

Merging #1361 (18ac289) into master (23b269b) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1361      +/-   ##
============================================
+ Coverage     77.81%   77.83%   +0.02%
  Complexity      705      705
============================================
  Files           244      244
  Lines          4693     4693
  Branches        901      901
============================================
+ Hits           3652     3653       +1
  Misses          550      550
+ Partials        491      490       -1


Option to check whether the issue already exists on the project

Create an option called ignore-if-already-exists or something more aptly named.

When set to true, it would check the board to see if the issue has already been added to it, and if so, it would complete successfully without any further actions.
When set to false, it would check the board to see if the issue has already been added to it, and if so, the workflow fails with a clear message stating the issue already exists.

Currently what happens is that the workflow fails with an uninformative "Validation Failed" error in a situation where the issue already exists on the board.
Use case:
Users use the project board to create a new issue, so on creation, the issue can already be on the board.

@c00 check out #14


Property '__scanOCR' doesn't exist

Hi,
i am trying to get start with video-camera-ocr project, but with no luck. When I wan't to use scanOCR(frame) function, I always get error: Property '__scanOCR' doesn't exist. I am using yarn to install.
versions:
iOS: 16.0.3
xCode: 14.0.1

my dependencies:
"react-native": "0.70.3",
"react-native-reanimated": "^2.11.0",
"react-native-vision-camera": "^2.15.1",
"vision-camera-ocr": "^1.0.0",

my babel.config.js:
module.exports = {
    presets: ['module:metro-react-native-babel-preset'],
    plugins: [
        [
            'react-native-reanimated/plugin',
            {
                globals: ['__scanOCR', '__labelImage', ],
            },
        ],
    ],
}

Whole error:
Property '__scanOCR' doesn't exist

ReferenceError: Property '__scanOCR' doesn't exist
    at scanOCR (/Users/Developer/test/node_modules/vision-camera-ocr/src/index.tsx (49:7):1:33)
    at scanOCR (native)
    at _f (/Users/Developer/test/components/ScanScreen.js (36:45):1:77)
    at _f (native)
    at _f (/Users/Developer/test/node_modules/react-native-vision-camera/src/hooks/useFrameProcessor.ts (28:21):1:425)
    at _f (native)

reanimated::REAIOSErrorHandler::raiseSpec()
    REAIOSErrorHandler.mm:18
reanimated::ErrorHandler::raise()::'lambda'()::operator()()
decltype(static_cast<reanimated::ErrorHandler::raise()::'lambda'()&>(fp)()) std::__1::__invoke<reanimated::ErrorHandler::raise()::'lambda'()&>(reanimated::ErrorHandler::raise()::'lambda'()&)
void std::__1::__invoke_void_return_wrapper<void, true>::__call<reanimated::ErrorHandler::raise()::'lambda'()&>(reanimated::ErrorHandler::raise()::'lambda'()&)
std::__1::__function::__alloc_func<reanimated::ErrorHandler::raise()::'lambda'(), std::__1::allocator<reanimated::ErrorHandler::raise()::'lambda'()>, void ()>::operator()()
std::__1::__function::__func<reanimated::ErrorHandler::raise()::'lambda'(), std::__1::allocator<reanimated::ErrorHandler::raise()::'lambda'()>, void ()>::operator()()
std::__1::__function::__value_func<void ()>::operator()() const
std::__1::function<void ()>::operator()() const
invocation function for block in vision::VisionCameraScheduler::scheduleOnUI(std::__1::function<void ()>)
C663D847-B94F-3FB0-9254-32EDBC55315E
C663D847-B94F-3FB0-9254-32EDBC55315E
C663D847-B94F-3FB0-9254-32EDBC55315E
C663D847-B94F-3FB0-9254-32EDBC55315E
C663D847-B94F-3FB0-9254-32EDBC55315E
_pthread_wqthread
start_wqthread

I tried just clone example from this repository, same problem...
I tried other preprocessors (for example Image labeler and it's OK).
Thank you.

did you you try running this command?
react-native start -- --resetCache

Yes, many times 🙂 I tried just clone example project, run it with npm, yarn..no luck...maybe it is cause by XCode version (14.0.1). I've read many other forums where they describe a similar error and some have been helped by downgrading Xcode to version 13. But I haven't tried this.

So I figured it up. It seems it isn't fault of this package but problem of the Vision camera package and Xcode version 14. One workaround could be downgrade Xcode to version 13. Or you can follow this thread.
In Xcode workspace, find FrameProcessorPlugin.h file and replace line 56:
__attribute__((constructor)) static void VISION_CONCAT(initialize_, objc_name)()    \
with
+(void)load                                                                        \
Built project, it works 🙂


Change the divider size depending not only on the position but also on the content?

Hi there,
Is there a way of changing the divider size depending not only on the position but also on the content?
In my case, my adapter extends from a CursorRecyclerAdapter and depending on the position content I set a different view type.
    @Override
    public int getItemViewType(int position) {
        if (mDataValid && mCursor != null && mCursor.moveToPosition(position)) {
            String cursorUid = mCursor.getString(mCursor.getColumnIndex(ChatProvider.COL_FROM_UID));
            String previousUid = "";
            if (!mCursor.isFirst()) {
                mCursor.moveToPrevious();
                previousUid = mCursor.getString(mCursor.getColumnIndex(ChatProvider.COL_FROM_UID));
                mCursor.moveToNext();
            }

            if (cursorUid.equals(uid))
                return VIEW_TYPE_ME;
            else if (previousUid.equals(cursorUid))
                return VIEW_TYPE_OTHERS_BIS;
            else
                return VIEW_TYPE_OTHERS;

        }
        return 0;
    }

My problem is that I set the adapter to the recyclerview when the cursor is loaded inside the onLoadFinished method of the CursorLoader and the "dividerSize" method seems to get called before the cursor is loaded setting the default divider to all items.
@Override
    public int dividerSize(int position, RecyclerView parent) {
        switch (getItemViewType(position)) {
            case VIEW_TYPE_ME:
                Utils.convertDpToPixel(context.getResources().getDimension(R.dimen.divider_chat_normal), context);
                break;

            case VIEW_TYPE_OTHERS:
                Utils.convertDpToPixel(context.getResources().getDimension(R.dimen.divider_chat_normal), context);
                break;

            case VIEW_TYPE_OTHERS_BIS:
                Utils.convertDpToPixel(context.getResources().getDimension(R.dimen.divider_chat_bis), context);
                break;
        }
        return Utils.convertDpToPixel(context.getResources().getDimension(R.dimen.divider_chat_normal), context);
    }

I've tried to call addItemDecoration after the data is loaded into the cursor with no luck.
   @Override
    public void onLoadFinished(Loader<Cursor> loader, Cursor data) {
        messagesChatAdapter.swapCursor(data);
        recyclerView.scrollToPosition(messagesChatAdapter.getItemCount() - 1);
        recyclerView.addItemDecoration(new HorizontalDividerItemDecoration.Builder(getActivity())
                .sizeProvider(messagesChatAdapter)
                .color(android.R.color.transparent)
                .build());
    }

@MrBrightside29
how about calling notifyItemDataSetChanged in onLoadFinished?

My recyclerView swapCursor method already calls notifyItemDataSetChanged and swapCursor is being called in onLoadFinished with no difference.
public Cursor swapCursor(Cursor newCursor) {
        if (newCursor == mCursor) {
            return null;
        }
        Cursor oldCursor = mCursor;
        mCursor = newCursor;
        if (newCursor != null) {
            mRowIDColumn = newCursor.getColumnIndexOrThrow("_id");
            mDataValid = true;
            // notify the observers about the new cursor
            notifyDataSetChanged();
        } else {
            mRowIDColumn = -1;
            mDataValid = false;
            // notify the observers about the lack of a data set
            notifyItemRangeRemoved(0, getItemCount());
        }
        return oldCursor;
    }

I believe dividerSize should be called when notifyDataSetChanged is called.
So, please check if dividerSize is called after swapCursor is executed.

It was a silly mistake. I missed the return statement inside each case of the switch as can see.
Sorry for making you lose time and thanks for your help.


feat(#775): now we see one a question at a time

Closes #775

Summary by CodeRabbit

New Feature: Enhanced the FAQ section with an interactive accordion feature. Users can now click on a question to view the answer, providing a more streamlined and intuitive experience.
Refactor: Updated the data source for FAQs, improving the ease of updating and managing FAQ content.
Chore: Improved code quality and maintainability by enforcing commit message standards using a commit linter. This ensures more readable and consistent commit messages, aiding team collaboration.

Hey there @AliReza1083, can you check your Linting issues here? There seems to be an error.

I am doing it but I keep getting the same issues.

@AliReza1083  @tobySolutions I am closing this


Added maxPinnedRemoteVideoTiles prop to VideoGallery to disable pin menu button

What

Added maxPinnedRemoteVideoTiles prop to VideoGallery.
Disabling pin menu button on remote VideoTile of VideoGallery when max pinned remote video tiles is reached
Added enzyme tests for pinned participants enzyme tests including those that test prop maxPinnedRemoteVideoTiles
Added 1 hermetic playwright tests to test that CallComposite will limit max pinned remote video tiles to 4
Added a revision to API View for Pinned Participants here: https://apiview.dev/Assemblies/Review/7276a0d82fce4755b833fc91def19dbc/8a35753f996445c28156396635624f28?diffRevisionId=80605558e3ea4faa8acc2db2edb2e3fa&doc=False&diffOnly=True

Why

https://skype.visualstudio.com/SPOOL/_workitems/edit/3043119
https://skype.visualstudio.com/SPOOL/_workitems/edit/3050025
https://skype.visualstudio.com/SPOOL/_workitems/edit/3045927
https://skype.visualstudio.com/SPOOL/_workitems/edit/3050071
How Tested

Local calling sample, storybook, and through enzyme tests and 1 playwright test
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

LGTM! Just waiting for green CI before approving. Added update_snapshots label to get snapshots of the new e2e test

I actually worry about disabling the button - it's not clear to the user why it's disabled and how they can go about fixing that, can you check in with design on this?

nit: the pin icon doesn't quite have the correct padding around it, the text is closer to the pin than the pin is to the left hand side:

nit: the pin icon doesn't quite have the correct padding around it, the text is closer to the pin than the pin is to the left hand side:
I think the snapshot you saw might have been outdated because the margins look fine to me.

I looked at the margins on storybook and they seem ok as well.

Going by the latest snapshot update the horizontal margins are still a little off (by ~30% depending on resolution), and the vertical direction isn't center aligned:

^ The icon should be vertically centered with the text and not bottom-aligned?
I see the same issue in storybook:

For reference this is what Teams' looks like:

Icon alignment is tricky (fluent icons aren't the best). Happy to defer to design and have them sign off or not on if this is an acceptable level of alignment

Going by the latest snapshot update the horizontal margins are still a little off (by ~30% depending on resolution), and the vertical direction isn't center aligned:  ^ The icon should be vertically centered with the text and not bottom-aligned?
I see the same issue in storybook:
For reference this is what Teams' looks like (notice the pin icon extends ~the same amount above and below the P in Pin):
Icon alignment is tricky (fluent icons aren't the best). Happy to defer to design and have them sign off or not on if this is an acceptable level of alignment

I was able to change the icon size so that the icon is vertically aligned with the menu text. But there is now a little more space on the right side due that natural padding of the span element which is what is the menu text is.

. Let me know if I should file a bug to fix this. Thanks.

I actually worry about disabling the button - it's not clear to the user why it's disabled and how they can go about fixing that, can you check in with design on this?

Talked with Alex P and we are now indicating that the limit is reached. Please see updated snapshot.

was able to change the icon size so that the icon is vertically aligned with the menu text

The icon in the snapshot is still not vertically centered:


chore(structure/dev-tools): Structure updated and dev tools improved (gulp, rollup, build)

Use of jvandemo/generator-angular2-library as base tools
Use of gulp as build system
Inline html/css templates using ludohenin/gulp-inline-ng2-template
Build with rollup (flat ESM)
Cleaner dist and build proccess
Lib directory cleaned
Use of angular's codelyzer and better TSLint rules
demos are out

Once it is merged, to publish a new version, run:

change ng2-inline-editor version in package.json
npm i or yarn
npm run build or yarn build
npm run publish

Great like ever! :-)


golang.org/x/tools/gopls master branch introduce a breaking change

As vscode-go lock the gopls at<EMAIL_ADDRESS>The master branch breaks the existing installation.
Detail
https://github.com/microsoft/vscode-go/issues/2886

See previously https://github.com/golang/go/issues/34076#issuecomment-527931145.


Slidebox with scroll inside is too sensitive

there is a slidebox with scroll content in each slide. then the slidebox is too sensitive on device (OK in browser), sometimes i actually want to scroll the content but missed to change the slide pages.
it seems sometimes when i put my finger, for the first pixel, the delta.x = delta.y = 0, then the touch move takes it as change slide pages.
this could be fixed by add following code (unsure about the impact)
if (delta.x == 0 && delta.y == 0) {
return;
}
in touchmove: function (event) after
delta = {
x: touches.pageX - start.x,
y: touches.pageY - start.y
};

Greetings @ghostgrass!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Can you try the new slidebox?
<ion-slides>
  <ion-slide-page>
    <ion-content>

Shoudl fix it for you


Analyze and improve data query performance in Dynamics 365 (online), version 9.x

The above is no longer applicable in Dynamics 365 (online), version 9.x. The menu option is still visible but no optimizations can be created/deleted.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aaf5b280-7935-de15-c98e-6feba636e79b
Version Independent ID: 97594869-bde7-f551-3b90-2c4a5e3e6693
Content: Analyze and improve data query performance for Dynamics 365 Customer Engagement
Content Source: ce/admin/analyze-improve-data-query-performance.md
Service: crm-online
GitHub Login: @Mattp123
Microsoft Alias: matp

Is this feature available or has thing been killed in v9?

Killed in v9.

@PaulFearn what are you basing this on? Where did you get this information?

Based on my experience and also talking to Microsoft Fasttrack.
Try logging onto a v8 365 Org and you will see this option presents optimisations but on a v9 365 Org no optimisations are presented.
Microsoft is working towards a solution for self tuning 365 Orgs.

@PaulFearn & @MattNC
The document says 'Notice that out-of-box and custom entity queries that complete within three seconds aren't displayed in the view.'. Seems like if you don't have any queries that exceed this time duration, they won't appear?
I've asked @Mattp123 to consider making this item of information easier to find b/c it seems possible that this is being misinterpreted.

Thanks @JimDaly So it sounds like this feature is still part of v9 then, but perhaps v9 performance has improved so it is less likely to see entities that require optimization.

No more performance problems!

Thanks for the update Jim. That's helpful to know! Is there any documentation on the underlying architecture changes that obviated the need for this sort of perf tuning?

On Nov 29, 2018, at 4:24 AM, Jim Daly<EMAIL_ADDRESS>wrote:
What I've heard from hallway conversations is that this doesn't apply any longer. @PaulFearn is correct.
@Mattp123 & @mayadumesh can you get this document updated and close this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Azure SQL provides many new capabilities for keeping index up-to-date and healthy. We are using those to allow for better detection and reconciliation of slow running queries. There is also ongoing effort to improve platform functionality around performance that looks at the creating and maintaining indexes. Both of the above working better than feature in question.
Thanks
Maya
From: Jim Daly<EMAIL_ADDRESS>Sent: Sunday, December 2, 2018 1:29 PM
To: MicrosoftDocs/dynamics-365-customer-engagement<EMAIL_ADDRESS>Cc: Maya Dumesh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Analyze and improve data query performance in Dynamics 365 (online), version 9.x (#254)
This isn’t my area of expertise, so I don’t want to speculate about the reasons or what kind of documentation will be provided. @Mattp123 & @mayadumesh are the best sources to comment.
From: MattNC <notifications<EMAIL_ADDRESS>Sent: Sunday, December 2, 2018 9:15 AM
To: MicrosoftDocs/dynamics-365-customer-engagement <dynamics-365-customer-engagement<EMAIL_ADDRESS>Cc: Jim Daly <Jim.Daly<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Analyze and improve data query performance in Dynamics 365 (online), version 9.x (#254)
Thanks for the update Jim. That's helpful to know! Is there any documentation on the underlying architecture changes that obviated the need for this sort of perf tuning?

On Nov 29, 2018, at 4:24 AM, Jim Daly <notifications<EMAIL_ADDRESS>wrote:
What I've heard from hallway conversations is that this doesn't apply any longer. @PaulFearn is correct.
@Mattp123 & @mayadumesh can you get this document updated and close this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F254%23issuecomment-443523846&data=02|01|jim.daly%40microsoft.com|d20e424edd85435d31b308d65879b1aa|72f988bf86f141af91ab2d7cd011db47|1|0|636793677032315353&sdata=2rBvsoDhx%2Fp81ka%2FgBRwiG31MaSMSXg4p8KAGxQVc4g%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGDzSCiEc77-uoj3VXk_EHne9wxcDnI0ks5u1AqUgaJpZM4WaU0A&data=02|01|jim.daly%40microsoft.com|d20e424edd85435d31b308d65879b1aa|72f988bf86f141af91ab2d7cd011db47|1|0|636793677032325363&sdata=eItqgZafXm1nTMHyY%2Bco492%2FuMQoQO0%2BqgDlEf0TORQ%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F254%23issuecomment-443543889&data=02|01|Maya.Dumesh%40microsoft.com|19d20833e87f4b8bb1e608d6589d3920|72f988bf86f141af91ab2d7cd011db47|1|0|636793829623700549&sdata=1RJtRZ9Hfzzt3TqWHaF%2Fohax04VsN6wpVl5xGg8jI54%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAiIbWdpvfWkqIE8_2c1j81dxN4aOyOr_ks5u1EYvgaJpZM4WaU0A&data=02|01|Maya.Dumesh%40microsoft.com|19d20833e87f4b8bb1e608d6589d3920|72f988bf86f141af91ab2d7cd011db47|1|0|636793829623710554&sdata=ndnX1SAyQxTJONMxL%2BQ4DUg4oXZGcF3QBt7ZVMJG4wM%3D&reserved=0.


[TrapFocus] Restore focus issue

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior
Modal component when pressing escape, focus is not being correctly restored to clicked element. Clicked element is an IconButton wrapped in a Tooltip.
Focus does not trigger expected highlighting of button and tooltip popup. Moving to a different tab and moving back to the page restores focus as expected.
Expected Behavior
Focus should be restored with a highlighted button and open Tooltip.
Steps to Reproduce
https://codesandbox.io/s/modal-focus-issue-ge4pr?fontsize=14&hidenavigation=1&theme=dark

Open either modal
Press escape

Alternate:
1.Open either modal
2. Press escape
3. Change tab and change back
Your Environment
Using Typescript and Hooks but clearly exists with vanillajs

Confirmed, I remember looking at this issue in the past. I couldn't understand exactly what was going on. From what I recall, the focus event wasn't firing, leading to a wrong focus visible style. Introducing a setTimeout in the .focus() call was solving the problem. In any case, the DOM focus is handled correctly, the UI feedback is not.

Thanks for looking into the issue quickly. Currently switched to using the Dialog component which restores focus correctly.

We need to entangle what you mean by "focus not being returned". There are two levels of focus that are relevant here: visible focus and (standard) focus.
The standard focus is behaving as expected (otherwise please include the operating system you are using i.e. do you use a mac or not).
What I see is not behaving as expected is visible focus. Even when only operating the codesandbox with a keyboard the the visible focus is not returned to the button (it is focused though). If I switch tabs it does get visibly focused though.
It seems like an issue with the tooltip integration. Should be possible to write an integration test using Button, Modal and Tooltip and debug what's happening.

I agree this is an issue with "visible focus" rather than focus being returned to the element. However it doesn't seem to be a tooltip issue.
I have duplicated a button on the sandbox linked above and removed the Tooltip wrapper and the issue still exists.

@ljones-i-nexus , please look at screenshot below and confirm, that I understand correctly

@fyodore82 Correct, the actual element is in focus after pressing ESC, but the focus is not visible.

This comment https://github.com/facebook/react/issues/17894#issuecomment-656094405 suggest that the observed
bug here will be fixed in React 17.

This bug is fixed in React 17.0.0 https://codesandbox.io/s/o6isx?file=/demo.tsx. It's definitely broken in React 16.14.0 https://codesandbox.io/s/basicmodal-material-demo-forked-g3y2p.
The documentation will no longer showcase the problem once we migrate the version of React we use. For now, our docs still have the issue: https://next--material-ui.netlify.app/components/modal/#basic-modal.

@eps1lon Should we close it now, or wait for the docs to upgrade to use React 17?

We first have to revisit what the plan is regarding supported React versions. I've been pushing for a single version from the beginning but you've always wanted to support multiple versions.
Is this still your opinion or have you reconsidered after realizing that supporting older versions also means supporting buggier React versions?

We first have to revisit what the plan is regarding supported React versions.

@eps1lon What do you think about upgrading the dev dependencies to React 17, and keep the current peer dependency scope for React?

accepting React 16.8 in the peer dependency comes with almost no cost (we can systematically tell developers to upgrade if the bug is outside of our control). No need to run tests with it.

It is a huge cost right now.

It is a huge cost right now.

@eps1lon In this case, I'm missing context. What cost do you have in mind? I can only think of one:
Developers raising something not working with 16.8 and us telling them: it's fixed with React 17.0, upgrade. This can create some support overhead for us. But developers would likely raise it anyway regardless of what or peer dependencies say (I'm pretty sure they most ignore this). It would also harm a bit the trust in the project, depending on what level of expectations developers have for when we say we support older versions of React.

Now that we have<EMAIL_ADDRESS>as a peer dependency, I believe we can close this. I've checked the original sandbox, and I can no longer reproduce the bug, as the latest version of react is this one.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit e0b0a3e:
:clock10: Full build: the average full build time is 6 min(s) 6 sec(s), this is based on the last 468 build(s) for this repository.

Docs Build status updates of commit e0b0a3e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Documentation?

Nice new little app. But it is not clear what the app can be used for apart from writing some text and if there is supposed to be a preview to the right or some other (hidden) features or settings?

This is merely the YunoHost's package of the app, I guess your question is better suited for the upstream repo of the app: https://github.com/Stylix58/codepad

I partly disagree. The person who packaged the app for Yunohost did so for a reason. From a user perspective I would expect some words about why this app is useful or even cool. The detailed documentation will have to be provided at the upstream repro, of course. In this case, the documentation is lacking there as well. and this was the reason I opened this issue.

Sorry... I don't really work on this app these days. But I will try to fix this later.


Fix TextFields breaking on MacOS

Code introduced in #134554 caused TextFields to break on certain conditions, only reproducible on MacOS.
Closes: #143270
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

fly-by comment from triage: Could you please add a test so we don't break this again in the future. Also, it looks like this is failing some existing tests. Can you take a look at those and address those failures?


Added support for campaign groups (i.e. campaign segments and recipients)

Fixes #16, Fixes #18
Can now read and write campaigns with segments or grouping conditions.

Updated pull request to address a NullPointerException that would occur when the Mailchimp API returns an empty response body.
Also added support to send test emails for a campaign.

Thanks for this pull request, it enriches the library functionality a lot. I am not as fast as you implementing all your new features into the new Unirest style, so please bear with me.


[BUG] AttributeError: module 'graphscope' has no attribute 'nx'

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1、安装好graphscopeK8S集群，执行报错：
import graphscope
import graphscope.nx as nx
graphscope.set_option(show_log=False)
2、报错信息:
AttributeError: module 'graphscope' has no attribute 'nx'
Environment (please complete the following information):

Helm中 chart中 appVersion: 0.9.0

Additional context
Add any other context about the problem here.

hi, @superad, the bug has been fixed by commit e3c6c83, you  can update the graphscope-client to the commit and try again.

related pr: https://github.com/alibaba/GraphScope/pull/1123

@lidongze0629 could you update the pip as v0.9.1 to fix this?

@superad  You can upgrade  the latest version by pip3 install graphscope-client==0.9.0 --force-reinstall  and try again

ok,it's works!

Just as a note here:
The different behavior between Python 3.6 and Python 3.7 is caused by https://github.com/python/cpython/pull/1264, which is to solve https://github.com/python/cpython/issues/74210.
Indeed, this change has been documented in the changelog of Python 3.7:

Circular imports involving absolute imports with binding a submodule to a name are now supported. (Contributed by Serhiy Storchaka in bpo-30024.)