CircleCI + Xcode 9

Issue Description
Hello! I have a problem in CircleCI after Xcode update to 9.0.
When I start the same fastlane script without circle it works.
It worked before update.
Complete output when running fastlane, including the stack trace and command used
[03:08:11]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[03:08:14]: -------------------------------------------------
[03:08:14]: --- Step: Verifying required fastlane version ---
[03:08:14]: -------------------------------------------------
[03:08:14]: Your fastlane version 2.59.0 matches the minimum requirement of 2.59.0  ✅
[03:08:14]: ------------------------------
[03:08:14]: --- Step: default_platform ---
[03:08:14]: ------------------------------
[03:08:14]: Driving the lane 'ios flashfood_rainforest_dev' 🚀
[03:08:14]: -----------------------
[03:08:14]: --- Step: cocoapods ---
[03:08:14]: -----------------------
[03:08:14]: $ pod install
[03:08:15]: ▸ Preparing
[03:08:18]: ▸ Analyzing dependencies
[03:08:18]: ▸ Inspecting targets to integrate
[03:08:18]: ▸ Using ARCHS setting to build architectures of target Pods-flash-food-ios: (``)
[03:08:18]: ▸ Finding Podfile changes
[03:08:18]: ▸ - ActionSheetPicker-3.0
[03:08:18]: ▸ - Alamofire
[03:08:18]: ▸ - AlamofireImage
[03:08:18]: ▸ - Branch
[03:08:18]: ▸ - CardIO
[03:08:18]: ▸ - CircleProgressView
[03:08:18]: ▸ - CocoaLumberjack
[03:08:18]: ▸ - Crashlytics
[03:08:18]: ▸ - DTPhotoViewerController
[03:08:18]: ▸ - Fabric
[03:08:18]: ▸ - FacebookCore
[03:08:18]: ▸ - FacebookLogin
[03:08:18]: ▸ - Google
[03:08:18]: ▸ - IQKeyboardManagerSwift
[03:08:18]: ▸ - MBProgressHUD
[03:08:18]: ▸ - Mixpanel-swift
[03:08:18]: ▸ - NVActivityIndicatorView
[03:08:18]: ▸ - NYTPhotoViewer
[03:08:18]: ▸ - ReachabilitySwift
[03:08:18]: ▸ - RxCocoa
[03:08:18]: ▸ - RxSwift
[03:08:18]: ▸ - Sentry
[03:08:18]: ▸ - Siren
[03:08:18]: ▸ - SnapKit
[03:08:18]: ▸ - Stripe
[03:08:18]: ▸ - SwiftSpinner
[03:08:18]: ▸ - SwiftyJSON
[03:08:18]: ▸ - Timepiece
[03:08:18]: ▸ Resolving dependencies of Podfile
[03:08:18]: ▸ Comparing resolved specification to the sandbox manifest
[03:08:18]: ▸ - ActionSheetPicker-3.0
[03:08:18]: ▸ - Alamofire
[03:08:18]: ▸ - AlamofireImage
[03:08:18]: ▸ - Bolts
[03:08:18]: ▸ - Branch
[03:08:18]: ▸ - CardIO
[03:08:18]: ▸ - CircleProgressView
[03:08:18]: ▸ - CocoaLumberjack
[03:08:18]: ▸ - Crashlytics
[03:08:18]: ▸ - DTPhotoViewerController
[03:08:18]: ▸ - FBSDKCoreKit
[03:08:18]: ▸ - FBSDKLoginKit
[03:08:18]: ▸ - FLAnimatedImage
[03:08:18]: ▸ - Fabric
[03:08:18]: ▸ - FacebookCore
[03:08:18]: ▸ - FacebookLogin
[03:08:18]: ▸ - FirebaseAnalytics
[03:08:18]: ▸ - FirebaseCore
[03:08:18]: ▸ - FirebaseInstanceID
[03:08:18]: ▸ - GTMOAuth2
[03:08:18]: ▸ - GTMSessionFetcher
[03:08:18]: ▸ - Google
[03:08:18]: ▸ - GoogleSignIn
[03:08:18]: ▸ - GoogleToolboxForMac
[03:08:18]: ▸ - IQKeyboardManagerSwift
[03:08:18]: ▸ - KSCrash
[03:08:18]: ▸ - MBProgressHUD
[03:08:18]: ▸ - Mixpanel-swift
[03:08:18]: ▸ - NVActivityIndicatorView
[03:08:18]: ▸ - NYTPhotoViewer
[03:08:18]: ▸ - ReachabilitySwift
[03:08:18]: ▸ - RxCocoa
[03:08:18]: ▸ - RxSwift
[03:08:18]: ▸ - Sentry
[03:08:18]: ▸ - Siren
[03:08:18]: ▸ - SnapKit
[03:08:18]: ▸ - Stripe
[03:08:18]: ▸ - SwiftSpinner
[03:08:18]: ▸ - SwiftyJSON
[03:08:18]: ▸ - Timepiece
[03:08:18]: ▸ Downloading dependencies
[03:08:18]: ▸ -> Using ActionSheetPicker-3.0 (2.2.0)
[03:08:18]: ▸ -> Using Alamofire (4.5.1)
[03:08:18]: ▸ -> Using AlamofireImage (3.3.0)
[03:08:18]: ▸ -> Using Bolts (1.8.4)
[03:08:18]: ▸ -> Using Branch (0.18.8)
[03:08:18]: ▸ -> Using CardIO (5.4.1)
[03:08:18]: ▸ -> Using CircleProgressView (1.1.2)
[03:08:18]: ▸ -> Using CocoaLumberjack (3.0.0)
[03:08:18]: ▸ -> Using Crashlytics (3.8.6)
[03:08:18]: ▸ -> Using DTPhotoViewerController (0.2.1)
[03:08:18]: ▸ -> Using FBSDKCoreKit (4.26.0)
[03:08:18]: ▸ -> Using FBSDKLoginKit (4.26.0)
[03:08:18]: ▸ -> Using FLAnimatedImage (1.0.12)
[03:08:18]: ▸ -> Using Fabric (1.6.13)
[03:08:18]: ▸ -> Using FacebookCore (0.2.0)
[03:08:18]: ▸ -> Using FacebookLogin (0.2.0)
[03:08:18]: ▸ -> Using FirebaseAnalytics (3.9.0)
[03:08:18]: ▸ -> Using FirebaseCore (3.6.0)
[03:08:18]: ▸ -> Using FirebaseInstanceID (1.0.10)
[03:08:18]: ▸ -> Using GTMOAuth2 (1.1.5)
[03:08:18]: ▸ -> Using GTMSessionFetcher (1.1.11)
[03:08:18]: ▸ -> Using Google (3.1.0)
[03:08:18]: ▸ -> Using GoogleSignIn (4.1.0)
[03:08:18]: ▸ -> Using GoogleToolboxForMac (2.1.1)
[03:08:18]: ▸ -> Using IQKeyboardManagerSwift (4.0.13)
[03:08:18]: ▸ -> Using KSCrash (1.15.12)
[03:08:18]: ▸ -> Using MBProgressHUD (1.0.0)
[03:08:18]: ▸ -> Using Mixpanel-swift (2.1.8)
[03:08:18]: ▸ -> Using NVActivityIndicatorView (3.7.0)
[03:08:18]: ▸ -> Using NYTPhotoViewer (1.1.0)
[03:08:18]: ▸ -> Using ReachabilitySwift (3)
[03:08:18]: ▸ -> Using RxCocoa (3.0.1)
[03:08:18]: ▸ -> Using RxSwift (3.0.1)
[03:08:18]: ▸ -> Using Sentry (2.1.0)
[03:08:18]: ▸ -> Using Siren (3.0.1)
[03:08:18]: ▸ -> Using SnapKit (3.0.2)
[03:08:18]: ▸ -> Using Stripe (9.4.0)
[03:08:18]: ▸ -> Using SwiftSpinner (1.1.0)
[03:08:18]: ▸ -> Using SwiftyJSON (3.1.4)
[03:08:18]: ▸ -> Using Timepiece (0.6.0)
[03:08:18]: ▸ - Running pre install hooks
[03:08:18]: ▸ - Podfile
[03:08:18]: ▸ Generating Pods project
[03:08:18]: ▸ - Creating Pods project
[03:08:18]: ▸ - Adding source files to Pods project
[03:08:18]: ▸ - Adding frameworks to Pods project
[03:08:18]: ▸ - Adding libraries to Pods project
[03:08:18]: ▸ - Adding resources to Pods project
[03:08:18]: ▸ - Linking headers
[03:08:18]: ▸ - Installing targets
[03:08:18]: ▸ - Installing target ActionSheetPicker-3.0 iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/ActionSheetPicker-3.0/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/ActionSheetPicker-3.0/ActionSheetPicker-3.0.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/ActionSheetPicker-3.0/ActionSheetPicker-3.0-umbrella.h
[03:08:18]: ▸ - Installing target Alamofire iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/Alamofire/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/Alamofire/Alamofire.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/Alamofire/Alamofire-umbrella.h
[03:08:18]: ▸ - Installing target AlamofireImage iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/AlamofireImage/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/AlamofireImage/AlamofireImage.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/AlamofireImage/AlamofireImage-umbrella.h
[03:08:18]: ▸ - Installing target Bolts iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/Bolts/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/Bolts/Bolts.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/Bolts/Bolts-umbrella.h
[03:08:18]: ▸ - Installing target Branch iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/Branch/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/Branch/Branch.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/Branch/Branch-umbrella.h
[03:08:18]: ▸ - Installing target CircleProgressView iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/CircleProgressView/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/CircleProgressView/CircleProgressView.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/CircleProgressView/CircleProgressView-umbrella.h
[03:08:18]: ▸ - Installing target CocoaLumberjack iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/CocoaLumberjack/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/CocoaLumberjack/CocoaLumberjack.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/CocoaLumberjack/CocoaLumberjack-umbrella.h
[03:08:18]: ▸ - Installing target DTPhotoViewerController iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/DTPhotoViewerController/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/DTPhotoViewerController/DTPhotoViewerController.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/DTPhotoViewerController/DTPhotoViewerController-umbrella.h
[03:08:18]: ▸ - Installing target FBSDKCoreKit iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/FBSDKCoreKit/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/FBSDKCoreKit/FBSDKCoreKit.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/FBSDKCoreKit/FBSDKCoreKit-umbrella.h
[03:08:18]: ▸ - Installing target FBSDKLoginKit iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/FBSDKLoginKit/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/FBSDKLoginKit/FBSDKLoginKit.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/FBSDKLoginKit/FBSDKLoginKit-umbrella.h
[03:08:18]: ▸ - Installing target FLAnimatedImage iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/FLAnimatedImage/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/FLAnimatedImage/FLAnimatedImage.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/FLAnimatedImage/FLAnimatedImage-umbrella.h
[03:08:18]: ▸ - Installing target FacebookCore iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/FacebookCore/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/FacebookCore/FacebookCore.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/FacebookCore/FacebookCore-umbrella.h
[03:08:18]: ▸ - Installing target FacebookLogin iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/FacebookLogin/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/FacebookLogin/FacebookLogin.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/FacebookLogin/FacebookLogin-umbrella.h
[03:08:18]: ▸ - Installing target GTMOAuth2 iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/GTMOAuth2/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/GTMOAuth2/GTMOAuth2.modulemap
[03:08:18]: ▸ - Generating umbrella header at Pods/Target Support Files/GTMOAuth2/GTMOAuth2-umbrella.h
[03:08:18]: ▸ - Installing target GTMSessionFetcher iOS 8.0
[03:08:18]: ▸ - Generating Info.plist file at Pods/Target Support Files/GTMSessionFetcher/Info.plist
[03:08:18]: ▸ - Generating module map file at Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher-umbrella.h
[03:08:22]: ▸ - Installing target GoogleToolboxForMac iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/GoogleToolboxForMac/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/GoogleToolboxForMac/GoogleToolboxForMac.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/GoogleToolboxForMac/GoogleToolboxForMac-umbrella.h
[03:08:22]: ▸ - Installing target IQKeyboardManagerSwift iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/IQKeyboardManagerSwift/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/IQKeyboardManagerSwift/IQKeyboardManagerSwift.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/IQKeyboardManagerSwift/IQKeyboardManagerSwift-umbrella.h
[03:08:22]: ▸ - Installing target KSCrash iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/KSCrash/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/KSCrash/KSCrash.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/KSCrash/KSCrash-umbrella.h
[03:08:22]: ▸ - Installing target MBProgressHUD iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/MBProgressHUD/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/MBProgressHUD/MBProgressHUD.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/MBProgressHUD/MBProgressHUD-umbrella.h
[03:08:22]: ▸ - Installing target Mixpanel-swift iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Mixpanel-swift/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Mixpanel-swift/Mixpanel-swift.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Mixpanel-swift/Mixpanel-swift-umbrella.h
[03:08:22]: ▸ - Installing target NVActivityIndicatorView iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/NVActivityIndicatorView/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/NVActivityIndicatorView/NVActivityIndicatorView.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/NVActivityIndicatorView/NVActivityIndicatorView-umbrella.h
[03:08:22]: ▸ - Installing target NYTPhotoViewer iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/NYTPhotoViewer/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/NYTPhotoViewer/NYTPhotoViewer.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/NYTPhotoViewer/NYTPhotoViewer-umbrella.h
[03:08:22]: ▸ - Installing target ReachabilitySwift iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/ReachabilitySwift/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/ReachabilitySwift/ReachabilitySwift.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/ReachabilitySwift/ReachabilitySwift-umbrella.h
[03:08:22]: ▸ - Installing target RxCocoa iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/RxCocoa/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/RxCocoa/RxCocoa.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/RxCocoa/RxCocoa-umbrella.h
[03:08:22]: ▸ - Installing target RxSwift iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/RxSwift/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/RxSwift/RxSwift.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/RxSwift/RxSwift-umbrella.h
[03:08:22]: ▸ - Installing target Sentry iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Sentry/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Sentry/Sentry.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Sentry/Sentry-umbrella.h
[03:08:22]: ▸ - Installing target Siren iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Siren/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Siren/Siren.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Siren/Siren-umbrella.h
[03:08:22]: ▸ - Installing target SnapKit iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/SnapKit/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/SnapKit/SnapKit.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/SnapKit/SnapKit-umbrella.h
[03:08:22]: ▸ - Installing target Stripe iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Stripe/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Stripe/Stripe.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Stripe/Stripe-umbrella.h
[03:08:22]: ▸ - Installing target SwiftSpinner iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/SwiftSpinner/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/SwiftSpinner/SwiftSpinner.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/SwiftSpinner/SwiftSpinner-umbrella.h
[03:08:22]: ▸ - Installing target SwiftyJSON iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/SwiftyJSON/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/SwiftyJSON/SwiftyJSON.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/SwiftyJSON/SwiftyJSON-umbrella.h
[03:08:22]: ▸ - Installing target Timepiece iOS 8.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Timepiece/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Timepiece/Timepiece.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Timepiece/Timepiece-umbrella.h
[03:08:22]: ▸ - Installing target Pods-flash-food-ios iOS 9.0
[03:08:22]: ▸ - Generating Info.plist file at Pods/Target Support Files/Pods-flash-food-ios/Info.plist
[03:08:22]: ▸ - Generating module map file at Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.modulemap
[03:08:22]: ▸ - Generating umbrella header at Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios-umbrella.h
[03:08:22]: ▸ - Running post install hooks
[03:08:22]: ▸ - Podfile
[03:08:22]: ▸ - Writing Xcode project file to Pods/Pods.xcodeproj
[03:08:22]: ▸ - Generating deterministic UUIDs
[03:08:22]: ▸ - Writing Lockfile in Podfile.lock
[03:08:22]: ▸ - Writing Manifest in Pods/Manifest.lock
[03:08:22]: ▸ Integrating client project
[03:08:22]: ▸ Integrating target Pods-flash-food-ios (flash-food-ios.xcodeproj project)
[03:08:22]: ▸ - Running post install hooks
[03:08:22]: ▸ - cocoapods-stats from /Users/distiller/.gem/ruby/2.3.4/gems/cocoapods-stats-1.0.0/lib/cocoapods_plugin.rb
03:08:23: ▸ Sending stats
03:08:23: ▸ - ActionSheetPicker-3.0, 2.2.0
03:08:23: ▸ - Alamofire, 4.5.1
03:08:23: ▸ - AlamofireImage, 3.3.0
03:08:23: ▸ - Bolts, 1.8.4
03:08:23: ▸ - Branch, 0.18.8
03:08:23: ▸ - CardIO, 5.4.1
03:08:23: ▸ - CircleProgressView, 1.1.2
03:08:23: ▸ - CocoaLumberjack, 3.0.0
03:08:23: ▸ - Crashlytics, 3.8.6
03:08:23: ▸ - DTPhotoViewerController, 0.2.1
03:08:23: ▸ - FBSDKCoreKit, 4.26.0
03:08:23: ▸ - FBSDKLoginKit, 4.26.0
03:08:23: ▸ - FLAnimatedImage, 1.0.12
03:08:23: ▸ - Fabric, 1.6.13
03:08:23: ▸ - FacebookCore, 0.2.0
03:08:23: ▸ - FacebookLogin, 0.2.0
03:08:23: ▸ - FirebaseAnalytics, 3.9.0
03:08:23: ▸ - FirebaseCore, 3.6.0
03:08:23: ▸ - FirebaseInstanceID, 1.0.10
03:08:23: ▸ - GTMOAuth2, 1.1.5
03:08:23: ▸ - GTMSessionFetcher, 1.1.11
03:08:23: ▸ - Google, 3.1.0
03:08:23: ▸ - GoogleSignIn, 4.1.0
03:08:23: ▸ - GoogleToolboxForMac, 2.1.1
03:08:23: ▸ - IQKeyboardManagerSwift, 4.0.13
03:08:23: ▸ - KSCrash, 1.15.12
03:08:23: ▸ - MBProgressHUD, 1.0.0
03:08:23: ▸ - Mixpanel-swift, 2.1.8
03:08:23: ▸ - NVActivityIndicatorView, 3.7.0
03:08:23: ▸ - NYTPhotoViewer, 1.1.0
03:08:23: ▸ - ReachabilitySwift, 3
03:08:23: ▸ - RxCocoa, 3.0.1
03:08:23: ▸ - RxSwift, 3.0.1
03:08:23: ▸ - Sentry, 2.1.0
03:08:23: ▸ - Siren, 3.0.1
03:08:23: ▸ - SnapKit, 3.0.2
03:08:23: ▸ - Stripe, 9.4.0
03:08:23: ▸ - SwiftSpinner, 1.1.0
03:08:23: ▸ - SwiftyJSON, 3.1.4
03:08:23: ▸ - Timepiece, 0.6.0
03:08:23: ▸ -> Pod installation complete! There are 28 dependencies from the Podfile and 40 total pods installed.
03:08:23: ▸ [!] Smart quotes were detected and ignored in your Podfile. To avoid issues in the future, you should not use TextEdit for editing it. If you are not using TextEdit, you should turn off smart quotes in your editor of choice.
03:08:23: ▸ [!] xcodeproj was renamed to project. Please update your Podfile accordingly.
03:08:23: ▸ [!] The flash-food-ios [Debug] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.debug.xcconfig'. This can lead to problems with the CocoaPods installation [03:08:23]: ▸ [!] The flash-food-ios [Training]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.training.xcconfig'. This can lead to problems with the CocoaPods installation
03:08:23: ▸ [!] The flash-food-ios [Devmi] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.devmi.xcconfig'. This can lead to problems with the CocoaPods installation [03:08:23]: ▸ [!] The flash-food-ios [Dev]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.dev.xcconfig'. This can lead to problems with the CocoaPods installation
03:08:23: ▸ [!] The flash-food-ios [Staging] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.staging.xcconfig'. This can lead to problems with the CocoaPods installation [03:08:23]: ▸ [!] The flash-food-ios [Development]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.development.xcconfig'. This can lead to problems with the CocoaPods installation
03:08:23: ▸ [!] The flash-food-ios [Release] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.release.xcconfig'. This can lead to problems with the CocoaPods installation [03:08:23]: ▸ [!] The flash-food-ios [DevRelease]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.devrelease.xcconfig'. This can lead to problems with the CocoaPods installation
03:08:23: ▸ [!] The flash-food-ios [Production] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.production.xcconfig'. This can lead to problems with the CocoaPods installation [03:08:23]: ▸ [!] Google has been deprecated [03:08:23]: ▸ - Use the $(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)flag, or [03:08:23]: ▸ - Remove the build settings from the target. [03:08:23]: ▸ - Use the$(inherited)` flag, or
03:08:23: ▸ - Remove the build settings from the target.
03:08:23: ---------------------------------------------------
03:08:23: --- Step: git log --format=%B -n 1 $CIRCLE_SHA1 ---
03:08:23: ---------------------------------------------------
03:08:23: $ git log --format=%B -n 1 $CIRCLE_SHA1
03:08:23: ▸ Works local
03:08:23: Works local
03:08:23: --- Step: cert ---
03:08:23: ------------------
+---------------+------------------------------------------------------+
|                       Summary for cert 2.59.0                        |
+---------------+------------------------------------------------------+
| development   | false                                                |
| force         | false                                                |
| username      |<EMAIL_ADDRESS>                         |
| team_id       | RZLZW449XK                                           |
| keychain_path | /Users/distiller/Library/Keychains/login.keychain-db |
| platform      | ios                                                  |
+---------------+------------------------------------------------------+
03:08:23: Starting login with user<EMAIL_ADDRESS>[03:08:25]: Successfully logged in
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  1062  100  1062    0     0   2473      0 --:--:-- --:--:-- --:--:--  2475
[03:08:27]: Certificate N9V4ECYWMY (iOS Distribution) can't be found on your local computer
[03:08:27]: Certificate A5LEA76A92 (iOS Distribution) can't be found on your local computer
[03:08:27]: Found the certificate RHZW937777 (iOS Distribution) which is installed on the local machine. Using this one.
[03:08:28]: Verifying the certificate is properly installed locally...
[03:08:28]: Successfully installed certificate RHZW937777
[03:08:28]: Use signing certificate 'RHZW937777' from now on!
[03:08:28]: ------------------
[03:08:28]: --- Step: sigh ---
[03:08:28]: ------------------
+-------------------------------------+----------------------------------+
|                        Summary for sigh 2.59.0                         |
+-------------------------------------+----------------------------------+
| adhoc                               | true                             |
| development                         | false                            |
| skip_install                        | false                            |
| force                               | false                            |
| app_identifier                      | com.flashfood.flash-food-ios-dev |
| username                            |<EMAIL_ADDRESS>     |
| team_id                             | RZLZW449XK                       |
| ignore_profiles_with_different_name | false                            |
| cert_id                             | RHZW937777                       |
| skip_fetch_profiles                 | false                            |
| skip_certificate_verification       | false                            |
| platform                            | ios                              |
+-------------------------------------+----------------------------------+
[03:08:28]: Starting login with user<EMAIL_ADDRESS>[03:08:29]: Successfully logged in
[03:08:29]: Fetching profiles...
[03:08:30]: Verifying certificates...
[03:08:31]: Found 2 matching profile(s)
[03:08:31]: Downloading provisioning profile...
[03:08:32]: Successfully downloaded provisioning profile...
[03:08:32]: Installing provisioning profile...
/Users/distiller/flash-food-ios/AdHoc_com.flashfood.flash-food-ios-dev.mobileprovision
[03:08:32]: Setting Provisioning Profile type to 'ad-hoc'
[03:08:32]: -----------------
[03:08:32]: --- Step: gym ---
[03:08:32]: -----------------
[03:08:32]: $ xcodebuild -list -workspace flash-food-ios.xcworkspace
[03:08:36]: $ xcodebuild -showBuildSettings -workspace flash-food-ios.xcworkspace -scheme flash-food-ios-dev
[03:08:41]: Detected provisioning profile mapping: {:"com.flashfood.flash-food-ios-dev"=>"com.flashfood.flash-food-ios-dev AdHoc"}
+----------------------------------------------------------------------+--------------------------------------------------------------+
|                                                       Summary for gym 2.59.0                                                        |
+----------------------------------------------------------------------+--------------------------------------------------------------+
| scheme                                                               | flash-food-ios-dev                                           |
| workspace                                                            | flash-food-ios.xcworkspace                                   |
| export_method                                                        | ad-hoc                                                       |
| include_bitcode                                                      | false                                                        |
| include_symbols                                                      | true                                                         |
| export_options.provisioningProfiles.com.flashfood.flash-food-ios-dev | com.flashfood.flash-food-ios-dev AdHoc                       |
| destination                                                          | generic/platform=iOS                                         |
| output_name                                                          | flash-food-ios                                               |
| build_path                                                           | /Users/distiller/Library/Developer/Xcode/Archives/2017-09-28 |
| clean                                                                | false                                                        |
| output_directory                                                     | .                                                            |
| silent                                                               | false                                                        |
| codesigning_identity                                                 | iPhone Distribution: Flashfood Inc. (RZLZW449XK)             |
| skip_package_ipa                                                     | false                                                        |
| buildlog_path                                                        | /tmp/circle-artifacts.MBEtWXz/gym                            |
| xcode_path                                                           | /Applications/Xcode-9.app                                    |
+----------------------------------------------------------------------+--------------------------------------------------------------+
[03:08:41]: $ set -o pipefail && xcodebuild -workspace flash-food-ios.xcworkspace -scheme flash-food-ios-dev -destination 'generic/platform=iOS' -archivePath /Users/distiller/Library/Developer/Xcode/Archives/2017-09-28/flash-food-ios\ 2017-09-28\ 03.08.41.xcarchive archive CODE_SIGN_IDENTITY=iPhone\ Distribution:\ Flashfood\ Inc.\ (RZLZW449XK) | tee /tmp/circle-artifacts.MBEtWXz/gym/flash-food-ios-flash-food-ios-dev.log | xcpretty
[03:08:46]: ▸ Building Pods/Bolts [DevRelease]
[03:08:46]: ▸ Check Dependencies
[03:08:46]: ▸ Building Pods/ActionSheetPicker-3.0 [DevRelease]
[03:08:46]: ▸ Check Dependencies
[03:08:46]: ▸ Building Pods/Alamofire [DevRelease]
[03:08:46]: ▸ Check Dependencies
[03:08:46]: ▸ Building Pods/Branch [DevRelease]
[03:08:46]: ▸ Check Dependencies
[03:08:47]: ▸ ** ARCHIVE FAILED **
[03:08:47]: ▸ The following build commands failed:
[03:08:47]: ▸ Check dependencies
[03:08:47]: ▸ Check dependencies
[03:08:47]: ▸ Check dependencies
[03:08:47]: ▸ Check dependencies
[03:08:47]: ▸ (4 failures)
▸ Building Pods/Bolts [DevRelease]
▸ Check Dependencies
▸ Building Pods/ActionSheetPicker-3.0 [DevRelease]
▸ Check Dependencies
▸ Building Pods/Alamofire [DevRelease]
▸ Check Dependencies
▸ Building Pods/Branch [DevRelease]
▸ Check Dependencies
** ARCHIVE FAILED **
The following build commands failed:
Check dependencies
Check dependencies
Check dependencies
Check dependencies
(4 failures)
[03:08:47]: Exit status: 65
[03:08:47]:
[03:08:47]: Maybe the error shown is caused by using the wrong version of Xcode
[03:08:47]: Found multiple versions of Xcode in '/Applications/'
[03:08:47]: Make sure you selected the right version for your project
[03:08:47]: This build process was executed using '/Applications/Xcode-9.app'
[03:08:47]: If you want to update your Xcode path, either
[03:08:47]:
[03:08:47]: - Specify the Xcode version in your Fastfile
[03:08:47]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[03:08:47]:
[03:08:47]: - Specify an absolute path to your Xcode installation in your Fastfile
[03:08:47]: ▸ xcode_select "/Applications/Xcode8.app"
[03:08:47]:
[03:08:47]: - Manually update the path using
[03:08:47]: ▸ sudo xcode-select -s /Applications/Xcode.app
[03:08:47]:
+---------------+---------------------------+
|             Build environment             |
+---------------+---------------------------+
| xcode_path    | /Applications/Xcode-9.app |
| gym_version   | 2.59.0                    |
| export_method | ad-hoc                    |
| sdk           | iPhoneOS11.0.sdk          |
+---------------+---------------------------+
[03:08:47]: ▸ Code Signing Error: Alamofire does not support provisioning profiles. Alamofire does not support provisioning profiles, but provisioning profile NO_SIGNING/ has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor.
[03:08:47]: ▸ === BUILD TARGET Branch OF PROJECT Pods WITH CONFIGURATION DevRelease ===
[03:08:47]: ▸ Check dependencies
[03:08:47]: ▸ Code Signing Error: Branch does not support provisioning profiles. Branch does not support provisioning profiles, but provisioning profile NO_SIGNING/ has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor.
[03:08:47]:
[03:08:47]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[03:08:47]: 📋  For the complete and more detailed error log, check the full log at:
[03:08:47]: 📋  /tmp/circle-artifacts.MBEtWXz/gym/flash-food-ios-flash-food-ios-dev.log
[03:08:47]:
[03:08:47]: Looks like fastlane ran into a build/archive error with your project
[03:08:47]: It's hard to tell what's causing the error, so we wrote some guides on how
[03:08:47]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[03:08:47]: Before submitting an issue on GitHub, please follow the guide above and make
[03:08:47]: sure your project is set up correctly.
[03:08:47]: fastlane uses xcodebuild commands to generate your binary, you can see the
[03:08:47]: the full commands printed out in yellow in the above log.
[03:08:47]: Make sure to inspect the output above, as usually you'll find more error information there
[03:08:47]:
+---------------------+--------------------------------------------------------------------------------------------+
|                                                   Lane Context                                                   |
+---------------------+--------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM    | ios                                                                                |
| PLATFORM_NAME       | ios                                                                                |
| LANE_NAME           | ios flashfood_rainforest_dev                                                               |
| CERT_FILE_PATH      | /Users/distiller/flash-food-ios/RHZW937777.cer                                             |
| CERT_CERTIFICATE_ID | RHZW937777                                                                                |
| SIGH_PROFILE_PATH   | /Users/distiller/flash-food-ios/AdHoc_com.flashfood.flash-food-ios-dev.mobileprovision     |
| SIGH_PROFILE_PATHS  | ["/Users/distiller/flash-food-ios/AdHoc_com.flashfood.flash-food-ios-dev.mobileprovision"] |
| SIGH_UDID           | 1419b6c2-841c-4905-a73f-18afa27ab484                                                       |
| SIGH_UUID           | 1419b6c2-841c-4905-a73f-18afa27ab484                                                       |
| SIGH_PROFILE_TYPE   | ad-hoc                                                                                |
+---------------------+--------------------------------------------------------------------------------------------+
[03:08:47]: Error building the application - see the log above
+------+---------------------------------------+-------------+
|                      fastlane summary                      |
+------+---------------------------------------+-------------+
| Step | Action                                | Time (in s) |
+------+---------------------------------------+-------------+
| 1    | Verifying required fastlane version   | 0           |
| 2    | default_platform                      | 0           |
| 3    | cocoapods                             | 9           |
| 4    | git log --format=%B -n 1 $CIRCLE_SHA1 | 0           |
| 5    | cert                                  | 4           |
| 6    | sigh                                  | 4           |
| 💥   | gym                                   | 14          |
+------+---------------------------------------+-------------+
[03:08:47]: fastlane finished with errors
[!] Error building the application - see the log above
fastlane flashfood_rainforest_dev returned exit code 1
Action failed: fastlane flashfood_rainforest_dev
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.13.5 (Apple Git-94)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.0

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`

  fastlane_version "2.59.0"

  default_platform :ios

  platform :ios do
    before_all do
      ENV["SLACK_URL"] = "https://hooks.slack.com/services/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"
      cocoapods
    end

  desc "Submit a new Beta Build to Apple TestFlight"

lane :flashfood_dev do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "dev"

    gym(scheme: "flash-food-ios-" + env)
    pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
    slack({
        message: "FlashFood ios build is uploaded: " + env,
        success: true,
    })
end

lane :flashfood_rainforest_dev do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "dev"

    cert

    sigh(
     adhoc: true,
    )

    gym(
      scheme: "flash-food-ios-" + env,
      export_method: "ad-hoc",
    )

    slack({
        message: "FlashFood ios build is archived: " + env,
        success: true,
    })
end

lane :flashfood_devmi do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "devmi"

    gym(scheme: "flash-food-ios-" + env)
    pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
    slack({
        message: "FlashFood ios build is uploaded: " + env,
        success: true,
    })
end

lane :flashfood_staging do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "staging"

    gym(scheme: "flash-food-ios-" + env)
    pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
    slack({
        message: "FlashFood ios build is uploaded: " + env,
        success: true,
    })
end

lane :flashfood_production do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "production"

    gym(scheme: "flash-food-ios-" + env)
    pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
    slack({
        message: "FlashFood ios build is uploaded: " + env,
        success: true,
    })
end

lane :flashfood_training do

    COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
    puts COMMIT_MSG

    env = "training"

    gym(scheme: "flash-food-ios-" + env)
    pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
    slack({
        message: "FlashFood ios build is uploaded: " + env,
        success: true,
    })
end

  lane :build do
      COMMIT_MSG = sh("git log --format=%B -n 1 $CIRCLE_SHA1")
      puts COMMIT_MSG

      deploy_environemts = []

      if COMMIT_MSG.include? "-BUILD_ENV_ALL"
          deploy_environemts = ["dev", "devmi", "training"]
          puts "All"
      elsif COMMIT_MSG.include? "-BUILD_ENV_DEVMI"
          deploy_environemts = ["devmi"]
          puts "devmi"
      elsif COMMIT_MSG.include? "-BUILD_ENV_DEV"
          deploy_environemts = ["dev"]
          puts "dev"
      elsif COMMIT_MSG.include? "-BUILD_ENV_TRAINING"
          deploy_environemts = ["training"]
          puts "training"
      elsif COMMIT_MSG.include? "-BUILD_ENV_STAGING"
          deploy_environemts = ["staging"]
          puts "staging"
      elsif COMMIT_MSG.include? "-BUILD_ENV_PRODUCTION"
          deploy_environemts = ["production"]
          puts "production"
      end

      for env in deploy_environemts
          gym(scheme: "flash-food-ios-" + env)
          pilot(skip_waiting_for_build_processing:true, beta_app_description: COMMIT_MSG + env)
          slack({
              message: "FlashFood ios build is uploaded: " + env,
              success: true,
          })

       end
  end

    desc "Deploy a new version to the App Store"
    lane :release do
      # match(type: "appstore")
      # snapshot
      gym(scheme: "flash-food-ios") # Build your app - more options available
      deliver(force: true)
      # frameit
    end
  end

`./fastlane/Appfile`
app_identifier "com.flashfood.flash-food-ios-dev" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "RZLZW449XK" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.59.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

activesupport
4.2.9

addressable
2.5.1

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.14.6

claide
1.0.2

cocoapods
1.2.1

cocoapods-core
1.2.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

cocoapods-trunk
1.2.0

cocoapods-try
1.1.0

colored
1.2

colored2
3.1.2

commander-fastlane
4.4.5

declarative
0.0.9

declarative-option
0.1.0

domain_name
0.5.20170404

dotenv
2.2.0

escape
0.0.4

excon
0.55.0

faraday
0.12.1

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.1.0

fourflusher
2.0.1

fuzzy_match
2.0.4

gh_inspector
1.0.3

google-api-client
0.13.4

googleauth
0.5.1

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

i18n
0.8.6

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
3.0.0

little-plugger
1.1.4

logging
2.2.2

memoist
0.15.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.4.3

molinillo
0.5.7

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.3

nap
1.1.0

netrc
0.7.8

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.5

rake
10.4.2

rdoc
4.2.0

representable
3.0.4

retriable
2.1.0

rouge
1.11.1

ruby-macho
1.1.0

rubygems-update
2.5.2

rubyzip
1.2.1

security
0.1.3

signet
0.7.3

slack-notifier
1.5.1

sqlite3
1.3.13

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

thread_safe
0.3.6

tty-screen
0.5.0

tzinfo
1.2.3

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.3

word_wrap
1.0.0

xcodeproj
1.5.1

xcpretty
0.2.6

xcpretty-travis-formatter
0.0.4

generated on: 2017-09-28

It works via terminal on Mac. Problem with CircleCI

[03:08:47]: ▸ Code Signing Error: Alamofire does not support provisioning profiles. Alamofire does not support provisioning profiles, but provisioning profile NO_SIGNING/ has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor.

Yes but I already switched on Automatic before http://prntscr.com/gr1tny

Need to remove
environment:
GYM_CODE_SIGNING_IDENTITY:
In the circle.yml file

@YuriRudenyaDev How did you remove the error?

@ankur-sardar  Please check my answer on discuss.circleci.com https://discuss.circleci.com/t/xcode-9-fastlane-archive-failed/16924/4
If you need more details please let me know

Hi @YuriRudenyaDev , actually the problem is when I am unchecking the auto codesigning option, then the profile I am selecting are showing ineligible provisioning profiles. I could not find the correct profile from Xcode

Hi @ankur-sardar. First of all restart Xcode if it won't help will recreate certificate/provision check in KeyChain. Don't use Automatic manage signing try to fix it Manually. Circle doesn't work with automatic manage signing

Still facing this error

+1


Create stacmail.txt

@Bailey-Moir Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

You can provide us with any of the following as the proof:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

@Bailey-Moir You might miss my previous comment. Please react.

@Bailey-Moir Yes, it's fine. Please provide us with all the remaining information about the school and the domain recognition. Thank you!

@Bailey-Moir Please let us know if you have any update on the matter. Otherwise, I'll have to close the request.

@Bailey-Moir I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Add jdk21 to build health report

Test run here: https://ci.adoptium.net/job/nightlyBuildAndTestStats_temurin/1059/

Can we make sure that this part of the process is documented in https://github.com/adoptium/temurin-build/blob/master/RELEASING.md#openjdk-new-major-release-process - probably using a link to this PR as an example.

Sure. I'll hold off until John Oliver has replied to this Slack message with the details of his changes to api.adoptium.net.

From the thread it seems that  https://github.com/adoptium/api.adoptium.net/blob/bda17356dae38e4a36a2aa2aef9bec3b5e9e4275/adoptium-models-parent/adoptium-api-v3-models/src/main/kotlin/net/adoptium/api/v3/models/Versions.kt#L5 needs to be updated too so that should be done and added to the docs as well (The immediate fix that was applied to resolve this was to override the java LATEST_JAVA_VERSION property in the API instead of updating that file)

API change PR: https://github.com/adoptium/api.adoptium.net/pull/578

Note: The docs change mentioned above was carried out here: https://github.com/adoptium/temurin-build/pull/3360


Global Install?

Why the need for an npm global installation?

Hello @r-i-c-h! There's no such need, it's just the recommended installation method to make it easier for people that are new to Node.js. You can play from a local install if you prefer by following the steps here.


WSL not working after update from Microsoft store

Version
Microsoft Windows [Version 10.0.19044.1586]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu20.04LTS
Other Software
Docker Desktop (Windows), version 4.6.1 (76265) Docker Engine v20.10.13
Repro Steps
I already had WSL installed from Microsoft Store few days and it was working fine. I got an update about the WSL from Microsoft Store and I updated it then it stopped working.
Expected Behavior
bash shell. Windows Subsystem for Linux is already installed so it should operate normally.
Actual Behavior
Hello I had successfully installed WSL few days ago and everything was working fine. But after the I got an update regarding WSL from Microsoft Store I updated WSL and since then it is throwing this error. I also restarted the computer and checked to make sure my Virtual Machine Platform and Windows Subsystem for Linux are ON and I found out that both of these services were already ON. still I get the same error. May I please get any guidance on this one? as I have to use WSL for my educational purpose that would be really helpful thanks
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070050
Error: 0x80070050 The file exists.
Press any key to continue...
Diagnostic Logs
No response

same issue here.  Please take a look at this.  I know there is the workaround but, really, when will Microsoft stop breaking stuff with updates?????

try https://github.com/microsoft/WSL/issues/8258#issuecomment-1094081305

try #8258 (comment)

I just fixed the entry in the terminal settings to use "bash.exe" for now.   The issue isn't the workaround, it's the sheer number of screw-ups that seem to continue to plague Microsoft updates

when I am running wsl.exe from start menu its working fine but when I am opening the actual Ubuntu application from start menu its not working

I am not willing to uninstall it as I run anaconda and Docker from WSL. But not sure how long can I wait to get this fixed? or I can just use wsl.exe what difference it is going to make

anyway, turn off automatic updates in the Microsoft Store

So the problem here is the new Ubuntu version in the Microsoft store is wrong right?

Try running the distro with "wsl.exe -d Ubuntu20.04LTS" instead of "ubuntu2004.exe". I solved the problem this way

I tried running the distro with "wsl.exe -d Ubuntu20.04LTS" like 1cekrim told and it worked but when I ran only ubuntu2004 then it was still wrong

I had the same problem here after an update. As pointed out above changing from ubuntu2004.exe to wsl.exe -d Ubuntu20.04LTS did the trick. However  this is clearly not an acceptable workaround. WSL should never break like that after an update. So please fix this.

I have also put up in https://askubuntu.com/questions/1401830/wsl-not-working-after-update-from-microsoft-store?noredirect=1#comment2432937_1401830 I hope this issue gets escalated and reaches to their tech support for fix asap. I think lot of people are more worried about their docker environment and anaconda including myself

For anyone having this issue, please see my answers to the OP's question on Ask Ubuntu.  And let me know the results.

So the problem here is the new Ubuntu version in the Microsoft store is wrong right?

Actually, it appears that the previous "Ubuntu 20.04" version in the Store was wrong.  It should have had the distribution name, Ubuntu-20.04, but for some reason it got renamed to Ubuntu20.04LTS.  Canonical "fixed" it in the latest version by changing the distribution name back to what it should be, but that broke things if you happened to have installed the "bad" version.

@NotTheDr01ds I had upgraded from a wsl1 "Ubuntu" distro to wsl2 "Ubuntu-20.04" a while back when wsl2 came out. I deleted the old wsl1 ubuntu on a clean-out and everything was okay, but a couple of days it wouldn't boot the 20.04. I thought I borked the 20.04 removing the old wsl1 distro! I manually pulled my files out the vhdx (latest 7-zip is your friend!). Then I unregistered my ubuntu-20.04 to try and reinstall today. It's not happening, getting the Error: 0x80070050 The file exists. running ubuntu2004 or wsl -d Ubuntu-20.04. If I run ubuntu.exe I get Error: 0x8007045b A system shutdown is in progress.. Checked the Lxss reg, there is a defaultDistribution pointing at a guid (a docker distro), and DefaultVersion: 2.

@kodikos So just one distro (the Docker one), showing in the registry, right?  Does the 0x8007045b occur after reboot?  I might could see the "state" being bad after encountering the 0x80070050.

but a couple of days ago it wouldn't boot the 20.04.

While most users are having problems after the "fix" of the Store Ubuntu, I have a feeling you are one of the ones who initially ran into this problem while the "bad" version was on your system.  That means that an ``--unregister` might not have "fully worked".  It probably removed the registry keys, but it sounds like it left the installation on your system.  Just guessing here from what I'm "visualizing" of the problem so far, but let's see if we can confirm ...
Check for the remnants of a %userprofile%\AppData\Local\Packages\CanonicalGroup...Ubuntu... directory on your system (maybe more than one).
Assuming that you don't have any other distros showing up in the registry (or via wsl -l -v), then try to move or rename those directories.  It might not let you due to permissions, and if not, then at least try to move the ..\LocalState\ext4.vhdx out of there.  Once it's gone, try the reinstall again.

