-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_all_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_core_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_location_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_map_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_search_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/connectivity
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_image_compress
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_plugin_android_lifecycle
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_qr_reader
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/fluttertoast
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/foundation_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/image_gallery_saver
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/image_picker
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/jpush_flutter
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/package_info
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/path_provider
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/permission_handler
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/photo_manager
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/shared_preferences
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/sharesdk_plugin
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/url_launcher
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/JCore -L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/JPush
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/SinaWeiboSDK
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/WeChatSDK
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/Mantle
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/Reachability
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_all_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_core_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_location_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_map_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/amap_search_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/connectivity
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_image_compress
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_plugin_android_lifecycle
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/flutter_qr_reader
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/fluttertoast
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/foundation_fluttify
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/image_gallery_saver
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/image_picker
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/jpush_flutter
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/package_info
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/path_provider
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/permission_handler
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/photo_manager
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/shared_preferences
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/sharesdk_plugin
-L/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/url_launcher
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/JCore -L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/JPush
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/SinaWeiboSDK
-L/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/WeChatSDK -L/Users/dingxiankun/Desktop/Demo/paas/ios/Flutter
-F/Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_core_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_location_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_map_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_search_fluttify/ios -F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../Flutter
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/MOBFoundation/MOBFoundation -F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/Optional
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformConnector
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/DouyinOpenSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/FacebookSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/OasisSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/QQSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/Required
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_core_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_location_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_map_fluttify/ios
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../.symlinks/plugins/amap_search_fluttify/ios -F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/../Flutter
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/MOBFoundation/MOBFoundation -F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/Optional
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformConnector
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/DouyinOpenSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/FacebookSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/OasisSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/PlatformSDK/QQSDK
-F/Users/dingxiankun/Desktop/Demo/paas/ios/Pods/mob_sharesdk/ShareSDK/Support/Required -F/Users/dingxiankun/Desktop/Demo/paas/ios/Flutter
-F/Users/dingxiankun/Desktop/Demo/paas/ios -filelist
/Users/dingxiankun/Library/Developer/Xcode/DerivedData/Runner-eeyybvzhcjbkdxghinlgzmnlgqjo/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Objects
-normal/x86_64/Runner.LinkFileList -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker
@loader_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -Xlinker -rpath -Xlinker
@executable_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker
/Users/dingxiankun/Library/Developer/Xcode/DerivedData/Runner-eeyybvzhcjbkdxghinlgzmnlgqjo/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Objects
-normal/x86_64/Runner_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -fobjc-arc -fobjc-link-runtime
-L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator -L/usr/lib/swift -Xlinker -add_ast_path
-Xlinker
/Users/dingxiankun/Library/Developer/Xcode/DerivedData/Runner-eeyybvzhcjbkdxghinlgzmnlgqjo/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Objects
-normal/x86_64/Runner.swiftmodule -ObjC -lMantle -lReachability -lWeChatSDK -lWeiboSDK -lamap_all_fluttify -lamap_core_fluttify -lamap_location_fluttify
-lamap_map_fluttify
-lamap_search_fluttify -lc++ -lconnectivity -lflutter_image_compress -lflutter_plugin_android_lifecycle -lflutter_qr_reader -lfluttertoast
-lfoundation_fluttify
-limage_gallery_saver -limage_picker -ljcore-ios-2.2.0 -ljpush-ios-3.2.8 -ljpush_flutter -lpackage_info -lpath_provider -lpermission_handler
-lphoto_manager -lresolv
-lshared_preferences -lsharesdk_plugin -lsqlite3 -lstdc++ -lurl_launcher -lz -framework AMapFoundationKit -framework AMapLocationKit -framework
AMapSearchKit -framework
CFNetwork -framework CoreFoundation -framework CoreGraphics -framework CoreLocation -framework CoreTelephony -framework CoreText -framework
DouyinConnector -framework
ExternalAccessory -framework FBSDKCoreKit -framework FBSDKLoginKit -framework FBSDKShareKit -framework FacebookConnector -framework Flutter -framework
Foundation -framework
GLKit -framework ImageIO -framework JavaScriptCore -framework MAMapKit -framework MOBFoundation -framework MOBFoundationEx -framework OasisConnector
-framework OasisSDK
-framework OpenGLES -framework QQConnector -framework QuartzCore -framework Security -framework ShareSDK -framework ShareSDKConnector -framework
ShareSDKExtension -framework
ShareSDKLink -framework ShareSDKUI -framework SinaWeiboConnector -framework SystemConfiguration -framework TencentOpenAPI -framework TikTokOpenPlatformSDK
-framework
TwitterConnector -framework UIKit -framework WechatConnector -weak_framework Accelerate -weak_framework Accounts -weak_framework AudioToolbox
-weak_framework
AuthenticationServices -weak_framework CoreGraphics -weak_framework CoreLocation -weak_framework CoreServices -weak_framework QuartzCore -weak_framework
SafariServices
-weak_framework Security -weak_framework Social -weak_framework UIKit -weak_framework UserNotifications -ObjC -lMantle -lReachability -lWeChatSDK
-lWeiboSDK
-lamap_all_fluttify -lamap_core_fluttify -lamap_location_fluttify -lamap_map_fluttify -lamap_search_fluttify -lc++ -lconnectivity -lflutter_image_compress
-lflutter_plugin_android_lifecycle -lflutter_qr_reader -lfluttertoast -lfoundation_fluttify -limage_gallery_saver -limage_picker -ljcore-ios-2.2.0
-ljpush-ios-3.2.8
-ljpush_flutter -lpackage_info -lpath_provider -lpermission_handler -lphoto_manager -lresolv -lshared_preferences -lsharesdk_plugin -lsqlite3 -lstdc++
-lurl_launcher -lz
-framework AMapFoundationKit -framework AMapLocationKit -framework AMapSearchKit -framework CFNetwork -framework CoreFoundation -framework CoreGraphics
-framework
CoreLocation -framework CoreTelephony -framework CoreText -framework DouyinConnector -framework ExternalAccessory -framework FBSDKCoreKit -framework
FBSDKLoginKit -framework
FBSDKShareKit -framework FacebookConnector -framework Flutter -framework Foundation -framework GLKit -framework ImageIO -framework JavaScriptCore
-framework MAMapKit
-framework MOBFoundation -framework MOBFoundationEx -framework OasisConnector -framework OasisSDK -framework OpenGLES -framework QQConnector -framework
QuartzCore -framework
Security -framework ShareSDK -framework ShareSDKConnector -framework ShareSDKExtension -framework ShareSDKLink -framework ShareSDKUI -framework
SinaWeiboConnector -framework
SystemConfiguration -framework TencentOpenAPI -framework TikTokOpenPlatformSDK -framework TwitterConnector -framework UIKit -framework WechatConnector
-weak_framework
Accelerate -weak_framework Accounts -weak_framework AudioToolbox -weak_framework AuthenticationServices -weak_framework CoreGraphics -weak_framework
CoreLocation
-weak_framework CoreServices -weak_framework QuartzCore -weak_framework SafariServices -weak_framework Security -weak_framework Social -weak_framework
UIKit -weak_framework
UserNotifications -ObjC -lMantle -lReachability -lWeChatSDK -lWeiboSDK -lamap_all_fluttify -lamap_core_fluttify -lamap_location_fluttify
-lamap_map_fluttify
-lamap_search_fluttify -lc++ -lconnectivity -lflutter_image_compress -lflutter_plugin_android_lifecycle -lflutter_qr_reader -lfluttertoast
-lfoundation_fluttify
-limage_gallery_saver -limage_picker -ljcore-ios-2.1.8 -ljpush-ios-3.2.8 -ljpush_flutter -lpackage_info -lpath_provider -lpermission_handler
-lphoto_manager -lresolv
-lshared_preferences -lsharesdk_plugin -lsqlite3 -lstdc++ -lurl_launcher -lz -framework AMapFoundationKit -framework AMapLocationKit -framework
AMapSearchKit -framework
CFNetwork -framework CoreFoundation -framework CoreGraphics -framework CoreLocation -framework CoreTelephony -framework CoreText -framework
DouyinConnector -framework
ExternalAccessory -framework FBSDKCoreKit -framework FBSDKLoginKit -framework FBSDKShareKit -framework FacebookConnector -framework Flutter -framework
Foundation -framework
GLKit -framework ImageIO -framework JavaScriptCore -framework MAMapKit -framework MOBFoundation -framework MOBFoundationEx -framework OpenGLES -framework
QQConnector
-framework QuartzCore -framework Security -framework ShareSDK -framework ShareSDKConnector -framework ShareSDKExtension -framework ShareSDKLink -framework
ShareSDKUI
-framework SinaWeiboConnector -framework SystemConfiguration -framework TencentOpenAPI -framework TikTokOpenPlatformSDK -framework TwitterConnector
-framework UIKit
-framework WechatConnector -weak_framework Accelerate -weak_framework Accounts -weak_framework AudioToolbox -weak_framework AuthenticationServices
-weak_framework
CoreGraphics -weak_framework CoreLocation -weak_framework CoreServices -weak_framework QuartzCore -weak_framework SafariServices -weak_framework Security
-weak_framework
Social -weak_framework UIKit -weak_framework UserNotifications -all_load -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker
/Users/dingxiankun/Library/Developer/Xcode/DerivedData/Runner-eeyybvzhcjbkdxghinlgzmnlgqjo/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Runner.
app-Simulated.xcent -framework Flutter -framework App -lPods-Runner -Xlinker -dependency_info -Xlinker
/Users/dingxiankun/Library/Developer/Xcode/DerivedData/Runner-eeyybvzhcjbkdxghinlgzmnlgqjo/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Objects
-normal/x86_64/Runner_dependency_info.dat -o /Users/dingxiankun/Desktop/Demo/paas/build/ios/Debug-iphonesimulator/Runner.app/Runner
ld: library not found for -ljcore-ios-2.1.8
clang: error: linker command failed with exit code 1 (use -v to see invocation)
                    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 6.0, but the range of supported deployment target versions is 8.0 to

