Multiple schemes found

Hello I'm trying to upload build to TestFlight via CircleCI
fastlane beta
[04:38:54]: -------------------------------------------------
[04:38:54]: --- Step: Verifying required fastlane version ---
[04:38:54]: -------------------------------------------------
[04:38:54]: Your fastlane version 2.44.1 matches the minimum requirement of 2.44.1  ✅
[04:38:54]: ------------------------------
[04:38:54]: --- Step: default_platform ---
[04:38:54]: ------------------------------
[04:38:54]: Driving the lane 'ios beta' 🚀
[04:38:54]: -----------------------
[04:38:54]: --- Step: cocoapods ---
[04:38:54]: -----------------------
[04:38:54]: $ bundle exec pod install
[04:39:03]: ▸ Analyzing dependencies
[04:39:03]: ▸ Downloading dependencies
[04:39:03]: ▸ Using ActionSheetPicker-3.0 (2.2.0)
[04:39:03]: ▸ Using Alamofire (4.4.0)
[04:39:03]: ▸ Using AlamofireImage (3.2.0)
[04:39:03]: ▸ Using Bolts (1.8.4)
[04:39:03]: ▸ Using Branch (0.15.3)
[04:39:03]: ▸ Using CardIO (5.4.1)
[04:39:03]: ▸ Using CircleProgressView (1.1.2)
[04:39:03]: ▸ Using CocoaLumberjack (3.0.0)
[04:39:03]: ▸ Using Crashlytics (3.8.4)
[04:39:03]: ▸ Using DTPhotoViewerController (0.2.1)
[04:39:03]: ▸ Using FBSDKCoreKit (4.23.0)
[04:39:03]: ▸ Using FBSDKLoginKit (4.23.0)
[04:39:03]: ▸ Using FLAnimatedImage (1.0.12)
[04:39:03]: ▸ Using Fabric (1.6.11)
[04:39:03]: ▸ Using FacebookCore (0.2.0)
[04:39:03]: ▸ Using FacebookLogin (0.2.0)
[04:39:03]: ▸ Using FirebaseAnalytics (3.9.0)
[04:39:03]: ▸ Using FirebaseCore (3.6.0)
[04:39:03]: ▸ Using FirebaseInstanceID (1.0.10)
[04:39:03]: ▸ Using GTMOAuth2 (1.1.4)
[04:39:03]: ▸ Using GTMSessionFetcher (1.1.10)
[04:39:03]: ▸ Using Google (3.1.0)
[04:39:03]: ▸ Using GoogleSignIn (4.0.2)
[04:39:03]: ▸ Using GoogleToolboxForMac (2.1.1)
[04:39:03]: ▸ Using IQKeyboardManagerSwift (4.0.10)
[04:39:03]: ▸ Using KSCrash (1.15.8)
[04:39:03]: ▸ Using MBProgressHUD (1.0.0)
[04:39:03]: ▸ Using Mixpanel-swift (2.1.6)
[04:39:03]: ▸ Using NVActivityIndicatorView (3.6.1)
[04:39:03]: ▸ Using NYTPhotoViewer (1.1.0)
[04:39:03]: ▸ Using ReachabilitySwift (3)
[04:39:03]: ▸ Using Realm (2.0.4)
[04:39:03]: ▸ Using RealmSwift (2.0.4)
[04:39:03]: ▸ Using RxCocoa (3.0.1)
[04:39:03]: ▸ Using RxSwift (3.0.1)
[04:39:03]: ▸ Using Sentry (2.1.0)
[04:39:03]: ▸ Using Siren (2.0.3)
[04:39:03]: ▸ Using SnapKit (3.0.2)
[04:39:03]: ▸ Using Stripe (9.4.0)
[04:39:03]: ▸ Using SwiftSpinner (1.1.0)
[04:39:03]: ▸ Using SwiftyBeaver (1.1.4)
[04:39:03]: ▸ Using SwiftyJSON (3.1.4)
[04:39:03]: ▸ Using Timepiece (0.6.0)
[04:39:03]: ▸ Generating Pods project
[04:39:03]: ▸ Integrating client project
[04:39:03]: ▸ Sending stats
[04:39:04]: ▸ Pod installation complete! There are 30 dependencies from the Podfile and 43 total pods installed.
[04:39:04]: ▸ [!] 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.
[04:39:04]: ▸ [!] xcodeproj was renamed to project. Please update your Podfile accordingly.
[04:39:04]: ▸ [!] The flash-food-ios [Debug] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [04:39:04]: ▸ [!] The flash-food-ios [Debug]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.debug.xcconfig'. This can lead to problems with the CocoaPods installation
[04:39:04]: ▸ [!] The flash-food-ios [Staging] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [04:39:04]: ▸ [!] The flash-food-ios [Staging]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.staging.xcconfig'. This can lead to problems with the CocoaPods installation
[04:39:04]: ▸ [!] The flash-food-ios [Development] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.development.xcconfig'. This can lead to problems with the CocoaPods installation [04:39:04]: ▸ [!] 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
[04:39:04]: ▸ [!] The flash-food-ios [Release] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [04:39:04]: ▸ [!] The flash-food-ios [Release]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.release.xcconfig'. This can lead to problems with the CocoaPods installation
[04:39:04]: ▸ [!] The flash-food-ios [Production] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [04:39:04]: ▸ [!] The flash-food-ios [Production]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.production.xcconfig'. This can lead to problems with the CocoaPods installation
[04:39:04]: ▸ [!] Google has been deprecated
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ▸ - Use the $(inherited) flag, or
[04:39:04]: ▸ - Remove the build settings from the target.
[04:39:04]: ------------------
[04:39:04]: --- Step: scan ---
[04:39:04]: ------------------
[04:39:04]: $ xcodebuild -list -workspace ./flash-food-ios.xcworkspace
[04:39:06]: Multiple schemes found but you haven't specified one.
[04:39:06]: Since this is a CI, please pass one using the scheme option
[04:39:06]: Couldn't find any schemes in this project, make sure that the scheme is shared if you are using a workspace
[04:39:06]: Open Xcode, click on Manage Schemes and check the Shared box for the schemes you want to use
[04:39:06]: Afterwards make sure to commit the changes into version control
[04:39:06]: Sending crash report...
[04:39:06]: The stacktrace is sanitized so no personal information is sent.
[04:39:06]: To see what we are sending, look here: /Users/distiller/.fastlane/latest_crash.json
[04:39:06]: Learn more at https://github.com/fastlane/fastlane#crash-reporting
[04:39:06]: You can disable crash reporting by adding opt_out_crash_reporting at the top of your Fastfile
+------------------+----------+
|        Lane Context         |
+------------------+----------+
| DEFAULT_PLATFORM | ios      |
| PLATFORM_NAME    | ios      |
| LANE_NAME        | ios beta |
+------------------+----------+
[04:39:06]: Multiple schemes found
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | cocoapods                           | 9           |
| 💥   | scan                                | 1           |
+------+-------------------------------------+-------------+
[04:39:06]: fastlane finished with errors
[!] Multiple schemes found
fastlane beta returned exit code 1
Action failed: fastlane beta
My yml file:
machine:
xcode:
version: “8.0”
dependencies:
pre:

sudo gem update fastlane
sudo gem install bundler
ls
deployment:
staging:
branch: develop2
commands:

fastlane release_staging
beta:
branch: Fastlane
commands:
fastlane beta
production:
branch: release
commands:
fastlane release_appstore