@NotTheDr01ds your fix worked for me. I usually stay away from regedit, but this was simple enough.
Thanks mate!

Start internet connection sharing service


AutoPr-CognitiveServices.Personalizer-dwaijam-REST Spec PrNumber 5835

Closing in favor of manual PR https://github.com/Azure/azure-sdk-for-net/pull/6041


Client Allocation Request for: Xinshu

Client Allocation Questions
Core Information

Name: Xinshu
Website / Social Media: Wechat: 拾时相册
Region: Greater China Region
DataCap Requested: 100TiB
Addresses to be Notarized: f16y7rzirf5xuhzvunhrcorc657tvekugfjl6c3qq
Notary Requested: UnionLabs2020

@Xinshu01 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for the request! Please answer the following questions giving as much detail as possible.
Please introduce yourself and the organization you represent.
How many employees does the company currently have?
In which region do you plan to use DataCap?
What kind of data do you plan to store? Can you share any kind of sample data?

@UnionLabs2020
I'm an employee of Xinshu. Shanghai Xinshu Information Technology Co., Ltd. was founded in March 2018. The company is committed to becoming a leading provider of image management solutions for the mobile Internet. The company's mission is to promote people to develop the habit of video recording and pick up the passing years. The brand of Shishi Photo Album is named after it. In May 2019, the company launched the Shishi Photo Album mobile app, officially entering the Internet industry. Shanghai Xinshu will promote Shishi photo albums into the daily life of every ordinary person, and let beautiful images record everyone's life.
Now we remain having more than 50 staffs.
We plan connected with sp
I plan to communicate with sp to cooperate on BDE platform. Welcome sp from different regions to recieve our deals.
This is our dataset, it's pictures from our platform.
dataset.zip


