Fail to debug on a simulator, showing error about building for iOS Simulator, but linking in object file built for iOS, file 'xxx' for architecture arm64, but it can debug on a physical device

I cannot debug iOS on the simulator(iPhone 8 Mobile) after upgrading Flutter to latest version, 2.5.3, on MacOS, saying the following error:
But It work well when I was debugging the same app on a physical device, my iPhone.

console error log

    ld: in /Users/mac/Downloads/test5/ios/Pods/WechatOpenSDK/OpenSDK<IP_ADDRESS>/libWeChatSDK.a(WechatAuthSDK.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/mac/Downloads/test5/ios/Pods/WechatOpenSDK/OpenSDK<IP_ADDRESS>/libWeChatSDK.a' for architecture arm64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Constructing build description
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'sqlite3' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'Aspects' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'WechatOpenSDK' from project 'Pods')

Could not build the application for the simulator.
Error launching application on iPhone 8.

In order to simplify the work for you to figure it out, I only include these following packages in pubspec.yaml, the same error on the simulator occurred as well
dependencies:
  flutter:
    sdk: flutter
  moor: ^3.4.0
  moor_ffi: ^0.8.0
  provider: ^6.0.1
  path_provider: ^1.3.0
  cloudbase_core: ^0.0.9
  cloudbase_auth: ^0.0.14
  cloudbase_storage: ^0.0.3
  cloudbase_database: ^0.0.12+2

dev_dependencies:
  flutter_test:
    sdk: flutter
  build_runner: ^1.10.0
  moor_generator: ^3.4.0

---- By the way,  the following is the result of flutter doctor ----
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.5.3, on Mac OS X 10.15.7 19H1419 darwin-x64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    ✗ 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
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] VS Code (version 1.62.0)
[✓] Connected device (5 available)

@jims57
From your log, it's failing due to:
ld: in /Users/mac/Downloads/test5/ios/Pods/WechatOpenSDK/OpenSDK<IP_ADDRESS>/libWeChatSDK.a(WechatAuthSDK.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/mac/Downloads/test5/ios/Pods/WechatOpenSDK/OpenSDK<IP_ADDRESS>/libWeChatSDK.a' for architecture arm64
indicating the third party SDK you are using WechatOpenSDK/OpenSDK<IP_ADDRESS> may not be supporting arm64 simulators. Can you confirm if that SDK you are using is latest one ?
Also, provide the entire verbose log in properly formatted text in a text file along with ios/podfile ?
You may also try once by switching to latest master and see if it works for you.

@darshankawar Thank you for your support.
Here is my verbose log:
my.log
This is the  podfile:
# Uncomment this line to define a global platform for your project
platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}.  Becuase I am using stable channel, I suppose stable channel is a channel more stable and fully tested by Flutter team and should be used by most of developers.

@jims57
You are correct. That is just to confirm if the possible fix has made it into stable or not from master.

@jims57
I looked at the verbose log again and as pointed out earlier, it seems to be failing and pointing to third party sdk you are using WechatOpenSDK/OpenSDK<IP_ADDRESS> which may not be supporting apps to run on arm64 simulators and hence the issue. As a workaround, you can try adding below line in ios/podfile inside post_install do |installer| which hopefully should get rid of the error:
 config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
Also, for the main-cause, you'll need to reach out in third party's sdk repo to know if they support arm64 simulator or not.
I am going ahead and closing this as a third-party issue. If you disagree, write in comments and I'll reopen it.
Thanks.

As a workaround, you can try adding below line in ios/podfile inside post_install do |installer| which hopefully should get rid of the error:
 config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'

@darshankawar  I tried the way you suggested like this:
post_install do |installer|
  config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

But it showed error, like this:

Click to expand to see detail
Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Finding Podfile changes
  - Flutter
  - app_tracking_transparency
  - cloudbase_auth
  - connectivity
  - device_info
  - flutter_image_compress
  - flutter_is_emulator
  - flutter_webview_plugin
  - gallery_saver
  - image_picker
  - keyboard_utils
  - multi_image_picker
  - package_info
  - path_provider
  - shared_preferences
  - sqlite3_flutter_libs
  - store_redirect
  - umeng_common_sdk
  - url_launcher

Fetching external sources
-> Fetching podspec for `Flutter` from `Flutter`
-> Fetching podspec for `app_tracking_transparency` from `.symlinks/plugins/app_tracking_transparency/ios`
-> Fetching podspec for `cloudbase_auth` from `.symlinks/plugins/cloudbase_auth/ios`
-> Fetching podspec for `connectivity` from `.symlinks/plugins/connectivity/ios`
-> Fetching podspec for `device_info` from `.symlinks/plugins/device_info/ios`
-> Fetching podspec for `flutter_image_compress` from `.symlinks/plugins/flutter_image_compress/ios`
-> Fetching podspec for `flutter_is_emulator` from `.symlinks/plugins/flutter_is_emulator/ios`
-> Fetching podspec for `flutter_webview_plugin` from `.symlinks/plugins/flutter_webview_plugin/ios`
-> Fetching podspec for `gallery_saver` from `.symlinks/plugins/gallery_saver/ios`
-> Fetching podspec for `image_picker` from `.symlinks/plugins/image_picker/ios`
-> Fetching podspec for `keyboard_utils` from `.symlinks/plugins/keyboard_utils/ios`
-> Fetching podspec for `multi_image_picker` from `.symlinks/plugins/multi_image_picker/ios`
-> Fetching podspec for `package_info` from `.symlinks/plugins/package_info/ios`
-> Fetching podspec for `path_provider` from `.symlinks/plugins/path_provider/ios`
-> Fetching podspec for `shared_preferences` from `.symlinks/plugins/shared_preferences/ios`
-> Fetching podspec for `sqlite3_flutter_libs` from `.symlinks/plugins/sqlite3_flutter_libs/ios`
-> Fetching podspec for `store_redirect` from `.symlinks/plugins/store_redirect/ios`
-> Fetching podspec for `umeng_common_sdk` from `.symlinks/plugins/umeng_common_sdk/ios`
-> Fetching podspec for `url_launcher` from `.symlinks/plugins/url_launcher/ios`

Resolving dependencies of `Podfile`
  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_f_f_3.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/f/f/3/WechatOpenSDK/<IP_ADDRESS>/WechatOpenSDK.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_f_2_0.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/f/2/0/Aspects/1.4.1/Aspects.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_c_7_9.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/c/7/9/Reachability/3.2/Reachability.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_5_d_c.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/5/d/c/Mantle/2.1.6/Mantle.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_1_1_7.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/1/7/SDWebImage/5.12.1/SDWebImage.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_e_9_d.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/e/9/d/SDWebImageWebPCoder/0.8.4/SDWebImageWebPCoder.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_7_e_0.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/7/e/0/BSImagePicker/3.3.1/BSImagePicker.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_d_c_2.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_b_c_6.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/c/6/UMCommon/7.3.5/UMCommon.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_3_1_e.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/3/1/e/UMDevice/2.0.5/UMDevice.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/1/7/SDWebImage/5.12.1/SDWebImage.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/1/7/SDWebImage/5.12.1/SDWebImage.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/7/e/0/BSImagePicker/2.10.3/BSImagePicker.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_4_b_c.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/4/b/c/BSImageView/1.0.3/BSImageView.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_b_f_6.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/f/6/BSGridCollectionViewLayout/1.2.5/BSGridCollectionViewLayout.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/f/6/BSGridCollectionViewLayout/1.2.5/BSGridCollectionViewLayout.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/5/d/c/Mantle/2.1.6/Mantle.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/5/d/c/Mantle/2.1.6/Mantle.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/f/f/3/WechatOpenSDK/<IP_ADDRESS>/WechatOpenSDK.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/f/2/0/Aspects/1.4.1/Aspects.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/c/6/UMCommon/7.3.5/UMCommon.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/e/9/d/SDWebImageWebPCoder/0.8.4/SDWebImageWebPCoder.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/1/7/SDWebImage/5.12.1/SDWebImage.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_1_9_2.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/9/2/libwebp/1.2.1/libwebp.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/4/b/c/BSImageView/1.0.3/BSImageView.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/c/7/9/Reachability/3.2/Reachability.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/3/1/e/UMDevice/2.0.5/UMDevice.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/d/c/2/sqlite3/3.36.0/sqlite3.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/9/2/libwebp/1.2.1/libwebp.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/9/2/libwebp/1.2.1/libwebp.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/9/2/libwebp/1.2.1/libwebp.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/1/9/2/libwebp/1.2.1/libwebp.podspec.json exists! Returning local because checking is only performed in repo update