My Fastfile:
fastlane_version “2.44.1”
default_platform :ios
platform :ios do
before_all do
cocoapods
end
desc “Runs all the tests”
lane :test do
scan
end
desc “Submit a new Beta Build to Apple TestFlight”
desc “This will also make sure the profile is up to date”
lane :beta do
gym(scheme: “flash-food-ios”) # Build your app - more options available
testflight
end
desc “Deploy a new version to the App Store”
lane :release do
gym(scheme: “flash-food-ios”) # Build your app - more options available
deliver(force: true)
end
after_all do |lane|
end
error do |lane, exception|
end
end
Also I added Gymfile:
scheme “flash-food-ios”
sdk “iphoneos9.0"
clean true
output_directory “./build”    # store the ipa in this folder
output_name “flash-food-ios”           # the name of the ipa file
**But the same result with or without Gymfile **
fastlane beta
[02:48:28]: -------------------------------------------------
[02:48:28]: --- Step: Verifying required fastlane version ---
[02:48:28]: -------------------------------------------------
[02:48:28]: Your fastlane version 2.44.1 matches the minimum requirement of 2.44.1  ✅
[02:48:28]: ------------------------------
[02:48:28]: --- Step: default_platform ---
[02:48:28]: ------------------------------
[02:48:28]: Driving the lane 'ios beta' 🚀
[02:48:28]: -----------------------
[02:48:28]: --- Step: cocoapods ---
[02:48:28]: -----------------------
[02:48:29]: $ pod install
[02:48:34]: ▸ Analyzing dependencies
[02:48:34]: ▸ Downloading dependencies
[02:48:34]: ▸ Using ActionSheetPicker-3.0 (2.2.0)
[02:48:34]: ▸ Using Alamofire (4.4.0)
[02:48:34]: ▸ Using AlamofireImage (3.2.0)
[02:48:34]: ▸ Using Bolts (1.8.4)
[02:48:34]: ▸ Using Branch (0.15.3)
[02:48:34]: ▸ Using CardIO (5.4.1)
[02:48:34]: ▸ Using CircleProgressView (1.1.2)
[02:48:34]: ▸ Using CocoaLumberjack (3.0.0)
[02:48:34]: ▸ Using Crashlytics (3.8.4)
[02:48:34]: ▸ Using DTPhotoViewerController (0.2.1)
[02:48:34]: ▸ Using FBSDKCoreKit (4.23.0)
[02:48:34]: ▸ Using FBSDKLoginKit (4.23.0)
[02:48:34]: ▸ Using FLAnimatedImage (1.0.12)
[02:48:34]: ▸ Using Fabric (1.6.11)
[02:48:34]: ▸ Using FacebookCore (0.2.0)
[02:48:34]: ▸ Using FacebookLogin (0.2.0)
[02:48:34]: ▸ Using FirebaseAnalytics (3.9.0)
[02:48:34]: ▸ Using FirebaseCore (3.6.0)
[02:48:34]: ▸ Using FirebaseInstanceID (1.0.10)
[02:48:34]: ▸ Using GTMOAuth2 (1.1.4)
[02:48:34]: ▸ Using GTMSessionFetcher (1.1.10)
[02:48:34]: ▸ Using Google (3.1.0)
[02:48:34]: ▸ Using GoogleSignIn (4.0.2)
[02:48:34]: ▸ Using GoogleToolboxForMac (2.1.1)
[02:48:34]: ▸ Using IQKeyboardManagerSwift (4.0.10)
[02:48:34]: ▸ Using KSCrash (1.15.8)
[02:48:34]: ▸ Using MBProgressHUD (1.0.0)
[02:48:34]: ▸ Using Mixpanel-swift (2.1.6)
[02:48:34]: ▸ Using NVActivityIndicatorView (3.6.1)
[02:48:34]: ▸ Using NYTPhotoViewer (1.1.0)
[02:48:34]: ▸ Using ReachabilitySwift (3)
[02:48:34]: ▸ Using Realm (2.0.4)
[02:48:34]: ▸ Using RealmSwift (2.0.4)
[02:48:34]: ▸ Using RxCocoa (3.0.1)
[02:48:34]: ▸ Using RxSwift (3.0.1)
[02:48:34]: ▸ Using Sentry (2.1.0)
[02:48:34]: ▸ Using Siren (2.0.3)
[02:48:34]: ▸ Using SnapKit (3.0.2)
[02:48:34]: ▸ Using Stripe (9.4.0)
[02:48:34]: ▸ Using SwiftSpinner (1.1.0)
[02:48:34]: ▸ Using SwiftyBeaver (1.1.4)
[02:48:34]: ▸ Using SwiftyJSON (3.1.4)
[02:48:34]: ▸ Using Timepiece (0.6.0)
[02:48:34]: ▸ Generating Pods project
[02:48:39]: ▸ Integrating client project
[02:48:39]: ▸ Sending stats
[02:48:39]: ▸ Pod installation complete! There are 30 dependencies from the Podfile and 43 total pods installed.
[02:48:39]: ▸
[02:48:39]: ▸ [!] Your Podfile has had smart quotes sanitised. 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.
[02:48:39]: ▸
[02:48:39]: ▸ [!] xcodeproj was renamed to project. Please update your Podfile accordingly.
[02:48:39]: ▸
[02:48:39]: ▸ [!] The flash-food-ios [Debug] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [02:48:39]: ▸  [02:48:39]: ▸ [!] The flash-food-ios [Debug]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.debug.xcconfig'. This can lead to problems with the CocoaPods installation
[02:48:39]: ▸
[02:48:39]: ▸ [!] The flash-food-ios [Staging] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [02:48:39]: ▸  [02:48:39]: ▸ [!] The flash-food-ios [Staging]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.staging.xcconfig'. This can lead to problems with the CocoaPods installation
[02:48:39]: ▸
[02:48:39]: ▸ [!] The flash-food-ios [Development] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.development.xcconfig'. This can lead to problems with the CocoaPods installation [02:48:39]: ▸  [02:48:39]: ▸ [!] 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
[02:48:39]: ▸
[02:48:39]: ▸ [!] The flash-food-ios [Release] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [02:48:39]: ▸  [02:48:39]: ▸ [!] The flash-food-ios [Release]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.release.xcconfig'. This can lead to problems with the CocoaPods installation
[02:48:39]: ▸
[02:48:39]: ▸ [!] The flash-food-ios [Production] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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 [02:48:39]: ▸  [02:48:39]: ▸ [!] The flash-food-ios [Production]target overrides theSWIFT_VERSIONbuild setting defined inPods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.production.xcconfig'. This can lead to problems with the CocoaPods installation
[02:48:39]: ▸
[02:48:39]: ▸ [!] Google has been deprecated
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: ▸ - Use the $(inherited) flag, or
[02:48:39]: ▸ - Remove the build settings from the target.
[02:48:39]: -----------------
[02:48:39]: --- Step: gym ---
[02:48:39]: -----------------
[02:48:40]: Detected provisioning profile mapping: {"com.flashfood.flash-food-ios-training"=>"Flashfood_Training_AppStore"}
[02:48:40]: $ xcodebuild -list -workspace ./flash-food-ios.xcworkspace
[02:48:42]: Couldn't find specified scheme 'flash-food-ios-main'.
[02:48:42]: Multiple schemes found but you haven't specified one.
[02:48:42]: Since this is a CI, please pass one using the scheme option
[02:48:42]: Couldn't find any schemes in this project, make sure that the scheme is shared if you are using a workspace
[02:48:42]: Open Xcode, click on Manage Schemes and check the Shared box for the schemes you want to use
[02:48:42]: Afterwards make sure to commit the changes into version control
[02:48:42]: Sending crash report...
[02:48:42]: The stacktrace is sanitized so no personal information is sent.
[02:48:42]: To see what we are sending, look here: /Users/distiller/.fastlane/latest_crash.json
[02:48:42]: Learn more at https://github.com/fastlane/fastlane#crash-reporting
[02:48:42]: You can disable crash reporting by adding opt_out_crash_reporting at the top of your Fastfile
+------------------+----------+
|        Lane Context         |
+------------------+----------+
| DEFAULT_PLATFORM | ios      |
| PLATFORM_NAME    | ios      |
| LANE_NAME        | ios beta |
+------------------+----------+
[02:48:42]: Multiple schemes found
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | cocoapods                           | 10          |
| 💥   | gym                                 | 2           |
+------+-------------------------------------+-------------+
[02:48:42]: fastlane finished with errors
[!] Multiple schemes found
fastlane beta returned exit code 1
Action failed: fastlane beta
It works if I start from terminal without CircleCI and YML file. The problem is appearing in CircleCI.
Full operation stack from CircleCI:
Starting the build00:03
Installing inference daemon...
Inference daemon installed.
Starting inference daemon...
Inference daemon started.
Start container00:02config
Starting node
Applying container tweaks
$ if [ -e '/private/etc/ssh_config' ]; then LOCATION=/private/etc/ssh_config; else LOCATION=/private/etc/ssh/ssh_config; fi && sudo mv $LOCATION{,.back} && echo 'UseRoaming no' | cat - $LOCATION.back  | sudo tee $LOCATION > /dev/null ; rm -rf $HOME'/Library/MobileDevice/Provisioning Profiles/'* ; echo 'source /usr/local/share/chruby/chruby.sh'' && source /usr/local/share/chruby/auto.sh' >> ~/.bashrc && echo '2.3' > ~/.ruby-version ; sudo pmset -a displaysleep 0 disksleep 0 sleep 0 powernap 0 hibernatemode 0 && caffeinate -u echo wake up ; if [[ -d /Applications/Xcode-8.3.2.app ]]; then ln -s /Applications/Xcode-8.3.2.app /Applications/Xcode-8.3.app ; fi ; if [[ -d /Applications/Xcode-9.app ]]; then ln -s /Applications/Xcode-9.app /Applications/Xcode-9.0.app ; fi
wake up
Adding per build SSH keypair
Add containers to ~/.ssh/config as node0
Setting build environment variables
CIRCLE_ARTIFACTS=/tmp/circle-artifacts.MpVg554
CIRCLE_BRANCH=Fastlane
CIRCLE_BUILD_IMAGE=osx
CIRCLE_BUILD_NUM=27
CIRCLE_BUILD_URL=https://circleci.com/gh/Flashfoodco/flash-food-ios/27
CIRCLE_COMPARE_URL=https://github.com/Flashfoodco/flash-food-ios/compare/bc29a79314e7...bb206569eb03
CIRCLE_NODE_INDEX=0
CIRCLE_NODE_TOTAL=1
CIRCLE_PREVIOUS_BUILD_NUM=26
CIRCLE_PROJECT_REPONAME=flash-food-ios
CIRCLE_PROJECT_USERNAME=Flashfoodco
CIRCLE_REPOSITORY_URL=https://github.com/Flashfoodco/flash-food-ios
CIRCLE_SHA1=bb206569eb03a240ab18c0b33406e14c70196242
CIRCLE_TEST_REPORTS=/tmp/circle-junit.M7pJalu
CIRCLE_USERNAME=YuriRudenyaDev
fatal: No such section!
fatal: No such section!
Enable SSH00:00
Host fingerprint: SHA256:YEbR8nqYo5TFjaeXIVFscL3yl1GR4KUdaIQJJYXtrRk
You can now SSH into this VM if your SSH public key is added:
$ ssh -p 55004<EMAIL_ADDRESS>Use the same SSH public key that you use for GitHub.  If you have not added your public keys to this build and you would like to SSH to it, you can add them by clicking the "SSH to this build" button in the "Debug via SSH" tab.
This box will stay up for 30 minutes if anyone has added their keys.  This takes up one of your concurrent builds, so cancel it when you're done.
CHECKOUT
Restore source cache00:00cache
Extracting source cache...
Checkout using deploy key: f7:63:60:1b:36:be:86:9d:71:09:c5:40:b0:42:df:6e00:02config
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
remote: Counting objects: 4, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 4 (delta 2), reused 4 (delta 2), pack-reused 0
Unpacking objects: 100% (4/4), done.
From github.com:Flashfoodco/flash-food-ios
bc29a79..bb20656  Fastlane   -> origin/Fastlane
MACHINE
Configure the build00:01cache
Select Xcode Version00:00inference
Exit code: 0
sudo xcode-select --switch /Applications/Xcode-8.0.app && xcodebuild -version
Xcode 8.0
Build version 8A218a
Install Code Signing Credentials00:06inference
Dumped code signing settings from the current project to the build artifacts.
Created and unlocked circle.keychain (the password is 'circle').
1 key imported.
Found 1 provisioning profile in the project settings.
Installing /Users/distiller/Library/MobileDevice/Provisioning Profiles/a0d93954-f6fc-4da3-899f-7e800334db8c.mobileprovision => a0d93954-f6fc-4da3-899f-7e800334db8c.mobileprovision
Team:            Flashfood Inc.
App:             Flashfood Training
Team Identifier: RZLZW449XK
Expires:         2018-04-28T14:20:55.000Z
Installing 1 developer certificate(s) from provisioning profiles
1 certificate imported.
Currently installed Code-Signing identities:
Policy: Code Signing
Matching identities

1C9D98E59AAB69D449DBCDB17A97F95B7547EF94 "iPhone Distribution: Flashfood Inc. (RZLZW449XK)"
1 identities found

Valid identities only