recent opencv 3.0 dev on android , load opencv_java3.so crash

commit id : 8b554d3c2dffc5616b5099517386b4d722d82640
when executing System.loadLibrary("opencv_java3"); , the tutorial4-opencl sample app crashed,
crash log:

11-20 10:11:39.628 18556-18593/org.opencv.samples.tutorial4 A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x30 in tid 18593 (GLThread 457)

the android.mk

LOCAL_PATH := $(call my-dir)
add OpenCV
include $(CLEAR_VARS)
OPENCV_INSTALL_MODULES:=on
#OPENCV_LIB_TYPE:=STATIC
ifdef OPENCV_ANDROID_SDK
ifneq ("","$(wildcard $(OPENCV_ANDROID_SDK)/OpenCV.mk)")
include ${OPENCV_ANDROID_SDK}/OpenCV.mk
else
include ${OPENCV_ANDROID_SDK}/sdk/native/jni/OpenCV.mk
endif
else
include ../../sdk/native/jni/OpenCV.mk
endif
ifndef OPENCL_SDK
$(error Specify OPENCL_SDK to Android OpenCL SDK location)
endif
add OpenCL
LOCAL_C_INCLUDES+= $(OPENCL_SDK)/include
LOCAL_LDLIBS 	+= -L$(OPENCL_SDK)/lib/$(TARGET_ARCH_ABI) -lOpenCL
LOCAL_MODULE    := JNIpart
LOCAL_SRC_FILES := jni.c CLprocessor.cpp
#LOCAL_CFLAGS 	+= -fopenmp
#LOCAL_LDFLAGS 	+= -fopenmp
LOCAL_LDLIBS    += -llog -lGLESv2 -lEGL
include $(BUILD_SHARED_LIBRARY)