Comparing resolved specification to the sandbox manifest
  A Aspects
  A BSGridCollectionViewLayout
  A BSImagePicker
  A BSImageView
  A Flutter
  A Mantle
  A Reachability
  A SDWebImage
  A SDWebImageWebPCoder
  A UMCommon
  A UMDevice
  A WechatOpenSDK
  A app_tracking_transparency
  A cloudbase_auth
  A connectivity
  A device_info
  A flutter_image_compress
  A flutter_is_emulator
  A flutter_webview_plugin
  A gallery_saver
  A image_picker
  A keyboard_utils
  A libwebp
  A multi_image_picker
  A package_info
  A path_provider
  A shared_preferences
  A sqlite3
  A sqlite3_flutter_libs
  A store_redirect
  A umeng_common_sdk
  A url_launcher

Downloading dependencies

-> Installing Aspects (1.4.1)
  > Copying Aspects from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/Aspects/1.4.1-7595b` to `Pods/Aspects`

-> Installing BSGridCollectionViewLayout (1.2.5)
  > Copying BSGridCollectionViewLayout from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/BSGridCollectionViewLayout/1.2.5-333dc` to `Pods/BSGridCollectionViewLayout`

-> Installing BSImagePicker (2.10.3)
  > Copying BSImagePicker from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/BSImagePicker/2.10.3-07404` to `Pods/BSImagePicker`

-> Installing BSImageView (1.0.3)
  > Copying BSImageView from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/BSImageView/1.0.3-a1494` to `Pods/BSImageView`

-> Installing Flutter (1.0.0)

-> Installing Mantle (2.1.6)
  > Copying Mantle from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/Mantle/2.1.6-4c0ed` to `Pods/Mantle`

-> Installing Reachability (3.2)
  > Copying Reachability from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/Reachability/3.2-33e18` to `Pods/Reachability`

-> Installing SDWebImage (5.12.1)
  > Copying SDWebImage from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/SDWebImage/5.12.1-4dc3e` to `Pods/SDWebImage`

-> Installing SDWebImageWebPCoder (0.8.4)
  > Copying SDWebImageWebPCoder from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/SDWebImageWebPCoder/0.8.4-f9301` to `Pods/SDWebImageWebPCoder`

-> Installing UMCommon (7.3.5)
  > Copying UMCommon from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/UMCommon/7.3.5-ab4d8` to `Pods/UMCommon`

-> Installing UMDevice (2.0.5)
  > Copying UMDevice from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/UMDevice/2.0.5-c13bb` to `Pods/UMDevice`

-> Installing WechatOpenSDK (<IP_ADDRESS>)
  > Copying WechatOpenSDK from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/WechatOpenSDK/<IP_ADDRESS>-6a4d1` to `Pods/WechatOpenSDK`

-> Installing app_tracking_transparency (0.0.1)

-> Installing cloudbase_auth (0.0.1)

-> Installing connectivity (0.0.1)

-> Installing device_info (0.0.1)

-> Installing flutter_image_compress (0.0.1)

-> Installing flutter_is_emulator (0.0.1)

-> Installing flutter_webview_plugin (0.0.1)

-> Installing gallery_saver (0.0.1)

-> Installing image_picker (0.0.1)

-> Installing keyboard_utils (0.0.1)

-> Installing libwebp (1.2.1)
  > Copying libwebp from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/libwebp/1.2.1-98a37` to `Pods/libwebp`

-> Installing multi_image_picker (4.8.00)

-> Installing package_info (0.0.1)

-> Installing path_provider (0.0.1)

-> Installing shared_preferences (0.0.1)

-> Installing sqlite3 (3.36.0)
  > Copying sqlite3 from `/Users/mac/Library/Caches/CocoaPods/Pods/Release/sqlite3/3.36.0-797b1` to `Pods/sqlite3`

-> Installing sqlite3_flutter_libs (0.0.1)

-> Installing store_redirect (0.0.1)

-> Installing umeng_common_sdk (0.0.1)

-> Installing url_launcher (0.0.1)
  - Running pre install hooks
  - Running pre integrate hooks

Generating Pods project
  - Creating Pods project
  - Installing files into Pods project
    - Adding source files
    - Adding frameworks
    - Adding libraries
    - Adding resources
    - Adding development pod helper files
    - Linking headers
  - Installing Pod Targets
    - Installing target `Aspects` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/Aspects/Aspects.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Aspects/Aspects-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/Aspects/Aspects-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/Aspects/Aspects-dummy.m`
    - Installing target `BSGridCollectionViewLayout` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/BSGridCollectionViewLayout/BSGridCollectionViewLayout.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/BSGridCollectionViewLayout/BSGridCollectionViewLayout-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/BSGridCollectionViewLayout/BSGridCollectionViewLayout-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/BSGridCollectionViewLayout/BSGridCollectionViewLayout-dummy.m`
    - Installing target `BSImagePicker` iOS 9.0
      - Generating Info.plist file at `Pods/Target Support Files/BSImagePicker/ResourceBundle-BSImagePicker-BSImagePicker-Info.plist`
      - Generating module map file at `Pods/Target Support Files/BSImagePicker/BSImagePicker.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/BSImagePicker/BSImagePicker-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/BSImagePicker/BSImagePicker-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/BSImagePicker/BSImagePicker-dummy.m`
    - Installing target `BSImageView` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/BSImageView/BSImageView.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/BSImageView/BSImageView-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/BSImageView/BSImageView-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/BSImageView/BSImageView-dummy.m`
    - Installing target `Flutter` iOS 9.0
    - Installing target `Mantle` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/Mantle/Mantle.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Mantle/Mantle-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/Mantle/Mantle-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/Mantle/Mantle-dummy.m`
    - Installing target `Reachability` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/Reachability/Reachability.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Reachability/Reachability-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/Reachability/Reachability-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/Reachability/Reachability-dummy.m`
    - Installing target `SDWebImage` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/SDWebImage/SDWebImage.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/SDWebImage/SDWebImage-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/SDWebImage/SDWebImage-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/SDWebImage/SDWebImage-dummy.m`
    - Installing target `SDWebImageWebPCoder` iOS 9.0
      - Copying module map file to `Pods/Target Support Files/SDWebImageWebPCoder/SDWebImageWebPCoder.modulemap`
      - Generating Info.plist file at `Pods/Target Support Files/SDWebImageWebPCoder/SDWebImageWebPCoder-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/SDWebImageWebPCoder/SDWebImageWebPCoder-dummy.m`
    - Installing target `UMCommon` iOS 8.0
    - Installing target `UMDevice` iOS 8.0
    - Installing target `WechatOpenSDK` iOS 8.0
    - Installing target `app_tracking_transparency` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/app_tracking_transparency/app_tracking_transparency.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/app_tracking_transparency/app_tracking_transparency-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/app_tracking_transparency/app_tracking_transparency-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/app_tracking_transparency/app_tracking_transparency-dummy.m`
    - Installing target `cloudbase_auth` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/cloudbase_auth/cloudbase_auth.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/cloudbase_auth/cloudbase_auth-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/cloudbase_auth/cloudbase_auth-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/cloudbase_auth/cloudbase_auth-dummy.m`
    - Installing target `connectivity` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/connectivity/connectivity.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/connectivity/connectivity-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/connectivity/connectivity-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/connectivity/connectivity-dummy.m`
    - Installing target `device_info` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/device_info/device_info.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/device_info/device_info-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/device_info/device_info-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/device_info/device_info-dummy.m`
    - Installing target `flutter_image_compress` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/flutter_image_compress/flutter_image_compress.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/flutter_image_compress/flutter_image_compress-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/flutter_image_compress/flutter_image_compress-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/flutter_image_compress/flutter_image_compress-dummy.m`
    - Installing target `flutter_is_emulator` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/flutter_is_emulator/flutter_is_emulator.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/flutter_is_emulator/flutter_is_emulator-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/flutter_is_emulator/flutter_is_emulator-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/flutter_is_emulator/flutter_is_emulator-dummy.m`
    - Installing target `flutter_webview_plugin` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/flutter_webview_plugin/flutter_webview_plugin.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/flutter_webview_plugin/flutter_webview_plugin-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/flutter_webview_plugin/flutter_webview_plugin-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/flutter_webview_plugin/flutter_webview_plugin-dummy.m`
    - Installing target `gallery_saver` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/gallery_saver/gallery_saver.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/gallery_saver/gallery_saver-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/gallery_saver/gallery_saver-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/gallery_saver/gallery_saver-dummy.m`
    - Installing target `image_picker` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/image_picker/image_picker.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/image_picker/image_picker-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/image_picker/image_picker-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/image_picker/image_picker-dummy.m`
    - Installing target `keyboard_utils` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/keyboard_utils/keyboard_utils.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/keyboard_utils/keyboard_utils-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/keyboard_utils/keyboard_utils-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/keyboard_utils/keyboard_utils-dummy.m`
    - Installing target `libwebp` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/libwebp/libwebp.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/libwebp/libwebp-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/libwebp/libwebp-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/libwebp/libwebp-dummy.m`
    - Installing target `multi_image_picker` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/multi_image_picker/multi_image_picker.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/multi_image_picker/multi_image_picker-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/multi_image_picker/multi_image_picker-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/multi_image_picker/multi_image_picker-dummy.m`
    - Installing target `package_info` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/package_info/package_info.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/package_info/package_info-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/package_info/package_info-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/package_info/package_info-dummy.m`
    - Installing target `path_provider` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/path_provider/path_provider.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/path_provider/path_provider-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/path_provider/path_provider-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/path_provider/path_provider-dummy.m`
    - Installing target `shared_preferences` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/shared_preferences/shared_preferences.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/shared_preferences/shared_preferences-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/shared_preferences/shared_preferences-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/shared_preferences/shared_preferences-dummy.m`
    - Installing target `sqlite3` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/sqlite3/sqlite3.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/sqlite3/sqlite3-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/sqlite3/sqlite3-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/sqlite3/sqlite3-dummy.m`
    - Installing target `sqlite3_flutter_libs` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/sqlite3_flutter_libs/sqlite3_flutter_libs.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/sqlite3_flutter_libs/sqlite3_flutter_libs-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/sqlite3_flutter_libs/sqlite3_flutter_libs-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/sqlite3_flutter_libs/sqlite3_flutter_libs-dummy.m`
    - Installing target `store_redirect` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/store_redirect/store_redirect.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/store_redirect/store_redirect-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/store_redirect/store_redirect-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/store_redirect/store_redirect-dummy.m`
    - Installing target `umeng_common_sdk` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/umeng_common_sdk/umeng_common_sdk.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/umeng_common_sdk/umeng_common_sdk-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/umeng_common_sdk/umeng_common_sdk-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/umeng_common_sdk/umeng_common_sdk-dummy.m`
    - Installing target `url_launcher` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/url_launcher/url_launcher.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/url_launcher/url_launcher-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/url_launcher/url_launcher-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/url_launcher/url_launcher-dummy.m`
  - Installing Aggregate Targets
    - Installing target `Pods-Runner` iOS 9.0
      - Generating Info.plist file at `Pods/Target Support Files/Pods-Runner/Pods-Runner-Info.plist`
      - Generating module map file at `Pods/Target Support Files/Pods-Runner/Pods-Runner.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Pods-Runner/Pods-Runner-umbrella.h`
      - Generating dummy source at `Pods/Target Support Files/Pods-Runner/Pods-Runner-dummy.m`
  - Generating deterministic UUIDs
  - Stabilizing target UUIDs
  - Running post install hooks