13.2.99. (in target
'Reachability' from project 'Pods')
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 5.0, but the range of supported deployment target versions is 8.0 to
13.2.99. (in target
'Mantle' from project 'Pods')
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the range of supported deployment target versions is 8.0 to
13.2.99. (in target
'JCore' from project 'Pods')
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 6.0, but the range of supported deployment target versions is 8.0 to
13.2.99. (in target
'JPush' from project 'Pods')
warning: Mapping architecture armv7 to i386. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the
iOS Simulator
platform. (in target 'image_picker' from project 'Pods')
warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the
iOS Simulator
platform. (in target 'image_picker' from project 'Pods')
[ +494 ms] Could not build the application for the simulator.
[   +1 ms] Error launching application on iPhone 11 Pro Max.
[   +2 ms] "flutter run" took 38,981ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:509:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#3      _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#4      _rootRunUnary (dart:async/zone.dart:1134:38)
#5      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#9      Future._completeWithValue (dart:async/future_impl.dart:524:5)
#10     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#11     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#12     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#13     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#14     _rootRunUnary (dart:async/zone.dart:1134:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#22     IosProject.isSwift (package:flutter_tools/src/project.dart)
#23     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#24     _rootRunUnary (dart:async/zone.dart:1134:38)
#25     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#26     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#27     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#28     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#29     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#30     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#31     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#32     IosProject.buildSettings (package:flutter_tools/src/project.dart)
#33     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#34     _rootRunUnary (dart:async/zone.dart:1134:38)
#35     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#36     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#37     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#38     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#39     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#40     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#41     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#42     XcodeProjectInterpreter.getBuildSettings (package:flutter_tools/src/ios/xcodeproj.dart)
#43     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#44     _rootRunUnary (dart:async/zone.dart:1134:38)
#45     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#46     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#47     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#48     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#49     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#50     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#51     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#52     _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart)
#53     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#54     _rootRunUnary (dart:async/zone.dart:1134:38)
#55     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#56     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#57     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#58     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#59     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#60     Future.wait. (dart:async/future.dart:400:22)
#61     _rootRunUnary (dart:async/zone.dart:1134:38)
#62     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#63     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#64     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#65     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#66     Future._complete (dart:async/future_impl.dart:514:7)
#67     _BufferingStreamSubscription.asFuture. (dart:async/stream_impl.dart:206:14)
#68     _rootRun (dart:async/zone.dart:1122:38)
#69     _CustomZone.run (dart:async/zone.dart:1023:19)
#70     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#71     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:391:13)
#72     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:401:15)
#73     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:285:7)
#74     _SinkTransformerStreamSubscription._close (dart:async/stream_transformers.dart:98:11)
#75     _EventSinkWrapper.close (dart:async/stream_transformers.dart:25:11)
#76     _StringAdapterSink.close (dart:convert/string_conversion.dart:251:11)
#77     _Utf8ConversionSink.close (dart:convert/string_conversion.dart:302:20)
#78     _ConverterStreamEventSink.close (dart:convert/chunked_conversion.dart:82:18)
#79     _SinkTransformerStreamSubscription._handleDone (dart:async/stream_transformers.dart:143:24)
#80     _rootRun (dart:async/zone.dart:1122:38)
#81     _CustomZone.run (dart:async/zone.dart:1023:19)
#82     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#83     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:391:13)
#84     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:401:15)
#85     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:285:7)
#86     _SyncStreamControllerDispatch._sendDone (dart:async/stream_controller.dart:774:19)
#87     _StreamController._closeUnchecked (dart:async/stream_controller.dart:631:7)
#88     _StreamController.close (dart:async/stream_controller.dart:624:5)
#89     _Socket._onData (dart:io-patch/socket_patch.dart:1838:21)
#90     _rootRunUnary (dart:async/zone.dart:1138:13)
#91     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#92     _CustomZone.runUnaryGuarded (dart:async/zone.dart:933:7)
#93     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:338:11)
#94     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:265:7)
#95     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:766:19)
#96     _StreamController._add (dart:async/stream_controller.dart:642:7)
#97     _StreamController.add (dart:async/stream_controller.dart:588:5)
#98     new _RawSocket. (dart:io-patch/socket_patch.dart:1386:35)
#99     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:892:18)
#100    _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#101    _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#102    _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#103    _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

Hi @m18210875071
Could you please your flutter run --verbose
I see that you are using several 3rd party plugins
could you provide your pubspec.yaml as well
or if possible a reproducible minimal code sample.
Thank you

name: paasapp
description: An office application of Jili
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
国际化
flutter_localizations:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
网络
dio: 3.0.7
检查网络
connectivity: ^0.4.1+1
socket
web_socket_channel: ^1.1.0
json
json_annotation: 2.0.0
通信
event_bus: 1.0.1
加密
crypto: 2.1.3
上拉刷新，下拉加载更多
flutter_easyrefresh: ^2.0.4
图片压缩
flutter_image_compress: 0.6.4
保存图片到相册
image_gallery_saver:
path: ./lib/comm/widget/image_gallery_saver
相机相册
image_picker: ^0.6.1+3
获取本地路径
path_provider: 1.5.1
加载loading
flutter_spinkit: 3.1.0
包信息
package_info: 0.3.2
toast
fluttertoast: 3.0.1
数据管理层
provider: ^3.1.0+1
卡片滑动
flutter_swiper: ^1.1.6
下拉菜单
gzx_dropdown_menu: ^1.0.3
时间选择器
flutter_datetime_picker: ^1.2.6
选择器 支持自定义数据格式和时间选择
flutter_picker: ^1.1.0
时间选择器-iOS风格 支持自定义时间格式
flutter_cupertino_date_picker: ^1.0.12
flustars: ^0.2.6+1
left_scroll_actions: any
生成二维码
qr_flutter: ^3.1.0
短信/电话
url_launcher:
扫描二维码
flutter_qr_reader: ^1.0.3
权限
permission_handler: ^4.0.0
图表
charts_flutter: ^0.8.1
侧滑
flutter_slidable: ^0.5.4
ShareSDK
sharesdk_plugin:
amap地图整合
amap_all_fluttify: ^0.9.0
极光推送
jpush_flutter:
git:
url: git://github.com/jpush/jpush-flutter-plugin.git
ref: master
日历
flutter_calendar_carousel: ^1.4.10
svg
flutter_svg: ^0.15.0
CRM用到的库
大图预览
photo_view: 0.4.2
可拖动Widget库
reorderables:
绘制地图时用
decorated_flutter: ^0.10.0
图表库
fl_chart: ^0.6.0
相册
photo: ^0.4.5
悬停式header
sticky_headers: ^0.1.8
photo_manager: ^0.4.8
dev_dependencies:
flutter_test:
sdk: flutter
build_runner: 1.1.1
json_serializable: 2.0.0
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
assets:
- assets/
#tabbar
- assets/icon_tab_app_sel.png
- assets/icon_tab_app.png
- assets/icon_tab_home_sel.png
- assets/icon_tab_home.png
- assets/icon_tab_integral_sel.png
- assets/icon_tab_integral.png
- assets/icon_tab_mine_sel.png
- assets/icon_tab_mine.png
- assets/icon_tab_work_sel.png
- assets/icon_tab_work.png
# login
- assets/icon_invite_bg.png
- assets/icon_problem.png
# work
- assets/icon_organization.png
- assets/icon_organization_circular.png
- assets/icon_apply.png
- assets/icon_approval.png
- assets/icon_attendance.png
- assets/icon_gq.png
- assets/icon_jidou.png
- assets/icon_leave.png
- assets/icon_notice.png
- assets/icon_overtime.png
- assets/icon_patch.png
- assets/icon_remind.png
- assets/icon_report.png
- assets/icon_travel.png
- assets/icon_address_book.png
- assets/icon_phone_hollow.png
- assets/icon_qrcode_hollow.png
- assets/icon_sms_hollow.png
- assets/icon_sms.png
- assets/icon_wechat_hollow.png
- assets/icon_wechat.png
- assets/icon_telephone_hollow.png
- assets/icon_add_gray.png
# CRM Related
- assets/crm_arrow_down.png
- assets/crm_card_company.png
- assets/crm_card_location.png
- assets/crm_card_phone.png
- assets/crm_sign_in.png
- assets/crm_telphone.png
- assets/crm_write_record.png
- assets/crm_fliter.png
- assets/crm_phone_call.png
- assets/crm_plus.png
- assets/crm_search.png
- assets/crm_sort.png
- assets/crm_location.png
- assets/crm_delete_photo.png
- assets/crm_upload_photo.png
- assets/crm_drag.png
- assets/crm_green_add.png
- assets/crm_red_delete.png
- assets/crm_sort_common.png
- assets/crm_sort_down.png
- assets/crm_sort_up.png
- assets/crm_item_selected.png
- assets/crm_arrow_forward.png
- assets/crm_camera.png
- assets/crm_chat.png
- assets/crm_store.png
- assets/crm_website.png
- assets/crm_product.png
- assets/crm_refresh.png
- assets/crm_store_default.png
- assets/crm_orange_add.png
- assets/crm_selected.png

