Running commit_version_bump in Jenkins directory fails, even though expected files changed

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I've been "manually" using fastlane for a few years now, it's a great tool, thanks to everyone involved!
I am now working on setting up Jenkins to run the scripts automatically.
When Jenkins runs fastlane it fails at the commit_version_bump step. This also happens if I cd to the Jenkins directory and run the command myself.
In my regular code directory it works as expected.
The really weird thing is that the changed files do look correct, the only thing is they are in a different order.
For manual running I have a lane beta for Jenkins I created the lane jenkins. Both lanes fail with the same error when I run them in the Jenkins directory.
Command executed

bundle exec /usr/local/bin/fastlane jenkins
Complete output when running fastlane, including the stack trace and command used

Last login: Fri Jul 30 14:09:46 on ttys001
me@Mac-mini ~ % cd ~/.jenkins/workspace/Emoji\ Countdown
me@Mac-mini Emoji Countdown % bundle exec /usr/local/bin/fastlane jenkins
[✔] 🚀
[14:30:41]: ------------------------------
[14:30:41]: --- Step: default_platform ---
[14:30:41]: ------------------------------
[14:30:41]: --------------------------
[14:30:41]: --- Step: xcode_select ---
[14:30:41]: --------------------------
[14:30:41]: Setting Xcode version to /Applications/Xcode.app for all build steps
[14:30:41]: Driving the lane 'ios jenkins' 🚀
[14:30:41]: --------------------------
[14:30:41]: --- Step: xcode_select ---
[14:30:41]: --------------------------
[14:30:41]: Setting Xcode version to /Applications/Xcode.app for all build steps
[14:30:41]: ---------------------------
[14:30:41]: --- Step: setup_jenkins ---
[14:30:41]: ---------------------------
[14:30:41]: Not executed by Continuous Integration system.
[14:30:41]: ------------------------------------
[14:30:41]: --- Step: increment_build_number ---
[14:30:41]: ------------------------------------
Current version of project Event Coutdown App is:
132
/Users/me/.jenkins/workspace/Emoji Countdown
[14:30:41]: $ cd /Users/me/.jenkins/workspace/Emoji\ Countdown && agvtool next-version -all && cd -
[14:30:42]: ▸ Setting version of project Event Coutdown App to:
[14:30:42]: ▸ 133.
[14:30:42]: ▸ Also setting CFBundleVersion key (assuming it exists)
[14:30:42]: ▸ Updating CFBundleVersion in Info.plist(s)...
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Countdown Widget/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../ECD Widget Preview/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Event Coutdown App/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Event Coutdown AppTests/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Event Coutdown AppUITests/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Watch Extension/Info.plist" to 133
[14:30:42]: ▸ Updated CFBundleVersion in "Event Coutdown App.xcodeproj/../Watch/Info.plist" to 133
[14:30:42]: ▸ Cannot find "Event Coutdown App.xcodeproj/../YES"
[14:30:42]: ▸ /Users/me/.jenkins/workspace/Emoji Countdown
[14:30:42]: -----------------------
[14:30:42]: --- Step: build_app ---
[14:30:42]: -----------------------
[14:30:43]: Resolving Swift Package Manager dependencies...
[14:30:43]: $ xcodebuild -resolvePackageDependencies -workspace Event\ Coutdown\ App.xcworkspace -scheme Event\ Coutdown\ App
[14:30:44]: ▸ Command line invocation:
[14:30:44]: ▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace "Event Coutdown App.xcworkspace" -scheme "Event Coutdown App"
[14:30:44]: ▸ User defaults from command line:
[14:30:44]: ▸     IDEPackageSupportUseBuiltinSCM = YES
[14:30:44]: ▸ Resolve Package Graph
[14:30:48]: ▸ Resolved source packages:
[14:30:48]: ▸   Beacon-iOS: https://github.com/helpscout/beacon-ios-sdk @ 2.2.3
[14:30:48]: ▸   SwizzleSwift: https://github.com/MarioIannotta/SwizzleSwift @ master
[14:30:48]: ▸   DeviceKit: https://github.com/devicekit/DeviceKit @ 4.4.0
[14:30:48]: ▸   Mixpanel: https://github.com/mixpanel/mixpanel-swift @ 2.10.2
[14:30:48]: ▸   Purchases: https://github.com/RevenueCat/purchases-ios @ 3.12.2
[14:30:48]: ▸ resolved source packages: Beacon-iOS, SwizzleSwift, DeviceKit, Mixpanel, Purchases
[14:30:48]: $ xcodebuild -showBuildSettings -workspace Event\ Coutdown\ App.xcworkspace -scheme Event\ Coutdown\ App
+--------------------------------------+---------------------------------------------------------------+
|                                       Summary for gym 2.190.0                                        |
+--------------------------------------+---------------------------------------------------------------+
| workspace                            | Event Coutdown App.xcworkspace                                |
| scheme                               | Event Coutdown App                                            |
| clean                                | false                                                         |
| output_directory                     | .                                                             |
| output_name                          | Countdown                                                     |
| silent                               | false                                                         |
| skip_package_ipa                     | false                                                         |
| skip_package_pkg                     | false                                                         |
| build_path                           | /Users/me/Library/Developer/Xcode/Archives/2021-08-03 |
| result_bundle                        | false                                                         |
| buildlog_path                        | ~/Library/Logs/gym                                            |
| destination                          | generic/platform=iOS                                          |
| skip_profile_detection               | false                                                         |
| skip_package_dependencies_resolution | false                                                         |
| disable_package_automatic_updates    | false                                                         |
| use_system_scm                       | false                                                         |
| xcode_path                           | /Applications/Xcode.app                                       |
+--------------------------------------+---------------------------------------------------------------+
[14:30:52]: $ set -o pipefail && xcodebuild -workspace Event\ Coutdown\ App.xcworkspace -scheme Event\ Coutdown\ App -destination 'generic/platform=iOS' -archivePath /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive archive | tee /Users/me/Library/Logs/gym/Countdown-Event\ Coutdown\ App.log | xcpretty
[14:30:57]: ▸ Compiling TakeoverNotificationViewController~iphoneportrait.xib
[14:31:00]: ▸ Compiling TakeoverNotificationViewController~iphonelandscape.xib
[14:31:01]: ▸ Compiling TakeoverNotificationViewController~ipad.xib
[14:31:01]: ▸ Compiling MiniNotificationViewController.xib
[14:31:07]: ▸ Compiling Device.generated.swift
[14:31:07]: ▸ Compiling Device.generated.swift
[14:31:07]: ▸ Processing Info.plist
[14:31:07]: ▸ Processing Info.plist
[14:31:07]: ▸ Processing empty-Mixpanel_Mixpanel.plist
[14:31:07]: ▸ Touching Mixpanel_Mixpanel.bundle (in target 'Mixpanel_Mixpanel' from project 'Mixpanel')
[14:31:36]: ▸ Linking DeviceKit.o
[14:31:36]: ▸ Linking DeviceKit.o
[14:31:36]: ▸ Compiling CountdownKit_vers.c
[14:31:36]: ▸ Linking CountdownKit
[14:31:36]: ▸ Compiling CountdownKitWatchOs_vers.c
[14:31:36]: ▸ Compiling CountdownKitWatchOs_vers.c
[14:31:36]: ▸ Linking CountdownKitWatchOs
[14:31:36]: ▸ Linking CountdownKitWatchOs
[14:31:36]: ▸ Generating 'CountdownKit.framework.dSYM'
[14:31:36]: ▸ Generating 'CountdownKitWatchOs.framework.dSYM'
[14:31:36]: ▸ Touching CountdownKit.framework (in target 'CountdownKit' from project 'CountdownKit')
[14:31:36]: ▸ Touching CountdownKitWatchOs.framework (in target 'CountdownKitWatchOs' from project 'CountdownKit')
[14:31:36]: ▸ Linking PurchasesCoreSwift.o
[14:31:36]: ▸ Linking PurchasesCoreSwift.o
[14:31:36]: ▸ Compiling RCSubscriberAttributesManager.m
[14:31:36]: ▸ Compiling RCSystemInfo.m
[14:31:36]: ▸ Compiling RCSubscriberAttribute.m
[14:31:36]: ▸ Compiling RCStoreKitWrapper.m
[14:31:36]: ▸ Compiling RCStoreKitRequestFetcher.m
[14:31:36]: ▸ Compiling RCReceiptFetcher.m
[14:31:36]: ▸ Compiling RCPurchasesErrorUtils.m
[14:31:36]: ▸ Compiling RCPurchases.m
[14:31:36]: ▸ Compiling RCPurchases+SubscriberAttributes.m
[14:31:36]: ▸ Compiling RCPurchaserInfoManager.m
[14:31:36]: ▸ Compiling RCPurchaserInfo.m
[14:31:36]: ▸ Compiling RCPromotionalOffer.m
[14:31:36]: ▸ Compiling RCProductInfoExtractor.m
[14:31:36]: ▸ Compiling RCProductInfo.m
[14:31:36]: ▸ Compiling RCPackage.m
[14:31:36]: ▸ Compiling RCOfferingsFactory.m
[14:31:36]: ▸ Compiling RCOfferings.m
[14:31:36]: ▸ Compiling RCOffering.m
[14:31:36]: ▸ Compiling RCLoggerBridge.m
[14:31:36]: ▸ Compiling RCIntroEligibility.m
[14:31:36]: ▸ Compiling RCInMemoryCachedObject.m
[14:31:36]: ▸ Compiling RCIdentityManager.m
[14:31:36]: ▸ Compiling RCISOPeriodFormatter.m
[14:31:36]: ▸ Compiling RCHTTPRequest.m
[14:31:36]: ▸ Compiling RCHTTPClient.m
[14:31:36]: ▸ Compiling RCEntitlementInfos.m
[14:31:36]: ▸ Compiling RCEntitlementInfo.m
[14:31:36]: ▸ Compiling RCDeviceCache.m
[14:31:36]: ▸ Compiling RCDateProvider.m
[14:31:36]: ▸ Compiling RCBackend.m
[14:31:36]: ▸ Compiling RCAttributionTypeFactory.m
[14:31:36]: ▸ Compiling RCAttributionFetcher.m
[14:31:36]: ▸ Compiling RCAttributionData.m
[14:31:36]: ▸ Compiling NSLocale+RCExtensions.m
[14:31:36]: ▸ Compiling NSError+RCExtensions.m
[14:31:36]: ▸ Compiling NSDictionary+RCExtensions.m
[14:31:36]: ▸ Compiling NSDate+RCExtensions.m
[14:31:36]: ▸ Compiling NSData+RCExtensions.m
[14:31:36]: ▸ Compiling RCSystemInfo.m
[14:31:36]: ▸ Compiling RCSubscriberAttributesManager.m
[14:31:36]: ▸ Compiling RCSubscriberAttribute.m
[14:31:36]: ▸ Compiling RCStoreKitWrapper.m
[14:31:36]: ▸ Compiling RCStoreKitRequestFetcher.m
[14:31:36]: ▸ Compiling RCReceiptFetcher.m
[14:31:37]: ▸ Linking Purchases.o
[14:31:37]: ▸ Compiling RCPurchasesErrorUtils.m
[14:31:37]: ▸ Compiling RCPurchases.m
[14:31:37]: ▸ Compiling RCPurchases+SubscriberAttributes.m
[14:31:37]: ▸ Compiling RCPurchaserInfoManager.m
[14:31:37]: ▸ Compiling RCPurchaserInfo.m
[14:31:37]: ▸ Compiling RCPromotionalOffer.m
[14:31:37]: ▸ Compiling RCProductInfoExtractor.m
[14:31:37]: ▸ Compiling RCProductInfo.m
[14:31:37]: ▸ Compiling RCPackage.m
[14:31:37]: ▸ Compiling RCOfferingsFactory.m
[14:31:38]: ▸ Compiling RCOfferings.m
[14:31:38]: ▸ Compiling RCOffering.m
[14:31:38]: ▸ Compiling RCLoggerBridge.m
[14:31:38]: ▸ Compiling RCIntroEligibility.m
[14:31:38]: ▸ Compiling RCInMemoryCachedObject.m
[14:31:38]: ▸ Compiling RCIdentityManager.m
[14:31:38]: ▸ Compiling RCISOPeriodFormatter.m
[14:31:38]: ▸ Compiling RCHTTPRequest.m
[14:31:38]: ▸ Compiling RCHTTPClient.m
[14:31:38]: ▸ Compiling RCEntitlementInfos.m
[14:31:38]: ▸ Compiling RCEntitlementInfo.m
[14:31:38]: ▸ Compiling RCDeviceCache.m
[14:31:38]: ▸ Compiling RCDateProvider.m
[14:31:38]: ▸ Compiling RCBackend.m
[14:31:41]: ▸ Compiling RCAttributionTypeFactory.m
[14:31:41]: ▸ Compiling RCAttributionData.m
[14:31:41]: ▸ Compiling RCAttributionFetcher.m
[14:31:41]: ▸ Compiling NSLocale+RCExtensions.m
[14:31:41]: ▸ Compiling NSError+RCExtensions.m
[14:31:41]: ▸ Compiling NSDictionary+RCExtensions.m
[14:31:41]: ▸ Compiling NSDate+RCExtensions.m
[14:31:41]: ▸ Compiling NSData+RCExtensions.m
[14:31:41]: ▸ Compiling Watch\ Extension_vers.c
[14:31:41]: ▸ Compiling Watch\ Extension_vers.c
[14:31:41]: ▸ Linking Watch
[14:31:41]: ▸ Linking Mixpanel.o
[14:31:41]: ▸ Linking Watch
[14:31:41]: ▸ Linking Mixpanel.o
[14:31:41]: ▸ Processing Info.plist
[14:31:41]: ▸     'CLKComplicationSupportedFamilies' has been deprecated starting in watchOS 7.0, use the ClockKit complications API instead. (in target 'Watch Extension' from project 'Event Coutdown App')
[14:31:41]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-watchos/CountdownKitWatchOs.framework
[14:31:41]: ▸ Generating 'Watch\ Extension.appex.dSYM'
[14:31:41]: ▸ Touching Watch\ Extension.appex (in target 'Watch Extension' from project 'Event Coutdown App')
[14:31:41]: ▸ Compiling Interface.storyboard
[14:31:41]: ▸ Processing Info.plist
[14:31:41]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-watchos/Watch\ Extension.appex
[14:31:41]: ▸ Touching Countdown.app (in target 'Watch' from project 'Event Coutdown App')
[14:31:41]: ▸ Linking Purchases.o
[14:31:41]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-iphoneos/Mixpanel_Mixpanel.bundle
[14:31:48]: ▸ Linking Countdown
[14:31:48]: ▸ ⚠  ld: linking against a dylib which is not safe for use in application extensions: /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event Coutdown App/BuildProductsPath/Release-iphoneos/CountdownKit.framework/CountdownKit
[14:31:52]: ▸ Processing Info.plist
[14:31:52]: ▸ Generating 'Countdown\ WidgetExtension.appex.dSYM'
[14:31:52]: ▸ Touching Countdown\ WidgetExtension.appex (in target 'Countdown WidgetExtension' from project 'Event Coutdown App')
[14:31:52]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-iphoneos/Mixpanel_Mixpanel.bundle
[14:32:04]: ▸ Compiling Countdown_vers.c
[14:32:04]: ▸ Linking Countdown
[14:32:08]: ▸ Processing Info.plist
[14:32:08]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-iphoneos/CountdownKit.framework
[14:32:08]: ▸ Generating 'Countdown.app.dSYM'
[14:32:09]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-watchos/Countdown.app
[14:32:09]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/Build/Intermediates.noindex/ArchiveIntermediates/Event\ Coutdown\ App/BuildProductsPath/Release-iphoneos/Countdown\ WidgetExtension.appex
[14:32:09]: ▸ Copying /Users/me/Library/Developer/Xcode/DerivedData/Event_Coutdown_App-anqxktqouuttmxbmskpkaodcfvqd/SourcePackages/checkouts/beacon-ios-sdk/Beacon.xcframework/ios-arm64/Beacon.framework
[14:32:11]: ▸ Touching Countdown.app (in target 'Event Coutdown App' from project 'Event Coutdown App')
[14:32:11]: ▸ Archive Succeeded
[14:32:11]: Generated plist file with the following values:
[14:32:11]: ▸ -----------------------------------------
[14:32:11]: ▸ {
[14:32:11]: ▸   "method": "app-store"
[14:32:11]: ▸ }
[14:32:11]: ▸ -----------------------------------------
[14:32:11]: $ /usr/bin/xcrun /Library/Ruby/Gems/2.6.0/gems/fastlane-2.190.0/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/ss/qnk6748n5f32_y2ytxfsrkyr0000gn/T/gym_config20210803-7374-18n2s1x.plist' -archivePath /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive -exportPath '/var/folders/ss/qnk6748n5f32_y2ytxfsrkyr0000gn/T/gym_output20210803-7374-cex5m'
[14:32:16]: Mapping dSYM(s) using generated BCSymbolMaps
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/07473188-EF69-3EB4-B621-8893FA847B61.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/Countdown.app.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/521C5EA7-96B3-34D5-AF6B-22AA97A37E64.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/Countdown\ WidgetExtension.appex.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/95EC622E-CB23-3D18-B08E-0E12DEC5DD2B.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/CountdownKit.framework.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/0B9F057D-0331-3A66-A327-D4BDB5A11895.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/CountdownKitWatchOs.framework.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/19DE11D0-7387-35F4-8437-75156F5EB12F.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/CountdownKitWatchOs.framework.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/Beacon.framework.dSYM
warning: /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown 2021-08-03 14.30.52.xcarchive/BCSymbolMaps/Beacon-arm64.bcsymbolmap: No such file or directory: not unobfuscating.
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/89BEE1EF-C93B-3995-8943-6A908F43EBC6.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/Watch\ Extension.appex.dSYM
[14:32:16]: $ dsymutil --symbol-map /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/BCSymbolMaps/2F540930-A9C7-3B6A-8793-8D9994857D89.bcsymbolmap /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown\ 2021-08-03\ 14.30.52.xcarchive/dSYMs/Watch\ Extension.appex.dSYM
14:32:17: Compressing 6 dSYM(s)
14:32:17: $ cd '/Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown 2021-08-03 14.30.52.xcarchive/dSYMs' && zip -r '/Users/me/.jenkins/workspace/Emoji Countdown/Countdown.app.dSYM.zip' *.dSYM
14:32:17: ▸ updating: Beacon.framework.dSYM/ (stored 0%)
14:32:17: ▸ updating: Beacon.framework.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: Beacon.framework.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: Beacon.framework.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: Beacon.framework.dSYM/Contents/Resources/DWARF/Beacon (deflated 71%)
14:32:17: ▸ updating: Beacon.framework.dSYM/Contents/Info.plist (deflated 52%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/ (stored 0%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/Contents/Resources/DWARF/Countdown WidgetExtension (deflated 72%)
14:32:17: ▸ updating: Countdown WidgetExtension.appex.dSYM/Contents/Info.plist (deflated 51%)
14:32:17: ▸ updating: Countdown.app.dSYM/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/DWARF/Countdown (deflated 75%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/Swift/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/Swift/aarch64/ (stored 0%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Resources/Swift/aarch64/Beacon.swiftinterface (deflated 82%)
14:32:17: ▸ updating: Countdown.app.dSYM/Contents/Info.plist (deflated 51%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/ (stored 0%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/Contents/Resources/DWARF/CountdownKit (deflated 63%)
14:32:17: ▸ updating: CountdownKit.framework.dSYM/Contents/Info.plist (deflated 52%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/ (stored 0%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/Contents/Resources/DWARF/CountdownKitWatchOs (deflated 63%)
14:32:17: ▸ updating: CountdownKitWatchOs.framework.dSYM/Contents/Info.plist (deflated 52%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/ (stored 0%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/Contents/ (stored 0%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/Contents/Resources/ (stored 0%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/Contents/Resources/DWARF/ (stored 0%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/Contents/Resources/DWARF/Watch Extension (deflated 62%)
14:32:17: ▸ updating: Watch Extension.appex.dSYM/Contents/Info.plist (deflated 51%)
14:32:17: Successfully exported and compressed dSYM file
14:32:17: Successfully exported and signed the ipa file:
14:32:17: /Users/me/.jenkins/workspace/Emoji Countdown/Countdown.ipa
14:32:17: ---------------------------------
14:32:17: --- Step: commit_version_bump ---
14:32:17: ---------------------------------
14:32:17: $ git rev-parse --show-toplevel
14:32:17: ▸ /Users/me/.jenkins/workspace/Emoji Countdown
14:32:17: $ git diff --name-only HEAD
14:32:17: ▸ Countdown Widget/Info.plist
14:32:17: ▸ ECD Widget Preview/Info.plist
14:32:17: ▸ Event Coutdown App.xcodeproj/project.pbxproj
14:32:17: ▸ Event Coutdown App/Info.plist
14:32:17: ▸ Event Coutdown AppTests/Info.plist
14:32:17: ▸ Event Coutdown AppUITests/Info.plist
14:32:17: ▸ Watch Extension/Info.plist
14:32:17: ▸ Watch/Info.plist
14:32:17: $ git ls-files --other --exclude-standard
[[[ SNIP ]]]
14:32:17: --- Step: notification ---
14:32:17: --------------------------
+--------------------+-------------------------------------------------------------------------------------+
|                                               Lane Context                                               |
+--------------------+-------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM   | ios                                                                                |
| PLATFORM_NAME      | ios                                                                                |
| LANE_NAME          | ios jenkins                                                                         |
| BUILD_NUMBER       | 133                                                                                |
| IPA_OUTPUT_PATH    | /Users/me/.jenkins/workspace/Emoji Countdown/Countdown.ipa                  |
| XCODEBUILD_ARCHIVE | /Users/me/Library/Developer/Xcode/Archives/2021-08-03/Countdown 2021-08-03  |
|                    | 14.30.52.xcarchive                                                                  |
| DSYM_OUTPUT_PATH   | /Users/me/.jenkins/workspace/Emoji Countdown/Countdown.app.dSYM.zip         |
+--------------------+-------------------------------------------------------------------------------------+
[14:32:18]: Found unexpected uncommitted changes in the working directory. Expected these files to have
changed:
Event Coutdown App.xcodeproj/project.pbxproj
Event Coutdown App/Info.plist
Watch/Info.plist
Watch Extension/Info.plist
Countdown Widget/Info.plist
Event Coutdown AppTests/Info.plist
Event Coutdown AppUITests/Info.plist
ECD Widget Preview/Info.plist.
But found these actual changes:
Countdown Widget/Info.plist
ECD Widget Preview/Info.plist
Event Coutdown App.xcodeproj/project.pbxproj
Event Coutdown App/Info.plist
Event Coutdown AppTests/Info.plist
Event Coutdown AppUITests/Info.plist
Watch Extension/Info.plist
Watch/Info.plist
[[[ snip ]]]
Make sure you have cleaned up the build artifacts and
are only left with the changed version files at this stage in your lane, and don't touch the
working directory while your lane is running. You can also use the :force option to bypass this
check, and always commit a version bump regardless of the state of the working directory.
+------+------------------------+-------------+
|              fastlane summary               |
+------+------------------------+-------------+
| Step | Action                 | Time (in s) |
+------+------------------------+-------------+
| 1    | default_platform       | 0           |
| 2    | xcode_select           | 0           |
| 3    | xcode_select           | 0           |
| 4    | setup_jenkins          | 0           |
| 5    | increment_build_number | 1           |
| 6    | build_app              | 95          |
| 💥   | commit_version_bump    | 0           |
| 8    | notification           | 0           |
+------+------------------------+-------------+
[14:32:18]: fastlane finished with errors
[!] Found unexpected uncommitted changes in the working directory. Expected these files to have
changed:
Event Coutdown App.xcodeproj/project.pbxproj
Event Coutdown App/Info.plist
Watch/Info.plist
Watch Extension/Info.plist
Countdown Widget/Info.plist
Event Coutdown AppTests/Info.plist
Event Coutdown AppUITests/Info.plist
ECD Widget Preview/Info.plist.
But found these actual changes:
Countdown Widget/Info.plist
ECD Widget Preview/Info.plist
Event Coutdown App.xcodeproj/project.pbxproj
Event Coutdown App/Info.plist
Event Coutdown AppTests/Info.plist
Event Coutdown AppUITests/Info.plist
Watch Extension/Info.plist
Watch/Info.plist
[[[ snip ]]]
Make sure you have cleaned up the build artifacts and
are only left with the changed version files at this stage in your lane, and don't touch the
working directory while your lane is running. You can also use the :force option to bypass this
check, and always commit a version bump regardless of the state of the working directory.
me@Mac-mini Emoji Countdown %

Environment

 ✅ fastlane environment ✅
Stack

Key
Value

OS
11.5.1

Ruby
2.6.3

Bundler?
true

Git
git version 2.30.1 (Apple Git-130)

Installation Source
/usr/local/bin/fastlane

Host
macOS 11.5.1 (20G80)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-13.0.0-Beta.4.app/Contents/Developer/

Xcode Version
13.0

Swift Version
5.5

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
ENV["FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT"] = "180"
ENV["FASTLANE_XCODE_LIST_TIMEOUT"] = "180"

default_platform(:ios)
xcode_select("/Applications/Xcode.app")

platform :ios do
  desc "Upload a new build to Apple"
  lane :beta do

    # git_pull
    clear_derived_data

    # run_tests(workspace: "Event Coutdown App.xcworkspace",
    #   scheme: "Event Coutdown App",
    #   derived_data_path: "scan_derived_data",
    # )

    build_number = increment_build_number

    # prompt_for_marketing_version

    build_app(workspace: "Event Coutdown App.xcworkspace", scheme: "Event Coutdown App")
    commit_version_bump(xcodeproj: "Event Coutdown App.xcodeproj")

    upload_to_testflight(skip_waiting_for_build_processing: true)
    add_git_tag(build_number: build_number)
    push_to_git_remote()
    notification(subtitle: "Countdown build uploaded to TestFlight", message: "Version uploaded" + build_number)
  end

  lane :jenkins do

    xcode_select("/Applications/Xcode.app")
    setup_jenkins

    # run_tests(workspace: "Event Coutdown App.xcworkspace",
    #   scheme: "Event Coutdown App",
    #   derived_data_path: "scan_derived_data",
    # )

    build_number = increment_build_number

    # prompt_for_marketing_version

    build_app(workspace: "Event Coutdown App.xcworkspace", scheme: "Event Coutdown App")
    commit_version_bump(xcodeproj: "Event Coutdown App.xcodeproj")

    upload_to_testflight(skip_waiting_for_build_processing: true)
    add_git_tag(build_number: build_number)
    # push_to_git_remote()
    notification(subtitle: "Countdown build uploaded to TestFlight", message: "Version uploaded" + build_number)
  end

  error do |ex|
    # reset_git_repo
    notification(subtitle: "Failed", message: "Bad times")
  end

  private_lane :prompt_for_marketing_version do |options|
    marketing_version = get_version_number(target: "Event Coutdown App")
    new_version = UI.input("What marketing version? <enter to keep it at #{marketing_version}>")
    unless new_version.strip == ""
      increment_version_number(version_number: new_version)
      UI.message("Version number set to #{new_version}")
      marketing_version = new_version
      add_git_tag(tag: new_version)
    end
  end

  desc "Update major version number, eg 2021.2, then push to Apple"
  lane :new_version do
    git_pull
    increment_version_number(
      bump_type: "major"
      )

    beta
  end

end

`./fastlane/Appfile`
app_identifier("com.lasmit.events.Event-Coutdown-App") # The bundle identifier of your app
apple_id("----") # Your Apple email address

itc_team_id("---") # App Store Connect Team ID
team_id("----") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.190.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

bundler
1.17.2

etc
1.0.1

forwardable
1.2.0

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.8.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.416.0

aws-sigv4
1.2.2

jmespath
1.4.0

aws-sdk-core
3.111.1

aws-sdk-kms
1.41.0

aws-sdk-s3
1.87.0

babosa
1.0.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

declarative-option
0.1.0

digest-crc
0.6.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.1

excon
0.78.1

faraday-net_http
1.0.1

multipart-post
2.0.0

ruby2_keywords
0.0.2

faraday
1.3.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.1

gh_inspector
1.1.3

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.14.0

googleauth
0.16.2

httpclient
2.8.3

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

rexml
3.2.4

webrick
1.4.2

google-apis-core
0.4.1

google-apis-androidpublisher_v3
0.9.0

google-apis-playcustomapp_v1
0.2.0

google-apis-iamcredentials_v1
0.1.0

google-apis-storage_v1
0.1.0

google-cloud-env
1.4.0

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

google-cloud-storage
1.31.0

json
2.5.1

mini_magick
4.11.0

naturally
2.2.0

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-08-03

after setting force: true it works. When I check the git history it doesn't seem to be changing any unexpected files:
% git log --name-status HEAD^..HEAD
commit 6865d1d792e057a3f82afd9bae6b3a9c1faae022 (HEAD)
Author: Lewis <--->
Date:   Tue Aug 3 15:00:58 2021 +0100

    Version Bump to 132

M       Countdown Widget/Info.plist
M       ECD Widget Preview/Info.plist
M       Event Coutdown App.xcodeproj/project.pbxproj
M       Event Coutdown App/Info.plist
M       Event Coutdown AppTests/Info.plist
M       Event Coutdown AppUITests/Info.plist
M       Watch Extension/Info.plist
M       Watch/Info.plist

It would be good to not have to rely on the force option tho if possible.

Hi @lewis-smith
First of all, I will recommend to commit_version_bump immediately after the version-bump step, currently, you are building the app first which created IPA and lots of temp files in build folders
Also, small tip, please just run
bundle exec fastlane jenkins      # you don't have to use "/usr/local/bin/fastlane"

In case, you still face issues after this suggestion, please let us know here
https://github.com/fastlane/fastlane/discussions/categories/q-a


multiprocessing: AssertionError: Something went wrong with the worker initialization

Description
I tried to use the Evaluator in from "gluonts.evaluation import Evaluator", but an assertion error occurred related to multiprocessing. When I re-downloaded the tutorial in the document (https://gluon-ts.mxnet.io/examples/basic_forecasting_tutorial/tutorial.html#Create-your-own-forecast-model), the same thing happened. The code worked several weeks ago with the same OS. Besides, I changed the multiprocessing version back to the previous version, the bug still existed.
To Reproduce
from gluonts.evaluation import Evaluator
evaluator = Evaluator(quantiles=[0.1, 0.5, 0.9])
agg_metrics, item_metrics = evaluator(iter(tss), iter(forecasts), num_series=len(dataset.test))```

Error message or code output
(Paste the complete error message, including stack trace, or the undesired output that the above snippet produces.)
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/pool.py", line 125, in worker
    result = (True, func(*args, **kwds))
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/pool.py", line 48, in mapstar
    return list(map(*args))
  File "/Users/caixiyan/Library/Python/3.8/lib/python/site-packages/gluonts/evaluation/_base.py", line 808, in _worker_fun
    assert isinstance(
AssertionError: Something went wrong with the worker initialization.

AssertionError                            Traceback (most recent call last)
<ipython-input-29-b25f87fe7d03> in <module>
      1 evaluator = Evaluator(quantiles=[0.1, 0.5, 0.9])
----> 2 agg_metrics, item_metrics = evaluator(iter(tss), iter(forecasts), num_series=len(dataset.test))

~/Library/Python/3.8/lib/python/site-packages/gluonts/evaluation/_base.py in __call__(self, ts_iterator, fcst_iterator, num_series)
    168                     initializer=_worker_init(self), processes=self.num_workers
    169                 )
--> 170                 rows = mp_pool.map(
    171                     func=_worker_fun,
    172                     iterable=iter(it),

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/pool.py in map(self, func, iterable, chunksize)
    362         in a list that is returned.
    363         '''
--> 364         return self._map_async(func, iterable, mapstar, chunksize).get()
    365
    366     def starmap(self, func, iterable, chunksize=None):

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/pool.py in get(self, timeout)
    766             return self._value
    767         else:
--> 768             raise self._value
    769
    770     def _set(self, i, obj):

AssertionError: Something went wrong with the worker initialization.

Environment

Operating system: MacOS 10.15.6
Python version: 3.8
GluonTS version: 0.5.1
MXNet version: 1.6.0
multiprocessing version: 0.70.10 (also used 0.70.9)
(Add as much information about your environment as possible, e.g. dependencies versions.)

@arianacai1997 could you try on python 3.7?

Thanks for the advice. It works!

let's leave this open then so that we can track python 3.8 support

@arianacai1997 Hey bro, What version of Python are you working on? I found the same BUG in Python3.7.4


Fix header formatting in intersections guide

This marks up what should be a header in intersections.md and also brings all the other section headers there to the same level. Even if I didn’t get the latter right (I’m sure “Impossible intersection types” shouldn’t a subsection of “Intersection type syntax”, but the analogous markup of unions.md seems to think otherwise), the former should be fixed.

seems good to me, thanks!


Memory leak detection with basic usage of NLOHMANN_JSON_SERIALIZE_ENUM

Description
The basic usage of NLOHMANN_JSON_SERIALIZE_ENUM seems to return an error with _CrtMemCheckpoint Microsoft tool.
Reproduction steps
A basic google test return "Memory leak of 108 byte(s) detected" with the code provided as example.
Expected vs. actual results
Expected no memory leaks vs 108 byte(s).
Minimal code example
// ================================
// example enum type declaration
enum TaskState {
    TS_STOPPED,
    TS_RUNNING,
    TS_COMPLETED,
    TS_INVALID = -1,
};

// map TaskState values to JSON as strings
NLOHMANN_JSON_SERIALIZE_ENUM(TaskState, {
    {TS_INVALID, nullptr},
    {TS_STOPPED, "stopped"},
    {TS_RUNNING, "running"},
    {TS_COMPLETED, "completed"},
    })

TEST(TestGensBoard, MemoryLeak)
{
    test_helpers::MemoryLeakDetector detector;

     // json string to enum
     json j3 = "running";
     assert(j3.get<TaskState>() == TS_RUNNING);
}

// ================================
MemoryLeakDetector::MemoryLeakDetector()
{
    _CrtMemCheckpoint(&_memState);
}

MemoryLeakDetector::~MemoryLeakDetector()
{
    _CrtMemState stateNow, stateDiff;
    _CrtMemCheckpoint(&stateNow);
    const auto diffResult = _CrtMemDifference(&stateDiff, &_memState, &stateNow);
    if (diffResult)
        reportFailure(stateDiff.lSizes[1]);
}

void MemoryLeakDetector::reportFailure(unsigned int unfreedBytes)
{
    FAIL() << "Memory leak of " << unfreedBytes << " byte(s) detected.";
}

Error messages
No response
Compiler and operating system
Microsoft Visual C++ 2019 (Win32), Window10
Library version
v3.11.2
Validation

[ ] The bug also occurs if the latest version from the develop branch is used.
[ ] I can successfully compile and run the unit tests.

I would recommend using void _CrtMemDumpAllObjectsSince(const _CrtMemState *state); to report more information about the leak.

0 bytes in 0 Free Blocks.
108 bytes in 6 Normal Blocks.
0 bytes in 0 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 0 bytes.
Total allocations: 144 bytes.
Dumping objects ->
{2239} normal block at 0x0154C258, 8 bytes long.
Data: <( T     > 28 E0 54 01 00 00 00 00
{2238} normal block at 0x0154E028, 28 bytes long.
Data:  58 C2 54 01 63 6F 6D 70 6C 65 74 65 64 00 CD CD
{2237} normal block at 0x0154C098, 8 bytes long.
Data: <  T     > C8 E5 54 01 00 00 00 00
{2236} normal block at 0x0154E5C8, 28 bytes long.
Data: <  T running     > 98 C0 54 01 72 75 6E 6E 69 6E 67 00 CD CD CD CD
{2235} normal block at 0x0154C060, 8 bytes long.
Data: <  T     > 00 E1 54 01 00 00 00 00
{2234} normal block at 0x0154E100, 28 bytes long.

That looks to me like it's from the testing infrastructure.  If you remove the json variable, do you get the same result?

Ah, it's probably from the static storage inside those functions that gets initialized on the first use:
static const std::pair<ENUM_TYPE, BasicJsonType> m[] = __VA_ARGS__;

Thank you.
I still have to see how to correct my unit test, especially for the user classes.


usually inaccurate output: License file: LICENSE.txt License: no license

As noted if licensee can find a license file but can't positively identify the license, it outputs "no license", which is usually inaccurate. "Unknown" or "Unrecognized" would be accurate. Example:
script/git-repo https://github.com/getify/You-Dont-Know-JS
License file: LICENSE.txt
License: no license

In some cases licensee does output "Unknown" and maybe "Not detected" (see https://github.com/benbalter/licensee/blob/3120af283634fd3bd3731f2abe4167c6eba216f0/bin/licensee#L20 ... I haven't followed when this code is executed), but obviously not in the above example.

This is fixed on master, at least for the command line-output.
script/git-repo https://github.com/getify/You-Dont-Know-JS
License file: LICENSE.txt
License: Not detected

Here's the closest licenses:
* CC-BY-SA-4.0 similarity: 57.12%
* GPL-2.0 similarity: 40.39%
* LPPL-1.3c similarity: 36.35%

it outputs "no license", which is usually inaccurate. "Unknown" or "Unrecognized" would be accurate.

To be clear, that was an artifact of a quick command-line diagnostic tool (now fixed with expanded output). Internally, Licensee has the concept of the "matched file" and the "matched license". If there's a matched file, that means it found a license file (it has a license or copyright notice). In that case, MatchedFile#match would return nil if it wasn't matched, or the License, if it was (the actual output is up to the platform implementing the interface (e.g., GitHub, command line)).


Feat/fsspec filecache

Available PR templates

Default
Version Release
Alternatively delete and start empty

closing in preference for #47


it cannot back.

When I add
[self performSelector:@selector(endAnimationHandle) withObject:nil afterDelay:4.0f];
in sunnyControlDidStartAnimation,
and I pull up in 3.9 second,  it stop and no back.

Please call endAnimation selector synchronously.


Feature Request: Backup Codes

A lot of other 2FA systems give the user a bunch of Backup Codes when activating, to use as an alternative login method in case the authenticator device is lost or unavailable.
I think this would be a great addition to the Two-Factor Authentication plugin, so a user in this situation may not have to wait for an Admin to come online to remove 2FA from their account for them.

Thanks @KarlBishop, this would be a great feature. Because of the upcoming native 2FA feature in Craft i'm a little hesitant to add this. It would involve a lot of work and we think this plugin is on it's way out.

@roelvanhintum oh cool, good to hear 2FA is becoming native 👍


There still small bug in Immerse mode

https://user-images.githubusercontent.com/25120376/172993724-84cfc94c-aecc-487d-9c71-43a8edddbd06.mp4
Describe the bug
In immerse mode, the navigation bar doesn't disappear along with reader sheet when it was tap, this occur when I swipe up to
to view my navigation buttons.
To Reproduce
Steps to reproduce the behavior:

Enable Immerse mode
Swipe up the navigation bar in order for the navigation button show up
See the Video

Expected behavior
The phone navigation should disappear along with the reader sheet when it was tap or should automatically disappear after 5  sec (just like in Tachiyomi)
Smartphone (please complete the following information):

OS: [Android 9]
Version [Stable 0.1.24]

already fixed this problem.


Davis and YouTube datasets are multi-targeted, right?

Davis and YouTube datasets are multi-target, right? Or is there a single target? Self. single_object is also important?

That flag is used for static image pretraining only.

That flag is used for static image pretraining only.

@hkchengrex You mean there is no single target in YouTube and davis2017 datasets?However, I saw the mask of single target in the ground Truth of YouTube and Davis2017 data set. Now the test accuracy rate is close to 0 after I change the code. I suspect that only the code of multiple targets has been changed, but the code of single target has not been changed.(No pre-training)

The single_object flag is set here: https://github.com/hkchengrex/STCN/blob/e03c1585fd852624204b5c4e8d8e828ddb2d406f/util/hyper_para.py#L59
So it should not enter the single object path if no pretraining is done.


doc: fix sipi docs link

@benjamingeer this is an old one. Tobias never reviewed it and I forgot about it. Only one line to review :-)


Handle seenEmittedFiles which was not being set when emit of a file was complete

It was issue only when errors are reported before emitting (which puts the files into pendingEmit that needs to check only in seenEmittedFiles and not seenAffectedFiles)
If emit happens before semantic diagnostics query this issue is not repro, because the affected files come into play and those are being set correctly.
Fixes #31398
Thanks to @ericanderson and @bjlaub for getting us the repro.
As part of this I also found out that when --declarationMap is on in project we were using .d.ts.map instead of .d.ts as signature which is not desirable (since the map can change without changing d.ts resulting in complete refresh even if it didn't affect .d.ts). I have fixed this in this PR along with ensuring that we have test case for that. Changed the createHash of SolutionBuilderHost for tests to emit signature-content so that its easily diagnosable.

@typescript-bot pack this

@sheetalkamat I ran this branch on our production codebase test case (from https://github.com/microsoft/TypeScript/pull/33061#issuecomment-524873855) and it seems to fix the issue! Thanks so much for getting this resolved!

@sheetalkamat Will this be in 3.6.1?

Will this be in 3.6.x?

yes

@typescript-bot cherry-pick this to release-3.6


Turn off quic?

Describe your question
I dont know if this is at all possible but we have a single customer blocking QUIC in their firewall and we cant use WebSockets without a lot of rework (auth issues).  Is it possible to fallback to using plain old TCP/UDP or whatever came before QUIC?  Assuming this would be a client configuration since I cant find any reference to QUIC in the AWS IoT Core docs.
Which project is your question related to?

Client or
ManagedClient

For the HTTP-stack within .NET you can disable QUIC via the environment variable DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP3SUPPORT by setting it to false.
But I wonder how is this related to MQTTnet as that doesn't support QUIC. See https://github.com/dotnet/MQTTnet/issues/1195
Or is there something going on that originates from .NET itself (as you mentioned Websockets).
Can you share what .NET version you are using?

I'll try that. We are using .net 6 currently.
Thanks!

We are using .net 6 currently.

That's interesting, because until .NET 7 QUIC was only used internally for HTTP/3. So I wonder where the (blocked) traffic comes from.
MQTT here is based on TCP, so no QUIC which is UDP based.

Are you sure that setting is not DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT  ?  Looking at this page: https://learn.microsoft.com/en-us/dotnet/core/runtime-config/networking
I tried setting HTTP3 and HTTP2 to 0 then running my app but I still see QUIC traffic in wireshark - which may be other apps I guess. Its the first time Ive had to use wireshark.  Also, Im not sure how to block quic on my setup (VM running under VirtualBox on PopOs) so I cant emulate whatever the client has done.

So your saying that MQTT doesnt use QUIC at all? Maybe theres some lookup thing happening as part of initialisation of the networking.  Im definitely seeing some QUIC packets when I start my app so maybe the MQTT thing  is a red herring.  I wish I could block QUIC here then it might be more obvious.

Are you sure that setting is not DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT ?

Yes, as HTTP/2 has nothing to do with QUIC.

MQTT doesnt use QUIC at all?

At least the implementation here. https://github.com/dotnet/MQTTnet/issues/1195 discusses using QUIC for MQTT.

seeing some QUIC packets when I start my app

Just as wild guess: .NET SDK and .NET CLI telemetry where you can opt-out.
How do you start the app?

Pretty wild yes :)  I have a compiled exe.  Normally debugging via Visual Studio but Ive started from powershell also.  Not using dotnet run.
I'll need to actually block QUIC locally to see whats going on but it's looking more and more like it's not related to MQTT.
Thanks for all the help.  I'll post an update if/when I figure it out.


update to laravel 8

update composer.json according to https://laravel.com/docs/8.x/upgrade
composer update
composer install

fixes #109


Is it possible to make Proxy Manager a suggest instead of a requirement?

Hi @mnapoli,
During an installation of PHP-DI using composer I noticed that 'ocramius/proxy-manager' is being installed, which brings the dependencies zendframework/zend-code, zendframework/zend-eventmanager, zendframework/zend-stdlib.
As far as I can see I do not need those dependencies because I am not using the proxy functionality; would it make sense to move the ocramius/proxy-manager to the require-dev or suggests so that it is not added by default?

Hey @mvriel, glad to know you are giving this package a try!
It's planned and implemented in (future) v5 (see #198). The pull request for v5 is in #200 if you are curious.

Looking good! I am curious: what timeframe are you thinking of with version 5 and is it stable enough to try out in a new project?

I wouldn't say it's stable, even though we are using it in Piwik. The idea is to test features with a real life use case and have the liberty to adjust. Once it's stable, v5 will be released. But I think there might be some changes coming (not 100% sure yet) so if I were you I wouldn't.
The main thing of v5 is support for modular systems (i.e. like Symfony bundles, where modules can extend the base config and override each others). If you don't need that, then v4 should definitely be good enough. And the upgrade path to v5 will be fairly easy and documented.
There is not really a timeframe, it could be in 1 month or up to 3-4 :)

The project on which I am working isn't in a hurry and what you describe does sound appealing; I might give it a try knowing that you will be changing things. That modular systems change, is that already done? I couldn't find docs in the PR so I want to know before I go searching in the sourcecode ;)

That's interesting! Maybe you'll have feedback to give also on those new features.
Regarding documentation, I think you can find everything in the separate issues. Those features are mainly about inheriting definitions and extending definitions (needed for a modular system), and they are mainly discussed in #214. It's quite a read, but I'm very interested in your feeling about it if you do read it. Most of it is not implemented yet.
A smaller issue about string definitions: #224 (implemented)
Also some "syntactic sugar" that I documented in a blog post: http://php-di.org/news/14-php-di-5-syntaxic-sugar.html That is all implemented in the branch except #208 (nested definitions).
The main BC break I'm considering for v5 is this: right now object definitions automatically extend each-other. For example in file A you define an object, and in file B you change one constructor parameter value. The main reason for this feature being the default is to allow simple integration between autowiring, annotations and file configs… E.g. if you have:
public function __construct(LoggerInterface $logger, $dbHost)

You can do only this in the config file:
return [
     'MyClass' => DI\object()
        ->constructorParameter('dbHost', 'localhost');
];

(no need to define again the $logger parameter)
That's cool, but it has some problems, and I'm considering making the default different:

by default, definitions override any previous definition (i.e. file definition would completely override the "autowiring" definition)
you can optionally choose to extend/decorate the previous definition (that requires to explicitly do it)

That behavior would then be consistent across all definition types. See this comment for the detailed arguments.
What do you feel about this change and the related BC break?

If you do start using v5, let me know I'll try to think about you if I push anything that might break. But except the BC break I just detailed, the rest should be pretty stable.
Also will you have very high performance expectations on your application? In most cases the container is just a fraction of the request so it's no problem but just so you know this branch is not benchmarked or optimized yet.

Ohh is that this? That readme sounds super interesting, if you need any help regarding PHP-DI ping me in your project I'll be glad to help! (or you can open an issue here too)

You are absolutely, right! I am trying out PHP-DI 5 in Somos as I believe that Somos will take quite some time for it to be ready enough for beta and that means that with any luck PHP-DI 5 will be launched by then :)
And don't worry about breaks because I am trying it out; I am aware I am using experimental / development releases. I have the same thing going with phly/http

Awesome good luck!

Just a FYI regarding https://github.com/somos/framework/issues/31 (didn't want to derail the topic so I'm posting here), PHP-DI offers a call() method that works a bit like AngularJS:
$parameters = [
    'data' => /* some variable */
];

$container->call(function (Logger $logger, $data) {
    // ...
}, $parameters);

Beyond allowing to inject dependencies at will, it's also a good way to invoke stuff without having to implement it again. In the issue you mention the ability to define business logic as a closure, or an invokable object, or also the class name as a string (which will be resolved using the container): PHP-DI can do that with call().
It gives an interesting solution: you can then use DI both in classes (traditional way with constructor parameters) but also in action callables. That means you can write actions as closures and still benefit from DI even though you don't have a constructor/state. And you can mix injecting services with injecting request parameters (matching is done first by type-hint to find a service, then by argument name).
I've used that in a (not-serious) micro-framework I built to show that feature: https://github.com/mnapoli/minimal-app#dependency-injection-in-controller-actions
Maybe it will give you ideas who knows!

That does sounds interesting! Thank you for sharing that as it will simplify the code that I am currently writing.
Does it also support this use-case?
class MyAction
{
    public function __construct(MyDependency $dependency)
    {
        ...
    }

    public function indexAction(Request $request)
    {
        ...
    }

    public function showAction(Request $request)
    {
        ...
    }
}

$di->call('MyAction::indexAction');

Also: do I understand correctly that in your example the data field in the array $parameters is injected into $data because the name matches?

MyAction::indexAction is actually the only PHP callable format that isn't supported ;) (see this comment). I wouldn't have a problem with adding support for that though, I just didn't bother at the time because using the array notation is much more PHP 5.5 friendly with ::class:
use Super\Long\Namespace\MyAction;

$container->call([MyAction::class, 'indexAction']);

The version that you wrote will try to invoke a static method indexAction instead of constructing an object first; or will PHP-DI create / retrieve an object if it doesn't find a static method?

If it's a static method, it will just call the static method.
If it's an object method, it will resolve the object using the container.
PS: I've updated my comment above with more info.

Awesome! You don't have to change any behaviour then; I will alter the text of https://github.com/somos/framework/issues/31 to match this

One last thing!

Also: do I understand correctly that in your example the data field in the array $parameters is injected into $data because the name matches?

Is this true?

Also: do I understand correctly that in your example the data field in the array $parameters is injected into $data because the name matches?

Yes exactly. It can match for 2 reasons:

the type-hint == a container entry name (which are usually class names when you use autowiring) -> this is dependency injection
the parameter name == the name of an item of the array -> this is just call_user_func_array behavior

I use it e.g. to do something like this:
$controller = function (LoggerInterface $logger, $name) {
    // $name is the same as $_GET['name']
}

$container->call($controller, $_GET + $_POST);

The only problem with that is that it's impossible to inject a container entry that is not indexed by the class name (because you can't type-hint it). I haven't found a clean way to do that yet, except introducing a new array:
$container->set('logger.log_file_name', '/tmp/app.log');

$controller = function ($logFile, $name) {
}

$containerEntriesMapping = [
    'logFile' => 'logger.log_file_name'
];

$container->call($controller, $_GET, $containerEntriesMapping);

2 arrays for similar yet different stuff, quite confusing… So I don't really know about that.

@mnapoli in an earlier comment (https://github.com/mnapoli/PHP-DI/issues/228#issuecomment-74369161) you talked about breaking BC because Object references now extend by default; I am totally ok with that break. In fact: I like it.
It feels intuitive for me to override entries if you redefine them and extending an object should be an explicit action. That just makes sense to me (perhaps because I am used to Pimple?)

:+1: I think all other containers behave that way (at least those that have a way to override/extend definitions).
Thanks for the feedback.


name of the overlay network

File: compose/compose-file/index.md, CC @gbarr01
It doesn't work while setting the name of an overlay network.No network named with such name in the network list (docker network ls) . The network is named prefixed with the stack name in that list.  docker compose version is set to 3.5 or 3.6，docker engine‘s version is 18.02.0.

It work while I update the docker engine to the version 18.04.0-ce.


Control signals appear not to be emitted

Operating system or device - Godot version:
Mageia 6 x86_64, master 2e73be9
Issue description:
Some signals of Control nodes seem not to be emitted as they should, namely (tested so far, might be more broken):

Control.gui_input
Control.mouse_entered
Control.mouse_exited

Steps to reproduce:
See attached demo.
Link to minimal example project:
test_signals.zip

Downloaded project, it seems problem is somewhere else, after changing Mouse->filter to stop or pass from ignore signals are emitted:

It seems the problem is that Control.filter is not converted correctly.

Isn't that related to #7622 ?

At least for Label it seems to be on purpose: https://github.com/godotengine/godot/blob/db3b05d/scene/gui/label.cpp#L681
So it would more be a documentation issue than a bug.

CC @godotengine/documentation, someone should document the mouse-related stuff in Control.xml to make this clearer.


Use @netlify/heuristics package for detection

- Summary
Uses a generalized version of Netlify CLI detectors introduced in @netlify/heuristics for project settings, functions builder settings and Git repo information. Depends on https://github.com/netlify/build/pull/678
- Test plan

Run netlify dev in a existing project

- Description for the changelog

Use @netlify/heuristics package for detection.
Patch the information returned from @netlify/heuristics package with Netlify CLI specific parameters.

- A picture of a cute animal (not mandatory but encouraged)
🐵

@RaeesBhatti, is this still relevant? Should we re-visit it in the future?

This should be closed


Panic downloading video

With https://github.com/iawia002/annie/commit/4315740814dd81144009eb0f9fc4209dd2041dec I got the following output downloading a YouTube playlist, behind an HTTP proxy :
panic: Get https://www.youtube.com/watch?v=lLOvB1qFE1E&gl=US&hl=en&has_verified=1&bpctr=9999999999: Bad Gateway

goroutine 1 [running]:
github.com/iawia002/annie/request.Request(0x70a4cf, 0x3, 0xc4204a0240, 0x57, 0x0, 0x0, 0x0, 0xc4204a0240)
	/home/lamg/go/src/github.com/iawia002/annie/request/request.go:88 +0xc7b
github.com/iawia002/annie/request.Get(0xc4204a0240, 0x57, 0x0, 0x0)
	/home/lamg/go/src/github.com/iawia002/annie/request/request.go:111 +0x7b
github.com/iawia002/annie/extractors.youtubeDownload(0xc4204a01e0, 0x53, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/home/lamg/go/src/github.com/iawia002/annie/extractors/youtube.go:71 +0x16b
github.com/iawia002/annie/extractors.Youtube(0x7ffcacfc62d0, 0x44)
	/home/lamg/go/src/github.com/iawia002/annie/extractors/youtube.go:52 +0x21c
main.main()
	/home/lamg/go/src/github.com/iawia002/annie/main.go:60 +0x428

@lamg I tried this annie -i -p https://www.youtube.com/watch?v=4FE79y_JkCE&list=PLGxuz-nmYlQMO2wRhUhV_g6AN3vLN_4X7, but everything is normal here. Can you retry this to see it still wrong?

The following code (from request.go) causes this error, is wrong because input/output errors shouldn't be treated as exceptional:
res, err := client.Do(req)
	if err != nil {
		log.Print(url)
		panic(err)
}

You should return the error value.

You mean to ignore this error?
res, _ := client.Do(req)

But I don't understand why you got this Bad Gateway error

I mean it shouldn't be treated as something worth of a panic call. Checkout the pattern I use for handling errors in https://github.com/lamg/pmproxy/blob/master/cmd/pmproxy/main.go. Every error in internal procedures is returned, the command line interface handles them at the end, because showing messages to the user is its concern.
The Bad Gateway probably is a consequence of using a very busy HTTP proxy server with little bandwidth for serving its clients.

I mean a panic call isn't the better way of handling it. Checkout https://github.com/lamg/pmproxy/blob/master/cmd/pmproxy/main.go: internal procedures that fail with errors that should be shown to the user return them, and the correct place to handle them is in the command line interface's code. Bad Gateway is probably the consequence of using a very busy HTTP proxy with little bandwidth for serving its clients.

@lamg I used to use the log.Fatal, but then I think I should use panic(5413cd2). The output of log.Fatal is too short, too similar. I don't know which request was wrong.


[WIP] Enable HTTP/2 Support

Nevermind. We cannot have HTTP/2 until we decide to move away from Heroku https://devcenter.heroku.com/articles/http-routing#http-versions-supported
More reasons why Heroku is not ideal:
https://hexdocs.pm/phoenix/heroku.html#limitations


java: Update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

org.junit.platform:junit-platform-launcher (source)
dependencies
patch
1.11.1 -> 1.11.2

org.junit.jupiter:junit-jupiter-engine (source)
dependencies
patch
5.11.1 -> 5.11.2

org.junit.jupiter:junit-jupiter-api (source)
dependencies
patch
5.11.1 -> 5.11.2

de.gdata:vaas
dependencies
patch
8.3.2 -> 8.3.3

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

no need for release because these are just dev-/test-dependencies.


Improve 3.x compatibility with 2.x (or vice versa)

Description
Not sure we can do everything we want and have a perfect world, but we can make things a bit better.
There is a summary and diff here that you can read to learn more about the changes that we have: https://github.com/mono/SkiaSharp/blob/main/changelogs/SkiaSharp/3.0.0/SkiaSharp.humanreadable.md
Using this list and some community libraries, we have found ways to improve compatibility without much additional effort for you or the maintenance in general.
Implementation
This work is 2 parts:

Add "hidden" APIs in 3.x that allow for upgrades where API usage is small or restricted to common things. Typically, the APIs that are used in most apps all have overloads, alternatives or other mechanisms that are better.

https://github.com/mono/SkiaSharp/pull/2789

Add new APIs in 2.x so that people can use the new APIs today, and then they can upgrade to 3.x without any changes as they are using it already.

https://github.com/mono/SkiaSharp/pull/2810

Changes
Here is a list of PRs that may or may not make it in but cover this area:

https://github.com/mono/SkiaSharp/pull/2810
https://github.com/mono/SkiaSharp/pull/2756
https://github.com/mono/SkiaSharp/pull/2789
https://github.com/mono/SkiaSharp/pull/2775

Tools
I have also been working to make a tool that can be used to detect any cases where a breaking will occur, without having to update and hope everything is fine. In some cases, different overloads will resolve, hiding a potential break.
Tool: https://www.nuget.org/packages/api-tools
Docs: https://github.com/mattleibow/Mono.ApiTools.NuGetDiff/blob/main/docs/api-tools.md#compat-command
dotnet api-tools compat Svg.Skia/Svg.Skia.dll SkiaSharp/v3/SkiaSharp.dll

<?xml version="1.0" encoding="utf-8"?>
<assemblies>
  <assembly>
    <types>
      <type fullname="SkiaSharp.SKImageFilter/CropRect" />
      <type fullname="SkiaSharp.SKCropRectFlags" />
    </types>
    <members>
      <member fullname="System.Void SkiaSharp.SKImageFilter/CropRect::.ctor(SkiaSharp.SKRect,SkiaSharp.SKCropRectFlags)" />
      <member fullname="SkiaSharp.SKImageFilter SkiaSharp.SKImageFilter::CreateMerge(SkiaSharp.SKImageFilter[],SkiaSharp.SKImageFilter/CropRect)" />
      <member fullname="SkiaSharp.SKImageFilter SkiaSharp.SKImageFilter::CreatePaint(SkiaSharp.SKPaint,SkiaSharp.SKImageFilter/CropRect)" />
      <!-- several other items -->
      <member fullname="System.Void SkiaSharp.SKPath::Transform(SkiaSharp.SKMatrix)" />
      <member fullname="System.Void SkiaSharp.SKCanvas::SetMatrix(SkiaSharp.SKMatrix)" />
    </members>
  </assembly>
</assemblies>

For this result, we have done some things:

We added overloads to the SKImageFilter type that allow for creating of filters without SKImageFilter.CropRect and instead use SKRect.
We added a hidden API SKCanvas.SetMatrix that matches 2.x, but we cannot add it to the public API as it is ambiguous to VB and not what we want to use going forward.

Fantastic effort on easing migration and adoption of v3!


Allow range to have min/max int for value in float

It would be great to have this possible:
    #[garde(range(min = 0, max = 100))]
    pub value: f64,

now it gives error:
expected `f64`, found integer
help: use a float literal: `0.0`

You have to use a float literal like that error message is telling you, just like with regular rust syntax (0.0..100.0)

In general, I don't want to special case any rule in this library based on the provided typename. In this case it'd require something like:
if field_type.to_string() == "f64" {
  quote!(range(#min as f64, #max as f64))
} else {
  quote!(range(#min, #max))
}

That's very brittle, because there's no guarantee that the field is actually the primitive.

it would be very helpful for validation openapi with minimum and maximum


Testing setting registry key fails due to value comparison

I'm trying to test setting a registry key value in ChefSpec but I'm getting a weird failure.
My chef code to set the registry values is:
registry_key 'HKLM\\SYSTEM\\CurrentControlSet\\Services\\Dnscache\\Parameters' do
  values [
    {
      name: 'NegativeCacheTime',
      type: :dword,
      data: 0x0
    },
    {
      name: 'NetFailureCacheTime',
      type: :dword,
      data: 0x0
    },
    {
      name: 'NegativeSOACacheTime',
      type: :dword,
      data: 0x0
    }]
  action :create
end

And to test that I have the following spec code:
it 'disables the DNS caching of negative responses' do
    expect(chef_run).to create_registry_key('HKLM\\SYSTEM\\CurrentControlSet\\Services\\Dnscache\\Parameters').with(
      values: [
        {
          name: 'NegativeCacheTime',
          type: :dword,
          data: 0x0
        },
        {
          name: 'NetFailureCacheTime',
          type: :dword,
          data: 0x0
        },
        {
          name: 'NegativeSOACacheTime',
          type: :dword,
          data: 0x0
        }])
  end

When running the test I get the following error:
ops_resource_core::consul_as_dns disables the DNS caching of negative responses
       Failure/Error: expect(chef_run).to create_registry_key('HKLM\\SYSTEM\\CurrentControlSet\\Services\\Dnscache\\Parameters').with(
         expected "registry_key[HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]" to have parameters:

           values [{:name=>"NegativeCacheTime", :type=>:dword, :data=>0}, {:name=>"NetFailureCacheTime", :type=>:dword, :data=>0}, {:name=>
  "NegativeSOACacheTime", :type=>:dword, :data=>0}], was [{:name=>"NegativeCacheTime", :type=>:dword, :data=>"cfcd208495d565ef66e7dff9f9876
  4da"}, {:name=>"NetFailureCacheTime", :type=>:dword, :data=>"cfcd208495d565ef66e7dff9f98764da"}, {:name=>"NegativeSOACacheTime", :type=>:
  dword, :data=>"cfcd208495d565ef66e7dff9f98764da"}]

It is clear why the values are not the same but what I don't understand is where does the cfcd208495d565ef66e7dff9f98764da value come from. I'm assuming it's some kind of hash / encrypted value of 0, but if that is the case how am I supposed to test that the correct values are being set?

That's the MD5 sum of "0". Chef must be converging this somehwere, since ChefSpec doesn't change any inputs.

Ok thanks. I guess I'll just put the MD5 sum in my spec then.

@pvandervelde I got the same error today, a quick look at the Chef resource for Registry Key showed up this
      def values(arg = nil)
        if not arg.nil?
			# Code for assignment ...
        elsif self.instance_variable_defined?(:@values)
          scrub_values(@values)
        end
      end

      def scrub_values(values)
		# For each value ...
          if needs_checksum?(scrubbed_value)
			# Apply checksum ...
		  end
        end
        # Returned scrubbed values
      end

      # Some data types may raise errors when sent as json. Returns true if this
      # value's data may need to be converted to a checksum.
      def needs_checksum?(value)
        unsafe_types = [:binary, :dword, :dword_big_endian, :qword]
        unsafe_types.include?(value[:type])
      end

No idea why the value needs to be converted to a checksum, @sethvargo ?
Using pry I could see that the resource has an unscrubbed_values method so for the purpose of testing I changed the expectation, therefore
it 'disables the DNS caching of negative responses' do
    expect(chef_run).to create_registry_key('HKLM\\SYSTEM\\CurrentControlSet\\Services\\Dnscache\\Parameters').with(
      unscrubbed_values: [
        {
          name: 'NegativeCacheTime',
          type: :dword,
          data: 0x0
        },
        {
          name: 'NetFailureCacheTime',
          type: :dword,
          data: 0x0
        },
        {
          name: 'NegativeSOACacheTime',
          type: :dword,
          data: 0x0
        }])
  end


scaling is off

I do not plan on implementing this as we don't have to make it responsive.
I will fix this if I have time this weekend


[Fix-12214] Fix oracle can't choose schema

Purpose of the pull request
fix bug #12214

Brief change log
oracle can only use the default database, we can't choose databases

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

I'll submit a new PR.


[Meta Schedule][M3c] Argument Info

This PR is part of the meta schedule project (#8473) that adds metadata of each PrimFunc's argument. This feature is necessary for dynamic shape auto-tuning.
@ZihengJiang @ArmageddonKnight @mbrookhart Would you guys help review this PR? Thanks a lot!

Running late to the party, but this looks good to me :D Thanks!

Thanks @mbrookhart :-)


networks: make ifname hint also valid qemu identifier

这个 PR 实现什么功能/修复什么问题:
networks: make ifname hint also valid qemu identifier

是否需要 backport 到之前的 release 分支:

release/2.10.0

/area region
/cc @wanyaoqi

Codecov Report

Merging #4412 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #4412      +/-   ##
=========================================
- Coverage    6.86%   6.86%   -0.01%
=========================================
  Files         521     521
  Lines       88277   88287      +10
=========================================
- Hits         6059    6057       -2
- Misses      81713   81724      +11
- Partials      505     506       +1

Flag
Coverage Δ

#aFlag
6.86% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/networks.go
0.55% <0%> (-0.01%)
:arrow_down:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

/lgtm
/approve


Usability: Enable search & sorting for select/dropdowns

Many of the select/dropdown boxes would benefit from enabling search and sorting functionality, e.g. Vendor and Filament dropdowns where it's easy to accumulate dozens or hundreds of entries.
Looks like the UI is using Ant Design components, this is the feature I was thinking of: https://ant.design/components/select#select-demo-search-sort

Search is very cool but pls also sort the entries ;)
ie  (localeCompare() with {sensitivity: 'base'})


[doc-bug][ttk-fixes]

Added links and minor content fix

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/create-new-project.md
92
3
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
85
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 390a3ea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Meriging similar modules

I didn't like the module structure of the core crate since it contained multiple modules with similar names and related contents (e.g. the port and ports module). Therefore, I streamlined the structure a bit. I hope you like it!

I agree having both port and ports as module names can be quite misleading.
The idea I had that port was the implementation of the notion of port (traits, etc.), while ports is all of the port types provided by the spec, so pretty much every spec would have a ports module (same for features).
Although in retrospect, I agree it is probably more confusing to have several similar-named modules than everything in a single one.


(ManagerV2): add accounts button

Manager V2

add accounts button added into installed apps section

Type
Feature
Context
Parts of the app affected / Test plan
Manager V2

@LFBarreto some conflict


Document TLE's derived values

There are four derived values for TLEs and Latest TLEs: period, SMA, apogee height, perigee height. They may not be calculated how the user expects, so they should be documented. The following formulas come from the SpaceTrack website:

period = 1440/n
Using mu, the standard gravitational parameter for the earth<PHONE_NUMBER>), semi-major axis "a" = (mu/(n2pi/(24*3600))^2)^(1/3)
Using semi-major axis "a", eccentricity "e", and the Earth's radius in km, apogee = (a * (1 + e))- 6378.135
Using semi-major axis "a", eccentricity "e", and the Earth's radius in km, perigee = (a * (1 - e))- 6378.135

Perhaps those TLE-related classes would include getters for apogee/perigee radius as well.

The getters for the radius values were added in version 1.1.0.


UI should list somewhere the openshift console and/or api urls

Once you run the wizards you don't have a way to actually browse to see the openshift console nor info on what api urls to use if using oc
Suggestion is to have the environment "tile" actually give a link to your spaces openshift console project(s)/environments - or at least a minimum the main console.
This would at least allow users to browse the details and find info to get cli access.
p.s. The environment page currently seems hardcoded to point to https://console.free-int.openshift.com/ instead of https://console.starter-us-east-2.openshift.com/console/ - which is just wrong for openshift.io.

from @pmuir on this from mailing list:
There will be links from the environments widget, and we will add the
applications page (like the environments page but better) after
Summit.
We're also adding the access tokens to the profile again, and it could
be good to have link to the openshift console there as well.

this PR adds a link to the openshift console on the Pipelines page

This has been fixed here https://github.com/fabric8io/fabric8-ui/pull/1062/files#diff-28519934ef78f3a7270b64304cb53b39R178


TUI characters not working

I'm trying to run gcalcli with viddy but the terminal characters are not rendering properly.
I'm running it with
viddy -n 300 --shell /bin/bash -t -- gcalcli calw --military --nostarted --nodeclined

and it looks like this

It should look like this

Is there a way to render the characters properly?

I restarted my terminal and tried again and this is working. Not sure what I broke before.


Assets 32349

JIRA: ASSETS-32349
Made changes to dynamically set the href of the adp-logo depending on whether the user is logged in and/or whether the user is navigating the /qa section of the site.
A bug that prevented quick-links in /qa from being selected was also resolved.

Test URLs:

Before: https://main--adobe-gmo--adobe.hlx.page/sample-public-site
After: https://assets-32349--adobe-gmo--adobe.hlx.page/sample-public-site

@cheintzman I am getting redirected to landing page, if I am logged-in and on faq page. Shouldn't user be redirected to /assets page from https://assets-32349--adobe-gmo--hlxsites.hlx.page/faq if user is logged-in?

@shiv-gup Yes, that would be the ultimate end goal, however due to the way public pages are handled, the method used here to determine whether a user is logged in cannot be used on public pages. It will require changing/adding code to security.js and security-imslibs.js in order to resolve the issue properly. These changes will get the logo working properly for majority of the site until that gets part resolved.

@cheintzman can you share the JIRA story where the changes were requested. I feel for now just making the logo image configurable should be good. From all pages if user clicks on logo the same page should be redirected (not dependent on user login status). Please check once with Debbie and Diana for requirement.

This is the initial story: DXI-23112
Diana had asked that the /assets page be considered the "home" page once the use is logged in, and the landing page be considered the home page for unauthenticated users. Debbie had mentioned I should make this change after the RCP since the security files needed some more people to be involved in order to resolve it properly.


[Bug]: Respect annotations as optional for ImageStreams

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When you create an image stream without any annotations, our backend code does not handle this.
Code in question: https://github.com/opendatahub-io/odh-dashboard/blob/main/backend/src/routes/api/images/imageUtils.ts#L95
Expected Behavior
Should be able to handle an image stream without annotations and take reasonable defaults that we already have in place.
Steps To Reproduce

Have image stream without any annotations
View the Jupyter tile spawner page (should also cause problems on the DS Projects workbench creation page)

Workaround (if any)
Add any annotation to get past the issue. Eg. opendatahub.io/test: 'test'
What browsers are you seeing the problem on?
No response
Open Data Hub Version
2.5.2

Anything else
No response

This will break the notebook controller spawner page but will not break the DSG workbench creation page because they are using different ways to process the image streams (backend API vs pass-through API)

Good to note Juntao, thanks!


AttributeError with out of range position at command line for --debug_references

This is a really uninteresting bug. An AttributeError exception is raised if I call fortls with out of range position arguments as in
fortls --debug_references --debug_filepath some.f90 --debug_line 123456 --debug_char 123456
With other debug options the out of range problem is caught.

I just noticed that the AttributeError also happens if the position is not on some proper object, e.g. on a empty space, or some '::' delimiter. So this might be more serious than initially assumed.
(For example invoking lsp-find-references in emacs with the cursor on some '::' triggers this error from the editor.)

Thanks for the report. I have just pushed a fix for this issue that will be included in the next patch.


camel-jbang - Auto detect vault dependencies

Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

@oscerd here is how we can auto detect the vault JARs with jbang

Thanks

PS: This should be combined with the export variant, as the export should also download, but return an null value so the task is not started.


dev experience when running on empty db

Hey, I saw your post on HN and was curious, and have a bunch of random feedback.
I followed the readme for getting things set up. However, I didn't have an sqlite db lying around, so i made an empty one.
Studio started on a different port than 3000, probably because I'm running a different dev server on 3000, so I got a cors error when running on this different port. Possibly set cors origins to allow * in dev?
Besides that running studio I got some semi-broken UI, probably because my db is empty, and errors in console. I fixed some of them locally but ended up getting too many retries (http) errors and ended up giving up 😭
Anyways.. mostly a feedback around "maybe you should try to get it working with an empty db file" ?
Anyways, the concept is nice, good luck and keep it up

Hi @arnorhs,
Thanks for checking out Soul and also sorry for the poor experience you had with Studio. As I mentioned in HN, studio is really at the beginning steps.
If you don't have any db and want to create a fresh one you can simply do soul -d newdb.db and Soul automatically generates one with the same name.
About the example you're totally right, I need to add it.
Thanks again.

@arnorhs ,
By the way for the cors issue you need to update your .env variables in core directory:
CORS_ORIGIN_WHITELIST=http://localhost:3456


"Run All" button skips cells randomly

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Steps taken

Create new notebook
Write x = 1 in cell 1, x in cell 2, y=2 in cell 3, y in cell 4, etc.
Click the "Run All" button, or hover on cell 1 and click "Execute Cell and Below"

Expected outcome
Cells get executed in order.
Observed outcome
Cell 2n raises a NameError of undefined variable because cell 2n-1 was not executed.
VS Code Version
Version: 1.92.1 Commit: eaa41d57266683296de7d118f574d0c2652e1fc4 Date: 2024-08-07T20:16:39.455Z Electron: 30.1.2 ElectronBuildId: 9870757 Chromium: 124.0.6367.243 Node.js: 20.14.0 V8: <IP_ADDRESS>-electron.0 OS: Darwin arm64 23.5.0
Jupyter Extension Version
v2024.7.0
Jupyter logs
14:36:21.029 [warn] Cell completed with errors Qd [Error]: name 'x' is not defined
    at n.execute (/home/~/.vscode-server/extensions/ms-toolsai.jupyter-2024.7.0-linux-x64/dist/extension.node.js:297:4958) {
  ename: 'NameError',
  evalue: "name 'x' is not defined",
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mNameError\x1B[0m                                 Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[1], line 1\x1B[0m\n\x1B[0;32m----> 1\x1B[0m \x1B[43mx\x1B[49m\n',
    "\x1B[0;31mNameError\x1B[0m: name 'x' is not defined"
  ]
}
14:36:21.029 [warn] Cancel all remaining cells due to cancellation or failure in execution

Coding Language and Runtime Version
Python v3.12.3
Language Extension Version (if applicable)
v2024.12.3
Anaconda Version (if applicable)
conda 23.11.0, micromamba 1.5.8
Running Jupyter locally or remotely?
Remote

that's strange - I can't think of why that would happen. Just to confirm, if you execute the cells one by one, do they run successfully?
Can you try creating a new profile and just installing the python and jupyter extensions and see if it still repro's.
if so, can you set "jupyter.logging.level": "trace", go through the steps again, and post the logs from that run.

that's strange - I can't think of why that would happen. Just to confirm, if you execute the cells one by one, do they run successfully?

Correct I can still shift+enter all the way down to the end without problems.

Can you try creating a new profile and just installing the python and jupyter extensions and see if it still repro's.

This was a good call! The issue did not reproduce in the new profile. When I switched back to the default profile it also seems to run all cells sequentially without problems, although I had to re-install the Python and Jupyter extensions for some reason.
I'm going to close the issue for now and add comments if the problem comes back. Thanks for the help!

I think what I am experiencing might be related to this, though to me it looks more like cells are executed in a random order, causing it to seem like some are skipped.
https://github.com/user-attachments/assets/9aaeb26d-2725-4ca9-b379-aeb6d0bb200a
With a log (though from a different execution) that confirms the strange order:
18:06:22.022 [debug] Handle Execution of Cells 0,1,2,3,4,5 for ~/Dropbox/University/ES9/jupyterbug.ipynb
18:06:22.120 [trace] Cell Index:2 sent to kernel
18:06:22.141 [trace] Start cell 2 execution @<PHONE_NUMBER>140 (clear output)
18:06:22.145 [debug] Kernel acknowledged execution of cell 2 @<PHONE_NUMBER>140
18:06:22.150 [trace] Cell 2 completed in 0.009s (start:<PHONE_NUMBER>140, end:<PHONE_NUMBER>149)
18:06:22.151 [trace] Cell 2 executed successfully
18:06:22.154 [trace] Cell Index:4 sent to kernel
18:06:22.163 [trace] Start cell 4 execution @<PHONE_NUMBER>163 (clear output)
18:06:22.165 [debug] Kernel acknowledged execution of cell 4 @<PHONE_NUMBER>163
18:06:22.168 [trace] Cell 4 completed in 0.005s (start:<PHONE_NUMBER>163, end:<PHONE_NUMBER>168)
18:06:22.170 [trace] Cell 4 executed successfully
18:06:22.173 [trace] Cell Index:3 sent to kernel
18:06:22.185 [trace] Start cell 3 execution @<PHONE_NUMBER>185 (clear output)
18:06:22.188 [debug] Kernel acknowledged execution of cell 3 @<PHONE_NUMBER>185
18:06:22.191 [trace] Cell 3 completed in 0.006s (start:<PHONE_NUMBER>185, end:<PHONE_NUMBER>191)
18:06:22.192 [trace] Cell 3 executed successfully
18:06:22.195 [trace] Cell Index:0 sent to kernel
18:06:22.206 [trace] Start cell 0 execution @<PHONE_NUMBER>205 (clear output)
18:06:22.208 [debug] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>205
18:06:22.216 [trace] Cell 0 completed in 0.011s (start:<PHONE_NUMBER>205, end:<PHONE_NUMBER>216)
18:06:22.218 [trace] Cell 0 executed successfully
18:06:22.222 [trace] Cell Index:5 sent to kernel
18:06:22.231 [trace] Start cell 5 execution @<PHONE_NUMBER>231 (clear output)
18:06:22.233 [debug] Kernel acknowledged execution of cell 5 @<PHONE_NUMBER>231
18:06:22.240 [trace] Cell 5 completed in 0.009s (start:<PHONE_NUMBER>231, end:<PHONE_NUMBER>240)
18:06:22.245 [trace] Cell 5 executed successfully
18:06:22.247 [trace] Cell Index:1 sent to kernel
18:06:22.260 [trace] Start cell 1 execution @<PHONE_NUMBER>260 (clear output)
18:06:22.261 [debug] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>260
18:06:22.268 [trace] Cell 1 completed in 0.007s (start:<PHONE_NUMBER>260, end:<PHONE_NUMBER>267)
18:06:22.270 [trace] Cell 1 executed successfully

I also ran into the issue a few times and it does seem to happen randomly. Sometimes it works fine after restarting the kernel.

@amunger Following up to see if additional information is needed. Thanks!

+1
I have the same issue for a few weeks. Happens only sometimes and usually causes NameError: name 'X' is not defined as the cell
that should define it runs before, so cells look as though they are skipped, but might be just random order of execution. Also Shift+Enter works good for me.

Yeah this is pretty much breaking issue for those of us that experience it. I would be happy to provide system/configuration information if needed.

This is a duplicate of https://github.com/microsoft/vscode-jupyter/issues/15746
Please install the latest pre-release version of the Jupyter extension (2024.8.***) or the latest release (should get released some time today/tomorrow).
If the problem still persists, please do ping here or feel free to create a new issue.