[!] An error occurred while processing the post-install hook of the Podfile.

undefined local variable or method `config' for #<Pod::Podfile:0x00007f7f31a77080>

/Users/mac/Documents/GitHub/seal_note/ios/Podfile:38:in `block (2 levels) in from_ruby'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.11.2/lib/cocoapods-core/podfile.rb:196:in `post_install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:945:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:933:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:149:in `message'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:932:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:331:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:330:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:309:in `create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:301:in `generate_pods_project'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:180:in `integrate'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:167:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:947:in `rescue in run_podfile_post_install_hook'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:944:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:933:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:149:in `message'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:932:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:331:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:330:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:309:in `create_and_save_projects'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:301:in `generate_pods_project'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:180:in `integrate'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:167:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

Error running pod install
Error launching application on iPhone 8.

@darshankawar Please reopen this issue, it isn't fixed

@darshankawar This can be closed. It is fixed after I switched to master channel and run flutter upgrade again.

I found another solution:
I first switch Flutter to master channel, and then switched it back stable channel, it seems work for me.
Now I am using stable channel without this issue.


exceptions: add com.vysp3r.ProtonPlus

Hi, I am the co-maintainer of ProtonPlus, and we have spent a few weeks working on a major update to ProtonPlus which adds support for the popular Steam Tinker Launch compatibility tool.
Due to the way STL has to be installed on the host, we need to check for dependencies via flatpak-spawn --host which <dependency>, and we also need to trigger STL's steamtinkerlaunch compat add command on the host, and another command which STL requires for downloading its dependencies on Steam Deck:
https://github.com/sonic2kk/steamtinkerlaunch/wiki/Steam-Compatibility-Tool#command-line-usage
https://github.com/sonic2kk/steamtinkerlaunch/wiki/Installation#install
As much as it pained us to add the flatpak-spawn permission, there is no way around it. ProtonPlus is an application for installing, upgrading and managing compatibility tools for apps and games on Linux, and as such we unfortunately need the permission to manage those tools on the host. There is no way around it.
I hope you can help us out with this and get the next version of ProtonPlus into the hands of the users. We think they will love it as much as we do. It's been a lot of hard work! :)
Related pull request for the app update: https://github.com/flathub/com.vysp3r.ProtonPlus/pull/33

For reference, ProtonUp-Qt is another compatibility tool manager for Linux, which has the same permission on Flathub due to the same requirement of managing the host's runtimes:
https://github.com/flathub/net.davidotek.pupgui2

@bbhtt Great to see you again. Thank you! I appreciate the fast processing! :)


Null pointer exception

Source information
Asura scans
Source language
English
Steps to reproduce
When trying to manual update a manhwa within its extension it trows a null pointer exception
Expected behavior
It should update
Actual behavior
Throws a null pointer eception
Mihon/Tachiyomi version
1.4.39
Android version
App version: 0.16.5 (standard, 2a01a2a, 6, 2024-04-09T09:58:14Z) Android version: 14 (SDK 34; build UP1A.231005.007.A155FXXU3BXG4) Device brand: samsung Device manufacturer: samsung Device name: a15 (a15nsxx) Device model: SM-A155F WebView: Android System WebView 128.0.6613.146
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Duplicate of #5198
Search the existing issues first before opening a new one, and acknowledging that you did when you clearly didn't again


Camera-frame and task-frame

Hi,
Very cool paper. I have two questions:

I am a bit confused about the camera-frame and task-frame mentioned in the paper, are they the same one?

When you say diffusion policy infers end-effector trajectory in the camera-frame, but the camera is attached to the end-effector, the transformation between the end-effector and the camera is fixed. Or I misunderstand something here?

They aren't the same. When we say task frame, we mean a frame fixed with respect to the world frame. On the other hand, the camera is attached to a moving link on the robot.
Your understanding is correct. The camera frame is a fixed transform from the end effector. As long as your policy predicts a trajectory relative to one of these frames, it will be robot base frame agnostic, and therefore enable cross embodiment deployment.

Thanks for the quick response, got it!


Experimental support for closed callbacks.

This is an experimental PR for supporting closed callbacks.
https://github.com/rack/rack/pull/1932
Types of Changes

New feature.

Testing

[ ] I added tests for my changes.
[ ] I tested my changes locally.
[ ] I tested my changes in staging.
[ ] I tested my changes in production.

I no longer have a positive feeling about this feature.


Bump CAPI to v1.5.0

Describe the solution you'd like
We want to bump CAPI to 1.5.0 (as soon as its released).
Anything else you would like to add:
We had an issue to bump to the RC which is already done: https://github.com/kubernetes-sigs/cluster-api-operator/issues/183
/kind feature
/help

/triage accepted


Check if Tmux is installed

Hi,
Nasty error message if Tmux is not installed (version 1.2.7):
Exception for None -V:
[Errno 2] No such file or directory: 'None'
Traceback (most recent call last):
  File "/home/sdouche/.pyenv/versions/vdefault/bin/tmuxp", line 11, in <module>
    sys.exit(cli.cli())
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/click/core.py", line 1063, in invoke
    Command.invoke(self, ctx)
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/tmuxp/cli.py", line 318, in cli
    has_required_tmux_version()
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/libtmux/common.py", line 414, in has_required_tmux_version
    proc = tmux_cmd('-V')
  File "/home/sdouche/.pyenv/versions/3.6.0/envs/vdefault/lib/python3.6/site-packages/libtmux/common.py", line 178, in __init__
    self.stdout = console_to_str(stdout)

Would you like to make a PR / test? This should be an easy one.

I may take this one on if you don't have time.
What we need:

libtmux to raise an exception that tmux wasn't found in paths.
tmuxp should give a friendlier error message

@sdouche This made it in v1.2.8. It's up on pip now


Add lock while writing to console and closing it

This patch attemps to fix server side race found in #6148
With a -race build the race can be triggered just running:
docker run -ti busybox /bin/sh
Ctrl^d
[DATA RACE HERE AND DAEMON SIDE]

@LK4D4 I don't experience any lockup with the commands you posted in the issue so maybe something was already fixed about this (not sure, in case I'll close this)
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

I don't know :) maybe it's ok.

I also wonder if libcontainer also needs a lock in console_linux

@runcom I'm not a fan of locks in libcontainer :)

@LK4D4 yeah me neither, was just wondering waiting your comment :smile:

DockerSuite.TestRunNonRootUserResolvName failing three times on CI but passes on local, any clue?

@runcom Could you check if there are no leaked goroutines after -it containers stop?

Checked before submitting this pr and IIRC at least one go routine was leaked :/

@LK4D4 this patch doesn't solve anything about goroutine leakage tho..
after -ti command there are 4 more FD and 4 goroutine leaked

Hmm, this looks doesn't look like it would work.
io.Copy blocks until EOF, EOF won't happen because Close is also surrounded by lock... unless somewhere pipes.Stdout is getting closed.

oww I see

At least we know that we need to write some test :)

@cpuguy83 @LK4D4  I suppose, somehow, when pipes.stdout is closed with ctrl^d the write to stdout in https://golang.org/src/io/io.go#L364 errors out and break releasing the lock in io.Copy and Close gets executed....does this make sense?

@runcom I more concerned about application side of closing.


VS15 Linking problem

I get the following output when I try to build robot as a static library in my project.
1>C:\Users\rogueyoshi\Documents\Visual Studio 2015\Projects\AetherSource\src\robot\Source\memory.h(116): error C3423: Use of incomplete type 'Robot::Process' (compiling source file DirectXWrapper.cpp)
1>  C:\Users\rogueyoshi\Documents\Visual Studio 2015\Projects\AetherSource\src\robot\Source\memory.h(21): note: see declaration of 'Robot::Process' (compiling source file DirectXWrapper.cpp)

Are you using the Premade solution or CMake?
If it is the solution then likely you are missing something, if it is the CMake file then that is possible too but maybe I missed something in the library search when I did that.


Fix registration with Google

Currently registering a new user via Mobiilivihko with Google account is broken.

Can't repro, marking as done.


Module hiero-base miss tests for functionality of FileClientImpl.getExpirationTime

🆕🐥 First Timers Only
This issue is reserved for people who have never contributed to this project or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution.
👾 Description of the issue
In the hiero-base module, the FileClientImpl class implements the getExpirationTime method, which retrieves the expiration time of a file on Hedera by interacting with the ProtocolLayerClient. However, this method currently lacks unit and integration tests. Scenarios such as successfully retrieving the expiration time, handling invalid file IDs, and exception handling (e.g., HieroException) are untested. This leaves the functionality susceptible to bugs or unhandled edge cases.
Suggested solution
Create a new test class or extend the existing test suite for FileClientImpl to include tests for the getExpirationTime method. Use JUnit to validate:
Positive scenarios: Successfully retrieving the expiration time for a valid FileId.
Negative scenarios: Handling cases such as null FileId, invalid or non-existent file IDs, and expired files.
Error handling: Ensuring that proper exceptions (e.g., HieroException) are thrown for failures or unexpected conditions.
📋 Step by step guide to do a contribution
If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow.
A more detailed general documentation of the GitHub PR workflow can be found here.

[ ] Claim this issue: Comment below that you are interested in working on the issue
[ ] Wait for assignment: A community member with the given rights will add you as an assignee of the issue
[ ] Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
[ ] Check out the forked repository
[ ] Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
[ ] Solve the issue in your branch.
[ ] Commit your changes: to your branch. Here it is important to sign-off you commits to fullfill the Developer Certificate of Origin (DCO). More information can be found in our contribution guideline.
[ ] Start a Pull Request (PR): in the hedera-enterprise repository
[ ] Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the community for support.
[ ] Wait for reviews: Members of the community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
[ ] You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of our community as an open-source contributor ❤

🎉 Contribute to Hacktoberfest
Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽
🤔 Additional informantion
If you have any questions, just ask us directly in this issue by adding a comment. A general manual about open-source contributions can be found here.

Hi @hendrikebbers, @Ndacyayisenga-droid, I would like to work on these issue.


⚠ Bofrost.es has degraded performance

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

HTTP code: 200
Response time: 1368 ms

Resolved: Bofrost.es performance has improved in aea408c after 9 minutes.


refactor: Optimize performance

If there is already an element in the queue, it is no longer requested
What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #9578 (09f2f37) into 3.0 (84c4b07) will decrease coverage by 0.54%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.0    #9578      +/-   ##
============================================
- Coverage     65.71%   65.16%   -0.55%
+ Complexity      297      296       -1
============================================
  Files          1189     1191       +2
  Lines         51788    51954     +166
  Branches       7833     7855      +22
============================================
- Hits          34031    33855     -176
- Misses        14089    14402     +313
- Partials       3668     3697      +29

Impacted Files
Coverage Δ

...bbo/rpc/cluster/support/ForkingClusterInvoker.java
87.80% <100.00%> (+0.62%)
:arrow_up:

...dubbo/remoting/zookeeper/ZookeeperTransporter.java
55.55% <0.00%> (-33.34%)
:arrow_down:

...pache/dubbo/common/function/ThrowableFunction.java
71.42% <0.00%> (-28.58%)
:arrow_down:

...ing/zookeeper/curator/Curator5ZookeeperClient.java
42.02% <0.00%> (-25.61%)
:arrow_down:

...va/org/apache/dubbo/rpc/protocol/tri/Metadata.java
75.00% <0.00%> (-25.00%)
:arrow_down:

.../apache/dubbo/rpc/filter/ProfilerServerFilter.java
59.37% <0.00%> (-25.00%)
:arrow_down:

.../dubbo/rpc/protocol/tri/command/QueuedCommand.java
68.75% <0.00%> (-15.87%)
:arrow_down:

...ache/dubbo/rpc/proxy/InvokerInvocationHandler.java
69.81% <0.00%> (-15.10%)
:arrow_down:

...bo/rpc/cluster/support/FailbackClusterInvoker.java
59.37% <0.00%> (-14.07%)
:arrow_down:

...mmon/threadpool/support/AbortPolicyWithReport.java
70.17% <0.00%> (-14.04%)
:arrow_down:

... and 89 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 84c4b07...09f2f37. Read the comment docs.


Add route 53 record set and common outputs.

Add route 53 record set and common outputs.

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update site does not keep history

It would be good that the update site at least keeps the latest release in addition to the current snapshot. Right now, only the version corresponding to the latest commit will be in the update site. We can of course manually enable/disable the build of the update site, but it is not convenient.

this would be helpful. I had trouble restoring a previous version in connection with issue #129.

When we make a release, the update site will be available on GitHub, into the releases. The other update site will contain the latest version of ThingML. In any case, it should now be possible to fallback to a stable update site.


isTSTypeAssertion is not a function

if code is
let a = {
  	"b" : false ? 0 : 1
}

then
Error at buildFlowTreeFromAstt.isTSTypeAssertion is not a function

Hmm! That's similar to #31 .


Header popover close button doesn't align

This might be a patternfly issue. The X doesn’t line up with the end of the content popover.

So this is definitely a patternfly thing https://www.patternfly.org/v4/components/popover all the examples have the same alignment. Could open an issue with in https://github.com/patternfly/patternfly-design for it.

To be addressed: https://github.com/patternfly/patternfly/issues/4781

Fixed by PatternFly


Scroll to map on filter change

We've gone back and forth on whether changing a filter should scroll to the list, to the map, or not at all. How about a solution where we scroll to the map if it's available, or to the list if the page was created with ?hide-map=true? I'm probably biased since I want to show off the show-others feature, so I'm open to feedback on this behavior...

I've gotten a number of points of feedback that the autoscroll behavior is jarring. My bias at this point is simply to remove. @drwestco thoughts?

Removed auto-scroll in latest iteration. May need to revisit for mobile since the filters section is so large.


[snapshot] Add Missing Older iPhone & iPad models to Generated Snapshot Reports

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[ ] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context
I noticed running snapshot on some older iPhone and iPad models that they were missing. I worked out the list of supported devices for the report is hardcoded, so have updated the list of devices.
Description
Added missing older iPhone simulator names to the definitions used to output generated HTML files.
Also reordered the iPads and Apple Watches to that the all ascend from oldest to newest, in the same order as the iPhone models are listed.

@getaaron New PR which adds back in the extra iPad and iPhone models from PR #21225 which weren't included in PR #21554

Thanks for the PR, @kylehowells! I don't think there will be any issues, but to be on the safe side can you login to CircleCI using GitHub OAuth so the tests run on your PR?


Can't change PDF link in PDF Signer

Description
I was able to run PDF Signer successfully with no issue by the help of the pdf example (below).

But when I tried to change the pdf link to many other pdfs, it always fail.

And the docs doesn't specify any kind of pdfs.

It appears that the encountered behavior is not a software issue. To ensure smooth operation, please make sure you provide a PDF URL with CORS-ORIGIN enabled. If CORS (Cross-Origin Resource Sharing) is not enabled on the provided URL, the issue you mentioned might occur.
However, we can for sure return an error to the user to inform him that he must provide a PDF URL with CORS enabled.