1C9D98E59AAB69D449DBCDB17A97F95B7547EF94 "iPhone Distribution: Flashfood Inc. (RZLZW449XK)"
1 valid identities found
Restore cache00:03cache
Extracting dependency cache...
DEPENDENCIES
$ sudo gem update fastlane00:07config
Exit code: 0
sudo gem update fastlane
Updating installed gems
Updating fastlane
Fetching: claide-1.0.2.gem (100%)
Successfully installed claide-1.0.2
Fetching: colored2-3.1.2.gem (100%)
Successfully installed colored2-3.1.2
Fetching: nanaimo-0.2.3.gem (100%)
Successfully installed nanaimo-0.2.3
Fetching: xcodeproj-1.5.0.gem (100%)
Successfully installed xcodeproj-1.5.0
Fetching: addressable-2.5.1.gem (100%)
Successfully installed addressable-2.5.1
Fetching: tty-screen-0.5.0.gem (100%)
Successfully installed tty-screen-0.5.0
Fetching: commander-fastlane-4.4.5.gem (100%)
Successfully installed commander-fastlane-4.4.5
Fetching: fastimage-2.1.0.gem (100%)
Successfully installed fastimage-2.1.0
Fetching: google-api-client-0.12.0.gem (100%)
Successfully installed google-api-client-0.12.0
Fetching: fastlane-2.44.1.gem (100%)
Successfully installed fastlane-2.44.1
Gems updated: addressable claide colored2 commander-fastlane fastimage fastlane google-api-client nanaimo tty-screen xcodeproj
Fetch CocoaPods specs01:32inference
Downloading CocoaPods master repo from cocoapods-specs S3 bucket...
Uncompressing CocoaPods master repo...
Successfully downloaded CocoaPods master repo.
Using specs repo revision 366dc42bef3f87eb3900b8beee08ad71ee347a9d.
Install CocoaPods00:12inference
Exit code: 0
cd "."
export LC_CTYPE="en_US.UTF-8"
pod install --verbose
Preparing

Analyzing dependencies
[!] The version of CocoaPods used to generate the lockfile (1.2.1) is higher than the version of the current executable (1.1.1). Incompatibility issues may arise.
Inspecting targets to integrate
Using ARCHS setting to build architectures of target Pods-flash-food-ios:
(``)
Finding Podfile changes

ActionSheetPicker-3.0
Alamofire
AlamofireImage
Branch
CardIO
CircleProgressView
CocoaLumberjack
Crashlytics
DTPhotoViewerController
Fabric
FacebookCore
FacebookLogin
Google
IQKeyboardManagerSwift
MBProgressHUD
Mixpanel-swift
NVActivityIndicatorView
NYTPhotoViewer
ReachabilitySwift
RealmSwift
RxCocoa
RxSwift
Sentry
Siren
SnapKit
Stripe
SwiftSpinner
SwiftyBeaver
SwiftyJSON
Timepiece

Resolving dependencies of Podfile
Comparing resolved specification to the sandbox manifest

ActionSheetPicker-3.0
Alamofire
AlamofireImage
Bolts
Branch
CardIO
CircleProgressView
CocoaLumberjack
Crashlytics
DTPhotoViewerController
FBSDKCoreKit
FBSDKLoginKit
FLAnimatedImage
Fabric
FacebookCore
FacebookLogin
FirebaseAnalytics
FirebaseCore
FirebaseInstanceID
GTMOAuth2
GTMSessionFetcher
Google
GoogleSignIn
GoogleToolboxForMac
IQKeyboardManagerSwift
KSCrash
MBProgressHUD
Mixpanel-swift
NVActivityIndicatorView
NYTPhotoViewer
ReachabilitySwift
Realm
RealmSwift
RxCocoa
RxSwift
Sentry
Siren
SnapKit
Stripe
SwiftSpinner
SwiftyBeaver
SwiftyJSON
Timepiece

Downloading dependencies
-> Using ActionSheetPicker-3.0 (2.2.0)
-> Using Alamofire (4.4.0)
-> Using AlamofireImage (3.2.0)
-> Using Bolts (1.8.4)
-> Using Branch (0.15.3)
-> Using CardIO (5.4.1)
-> Using CircleProgressView (1.1.2)
-> Using CocoaLumberjack (3.0.0)
-> Using Crashlytics (3.8.4)
-> Using DTPhotoViewerController (0.2.1)
-> Using FBSDKCoreKit (4.23.0)
-> Using FBSDKLoginKit (4.23.0)
-> Using FLAnimatedImage (1.0.12)
-> Using Fabric (1.6.11)
-> Using FacebookCore (0.2.0)
-> Using FacebookLogin (0.2.0)
-> Using FirebaseAnalytics (3.9.0)
-> Using FirebaseCore (3.6.0)
-> Using FirebaseInstanceID (1.0.10)
-> Using GTMOAuth2 (1.1.4)
-> Using GTMSessionFetcher (1.1.10)
-> Using Google (3.1.0)
-> Using GoogleSignIn (4.0.2)
-> Using GoogleToolboxForMac (2.1.1)
-> Using IQKeyboardManagerSwift (4.0.10)
-> Using KSCrash (1.15.8)
-> Using MBProgressHUD (1.0.0)
-> Using Mixpanel-swift (2.1.6)
-> Using NVActivityIndicatorView (3.6.1)
-> Using NYTPhotoViewer (1.1.0)
-> Using ReachabilitySwift (3)
-> Using Realm (2.0.4)
-> Using RealmSwift (2.0.4)
-> Using RxCocoa (3.0.1)
-> Using RxSwift (3.0.1)
-> Using Sentry (2.1.0)
-> Using Siren (2.0.3)
-> Using SnapKit (3.0.2)
-> Using Stripe (9.4.0)
-> Using SwiftSpinner (1.1.0)
-> Using SwiftyBeaver (1.1.4)
-> Using SwiftyJSON (3.1.4)
-> Using Timepiece (0.6.0)

Running pre install hooks

Podfile

Generating Pods project

Creating Pods project
Adding source files to Pods project
Adding frameworks to Pods project
Adding libraries to Pods project
Adding resources to Pods project
Linking headers
Installing targets

Installing target ActionSheetPicker-3.0 iOS 8.0

Generating Info.plist file at Pods/Target Support Files/ActionSheetPicker-3.0/Info.plist
Generating module map file at Pods/Target Support Files/ActionSheetPicker-3.0/ActionSheetPicker-3.0.modulemap
Generating umbrella header at Pods/Target Support Files/ActionSheetPicker-3.0/ActionSheetPicker-3.0-umbrella.h

Installing target Alamofire iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Alamofire/Info.plist
Generating module map file at Pods/Target Support Files/Alamofire/Alamofire.modulemap
Generating umbrella header at Pods/Target Support Files/Alamofire/Alamofire-umbrella.h

Installing target AlamofireImage iOS 8.0

Generating Info.plist file at Pods/Target Support Files/AlamofireImage/Info.plist
Generating module map file at Pods/Target Support Files/AlamofireImage/AlamofireImage.modulemap
Generating umbrella header at Pods/Target Support Files/AlamofireImage/AlamofireImage-umbrella.h

Installing target Bolts iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Bolts/Info.plist
Generating module map file at Pods/Target Support Files/Bolts/Bolts.modulemap
Generating umbrella header at Pods/Target Support Files/Bolts/Bolts-umbrella.h

Installing target Branch iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Branch/Info.plist
Generating module map file at Pods/Target Support Files/Branch/Branch.modulemap
Generating umbrella header at Pods/Target Support Files/Branch/Branch-umbrella.h

Installing target CircleProgressView iOS 8.0

Generating Info.plist file at Pods/Target Support Files/CircleProgressView/Info.plist
Generating module map file at Pods/Target Support Files/CircleProgressView/CircleProgressView.modulemap
Generating umbrella header at Pods/Target Support Files/CircleProgressView/CircleProgressView-umbrella.h

Installing target CocoaLumberjack iOS 8.0

Generating Info.plist file at Pods/Target Support Files/CocoaLumberjack/Info.plist
Generating module map file at Pods/Target Support Files/CocoaLumberjack/CocoaLumberjack.modulemap
Generating umbrella header at Pods/Target Support Files/CocoaLumberjack/CocoaLumberjack-umbrella.h

Installing target DTPhotoViewerController iOS 8.0

Generating Info.plist file at Pods/Target Support Files/DTPhotoViewerController/Info.plist
Generating module map file at Pods/Target Support Files/DTPhotoViewerController/DTPhotoViewerController.modulemap
Generating umbrella header at Pods/Target Support Files/DTPhotoViewerController/DTPhotoViewerController-umbrella.h

Installing target FBSDKCoreKit iOS 8.0

Generating Info.plist file at Pods/Target Support Files/FBSDKCoreKit/Info.plist
Generating module map file at Pods/Target Support Files/FBSDKCoreKit/FBSDKCoreKit.modulemap
Generating umbrella header at Pods/Target Support Files/FBSDKCoreKit/FBSDKCoreKit-umbrella.h

Installing target FBSDKLoginKit iOS 8.0

Generating Info.plist file at Pods/Target Support Files/FBSDKLoginKit/Info.plist
Generating module map file at Pods/Target Support Files/FBSDKLoginKit/FBSDKLoginKit.modulemap
Generating umbrella header at Pods/Target Support Files/FBSDKLoginKit/FBSDKLoginKit-umbrella.h

Installing target FLAnimatedImage iOS 8.0

Generating Info.plist file at Pods/Target Support Files/FLAnimatedImage/Info.plist
Generating module map file at Pods/Target Support Files/FLAnimatedImage/FLAnimatedImage.modulemap
Generating umbrella header at Pods/Target Support Files/FLAnimatedImage/FLAnimatedImage-umbrella.h

Installing target FacebookCore iOS 8.0

Generating Info.plist file at Pods/Target Support Files/FacebookCore/Info.plist
Generating module map file at Pods/Target Support Files/FacebookCore/FacebookCore.modulemap
Generating umbrella header at Pods/Target Support Files/FacebookCore/FacebookCore-umbrella.h

Installing target FacebookLogin iOS 8.0

Generating Info.plist file at Pods/Target Support Files/FacebookLogin/Info.plist
Generating module map file at Pods/Target Support Files/FacebookLogin/FacebookLogin.modulemap
Generating umbrella header at Pods/Target Support Files/FacebookLogin/FacebookLogin-umbrella.h

Installing target GTMOAuth2 iOS 8.0

Generating Info.plist file at Pods/Target Support Files/GTMOAuth2/Info.plist
Generating module map file at Pods/Target Support Files/GTMOAuth2/GTMOAuth2.modulemap
Generating umbrella header at Pods/Target Support Files/GTMOAuth2/GTMOAuth2-umbrella.h