I attempted to link with static lib , it throws link error ,

D:/opensource/opencv/build_mini/install/sdk/native/jni/../libs/armeabi-v7a/libopencv_core.a(parallel.cpp.o):parallel.cpp:function cv::parallel_for_(cv::Range const&, cv::ParallelLoopBody const&, double): error: undefined reference to 'GOMP_parallel'

Where do you get OpenCV android library? Do you build it yourself? What cmake parameters do you use?

Looks like it is not actual anymore


Replace runtime a11y errors with discriminated unions

Some of our form components throw runtime errors in dev mode.  The most common case is when a label is falsy, we want to require aria-label for a11y reasons.  Instead of doing a runtime error, we should be able to leverage discriminated unions https://www.typescriptlang.org/docs/handbook/2/narrowing.html#discriminated-unions

This is a bit tricky to do properly at the moment.  We will stick with runtime errors for now.


question of compute_accuracy

question of compute_accuracy

I would like to know what this method(compute_accuracy) does? centralized learning？Model warm up？

Hi @18811449050 ,
This method computes the prediction accuracy of the input model on the input dataset. There is no training on the model inside compute_accuracy.

loss2 = mu * criterion(logits, labels)  loss1 = criterion(out, target)  loss = loss1 + loss2

Currently, MOON is designed for the classification task. For regression task, you may need to change the cross-entropy loss (e.g., line 130 of main.py) to loss for regression (e.g., MSELoss). You also need to change the model architecture.