Should be improved in https://github.com/threefoldtech/tfgrid-sdk-ts/pull/1189

it was documented to which PDF type that should be used


Typos discovered by codespell

$ codespell
./s3transfer/CHANGELOG.rst:75: enhancment ==> enhancement
./s3transfer/scripts/performance/benchmark-upload:132: performace ==> performance
./s3transfer/scripts/performance/benchmark-download:155: performace ==> performance
./s3transfer/tests/unit/test_tasks.py:162: propogates ==> propagates
./s3transfer/tests/unit/test_tasks.py:219: anounce ==> announce
./s3transfer/tests/unit/test_tasks.py:250: anounce ==> an ounce
./s3transfer/tests/unit/test_tasks.py:271: onece ==> once
./s3transfer/tests/unit/test_subscribers.py:65: overriden ==> over ridden
./s3transfer/tests/unit/test_download.py:81: sigal ==> signal, sigil
./s3transfer/tests/unit/test_download.py:687: intially ==> initially
./s3transfer/tests/unit/test_compat.py:31: execption ==> exception
./s3transfer/tests/unit/test_compat.py:57: becase ==> because
./s3transfer/tests/unit/test_s3transfer.py:457: propogates ==> propagates
./s3transfer/tests/unit/test_s3transfer.py:567: temorary ==> temporary
./s3transfer/tests/unit/test_s3transfer.py:637: propogate ==> propagate
./s3transfer/tests/unit/test_futures.py:214: rasied ==> raised
./s3transfer/tests/unit/test_futures.py:277: succes ==> success
./s3transfer/tests/unit/test_manager.py:108: seperate ==> separately
./s3transfer/tests/unit/test_manager.py:119: seperate ==> separate
./s3transfer/tests/functional/test_download.py:84: incase ==> in case
./s3transfer/tests/functional/test_download.py:282: becasue ==> because
./s3transfer/tests/functional/test_download.py:323: seperate ==> separate
./s3transfer/tests/functional/test_upload.py:445: propogate ==> propagate
./s3transfer/tests/functional/test_upload.py:497: propogated ==> propagates
./s3transfer/tests/functional/test_crt.py:102: resopnse ==> response
./s3transfer/tests/integration/test_download.py:93: preceeding ==> preceding, proceeding
./s3transfer/tests/integration/test_download.py:150: preceeding ==> preceding, proceeding
./s3transfer/tests/integration/test_upload.py:81: preceeding ==> preceding, proceeding
./s3transfer/tests/integration/test_upload.py:138: preceeding ==> preceding, proceeding
./s3transfer/.github/workflows/fail-master-prs.yml:13: aginst ==> against
./s3transfer/s3transfer/utils.py:595: aquired ==> acquired
./s3transfer/s3transfer/upload.py:170: configuartion ==> configuration
./s3transfer/s3transfer/processpool.py:479: proccess ==> process
./s3transfer/s3transfer/bandwidth.py:159: amonut ==> amount
./s3transfer/s3transfer/download.py:495: arguements ==> arguments
./s3transfer/s3transfer/download.py:656: existance ==> existence
./s3transfer/s3transfer/manager.py:62: mangager ==> manager
./s3transfer/s3transfer/manager.py:74: transfering ==> transferring
./s3transfer/s3transfer/manager.py:100: streamming ==> streaming
./s3transfer/s3transfer/manager.py:102: recieving ==> receiving
./s3transfer/s3transfer/manager.py:126: dowload ==> download
./s3transfer/s3transfer/manager.py:645: cancelation ==> cancellation
./s3transfer/s3transfer/manager.py:674: propogate ==> propagate
./s3transfer/s3transfer/futures.py:105: propogate ==> propagate
./s3transfer/s3transfer/futures.py:396: excpetion ==> exception
./s3transfer/s3transfer/futures.py:406: implentation ==> implementation
./s3transfer/s3transfer/futures.py:452: assocaited ==> associated
./s3transfer/s3transfer/futures.py:497: parm ==> param, pram, parma
./s3transfer/s3transfer/tasks.py:120: depenent ==> dependent
./s3transfer/s3transfer/tasks.py:178: keword ==> keyword
./s3transfer/s3transfer/tasks.py:189: occassionally ==> occasionally
./s3transfer/s3transfer/tasks.py:201: deffered ==> differed, deferred
./s3transfer/s3transfer/tasks.py:263: implmentations ==> implementations
./s3transfer/s3transfer/tasks.py:272: anounce ==> announce
./s3transfer/s3transfer/tasks.py:281: submition ==> submission
./s3transfer/s3transfer/tasks.py:327: intialization ==> initialization

Thanks for these, @cclauss! A few recent PRs appear to have resolved most of these. I've added #225 to get the last issue and codespell should be running clean after that point.


Research how to allow user to rate Resource using Stars

Overview
Once User has selected star rating, display average star rating on Resource page
Technical Notes

https://pypi.org/project/django-star-ratings/


Don't use for (const ...