Installing target GTMSessionFetcher iOS 8.0

Generating Info.plist file at Pods/Target Support Files/GTMSessionFetcher/Info.plist
Generating module map file at Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher.modulemap
Generating umbrella header at Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher-umbrella.h

Installing target GoogleToolboxForMac iOS 8.0

Generating Info.plist file at Pods/Target Support Files/GoogleToolboxForMac/Info.plist
Generating module map file at Pods/Target Support Files/GoogleToolboxForMac/GoogleToolboxForMac.modulemap
Generating umbrella header at Pods/Target Support Files/GoogleToolboxForMac/GoogleToolboxForMac-umbrella.h

Installing target IQKeyboardManagerSwift iOS 8.0

Generating Info.plist file at Pods/Target Support Files/IQKeyboardManagerSwift/Info.plist
Generating module map file at Pods/Target Support Files/IQKeyboardManagerSwift/IQKeyboardManagerSwift.modulemap
Generating umbrella header at Pods/Target Support Files/IQKeyboardManagerSwift/IQKeyboardManagerSwift-umbrella.h

Installing target KSCrash iOS 8.0

Generating Info.plist file at Pods/Target Support Files/KSCrash/Info.plist
Generating module map file at Pods/Target Support Files/KSCrash/KSCrash.modulemap
Generating umbrella header at Pods/Target Support Files/KSCrash/KSCrash-umbrella.h

Installing target MBProgressHUD iOS 8.0

Generating Info.plist file at Pods/Target Support Files/MBProgressHUD/Info.plist
Generating module map file at Pods/Target Support Files/MBProgressHUD/MBProgressHUD.modulemap
Generating umbrella header at Pods/Target Support Files/MBProgressHUD/MBProgressHUD-umbrella.h

Installing target Mixpanel-swift iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Mixpanel-swift/Info.plist
Generating module map file at Pods/Target Support Files/Mixpanel-swift/Mixpanel-swift.modulemap
Generating umbrella header at Pods/Target Support Files/Mixpanel-swift/Mixpanel-swift-umbrella.h

Installing target NVActivityIndicatorView iOS 8.0

Generating Info.plist file at Pods/Target Support Files/NVActivityIndicatorView/Info.plist
Generating module map file at Pods/Target Support Files/NVActivityIndicatorView/NVActivityIndicatorView.modulemap
Generating umbrella header at Pods/Target Support Files/NVActivityIndicatorView/NVActivityIndicatorView-umbrella.h

Installing target NYTPhotoViewer iOS 8.0

Generating Info.plist file at Pods/Target Support Files/NYTPhotoViewer/Info.plist
Generating module map file at Pods/Target Support Files/NYTPhotoViewer/NYTPhotoViewer.modulemap
Generating umbrella header at Pods/Target Support Files/NYTPhotoViewer/NYTPhotoViewer-umbrella.h

Installing target ReachabilitySwift iOS 8.0

Generating Info.plist file at Pods/Target Support Files/ReachabilitySwift/Info.plist
Generating module map file at Pods/Target Support Files/ReachabilitySwift/ReachabilitySwift.modulemap
Generating umbrella header at Pods/Target Support Files/ReachabilitySwift/ReachabilitySwift-umbrella.h

Installing target Realm iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Realm/Info.plist
Copying module map file to Pods/Target Support Files/Realm/Realm.modulemap

Installing target RealmSwift iOS 8.0

Generating Info.plist file at Pods/Target Support Files/RealmSwift/Info.plist
Generating module map file at Pods/Target Support Files/RealmSwift/RealmSwift.modulemap
Generating umbrella header at Pods/Target Support Files/RealmSwift/RealmSwift-umbrella.h

Installing target RxCocoa iOS 8.0

Generating Info.plist file at Pods/Target Support Files/RxCocoa/Info.plist
Generating module map file at Pods/Target Support Files/RxCocoa/RxCocoa.modulemap
Generating umbrella header at Pods/Target Support Files/RxCocoa/RxCocoa-umbrella.h

Installing target RxSwift iOS 8.0

Generating Info.plist file at Pods/Target Support Files/RxSwift/Info.plist
Generating module map file at Pods/Target Support Files/RxSwift/RxSwift.modulemap
Generating umbrella header at Pods/Target Support Files/RxSwift/RxSwift-umbrella.h

Installing target Sentry iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Sentry/Info.plist
Generating module map file at Pods/Target Support Files/Sentry/Sentry.modulemap
Generating umbrella header at Pods/Target Support Files/Sentry/Sentry-umbrella.h

Installing target Siren iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Siren/Info.plist
Generating module map file at Pods/Target Support Files/Siren/Siren.modulemap
Generating umbrella header at Pods/Target Support Files/Siren/Siren-umbrella.h

Installing target SnapKit iOS 8.0

Generating Info.plist file at Pods/Target Support Files/SnapKit/Info.plist
Generating module map file at Pods/Target Support Files/SnapKit/SnapKit.modulemap
Generating umbrella header at Pods/Target Support Files/SnapKit/SnapKit-umbrella.h

Installing target Stripe iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Stripe/Info.plist
Generating module map file at Pods/Target Support Files/Stripe/Stripe.modulemap
Generating umbrella header at Pods/Target Support Files/Stripe/Stripe-umbrella.h

Installing target SwiftSpinner iOS 8.0

Generating Info.plist file at Pods/Target Support Files/SwiftSpinner/Info.plist
Generating module map file at Pods/Target Support Files/SwiftSpinner/SwiftSpinner.modulemap
Generating umbrella header at Pods/Target Support Files/SwiftSpinner/SwiftSpinner-umbrella.h

Installing target SwiftyBeaver iOS 8.0

Generating Info.plist file at Pods/Target Support Files/SwiftyBeaver/Info.plist
Generating module map file at Pods/Target Support Files/SwiftyBeaver/SwiftyBeaver.modulemap
Generating umbrella header at Pods/Target Support Files/SwiftyBeaver/SwiftyBeaver-umbrella.h

Installing target SwiftyJSON iOS 8.0

Generating Info.plist file at Pods/Target Support Files/SwiftyJSON/Info.plist
Generating module map file at Pods/Target Support Files/SwiftyJSON/SwiftyJSON.modulemap
Generating umbrella header at Pods/Target Support Files/SwiftyJSON/SwiftyJSON-umbrella.h

Installing target Timepiece iOS 8.0

Generating Info.plist file at Pods/Target Support Files/Timepiece/Info.plist
Generating module map file at Pods/Target Support Files/Timepiece/Timepiece.modulemap
Generating umbrella header at Pods/Target Support Files/Timepiece/Timepiece-umbrella.h

Installing target Pods-flash-food-ios iOS 9.0

Generating Info.plist file at Pods/Target Support Files/Pods-flash-food-ios/Info.plist
Generating module map file at Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.modulemap
Generating umbrella header at Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios-umbrella.h

Running post install hooks

Podfile

Writing Xcode project file to Pods/Pods.xcodeproj

Generating deterministic UUIDs

Writing Lockfile in Podfile.lock
Writing Manifest in Pods/Manifest.lock

Integrating client project
Integrating target Pods-flash-food-ios (flash-food-ios.xcodeproj project)

Running post install hooks

cocoapods-stats from
/opt/rubies/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/cocoapods-stats-1.0.0/lib/cocoapods_plugin.rb