- assets/crm_active_member.png
- assets/crm_activity_red.png
- assets/crm_activity.png
- assets/crm_card_fission.png
- assets/crm_company_manage.png
- assets/crm_deliver_redpacket.png
- assets/crm_deliver.png
- assets/crm_distribution.png
- assets/crm_home_arrow_big.png
- assets/crm_home_arrow_small.png
- assets/crm_home_bg.png
- assets/crm_home_setting.png
- assets/crm_invite_red.png
- assets/crm_invite_seller.png
- assets/crm_invite.png
- assets/crm_scan_spend.png
- assets/crm_share_red.png
- assets/crm_share.png
- assets/crm_ticket_red.png
- assets/crm_ticket.png
- assets/blank_white.png
- assets/crm_sign_in_blue.png
- assets/crm_phone_detail.png
- assets/crm_client_follow.png
- assets/crm_ylb_bg.png
- assets/crm_poster_bg.png
- assets/crm_member_share_bg.png
- assets/crm_member_edit.png
- assets/crm_member_vip.png
- assets/crm_vip_bg_big.png
- assets/crm_vip_bg_small.png
- assets/crm_check.png
- assets/crm_success.png
- assets/crm_info.png
- assets/crm_face2face.png
- assets/crm_wechat_session.png
- assets/crm_wechat_timeline.png
- assets/crm_ticket_bg.png

- assets/test.json
- assets/moment.json
- assets/follow_ups.json
- assets/chat.json

Hi @m18210875071
Could you please your flutter run --verbose
I see that you are using several 3rd party plugins
could you provide your pubspec.yaml as well
or if possible a reproducible minimal code sample.
Thank you

name: paasapp
description: An office application of Jili
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
dio: 3.0.7
connectivity: ^0.4.1+1
web_socket_channel: ^1.1.0
json_annotation: 2.0.0
event_bus: 1.0.1
crypto: 2.1.3
flutter_easyrefresh: ^2.0.4
flutter_image_compress: 0.6.4
image_gallery_saver:
path: ./lib/comm/widget/image_gallery_saver
image_picker: ^0.6.1+3
path_provider: 1.5.1
flutter_spinkit: 3.1.0
package_info: 0.3.2
fluttertoast: 3.0.1
provider: ^3.1.0+1
flutter_swiper: ^1.1.6
gzx_dropdown_menu: ^1.0.3
flutter_datetime_picker: ^1.2.6
flutter_picker: ^1.1.0
flutter_cupertino_date_picker: ^1.0.12
flustars: ^0.2.6+1
left_scroll_actions: any
qr_flutter: ^3.1.0
url_launcher:
flutter_qr_reader: ^1.0.3
permission_handler: ^4.0.0
charts_flutter: ^0.8.1
flutter_slidable: ^0.5.4
sharesdk_plugin:
amap_all_fluttify: ^0.9.0
jpush_flutter:
git:
url: git://github.com/jpush/jpush-flutter-plugin.git
ref: master
flutter_calendar_carousel: ^1.4.10
flutter_svg: ^0.15.0
photo_view: 0.4.2
reorderables:
decorated_flutter: ^0.10.0
fl_chart: ^0.6.0
photo: ^0.4.5
sticky_headers: ^0.1.8
photo_manager: ^0.4.8
dev_dependencies:
flutter_test:
sdk: flutter
build_runner: 1.1.1
json_serializable: 2.0.0
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
assets:
- assets/

`
name: paasapp
description: An office application of Jili
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
dio: 3.0.7
connectivity: ^0.4.1+1
web_socket_channel: ^1.1.0
json_annotation: 2.0.0
event_bus: 1.0.1
crypto: 2.1.3
flutter_easyrefresh: ^2.0.4
flutter_image_compress: 0.6.4
image_gallery_saver:
path: ./lib/comm/widget/image_gallery_saver
image_picker: ^0.6.1+3
path_provider: 1.5.1
flutter_spinkit: 3.1.0
package_info: 0.3.2
fluttertoast: 3.0.1
provider: ^3.1.0+1
flutter_swiper: ^1.1.6
gzx_dropdown_menu: ^1.0.3
flutter_datetime_picker: ^1.2.6
flutter_picker: ^1.1.0
flutter_cupertino_date_picker: ^1.0.12
flustars: ^0.2.6+1
left_scroll_actions: any
qr_flutter: ^3.1.0
url_launcher:
flutter_qr_reader: ^1.0.3
permission_handler: ^4.0.0
charts_flutter: ^0.8.1
flutter_slidable: ^0.5.4
sharesdk_plugin:
amap_all_fluttify: ^0.9.0
jpush_flutter:
git:
url: git://github.com/jpush/jpush-flutter-plugin.git
ref: master
flutter_calendar_carousel: ^1.4.10
flutter_svg: ^0.15.0
photo_view: 0.4.2
reorderables:
decorated_flutter: ^0.10.0
fl_chart: ^0.6.0
photo: ^0.4.5
sticky_headers: ^0.1.8
photo_manager: ^0.4.8
dev_dependencies:
flutter_test:
sdk: flutter
build_runner: 1.1.1
json_serializable: 2.0.0
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
assets:
- assets/
`

Hi @m18210875071
Could you please your flutter run --verbose
I see that you are using several 3rd party plugins
could you provide your pubspec.yaml as well
or if possible a reproducible minimal code sample.
Thank you

name: paasapp
description: An office application of Jili
version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
dio: 3.0.7
connectivity: ^0.4.1+1
web_socket_channel: ^1.1.0
json_annotation: 2.0.0
event_bus: 1.0.1
crypto: 2.1.3
flutter_easyrefresh: ^2.0.4
flutter_image_compress: 0.6.4
image_gallery_saver:
path: ./lib/comm/widget/image_gallery_saver
image_picker: ^0.6.1+3
path_provider: 1.5.1
flutter_spinkit: 3.1.0
package_info: 0.3.2
fluttertoast: 3.0.1
provider: ^3.1.0+1
flutter_swiper: ^1.1.6
gzx_dropdown_menu: ^1.0.3
flutter_datetime_picker: ^1.2.6
flutter_picker: ^1.1.0
flutter_cupertino_date_picker: ^1.0.12
flustars: ^0.2.6+1
left_scroll_actions: any
qr_flutter: ^3.1.0
url_launcher:
flutter_qr_reader: ^1.0.3
permission_handler: ^4.0.0
charts_flutter: ^0.8.1
flutter_slidable: ^0.5.4
sharesdk_plugin:
amap_all_fluttify: ^0.9.0
jpush_flutter:
git:
url: git://github.com/jpush/jpush-flutter-plugin.git
ref: master
flutter_calendar_carousel: ^1.4.10
flutter_svg: ^0.15.0
photo_view: 0.4.2
reorderables:
decorated_flutter: ^0.10.0
fl_chart: ^0.6.0
photo: ^0.4.5
sticky_headers: ^0.1.8
photo_manager: ^0.4.8
dev_dependencies:
flutter_test:
sdk: flutter
build_runner: 1.1.1
json_serializable: 2.0.0
flutter:
uses-material-design: true
assets:
- assets/

Hi @m18210875071
crash happened because of library not found for -ljcore-ios-2.1.8
try to change 2.1.8 to 2.2.0 as here
Does it help?

Hi @m18210875071
crash happened because of library not found for -ljcore-ios-2.1.8
try to change 2.1.8 to 2.2.0 as here
Does it help?

Thank you very much for helping me to solve the problem that has troubled me for a long time


build: Fix up missing changes from package.json files

As noted in #15815, the main/next merges have apparently been causing some package.json changes to get lost, most likely due to merge conflicts that were merged incorrectly.
This PR attempts to correct the problem. I did the following:

Reset the lockfile and all package.json files to the state they were in commit 6d2d570c46577319ac132f671d8881829c6cdc52 - the commit right before the main/next convergence.
Manually merged in the package.json changes from commit ef6679201c66201de6cd7c7c140969bae7514fae - the latest in next. I did this manually and reviewed every change. I still may have made a mistake.
Manually reset the previous version for typetests to 4.1.0 - that was the most commonly used version, though a couple of packages were using 4.0.0. This isn't super important since the typetests will all be reset as part of the release(s), but I want to get back into a state matching the old main as much as possible at the moment.

The changes in here look good, and restore some of the things that were lost in merges in next. I can't confirm that this restores everything it should (I don't have a good way to review for that), but it seems like an improvement, so I am approving.


Extend test for EbayDialog

As a follow up for bugfix on aria-hidden: https://github.corp.ebay.com/React/ebayui-core-react/pull/120#issuecomment-1329665
The test should test if the aria-hidden is set accordingly in case of dialog is open and closed. Possible test case:

mount dialog with other divs

mount(
  <>

    <EbayDialog>...</EbayDialog>

  </>
)

Assert no aria-hidden on test divs
trigger dialog to show
Assert aria-hidden=true on test divs
trigger dialog to close
Assert no aria-hidden on test divs

Not an issue anymore since @HenriqueLimas  has replaced our custom ariaHidder with makeup js


Add support for Wox

Hello,
Wox is an effective launcher for Windows. You can learn more about the project on its repository.
Right now, I have the support for the dark and the light template (here with the solarized scheme):

I created them with wox's theme builder with inspiration from Alfred (1 2 3 4). I chose 0A as accent color but any accent color will fit (I found 0C really convenient too).

Sounds awesome.
If we can make this happen, it'll make this tool much more compelling for Windows users.

@alexbooker
Thank you. I added the light theme too :) (Lumosh powa \o/)

More pics
Paraiso:

Flat:

I need schemer to run them all! ;)


IE 11 gives different results to chrome