I realise that for (const ... is arguably more correct here, since you don't intend to modify the value of prop inside the loop body. However, it doesn't work in some versions of Firefox, which is inconvenient.
Would you consider merging this PR?

We aim for Node.js, not the browser. You can find a more detailed explanation here https://github.com/sindresorhus/ama/issues/446.
If you use Webpack, check out babel-engine-plugin, which transpiles only the dependencies that needs to be transpiled.


Create RubeusKeeper.md

Project Abstract
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[x] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello, David @Noc2 !
The extension will be fully developed by our team, we are going to use JavaScript, as well as for the testing page.
I've split the first milestone in two, so now there are 3.

Hey, @Noc2 , thank you for your suggestions! We fully accept them. I've corrected the application - it now contains only 2 milestones. Also, I've added description about cryptographic algorithm to be used in this project.


Does this work currently?

Does this work currently?

It should.
I haven't really used it in a while, but recently started using my Chromecast again, so I'll probably set this up myself again soon.


adopter onboarding for Li Auto

What type of PR is this?
/kind documentation

What this PR does / why we need it:
adopter onboarding for Li Auto
Which issue(s) this PR fixes:
Parts of #74
Special notes for your reviewer:

Welcome ~


Missing infomation about deleting

Hi,
I think the information about kind of deleting is missing.
Is it a permanent delete or are the lists in recycle bin ?
Regards - Sven

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

ID: 4266835c-a885-dd32-3b74-b655576e92d8
Version Independent ID: ea136a91-6225-547e-5c8c-19aa47eb7515
Content: SPList.Delete Method (Microsoft.SharePoint)
Content Source: sharepoint-server/xml/Microsoft.SharePoint/SPList.xml
Product: sharepoint
GitHub Login: @dotnet-bot
Microsoft Alias: o365devx

It is a permanent delete. Due to use can use a temp list to test it, so the information is optional.

Honestly ?
Yor prefer to let the people doing a test deleting instead of write three words ??
Wow, that's what I would call client-friendly...


Package FluentEmail.Liquid conflicts with Elsa

FluentEmail.Liquid/3.0.2 nuget package conflicts with Elsa/2.7.0 package (both use Fluid library).
As soon as I'm referencing Elsa package in a project, FluentEmail is failing
System.Runtime.InteropServices.ExternalException (0xFFFFFFFF): System.TypeLoadException: Could not load type 'Fluid.BaseFluidTemplate`1' from assembly 'Fluid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=51cdb8c1938e4789'.
   at FluentEmail.Liquid.LiquidRenderer.ParseAsync[T](String template, T model, Boolean isHtml)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at FluentEmail.Liquid.LiquidRenderer.ParseAsync[T](String template, T model, Boolean isHtml)
   at FluentEmail.Liquid.LiquidRenderer.Parse[T](String template, T model, Boolean isHtml)
   at FluentEmail.Core.Email.UsingTemplate[T](String template, T model, Boolean isHtml)

Probably, version referencing for Fluid.Core (>= 1.0.0) isn't quite correct.

Crosspost from https://github.com/lukencode/FluentEmail/issues/331
I am currently missing the ability to modify the MemberAccessStrategy which has been merged to master on 21 march 2022 on PR https://github.com/lukencode/FluentEmail/pull/284 but has not been released on Nuget yet.
I would also like a new release for FluentEmail.Liquid
As i would like to use this feature (without directly including the source in my project)

There is a similar issue with NSwag code generation #339

There is any news on this issue? @florisdipt I'm also looking to modify MemberAccessStrategy did you found a solution?


[BUG] Calculation of hmax is broken

Describe the bug
In build.py, vbuild(), line 102, the calculation of hmax is for a double null machine. However in the case of a single null machine, this same calculation is used. This will give the incorrect value of hmax for a single null machine.
Edit
This may not be broken, but rather poorly explained in code and documentation. In PROCESS we may assume the TF coil is exactly symmetrical, therefore the calculation is fine.
Fix
Check whether this is broken or poorly explained. Fix the brokenness and/or explain.
Add a check for the type of machine, double or single null, and perform the correct calculation for each.

I have decided this calculation is fine, but I have removed the confusing comment and added a clarifying one.


Switch from Requires to extensions

Added two extensions

TensorInferenceCUDAExt = "CUDA"
TensorInferenceGTNExt = "GenericTensorNetworks"

I had an issue trying to run the tests on my machine:
(TensorInference) pkg> test
julia> ERROR: Compat `CUDA` not listed in `deps` or `extras` section.

What is your Julia version? The extensions feature requires Julia > 1.9.

Hmm, I see. I have Julia 1.8.5 installed on my machine. Given the requirement for Julia > 1.9 for the extensions feature, should we consider dropping support for the 1.8.x versions? Or is there a workaround to make it compatible with Julia 1.8.x?

The backward compatibility is discussed here: https://pkgdocs.julialang.org/v1.9/creating-packages/#Backwards-compatibility
However, I am against using compatibility treatment. For some users who want to stick to older version, they can use older version of TensorInference.
We can either merge this PR directly, or merge it at the next julia LTS release. The previous LTS version is 1.6.

Since we are gonna drop support for older Julia versions, I propose we merge this once the next LTS is out.


Clean up TransactionBuilderContext to be easier for a user to use.

This PR was geared up to be something a bit different, in line with https://github.com/stratisproject/StratisBitcoinFullNode/pull/1773 but in the end we opted for a less disruptive change.

Transaction Transaction and bool Sign were removed from the TransactionBuilderContext object because the user shouldn't set them.
The object originally passed to TransactionBuilderContext's ctor are now initialized via properties. This has the advantage to allow more flexibility as to where the inputs are taken from, and it also shows to the user that all the properties are settable and effectively on the same level.

Closes https://github.com/stratisproject/StratisBitcoinFullNode/pull/1773
Closes https://github.com/stratisproject/StratisBitcoinFullNode/issues/1689
@codingupastorm if you need changes with the changeAddress stuff, please do it as part of a SC issue.
🍒 All unit test + integration tests passing (all bar one).
🍒 Nodes are syncing.

This one is very easy when reviewed commit by commit.

Logic looks good to me.
I don't believe this closes #1773 though and I don't think this gets us any closer to safe public consumption of the BuildTransaction functionality, so I'll reopen the issue after this PR goes in.

I think it does bring us a bit closer, as Transaction and Sign are now removed and can't be set by the user.
Maybe in another PR we can make it clear that when you give a context to the TransactionBuilder methods, it comes back "enriched".

@codingupastorm @fassadlr if one of you can merge this, it'll be great.
@codingupastorm I've changed this issue to NOT close #1689 so we can improve on it.
However I'll remove the sp1 label from it as I don't think this is critical from production.


Yaki Admin - Privacy Policy

Requirement
The user can access to the privacy policy on the login page of yaki admin
To do
add a modal or a pop-up where we display all the privacy policy
Test
Test is not required

This was handled and privacy policy are accessible at the logging page


force overwrite=false for disk_setup and fs_setup on etcd disk

We only want to set the partition table and format the first partition on initial VM boot. Regardless of if cloud-init is meant to re-execute those stages, we don't want them to overwrite. Specifically, consider an upgrade scenario with immutable replacement of VMs. We don't want the etcd data disk to be reattached and then wiped/formatted during the (new) VM's initial boot.
Not addressed in this PR: There is concern around whether fs_setup will respect overwrite if a custom command is set (though I'm not sure the extra_opts alone qualifies as a custom command)
cc: @amanohar

This change is

@acs-bot test this please

This already was merged as part of one of Anubhuti's PRs. Closing.


Passing danglingCloseParenthesis to the CLI

Is it possible to set this value to the CLI? It seems that +preserveDanglingCloseParenthesis is ignored.

I also experience this problem.

This option has been deprecated in favor of danglingCloseParenthesis. I removed the examples in the README which use this old setting.


Sync release-3.0 with main

Conflict resolution is detailed in the merge commit.
@krajorama @kofclubs @beorn7 Could you please check if I merged #13662 and #13904 correctly?

On that front, I have a tiny change in the tests to request.

Thanks, fixed!


Integrate namespace into ReentrancyGuard

Resolves #306. This PR updates ReentrancyGuard to utilize namespace and also proposes to append an underscore on the end method: Reentrancy.end_. The reason for the underscore is because end itself is a protected keyword in Cairo and prepending the underscore may conflict or cause confusion with the new extensibility pattern.

I think preppending is acceptable, since these are type B/public (not C/external) functions anyway.

Looks good! But we can use _start and _end for consistency.

Yes, sir! Sounds good


As an analyst, I want to retrieve a list of all cities in a district organized by their population from largest to smallest, so that I can use this information to assist the understanding of the demographic distribution across cities in a district.

Finished issue.


multidoge hang during synchro

Hi, my multidoge client hang during synchro.
Got 8 payment address in one wallet file.
1 address is used by my miner on p2pool and receive a lot of transaction.
If I import the priv key in a newly created wallet file, the synchro hang too. It seems the client can't handle such amount of transaction.
I haven't found any related issue on the web.

same here im stuck at Synchronising with network, i like to try this software if working

Windows 7 у меня. Подскажите пожалуйста  в какой паке искать ключ, что бы отправить его на Импортировать закрытый ключ https://my.dogechain.info/#/wallet
Как называется файл, и по какому пути искать? C:\Users\A\AppData\Roaming\MultiDoge или
C:\Program Files (x86)\MultiDoge-0.1.7
I have Windows 7. Please tell me in which pack to look for a key to send it to Import private key https://my.dogechain.info/#/wallet
What is the name of the file, and which way to look for?
Had the same issue. Here's an easy and quick way to solve it:

Export Private Key from your multidoge wallet - without password
Create a wallet on https://my.dogechain.info
Import your Private Key in this wallet (there's a button for that, than just copy-paste the key from the opened key-file)
Refresh the new wallet with the refresh button below your balance. Done. Spend your coins.

I registered just to tell you that (check it).
How about you buy me a beer, fair enough?: DShcCFQ1NqT4FiAYouFtDbmfoFVBEuvhx7
Cheers
Vale

I have Windows 7. Please tell me in which pack to look for a key to send it to Import private key https://my.dogechain.info/#/wallet
What is the name of the file, and which way to look for?  Thanks for the reply and tip! As my Multidoge show's 0 balance it has not synced even once. Can I still just export the wallet's private key and have it synced at the online doge wallet? Shooting you a beer once get hand of my coins lol On 7 Jan 2018 23:19, "1salomon3"<EMAIL_ADDRESS>wrote: Hey Man, the multidoge app seems pretty shitty. Had the same issue. Here's an easy and quick way to solve it: 1. Export Private Key from your multidoge wallet - without password 2. Create a wallet on https://my.dogechain.info 3. Import your Private Key in this wallet (there's a button for that, than just copy-paste the key from the opened key-file) 4. Refresh the new wallet with the refresh button below your balance. Done. Spend your coins. I registered just to tell you that (check it). How about you buy me a beer, fair enough?: DShcCFQ1NqT4FiAYouFtDbmfoFVBEu vhx7 Cheers Vale — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AheYuHQclkeB6ktsMLfG6oZ-MM-K7QjUks5tITTbgaJpZM4BqY7t .

You have no idea how much you've helped.  Thanks

Hey! Thanks for the reply and tip! As my Multidoge show's 0 balance it has not synced even once. Can I still just export the wallet's private key and have it synced at the online doge wallet? Shooting you a beer once get hand of my coins lol On 7 Jan 2018 23:19, "1salomon3"<EMAIL_ADDRESS>wrote: Hey Man, the multidoge app seems pretty shitty. Had the same issue. Here's an easy and quick way to solve it: 1. Export Private Key from your multidoge wallet - without password 2. Create a wallet on https://my.dogechain.info 3. Import your Private Key in this wallet (there's a button for that, than just copy-paste the key from the opened key-file) 4. Refresh the new wallet with the refresh button below your balance. Done. Spend your coins. I registered just to tell you that (check it). How about you buy me a beer, fair enough?: DShcCFQ1NqT4FiAYouFtDbmfoFVBEu vhx7 Cheers Vale — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AheYuHQclkeB6ktsMLfG6oZ-MM-K7QjUks5tITTbgaJpZM4BqY7t .

You have no idea how much you've helped.  Thanks

@namtabio
You have no idea how much you just helped me. Been stressing, but luckily I found this.  Been stressing, but luckily I found this. You are a legend

I have been stuck with MultiDoge, without being able to sell the coins. Once imported with private keys, does https://my.dogechain.info allows sell in USD ?

@1salomon3 Thanks for the tip. There are really very few references I found helping taking the coins out of Multidoge. Coins sent for the evening Beer :-).