Sending stats
- ActionSheetPicker-3.0, 2.2.0
- Alamofire, 4.4.0
- AlamofireImage, 3.2.0
- Bolts, 1.8.4
- Branch, 0.15.3
- CardIO, 5.4.1
- CircleProgressView, 1.1.2
- CocoaLumberjack, 3.0.0
- Crashlytics, 3.8.4
- DTPhotoViewerController, 0.2.1
- FBSDKCoreKit, 4.23.0
- FBSDKLoginKit, 4.23.0
- FLAnimatedImage, 1.0.12
- Fabric, 1.6.11
- FacebookCore, 0.2.0
- FacebookLogin, 0.2.0
- FirebaseAnalytics, 3.9.0
- FirebaseCore, 3.6.0
- FirebaseInstanceID, 1.0.10
- GTMOAuth2, 1.1.4
- GTMSessionFetcher, 1.1.10
- Google, 3.1.0
- GoogleSignIn, 4.0.2
- GoogleToolboxForMac, 2.1.1
- IQKeyboardManagerSwift, 4.0.10
- KSCrash, 1.15.8
- MBProgressHUD, 1.0.0
- Mixpanel-swift, 2.1.6
- NVActivityIndicatorView, 3.6.1
- NYTPhotoViewer, 1.1.0
- ReachabilitySwift, 3
- Realm, 2.0.4
- RealmSwift, 2.0.4
- RxCocoa, 3.0.1
- RxSwift, 3.0.1
- Sentry, 2.1.0
- Siren, 2.0.3
- SnapKit, 3.0.2
- Stripe, 9.4.0
- SwiftSpinner, 1.1.0
- SwiftyBeaver, 1.1.4
- SwiftyJSON, 3.1.4
- Timepiece, 0.6.0
-> Pod installation complete! There are 30 dependencies from the Podfile and 43 total pods installed.
[!] Your Podfile has had smart quotes sanitised. 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.
[!] xcodeproj was renamed to project. Please update your Podfile accordingly.
[!] The flash-food-ios [Debug] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] The flash-food-ios [Staging] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] The flash-food-ios [Development] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.development.xcconfig'. This can lead to problems with the CocoaPods installation     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] The flash-food-ios [Development] target overrides the SWIFT_VERSION build setting defined in Pods/Target Support Files/Pods-flash-food-ios/Pods-flash-food-ios.development.xcconfig'. This can lead to problems with the CocoaPods installation     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] The flash-food-ios [Release] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] The flash-food-ios [Production] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] 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     - Use the $(inherited)` flag, or
- Remove the build settings from the target.
[!] Google has been deprecated
DATABASE
Save cache00:20cache
Creating dependency cache from the following paths:
✓ /Users/distiller/.bundle
✗ /Users/distiller/.cache/bower
✗ /Users/distiller/.go_workspace
✗ /Users/distiller/.gradle
✗ /Users/distiller/.ivy2
✗ /Users/distiller/.m2
✓ /Users/distiller/flash-food-ios/Pods
✗ /Users/distiller/flash-food-ios/vendor/bundle
✗ /Users/distiller/virtualenvs
Creating source cache from the following paths:
✓ /Users/distiller/flash-food-ios/.git

It is not code signing issue. Could you check operation stack? We are sticking here:
[04:39:04]: $ xcodebuild -list -workspace ./flash-food-ios.xcworkspace
[04:39:06]: Multiple schemes found but you haven't specified one.
The next step should be $ xcodebuild -showBuildSettings -workspace ./Timer.xcworkspace -scheme Timer

SOLUTION:
Git ignore doesn't commit schemes. Just remove all Xcode lines from git a ignore file and "force" commit all schemes

Actually, there is a better solution. In your fastfile, you got to add (if you do scan):
  scan(
	scheme: "TheNameOfTheSchemeYouNeedItToLookAt"
)

You are basically telling it to choose the correct scheme name.


Timestamp in EnclaveRegistry in teerex pallet never gets refreshed

There's a config type MaxSilenceTime in pallet_teerex that controls how long a worker can stay silent. If it goes beyond this time, the enclave will be removed.
However, the timestamp seems never refreshed after the initial registration. It should either be an upstream bug or we misused it.
It means after MaxSilenceTime milliseconds (current setting = 48 hours) the enclave will be removed from the EnclaveRegistry and no more syncing is possible.
Tested with MaxSilenceTime = 120_000:

Worker logs:
[2022-11-19T23:20:46Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:47Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:47Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:47Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:48Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:48Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:48Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author
[2022-11-19T23:20:49Z WARN  its_block_verification::slot] Authorities list is empty, cannot determine slot author

Reported upstream


Publish CTRF JSON plugin

Repository URL
https://github.com/ctrf-io/ctrf-json-plugin
New Repository Name
ctrf-json-plugin
Description
This plugin allows users to publish CTRF reports on jenkins, CTRF is a JSON test report schema that provides standardized JSON test results reports.
GitHub users to have commit permission
ma11hewthomas
Jenkins project users to have release permission
ma11hewthomas
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.28.0)

The Jenkins Security Scan discovered 3 finding(s) :mag:.
Please follow the instructions below for every identified issues:

Implement the recommended fix to address the issue.
If you think it's a false positive, suppress the warning directly within the code.
Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
HelloWorldBuilder.java#174
Potential CSRF vulnerability: If DescriptorImpl#doCheckJsonFilePattern connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Stapler: Missing permission check
You can find detailed information about this finding here.
HelloWorldBuilder.java#174
Potential missing permission check in DescriptorImpl#doCheckJsonFilePattern

Jenkins: Potentially unsafe classes
You can find detailed information about this finding here.
HelloWorldBuilder.java#100
This use of class [javax.xml.transform.TransformerFactory](1) should be reviewed for unsafe behavior, like allowing XML External Entity injection, or arbitrary code execution.

/hosting re-check

/hosting re-check

/request-security-scan

The Jenkins Security Scan discovered 3 finding(s) :mag:.
Please follow the instructions below for every identified issues:

Implement the recommended fix to address the issue.
If you think it's a false positive, suppress the warning directly within the code.
Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
HelloWorldBuilder.java#189
Potential CSRF vulnerability: If DescriptorImpl#doCheckJsonFilePattern connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Stapler: Missing permission check
You can find detailed information about this finding here.
HelloWorldBuilder.java#189
Potential missing permission check in DescriptorImpl#doCheckJsonFilePattern

Jenkins: Potentially unsafe classes
You can find detailed information about this finding here.
HelloWorldBuilder.java#101
This use of class [javax.xml.transform.TransformerFactory](1) should be reviewed for unsafe behavior, like allowing XML External Entity injection, or arbitrary code execution.

The Jenkins Security Scan discovered 3 finding(s) :mag:.
Please follow the instructions below for every identified issues:

Implement the recommended fix to address the issue.
If you think it's a false positive, suppress the warning directly within the code.
Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
HelloWorldBuilder.java#189
Potential CSRF vulnerability: If DescriptorImpl#doCheckJsonFilePattern connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Stapler: Missing permission check
You can find detailed information about this finding here.
HelloWorldBuilder.java#189
Potential missing permission check in DescriptorImpl#doCheckJsonFilePattern

Jenkins: Potentially unsafe classes
You can find detailed information about this finding here.
HelloWorldBuilder.java#101
This use of class [javax.xml.transform.TransformerFactory](1) should be reviewed for unsafe behavior, like allowing XML External Entity injection, or arbitrary code execution.

Maybe fix the package name and rename HelloWorldBuilder, that doesn't look good 😉

@daniel-beck thanks for the feedback, I've made those changes.

/request-security-scan

/hosting re-check

The Jenkins Security Scan discovered 3 finding(s) :mag:.
Please follow the instructions below for every identified issues:

Implement the recommended fix to address the issue.
If you think it's a false positive, suppress the warning directly within the code.
Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
PublishCtrfJson.java#189
Potential CSRF vulnerability: If DescriptorImpl#doCheckJsonFilePattern connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Stapler: Missing permission check
You can find detailed information about this finding here.
PublishCtrfJson.java#189
Potential missing permission check in DescriptorImpl#doCheckJsonFilePattern

Jenkins: Potentially unsafe classes
You can find detailed information about this finding here.
PublishCtrfJson.java#101
This use of class [javax.xml.transform.TransformerFactory](1) should be reviewed for unsafe behavior, like allowing XML External Entity injection, or arbitrary code execution.

Sorry about the misleading suppression guidance, it's being fixed in https://github.com/jenkins-infra/jenkins-codeql/pull/42.

/request-security-scan

/hosting re-check

The Jenkins Security Scan discovered 1 finding(s) :mag:.
Please follow the instructions below for every identified issues:

Implement the recommended fix to address the issue.
If you think it's a false positive, suppress the warning directly within the code.
Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
PublishCtrfJson.java#189
Potential CSRF vulnerability: If DescriptorImpl#doCheckJsonFilePattern connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

/request-security-scan

/hosting re-check

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

/hosting re-check

/hosting re-check

Hello, I looked at the repository of the plugin and I have a few comments.

https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/pom.xml#L30-L31 it is not recommended to have no value in the changelist as in Maven context, development versions are suffixed with -SNAPSHOT. Please use -SNAPSHOT in changelist.
You seem to have followed (mostly) the CD enablement but the workflow is not present. Any reason not to use it?
You have a mismatch between jenkins.version and the BOM used (https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/pom.xml#L34 and https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/pom.xml#L43)
Please update the parent pom version (https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/pom.xml#L7)
The plugin description in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/pom.xml#L15 is deprecated and will break you plugin build in the future. Please put it in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/src/main/resources/index.jelly#L3
the team in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/.github/CODEOWNERS#L1 should be @jenkinsci/jenkins-ctrf-json-plugin-developers
the tag template in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/.github/release-drafter.yml#L2 should be ctrf-json-plugin-$NEXT_MINOR_VERSION
the principal branch of the repository is main. Please remove master from https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/.github/workflows/release-drafter.yml#L7-L8
I'd suggested to add the license header in your source code files
in https://github.com/ctrf-io/ctrf-json-plugin/tree/main/src/main/resources/io/jenkins/plugins/PublishCtrfJson, you are still using the demo plugin configuration ("use french" and such) when you don't have such fields in your configuration file
I understand it can be tiring but you might want to consider create unit tests for you test result parser.

Looking at what you plugin is doing, it seems that it's converting the CTRF files to JUnit format and let the JUnit plugin interpret those. I'm curious to know if you have tested to use your plugin on a project build that also has a JUnit report? How are the two behave?

Is it possible that the report be larger than the possible size of a String and so creates a problem with https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/src/main/java/io/jenkins/plugins/PublishCtrfJson/PublishCtrfJson.java#L62?
in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/src/main/java/io/jenkins/plugins/PublishCtrfJson/PublishCtrfJson.java#L80-L90 you publish a JUnit report for each CTRF file. Wouldn't it be better to publish only one for all of them?
I would suggested to be more specific than Exception in https://github.com/ctrf-io/ctrf-json-plugin/blob/360acb3945510516a9738ffeb77ccfbe34d00c03/src/main/java/io/jenkins/plugins/PublishCtrfJson/PublishCtrfJson.java#L92

you are not marking the build / run as failed if an exception occurred, is that voluntary?

I'd suggested to add the license header in your source code files

Most plugins don't do this

@alecharp thanks for the review
All items have been completed - additional comments below:
Is it possible that the report be larger than the possible size of a String and so creates a problem with
I’ve amended to use Jackson stream, which manages this better
you publish a JUnit report for each CTRF file. Wouldn't it be better to publish only one for all of them?
In most instances a single CTRF report is generated by the test frameworks, although multiple executions may happen in the same build, for this reason I don’t think it’s worth rearchitecting the approach at this stage.
Looking at what you plugin is doing, it seems that it's converting the CTRF files to JUnit format and let the JUnit plugin interpret those. I'm curious to know if you have tested to use your plugin on a project build that also has a JUnit report? How are the two behave?
I’ve tested both publish CTRF and publish junit and they behave nicely together. All tests are published successfully.
* you are not marking the build / run as failed if an exception occurred, is that voluntary?
Now marking build as failed if exception occurs
I would suggested to be more specific than Exception in
improved exception handling overall
* I'd suggested to add the license header in your source code files
`Not required as mentioned by @timja

Looks good so far! But I'd recommend

https://github.com/ctrf-io/ctrf-json-plugin/blob/f6318c46e8ec5ff7be535bf3591e4184852321bb/pom.xml#L113-L117 replacing that with org.xmlunit:xmlunit-legacy:2.10.0. The old package is end of life.
Removing the .vscode folder, you just need that locally, not on GitHub.
ensuring your plugin compiles with mvn clean verify package

Thanks for the feedback @NotMyFault, I've applied the recommended changes

/hosting host


Improve documentation on extensions

This PR improves the documentation on extensions and adds a list of extensions developed by users.

@J535D165 thank you for your review!
Broken links in the documentation are checked with linkchecker. For the website I have a broken link detector installed. For other repositories we have to manually check the broken links. Let me know if you are publishing a new release and I will make time to go trough all other repositories.


Setup Kanban Board

Project Link: https://github.com/cancelei/JS-capstone-M2/projects/3
We work on this project in a group of two Programmers.

Hi @Salarhabibi-amir and @cancelei
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not have the correct link on the description. The link needs to send to the project
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