MathML
<math   xmlns="http://www.w3.org/1998/Math/MathML">
          <mstyle>
            <mi>f</mi>
            <mrow>
              <mo>(</mo>
              <mi>a</mi>
              <mo>)</mo>
            </mrow>
            <mo>=</mo>
            <mfrac>
              <mn>1</mn>
              <mrow>
                <mn>2</mn>
                <mi>π
                  <!-- π -->
                </mi>
                <mi>i</mi>
              </mrow>
            </mfrac>
            <msub>
              <mo>∮</mo>
              <mrow>
                <mi>γ</mi>
              </mrow>
            </msub>
            <mfrac>
              <mrow>
                <mi>f</mi>
                <mo>(</mo>
                <mi>z</mi>
                <mo>)</mo>
              </mrow>
              <mrow>
                <mi>z</mi>
                <mo>−</mo>
                <mi>a</mi>
              </mrow>
            </mfrac>
            <mi>d</mi>
            <mi>z</mi>
          </mstyle>
        </math>

IE 11
f ( a ) = 12 π i ∮ γ f ( z ) z − ADZ
Chrome
f left parenthesis a right parenthesis equals start fraction one over two pi i end fraction contour integral sub gamma start fraction f left parenthesis z right parenthesis over z minus a end fraction d z

Thanks for the feedback.
Could you give me some details, on which version and how you are using sre? I.e., is it the latest via npm or something compiled directly from the github repo and if so, which target have you compiled?
Taking a guess on what the problem could be: IE has no xpath implementation (the one in Edge is incomplete) and sre relies on that. Therefore in the version we currently use with MathJax, I include wgxpath. However, that is not exposed via npm yet.
Could you please test you expression here and check the result in the first speech attribute in the enriched MathML expression below, whether this gives you the expected speech string on IE11.

I have compiled pull#37 from https://github.com/zorkow/speech-rule-engine.git and i have included wgxpath.
The output from IE is "f left-parenthesis a right-parenthesis equals StartFraction 1 Over 2 pi i EndFraction contour-integral Underscript gamma Endscripts StartFraction f left-parenthesis z right-parenthesis Over z minus a EndFraction d z"
The only think I did notice was when i do a build I get sre_browser and you are using sre_mathjax on the page. Could this be the issue?

The only think I did notice was when i do a build I get sre_browser and you are using sre_mathjax on
the page. Could this be the issue?

That is indeed the issue. The browser goal is from a time before we started experimenting with MathJax in IE/Edge.
However, I have been revamping the API anyway --- currently in the develop branch --- and wanted go over the goals in the Makefile before merging with master. Hopefully that will be ready by the end of the week. I'll close the issue once this is done.

Thanks For the help

I have just merged develop into master. sre_browser now correctly loads wgxpath (tested with Win 7, IE11).


Provide Maven Site

A Maven generated Plugin Site would be beneficial because it automatically documents all goals and its parameters in a standard way. The result could be hosted e.g with Github Pages.

There are some hints how to automate the publishing process at https://blog.soebes.de/blog/2015/06/12/making-github-page-for-mojohaus/


Unknown Dialect when query against and undefined explore

Test in nomodel.spec.malloy
        explore: foo is table('malloytest.state_facts'){primary_key: state}
        query: foox->{aggregate: c is count()}

Smallest model for this is just query: x->{ group_by: y }

Fixed 75e06687815d4655f3da79827818c92e71758d38


Make SK text and embedding generator wrappers public

Currently it's possible to inject Semantic Kernel classes into KM only using

IKernelMemoryBuilder.WithSemanticKernelTextGenerationService
IKernelMemoryBuilder.WithSemanticKernelTextEmbeddingGenerationService
IServiceCollection.AddSingleton(instance)
IServiceCollection.AddSingleton(instance)

However, it's not possible to create an instance of Semantic Kernel classes directly without writing a custom wrapper class first. Since the project already includes such wrapper, as internal classes, this PR changes them to public classes, to reduce the amount of code to write.
Classes:

SemanticKernelTextGenerator
SemanticKernelTextEmbeddingGenerator

See also https://github.com/microsoft/kernel-memory/pull/801


Problem with styled componets

I'm having trouble using this library with Styled Components, has anyone had this problem?

can you upload example code?

Styled use px as default unit.
No working (Only styled)
export const Text = styled.Text`
  flex: 1;
  font-weight: bold;
  font-size: RFValue(18, 580);
  opacity: 0.78;
`;

// index.js
<Text allowFontScaling>
          {text}
</Text>

Solution:
Working (Mix styled + react style)
// style.js
export const Text = styled.Text`
  flex: 1;
  font-weight: bold;
  opacity: 0.78;
`;

// index.js
<Text allowFontScaling style={{fontSize: RFValue(18, 580)}}>
          {text}
</Text>

Styled use px as default unit.
No working (Only styled)
export const Text = styled.Text`
  flex: 1;
  font-weight: bold;
  font-size: RFValue(18, 580);
  opacity: 0.78;
`;

// index.js
<Text allowFontScaling>
          {text}
</Text>

Solution:
Working (Mix styled + react style)
// style.js
export const Text = styled.Text`
  flex: 1;
  font-weight: bold;
  opacity: 0.78;
`;

// index.js
<Text allowFontScaling style={{fontSize: RFValue(18, 580)}}>
          {text}
</Text>

Your code is wrong, try this:
export const Text = styled.Text`
   flex: 1;
   font-weight: bold;
   font-size: ${RFValue(18, 580)}px;
   opacity: 0.78;
`;

@TiagoDanin  Have you tried?    font-size: ${RFValue(18, 580)}px;

Your code is wrong, try this:
@albertoammar it's not wrong... this is example of how some people expect can use ;)

@TiagoDanin Have you tried? font-size: ${RFValue(18, 580)}px;
Yes this also work! but dp is different from px, recommend use in style prop.

I don't see it as a problem, just commented so you could know why of no working with styled.


Feature: Enrich harbor_project data source

Is your feature request related to a problem? Please describe.
It would be really useful to be able to determine if a project is a proxy cache project in Terraform (especially in combination with this feature request)
This would allow a lot more permissions to be set dynamically, and make the provider much more flexible.
Describe the solution you'd like
Add a new attribute to harbor_project data source, which will indicate if it is a proxy cache project or not. Something like type: proxy_cache

Hi @slushysnowman,
Thank you for the feature request, it will be available with release v3.10.0.

same for this, really appreciated @flbla !


Update ExpansionTile to support Material 3

https://m3.material.io/components/lists/guidelines#f6fe9c4e-7498-420a-b820-d12a2b59fc99

cc: @guidezpl
Can you please add this to the Material 3 issue?

This is reverted in https://github.com/flutter/flutter/pull/120300

@HansMuller
Do you propose some sort of configuration to keep the primary color for the title and subtitle widgets?
I'm open to ideas to reland this.


Flaky tests

Tests in test_yahoo.py can be flaky (SEE following comment for update). The module includes integration tests of public methods (for example, PricesYahoo.get) that call the yahoo API. These tests are not isolated, rather they are susceptible to inconsistent returns from the API, not least the 'missing prices for certain sessions' issue explained here (NB the issue arises as result of the high frequency of requests associated with executing the full test suite, it does not affect general usage or tests executed in isolation).
If one of these tests fails, either:

it's still susceptible to flakylisted sessions - ~the test needs revising~ EDIT - migrate it to test_base_prices.py and redefine to get prices from a locally stored resource.
it's failing on a nature of inputs that it hasn't been tested against before (or if it was it wasn't addressed). In which case:

either there's a bug in the code that needs fixing.
or there's a bug in the test that needs fixing.

Over time these flaky tests were weeded out as bugs were caught and the moderation of test inputs was tightened up (for example, through the use of test_yahoo.get_valid_sessions). However, some flaky tests WILL remain and it remains a matter of ~investigating~ migrating any of them that fail due to missing price data ~in order that another weed can be pulled out~.
Separately, tests of test_daterange.py employ hypothesis which subjects the tests to dynamic inputs. Whilst flaky tests here are now rare, there's always the possibility of a failure on an combination of inputs that hypothesis hadn't tried before. Again, it's a matter of investigating there and then and either fixing the code being tested or the test itself.

Recently there have been occasions where during execution of the full test suite the yahoo API has failed to return prices for any indice over a requested period. No choice but to migrate tests to use locally stored resources. Migration details here.


How to make expect().toContain() behaves like expect().toContainEqual()

Using .toContain() in this code will fail (because it does strict equality on the object):
it('test A', () =>
   expect([{a: 1}, {b: 2}]).toContain({a: 1})
)

However, using toContainEqual() will work (because it does recursive equality on each object property):
it('test B', () =>
   expect([{a: 1}, {b: 2}]).toContainEqual({a: 1})
)

But I want toContain() to behave like toContainEqual() (to match jasmine behavior).
I tried to write the following line before all tests, but it didn't work:
expect.toContain = expect.toContainEqual;

Any idea how to temporarily make expect().toContain() behaves like expect().toContainEqual()?

Maybe just use asymmetric matchers?

@thymikee thanks for your suggestion. Using asymmetric matcher will work (and it is compatible with jasmine):
it('test A', () =>
   expect([{a: 1}, {b: 2}]).toEqual(expect.arrayContaining([{a: 1}]))
)

But as you can see, the construct is less readable than before.
I still wonder if I can use .toContain() and make it behaves like toContainEqual().

You can use it, as long as you compare primitives. It's just as you said and it works this way: http://facebook.github.io/jest/docs/expect.html#tocontainitem. And changing it to work with objects would be a breaking change (there's a chance somebody relies on this strict comparison behaviour).
Just use toContainEqual(), it's made just for that case and it's not that hard to change, right?

No, it's not hard at all to change all .toContain() to .toContainEqual(). But I want to run the same set of tests in the browser via karma + jasmine. Thats why I want to keep my test code compatible in both situations.

Maybe you can a flag option in the initialization of jest to change the behavior of .toContain() so that it will not break existing codes.

So you should be able to hack it like that:
expect.extend({
    toContain(collection, value) {
      // code for toContainEqual
    }
})