Hi,
I'm brand new to crypto and was wondering if anyone can help.
I bought some Dogecoins yesterday and they are showing on my balance in my Multidoge wallet but spendable amount is zero.
Status says "seen by 19 peers. Pending / unconfirmed.  I've tried to follow your instructions and have done the following....
.

I've exported my private key which I've now got a .key file with my key inside
I've tried to import this private key into another wallet on Dogechain but I just get a "Please specify a valid private key error" message
I've reimported my private key back into Multidoge and is showing balance again but still spendable is zero.

I'm at a loss on what to do next
Thanks

Why don't you remove the MultiDoge wallet from the site already? It is so shitty and I have seen many users including myself having that same syncing problem in Reddit. I am yet to try the solution to export my keys to another wallet and uninstall this thing and never use it/recommend it again.

@Panqueque1 You right.  Even you try to close that it will be hanging and you don't have any choice except to restart your computer at the end of the day.


Left nav section resizing on menu selection

Left nav is resizing on menu selections. Creates a jumpy visual when moving from menu selection to another selection.
To see example go here:
https://learn.hasura.io/graphql/react/queries/2-create-query
then select the content below the 'queries' section.
screenshot
https://screencast.com/t/EtZLmTu5t
At first I thought it was the size of the TOC on the right but that's not the cause.

@i001962 - This seems to have been fixed in one of the recent updates to styles and emotion dependency updates.


feat: Add QnA files to dispatch model in skill manifest

Description
Add QnA files to the dispatch models property in the skill manifest editor.
Task Item
Closes #3984

Coverage increased (+0.04%) to 56.771% when pulling 7370d159c0a56742fe6494c373e6ab724a4f7a03 on tdurnford:feat/skill-manifest-qna into 6e552e32f6d7f306c779b95ae040d8419fbfeb13 on microsoft:main.

@tdurnford please fix conflicts


Checking whether MinGW really supports threads

Related to https://github.com/cnjinhao/nana/issues/295, see the detailed description in the issue.
Further investigation revealed that unless the MinGW binary is built with --enable-threads=posix - which is not the default - it can't implement threading as we expect in Nana, despite the mutex header being present.
I tested the changes with i686-w64-mingw32-g++, gcc version 6.3.0 20170516 (GCC), targeting Windows x86 from Linux.

Thanks for your PR.


[Bug]: Unable to remove mods from Inactive Mod List

Operating System
Windows 11 Pro Version	23H2 OS build	22631.3880 Experience Windows Feature Experience Pack 1000.22700.1020.0
BG3 Mod Manager Version
<IP_ADDRESS>
BG3 Game Version
Version Number <IP_ADDRESS>22896	Hotfix #25
Bug Summary
I have 14 mods in the Inactive Mod list (including Dice Set and Honour from Larian) that BG3MM tells me the files don't exist and that I can't delete them, similar to Bug Report # 252 - Unable to remove non-existent mods {https://github.com/LaughingLeader/BG3ModManager/issues/252}.
BG3MM tells me the 12 non-Larian mods I had added to the mod list also don't exist and can't be deleted.

I tried re-adding a1_dIstinctive_dyes (Distinctive Dyes v2.2-4003-1-22-1702551874.zip) and BCPP_16x9_6cahrs5x6inventory (BCPP 16x9 6 chars 5x6 inventory-1580-1-62-1709813289.zip) to the inactive mod list.  They're now listed as overrides and I still can't delete them.

Links
No response

All mods are override mods as displayed in the overrides window after reinstallation.  The Inactive Mod list still says the mods can't be deleted even after reinstallation.

All 14 mods were deleted using the Override Window and the mods were removed from the Inactive Mods list.

The order was saved {Ctrl-S}, exported to game {Ctrl-E}, Reload All {F5} was processed, removing the overrides from the Override list, but readding them to the Inactive Mods list.