STATUS: APPROVED :100:
There is nothing else to say than it's time to merge... :partying_face:
Cheers and Happy coding! :clap:  :computer:  :wine_glass:
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
You can also consider:
Please be reminded to not open a new pull request after you get a review, only use the same one :thought_balloon:
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
_As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Closing issue since both participants completed the task.


Run Selection/Line in interactive window shortcut does not work

Jupyter: v2022.8.1002431955Version: 1.71.2
Commit: 74b1f979648cc44d385a2286793c226e611f59e7
Date: 2022-09-14T21:07:15.900Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: No

I tried the same key comb with my other files (in a non-jupyter env) and it works. For some reason, I have to click the action in the context menu after a selection. A shortcut wouldn't execute my selection. I believe I set it up to only work with .py file. I attached my keybindings.json. Am I missing something or maybe this is a bug.
keybindings.json.zip

Do you have this setting enabled?
"jupyter.sendSelectionToInteractiveWindow": true

@amunger Thank you man... it works.

no problem - it would make more sense for us to enable that command if send to terminal and send to IW each have dedicated commands as was the case for you, but we're just disabling it entirely right now.


Plugins routes issues

Temporarily load CakeDC\Users plugin after our plugins, fixes issue with broken routes

:+1:

:+1:


Add CLI for clipping cubes

Required for metoppv/mo-blue-team#516
Acceptance_test_PR: metoppv/improver_test_data#17
Adds in a CLI calling a pre-existing function in IMPROVER to clip data in a cube between an upper and lower bound. This is required to be able to clip cloud bases to 0m in the suite. This PR also includes some acceptance tests for the new CLI.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I've updated the docsting as you mentioned to make it clearer.
When I was running a suite I realised that the function clip_cube_data  only works on gridded data as it requires an x and y coordinate to slice over. This is done to reduce memory requirements but as spot data isn't as memory hungry np.clip can be called directly in the cli. I've added some accpetance tests for this as well.


conflict in package on mirror update

When trying to mirror precise or trusty from packages.erlang-solutions.com/ubuntu/
I get this error:
$ aptly mirror update erlang-precise
Downloading http://packages.erlang-solutions.com/ubuntu/dists/precise/InRelease...
Downloading http://packages.erlang-solutions.com/ubuntu/dists/precise/Release...
Downloading http://packages.erlang-solutions.com/ubuntu/dists/precise/Release.gpg...
gpgv: Signature made Thu 11 Dec 2014 06:46:05 AM CST using RSA key ID A14F4FCA
gpgv: Good signature from "Erlang Solutions Ltd<EMAIL_ADDRESS>Downloading & parsing package files...
Downloading http://packages.erlang-solutions.com/ubuntu/dists/precise/contrib/binary-amd64/Packages.bz2...
ERROR: unable to update: conflict in package elixir_1.0.0-1_all

The -force-overwrite doesn't appear to be usable for the mirror commands and I'm not sure how to work around this.

@paulczar this seems to be exact duplicate of #183. I'll try to deal with it today and release nightly build.


cis scan p0 test automation

Issue:
https://github.com/rancher/qa-tasks/issues/783

This PR serves the purpose of automating the CIS Scan P0 checks.
Following are the requirements before running the test.

Should have a cluster ready on rancher server.
Following config file should be set as CATTLE_TEST_CONFIG.

rancher:
 host: "<rancher server IP address>"
 adminToken: "<admin/user token>"
 cleanup: true
 clusterName: "<Name of cluster>"
cis:
 profileName: "<CIS Profile Name>"

Update everything in the angle brackets < > with actual value.
run the test with following command.
go test csibenchmark_test.go -timeout 0m -v
If all the checks pass, the test will pass successfully. If there are any failures, the test will fail and list all the failures in terminal/console.

@anupama2501 @sowmyav27 could you please review again.

@caliskanugur Please review again.

@sowmyav27 please review and accept the changes. Merging is blocked for your review.

Also can we get a forward port? Thank you!

@vivek-shilimkar looks good to me, could you do a forward port. Is there any other concerns @sowmyav27 ?

Could we have a 2.8 port and a rebase?

In addition I've created a new func for running scan, since the code will run the scan more than once.

Closing this PR since it is not valid anymore.


Please cite your work

Hi,
Do you have a user study and a paper reference for your metrics?
edit:  This is really a poor way to communicate, but I couldn't find an email address or other way to add the request.
Thanks
-Alex

You can reach me at<EMAIL_ADDRESS>There is no public documentation yet. I'll try to produce something soon, say in two weeks.


tests: Add assert for multiple initializations

Added an assert in render framework to flag an InitFramework() call
when the VkInstance is already initialized. Re-initializing without an
explicit shutdown was leaking Vk* resources and sowing potential ICD
confusion. Fixed a few tests that tripped the assert.

Thanks for the changes - LGTM

Tony pointed out a much better fix for the multi-init tests that avoids using the ShutdownFramework() big hammer.


Baseline correcting signal

Hello
I have a 7 minute nature video recording at the beginning of my experiment which I would like to use as baseline for my EDA and RR signal. Currently I'm just using the whole 7 minutes or the last 3 minutes which can be a bad choice because it is possible that a participant relaxes at the beginning but after some minutes starts getting annoyed of the video. I thought about searching the minimum EDA or RR/HR signal of the video baseline and then using for example a 10s window around this minimum as baseline.
Do you know other common possibilities? I did not find very much useful information about baseline correction for this special case.

Hi Dominique
Thank you very much for your fast answer, it is great. In detail, I'm using the following features:
EDA: Latency, rise time, recovery time, number of peaks, mean/max/min/std of phasic and tonic signal, mean/max/min of amplitude
RR: mean, sdnn, sdss, pnn50, pnn20 as well as high and low frequency features
Regarding baseline correction I thought about calculating the above features in a 10 second window around the minimum of EDA or RR during baseline period.
Which of the features would you baseline correct? I don't understand completely why amplitudes should not be baseline corrected. When I run cvxEDA then I still get differences in amplitudes between participants.

Do you have any thoughts on this?

@Eichhof
For RRi, it often makes sense to correct for baseline as you're interested in RRi variations rather than absolute values. For example, let's say that the mean or minimum heart rate, during your experimental stimulus, is 80bpm. This could be a deceleration or a acceleration, depending on the baseline heart rate (if it was 100 or 60 bpm just before the stimulus).
To simplify, for EDA, the phasic component is detrended to keep only the SCRs. Other parts of the signal when there are no SCRs (which are event related responses) are 0. So you don't need to correct for the baseline, which is 0. Moreover, the values make sense in themselves:

"Although individuals and experimental situations vary considerably, some very general estimations of 'typical' strength values can be provided. In terms of phasic SCRs, amplitudes can typically range from threshold to a maximum of around 2-3uS (X = 0.30uS - 1.30uS: raw scores, non-normalized) and around 0.20 - 0.60uS on average when logarithmized. In experiments where highly aversive / threatening / fearful stimuli are used, this maximum response can increase to around 8uS (non-normalized), but this is rare. Estimations for the Frequency of NS-SCRs are difficult, but an average of 1-3 per/min (with around 10 per/min being possible during periods of quietness) has been suggested. High arousal is associated with around 20-25 per/min (Boucsein, 2012). For SCL, a range of 1-40uS has been mentioned (Venables & Christie, 1980) though averages are more likely between 2 -16uS. These numbers can be influenced by the size of electrodes and this should be noted in all scientific reporting" (here)

Hi Dominique
Thanks, that matkes sense. But when I look at the mean of the phasic component rather than the max amplitude then it makes again sense to baseline correct, am I right? I think the same should hold for the tonic component because it is not bounded to 0.

I don't know, for EDA traditional outcomes are either the number of SCRs or their amplitude (peak max). I've personally never heard of averaging the signal


Ensure that the default network does not exist in a project

Possible check to target the following resource

[ ] google_project

closing, tracking in spreadsheet


[Task]: Write migration for auto-commit for the removal of version info from app JSON

SubTasks
TBD

We don’t need a migration script for auto-commit, and here’s why:
The transition from a push- to pull-based upgrade model occurs only when:

The release_jit_package_pull_enabled flag is accessible.
The package is published after the above flag is enabled.

When the package is published, uncommitted changes can arise in two scenarios:

Legitimate changes due to interface-level updates in the modules.
Version information removal causing changes, even without interface updates.

Since users transitioning from the push model already encounter version bump-related changes, migration scripts are unnecessary. Basically, the existing experience of the users with push model eliminates the need of writing such migration.


Is it possible to pass a single file with all the arguements instead of specifying them on the command line?

subj

I don't believe so atm.

ok, thanks


Attempt to create scheme-specific collections in database

I think it would be beneficial to have the data separated by scheme in firestore. This way, we wouldn't have to wipe the database every time we release a new scheme, and we could also export scheme-specific JSON files. I believe implementing this means messing with the firestore security rules, so I'm going to wait to try it until after data collection for scheme 1 is done.

OK, sounds good. As a cautionary measure, it may be good to download the data before making any changes to Firebase to avoid accidental deletions or confusions that we would need to sort out later.

I think it would be beneficial to have the data separated by scheme in firestore.

@chunyuema or @ekuller, if it so happens that you are aware of any considerations or Firebase workings in this regard, I would appreciate your comment (no worries if you are busy).

I believe I've made a breakthrough here. By slightly altering the firebase security rules, I've successfully been able to create a second collection titled "users-scheme2." This is where I plan to send the user data for scheme 2. I will close this issue after a little more testing.

Excellent!


⚠ Bofrost.fr has degraded performance

In 55e8b38, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1172 ms

Resolved: Bofrost.fr performance has improved in 6891363 after 6 minutes.


Polygon2.Contains doesn't work properly

When a long rectangle is checked against a small circle along a diagonal axis, the Polygon2.Contains test misreports overlaps. See pictures: https://imgur.com/a/tuuV5Ph

I've found a more resilient approach for polygon intersection that should resolve this issue, coding it up now

I believe this is fixed with https://github.com/Tjstretchalot/SharpMath2/commit/a48eb507daee280d39f884e550fc0c362040f6d3


JWKS implementation

Purpose

Currently JWKs endpoints serve traffic without SSL. Also they are a part of existing STS process.
As a good practice we need to implement JWKS server as a separate process and also serve it through TLS as a way to trust bootstrap.

Didn't we decide to write test cases for this in the code review? If this is not urgent shall we do it?

Can we have all the environment variables and other required constants described in the description section of the PR ?


F-Droid: Add Fastlane File Structure for App Description