Implementation is here.
And here's more on expect.extend

Tried to follow your suggestion:
expect.extend({
    toContain(collection, value) {
        const collectionType = this.utils.getType(collection);
        let converted = null;
        if (Array.isArray(collection)) {
            converted = collection;
        } else {
            try {
                converted = Array.from(collection);
            } catch (e) {
                throw new Error(
                    this.utils.matcherHint('[.not].toContainEqual', 'collection', 'value') +
                        '\n\n' +
                        `Expected ${('collection')} to be an array-like structure.\n` +
                        this.utils.printWithType('Received', collection, printReceived),
                );
            }
        }
        const pass = converted.findIndex(item => equals(item, value, [this.utils.iterableEquality])) !== -1;
        const message = pass ? () =>
            this.utils.matcherHint('.not.toContainEqual', collectionType, 'value') +
            '\n\n' +
            `Expected ${collectionType}:\n` +
            `  ${this.utils.printReceived(collection)}\n` +
            `Not to contain a value equal to:\n` +
            `  ${this.utils.printExpected(value)}\n`
        : () =>
            this.utils.matcherHint('.toContainEqual', collectionType, 'value') +
            '\n\n' +
            `Expected ${collectionType}:\n` +
            `  ${this.utils.printReceived(collection)}\n` +
            `To contain a value equal to:\n` +
            `  ${this.utils.printExpected(value)}`;
        return {message, pass};
    }
});

But got this error:
ReferenceError: equals is not defined

Because of equals() in this line:
const pass = converted.findIndex(item => equals(item, value, [this.utils.iterableEquality])) !== -1;

But can't I achieve this in a simpler way? something like:
expect.extend({
  toContain(collection, value) {
    return ???????.toContainEqual(collection, value);
  }
})

Since Jest 20 you can use this.equals
Highly unstable solution, but it works:
expect.extend({
  toContain(collection, value) {
    return require('jest-matchers/build/matchers.js').toContainEqual(
      collection,
      value
    );
  }
});

expect([{a: 'a'}]).toContain({a: 'a'});

Please don't overwrite toContain. We will not be renaming the matcher.

@cpojer I guess this is about comparing Jest vs Karma+Jasmine and see what's faster/better, so I see it as a temporary hack.  It worked!
👍👍👍👍👍👍👍
@cpojer We are not trying to permanently overwrite toContain(). I don't expect the behaviour of toContain() to change in the future either. I just need a temporary and elegant solution to use a single test code base for both environments.


[Bug]: Not able to Create an API query for an Authenticated API that has only Staging Environment set

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I create an Authenticated API by setting the Staging environment the API is saved. However, I can't create an API Query for this. The query creation fails as shown below:

Steps To Reproduce

Create an Authenticated API, and Set the API using the Staging environment. The production env is left blank.
The Datasource is saved successfully.
Click the New API + button to add a query
The query cannot be created and fails with an error message:Unable to create API. Try adding a URL to the datasource.

Public Sample App
No response
Environment
Release
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Self-hosted

@jnikhila , it is not clear from the attached screenshot, but which was the active environment when you attempted to create a new API?

aside: if the active env is prod and the config only exists in staging (or vice versa), we should either:

deactivate the new api button (not a good solution IMO, because the reason can be mysterious to the user)
change the error message to include the fact that config doesn't exist in the selected or active environment (whichever is the accurate term)

@rohan-arthur - the active environment was staging. The production doesn't have any configuration. My thought was that I can configure one environment as per my need in different instances - like staging instance will have configuration for staging environment that is connecting to a stage db. Similarly, if I want production then I will set up db details in production environment. However, the error is thrown when there is no configuration in production.
Also, I don't understand if there is a way to set up active environment. I presume an active environment to be the one which has configuration. Am I missing something here?

@jnikhila by active environment I mean the one that is selected (check screenshot in my previous comment)

Bumping this issue up to prod because it should have made it's way there by now if it was not fixed


e2e test: remove debug fmt.Println 🤕

Changes
:bowing_man: :bowing_man: :bowing_man: :bowing_man: :bowing_man:
cc @abayer
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ :no_good_man: ] Includes tests (if functionality changed/added)
[ :no_good_man: ] Includes docs (if user facing)
[:ok:] Commit messages follow commit message best practices

See the contribution guide
for more details.

/lgtm


Implement 'title' directive argument

*Issue number of the reported bug or feature request: Closes #2
Describe your changes
Added :title: directive argument that, when provided, the <prog> - CLI interface title is replaced by the value, and if empty is not included.
Testing performed
Tested in two different new tests and manually in my own project.
Additional context
Let me know if you want another name for this argument.

Ok :+1: Let me update this pull

https://github.com/gaborbernat/sphinx-argparse-cli/releases/tag/1.2.0

Release in progress under https://github.com/gaborbernat/sphinx-argparse-cli/actions/runs/540540089

Release in progress under...

Perfect, thanks :clap:


Cannot construct tcp_stream following the simple HTTP client example

net::io_context ioc; tcp::resolver resolver(ioc); beast::tcp_stream stream(ioc);
This does not compile due to no matching constructor for tcp_stream.

It's compiling on godbolt for MSVC too.
https://godbolt.org/z/YeWEovxhW
Are you able to confirm for me that the code here is as you would expect?