fix: update required ibm provider version to >= 1.65.0

Description
Updated required ibm provider version to >= 1.65.0.
Github issue.
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.22.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Your domain is down..

I can't access the library's FULL Documentation.
Your personal site is down.
Thanks

It has been for a few weeks at least now. In the mean time, a not pretty copy of the documentation is on the wayback machine... https://web.archive.org/web/20180813014444/http://ryandowning.net/PersWiFiManager/

I've also just done a PR with a markdown doc containing the V3 documentation from the site... #30
You can see it better here :
https://github.com/r-downing/PersWiFiManager/blob/8f9c36e921b286655b54da842bdde83b37752377/api-reference.md

Super.
It will be useful to everyone to have this link on the PersWiFiManager main page instead of the broken link.
Thanks

Or the github easy to remember alias - http://r-downing.github.io/PersWiFiManager

Fantastic! Now that I see it again, I actually think either the documentation URL in the readme re-directed to that, or a copy of that was hosted on his own server, so thanks for spotting the gh-pages branch! :) I'll close #30, and do a new PR simply requesting the github link be used instead. ;)


DOC: strip rst formatting from description text

This is a very imperfect solution. But it's the most readily available one, and our needs are not (yet) complicated. I would /love/ for there to be a "plaintext" docutils writer.
Fixes #154

Codecov Report
Base: 64.08% // Head: 63.90% // Decreases project coverage by -0.18% :warning:

Coverage data is based on head (ee54bf7) compared to base (3a14151).
Patch coverage: 16.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #188      +/-   ##
==========================================
- Coverage   64.08%   63.90%   -0.19%
==========================================
  Files          20       20
  Lines        1189     1194       +5
  Branches      244      244
==========================================
+ Hits          762      763       +1
- Misses        347      351       +4
  Partials       80       80

Impacted Files
Coverage Δ