By adding the Fastlane File Structure we can speed up the time necessary from pushing a tag until it being shown in the F-Droid App store. Furthermore it is possible to provide the corresponding data, images and screenshots to be shown on the app page.
The file structure required can be seen here:

https://gitlab.com/-/snippets/1895688

More info about fastlane can be found here:

https://docs.fastlane.tools/actions/supply/

Ticket is (softly) blocked by #14 (not mandatory, but nice to have)
Ticket is blocked by #16 (required for version and changelog)
Ticket is blocked by #17


Update machine-learning-faq.md

This is a very subtle change but I felt that the previous version of this sentence "you can provide a blob storage location" was ambiguous. I've asked around and have determined that a blob storage location must be provided.

Hi @jamiekt, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Make Java extractors resilient to libraries without sources. [phab:D820]

Created by hanwen at 2016-04-07 15:05:53:
These can occur in Bazel BUILD files as forwarding targets for other
libraries.
Fixes #1102

zarko wrote at 2016-04-07 19:01:24:
Thanks!

zarko accepted this revision at 2016-04-07 19:01:24

zarko closed via commit 9f119475d16ae1b477a3a8b2d808c2c8248c8fdb at 2016-04-07 19:04:00


HTML injection

User input HTML should not get rendered, come on

Bro is building a whole subscription model and ecosystem but hasn't even finished the most basic functionality :skull:

@moritz-t-w
ChatGPT is free and will remain that way forever. The CodeGPT Plus version is paid and allows the entire team to continue working on the extension.
We are moving to a new version of the chat very soon that comes with all of this improved. Thank you for your comments, they help us continue improving the version and always make it FREE!

Oh I misinterpreted that banner. Thanks!


Infer @PointerBounds macro from clang __counted_by parameters

This results in an automatic wrapper function with safe pointer types
when the imported function has bounds attributes. This exercises similar
pathways as the recently added functionality for specifying macros from
swift_attr, and fixes some bugs related to macro source file management.
Includes some unmerged commits from #76969.

With luck, https://github.com/swiftlang/swift/pull/77580 should make the rebased version of this PR functional. I'm sure I missed something there, though.

With luck, #77580 should make the rebased version of this PR functional. I'm sure I missed something there, though.

Indeed, it works now! I'll start addressing the rest of the comments.

What is the difference between a language feature and and a flag?

There's a bunch of machinery around language features and their lifecycle that we don't get from a one-off flag. Plus, flags need to be manually handled in the driver, whereas language features are already available.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

After all the iterations of rebasing most of the intermediate commits didn't build anymore, and many contained a bunch of code that's removed in later commits, so I squashed them

@swift-ci please smoke test Windows


$interval sometime make browser and server stuck

https://github.com/afaqurk/linux-dash/blob/master/js/linuxDash.js#L396
https://github.com/afaqurk/linux-dash/blob/master/js/linuxDash.js#L505
refreshRate is 1000 ms as default. if scope.getData function execution-time longer than 1000ms, it'll make long Ajax queue, then browser and server stuck.
Usually my server response in 500ms. When busy will response out 1000ms or 2000ms. then not work well.
$timeout is better.

Good point, @weibangtuo . But I am not sure that using $timeout would solve anything. Linux Dash would still need to queue multiple $timeout instances due to the polling nature of requests when not using websockets. It would essentially be the same exact problem with more lines of code.
But you're right, I can imagine the queue getting large for slow responses from server. I am open to any suggestions to address this concern.

Could you not just use a $timeout and call a $timeout again when you've received a response from the server?

@triforce
You can definitely do that but it would cause 2 problems:

it becomes difficult to manage the cadence of the polling with $timeout. Instead of waiting 1000ms, the graph might be updated 100 times a second for a server with fast response time and 1 time per 3 seconds for a slow server. Since we lose control of the interval and simply queue up a $timeout right after the previous one finishes, it will introduce classic polling complexities about spamming servers.

data rendered on graph will have an inconsistent time-series. When the server response time changes, the number of plot points / second for that chart will also change. This can lead to misleading graph lines when the server slows down response times and plot points stretch across the time series of the graph.

Right now, OP's original issue is limited to servers with slow response times. By making the $timeout change, we introduce issues for everyone, regardless of response times.

@weibangtuo : I have tried to implement a possible solution on the interval-handling-enhancement branch.
You can see the changes here. An interval iteration will simply skip a server call if any previous call is still in progress. This would allow a faster server response to stay true to the interval while a slower series of server responses will cause iterations to be skipped until all calls are resolved.
Could you please try pulling down that branch and check to see if your issue is mitigated by the updates? If so, I can then proceed to clean-up the code and test it further.
Code feedback / improvements are welcome.

:+1:


vertical layout of \underset and \overset

Thanks for fixing #1275. This may be nitpicking, but I'm still not quite happy with \underset and \overset.
Compare the output of
\overset{a}{b}b\underset{a}{b}b

in LaTeX and KaTeX. In LaTeX, all b's are at exactly the same height, whereas in KaTeX the b's wobble.
Is this a known issue/limitation? Only reference to underset/overset I found is #1081 which I think is something different.
I understand that's not top priority, but I thought I'd mention.

KaTeX:

LaTeX (via quicklatex):

The wiggles definitely seem wrong, but so does the horizontal spacing between elements? Ideas, @ronkok?