Ah okay. For some reason Visual Studio identifies it as an error and gives a red squiggle in the editor but I can actually compile it with MSVC (which I didn't try before hand as I have never come across a situation like this). Is this a VS Intellisense bug then do you think?


Videos from a local folder are not being shuffled

General troubleshooting tips
Before logging an issue please check that:

[x] You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
[x] Your issue isn't already mentioned in our issues. You may find a workaround there or a similar request already made.
[x] Your problem isn't mentioned in the troubleshooting page.

If none of this fixes your issue, tell us about the problem you are experiencing or the feature you'd like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:

[x] Mac model: Mac mini 2018
[x] macOS version: 14.1.1 (23B81)
[x] Monitor setup: Two monitors, one 1920x1080 and one 2560x1440

If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
Videos from a local folder don't get shuffled/randomized. The video the screensaver starts with is always the same one.

Hi @Piipperi
Can you

go into Aerial's Settings, Advanced tab, scroll down, enable logs
launch the screen saver 3 or 4 times (launch, wait for say 10 seconds, exit, wait a bit, relaunch etc)
go back to same place in Aerial's settings and attach the AerialLog.txt here

Thanks, this will let me have a look at what's happening precisely

For some reason it works now, I had to switch a few times between the locations and now it's randomized like it should.

No worries, let me know if it happens again, sometimes it's just random luck. Take care.


Could you add a usage example?

That would help, I'd like to use it similarly to https://github.com/psych0der/pngquantjs
And thanks for that work

added demo #2


Update and rename bug_report.md to bug_report.yaml

Updating issue template to new format
Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

The changes passed @kevin-atx 's code review


Mock server response is always a 404

Partial copy of my API Blueprint:
## Group Collection [/groups?{onlyRemote}]

### List all active Groups [GET]

+ Parameters
    - onlyRemote (optional, boolean) - Only include groups with remote mappings
      - Default: false

+ Response 200 (application/json)
    - Attributes
        - data (array[Group])

I start the mock server using:
$ snowboard mock -i api-description.apib
Mock server is ready. Use <IP_ADDRESS>:8087
Available Routes:
GET     200     groups/:id
POST    201     groups/:id
GET     200     groups?:onlyRemote
GET     200     rosters/:id
GET     200     rosters

And every request results in a 404:
$ curl -i "http://<IP_ADDRESS>:8087/rosters"
HTTP/1.1 404 Not Found
Date: Tue, 11 Apr 2017 20:30:45 GMT
Content-Length: 0
Content-Type: text/plain; charset=utf-8

Hi @shadowhand, I Just published a fix for this issue. You can upgrade snowboard to v0.6.2.

Still getting 404s for every URL after upgrading.

That's strange. Can you post sample api blueprint? So I can try to reproduce here.

FORMAT: 1A
HOST: https://api.acme.net/
Acme
The complete API for Acme application.
Group Patient Groups
Resources related to patient groups.
Group [/groups/{id}]

Attributes

id: 1 (number)
name: Segment 1 (string, required)
remote_id: ABCD (string, nullable)

Parameters

id: 1 (number) - Group identifier

Fetch a Group [GET]

Response 200 (application/json)

Attributes

data (Group)

Create a Group [POST]

Request (application/json)

Attributes (Group Create)

Response 201 (application/json)

Attributes

data (Group Created)

Group Collection [/groups?{onlyRemote}]
List all active Groups [GET]

Parameters

onlyRemote (optional, boolean) - Only include groups with remote mappings

Default: false

Response 200 (application/json)

Attributes

data (array[Group])

Group Patient Rosters
Resources related to patient rosters.
Roster [/rosters/{id}]

Attributes

id: 1 (number, required)
name: North Region (string, required)

Parameters

id: 1 (number) - Roster identifier

Fetch a Roster [GET]

Response 200 (application/json)

Attributes

data (Roster)

Roster Collection [/rosters]
List all available Rosters [GET]

Response 200 (application/json)

Attributes

data (array[Roster])

Data Structures
Group Create (object)

name: Segment 2 (string, required)
remote_id (nullable, optional)

Group Created (object)

id: 2 (number)
Include Group Create

@subosito ^ see gist.

Hi @shadowhand can you test using https://github.com/subosito/snowboard/commit/f160439551d8804902a74a34b0b9b3a91d65d0e5 ?
There is an issue with url path resolution, so:
# previously
-----------------------
HOST: https://api.acme.net/
## Group [/groups/{id}]
===> will produce: groups/:id (which unfortunately not working)

to make it work:

HOST: https://api.acme.net <- no trailing slash
## Group [/groups/{id}]
===> will produce: /groups/:id (it's working)

The commit fixes above issue. So both HOST with trailing and without trailing slash will be handled properly.
Going to push a new release soon.

@subosito can I run it locally with docker somehow? I don't have Go installed on this machine.

Sure, you can use docker. Docker image is always pointing to master.

@subosito well, I'm not Docker expert. I managed to get it built and started, but I can't figure out how to connect to it. I assumed I would be able to do:
docker build -t snowboard .
docker run -it --rm -v $PWD:/doc snowboard mock -i api-description.apib
open "http://$(docker-machine ip):8087/rosters"

But no 🎲 , fails to to connect. Any idea what I am doing wrong?

@shadowhand You need to let snowboard binding to <IP_ADDRESS> so it can be accessed on docker host. You can try following:
docker run -it --rm -v $PWD:/doc -p 8087:8087 snowboard mock -b <IP_ADDRESS>:8087 -i api-description.apib
open "http://$(docker-machine ip):8087/rosters"

@subosito perfect, that did the trick. I have confirmed that this is working as expected now!

I have the Same 404 issue (not using the trailing slash)
Just using an index.html and app.js with AJAX 'GET' Method


AWS Officially releases native DynamoDB autoscaling

And just a couple days after I forked your project and deployed it...
https://aws.amazon.com/blogs/aws/new-auto-scaling-for-amazon-dynamodb/

It seems like Amazon's service doesn't really take throttling into account, however. We've experienced some issues with it.

And just after months of me reworking it.. 😣

@tmitchel2 I come here to thank you for your work with this OS project. 👏  I am continuing using this, until I find AWS autoscaling mature enough and heavily tested.
Probably auto-backup will come next from AWS?

@mseank I think that if you have autoscaling enabled, there's a new burst capability that unused provisioned capacity from the past 5 minutes can be consumed in order to avoid throttling. Then hopefully the autoscaling kicks in and boosts the provisioned capacity enough.

@efenderbosch no I don't think your right there.  The burst capability is something that has been there all along, it means your consumed capacity can burst above the provisioned for a very short period based upon a usage algorithm

Like @goncaloneves, I wanted to thank-you for this project. We're using it in a heavy production work-load and it's always been reliable. We wont be moving to AWS's auto-scaling until it's implemented some more of the features of this project at the very least!

@schodemeiss appreciate it.

My team tried out the Amazon version, but we've decided to come back to this. It's more stable and easily used. Thanks, @tmitchel2

@mseank That's interesting, would you able to comment on specific stability issues?  I did have a newer version in the works with better integrations and a potential paid for version but I'm on the fence about completing it.

@tmitchel2 Part of it is perhaps that the documentation for Amazon's is not very in-depth. Yours is much easier to follow. It kind of goes in line with what I was saying earlier in this thread, how it is difficult to control throttling with Amazon's in-house version. It was scaling, but when we would throttle, it wouldn't really register or do much of anythig. It would still be hitting our apparent set percentage, but not realizing that we weren't where we wanted to be. It also seems to struggle scaling down for some reason; again, this may be due to our setting the target utilization incorrectly.
They need more fields and better descriptions as to what they mean. The fields for your version are much more accessible and easily editable.

Going to use this issue to record commentary regarding Amazons implementation, good or bad.
For starters it seems like here they are suggesting a full 5 minutes of load to get the scaling to trigger https://forums.aws.amazon.com/thread.jspa?threadID=259029&tstart=0

I think we might be coming back to this solution. The official AWS solution doesn't seem to react quickly enough to increased capacity requirements. We'll get spikes of throttles. It also doesn't seem to scale down as often as it should. I've seen periods of more than 12 hours where tables were not scaled down.
Additionally, since the AWS solution uses CloudWatch alarms, you will see an increase in that portion of your bill. Since this solution queries the table's capacity metadata and makes changes itself, there's no cost other than the Lambda function time.

We are also still using this project for many of the reasons mentioned above.


KOGITO-9617: Remove the Extended Services from Serverless Logic Web Tools

Jira: https://issues.redhat.com/browse/KOGITO-9617
❗ Note: This PR depends on https://github.com/kiegroup/kie-tools/pull/1872, please merge after this. :exclamation:
Description:
The only reason we need the Extended Services in the Serverless Logic Web Tools is to use the CORS Proxy we have inside it to interact with OpenShift and Service Registries without being blocked by CORS policies.
After this PR , the CORS Proxy will be moved from the Extended Services to a new package, which will be deployed in favor of our current git-cors-proxy deployment.
The goal of this task is to remove the Extended Services from Serverless Logic Web Tools, which includes making changes in the code itself, quickstart guides, env vars, and GitHub workflows.
Since we have many references of the Extended Services in the docs, updating them is also part of this task.

Please hold the merge of this PR until we are closer to kie-tools 0.32.0 release.

As KIE Tools 0.32.0 release is planned for this week, this PR is ready to be merged. Thanks!

@krisv @ederign please approve

@kaldesai We've only removed unnecessary information here. Could you please take a look?

All the changes look good to me. Just one minor suggestion. Thank you!

Thank you @kaldesai for your suggestion


[Feature] Support Timescale DB

Timescale is essentially an extension of Postgres, with its own additional functionality like continuous queries.
Features required:

support postgres extensions https://github.com/ariga/atlas/issues/520
inspect/create/convert hypertable
support postgres materialized views as continuous aggregates

There's probably more but these would probably be the most common.

In fact support for Timescale extension was the first thing I checked. I guess it will be quite a challenge though.


WIP lxml: fixes and improvements

How is this different from PR #2148 that is in WIP?

@tiborsimko This seems to be indeed identical to https://github.com/inveniosoftware/invenio/pull/2148/ . The only explanation is that I did this PR without having seen the previous one by @kaplun . If @kaplun confirms, then we should go ahead and close this one.


Google Recaptcha

I've had bad experiences with load times in many projects with google's recaptcha, i think it would be a great add to this project.

Thanks, I agree. Will track here: https://github.com/nuxt/scripts/discussions/177


Trailing semicolon prevents signature help from displaying

Environment data
dotnet --info output:
CLI: 2.1.4
Commit: 5e8add2190
.NET Core 2.0.5
Build: 17373eb129b05aa18ece963f8795d65ef8ea54
Runtime: Windows 10 / ubuntu 16.04 x64

VS Code version: 1.20.0
C# Extension version: 1.14.0-beta4
Steps to reproduce
In a C# file add this code
Console.WriteLine;
Add opening parenthesis bracket in front of the semicolon
Expected  behavior
Signature help should give you some information about Console.WriteLine()
Actual behavior
The trailing semicolon is preventing the dialog from being presented. This case works correctly in VS.

Cannot reproduce with the current release.


Fix for Level XX : SpellName (syntax repair)

missed a + on line 91.
would work with "Level 5 : SpellName" but not with "Level  5 : SpellName"  the + fixes that.

ok - makes sense on the regex for 1 or more spaces


OpenSearch search engine file

This should take just a static file and a tag in
http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_description_document

:+1:


Feature Request: ability to create tv episode collections

Is your feature request related to a problem? Please describe.
Currently you can only add entire series to a collection, but episode collections are possible in plex.
Describe the solution you'd like
I would like to be able to create tv collections based on trakt lists that add just specific episodes instead of the entire series like for a Halloween and Christmas collection for example. Like this
Describe alternatives you've considered
Using plex-trakt-scobbler to bring the list into plex as a playlist, but a collection is preferred because it can be added to the homescreen for everyone.
Additional context
I just want all encompassing Halloween and Christmas tv episode collections.

Just chiming in to say this would be beneficial for a trakt list like this, The Essential X-Files Episodes, which only includes some episodes within a single series.
I tried making this the other day and it adds the entire series.

ive got this almost done

added collection_level as a Collection Detail you can give it either season or episode to create a collection of that type. You can only use plex_search and trakt_list with season or episode but it should work well if you add collection_order: custom as well.
Note. Plex doesn't allow shows in season or episode collections, doesn't allow seasons in show or episode collections, and doesn't allow episodes in show or season collections. Basically you can't combine shows, seasons, and episodes into the same collection.
Note 2. How season and episode collections play on your players and if they actually play in order could vary. i have a player that will play them in order but only from the beginning and then one player that just goes to that spot in the show and then just plays the next episode.


tip: respect empty lines

closes #1578

Argh, I was able to reproduce this, but then it suddenly stopped happening and I can’t debug. ☹


Added new serialization format and updated encryption logic

Resolved issues:
resolves #2480 resolves #2479
Description of changes:
Adds new serialization logic and encryption logic to session resumption.
Call-outs:
Because the tls13 deserialize function is being written later on, the tests for tls1.3 s2n_encrypt_session_ticket are not complete yet, although I do have a unit test that checks that the encryption size is correct.
Testing:
Unit tests for tls1.2 and tls1.3.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Tests are failing because build is broken.


403 issue for various vidoes I tried downloading

Noticed over the last few days that I was getting 403 errors when trying to use the GetStreamURL
Even the example in the Readme does not work.
Looking around at the other YT-DL libaries I found this issue/comment that has the same issue https://github.com/TeamNewPipe/NewPipe/issues/9038
I have implemented  their solution:  https://github.com/yt-dlp/yt-dlp/commit/81ca451480051d7ce1a31c017e005358345a9149
and it seems to work.

Thank you Robert.


Add System Level Timeout

TL;DR
Handles system level timeouts in 2 cases, PodQueued and PhaseInitializing.
PodQueued is part of interruptible, where if a pod is stuck in pending for a time longer than the maxSystemLevelTimeout,  we can assume that there are not enough resources in the ASG and we will then error out as a system level error and retry on the non-interruptible ASG.
PhaseInitializing is when some sort of system level error occurs that leaves us in this state. We will error with a system level error and retry launching the pod.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
_https://github.com/lyft/flyte/issues/382

cc @kumare3 as haytham is out.

@migueltol22 are we reviving this?


ContentIsland sample

This sample demonstrates the usage of the Content related API's part of the  WindowsAppSdk 1.2 experimental release.

/azp run SamplesCI-Content


Transform methods

Hi,
SRGAN paper's authors said that they scaled the range of the HR images to [−1, 1]. However, I wonder that your code do not implement this transform. Could you explain the reason? Thank you

@hmtrii  look at these code, we scale images to [0, 1]
https://github.com/leftthomas/SRGAN/blob/bed685fd4f48cfcecfc5b3a728aa0d220b1a11c0/data_utils.py#L20
https://github.com/leftthomas/SRGAN/blob/bed685fd4f48cfcecfc5b3a728aa0d220b1a11c0/model.py#L38

@hmtrii you could try that scale to [-1, 1] or [0, 1] will no any effort to the results.


Update sas-expiration-policy.md to indicate user delegation keys work

Current text implies that SAS tokens signed with a user delegation (rather than an account key) key are excluded from expiration policy monitoring.  However, I just tried it, and the warnings are generated for user delegation SAS tokens as well.  This commit clarifies that.

@pauljewellmsft
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Followed up with @asorrin-msft and PM internally.

@pauljewellmsft
Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Is there an example to concat two dataframes vertically?

Is there an example to concat two dataframes vertically?
I can not find a solution with dask

Did you see the docs for dask.dataframe.concat?
In [41]: df1 = pd.DataFrame({"A": [1, 2]}, index=pd.Index(['a', 'b'], name='A'))

In [42]: df2 = pd.DataFrame({"A": [1, 2]}, index=pd.Index(['c', 'd'], name='A'))

In [43]: ddf1 = dd.from_pandas(df1, 1)

In [44]: ddf2 = dd.from_pandas(df2, 1)

In [45]: dd.concat([ddf1, ddf2])
Out[45]:
Dask DataFrame Structure:
                   A
npartitions=2
a              int64
c                ...
d                ...
Dask Name: concat, 4 tasks

Yeah, you're going to want to use dd.concat, which works the same as pd.concat. Closing.


sidenav collapsible won't work within a separate JS file

Hey, so I don't think this is a "how to" question, and I've tried gitter and stackoverflow, but I doubt I'll get an answer there. I'm using the Materialize sidenav by calling M.AutoInit() which works for me until I try putting it in a separate Javascript file. I've been able to set up my footer this way so I don't have repeat code, but this doesn't seem to work for the sidenav. The sidenav shows up but the collapsible part will not open.
I think the problem is it doesn't like calling the collapsible part from HTML that is being inserted dynamically. But I tried separating out the collapsible portion (using 2 different querySelectors) which did not work either. If I were to put at least part of the sidenav back into my HTML page, it would defeat the purpose of me doing this.
Haven't seen a repeat issue, and there are many folks on Stackoverflow using jQuery, so I'm wondering if this is a bug or if anyone has a solution. Thanks for looking at it!
document.addEventListener("DOMContentLoaded", () => {
  M.AutoInit()

  document.querySelector('header').insertAdjacentHTML('afterbegin',
    `

        HEC Main

        Home

            <button class="collapsible-header">
              Historyarrow_drop_down
            </button>

                  A Brief Review

Philosophers List

Philosophers Map

The Beginning

Socrates

Plato

Aristotle

                  Bibliograpy / References

        Media

        Events

`)

  document.querySelector('main').insertAdjacentHTML('afterend',
    `

            Philosophy is sponsored by

              www.greece.org
             | © 2021 All Rights Reserved.

          arrow_upward

    `)
})

hmm have you tried to import jQuery on your web?
Because if I remembered correctly, there's still some components on the materializecss that dependent to jQuery

I haven't tried it with jQuery but it turns out someone solved it for me on Stackoverflow. The M.AutoInit() has to come AFTER the code for the menu/collapsible. It only initializes one time so it wasn't able to catch what else was in there. My code is working now, so I'll close this. Hopefully this helps anyone else who's stuck.

By the way, I wouldn't mark this as a 'bug' so people don't assume that it is.


remote config: more code review comments

These are my latest ideas and suggestions for https://github.com/DataDog/dd-trace-cpp/pull/74.
The changes proposed https://github.com/DataDog/dd-trace-cpp/pull/74 are looking very good. The design is sound, the code is straightforward, and the tests make sense.
In no particular order, here's what I'm thinking about when reviewing that code:
What is TracerID?
This has been a long series of conversations among me, Damien, Caleb, remote config maintainers, and others on Slack. I essentially throw up my hands trying to understand all of the potential relationships among:

runtime ID
client ID
service, environment
process, thread
class Tracer

Instead, I propose we choose a specifically vague abstraction in lieu of TracerID. Here I call it "TracerSignature". It's a weasel word, "signature," what does it mean? Well, it's kind of an ID, but not really an ID. I was tempted by TracerInfo but that's just giving up. What keeps me away from "TracerID" is that I wonder identity in what sense?
TracerSignature, on the other hand, is documented as meaning only a bag of data that is used in conjunction with telemetry and with remote config. Nothing more.
This vagueness and verbosity lacks elegance, but I think that it's an improvement over an under-defined notion of an "ID" for a tracer.
I'm not 100% sold on "signature" either.
More documentation
We don't have to document every member function, but please do put a little write-up at the top of every header file. Assume that the reader is smart, unfamiliar with the code, and in a hurry. You can help them answer the questions "do I need to drill down into this?" and "how does this fit into the other code?"
One of my past roles involved a culture of exhaustive, strictly codified, soul crushing documentation standards, so it's unlikely you'll overdo it.
Even little member functions that seem obvious by name and context can benefit from a sentence saying what it's about.
Unit Tests
Your tests are good.
I'm not a fan of the REMOTE_CONFIG_TEST macro (I know, DRY), but it doesn't bother me too much. Besides, I used the preprocessor in environment.h, span_defaults.cpp, and version.cpp, so I'm unqualified to judge.
I looked at a recent code coverage report and there are some code sections that would be good to cover in tests if it's not too onerous:

DatadogAgent::get_and_apply_remote_config_updates in datadog_agent.cpp
a few branches in remote_config.cpp (this one might not be worth the trouble)

These are integrated into Damien's PR.


Add support for 'Command' WorkingDirectory

Hello and thanks for FileWatcher!
I am currently using FW to monitor file changes and run an EXE on a change.
My issue is that the command line executable I'm running uses the "WorkingDirectory".
I can work around this limitation if I launch FW.exe from the desired "WorkingDirectory", i.e.
C:\Users\User\Desktop\Repo1>c:\Portable\FileWatcher\fw.exe
However, if I need to monitor files from two different folders (i.e. define two  configuration xml nodes), I can't run FW from both folder locations :)
[Unless I run two instances of FW?]
Therefore, does it make sense/possible to add a 'WorkingDirectory' XML 'Command' sub-node in the configuration file which would be applied when the EXE is run?
i.e.
`

<watch>
    <!--
        The path of the Mercurial repository I'm monitoring:
         -->
	<path>C:\Users\User\Desktop\Repo1</path>
	<commands>
		<command>
			<triggers>
				<trigger>Change</trigger>
			</triggers>
			<workingdirectory>C:\Users\User\Desktop\Repo1</workingdirectory>
			<path>C:\Program Files\TortoiseHg\thg.exe</path>
			<arguments>commit "[exactpath]"</arguments>
		</command>
	</commands>
</watch>
<watch>
    <!--
        The path of the Mercurial repository I'm monitoring:
    -->
	<path>C:\Users\User\Desktop\Repo2</path>
	<commands>
		<command>
			<triggers>
				<trigger>Change</trigger>
			</triggers>
			<workingdirectory>C:\Users\User\Desktop\Repo2</workingdirectory>
			<path>C:\Program Files\TortoiseHg\thg.exe</path>
			<arguments>commit "[exactpath]"</arguments>
		</command>
	</commands>
</watch>

`
Thanks in advance for your time :)

I have added the working directory tag to the 1.5.2 beta release: https://github.com/TechieGuy12/FileWatcher/releases/tag/1.5.2-beta.1.
Check to see if it works for you?

Hi,
Thanks for responding.
I tried the new binary (SHA-1 28eee7595623815bcf3004ebbcae3bd05c7dfe66) and updated my config file but the  tag does not seem to take effect...
<watches> 	<watch> 		<path>C:\Users\Greg\Desktop\Repo2</path> 		<commands> 			<command> 				<triggers> 					<trigger>Change</trigger> 				</triggers> 				<workingdirectory>C:\Users\Greg\Desktop\Repo2</workingdirectory> 				<path>C:\Program Files\TortoiseHg\thg.exe</path> 				<arguments>commit "[exactpath]"</arguments> 			</command> 		</commands>                    	</watch> </watches>
I tried with and without trailing backslash, ( i.e. Repo2\ ) but no luck
Is my syntax incorrect?
I can't see what you changed since there is nothing to compare in commit 3ab7185;
also the source code in the 1.5.2-Beta1 assets is identical to the release from 2023.12.29...
Could you add logging to confirm WorkingDirectory is being read correctly and/or actually used?
Again, thanks for your time :)