onyo/utils.py
53.89% <16.66%> (-0.59%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add ability to render templates in failfast fashion so that undefined values are forbidden.

I'm afraid that undefined is a perfectly valid value in JavaScript. If you want to make sure that your data is complete before rendering a template ... just make sure that the data is complete before rendering the template.
Often, something like this is nice: template(_.extend({}, defaults, data))


Typescript.ts

Nodeactyl.ts

A complete re write for a new version of nodeactyl called nodeactyl.ts.
This will be kept separate from the master nodeactyl.
Any type of contributions is credited via readme and is appreciated!
All contributed code is subject to review & tests.

Had to re fork as fork was behind master and had conflicts.


Update actions.csv

I've wrapped up the news searches for 2017-2019. Adding 10 new actions and have about 10 more I need to summarize. Not all are from those years.
Is this what you meant about adding directly to actions? Let me know if anything I should be doing differently.

yeah, something like that
Do you have python installed? If so, you can run:
python update.py --csv-cleanup # this will clean up the actions.csv and make sure all the fields are valid
python update.py --csv-to-files # this will update the actions folder with the actions.csv file
python update.py --csv-to-readme # this will update the readme.md with the actions.csv file

closing since this is duplicated in #156, feel free to reopen if this is not correct.


chore: release 2.13.0

:robot: I have created a release *beep* *boop*
2.13.0 (2024-11-14)
Features

build, docker: use buildkit by default (#6401) (fc7eb8a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v2.13.0 :sunflower:


Add certificate, URL, and AppID verification

The skill should verify before continuing on:

Application ID
Incoming request is from Amazon
Certificate URL comes from Amazon
Timestamp of certificate is valid
Certificate signature can be verified

I have code for all of this, but I need to factor it out of my other local changes.

For AWS Lambda, I'm not in a position to test these changes, so I figured I'd talk a bit about them here.
To verify the certificate validity, I currently get at the certificate and signature via the server environment variables HTTP_SIGNATURECERTCHAINURL and HTTP_SIGNATURE.  I then check the DNS field is exactly 'echo-api.amazon.com'; the expiration time of the certificate is not greater than the current server time; the incoming request is from 's3.amazonaws.com' and the url starts with '/echo.api/'; and finally, that the signature actually verifies.
Does all of that sound like it would work on AWS Lambda?  I'm just trying to avoid people spamming you with support requests.
I'll push this all up to a branch for you to look at soon.

Sounds great if you are self hosting the Python side of things.
When using AWS Lambda I'm pretty sure all the security between Echo and the Skill is handled for you.
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/developing-an-alexa-skill-as-a-lambda-function
But of course that doesn't include the traffic in and out of your Kodi box.

I honestly don't know, which is why I asked.  I can just only enable this stuff in the WSGI handler if that's what we decide to do.

According to the docs AWS does handle the security between the two

You do not need an SSL certificate.
You do not need to verify that requests are coming from the Alexa service yourself. Access to execute your function is controlled by permissions within AWS instead.
AWS Lambda runs your code only when you need it and scales with your usage, so there is no need to provision or continuously run servers.
Alexa encrypts its communications with Lambda utilizing TLS.

Lambda uses the same wsgi.py so it would need to be a configurable option.
Do you know of a way we can refactor the code to accommodate these types of variations yet still keep the bulk of the kodi/alexa bit the same?  I have some local tweaks that I think would be worth sharing, i.e. using https and a reverse proxy to speak to your local network.

They both use the same wsgi.py file, but they are handled by different methods. 'lambda_handler' for lambda and 'application' for wsgi

It already sends it to a separate handler in wsgi.py, so it's already separate.  I'd just add these things to the wsgi handler.
Dows AWS also handle verifying the appid?  I'd think not, and since this is an unpublished skill for everyone, I personally like to make sure it's my copy of the skill making the requests to my server.
On my local copy, I've moved configuration out of environment variables and into a config file (I called it 'wsgi.ini').  I had planned on adding two bools: one to enable cert validation, and one to enable appid verification.
I can make similar toggles for the Lambda handler too, and someone who actually has it deployed that way could enable them and see if it works (i.e., m0ngr31).
As for HTTPS, what do you mean exactly?  Between the skill server and Kodi?  From Amazon to skill server it's already HTTPS.

From skill to Kodi, at the moment kodi.py is only using http to speak to the jsonrpc
# These two methods construct the JSON-RPC message and send it to the Kodi player
def SendCommand(command):
  # Change this to the IP address of your Kodi server or always pass in an address
  KODI = os.getenv('KODI_ADDRESS', '<IP_ADDRESS>')
  PORT = int(os.getenv('KODI_PORT', 8080))
  USER = os.getenv('KODI_USERNAME', 'kodi')
  PASS = os.getenv('KODI_PASSWORD', 'kodi')

  print KODI

  url = "http://%s:%d/jsonrpc" % (KODI, PORT)

Changing it to:
# These two methods construct the JSON-RPC message and send it to the Kodi player
def SendCommand(command):

# Change this to the IP address of your Kodi server or always pass in an address
SCHEME = os.getenv('KODI_SCHEME', 'http')
KODI = os.getenv('KODI_ADDRESS', '<IP_ADDRESS>')
PORT = os.getenv('KODI_PORT', '8080')
USER = os.getenv('KODI_USERNAME', 'kodi')
PASS = os.getenv('KODI_PASSWORD', 'kodi')

print KODI

url = "%s://%s:%s/jsonrpc" % (SCHEME, KODI, PORT)

and adding the scheme to the .env
KODI_SCHEME = https
KODI_ADDRESS =
KODI_PORT =
KODI_USERNAME =
KODI_PASSWORD =
LAMBDA_ENV_VARS = KODI_SCHEME,KODI_PASSWORD,KODI_USERNAME,KODI_PORT,KODI_ADDRESS

changes that, but you do need a certificate at the local end, which is the reason I didn't want to PR it just yet.

Does AWS also handle verifying the appid? I'd think not, and since this is an unpublished skill for everyone, I personally like to make sure it's my copy of the skill making the requests to my server.

I thought the appid was unique to the developer's account it was created on. Whilst it is in development you can only use it on the Echo registered to the the same development account. The developer has to add users/roles to allow other amazon account holders access.

HTTPS between skill and Kodi would be nice, yes.

I thought the appid was unique to the developer's account it was created on. Whilst it is in development you can only use it on the Echo registered to the the same development account. The developer has to add users/roles to allow other amazon account holders access.

The scenario is if another user of this skill points it at your web server.  Without verifying the appid within the skill, someone else can pass commands through to you.

See PR #32 for the bulk of this.
@digiltd, you should make a separate Issue for HTTPS from skill <-> Kodi so we can track it.

Could a Heroku user please test as requested in PR #32?


[Eloquent] 'create' method returns instance with wrong id

Laravel Version: 5.5.25
PHP Version: 7.0
Database Driver & Version: MySQL 5.7.19

Description:
create method should return saved model instance. If id column doesn't have auto_increment attribute (only primary key) and id value is set using create method, returned instance has id set to 0 (in DB value is correct). Tested on my project and fresh install.
Steps To Reproduce:

create table without auto_increment attribute on id (e.g. $table->integer('id')->primary())
create model (id must be fillable)
use create method to insert data and check id of returned instance
compare id with record in DB

Example code
$id = rand(1, 50);

$var1 = \App\Test::create([
    'id' => $id
]);

$var2 = \App\Test::find($id);

dd([$var1->id, $var2->id]);

From the docs: https://laravel.com/docs/5.5/eloquent#eloquent-model-conventions

In addition, Eloquent assumes that the primary key is an incrementing integer value, which means that by default the primary key will be cast to an int automatically. If you wish to use a non-incrementing or a non-numeric primary key you must set the public $incrementing property on your model to false. If your primary key is not an integer, you should set the protected $keyType property on your model to string.

Sounds like you forgot to set the $incrementing property.
In the future please read the documentation before filing a bug report.

@36864 It's working, I didn't see that. Thanks.

I cannot get it. Why it creates with a different ID. For instance, I recreate DB, then I add a user it is created with ID 1 but IC 17 is returned by eloquent, And I have a primary key name id.


Update 02-OpenELM-3B-Instruct Lora微调.md

Fix doc error.

Thank you very much for correcting code interpretation errors for us.


handle connection error

Changes

We now give a more helpful message when network issues are detected.
Closes #1460

Also, tests are failing.


Create new linting GH workflow from scratch

Description
Related PR https://github.com/confluentinc/cp-ansible/pull/628. The available GHA seems a bit "immature", so I just created two custom jobs using two of the excellent awesome-ci images.
I added two deliberate errors, to see how it looks like. These should ofc be reverted before merge.
Also fixed an innocent warning in a meta-file, to be able to remove that particualar rule from the skip-list.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

Pretty cool failing tests there! I like this!

Pretty cool failing tests there! I like this!

Yes, me too. :-) Should I clean up and prepare for merge?

Yes, I'll approve when builds succeed!


Apply fails if the resources already exist

Self-explanatory, I think 😄
The error:
ERRO[0003] GoError: pods "httpbin" already exists
Run     at reflect.methodValueCall (native)
base    at setup (file:///Users/dgzlopes/go/src/github.com/grafana/xk6-disruptor/examples/httpbin/disrupt-pod.js:18:14(7))
disrupt at native  hint="script exception"

I have the feeling this shouldn't fail. Same way, while using kubectl, it doesn't fail if the resources already exist.

This is due to https://github.com/grafana/xk6-kubernetes/issues/77


Re-export hyper::client::connect::dns::Name

Problem
When impl reqwest::dns::Resolve, I need to define a resolve fn as doc:
fn resolve(&self, name: hyper::client::connect::dns::Name) -> Resolving {
        // do something
    }

But hyper::client::connect::dns::Name is not re-exported from reqwest, which means I must add hyper to my Cargo.toml with client feature.
Desired Behavior
Add a re-export for hyper::client::connect::dns::Name

I create a PR for this.
PR #1931

When reqwest v0.12 comes out (soon!), you'll no longer need to import the type from another crate, it will be reqwest::dns::Name.


JP - Remote Evaluator Integration

This PR integrates the new remote Scala evaluator within the scala-exercises project. As a part of this work, different tasks have been done:

[x] Exercise Compiler Plugin updated in order to generate automatically, the build meta information in the different libraries (like resolvers and libraryDependencies, among others).
[x] New Compiler Updates. Now, the compiler is able to to fetch meta data information and generate the associated code.
[x] Evaluator Client Algebra integrated in the Scala Exercises Service
[x] Added new Algebra and Interpreter associated to the Evaluator
[x] The old Evaluator has been removed
[x] There are some timeout issues between both services: scalaexercises - evaluator
[x] Include doobie and  fpinscala libraries
[x] Unwrap responses properly
[x] Formatting Error Message properly
[x] Report new issues to add unit tests that might increase the code coverage
[x] Test everything in stage env
[x] Stress Testing at https://scala-exercises-pr-571.herokuapp.com

Please, @raulraja @dialelo could you review? Thanks!

Other than my comment regarding transitive dependencies at compile time this LGTM.
@juanpedromoreno @jdesiloniz @dialelo Can we thoroughly test this to ensure appropriate errors and evaluation is shown to the end user before we merge it all?


HHH-18287 clarify @OrderColumn nullable

See https://hibernate.atlassian.net/issues/HHH-18287 for details.  Feel free to reword as necessary.

I have decided not to apply this change. The proposed placement of this test is right in the middle of an admonition that is explaining something completely different, and I don't see a good spot in the text where this information could belong. All this stuff is confusing enough, without making it even more confusing by adding too many little details of this sort.
Hibernate is much too big for the documentation to possibly cover every little possible variation and caveat.
Thanks anyway.


Materialize/Dematerialize operator

Materialize/Dematerialize operator implementation
http://reactivex.io/documentation/operators/materialize-dematerialize.html

Not implemented


[feature][nodejs] Cache node dependencies

Use the caching features of setup-node to cache dependencies and improve build times.

There is a SLSA build requirement that we should be mindful of.

Build caches, if used, MUST be purely content-addressable to prevent tampering.


Introduce protobuf serialization/deserialization support for transport requests/responses

Description
This is the first PR for adding support for protobuf serialization/deserialization coming from the POC and draft PR #9097. The idea is to add incremental changes (bottom-up) for the support to use protobuf for cat nodes API. In this PR, the following changes are included:

ProtobufWriteable - A version of Writeable where the reader reads from a byte array and writer writes to a java OutputStream. This is needed to serialize and deserialize to and from proto messages. There will be other changes in the OutboundHandler and InboundHandler to transfer bytes related to proto messages over the wire.
TransportRequest and TransportResponse support ProtobufWriteable.
TaskId is converted into a proto message.
TaskIdTests are moved to libs/core module since TaskId has been moved there.

Related Issues
#6844
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I like it. A couple of ideas/comments.

I think it's worth starting to document the new protobuf-based protocol from the start. This PR could contain some README content on how to enable protobuf, what parts of the protocol it replaces (e.g. some extension support is protobuf only).
I quickly read the code, how do I exercise it in a build of OpenSearch? I think it's important to find a path in which we can have something "useful" early.
Where can one read about the north star of completely replacing the custom-rolled OpenSearch protocol by Protobuf?

@dbwiddis will have lots of opinions here ;)

Great work so far. Some comments/questions in-line.

Thank you @dbwiddis! I have added a few responses, LMK what you think. I will keep refining the PR :)