My first guess is that the base element is being shifted from the baseline to a point where it is centered on the math axis. And my second guess is that we can fix that by changing line 75 in op.js from
if (base instanceof domTree.symbolNode) {

to
if (group.value.symbol) {

In fact, that line actually did read at one time exactly the way I am proposing. Some one had to have changed it and I don't know why. So before I charge in and change it back, I want to think a bit about why they may have done that. Give me a day or two.

@ronkok I traced that particular line back, and it's been there for at least 3 years. Maybe there was another place where you changed it which you're thinking of?

Maybe it was a different line that changed. I still think that line is the most likely way to fix this problem. I'll do some testing.

Fixed by #1290. Thanks for the bug report!


Renderer Optimization Round 1

Its time to start making the renderer fast! This first round is just picking a lot of low hanging fruit.
I ran my tests using the Bevymark example with 10,000 entities.
Starting Performance
// these numbers apply to both moving and non-moving sprites
frame_time    : 0.038522    (avg 0.038975)
fps           : 26.670384   (avg 26.018069)

This PR
// when sprites are static / don't move
frame_time    : 0.017887    (avg 0.017899)
fps           : 55.642482   (avg 55.782829)

// when sprites are moving
frame_time    : 0.023547    (avg 0.022696)
fps           : 41.949551   (avg 42.599443)

Summary of changes
(applied in order, so each item's numbers includes the previous item's changes)

Added change detection to RenderResourceNode, Sprites, and Transforms, which improved performance when those values don't change. (static: 0.0267, dynamic: 0.0336)
Mesh provider system now only updates mesh specialization when it needs to (static: 0.0250, dynamic: 0.0331)
Stop clearing bind groups every frame and remove stale bind groups every other frame. (static: 0.0265)

this is slightly more expensive on bevymark, but i think its probably still the right thing to do. ill keep an eye on this.

Store unmatched render resource binding results (which prevents redundant computations per-entity per-frame) (static: 0.02411)
Don't send render pass state change commands when the state has not actually changed (static: 0.0179, dynamic: 0.0227)

Looks like the load_gltf example isn't displaying anything

Actually that seems unrelated. I'm also hitting the gltf issue on the master branch.

I'm seeing a problem using this branch. I see a panic on this unwrap https://github.com/cart/bevy/blob/render-opt-round1/crates/bevy_wgpu/src/renderer/wgpu_render_resource_context.rs#L489
The issue seems to be that one part of the infrastructure has a BufferId that has been invalidated because the buffer it references has been resized here: https://github.com/cart/bevy/blob/render-opt-round1/crates/bevy_render/src/render_graph/nodes/render_resources_node.rs#L454
I think this call to write_uniform_buffers should be fixing the BufferId handle that's been removed but it's now behind a Changed filter that didn't used to be there and that is preventing it from getting called: https://github.com/cart/bevy/blob/render-opt-round1/crates/bevy_render/src/render_graph/nodes/render_resources_node.rs#L468
I'm not sure what the relationship is between the RenderResources component that controls the Changed filter and the arrays that are getting resized. But I assume that whatever change it is that causes the array to resize isn't getting caught by the change tracker. If I remove the Changed filter from the query then the panic goes away for me.

I'm also seeing this panic, which I think is related to this branch as I've never noticed it before but I'm not sure what exactly I'm doing to trigger it. It appears intermittently.
thread 'main' panicked at 'current render pipeline has a layout which is incompatible with a currently set bind group, first differing at entry index 1', /home/alec/.cargo/registry/src/github.com-1ecc6299db9ec823/
wgpu-0.6.2/src/backend/direct.rs:1355:35
stack backtrace:
   0: rust_begin_unwind
             at /rustc/1773f60ea5d42e86b8fdf78d2fc5221ead222bc1/library/std/src/panicking.rs:495:5
   1: std::panicking::begin_panic_fmt
             at /rustc/1773f60ea5d42e86b8fdf78d2fc5221ead222bc1/library/std/src/panicking.rs:437:5
   2: <core::result::Result<T,E> as wgpu::backend::direct::PrettyResult<T>>::unwrap_pretty::{{closure}}
             at /home/alec/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/backend/direct.rs:1355:35
   3: core::result::Result<T,E>::unwrap_or_else
             at /home/alec/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:825:23
   4: <core::result::Result<T,E> as wgpu::backend::direct::PrettyResult<T>>::unwrap_pretty
             at /home/alec/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/backend/direct.rs:1355:9
   5: <wgpu::backend::direct::Context as wgpu::Context>::command_encoder_end_render_pass
             at /home/alec/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/backend/direct.rs:1253:9
   6: <wgpu::RenderPass as core::ops::drop::Drop>::drop
             at /home/alec/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/lib.rs:2280:13
   7: core::ptr::drop_in_place
             at /home/alec/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175:1
   8: core::ptr::drop_in_place
             at /home/alec/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175:1
   9: <bevy_wgpu::renderer::wgpu_render_context::WgpuRenderContext as bevy_render::renderer::render_context::RenderContext>::begin_pass
             at /home/alec/Code/Vendor/bevy/crates/bevy_wgpu/src/renderer/wgpu_render_context.rs:152:9
  10: <bevy_render::render_graph::nodes::pass_node::PassNode<Q> as bevy_render::render_graph::node::Node>::update
             at /home/alec/Code/Vendor/bevy/crates/bevy_render/src/render_graph/nodes/pass_node.rs:207:9
  11: bevy_wgpu::renderer::wgpu_render_graph_executor::WgpuRenderGraphExecutor::execute
             at /home/alec/Code/Vendor/bevy/crates/bevy_wgpu/src/renderer/wgpu_render_graph_executor.rs:73:25
  12: bevy_wgpu::wgpu_renderer::WgpuRenderer::run_graph
             at /home/alec/Code/Vendor/bevy/crates/bevy_wgpu/src/wgpu_renderer.rs:103:9
  13: bevy_wgpu::wgpu_renderer::WgpuRenderer::update
             at /home/alec/Code/Vendor/bevy/crates/bevy_wgpu/src/wgpu_renderer.rs:114:9
  14: bevy_wgpu::get_wgpu_render_system::{{closure}}
             at /home/alec/Code/Vendor/bevy/crates/bevy_wgpu/src/lib.rs:39:9

I'm also seeing the same panic as above randomly
thread 'main' panicked at 'current render pipeline has a layout which is incompatible with a currently set bind group, first differing at entry index 2', /Users/francois/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/backend/direct.rs:1355:35

most of the time with at entry index 1, got a few times at entry index 2...
Also, I'm having a missing sprite sometimes but always the same, will try to reduce to something minimal

this will not display the sprite, even though it's logged:
use bevy::prelude::*;

fn main() {
    App::build()
        .add_plugins(DefaultPlugins)
        .add_startup_system(setup)
        .add_system(display)
        .run();
}

fn setup(commands: &mut Commands) {
    commands.spawn(Camera2dBundle::default());
}

fn display(
    commands: &mut Commands,
    mut first: Local<bool>,
    asset_server: Res<AssetServer>,
    mut materials: ResMut<Assets<ColorMaterial>>,
) {
    if !*first {
        let texture_handle = asset_server.load("branding/icon.png");
        info!(
            "displaying sprite: {:?}",
            commands
                .spawn(SpriteBundle {
                    material: materials.add(texture_handle.into()),
                    ..Default::default()
                })
                .current_entity()
        );
        *first = true;
    }
}

If I put display as a startup system, the sprite is displayed. If I removed the check on first, the sprite is displayed (but a new sprite is created on each frame, hard to know which one is displayed...)

this will crash with thread 'main' panicked at 'current render pipeline has a layout which is incompatible with a currently set bind group, first differing at entry index 1', /Users/francois/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.6.2/src/backend/direct.rs:1355:35 at the second time spawning text
use bevy::prelude::*;

fn main() {
    App::build()
        .add_plugins(DefaultPlugins)
        .add_startup_system(setup)
        .add_system(display)
        .run();
}

fn setup(commands: &mut Commands) {
    commands
        .spawn(UiCameraBundle::default())
        .with(Timer::from_seconds(1.0, true));
}

fn display(
    commands: &mut Commands,
    mut state: Local<bool>,
    time: Res<Time>,
    mut timers: Query<&mut Timer>,
    texts: Query<Entity, With<Text>>,
    asset_server: Res<AssetServer>,
) {
    for mut timer in timers.iter_mut() {
        timer.tick(time.delta_seconds());

        if timer.just_finished() {
            if *state {
                info!("removing all texts");
                for entity in texts.iter() {
                    commands.despawn_recursive(entity);
                }
            } else {
                info!("spawning texts");

                commands.spawn(TextBundle {
                    style: Style {
                        align_self: AlignSelf::FlexEnd,
                        ..Default::default()
                    },
                    text: Text {
                        value: "text".to_string(),
                        font: asset_server.load("fonts/FiraSans-Bold.ttf"),
                        style: TextStyle {
                            font_size: 60.0,
                            color: Color::WHITE,
                            ..Default::default()
                        },
                    },
                    ..Default::default()
                });
            }
            *state = !*state;
        }
    }
}

@mockersf That example makes sense based on when I'm seeing the panic. I think in my app it only happens when I switch between a state with UI components and one without or vice versa. But it doesn't happen every time the state changes, maybe 50% of the time which makes me think it might be a timing issue.

A big thanks to everyone for the testing / investigation. I'm diving in now.

this will not display the sprite, even though it's logged

@mockersf this was a result of us now caching NoMatch bind group lookup results (which prevented future changes to RenderResourceBindings from producing a match). Inserting new bindings now invalidates non-matching results.

I'm also seeing this panic, which I think is related to this branch as I've never noticed it before but I'm not sure what exactly I'm doing to trigger it. It appears intermittently.

@alec-deason I can trigger it consistently in the bevymark example by spawning in new entities via clicks (as opposed to spawning them all at startup like i did for my benchmarking)

I'm also seeing this panic, which I think is related to this branch as I've never noticed it before but I'm not sure what exactly I'm doing to trigger it. It appears intermittently.

@alec-deason dropping this commit resolves this issue, so its definitely scoped to that change set.

Lol past @cart was right about it needing a quality check.
@mockersf your text add/remove example is not fixed by reverting that commit, so it comes from somewhere else

@mockersf the add/remove example comes from the "remove stale bind groups" commit. interesting

@mockersf The add/remove example was broken because RenderResourceBindings isn't made aware when RenderResourceContext removes a "stale" bind group. Therefore even if the BindGroupStatus is "unchanged", we still need to try creating the bind group if it doesn't exist.
Performance-wise these are our options:

"broken" behavior: ~0.0162
revert the commit entirely: ~0.0180
the "fix": ~0.0173

We're leaving some performance on the table with the "fix", but its still an improvement over the previous behavior.

@mockersf  @alec-deason
Alrighty I think I've fixed all of the problems! Let me know if everything works on your end

Something is definitely wrong. It seems like bevy isn't getting the window size right, or maybe isn't handling window resizes correctly.
This is the button example running full screen:

My screenshot tool isn't capturing the cursor for some reason but in this image the cursor is in the middle of the screen, near the lower right hand corner of the gray box. That triggers the button's hover behavior and if you click there the button presses. I assume it's where the button should be.
Resizing the window doesn't seem to effect things the way it normally does, none of the UI resizes of adjusts its layout. I see similar results with other examples and with my application.

Also I just noticed that the button example is using large amounts of CPU across all my cores, even though it's not doing anything or even visible on the screen right now.

Never mind. Both problems happen on the current master so they aren't part of this branch.

Hmm the windowing issue is probably related to #947

And im planning on optimizing text rendering next, so hopefully that will resolve the button cpu usage issue

Hmm the windowing issue is probably related to #947

Yeah, that's the commit that caused the regression. I just wrote up an issue: #967

Ok, having discovered that #967 is an upstream issue I'm back to looking at this. All the issues I was having seem to be resolved. And everything is so much faster!

no more issues for me too 🎉

Score! Lets merge this.


How to increase font size in sc_violinClass and other SCN plots?

Hello SCN Team
Could you tell me how to increase font size in the SCN output images e.g. sc_violinClass as I need them for submitting to manuscripts. current plots have small fonts as the celltypes increase in training model
Thanks

-Biju

Hi Biju, you might have to go into the code to adjust the font size. While I am working on this improvement, which might take some time, here is what you can do.
Here is the source code for sc_violinClass. if you want to change the font size for cell type, just go down to where I indicated as change size here and change the number. afterward, source that function or simply run it on your R console. And you should be good to go.
`sc_violinClass<-function
(sampTab,
classRes,
sid = "cell_name",
dLevel="cluster",
addRand=0,
threshold=0.20,
ncol =1,
sub_cluster = NA){
rownames(sampTab) = sampTab[,sid]
sids <- rownames(sampTab)
colnames(sampTab)[which(colnames(sampTab) == dLevel)] = "cluster"
dLevel = "cluster"
classRes<-classRes[,sids]
stQ2<-cbind(sampTab[sids,], t(classRes[,sids]))
maxX <-apply(classRes, 1, max)
meaVar <-names(which(maxX>threshold))
test <- melt(stQ2, id.vars = c(sid, dLevel), measure.vars =  meaVar)
cnames <- colnames(test)
cnames[which(cnames=='value')] <- "classification_score"
cnames[which(cnames=='variable')] <- "cell_type"
colnames(test) <- cnames
xcol = length(unique(sampTab[,dLevel]))
getPalette <- colorRampPalette(brewer.pal(xcol, "Set2"))
if(!is.na(sub_cluster)){
test = test[test$cluster %in% sub_cluster,]
}
ggplot(test, aes(x = cluster, y = classification_score, fill = cluster)) + ylim(0,1) + geom_violin(scale='width', position='dodge', trim=FALSE) +
facet_wrap(~ cell_type, ncol=ncol) +
scale_y_continuous(
expand = c(0, 0),
name = "Class score",
breaks = c(0,  0.50,  1.0),
labels = c("0", "0.50", "1.0"),
limits = c(0,1)
) +
coord_cartesian(clip = "off") +
theme_dviz_hgrid() +
theme(
axis.line.x = element_blank(),
axis.ticks.x = element_blank(),
axis.title.y = element_text(size = 8),
axis.title.x = element_text(size = 8), #change size here
axis.text.x = element_text(size = 8, angle = 45, hjust=1),
axis.text.y = element_text(size = 8),
legend.title=element_text(size=10),
legend.text=element_text(size=10),
strip.text.x = element_text(size = 8)
) + geom_boxplot(width=0.1, outlier.size=.25) + scale_fill_manual(values = getPalette(xcol))
}`

Thanks


Fix typo

Category

[x] Content fix

What's in this Pull Request?
Fixed typo

thx @ganesh-sanap, appreciated.


Add support to Raspberry 4b/armhf

Is your feature request related to a problem? Please describe.
When I tried to install LocalSend-1.13.1-linux-arm-64.deb, OS said CPU arch is not armhf.
pi@rasp4b:~/Desktop $ sudo dpkg -i ./LocalSend-1.13.1-linux-arm-64.deb
dpkg: 处理归档 ./LocalSend-1.13.1-linux-arm-64.deb (--install)时出错：
软件包体系结构(arm64)与本机系统体系结构(armhf)不符
在处理时有错误发生：
./LocalSend-1.13.1-linux-arm-64.deb
OS info:
pi@rasp4b:~/Desktop $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
Describe the solution you'd like
Add support to Raspberry 4b/armhf. Many many thanks!
Describe alternatives you've considered
No response
Additional context
No response

Only ARMv8 (64bit) ist supported.
Please compile the app yourself if you want to use it on more niche architectures.