I forgot to mention the tag in the XML file is workingDirectory with a capital 'D'.
The commit for the beta is in the develop branch.

Working as expected with the right syntax :)
workingDirectory
I presumed all lower case based on 1) my original example config and 2) all lower case used for other config multiword tags, i.e. waitbefore
Again, thanks for fix :)


appliance/etcd: Update etcd to v2.0.11

https://github.com/coreos/etcd/compare/v2.0.10...v2.0.11

LGTM


Upgrade packages cant recover from previous failure

OS: Linux Ubuntu 18.04
Compiler: GCC 8.2.1

Steps to reproduce the behavior:
./vcpkg upgrade
then the upgrade should fail in the middle (for example, network issue)
./vcpkg upgrade again
no packages to upgrade
Failure logs

Building package upb[core]:x64-linux... done
Installing package upb[core]:x64-linux...
Installing package upb[core]:x64-linux... done
Elapsed time for package upb:x64-linux: 3.417 s
Starting package 57/110: protobuf:x64-linux
Building package protobuf[core]:x64-linux...
-- Downloading https://github.com/protocolbuffers/protobuf/archive/v3.11.4.tar.gz...
-- Downloading https://github.com/protocolbuffers/protobuf/archive/v3.11.4.tar.gz... Failed. Status: 22;"HTTP response code said error"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:175 (message):
  Failed to download file.
  If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
  variables to "https://user:password@your-proxy-ip-address:port/".
  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_from_github.cmake:132 (vcpkg_download_distfile)