I like it. A couple of ideas/comments.

I think it's worth starting to document the new protobuf-based protocol from the start. This PR could contain some README content on how to enable protobuf, what parts of the protocol it replaces (e.g. some extension support is protobuf only).
I quickly read the code, how do I exercise it in a build of OpenSearch? I think it's important to find a path in which we can have something "useful" early.
Where can one read about the north star of completely replacing the custom-rolled OpenSearch protocol by Protobuf?

Thank you @dblock for your comments!

Definitely! There will be more PRs for the same to add the support for the first API in OpenSearch (cat nodes). I will start a README for the same.
It will still need a few PRs to reach a point where this code can be exercised. I am adding in the changes incrementally but all the changes for the POC are in #9097. The POC ofcourse has some duplicate files since I created a parallel API to cat nodes with protobuf de/serialization for comparison.
I will write up an issue soon with all the work done, the next steps and what we are aiming for.

@dbwiddis I updated the code to represent the empty taskId using an empty byte array for protobuf taskId as discussed. Let me know what you think.

I discussed with Dan and I am closing this PR in favor of a new one with starting top down from the POC #9097 as it will make better sense as a PR and give proper context. We also discussed that we can leave TaskId alone for now and focus on the larger request/response classes to get immediate benefits.


feat: add many new icons and change some old ones

As discussed via email, here's the PR.
I added a bunch of icons, carefully searched the carbon library for potential matches.
Some icon sets I didn't touch because I couldn't find a full set match.
For example the file related icons, there are a few carbon icons that can replace some codicons, but not all. So in order to keep consistency I decided to keep the original codicons in these cases.
In some other cases I found a match, but decided the original codicons were better (for exmaple the "plus" icon, the "dots menu" icon, etc.)

That's awesome, thanks a lot!


QUESTION: How to get the middle of audio?

Hello, Alex.
I asked about extracting part of audio to you, and I solved that problem.
Thank You!
But, got something wrong about getting middle part of audio.
I tried
components.queryItems?.append(URLQueryItem(name: "range", value: "\(contentStart)-\(contentEnd)"))

this to get part of audio from youtube video.
Although, I successed for get 0:00~0:50 audio easily, I failed to get 2:00~2:50 audio.(Exactly, I got Audio Data, but it couldn;'t played with AVAudioPlayer...)
I can't understand why from 0:00 can be played, and others are impossible...
I always got this Error..😂😂
error	NSError	domain: "NSOSStatusErrorDomain" - code:<PHONE_NUMBER>	0x000000030342d0e0

So an audio file is, very simply put, set up like this: First bytes in the file is metadata that defines the codec etc for a player to know how to play this file, after that you have actual content. So when you only retrieve data from a point that is not 0, you basically remove the metadata, which is crucial.
Want do you want to achieve? Play the audio file from a certain position?

Yeah right!
Getting whole of the file needs too long time to wait and request too much of LTE or 5G data usage, so I want to get it only parts of audio like 0:00~0:10, 1:00~1:10, 2:00~2:10,...
Then I will use each part to play in the App.

@alexeichhorn  Do you need anything I have to provide more information?

If you plug in the unmodified url straight into AVPlayer (no manual downloading) and seek directly to the desired starting position, it shouldn't load unnecessary parts of the file. Or did you try this already?

I tried that and I couldn't play it.🥲🥲
Then you mean if I need to play the part of audio File, I have to download all data of the file?
And if it's long time to download, use this code several times
var request = URLRequest(url: externalURL)
                    request.addValue("bytes=\(startByte)-\(endByte)", forHTTPHeaderField: "Range")
                    var (data, response) = try await URLSession.shared.data(for: request)

to get each part(ex)0:00~2:00, 2:00~4:00, 4:00~6:00,...) of the audio data. Then append all of the audio data for using in player??

How did you try it?
Works for me. I have an audio app and I'm using AVPlayer (might not work on AVAudioPlayer). See this:
let audioStream = try await YouTube(url: URL(string: "https://www.youtube.com/watch?v=xyz)!)
                .streams
                .filterAudioOnly()
                .filter { $0.isNativelyPlayable }
                .highestAudioBitrateStream()!
let playerItemAudio = AVPlayerItem(url: audioStream.url)

I'm so sorry to answer lately.
I could make it works with getting whole Audio file from your server.
I used a method where a single audio file is divided into 15-minute segments, fetched, and then combined for use.


Theme: Beautify plain links with buttons

I think it would be great to have more straight links converted to buttons in different places, for example:

Or

Eventually, it will be added to:

Virtualmin Virtual Servers
Disk Quotas
New Features Log


Wrong method called

URL: https://pub.dartlang.org/packages/vibrate
The line that says Vibrate.vibrate(pauses); should actually be Vibrate.vibrateWithPauses(pauses);

This issue was moved to clovisnicolas/flutter_vibrate#8


Angular 6 app giving runtime error when using csvtojson v 2.0.7

I am using csvtojson v2.0.7 in my Angular 6 application. But I am getting this error at runtime:
Uncaught ReferenceError: Buffer is not defined
at Object../node_modules/core-util-is/lib/util.js (util.js:103)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/node_modules/readable-stream/lib/_stream_readable.js (_stream_readable.js:67)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/node_modules/readable-stream/readable-browser.js (readable-browser.js:1)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/v2/Converter.js (Converter.js:16)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/v2/index.js (index.js:2)
at webpack_require (bootstrap:76)

Receiving similar error!
This should be labeled as a bug
core.js:1671 ERROR ReferenceError: process is not defined
at Object../node_modules/process-nextick-args/index.js (index.js:3)
at webpack_require (bootstrap:76)
at Object../node_modules/readable-stream/lib/_stream_readable.js (_stream_readable.js:26)
at webpack_require (bootstrap:76)
at Object../node_modules/readable-stream/readable-browser.js (readable-browser.js:1)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/v2/Converter.js (Converter.js:16)
at webpack_require (bootstrap:76)
at Object../node_modules/csvtojson/v2/index.js (index.js:2)
at webpack_require (bootstrap:76)

Hi,
Would you test it with v2.0.8?
Regards,
Keyang

Close due to no activity


Issue Publishing with SQLite

How can I change this so dotnet electronize start uses win7-x64 instead of win-x64?

How to repro:
setup getting started code:
https://docs.microsoft.com/en-us/ef/core/get-started/netcore/new-db-sqlite
after everything is said done:
dotnet publish -r win-x64 --output ".\published"

cd \published
dotnet run

Error:

Unhandled Exception: System.TypeInitializationException: The type initializer for 'Microsoft.Data.Sqlite.SqliteConnection' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Unable to load DLL 'e_sqlite3': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at SQLitePCL.SQLite3Provider_e_sqlite3.NativeMethods.sqlite3_libversion_number()
at SQLitePCL.SQLite3Provider_e_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number()
at SQLitePCL.raw.SetProvider(ISQLite3Provider imp)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at Microsoft.Data.Sqlite.Utilities.BundleInitializer.Initialize()
at Microsoft.Data.Sqlite.SqliteConnection..cctor()
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Storage.Internal.SqliteRelationalConnection.CreateDbConnection()
at Microsoft.EntityFrameworkCore.Internal.LazyRef1.get_Value()    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)    at Microsoft.EntityFrameworkCore.Storage.Internal.SqliteRelationalConnection.Open(Boolean errorsExpected)    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.BeginTransaction(IsolationLevel isolationLevel)    at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(Tuple2 parameters)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(IEnumerable1 commandBatches, IRelationalConnection connection)    at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IReadOnlyList1 entriesToSave)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess)
at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)
at ConsoleApp.SQLite.Program.Main() in C:\Users<username>\Source\Repos\temp\sqlite_test\Program.cs:line 12