I've uninstalled all files for the Baldur's Gate III game, Steam application, Larian Launcher, BG3 Mod Manager and Vortex in their working directories and in {%LOCALAPPDATA%} directories, cleanly reinstalled all applications on a different drive, removed one mod from the load order when I moved from Vortex to BG3MM as mod manager because it was placing a subdirectory in {%LOCALAPPDATA%\Larian Studios\Baldur's Gate 3\Mods}, and I still have 32 mods listed in BG3MM Inactive Mods pane that do not exist and can't be deleted.


Update org.eclipse.jdt.core to 3.21.0

Updates org.eclipse.jdt:org.eclipse.jdt.core from 3.19.0 to 3.21.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.eclipse.jdt", artifactId = "org.eclipse.jdt.core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #671 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #671   +/-   ##
=======================================
  Coverage   81.13%   81.13%
=======================================
  Files          78       78
  Lines        5163     5163
  Branches      130      130
=======================================
  Hits         4189     4189
  Misses        974      974

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 9810a57...1949b7b. Read the comment docs.


[Improvement]: Requesting public API for supporting to check the Regex Pattern validity before code generation

Description
We have a requirement to validate the given regex pattern before giving the tooling support to ballerina code generations. Therefore it would be great if we can have a public API from NodeParser including the validity of the pattern and the details of the errors.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Closing as per https://github.com/ballerina-platform/ballerina-lang/pull/40339#issuecomment-1596483212.


⚠ SceneTime has degraded performance

In b9c8eda, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1631 ms

Resolved: SceneTime performance has improved in 9757de8 after 11 minutes.


请问，执行文档最后命令，服务没起来 有报错

$ python3 app.py  /   nohup python3 app.py & tail -f nohup.out
[3] 7025
Traceback (most recent call last):
File "/bot-on-anything/app.py", line 37, in
start_process(channel_type[0])
File "/bot-on-anything/app.py", line 20, in start_process
channel.startup()
File "/bot-on-anything/channel/terminal/terminal_channel.py", line 14, in startup
prompt = self.get_input("User:\n")
File "/bot-on-anything/channel/terminal/terminal_channel.py", line 32, in get_input
line = input()
OSError: [Errno 9] Bad file descriptor
Load config success
Load config success

怎么解决，一模一样


Resolve celery conflict

New in most recent test run:
2021-03-05T23:05:28.1348014Z The conflict is caused by:
2021-03-05T23:05:28.1349115Z     celery 5.0.5 depends on click-plugins>=1.1.1
2021-03-05T23:05:28.1350240Z     celery 5.0.4 depends on click-plugins>=1.1.1
2021-03-05T23:05:28.1351376Z     celery 5.0.3 depends on click-plugins>=1.1.1
2021-03-05T23:05:28.1351988Z
2021-03-05T23:05:28.1352580Z To fix this you could try to:
2021-03-05T23:05:28.1354073Z 1. loosen the range of package versions you've specified
2021-03-05T23:05:28.1355222Z 2. remove package versions to allow pip attempt to solve the dependency conflict
2021-03-05T23:05:28.1356007Z
2021-03-05T23:05:28.2330633Z ##[error]Process completed with exit code 1.

https://github.com/datalad/datalad-registry/pull/21/checks?check_run_id=2043616783

To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

Hmm, I'm not seeing anything in setup.cfg that would be problematic here:
https://github.com/datalad/datalad-registry/blob/ab451d7c4d5eaa1dc0bff323704190a29cedb83b/setup.cfg#L18-L24
And a fresh test run on the current master (ab451d7c) was green, so it looks like the above was a transient failure.
https://github.com/datalad/datalad-registry/runs/2057420341


Save functionality

We have open, but no way to save out the result to a file easily

Fixed in https://github.com/wycats/nushell/pull/93


Set up a "Hello world" project with rails-react gem

Setup a "Hello World" project with rails-react gem

Create a new Rails app called 'hello-rails-react'.
Initialize your project with Git.
Set up your project with webpacker the react-rails gems as described in the previous lesson's tutorial.
Make sure that your project has a Postgres database set up.
Create a table for storing your messages and create 5 different greetings.
Create an API endpoint that selects a random greeting from your table (you will need a controller with an action and Rails route).
Create a static view that will be the root of your app.
Create the App component with react-router and render it in your static view.
Create the Greeting component that will display a greeting. Set it up as a route in your App component.
Create a store, an action and a reducer that will connect to you API endpoint to get the random greeting.
Display the random greeting in your Greeting component.

Thank you for your nice review! 😃☺

Thank you !!


Add a non-yahp way to create FFCV dataset.

🚀 Feature Request
Currently we can create dataset in ffcv format if not specified via hparams.
Motivation
We want a way to create it beforehand.
[Optional] Implementation
Additional context

Closing -- merging this into 737


Document Summarization Quickstart : Errors encountered

Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, #33886.
Please be aware that @yuvrajharsha is the author of the original issue and include them for any questions or replies.
Details

Package Name:
Package Version:
Operating System:
.NET runtime version:

[Enter feedback here]
Hello,
I installed VS 17.4.4 for mac and as per instructions, given in the following link for 'Document Summarization', I ran the given C# code but encountered following 8 errors
https://learn.microsoft.com/en-us/azure/cognitive-services/language-service/summarization/quickstart?tabs=document-summarization&pivots=programming-language-csharp
/Program.cs(17,17): Error CS0117: 'TextAnalyticsActions' does not contain a definition for 'ExtractSummaryActions' (CS0117) (Summarisation)
/Program.cs(50,50): Error CS0246: The type or namespace name 'ExtractSummaryAction' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
/Program.cs(80,80): Error CS0246: The type or namespace name 'ExtractSummaryAction' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
/Program.cs(37,37): Error CS0246: The type or namespace name 'ExtractSummaryActionResult' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
/Program.cs(98,98): Error CS1061: 'AnalyzeActionsResult' does not contain a definition for 'ExtractSummaryResults' and no accessible extension method 'ExtractSummaryResults' accepting a first argument of type 'AnalyzeActionsResult' could be found (are you missing a using directive or an assembly reference?) (CS1061) (Summarisation)
/Program.cs(26,26): Error CS0246: The type or namespace name 'ExtractSummaryActionResult' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
/Program.cs(30,30): Error CS0246: The type or namespace name 'ExtractSummaryResult' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
/Program.cs(34,34): Error CS0246: The type or namespace name 'SummarySentence' could not be found (are you missing a using directive or an assembly reference?) (CS0246) (Summarisation)
Could you please help me run the example code for Document Summarization. Looking forward to your support. Thank you.
Best regards,
Yuvraj Harsha

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

ID: acf1d359-23da-2f07-af0d-d16284f738ba
Version Independent ID: eba6f1fd-cfe9-d038-b139-f02c0b48f4e0
Content: Quickstart: Use Document Summarization (preview) - Azure Cognitive Services
Content Source: articles/cognitive-services/language-service/summarization/quickstart.md
Service: cognitive-services
Sub-service: language-service
GitHub Login: @jboback
Microsoft Alias: aahi

@jsquire
Thanks for your feedback! We will investigate and update as appropriate.

#assign: jboback

@jsquire
I've delegated this to content author @jboback, who will review it and offer their insightful opinions.

Hi @jsquire, thanks for forwarding the feedback from Yuvraj. I've created a work item and will check in with the team about the issue to see if we can improve the docs.

#please-close


Fix docs

Description
This PR updates the Kind version in the examples (the previous one failed to start for me) and fixes two minor issues.
How Has This Been Tested?
I went through the fixed tutorial successfully using the new instructions.

/test

/test

/rebase test=true

/test


Can not delete namespaces

I can not delete namespaces.
Get:
  - lastTransitionTime: "2022-05-22T22:08:54Z"
    message: 'Discovery failed for some groups, 3 failing: unable to retrieve the
      complete list of server APIs: controlplane.antrea.io/v1beta2: the server is
      currently unable to handle the request, stats.antrea.io/v1alpha1: the server
      is currently unable to handle the request, system.antrea.io/v1beta1: the server
      is currently unable to handle the request'
    reason: DiscoveryFailed

To Reproduce
Antrea 1.6.1 on EKS
Expected
The namespace should be deleted.
Actual behavior
The namespace will be forever on terminating state.
Versions:

Antrea version (Docker image tag). 1.6.1
Kubernetes version (use kubectl version). v1.22.6-eks-14c7a48

I have a default DROP netpolicy, but kube-system can talk to Self and to control-plane and kubelets node IPs. I see no traffic being dropped from the controller to the api.
Anyways, I disabled the default DROP netpolicy and still it does not work.

This error means that the K8s control plane cannot communicate with the Antrea (Controller) API. This is independent of network policies given that the antrea-controller Pod is a hostNetwork Pod. Do you have any VPC security group rules denying such connections?

No, I have not.
I have deleted the controller pod and after it was rescheduled by k8s(at the same node btw) the deletion worked. Is there a proactive way to detect when this problem happens? What other problems can i face if the control plane can not take to antrea controller(I am supposing this is the problem )?

Antrea uses K8s aggregated APIs to expose some Antrea Controller APIs through the K8s apiserver. Some functions in antctl depend on that.
In K8s, if any API (including aggregated APIs) is not reachable, it prevents Namespace deletion.
I don't know why you get in a situation where these APIs are not accessible since communication between the K8s control plane and the Antrea Controller doesn't depend on Pod networking. But you can check the status for these apiservices with kubectl get apiservices.
And if you run kubectl get endpoints/antrea -n kube-system, it will show you the address that the K8s control plane should be using to access the API.

Closing this. Probably related to #3946


Fix getCache() internal key filtering

I didn't get a chance to get the context around this PR from Michael in person before he stepped out on vacation: https://github.com/Netflix/falcor/pull/640/ but it seems to have regressed model.getCache() behavior, by allowing some internal keys to remain in the results of model.getCache() (e.g. refN, ref-index, etc). It seems to be a pretty conscious change, so not sure if it was intentional.
However, in the absence of this context, it seems like the desired behavior is to strip ALL internal keys from the cache, when returning a copy through getCache().
This PR aims to fix the above regression, and also fix what seems to be a gap in the original implementation, where $size would still be left in the results of getCache() at the leaf/sentinel nodes, when cloning boxed values. I don't think this was intentional.
Unit tests added, to make sure:

Stripping refN, ref-index doesn't result in references breaking when the copy of the cache is used to re-hydrate a new model
Make sure no internal keys are left in the cache-copy returned by getCache()

@jhusain @michaelbpaulson @trxcllnt - eyes appreciated, especially since I'm making assumptions about the original design intention.

@sdesai 😍 thanks! cc: @ekosz

@sdesai All is correct.  The motivation for 'values which are objects' decision is a subtle one.
var m = new Model();
var m2 = new Model();

// set a complex object.
m.setValue(['foo'], {bar: 'baz'}).subscribe();

// Set the cache from m to m2
m2.setCache(m.getCache());

Without the check for objectyness the following would happen.
m2.get(['foo']).subscribe(log, log, log.bind(null, 'i completed!'));

This would simply console out i completed! because the underlying cache changed from m to m2.
m and m2's cache would be
// m
{
    foo: {
        $type: 'atom',
        value: {
            bar: 'baz'
        }
    }
}

//m2
{
    foo: {
            bar: {
                $type: 'atom',
                value: 'baz'
            }
    }
}

Hope that helps!

I see. Thanks. Makes sense. It's to distinguish between branches and atoms, and we don't need to take on the cost of the wrapper/clone for the non-object case, because there's nothing ambiguous to distinguish against.
Gonna merge this.

@sdesai is this going to be merged into master soon?

Hey Paul, I believe master has the original (prefix) based filter already. Otherwise can merge it in. This one does have the additional fix for sentinel wrappers

@sdesai from what I can tell, master's version of isInternalKey is still checking for specific internal keys.

Ok. I'm OOO for Xmas, but will merge it in, in between things


react-select-fast-filter-options and searchable filter controls

The filter box is not performing well for very long dropdown list. The situation gets better with react-select-fast-filter-options and searchable filter controls.

Coverage remained the same at 70.757% when pulling c24aba9ce21436af358f1df97f82bfe1ed56f2d7 on xiaoyugit:faster_filter_box into e121a8585e753e0e659f52da2bec6b5bc7f79444 on apache:master.

Coverage remained the same at 70.757% when pulling a023b1295c1d5f1c9f0f6f61aa8668bacc851021 on xiaoyugit:faster_filter_box into e121a8585e753e0e659f52da2bec6b5bc7f79444 on apache:master.

Coverage remained the same at 70.757% when pulling a023b1295c1d5f1c9f0f6f61aa8668bacc851021 on xiaoyugit:faster_filter_box into e121a8585e753e0e659f52da2bec6b5bc7f79444 on apache:master.


Fix typo in walkthrough.md

Just removing wrong space in a command

@DirectXMan12 this LGTM. Could you merge it ?

Thank you @zioproto The issue which this PR tried to fix was removed by https://github.com/DirectXMan12/k8s-prometheus-adapter/pull/84. Closing this PR.


fix: apply the q/a swap when the search value changes

Previously, when the flow was "answer->question" and the user edited
the search field, the list was re-filtered correctly but was also
reverted to "question->answer" flow.
This was because the logic for swapping the question and answer only
ran when the flow was toggled. When the user edited the search value,
the list of questions to display was recomputed from scratch and the
swap was lost.
Fix this by also running the swap logic when the search value changes.

DISCLAIMER: Completely untested. Not sure if this is the best approach.

Thanks for this PR, however I am swapping out this piece of code actually as I think there is no dependency between individual question and the flow, so TL;DR is this useEffect is going to go away.
We can close this PR, but thanks for pointing out the issue, I will test this before adding the changes.
It would be part of this PR (#9)