ports/protobuf/portfile.cmake:1 (vcpkg_from_github)
scripts/ports.cmake:90 (include)
Error: Building package protobuf:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: protobuf:x64-linux
Vcpkg version: 2020.02.04-unknownhash
Additionally, attach any relevant sections from the log files above.
user@machine:~/Development/vcpkg$ ./vcpkg upgrade --no-dry-run
All installed packages are up-to-date with the local portfiles.

see https://github.com/microsoft/vcpkg/issues/4360
You can add --keep-going before/after the --no-dry-run and it continue to install all the ports/features except those dependent on the failed port.
FWIW I run the vcpkg upgrade without the --no-dry-run and capture the output to a text file where I can at least recover the missing packages after fixing the failed port.
Example:
.\vcpkg.exe upgrade 1>.\upgrade.log 2>&1
followed by
.\vcpkg.exe upgrade --no-dry-run --keep-going

nice workaround, but I think it simply should work :)

See #10654

Thanks for posting this issue. Closed as duplicate of #4360.


In questions with a single part, show the "(not/partially) answered" text when feedback is not otherwise shown

It's in the part feedback box, just under the score.

Images for information:
A currently submitted single-part question looks like this:

Whilst a multi-part shows 'Answered':


Unable to delete 'xxxxxx' Unable to find tree node to delete

Seen in stroom_core-v6.0-beta.11-2
Steps to recreate:

Delete a folder containing content - folder is deleetd
Delete another folder

Get error

Unable to delete 'xxxxxx' Unable to find tree node to delete

where xxxxx is the name of the folder deleted in step 1.  Caching of the tree issue maybe?

Unable to recreate, possibly fixed as part of changes for gh-869


ENH: GTest for ImageMaskSpatialObject2

Added (optional) GoogleTest, to be enabled by advance CMake option ELASTIX_USE_GTEST.
Added first (rather trivial) GTest test function, for ImageMaskSpatialObject2.

Don't merge! Still unfinished! (WIP = work in progress)

It appears unnecessary to do find_package(GTest REQUIRED), as elastix can use the GoogleTest installation from ITK.
https://cmake.org/cmake/help/v3.14/module/FindGTest.html suggested using GTest::GTest GTest::Main.


Redirects to forum index after publishing a post

Steps to reproduce:

reply to an existing thread or post a new thread

Expected:
should redirect you to the thread you replied to or created. That's pretty obvious, and it's what all decent forums do.
Observed:
Redirects you to the index of the subforum where the thread is located. Quite annoying.

Also now seeing this issue.
Not getting to the topic from direct email links but the top of the forum as Per is seeing.
Category VERY ANNOYING

I agree it's annoying, but you can actually change this behaviour in the forum settings:
https://forum.arduino.cc/index.php?action=profile;area=theme
(check Return to topics after posting by default.)
I think any administrator can set this as a default behavior. Maybe you can open a poll on the forum?

This issue is now common place and seems to be a direct result of of some new software implementations about March 2020.
Was advised little can now be done about it. That seems to indicate a third party is involved.

Now by default new users start with "Return to topic after posting" enabled by default. Also it works for all users that never edited their profile.
For current users it is possible to switch off this param in their profiles and restore previous behavior or leave new default behavior.
Issue closed.

@Serjlee
This was caused by some new software.
The setting suggested was NOT the prime cause.

@BallscrewBob the issue as described by @teo1978 was just about the default configuration now tweaked by @supernova-ws
I think it's just a case of time correlation over causation, or you are talking about a different issue altogether: either way I think we can close this now


format according to SciMLStyle

Codecov Report

Merging #27 (d5e6682) into main (5ea136b) will increase coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
+ Coverage   99.41%   99.44%   +0.02%
==========================================
  Files          13       13
  Lines         342      360      +18
==========================================
+ Hits          340      358      +18
  Misses          2        2

Files
Coverage Δ

ext/DistributionFitsOptimExt.jl
100.00% <100.00%> (ø)

src/DistributionFits.jl
100.00% <100.00%> (ø)

src/fitstats.jl
100.00% <100.00%> (ø)

src/optimizer.jl
100.00% <100.00%> (ø)

src/univariate/continuous/estimateMoments.jl
100.00% <100.00%> (ø)

src/univariate/continuous/exponential.jl
100.00% <100.00%> (ø)

src/univariate/continuous/gamma.jl
100.00% <100.00%> (ø)

src/univariate/continuous/laplace.jl
100.00% <100.00%> (ø)

src/univariate/continuous/logitnormal.jl
100.00% <100.00%> (ø)

src/univariate/continuous/lognormal.jl
100.00% <100.00%> (ø)

... and 3 more


Plugin to Mark/Umark a directory on the fly.

I've previously written a shell script that allows the automatic bookmarking a directory or a path to a name and navigating to that by simply typing the bookmark name.
More info on the project are in: https://github.com/hasanein/BookmarkerScript
If people think that this might be useful, I can adapt that to a plugin to use within Oh-My-Zsh as I am using it locally at the moment.

No demand (and we have quite a few of these types of plugins already).


feat: adjust assertions syntax

What/Why/How?
Simplify the assertions syntax by getting rid of the nested arrays.
The code changes are only these few lines: https://github.com/Redocly/openapi-cli/pull/662/files#diff-47607adc7025266f655cda3df6abbd5cc9f1fbf4e9f493c7b0ba6ed6c3350614R716-R738
The rest is examples and docs changes.
This change basically collects all of the assertions under rules and puts them in an assertions rule. Thus only changing the definition in .redocly.yaml and not the internal handling.
Reference
https://github.com/Redocly/openapi-cli/issues/647
Testing
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

I had minor nitpicks and didn't consider the actual implementation. 😆 (I think it seems good in concept. 🎉 )

I will prepare the docs as a separate PR. Thank you. I'm really looking forward to this rule.

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٠٢ م، كتب Adam Altman @.***>:

I will prepare the docs as a separate PR. Thank you. I'm really looking
forward to this rule.
—
Reply to this email directly, view it on GitHub
https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119593139,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW4X6GCWLQHJ4IVZRKZFMETVIUJ45ANCNFSM5USLMSKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٠٤ م، كتب minalabib223 @.***

:

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٠٢ م، كتب Adam Altman @.***>:

I will prepare the docs as a separate PR. Thank you. I'm really looking
forward to this rule.
—
Reply to this email directly, view it on GitHub
<https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119593139
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AW4X6GCWLQHJ4IVZRKZFMETVIUJ45ANCNFSM5USLMSKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119595132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW4X6GFLMEB2PWDLBY7FZ3DVIUKFBANCNFSM5USLMSKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٣٩ م، كتب minalabib223 @.***

:

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٠٤ م، كتب minalabib223 @.***

:

في جمعة، ٦ مايو، ٢٠٢٢ في ٤:٠٢ م، كتب Adam Altman @.***>:

I will prepare the docs as a separate PR. Thank you. I'm really looking
forward to this rule.
—
Reply to this email directly, view it on GitHub
<
https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119593139
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AW4X6GCWLQHJ4IVZRKZFMETVIUJ45ANCNFSM5USLMSKA

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119595132
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AW4X6GFLMEB2PWDLBY7FZ3DVIUKFBANCNFSM5USLMSKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Redocly/openapi-cli/pull/662#issuecomment-1119634710,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW4X6GEWVOSY2KNJQ5JFZOTVIUOKRANCNFSM5USLMSKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Changing property header row styling for execution plan properties

Now:

Before:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.003%) to 42.032%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesView.ts
1
1.03%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
28023

Relevant Lines:
62069

💛  - Coveralls


ControlD integration

Description
Could someone (more talented than I) create a widget for DNS ControlD.  Seems comparably simple all things considered and a great service.  API Documentation here:
https://docs.controld.com/reference/get-started
Thanks!!!
Priority
Low (Nice-to-have)

Could you say more about what you'd wish to be in that integration?
Also, it seems to be a service comparable to AdGuard home and PiHole, would what you seek fit the DNS-Hole widgets?
https://homarr.dev/docs/dashboards/widgets/dns-hole/#summary

Hi
I agree it is a very similar service to those and we be thankful to just have that data/layout available.  At risk of over asking... would be awesome to see timeline charts for a sense of trends? exaample:

Thank you for even considering :)

Hi, as far as I can tell this is paid software. Is that correct?

They are a paid service at a premium.  Have a free resolver and free trial.  I am not sure if API is behind a paywall (I looked and cannot see in documentation).  With that said, totally get it the can't license all software etc.  My hope had been the API was open.