Temp Solution:
dotnet publish -r win7-x64 --output ".\published"
How can I change this so dotnet electronize start uses win7-x64 instead of win-x64?
Environment
.NET Command Line Tools (2.1.2)
Product Information:
Version:            2.1.2
Commit SHA-1 hash:<PHONE_NUMBER>
Runtime Environment:
OS Name:     Windows
OS Version:  6.1.7601
OS Platform: Windows
RID:         win7-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.2\
Microsoft .NET Core Shared Framework Host
Version  : 2.0.4
Build    : 7f262f453d8c8479b9af91d34c013b3aa05bc1ff
Thanks in advance!

We released a new version and now support addional params for the build command like this:
dotnet electronize build /target custom win7-x86;win32 /electron-arch ia32
The "custom" target can be used to specify the desired .NET Core platform and the desired electron packager platform. Be aware that the electron packager itself has an addional parameter called arch, which specifies x86/x64 etc.
For the SQLLite issue you may want to use "/target custom win7-x64;win32".
You should now be able to mix everything that you want :)
Just update the CLI to version 0.0.9


Enhance rancher-machine to be able to update configs

Currently rancher-machine always uses the on disk config when updating or deleting a machine. This is bad for people that do key rotation, update keys, etc.
Rancher-machine should support a way to pass in new keys and update the config on disk.
As part of this fix remove the AWS specific code in /pkg/nodeconfig/config.go so Rancher doesn't have to touch machine configs.

https://github.com/rancher/rancher/pull/24537


'Access-Control-Allow-Origin' header error on Helium API calls

The following error exists when loading data from the Helium API.
Access to XMLHttpRequest at 'https://api.helium.io/v1/*' from origin 'https://explorer.helium.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
A quick google search resulted in the following page: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin
With my community app (helium.watch) I was able to catch this error by running a Heroku server that caught those blocks and routed them with the header attached for my site. This is probably not ideal (costs me $8/mo with low site traffic) and maybe there could be a way to add new sites to the header during the API process? Or they just recommend using the wildcard * in the header for public APIs.

This issue belongs to blockchain http: https://github.com/helium/blockchain-http/issues
Can you refile over there?


Network  Overview mockup

Depends on #160

Maybe add a time field, eg 01:32:47 under the status bar for running/paused systems, in order to know how long the attack has been running for each system.

Perhaps divide the three different machine states (completed/attacking/not started) some way. Check Bootstrap's tabs if you find anything interesting.

screenshot

See #170 comment about deletion confirmation modal styling.

PC icons and labels/progress bars underneath are not horizontally aligned.

Would you consider using a different icon for a laptop and a mobile phone for clarity? We can use heuristics to detect them.

Fix build

LGTM


Key 'hood' not available

Describe the bug
Information about the status of the hood is not available for my car, this results in the following error:
Traceback (most recent call last):
  File "fetch.py", line 87, in <module>
    loop.run_until_complete(get_information())
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "fetch.py", line 26, in get_information
    vehicle = await client.get_vehicle_status(car)
  File "/usr/local/lib/python3.8/dist-packages/mytoyota/client.py", line 120, in get_vehicle_status
    car = Vehicle(
  File "/usr/local/lib/python3.8/dist-packages/mytoyota/vehicle.py", line 192, in __init__
    Status(status["protectionState"])
  File "/usr/local/lib/python3.8/dist-packages/mytoyota/vehicle.py", line 112, in __init__
    self.doors = Doors(status[HOOD], status[DOORS])
KeyError: 'hood'

To Reproduce
Steps to reproduce the behavior:
Execute the sample script of this repository.
Additional context
Response of the request:
{'overallStatus': 'OK', 'timestamp': '2021-09-17T18:12:40Z', 'doors': {'warning': False, 'driverSeatDoor': {'warning': False, 'closed': True, 'locked': True}, 'passengerSeatDoor': {'warning': False, 'closed': True, 'locked': True}, 'rearRightSeatDoor': {'warning': False, 'closed': True, 'locked': True}, 'rearLeftSeatDoor': {'warning': False, 'closed': True, 'locked': True}, 'backDoor': {'warning': False, 'closed': True, 'locked': True}}, 'lamps': {'warning': False, 'headLamp': {'warning': False, 'off': True}, 'tailLamp': {'warning': False, 'off': True}, 'hazardLamp': {'warning': False, 'off': True}}, 'windows': {'warning': False, 'driverSeatWindow': {'warning': False, 'state': 'close'}, 'passengerSeatWindow': {'warning': False, 'state': 'close'}, 'rearRightSeatWindow': {'warning': False, 'state': 'close'}, 'rearLeftSeatWindow': {'warning': False, 'state': 'close'}}, 'key': {'warning': False, 'inCar': False}, 'lock': {'lockState': 'locked', 'source': 'key', 'failedUnlockPreconditions': []}}

Car: Toyota Yaris model 2021

I will see if I can find time to look at it later today, it should be a simple fix. Feel free to contribute.
Thanks for reporting the issue. 😊

New version have been published. Please try upgrading to 0.6.2 😃

Can confirm that it's working now, thank you! 😃


Accept Langchain's RunnableConfig to Agent.execute_task

Accept config as an argument and forward it to the invoke() method of the underlying Langchain AgentExecutor.
It is very helpful for customizing the run, e.g. adding callbacks (see docs for more)

I like it, but we would need to update the agent attributes as well to allow the config to be send upon instantiating

Hey @whimo! Any thoughts on @joaomdmoura's suggestion to also update agente attributes?

Hey @whimo! Any thoughts on @joaomdmoura's suggestion to also update agente attributes?

Nothing against it. In fact, we can just update #632 with this and close the 2 PRs altogether.

@whimo I like the idea of closing both PRs and creating another one joining them, as we would have a conflict here anyway. Happy to streamline the review process for this new PR. cc @thehapyone

Hi @gvieira @thehapyone , I've updated this PR with changes from #632. Looking forward to a review.

Looks good to me 👌

Hi @gvieira, thanks for the approval, can we merge this now?

I would love to understand more what is the underlying need here before we merge, just because we override a lot of the the AgentExecutor and will probably keep overriding more, my fear is that this probably not accepts all the configs today and will probably break in the future.

I would love to understand more what is the underlying need here before we merge, just because we override a lot of the the AgentExecutor and will probably keep overriding more, my fear is that this probably not accepts all the configs today and will probably break in the future.

The AgentExceutor is based on Langchain runnable or atleast everything is migrating towards runnable has a native object. The runnable configs provides a lot of possibilities to customise the behaviour of any type of runnable. A very good use case of this is native callback and tracing possibilities without having to add new functionality to the existing agents codebase. So unless, langchain drops supports for runnable or crewAI moves away from langchain can’t see how this is an issue now or later. The agent still has it’s own config parameter which is a totally different thing.

Hi @joaomdmoura! Really looking forward to merging this. If you have any questions or concerns, please let us know :)
P.S. This change should never break, because AgentExecutor is a Runnable, and any Runnable accepts a RunnableConfig in its invoke() method.
We need this for observability (using Langchain's run_manager, which automatically reports chains' start and end events).

Hi @joaomdmoura @gvieira can you guys check this out? This is really a nice thing to have

@whimo I think this PR won't work again and should probably be closed. CrewAI has moved away from using langchain in the agentexecutor

I believe you're right. The issue can be closed, but I'd love if CrewAI introduced its own callback mechanism similar to what Langchain and LlamaIndex have, so that we can use observability tools, add logging etc.


Any way to rescue / omit any cases of non-workable languages without erroring an entire batch?

Hello! First, off, this is amazing work, thank you for this. The problem I'm running into is I have a set of texts batch_texts that I want to encode. They could be in any language, and I want to convert to english. What i see when I process a batch is something like:
INFO:easynmt.EasyNMT:Translate documents of language: en
INFO:easynmt.EasyNMT:Translate documents of language: ja
INFO:easynmt.EasyNMT:Translate documents of language: de
.........
INFO:easynmt.EasyNMT:Translate documents of language: et
INFO:easynmt.EasyNMT:Translate documents of language: la
WARNING:easynmt.EasyNMT:Exception: 'la'

And then it fails. I tried pulling out the supported_languages(), pre-checking all the texts and omitting non-supported texts, but still, in the internals, I hit this error on some text for some reason. Is there anything in the repo that can do an internal rescue of "if its an unsupported language or the case crashes out for whatever reason, just return None" or something of that nature?

Playing with a bit more, it seems like the offending sentence is 'I just ate a good breakfast I made 😂😮\u200d💨' which doesn't resolve to la with either langdetect or langid?
>>> detect(sentence)
'et'
>>> langid.classify(sentence)
('zh', -45.1043176651001)


[FR] Indentation Guides not available in Prism Live Preview mode

Is your feature request related to a problem? Please describe.
I am not sure if this is a bug or an intended styling but the Editor > Show Indentation Guides setting doesn't have an effect when it is toggled on when the user is in Live Preview mode.  No indentation guides are shown with Prism.

Live Preview:

Reading:

Describe the solution you'd like
It would be ideal if Prism could show indentation guides in live preview/edit mode.
Describe alternatives you've considered
I've tried to look to see if I could force these on through CSS and it looks like there is this that is preventing them from showing:
.markdown-source-view.mod-cm6 .cm-indent::before {
    border-right: none;
}

I was able to work around this, at least for myself, with a CSS snippet but I don't know if this might break anything else as I haven't very widely tested it:
.markdown-source-view.mod-cm6 .cm-indent::before {
  border-right: 1px solid var(--indentation-guide);
  margin-left: 2px;
}

I also added the margin-left to try to center is under the bullet; probably a better/more reliable way to do that.
Additional context
n/a

Hi @mbentley,
This issue should be resolve in the 3.0.0 update.


How to train the pretrained discrete_model?

Must I use the same dataset as I use in train_dsr.py？I'm a big fan. Please help me.

I read the paper too carelessly before; now I know it was pretrained on ImageNet.