Match still working?

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I have problems to get Match running :-(
I created all needed certs etc with match appstore. After that I try to build the app with gym.
The log says me that All required keys, certificates and provisioning profiles are installed but it ends with Code signing is required for product type 'Application' in SDK 'iOS 10.3'
When I open the project in Xcode it shows me Team: unknown name. When I log in into my Apple account Xcode generates something and after that I can build the app with Fastlane.
So something is missing when I generate / use the certs and profiles with Fastlane / Match but I don't know what. And Xcode can fix it but at the end I want a solution without any Xcode user interaction (I want to run it on my CI server).
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

Captured Output
Command Used: jenkins
Output/Log

Successfully loaded Appfile at path '/Users/ralphbergmann/development/xcode/foo/fastlane/Appfile'
- app_identifier: 'kmb.foo'
- apple_id<EMAIL_ADDRESS>- team_id: 'G2xxxxxX5Y'
-------
DEBUG [2017-05-25 20:52:06.34]: Checking if there are any plugins that should be loaded...
INFO [2017-05-25 20:52:06.36]: -------------------------------------------------
INFO [2017-05-25 20:52:06.36]: --- Step: Verifying required fastlane version ---
INFO [2017-05-25 20:52:06.36]: -------------------------------------------------
INFO [2017-05-25 20:52:06.36]: Your fastlane version 2.35.0 matches the minimum requirement of 2.33.0  ✅
INFO [2017-05-25 20:52:06.37]: ------------------------------
INFO [2017-05-25 20:52:06.37]: --- Step: default_platform ---
INFO [2017-05-25 20:52:06.37]: ------------------------------
INFO [2017-05-25 20:52:06.37]: Driving the lane 'ios jenkins' 🚀
INFO [2017-05-25 20:52:06.37]: -------------------
INFO [2017-05-25 20:52:06.37]: --- Step: match ---
INFO [2017-05-25 20:52:06.37]: -------------------

+-----------------------+--------------------------------------+
|                   Summary for match 2.35.0                   |
+-----------------------+--------------------------------------+
| readonly              | true                                 |
| type                  | appstore                             |
| app_identifier        | kmb.foo                              |
| team_id               | G2xxxxxX5Y                           |
| git_url               |<EMAIL_ADDRESS>|
|                       | /ralphbergmann/fastlanematch.git     |
| keychain_password     | ********                             |
| git_branch            | master                               |
| username              |<EMAIL_ADDRESS>                        |
| keychain_name         | login.keychain                       |
| verbose               | false                                |
| force                 | false                                |
| skip_confirmation     | false                                |
| shallow_clone         | false                                |
| clone_branch_directly | false                                |
| force_for_new_devices | false                                |
| skip_docs             | false                                |
| platform              | ios                                  |
+-----------------------+--------------------------------------+

INFO [2017-05-25 20:52:06.42]: Cloning remote git repo...
INFO [2017-05-25 20:52:06.42]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
INFO [2017-05-25 20:52:06.43]: $ GIT_TERMINAL_PROMPT=0 git clone<EMAIL_ADDRESS>'/var/folders/8r/gc1pstvs6n19pths08qyrhqw0000gn/T/d20170525-88256-l5k2om'
INFO [2017-05-25 20:52:06.43]: ▸ Cloning into '/var/folders/8r/gc1pstvs6n19pths08qyrhqw0000gn/T/d20170525-88256-l5k2om'...
INFO [2017-05-25 20:52:08.55]: ▸ remote: Counting objects: 48, done.
INFO [2017-05-25 20:52:08.55]: ▸ remote: Compressing objects: 100% (41/41), done.
INFO [2017-05-25 20:52:08.69]: ▸ remote: Total 48 (delta 2), reused 0 (delta 0)
INFO [2017-05-25 20:52:08.70]: ▸ Unpacking objects: 100% (48/48), done.
INFO [2017-05-25 20:52:08.72]: 🔓  Decrypted 'U8VGBURABK.cer'
INFO [2017-05-25 20:52:08.73]: 🔓  Decrypted 'U8VGBURABK.p12'
INFO [2017-05-25 20:52:08.73]: 🔓  Decrypted 'AdHoc_kmb.foo.mobileprovision'
INFO [2017-05-25 20:52:08.74]: 🔓  Decrypted 'AppStore_kmb.foo.mobileprovision'
INFO [2017-05-25 20:52:08.74]: 🔓  Successfully decrypted certificates repo
INFO [2017-05-25 20:52:08.74]: Installing certificate...
INFO [2017-05-25 20:52:08.74]: $ security list-keychains -d user
INFO [2017-05-25 20:52:08.75]: ▸     "/Users/ralphbergmann/Library/Keychains/login.keychain-db"
INFO [2017-05-25 20:52:08.75]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /Users/ralphbergmann/Library/Keychains/login.keychain-db
INFO [2017-05-25 20:52:08.78]: ▸ keychain: "/Users/ralphbergmann/Library/Keychains/login.keychain-db"
INFO [2017-05-25 20:52:08.78]: ▸ version: 512
INFO [2017-05-25 20:52:08.78]: ▸ class: 0x80001000
INFO [2017-05-25 20:52:08.78]: ▸ attributes:
INFO [2017-05-25 20:52:08.78]: ▸     "alis"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-05-25 20:52:08.78]: ▸     "cenc"<uint32>=0x00000003
INFO [2017-05-25 20:52:08.78]: ▸     "ctyp"<uint32>=0x00000001
INFO [2017-05-25 20:52:08.78]: ▸     "hpky"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-05-25 20:52:08.78]: ▸     "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204341  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\024\006\003U\004\003\023\015APPLE ROOT CA"
INFO [2017-05-25 20:52:08.78]: ▸     "labl"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-05-25 20:52:08.78]: ▸     "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-05-25 20:52:08.78]: ▸     "snbr"<blob>=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2017-05-25 20:52:08.78]: ▸     "subj"<blob>=0x308196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697479  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\014;Apple Worldwide Developer Relations Certification Authority"
DEBUG [2017-05-25 20:52:08.87]: Certificate 'U8VGBURABK.cer' is already installed on this machine
INFO [2017-05-25 20:52:08.87]: $ security import /var/folders/8r/gc1pstvs6n19pths08qyrhqw0000gn/T/d20170525-88256-l5k2om/certs/distribution/U8VGBURABK.p12 -k '/Users/ralphbergmann/Library/Keychains/login.keychain-db' -P '' -T /usr/bin/codesign -T /usr/bin/security
INFO [2017-05-25 20:52:08.94]: $ security set-key-partition-list -S apple-tool:,apple: -k "xxxxxxxx" /Users/ralphbergmann/Library/Keychains/login.keychain-db

<removed lots of keychain noise>

INFO [2017-05-25 20:52:11.72]: $ openssl x509 -inform der -in /var/folders/8r/gc1pstvs6n19pths08qyrhqw0000gn/T/d20170525-88256-l5k2om/certs/distribution/U8VGBURABK.cer -subject -dates -noout &
INFO [2017-05-25 20:52:11.74]: ▸ subject= /UID=G2xxxxxX5Y/CN=iPhone Distribution: Karlmax Berlin GmbH & Co. KG (G2xxxxxX5Y)/OU=G2xxxxxX5Y/O=Karlmax Berlin GmbH & Co. KG/C=US
INFO [2017-05-25 20:52:11.74]: ▸ notBefore=May 25 18:11:41 2017 GMT
INFO [2017-05-25 20:52:11.74]: ▸ notAfter=May 25 18:11:41 2018 GMT

+-------------------+----------------------------------------------------------------+
|                               Installed Certificate                                |
+-------------------+----------------------------------------------------------------+
| User ID           | G2xxxxxX5Y                                                     |
| Common Name       | iPhone Distribution: Karlmax Berlin GmbH & Co. KG (G2xxxxxX5Y) |
| Organisation Unit | G2xxxxxX5Y                                                     |
| Organisation      | Karlmax Berlin GmbH & Co. KG                                   |
| Country           | US                                                             |
| Start Datetime    | May 25 18:11:41 2017 GMT                                       |
| End Datetime      | May 25 18:11:41 2018 GMT                                       |
+-------------------+----------------------------------------------------------------+

INFO [2017-05-25 20:52:11.74]: Installing provisioning profile...
WARN [2017-05-25 20:52:11.83]: Setting environment variable 'sigh_kmb.foo_appstore' to 'c1d9374e-xxxx-xxxx-xxxx-be81956faf9f'
WARN [2017-05-25 20:52:11.83]: Setting environment variable 'sigh_kmb.foo_appstore_team-id' to 'G2xxxxxX5Y'
WARN [2017-05-25 20:52:11.83]: Setting environment variable 'sigh_kmb.foo_appstore_profile-name' to 'match AppStore kmb.foo'
WARN [2017-05-25 20:52:11.83]: Setting environment variable 'sigh_kmb.foo_appstore_profile-path' to '/Users/ralphbergmann/Library/MobileDevice/Provisioning Profiles/c1d9374e-xxxx-xxxx-xxxx-be81956faf9f.mobileprovision'

+---------------------+------------------------+------------------------+
|                    Installed Provisioning Profile                     |
+---------------------+------------------------+------------------------+
| Parameter           | Environment Variable   | Value                  |
+---------------------+------------------------+------------------------+
| App Identifier      |                        | kmb.foo                |
| Type                |                        | appstore               |
| Platform            |                        | ios                    |
| Profile UUID        | sigh_kmb.foo_appstore  | c1d9374e-xxxx-xxxx-xx  |
|                     |                        | xx-be81956faf9f        |
| Profile Name        | sigh_kmb.foo_appstore  | match AppStore         |
|                     | _profile-name          | kmb.foo                |
| Profile Path        | sigh_kmb.foo_appstore  | /Users/ralphbergmann/  |
|                     | _profile-path          | Library/MobileDevice/  |
|                     |                        | Provisioning           |
|                     |                        | Profiles/c1d9674e-4cc  |
|                     |                        | a-4553-94a1-be84956ee  |
|                     |                        | f2c.mobileprovision    |
| Development Team ID | sigh_kmb.foo_appstore  | G2xxxxxX5Y             |
|                     | _team-id               |                        |
+---------------------+------------------------+------------------------+

INFO [2017-05-25 20:52:11.84]: All required keys, certificates and provisioning profiles are installed 🙌
INFO [2017-05-25 20:52:11.86]: Setting Provisioning Profile type to 'app-store'
INFO [2017-05-25 20:52:11.86]: -----------------------------------
INFO [2017-05-25 20:52:11.86]: --- Step: clean_build_artifacts ---
INFO [2017-05-25 20:52:11.86]: -----------------------------------
INFO [2017-05-25 20:52:11.86]: Cleaned up build artifacts 🐙
INFO [2017-05-25 20:52:11.87]: --------------------------------
INFO [2017-05-25 20:52:11.87]: --- Step: clear_derived_data ---
INFO [2017-05-25 20:52:11.87]: --------------------------------
INFO [2017-05-25 20:52:11.87]: Derived Data path located at: /Users/ralphbergmann/Library/Developer/Xcode/DerivedData
INFO [2017-05-25 20:52:11.98]: Successfully cleared Derived Data ♻
INFO [2017-05-25 20:52:11.98]: -----------------
INFO [2017-05-25 20:52:11.98]: --- Step: gym ---
INFO [2017-05-25 20:52:11.98]: -----------------
INFO [2017-05-25 20:52:12.16]: $ xcodebuild -list -workspace foo.xcworkspace -configuration Release
INFO [2017-05-25 20:52:12.81]: $ xcodebuild -showBuildSettings -workspace foo.xcworkspace -scheme foo -configuration Release

+----------------------+--------------------------------------+
|                   Summary for gym 2.35.0                    |
+----------------------+--------------------------------------+
| workspace            | foo.xcworkspace                      |
| scheme               | foo                                  |
| silent               | true                                 |
| clean                | true                                 |
| configuration        | Release                              |
| export_method        | app-store                            |
| destination          | generic/platform=iOS                 |
| output_name          | foo                                  |
| build_path           | /Users/ralphbergmann/Library/Develo  |
|                      | per/Xcode/Archives/2017-05-25        |
| output_directory     | .                                    |
| skip_package_ipa     | false                                |
| use_legacy_build_api | false                                |
| buildlog_path        | ~/Library/Logs/gym                   |
| xcode_path           | /Applications/Xcode.app              |
+----------------------+--------------------------------------+

+--------------------------------------+----------------------+
|                   Generated Build Command                   |
+--------------------------------------+----------------------+
| Option                               | Value                |
+--------------------------------------+----------------------+
| set -o pipefail &&                   |                      |
| xcodebuild                           |                      |
| -workspace foo.xcworkspace           |                      |
| -scheme foo                          |                      |
| -configuration Release               |                      |
| -destination                         | generic/platform=iOS |
| -archivePath                         |                      |
| /Users/ralphbergmann/Library/Develo  |                      |
| per/Xcode/Archives/2017-05-25/foo\   |                      |
| 2017-05-25\ 20.52.13.xcarchive       |                      |
| clean                                |                      |
| archive                              |                      |
| | tee                                |                      |
| /Users/ralphbergmann/Library/Logs/g  |                      |
| ym/foo-foo.log                       |                      |
| | xcpretty                           |                      |
+--------------------------------------+----------------------+
INFO [2017-05-25 20:52:13.87]: ▸ 2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/HighlightSelectedString.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2017-05-25 20:52:13.87]: ▸ 2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/GitDiff.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2017-05-25 20:52:13.87]: ▸ 2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/CleanHeaders.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2017-05-25 20:52:13.87]: ▸ 2017-05-25 20:52:13.876 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/ClangFormat.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2017-05-25 20:52:13.87]: ▸ 2017-05-25 20:52:13.876 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2017-05-25 20:52:14.43]: ▸ Cleaning Pods/ObjcExceptionBridging [Release]
INFO [2017-05-25 20:52:14.43]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.50]: ▸ 2017-05-25 20:52:14.506 xcodebuild[88310:6407667]  DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-12153/DVTFoundation/Utilities/DVTFileSystemUtilities.mm:142
INFO [2017-05-25 20:52:14.50]: ▸ Details:  lstat('/Users/ralphbergmann/Library/Developer/Xcode/DerivedData/foo-atvbsqlxapihxcdgffgaylsrlhjv/Build/Products/Release-iphoneos/ObjcExceptionBridging/ObjcExceptionBridging.framework') failed with errno 2 (No such file or directory)
INFO [2017-05-25 20:52:14.50]: ▸ Function: DVTRecursiveMkdirResult dvt_recursiveMkdir_returningErrorString(NSString *__strong, NSString *__autoreleasing *)
INFO [2017-05-25 20:52:14.50]: ▸ Thread:   <NSThread: 0x7fd0f6d32730>{number = 4, name = (null)}
INFO [2017-05-25 20:52:14.50]: ▸ Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
INFO [2017-05-25 20:52:14.51]: ▸ Cleaning Pods/SwiftState [Release]
INFO [2017-05-25 20:52:14.51]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.52]: ▸ Cleaning Pods/ReachabilitySwift [Release]
INFO [2017-05-25 20:52:14.52]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.52]: ▸ Cleaning Pods/RxSwift [Release]
INFO [2017-05-25 20:52:14.52]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.63]: ▸ Cleaning Pods/QRCodeReader.swift [Release]
INFO [2017-05-25 20:52:14.63]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.63]: ▸ Cleaning Pods/SideMenu [Release]
INFO [2017-05-25 20:52:14.63]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.63]: ▸ Cleaning Pods/XCGLogger [Release]
INFO [2017-05-25 20:52:14.63]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.63]: ▸ Cleaning Pods/RxCocoa [Release]
INFO [2017-05-25 20:52:14.63]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.64]: ▸ Cleaning Pods/RxReachability [Release]
INFO [2017-05-25 20:52:14.64]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.64]: ▸ Cleaning Pods/Pods-foo [Release]
INFO [2017-05-25 20:52:14.64]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.64]: ▸ Cleaning foo/foo [Release]
INFO [2017-05-25 20:52:14.64]: ▸ Check Dependencies
INFO [2017-05-25 20:52:14.67]: ▸ Clean Succeeded
INFO [2017-05-25 20:52:14.76]: ▸ Building Pods/ReachabilitySwift [Release]
INFO [2017-05-25 20:52:14.76]: ▸ Check Dependencies
INFO [2017-05-25 20:52:16.28]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:16.30]: ▸ Compiling Reachability.swift
INFO [2017-05-25 20:52:19.03]: ▸ Compiling Reachability.swift
INFO [2017-05-25 20:52:20.99]: ▸ Compiling ReachabilitySwift-dummy.m
INFO [2017-05-25 20:52:21.08]: ▸ Compiling ReachabilitySwift_vers.c
INFO [2017-05-25 20:52:21.12]: ▸ Compiling ReachabilitySwift-dummy.m
INFO [2017-05-25 20:52:21.17]: ▸ Compiling ReachabilitySwift_vers.c
INFO [2017-05-25 20:52:21.19]: ▸ Linking ReachabilitySwift
INFO [2017-05-25 20:52:21.45]: ▸ Linking ReachabilitySwift
INFO [2017-05-25 20:52:21.48]: ▸ Generating 'ReachabilitySwift.framework.dSYM'
INFO [2017-05-25 20:52:21.62]: ▸ Copying ReachabilitySwift-umbrella.h
INFO [2017-05-25 20:52:21.77]: ▸ Touching ReachabilitySwift.framework
INFO [2017-05-25 20:52:21.97]: ▸ Building Pods/SideMenu [Release]
INFO [2017-05-25 20:52:21.97]: ▸ Check Dependencies
INFO [2017-05-25 20:52:21.97]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:21.99]: ▸ Compiling SideMenu-dummy.m
INFO [2017-05-25 20:52:22.00]: ▸ Compiling SideMenu_vers.c
INFO [2017-05-25 20:52:22.00]: ▸ Compiling SideMenu-dummy.m
INFO [2017-05-25 20:52:22.00]: ▸ Compiling SideMenu_vers.c
INFO [2017-05-25 20:52:22.01]: ▸ Linking SideMenu
INFO [2017-05-25 20:52:22.24]: ▸ Linking SideMenu
INFO [2017-05-25 20:52:22.27]: ▸ Generating 'SideMenu.framework.dSYM'
INFO [2017-05-25 20:52:22.35]: ▸ Copying SideMenu-umbrella.h
INFO [2017-05-25 20:52:22.35]: ▸ Touching SideMenu.framework
INFO [2017-05-25 20:52:22.38]: ▸ Building Pods/SwiftState [Release]
INFO [2017-05-25 20:52:22.38]: ▸ Check Dependencies
INFO [2017-05-25 20:52:22.38]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:23.13]: ▸ Compiling SwiftState-dummy.m
INFO [2017-05-25 20:52:23.22]: ▸ Compiling SwiftState_vers.c
INFO [2017-05-25 20:52:23.22]: ▸ Compiling SwiftState-dummy.m
INFO [2017-05-25 20:52:23.22]: ▸ Compiling SwiftState_vers.c
INFO [2017-05-25 20:52:23.23]: ▸ Linking SwiftState
INFO [2017-05-25 20:52:23.61]: ▸ Linking SwiftState
INFO [2017-05-25 20:52:23.63]: ▸ Generating 'SwiftState.framework.dSYM'
INFO [2017-05-25 20:52:23.68]: ▸ Copying SwiftState-umbrella.h
INFO [2017-05-25 20:52:23.68]: ▸ Touching SwiftState.framework
INFO [2017-05-25 20:52:23.70]: ▸ Building Pods/ObjcExceptionBridging [Release]
INFO [2017-05-25 20:52:23.71]: ▸ Check Dependencies
INFO [2017-05-25 20:52:23.71]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:23.71]: ▸ Compiling ObjcExceptionBridging-dummy.m
INFO [2017-05-25 20:52:23.71]: ▸ Compiling ObjectiveCMarker.m
INFO [2017-05-25 20:52:23.71]: ▸ Compiling ObjcExceptionBridging-dummy.m
INFO [2017-05-25 20:52:23.72]: ▸ Compiling ObjcExceptionBridging_vers.c
INFO [2017-05-25 20:52:23.72]: ▸ Compiling ObjectiveCMarker.m
INFO [2017-05-25 20:52:23.72]: ▸ Compiling ObjcExceptionBridging_vers.c
INFO [2017-05-25 20:52:23.72]: ▸ Linking ObjcExceptionBridging
INFO [2017-05-25 20:52:23.72]: ▸ Linking ObjcExceptionBridging
INFO [2017-05-25 20:52:23.73]: ▸ Generating 'ObjcExceptionBridging.framework.dSYM'
INFO [2017-05-25 20:52:23.73]: ▸ Copying ObjcExceptionBridging-umbrella.h
INFO [2017-05-25 20:52:23.73]: ▸ Copying ObjcExceptionBridging.h
INFO [2017-05-25 20:52:23.73]: ▸ Touching ObjcExceptionBridging.framework
INFO [2017-05-25 20:52:23.73]: ▸ Building Pods/QRCodeReader.swift [Release]
INFO [2017-05-25 20:52:23.73]: ▸ Check Dependencies
INFO [2017-05-25 20:52:23.74]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:23.76]: ▸ Compiling QRCodeReader.swift-dummy.m
INFO [2017-05-25 20:52:23.76]: ▸ Compiling QRCodeReader_vers.c
INFO [2017-05-25 20:52:23.76]: ▸ Compiling QRCodeReader.swift-dummy.m
INFO [2017-05-25 20:52:23.76]: ▸ Compiling QRCodeReader_vers.c
INFO [2017-05-25 20:52:23.77]: ▸ Linking QRCodeReader
INFO [2017-05-25 20:52:23.77]: ▸ Linking QRCodeReader
INFO [2017-05-25 20:52:23.77]: ▸ Generating 'QRCodeReader.framework.dSYM'
INFO [2017-05-25 20:52:23.78]: ▸ Copying QRCodeReader.swift-umbrella.h
INFO [2017-05-25 20:52:23.78]: ▸ Touching QRCodeReader.framework
INFO [2017-05-25 20:52:23.78]: ▸ Building Pods/RxSwift [Release]
INFO [2017-05-25 20:52:23.78]: ▸ Check Dependencies
INFO [2017-05-25 20:52:23.78]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:39.90]: ▸ Compiling RxSwift-dummy.m
INFO [2017-05-25 20:52:39.96]: ▸ Compiling RxSwift_vers.c
INFO [2017-05-25 20:52:39.96]: ▸ Compiling RxSwift-dummy.m
INFO [2017-05-25 20:52:39.96]: ▸ Compiling RxSwift_vers.c
INFO [2017-05-25 20:52:39.97]: ▸ Linking RxSwift
INFO [2017-05-25 20:52:41.00]: ▸ Linking RxSwift
INFO [2017-05-25 20:52:41.08]: ▸ Generating 'RxSwift.framework.dSYM'
INFO [2017-05-25 20:52:41.30]: ▸ Copying RxSwift-umbrella.h
INFO [2017-05-25 20:52:41.30]: ▸ Touching RxSwift.framework
INFO [2017-05-25 20:52:41.32]: ▸ Building Pods/XCGLogger [Release]
INFO [2017-05-25 20:52:41.32]: ▸ Check Dependencies
INFO [2017-05-25 20:52:41.32]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:41.36]: ▸ Compiling XCGLogger-dummy.m
INFO [2017-05-25 20:52:41.36]: ▸ Compiling XCGLogger_vers.c
INFO [2017-05-25 20:52:41.36]: ▸ Compiling XCGLogger_vers.c
INFO [2017-05-25 20:52:41.36]: ▸ Compiling XCGLogger-dummy.m
INFO [2017-05-25 20:52:41.37]: ▸ Linking XCGLogger
INFO [2017-05-25 20:52:41.37]: ▸ Linking XCGLogger
INFO [2017-05-25 20:52:41.37]: ▸ Generating 'XCGLogger.framework.dSYM'
INFO [2017-05-25 20:52:41.37]: ▸ Copying XCGLogger-umbrella.h
INFO [2017-05-25 20:52:41.37]: ▸ Touching XCGLogger.framework
INFO [2017-05-25 20:52:41.38]: ▸ Building Pods/RxCocoa [Release]
INFO [2017-05-25 20:52:41.38]: ▸ Check Dependencies
INFO [2017-05-25 20:52:41.38]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:50.65]: ▸ Compiling _RX.m
INFO [2017-05-25 20:52:50.68]: ▸ Compiling _RXDelegateProxy.m
INFO [2017-05-25 20:52:50.76]: ▸ Compiling _RXKVOObserver.m
INFO [2017-05-25 20:52:50.76]: ▸ Compiling _RXObjCRuntime.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling RxCocoa-dummy.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling RxCocoa_vers.c
INFO [2017-05-25 20:52:51.85]: ▸ Compiling _RX.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling _RXDelegateProxy.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling _RXKVOObserver.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling _RXObjCRuntime.m
INFO [2017-05-25 20:52:51.85]: ▸ Compiling RxCocoa-dummy.m
INFO [2017-05-25 20:52:51.86]: ▸ Compiling RxCocoa_vers.c
INFO [2017-05-25 20:52:51.86]: ▸ Linking RxCocoa
INFO [2017-05-25 20:52:52.55]: ▸ Linking RxCocoa
INFO [2017-05-25 20:52:52.58]: ▸ Generating 'RxCocoa.framework.dSYM'
INFO [2017-05-25 20:52:52.79]: ▸ Copying _RX.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying _RXDelegateProxy.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying _RXKVOObserver.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying _RXObjCRuntime.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying RxCocoa-umbrella.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying RxCocoaRuntime.h
INFO [2017-05-25 20:52:52.79]: ▸ Copying RxCocoa.h
INFO [2017-05-25 20:52:52.79]: ▸ Touching RxCocoa.framework
INFO [2017-05-25 20:52:52.81]: ▸ Building Pods/RxReachability [Release]
INFO [2017-05-25 20:52:52.81]: ▸ Check Dependencies
INFO [2017-05-25 20:52:52.82]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:53.25]: ▸ Compiling RxReachability_vers.c
INFO [2017-05-25 20:52:53.28]: ▸ Compiling RxReachability-dummy.m
INFO [2017-05-25 20:52:53.31]: ▸ Compiling RxReachability-dummy.m
INFO [2017-05-25 20:52:53.31]: ▸ Compiling RxReachability_vers.c
INFO [2017-05-25 20:52:53.31]: ▸ Linking RxReachability
INFO [2017-05-25 20:52:53.43]: ▸ Linking RxReachability
INFO [2017-05-25 20:52:53.44]: ▸ Generating 'RxReachability.framework.dSYM'
INFO [2017-05-25 20:52:53.47]: ▸ Copying RxReachability-umbrella.h
INFO [2017-05-25 20:52:53.47]: ▸ Touching RxReachability.framework
INFO [2017-05-25 20:52:53.48]: ▸ Building Pods/Pods-foo [Release]
INFO [2017-05-25 20:52:53.48]: ▸ Check Dependencies
INFO [2017-05-25 20:52:53.49]: ▸ Processing Info.plist
INFO [2017-05-25 20:52:53.50]: ▸ Compiling Pods-foo-dummy.m
INFO [2017-05-25 20:52:54.13]: ▸ Compiling Pods_foo_vers.c
INFO [2017-05-25 20:52:54.13]: ▸ Compiling Pods-foo-dummy.m
INFO [2017-05-25 20:52:54.14]: ▸ Compiling Pods_foo_vers.c
INFO [2017-05-25 20:52:54.14]: ▸ Copying Pods-foo-umbrella.h
INFO [2017-05-25 20:52:54.16]: ▸ Touching Pods_foo.framework
INFO [2017-05-25 20:52:54.17]: ▸ Building foo/foo [Release]
INFO [2017-05-25 20:52:54.17]: ▸ Check Dependencies
INFO [2017-05-25 20:52:54.20]: ▸ ❌  Code signing is required for product type 'Application' in SDK 'iOS 10.3'
INFO [2017-05-25 20:52:54.21]: ▸ ** ARCHIVE FAILED **
INFO [2017-05-25 20:52:54.21]: ▸ The following build commands failed:
INFO [2017-05-25 20:52:54.21]: ▸ Check dependencies
INFO [2017-05-25 20:52:54.21]: ▸ (1 failure)
2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/HighlightSelectedString.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/GitDiff.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-05-25 20:52:13.875 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/CleanHeaders.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-05-25 20:52:13.876 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/ClangFormat.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-05-25 20:52:13.876 xcodebuild[88310:6407664] [MT] PluginLoading: Required plug-in compatibility UUID DFFB3951-EB0A-4C09-9DAC-5F2D28CC839C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
▸ Cleaning Pods/ObjcExceptionBridging [Release]
▸ Check Dependencies
2017-05-25 20:52:14.506 xcodebuild[88310:6407667]  DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-12153/DVTFoundation/Utilities/DVTFileSystemUtilities.mm:142
Details:  lstat('/Users/ralphbergmann/Library/Developer/Xcode/DerivedData/foo-atvbsqlxapihxcdgffgaylsrlhjv/Build/Products/Release-iphoneos/ObjcExceptionBridging/ObjcExceptionBridging.framework') failed with errno 2 (No such file or directory)
Function: DVTRecursiveMkdirResult dvt_recursiveMkdir_returningErrorString(NSString *__strong, NSString *__autoreleasing *)
Thread:   <NSThread: 0x7fd0f6d32730>{number = 4, name = (null)}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
▸ Cleaning Pods/SwiftState [Release]
▸ Check Dependencies
▸ Cleaning Pods/ReachabilitySwift [Release]
▸ Check Dependencies
▸ Cleaning Pods/RxSwift [Release]
▸ Check Dependencies
▸ Cleaning Pods/QRCodeReader.swift [Release]
▸ Check Dependencies
▸ Cleaning Pods/SideMenu [Release]
▸ Check Dependencies
▸ Cleaning Pods/XCGLogger [Release]
▸ Check Dependencies
▸ Cleaning Pods/RxCocoa [Release]
▸ Check Dependencies
▸ Cleaning Pods/RxReachability [Release]
▸ Check Dependencies
▸ Cleaning Pods/Pods-foo [Release]
▸ Check Dependencies
▸ Cleaning foo/foo [Release]
▸ Check Dependencies
▸ Clean Succeeded
▸ Building Pods/ReachabilitySwift [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling Reachability.swift
▸ Compiling Reachability.swift
▸ Compiling ReachabilitySwift-dummy.m
▸ Compiling ReachabilitySwift_vers.c
▸ Compiling ReachabilitySwift-dummy.m
▸ Compiling ReachabilitySwift_vers.c
▸ Linking ReachabilitySwift
▸ Linking ReachabilitySwift
▸ Generating 'ReachabilitySwift.framework.dSYM'
▸ Copying ReachabilitySwift-umbrella.h
▸ Touching ReachabilitySwift.framework
▸ Building Pods/SideMenu [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling SideMenu-dummy.m
▸ Compiling SideMenu_vers.c
▸ Compiling SideMenu-dummy.m
▸ Compiling SideMenu_vers.c
▸ Linking SideMenu
▸ Linking SideMenu
▸ Generating 'SideMenu.framework.dSYM'
▸ Copying SideMenu-umbrella.h
▸ Touching SideMenu.framework
▸ Building Pods/SwiftState [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling SwiftState-dummy.m
▸ Compiling SwiftState_vers.c
▸ Compiling SwiftState-dummy.m
▸ Compiling SwiftState_vers.c
▸ Linking SwiftState
▸ Linking SwiftState
▸ Generating 'SwiftState.framework.dSYM'
▸ Copying SwiftState-umbrella.h
▸ Touching SwiftState.framework
▸ Building Pods/ObjcExceptionBridging [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling ObjcExceptionBridging-dummy.m
▸ Compiling ObjectiveCMarker.m
▸ Compiling ObjcExceptionBridging-dummy.m
▸ Compiling ObjcExceptionBridging_vers.c
▸ Compiling ObjectiveCMarker.m
▸ Compiling ObjcExceptionBridging_vers.c
▸ Linking ObjcExceptionBridging
▸ Linking ObjcExceptionBridging
▸ Generating 'ObjcExceptionBridging.framework.dSYM'
▸ Copying ObjcExceptionBridging-umbrella.h
▸ Copying ObjcExceptionBridging.h
▸ Touching ObjcExceptionBridging.framework
▸ Building Pods/QRCodeReader.swift [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling QRCodeReader.swift-dummy.m
▸ Compiling QRCodeReader_vers.c
▸ Compiling QRCodeReader.swift-dummy.m
▸ Compiling QRCodeReader_vers.c
▸ Linking QRCodeReader
▸ Linking QRCodeReader
▸ Generating 'QRCodeReader.framework.dSYM'
▸ Copying QRCodeReader.swift-umbrella.h
▸ Touching QRCodeReader.framework
▸ Building Pods/RxSwift [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling RxSwift-dummy.m
▸ Compiling RxSwift_vers.c
▸ Compiling RxSwift-dummy.m
▸ Compiling RxSwift_vers.c
▸ Linking RxSwift
▸ Linking RxSwift
▸ Generating 'RxSwift.framework.dSYM'
▸ Copying RxSwift-umbrella.h
▸ Touching RxSwift.framework
▸ Building Pods/XCGLogger [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling XCGLogger-dummy.m
▸ Compiling XCGLogger_vers.c
▸ Compiling XCGLogger_vers.c
▸ Compiling XCGLogger-dummy.m
▸ Linking XCGLogger
▸ Linking XCGLogger
▸ Generating 'XCGLogger.framework.dSYM'
▸ Copying XCGLogger-umbrella.h
▸ Touching XCGLogger.framework
▸ Building Pods/RxCocoa [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling _RX.m
▸ Compiling _RXDelegateProxy.m
▸ Compiling _RXKVOObserver.m
▸ Compiling _RXObjCRuntime.m
▸ Compiling RxCocoa-dummy.m
▸ Compiling RxCocoa_vers.c
▸ Compiling _RX.m
▸ Compiling _RXDelegateProxy.m
▸ Compiling _RXKVOObserver.m
▸ Compiling _RXObjCRuntime.m
▸ Compiling RxCocoa-dummy.m
▸ Compiling RxCocoa_vers.c
▸ Linking RxCocoa
▸ Linking RxCocoa
▸ Generating 'RxCocoa.framework.dSYM'
▸ Copying _RX.h
▸ Copying _RXDelegateProxy.h
▸ Copying _RXKVOObserver.h
▸ Copying _RXObjCRuntime.h
▸ Copying RxCocoa-umbrella.h
▸ Copying RxCocoaRuntime.h
▸ Copying RxCocoa.h
▸ Touching RxCocoa.framework
▸ Building Pods/RxReachability [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling RxReachability_vers.c
▸ Compiling RxReachability-dummy.m
▸ Compiling RxReachability-dummy.m
▸ Compiling RxReachability_vers.c
▸ Linking RxReachability
▸ Linking RxReachability
▸ Generating 'RxReachability.framework.dSYM'
▸ Copying RxReachability-umbrella.h
▸ Touching RxReachability.framework
▸ Building Pods/Pods-foo [Release]
▸ Check Dependencies
▸ Processing Info.plist
▸ Compiling Pods-foo-dummy.m
▸ Compiling Pods_foo_vers.c
▸ Compiling Pods-foo-dummy.m
▸ Compiling Pods_foo_vers.c
▸ Copying Pods-foo-umbrella.h
▸ Touching Pods_foo.framework
▸ Building foo/foo [Release]
▸ Check Dependencies

❌  Code signing is required for product type 'Application' in SDK 'iOS 10.3'

** ARCHIVE FAILED **

The following build commands failed:
Check dependencies
(1 failure)
ERROR [2017-05-25 20:52:54.23]: Exit status: 65
WARN [2017-05-25 20:52:54.23]: 📋  For a more detailed error log, check the full log at:
WARN [2017-05-25 20:52:54.24]: 📋  /Users/ralphbergmann/Library/Logs/gym/foo-foo.log

+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.35.0                  |
| sdk         | iPhoneOS10.3.sdk        |
+-------------+-------------------------+

WARN [2017-05-25 20:52:54.25]: Lane Context:
INFO [2017-05-25 20:52:54.25]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios jenkins", :SIGH_PROFILE_TYPE=>"app-store"}
ERROR [2017-05-25 20:52:54.25]: Error building the application - see the log above
INFO [2017-05-25 20:52:54.26]: Successfully generated documentation at path '/Users/ralphbergmann/development/xcode/foo/fastlane/README.md'

+------+-----------------------+-------------+
|              fastlane summary              |
+------+-----------------------+-------------+
| Step | Action                | Time (in s) |
+------+-----------------------+-------------+
| 1    | Verifying required    | 0           |
|      | fastlane version      |             |
| 2    | default_platform      | 0           |
| 3    | match                 | 5           |
| 4    | clean_build_artifacts | 0           |
| 5    | clear_derived_data    | 0           |
| 💥   | gym                   | 42          |
+------+-----------------------+-------------+

ERROR [2017-05-25 20:52:54.27]: fastlane finished with errors

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

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

Host
Mac OS X 10.12.6 (16G8c)

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

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.3.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.33.0"

default_platform :ios

platform :ios do
  before_all do
    ENV["SLACK_URL"] ||= "https://hooks.slack.com/services/T0xxx0AU/B4Yxx40HZ/0VJljxxxxxJnKs7UApvn"
    ENV['MATCH_PASSWORD'] = "qxxxxxx6X7j"
  end

  def change_log_since_last_tag
    # http://git-scm.com/docs/pretty-formats
    # <short hash> <commit title>
    return changelog_from_git_commits(pretty: '%h %s')
  end

  desc "Generate / update certs via Match"
  lane :certs do

    # Easily sync your certificates and profiles across your team using git
    # More details https://github.com/fastlane/fastlane/tree/master/match
      match(type: "appstore",
            app_identifier: "kmb.foo",
            team_id: "G2xxxxxX5Y",
            git_url<EMAIL_ADDRESS>            keychain_password: "xxxxxxxx"
            )

  end

  desc "Upload a developer build to Hockey."
  lane :jenkins do

    # Ensure that your git status is not dirty
#    ensure_git_status_clean

    # Easily sync your certificates and profiles across your team using git
    # More details https://github.com/fastlane/fastlane/tree/master/match
    match(readonly: true,
          type: "appstore",
          app_identifier: "kmb.foo",
          team_id: "G2xxxxxX5Y",
          git_url<EMAIL_ADDRESS>          keychain_password: "xxxxxxxx"
          )

    # Deletes files created as result of running gym, cert, sigh or download_dsyms
    clean_build_artifacts

    # Deletes the Xcode Derived Data
    clear_derived_data

    # Increment the build number (not the version number)
#    increment_build_number

    # Easily build and sign your app using gym
    gym(
      workspace: "foo.xcworkspace",
      scheme: "foo",
      silent: true,
      clean: true,
      configuration: "Release",
      # both of these flags are required for ad hoc
      # export_method: 'ad-hoc'
    )

    # Collect git commit messages into a changelog
    change_log = change_log_since_last_tag

#    hockey(
#      api_token: "8cea6xxxxxxxxxxxxxxe44dac7dc00c4",
#      public_identifier: "964dbxxxxxxxxxxxxx9f1da1b502c2f6",
#      notes: change_log,
#      mandatory: '1',
#      teams: "10023",
#      notify: '2', # Notify all testers
#      status: '2', # Make available for download
#      release_type: '0' # 'beta' release type
#    )
#
#    # Commit the version bump
#    commit_version_bump
#
#    # This will add an annotated git tag to the current branch
#    add_git_tag(
#      grouping: "fastlane-builds",
#      prefix: "v"
#    )
#
#    # Push the new commit and tag back to your git remote
#    push_to_git_remote

  end

  error do |lane, exception|
  	if ENV["SLACK_URL"]
#      slack(
#        message: exception.message,
#        success: false
#      )
    end
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "kmb.foo" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "G2xxxxxX5Y"  # Developer Portal Team ID

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.35.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

activesupport
<IP_ADDRESS>

addressable
2.5.1

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.14.3

claide
1.0.1

cocoapods
1.2.0

cocoapods-core
1.2.0

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

cocoapods-trunk
1.1.2

cocoapods-try
1.1.0

colored
1.2

colored2
3.1.2

commander
4.4.3

commander-fastlane
4.4.4

domain_name
0.5.20161129

dotenv
2.2.0

escape
0.0.4

excon
0.55.0

faraday
0.11.0

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.1.0

fastlane-plugin-update_project_codesigning
0.1.9

fourflusher
2.0.1

fuzzy_match
2.0.4

gh_inspector
1.0.3

google-api-client
0.9.26

googleauth
0.5.1

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

i18n
0.8.1

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
2.9.0

little-plugger
1.1.4

logging
2.1.0

memoist
0.15.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.10.1

molinillo
0.5.6

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.3

nap
1.1.0

netrc
0.7.8

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.5

rake
10.4.2

rdoc
4.2.0

representable
2.3.0

retriable
2.1.0

rouge
1.11.1

ruby-macho
0.2.6

rubygems-update
2.5.2

rubyzip
1.2.1

security
0.1.3

signet
0.7.3

slack-notifier
1.5.1

sqlite3
1.3.13

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

thread_safe
0.3.6

tty-screen
0.5.0

tzinfo
1.2.3

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.3

word_wrap
1.0.0

xcodeproj
1.4.4

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

generated on: 2017-05-25

Note: The Xcode project is setup to automatically manage signing maybe this is wrong?

Have you followed the code signing linked by the bot?

Okay with the help of one of my colleagues I got it :-)
you can close this ticket

@the4thfloor can you provide the working solution?

I quess it is not a general solution :-(

we have deleted all certs and profiles in Apples developer portal
deleted all certs in the keychain
created new ones with Match
finally added the environment variables instead of hard coded profile names, see Make Sure Everyone Will Use the Same Provisioning Profile


Inconsistent math binding when not using spaces between number and non-letter

Description
The following syntax is valid
$1/2pi$

It renders the same as
$1/2 pi$

It should render the same as
$1/(2pi)$

It doesn't have to be pi. It can be any symbol or letter.
Either 1/2pi should be a syntax error or it should be formatted as the meaning it conveys semantically: 2 and pi without separation.
This can be summarized with the following table
#let helloWorld = $"hello_world"$
#table(columns: 3)[typed][render][should][
  `1/2pi`][$1/2pi$][$1/(2pi)$][
  `1/2 pi`][$1/2 pi$][$1/2 pi$][
  `1/(2 pi)`][$1/(2 pi)$][$1/(2pi)$][
  `1/(2pi)`][$1/(2pi)$][$1/(2pi)$][
  `1/2helloWorld`][$1/2helloWorld$][$1/(2helloWorld)$][
  `1/2L`][$1/2L$][$1/(2L)$]

which generates

Reproduction URL
No response
Operating system
Windows, Linux
Typst version

[X] I am using the latest version of Typst

It seems pretty consistent, just counter to your preference
Personally I'd like to move in the other direction. That is, less whitespace-dependence in math mode and simpler parsing for both humans and compiles.
Division has the same precedence as multiplication, and 2pi simply means 2pi. This means that 1/2pi=1/2pi=pi/2. Moreover, your proposal would only ever work for integer literals, not named constanfs.

I don't know what you mean by

your proposal would only ever work for integer literals, not named constanfs.

but if this is intended behavior that a numeral and symbol with nothing separating in sourcefile shouldn't end with nothing separating in the final output and instead bind with the strength of a * or dot operator then I'll close the issue.
I think 1/2L reads as 2L in the denominator not 1/2 L but if it's just a personal preference thing and not a bug then it doesn't matter.


add execute/select via map

This needs more testing, but conceptual PR I suppose for #63

@simolus3 is it possible to support bool in bindParam? I'll work further on this PR.
### ArgumentError: Invalid argument (params[9]): Allowed parameters must either be null or an int, num, String or List<int>.: false

is it possible to support bool in bindParam?

So the thing is that there's no sqlite3_bind_boolean, but IMO having support for bool by mapping it to sqlite3_bind_int64(value ? 1 : 0) is reasonable. After all, the TRUE and FALSE keywords in sqlite3 are doing the same thing.

Something is wrong. sqlite3 inconsistently and erratically returns 0 for the index for bind_parameter.  Explains some of the issues I had which also seemed random. I'll have to investigate more. This is the index number returned, followed by the named parameter and the value. For three inserts. Notice that the 0's randomly appear!
0 - @fieldid c51c15b8-55ee-4aa6-928e-c35a62e30e86
2 - @name word
3 - @internalname word
0 - @datatype Text
5 - @displaytype Text
6 - @indextype None
7 - @ix -1
0 - @pos -1
9 - @iskey false
10 - @isreadonly true
0 - @isreadonlyreadonly false
12 - @ishidden false
0 - @issystem false

0 - @fieldid f81dace2-18d0-439f-9970-b6b6e0489ca6
0 - @name definition
0 - @internalname definition
4 - @datatype Text
5 - @displaytype Text
6 - @indextype FullText
7 - @ix -1
8 - @pos -1
9 - @iskey false
0 - @isreadonly true
11 - @isreadonlyreadonly false
0 - @ishidden false
0 - @issystem false

0 - @fieldid a3e7113e-7c4f-4c0e-960b-96380132dc9e
0 - @name entryorder
3 - @internalname entryorder
4 - @datatype Integer
5 - @displaytype Text
6 - @indextype None
7 - @ix -1
8 - @pos -1
9 - @iskey false
10 - @isreadonly true
0 - @isreadonlyreadonly false
0 - @ishidden true
13 - @issystem false

I checked this and was able to fix it with final keyPtr = allocateBytes(keyBytes, additionalLength: 1); i.e., adding a null byte at the end of the string. sqlite3_bind_parameter_index has no provision for length.

Note: I don't really know now if additionalLength makes a null byte, do you know?*

Yes, allocateBytes will write zeroes for the additional length, so you don't have to ensure that manually.

I think I have given you access.

Thanks!


Diabetes prediction

Have you read the Contributing Guidelines ?
Yes I have read and followed all guidelines with regards to contributing
Description
Added Decision Tree, KNN, Naive Bayes and Logistic Regression, given that this topic is a first time project for many students, I have also added short descriptions about the algorithms and their working
Fixes #311

Checklist

[ Y] I've read the contribution guidelines.
[ Y] I've checked the issue list before deciding what to submit.
[Y ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
The future Scope of this could be adding Ensemble Models which I would like to do in a later pull request!

Will do :)


RCT1 vehicles

A while ago @Gymnasiast (I believe) mentioned importing RCT1 vehicles. There currently is the ability to add this to OpenRCT2, although it is not in an ideal state because there will be many sprites wasted.
This branch solves the waste of sprites for the most part, and is the branch against which the current vehicles are created:
https://github.com/spacek531/OpenRCT2/tree/frames-rotation-count-part-1
This vehicles repository:
https://github.com/spacek531/RCT1Vehicles
The vehicles in the repository could be merged with this repository after some tasks are complete.
Although it is relatively simple to load appropriate RCT1 vehicles only when necessary, users loading a park that has been touched originally by a linked version of OpenRCT2 will not see any sprites. This may or may not be an issue.

Duplicate of https://github.com/OpenRCT2/objects/issues/138


Prevent large values in conv module in wav2vec2_module.py in SSL recipe

I'm moving the conversation here since the previous PR was closed.
I ran @yfyeung 's training command using the merged k2ssl codes, with the batch-size and world-size adjusted to fit my environment. However, training crashed at epoch 31.
I then implemented @danpovey 's recommended changes, and reran training from the checkpoint at epoch 26. This time, training crashed at epoch 30.
The inf_check for this epoch 30 are as below. Infinity occurred at the forward pass of feature_extractor.
inf_check_ep30.txt
I have the diagnostics too for the start of epoch 30, but the file is too big to attach on Github. I can send it through email too if you'd like to take a look at it.
From what I can see, the Convolutional modules in the feature_extractor indeed have larger outputs.
Also, I'm wondering if I should rerun training from scratch using the recommended changes of penalizing large abs_value, or change the feature_extractor to Fbank-based Conv2dSubsampling. This current implementation consumes wav directly, matching original HuBERT. What do you think?

I'm moving the conversation here since the previous PR was closed.
I ran @yfyeung 's training command using the merged k2ssl codes, with the batch-size and world-size adjusted to fit my environment. However, training crashed at epoch 31.
I then implemented @danpovey 's recommended changes, and reran training from the checkpoint at epoch 26. This time, training crashed at epoch 30.
The inf_check for this epoch 30 are as below. Infinity occurred at the forward pass of feature_extractor. inf_check_ep30.txt
I have the diagnostics too for the start of epoch 30, but the file is too big to attach on Github. I can send it through email too if you'd like to take a look at it. From what I can see, the Convolutional modules in the feature_extractor indeed have larger outputs.
Also, I'm wondering if I should rerun training from scratch using the recommended changes of penalizing large abs_value, or change the feature_extractor to Fbank-based Conv2dSubsampling. This current implementation consumes wav directly, matching original HuBERT. What do you think?

Hi, batch size is crucial for SSL. When batch size decreases, gradient noise becomes very large, which has a bad impact on half-precision and convergence.

When batch size decreases, gradient noise becomes very large, which has a bad impact on half-precision and convergence.

I see.  Based on my available GPU world-size=4, I calculated accum-grad=4 and max-duration=300 so that the same 4800s of data is collected before the model is updated. However, do you think my approximation to your setup could be wrong?

Here is the tensorboard of my pre-training experiments.

Thank you so much! I will have a look!

  --max-duration 300 \
  --accum-grad 4 \

The current gradient accumulation mechanism simulates multi-GPU setup. You can simulate my setup using 4 GPUs with acc_grad set to 2 and max-duration set to 600, but it cannot simultaneously simulate multi-GPU and large batch size.

OK, this error is different from the error you got before.  It's the grads that are infinite, not the activations:
2024-04-22 11:07:35,431 WARNING [hooks.py:69] (2/4) The sum of module.feature_extractor.conv_layers.0.0.grad[0] is not finite
2024-04-22 11:07:35,438 WARNING [hooks.py:69] (2/4) The sum of module.feature_extractor.conv_layers.0.1.grad[0] is not finite
2024-04-22 11:07:35,438 WARNING [hooks.py:78] (2/4) The sum of module.feature_extractor.conv_layers.0.0.weight.param_grad is not finite

Note that these are the grads after aggregating over the batch.  Too-large grads on the first input convolution layer when training with fp16 are a problem I have noticed before.  Probably the most certain fix would be to insert a ScaleGrad module to scale the grad down at that point during the backprop.  E.g. insert it after conv_layers.0, into the nn.Sequential's list or something.    See how I have used that in the zipformer recipe, to solve a similar issue.
This would change the numbering though, so would affect loading parameters.  Alternatively you might be able to add a ScaleGrad module at the end of the layer type you use in conv_layers, whatever it is.   Use a moderate scale, like, 0.5, if it will appear multiple times.  And it must never be inserted in a "side branch" of the computation graph that will re-join, or it will cause wrong update directions.  (Just don't add it anywhere except where computation is purely sequential.)   Caution, a too-small scale will lead to too much roundoff before aggregation of gradients.   You can make a pull request on top of my pull request.
I believe this will make the training recipe more robust; it's good that you found this issue, we should make sure to commit a fix to icefall.


[1.6] Support Alibaba Cloud Docker Hub webhook

payload of Alibaba Cloud Docker Hub's webhook is slightly different from Docker Hub.
PR for webhook-service change is here
So I have added an option in UI for it #9175
Also fixed the issues #7996 and #9022

@vincent99 backend is merged, though not released yet.


Remove Access-Control-Allow-Origin headers from all endpoints

This may not be necessary as the information exposed via the API is meant to be totally public and there are no security concerns with other sites requesting it.


Minimal diff

I see PR's from greenkeeper that remove whitespace "formatting" from the package.json.
Expected behavior:
If a version bump is suggested, the PR should affect only one line, and basically only the version string on that line.
Actual behavior:
Whitespace is removed, structures are "beautified" according to some preference/styleguide that isn't mine/ours.

Heya, thanks for the report! Can you show us a link to the PR?

I updated and squashed the one in question, but here's an old one that wasn't pulled;
https://github.com/the-grid/finitedomain/pull/31/files

And for reference, this is what I'd expect;
https://github.com/the-grid/finitedomain/pull/47/files

For reference: We're currently using this package to do the updates https://github.com/boennemann/json-preserve-indent
If anyone wants to improve our behaviour on their own a PR to that package is highly appreciated.
We are also considering switching to a RegEx based option, but would ideally would want to avoid it.
There is a package that already does what we want, except for it's broken: https://github.com/substack/jsup
Thanks,
Stephan

This is fixed, as we're now using https://github.com/finnp/json-in-place in the worker.
Thanks y'all.

thanks!


Remove redundant assertion for cyclic SyntaxArenas

When running the stress tester locally, the SwiftSyntax parser was significantly slowed down by this (we spent multiple seconds in this check).

It's a little strange that stress-tester reaches here so often. Does it often do incremental parsing many times?

@swift-ci Plese test

@swift-ci Please test


Exact matching for search terms no longer works after dependency updates

Caused by fixing #9

Exact issue is with the typeahead module. When selecting a recommendation given by typeahead, and doing the search, the results are not filtered accordingly.

Modified search logic, so in case a typeahead option is selected, the proper variable will be emitted for querying the API.
Opened #11 for further UX enhancements of the search logic.


As a developer I would like to do sync actions on property changes

Description
There is no public API that allows for sync actions like logging or "computed" properties.
Example use case:
Logging We like cats too :) whenever the property mood gets set to cat.
Live Demo
https://stackblitz.com/edit/lit-element-example-nkwdco?file=index.js
Expected Results
=> set to cat
We like cats too :)
=> set to foo
=> set to cat
We like cats too :)

Actual Results (when using public API update)
=> set to cat
=> set to foo
=> set to cat
We like cats too :)

Code for reference:
  update(changedProperties) {
    super.update(changedProperties);
    if (changedProperties.has('mood')) {
      if (this.mood === 'cat') {
        console.log('We like cats too :)');
      }
    }
  }

Note
Workaround with _requestUpdate works but it's a private API.
Code for reference:
  _requestUpdate(name, oldValue) {
    super._requestUpdate(name, oldValue);
    if (name === 'mood') {
      if (this.mood === 'cat') {
        console.log('We like cats too :)');
      }
    }
  }

Versions

lit-element: v2.1.0

another usage example
this.firstName = 'foo';
// fullName should be updated whenever firstName or lastName changes

if (this.fullName.contains('foo')) {
  // do something
  // never reached as fullName will only be updated in the next microtask if using `update`
}

You could use the hasChanged method:
  static get properties() {
    return {
      mood: {type: String, hasChanged: (newVal, oldVal) => {
        if (newVal === 'cat') {
          console.log('We like cats too :)');
        }
        return true
      }}
    }
  }

hmmm using hasChanged probably could work but that certainly looks like abuse 🙈
also when extending web components it's tough as you can't easily add another function in your child...

using hasChanged probably could work but that certainly looks like abuse

and you don't have access to component instance (this). So anything that needs to access the instance won't work

@daKmoR On the side of logging, to better inform the outcomes you hope to see in this request, can you explain how you see this as being different than a custom getter/setter?
get mood() { return this._mood; }
set mood(mood) {
  if (mood === this.mood) return;
  if (mood === 'cat') console.log('We like cats too :)');
  const old = this._mood;
  this._mood = mood;
  this.requestUpdate('mood', old);
}

In the context of your computed properties, it would seem that a getter would also provide much of what could be needed here:
get fullName() {
  return `${this.firstName} ${this.lastName}`;
}
...
this.firstName = 'foo';
// fullName should be updated whenever firstName or lastName changes

if (this.fullName.contains('foo')) {
  // do something
}

In the above case the // do something would be hit because the properties update of firstName is available synchronously. It's certainly not "reactive" in a way that would allow logging, but helping to clarify the the outcomes you hope to see in this request.
Maybe it's just boilerplate, or convention vs configuration, but whether those or something else I look forward to your thoughts here.

does 'updated' fire too late for your purposes, @daKmoR ?
updated(props){
  if(props.has('mood'){  //  mood has changed
    if(this.mood === 'cats'){  //  mood has changed to 'cats'
      console.log('we like cats too :)')
  }
}

actually, this whole thing started while I was preparing a blog post about testing - and I wanted to have a simple example of how you can do an action on a property change. In my ignorance, I thought just log something that should be easy... oh boy was I wrong 🙈
That was the actual test I started out with.
it('logs "We like cats too :)" if the value is set to "cat"', async () => {
  const el = /** @type {A11yInput} */ (await fixture(html`
    <a11y-input></a11y-input>
  `));
  const logSpy = sinon.spy(el, 'log');

  el.value = 'cat';
  expect(logSpy.callCount).to.equal(1);
});

So primarily it's not about logging - it was just an example. Depending on which type of logging you wanna do updated could certainly be good enough.
Why not a custom getter/setter?
I would still like to use all the features of a property.

reads inital attribute
reflect it to attribute
can react to attribute changes
show up in a properties list (you can use to auto generate playgrounds)
...

this of course works but I would need to redo all the attributes logic
Why not just a getter?

It should support arbitrary actions that do not need accessing the property
The computation of this "combined" value could be heavy (e.g. it should be performant to access it many many times)

Conclusion
As far as I can tell these are the hard requirements:

It needs to be synchronous
It needs to support arbitrary actions
It needs to allow adding of more actions when extending

You can read the really long full story here - the link goes tot he relevant part where I discover the "issue": https://dev.to/open-wc/testing-workflow-for-web-components-g73#spying-on-code

It seems like making _requestUpdate something protected like setProperty would unlock this? That's probably a reasonable change.

It seems like making _requestUpdate something protected like setProperty would unlock this?

AFAIK, yes

It seems like making _requestUpdate something protected like setProperty would unlock this? That's probably a reasonable change.

what do you mean? rename _requestUpdate  to setProperty?
or just call setProperty inside _requestUpdate like so
_requestUpdate(name, oldValue) {
  // _requestUpdate code then at the end
  this.setProperty(name, oldValue);
}

if yes then I (or someone) could prepare a PR for it 💪

@sorvell if you could give a hint on how it should look like I'm sure I could prepare a PR 🤗

Sorry, I was thinking just renaming _requestUpdate to setProperty. I
can't say for sure if this makes sense as I haven't really thought about it
much more, but we can iterate on the PR.
On Sat, Apr 27, 2019 at 6:39 AM Thomas Allmer<EMAIL_ADDRESS>wrote:

@sorvell https://github.com/sorvell if you could give a hint on how it
should look like I'm sure I could prepare a PR 🤗
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/lit-element/issues/643#issuecomment-487286903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAATIK6IAJYLIOQK4JQGQX3PSRJPRANCNFSM4HECYBNA
.

I was thinking just renaming _requestUpdate to setProperty

This covers my use case (i was overriding _requestUpdate)

The best place to do this is in _requestUpdate.
  /**
   * Called synchronously when a property has changed.
   */
  protected propertyChanged(name: PropertyKey, oldValue?: unknown): void {}

  private _requestUpdate(name?: PropertyKey, oldValue?: unknown) {
    let shouldRequestUpdate = true;
    // If we have a property key, perform property update steps.
    if (name !== undefined) {
      const ctor = this.constructor as typeof UpdatingElement;
      const options =
          ctor._classProperties!.get(name) || defaultPropertyDeclaration;
      if (ctor._valueHasChanged(
              this[name as keyof this], oldValue, options.hasChanged)) {
        if (!this._changedProperties.has(name)) {
          this._changedProperties.set(name, oldValue);
        }

        // Hook to allow synchronous property change observers.
        this.propertyChanged(name, oldValue);

        // Add to reflecting properties set.
        // Note, it's important that every change has a chance to add the
        // property to `_reflectingProperties`. This ensures setting
        // attribute + property reflects correctly.
        if (options.reflect === true &&
            !(this._updateState & STATE_IS_REFLECTING_TO_PROPERTY)) {
          if (this._reflectingProperties === undefined) {
            this._reflectingProperties = new Map();
          }
          this._reflectingProperties.set(name, options);
        }
      } else {
        // Abort the request if the property should not be considered changed.
        shouldRequestUpdate = false;
      }
    }
    if (!this._hasRequestedUpdate && shouldRequestUpdate) {
      this._enqueueUpdate();
    }
  }

Synchronous property change observers are useful in many cases, at least for me. Right now, I have to use custom setters to achieve that, which has a fair amount of boilerplate.

This has been inactive for awhile, but we recently merged https://github.com/Polymer/lit-element/pull/959 which is at least related to this.
In general we've chosen an asynchronous rendering model for LitElement because we think it sets up users for great performance out of the box. Rendering updates are naturally batched and occur before anything is painted to the screen. This does put a burden on the test environment, and this is one reason we've exposed the updateComplete promise. This promise can easily be awaited to check the rendering state of an element.
We've also recently landed the ability to customize LitElement's default property handling by specifying a custom property descriptor using static getPropertyDescriptor. This should enable users to make base classes that specify custom property options and perform specific actions. For example, it should be simple to make an observer type feature similar to what existed in Polymer. It's also possible to make properties that update the element synchronously by calling performUpdate. This matches our core development philosophy: setup developers for success as much as possible out of the box while also empowering them to innovate outside the box.


Create a workshop about interacting with HTTP services using the HTTP Camel component

Please describe the task that needs to be done
For demo purposes, it would be beneficial to create a workshop that uses the HTTP Camel component to retrieve data from an external source
To be published here: https://kaoto.io/workshop/
To be written here: https://github.com/KaotoIO/kaoto.io/tree/main/content/workshop

We have that one already at https://kaoto.io/workshop/beginner-camel-choice/ (see Section 3)


_NIOBeta doesn't compile with Swift 5.7

_NIOBeta is assuming Swift.Duration is a valid symbol in Swift 5.7 when it is not.
System and version information
swift-nio: dee448a
swift: swift-driver version: 1.62.8 Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.4 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx12.0

The bigger issue is that the symbol is valid in Swift 5.7 on every platform except macOS.

But more broadly, yes, it's possible to run Swift 5.7 with a newer SDK.


WebSocket checkStartWith behave not good when set websocket path to '/'

Expected behavior
when create an websocket handler like this
WebSocketServerProtocolHandler h = new WebSocketServerProtocolHandler("/",true);

i expected:
/ return true
/my-sub-path return true
Actual behavior
from https://github.com/netty/netty/issues/10582#issue-702625436
only these path can be passed
/
//my-sub-path
path like /my-sub-path is rejected,which is counter-intuitive
Steps to reproduce
just run a websocket server with this handler
WebSocketServerProtocolHandler h = new WebSocketServerProtocolHandler("/",true);

Minimal yet complete reproducer code (or URL to code)
/**
 * @author w00464553
 * @date 2020/5/25
 */
public class Application {
    public static void main(String[] args) {
        EmbeddedChannel channel = new EmbeddedChannel(
                new HttpServerCodec(),
                new HttpObjectAggregator(65536),
                new WebSocketServerCompressionHandler(),
                new WebSocketServerProtocolHandler("/", true));

        DefaultFullHttpRequest request = new DefaultFullHttpRequest(HttpVersion.HTTP_1_1, HttpMethod.GET,
                //this path will be rejected by handler,change to '/' or '//v1/my-path' to see
                //a successful handshake
                "/v1/my-path");
        request.headers().set("upgrade", "websocket");
        request.headers().set("sec-websocket-key", "dGhlIHNhbXBsZSBub25jZQ==");
        request.headers().set("sec-websocket-version", "13");

        channel.writeInbound(request);
        Object o = channel.readOutbound();
        if (o instanceof ByteBuf) {
            ByteBuf bb = ((ByteBuf) o);
            byte[] buf = new byte[bb.readableBytes()];
            bb.readBytes(buf);
            //if success, an 101 Switching Protocols will be printed
            System.out.println(new String(buf));
        } else {
            //or null
            System.out.println(o);
        }
    }
}

Netty version
4.1.63.Final

@roycarser I would be happy to review a PR... But please before try to update to the latest netty version and see if the issue still remains

@roycarser I would be happy to review a PR... But please before try to update to the latest netty version and see if the issue still remains

thanks,this issue still remains in 4.1.63.Final


fix: Permit enums w/o values. Fixes #11471.

Fixes #11471
Motivation
As described in the above issue, it's currently pretty impossible to use enum fields and have lint pass. This makes them effectively useless in workflow templates.
Modifications
Updated the enum checks in the validate code in order to respect allowEmptyValues.
Verification
Updated unit tests and tweaked code until they passed as expected.

Someone may need to rerun the E2E tests... I don't seem to have permission to do so!

Someone may need to rerun the E2E tests... I don't seem to have permission to do so!

@Just push an empty commit or something similar to get the CI to re-run


Add BDArmoury DMP Addon from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of jediminer543, to add BDArmoury DMP Addon to CKAN.
Please direct questions about this pull request to jediminer543.

Uses a custom version of BDArmory, waiting on info from author on if more changes will be made other than BahaTurret.dll

Only the 1 file should ever be affected. So a BDarmory split seems like the way to proceed.

https://github.com/KSP-CKAN/CKAN/issues/1311 would benefit this mod

Mod updated to 0.9.1, but there's also another PR relating to this. See PRs  #2042 and #2065

@draeath I think you're in the wrong PR. You're talking about BDArmory, this is to add BDArmoury DMP Addon.
Unrelated to that, I don't think we can currently index this mod via netkan. The mod author isn't using a version scheme we can follow, he's simply using the git commit hashes as his version numbers.

Closing this due to age. If the mod releases/gets a stable versioning scheme this can be re-opened.


Remove some obsolete // ignore:

Description
These were no longer ignoring any warnings. They have been identified as obsolete by @srawlins in https://github.com/flutter/flutter/pull/45855.
Related Issues
None
Tests
I added the following tests:
None, comment only change.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

Although cirrus seems to be unhappy right now. Looks to be timeouts.

Restarted all the cirrus checks that timed out.

This would be a good one to land on red to kick CI.  We've disabled some fuchsia tests that are flaky right now.  That should be rolled through in a few minutes.

@dnfield Feel free to submit this whenever the roll is done.

Submitting on red per @dnfield's comment.


Clean up dependencies

serde_json wasn't used at all in lumeo-commands
the new_v4 Uuid constructor is only used in a commands test

Seems a bit excessive to rewrite git history for such a small thing, but I'll keep it in mind for the future.


Enhancement: Run dependency analysis on PHP 8.0

This PR

[x] runs the dependency analysis on PHP 8.0

❗ Blocked by https://github.com/maglnet/ComposerRequireChecker/pull/201.

Closing because support for PHP 7.3 and below was dropped upstream.

Closing because support for PHP 7.3 and below was dropped upstream.


The public /api/customers/identify endpoint should be more secure

Problem
For customers who include Papercups in their self-hosted open-source projects, there is potential for their user IDs to conflict with other deployments of the project (e.g. if the users table has auto-incrementing integer IDs).
In the meantime, to work around this customers can fix this by updating the external_id set on the widget to be unique across environments (e.g. by including the hostname in the ID, or some other unique identifier)
But we should obvious fix it on our end too!
Solution
Some initial thoughts:

I think the easiest solution for now is to use the host information on the HTTP request as an additional filter when searching for a matching customer here: https://github.com/papercups-io/papercups/blob/master/lib/chat_api_web/controllers/customer_controller.ex#L47
We could also match on the customer email if one is provided in the config.
One potential issue with matching against the host name EXACTLY is that it would prevent user conversations from being shared across subdomains, but we can always fix that later. I'd rather err on the side of being more restrictive than less.

Open questions:

What's the most secure way we can allow our customers to make sure their users can always see their message histories when logged in (to our customers' platforms)?
We probably can't use cookies/localStorage since this wouldn't work across devices, right?
Should we add support for whitelisting URLs?

after thinking about this a bit more, it might be best to avoid using explicit customer fields (like id and email) to figure out which conversations to load in general, and just stick with the more opaque token we cache in the browser
this has the downside of not loading conversation history when a user switches browsers/devices, but it might be a reasonable trade-off

after thinking about this a bit more, it might be best to avoid using explicit customer fields (like id and email) to figure out which conversations to load in general, and just stick with the more opaque token we cache in the browser
this has the downside of not loading conversation history when a user switches browsers/devices, but it might be a reasonable trade-off

As a suggestion you could also optionally delegate the token logic to the client (e.g. PostHog). Then on the client side we can store a token (on our DB) with enough randomness to be secure enough. An even better approach would be the ability to provide a user ID with a tamper-proof signature that you can validate async (e.g. a JWT). With this, the client would have the option of supporting end users moving between devices/browsers without losing their chat history without compromising security. Though I would do this as an improvement after fixing the underlying bug.

As a suggestion you could also optionally delegate the token logic to the client (e.g. PostHog). Then on the client side we can store a token (on our DB) with enough randomness to be secure enough. An even better approach would be the ability to provide a user ID with a tamper-proof signature that you can validate async (e.g. a JWT). With this, the client would have the option of supporting end users moving between devices/browsers without losing their chat history without compromising security. Though I would do this as an improvement after fixing the underlying bug.

@paolodamico i like that idea :) but i'm still not completely sure i understand how that would work in practice -- would papercups be issuing the JWT, or would you guys?

@paolodamico i like that idea :) but i'm still not completely sure i understand how that would work in practice -- would papercups be issuing the JWT, or would you guys?

I've been giving it more thought and doing the shared secret or some sort of async signing might be an overkill. Particularly, if we consider for instance a JWT signed with HS256, the signature hash length would be 32 bytes. From this you could simply allow the client the option to provide the unique ID and maybe just clarify that the ID should have enough entropy (be generated by a cryptographically secure random generator and I would assume the 32 byte length), and that overriding this has security implications. You could consider enforcing on your end a certain length to make sure it's used correctly, but this is not enough to guarantee entropy and might not be worth the trouble.
Disclaimer: I'm not, by any means, an expert in security or cryptography.

I've been giving it more thought and doing the shared secret or some sort of async signing might be an overkill. Particularly, if we consider for instance a JWT signed with HS256, the signature hash length would be 32 bytes. From this you could simply allow the client the option to provide the unique ID and maybe just clarify that the ID should have enough entropy (be generated by a cryptographically secure random generator and I would assume the 32 byte length), and that overriding this has security implications. You could consider enforcing on your end a certain length to make sure it's used correctly, but this is not enough to guarantee entropy and might not be worth the trouble.
Disclaimer: I'm not, by any means, an expert in security or cryptography.


Why UDP??

Just one simple doubt. Why use of UDP for lora-gatewat-bridge.. Can we configure this with TCP/IP???

That is exactly what the LoRa Gateway Bridge is for, converting the packet_forwarder UDP protocol into JSON over MQTT (thus TCP/IP).


Failed test jumps to output line

I run a test that includes some console.log lines, and it fails. I'd prefer it to jump to the failed assert line, but it goes to the console.log line which is in a different file and isn't that helpful.

Actually, are these even differentiated in the API? Maybe it's not possible to change this


Can't originate TLS to external domains

    getambassador.io/config: |
      ---
      apiVersion: ambassador/v0
      kind:  Mapping
      name:  httpbin2_mapping
      prefix: /
      service: https://httpbin.org:443
      host_rewrite: httpbin.org

Doesn't work (you get an upstream connect error or disconnect/reset before headers).

@kflynn
This seems to be related to #424
Can you have a look at this issue?

The big difference between using a redirect and not is that when you use the redirect, the entity speaking TLS to example.com is actually the browser, rather than Ambassador's Envoy.  The actual error that happens when I try the non-redirect example (to httpbin.org) is
SSL error: 268436536:SSL routines:OPENSSL_internal:TLSV1_ALERT_INTERNAL_ERROR

which implies that we're looking at a version mismatch when Envoy tries to speak to httpbin.org. Sigh.

The previous comment is wrong. The problem is that unless SNI is explicitly configured, Envoy won't offer SNI, and httpbin.org requires SNI or it shuts the connection down. Looking at the minimal path forward here...


Change this title, poorly formatted issues will not be handled

System OS
Linux
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
v4.1.4
Expected Behavior vs Actual Behavior
Every time a song is being downloaded, it prints a red error:
Failed to get results for [song name]: Expecting value: line 1 column 1 (char 0)

It then successfully downloads the song, printing a green success message
Steps to reproduce - Ensure to include actual links!
Download any songs:
spotdl https://open.spotify.com/track/1MqzIgGsHP4cNjPboevsfq?si=03d85ea6a77f472d
Traceback
$ spotdl https://open.spotify.com/track/1MqzIgGsHP4cNjPboevsfq?si=03d85ea6a77f472d
Processing query:
https://open.spotify.com/track/1MqzIgGsHP4cNjPboevsfq?si=03d85ea6a77f472d
Failed to get results for Tourner Dans Le Vide - Indila: Expecting value: line 1
column 1 (char 0)
Downloaded "Indila - Tourner Dans Le Vide":
https://music.youtube.com/watch?v=ONlMB2oGWwE

Other details
No response

Can you upload more logs with --log-level DEBUG?

Sure 😃
[11:07:53] DEBUG    MainThread - Downloader settings:                downloader.py:114                    {'audio_providers': ['youtube-music'],
'lyrics_providers': ['genius', 'azlyrics',
'musixmatch'], 'playlist_numbering': False,
'scan_for_songs': False, 'm3u': None, 'output':
'{artists} - {title}.{output-ext}', 'overwrite':
'skip', 'search_query': None, 'ffmpeg':
'ffmpeg', 'bitrate': None, 'ffmpeg_args': None,
'format': 'mp3', 'save_file': None,
'filter_results': True, 'threads': 4,
'cookie_file': None, 'restrict': False,
'print_errors': False, 'sponsor_block': False,
'preload': False, 'archive': None,
'load_config': True, 'log_level': 'DEBUG',
'simple_tui': False, 'fetch_albums': False,
'id3_separator': '/', 'ytm_data': False,
'add_unavailable': False, 'geo_bypass': False,
'generate_lrc': False, 'force_update_metadata':
False}
[11:07:53] DEBUG    MainThread - FFmpeg path: ffmpeg                 downloader.py:132
[11:07:53] DEBUG    MainThread - Found 0 known songs                 downloader.py:157
[11:07:57] DEBUG    MainThread - Archive: 0 urls                     downloader.py:192
[11:07:57] DEBUG    MainThread - Downloader initialized              downloader.py:194
[11:07:57] INFO     MainThread - Processing query:                       search.py:123
https://open.spotify.com/track/1MqzIgGsHP4cNjPboevsf
q?si=19aa3dc296ef49cb
[11:07:57] DEBUG    MainThread - Found 1 songs in 0 lists                search.py:249
[11:07:57] DEBUG    MainThread - Downloading 1 songs                 downloader.py:241
[11:07:57] ERROR    asyncio_0 - Failed to get results for Tourner Dans Le   base.py:82
Vide - Indila: Expecting value: line 1 column 1 (char
0)
[11:07:57] DEBUG    asyncio_0 - Genius failed to find lyrics for     downloader.py:358
Indila - Tourner Dans Le Vide
[11:07:58] DEBUG    asyncio_0 - AzLyrics failed to find lyrics for   downloader.py:358
Indila - Tourner Dans Le Vide
[11:08:01] DEBUG    asyncio_0 - MusixMatch failed to find lyrics for downloader.py:358
Indila - Tourner Dans Le Vide
[11:08:01] DEBUG    asyncio_0 - No lyrics found for Indila - Tourner downloader.py:482
Dans Le Vide, lyrics providers: Genius,
AzLyrics, MusixMatch
[11:08:01] DEBUG    asyncio_0 - [1MqzIgGsHP4cNjPboevsfq] Searching for     base.py:163
indila - tourner dans le vide
[11:08:01] DEBUG    asyncio_0 - [1MqzIgGsHP4cNjPboevsfq] Found 3 results   base.py:175
for ISRC FRUM71400047
[11:08:01] DEBUG    asyncio_0 - [1MqzIgGsHP4cNjPboevsfq] Filtered to 3     base.py:187
ISRC results
[11:08:01] DEBUG    asyncio_0 - [1MqzIgGsHP4cNjPboevsfq] Best ISRC result  base.py:196
is https://music.youtube.com/watch?v=ONlMB2oGWwE with
score 100.0
[11:08:01] DEBUG    asyncio_0 - Downloading Indila - Tourner Dans Le downloader.py:554
Vide using
https://music.youtube.com/watch?v=ONlMB2oGWwE
[11:08:07] INFO     asyncio_0 - Downloaded "Indila - Tourner Dans Le downloader.py:716
Vide":
https://music.youtube.com/watch?v=ONlMB2oGWwE


Creating DX11.3 device succeeds when RenderDoc is present

My code is trying to create highest possible DX11 device, but when RenderDoc (v0.22) is present it succeeds even when GPU/OS is not capable of supporting device version.
Code here should fail on creating 11.3 and 11.2 on Win7:
https://github.com/bkaradzic/bgfx/blob/master/src/renderer_d3d11.cpp#L598

I think that change should fix it so QueryInterface will only return a pointer and S_OK when the underlying device does. It works for me (although I can get a 11.2 device on Win7 it seems, I think I have that horrible KB patch that backports no useful support but still returns the ID3D11Device2), but can you check that it fixes it for you?

This is fixed. Thanks! :+1:


Add Wireshark

Wireshark (network analysis and capture tool + USB capture) is GPL2.  There should be no barrier to redistribution.  The protocol analyzers are quite nice.

My thought is of a corporate environment.  I may have rights to have virtual machines but not run wireshark on the host box.  Inside the VM is a more tolerable solution for some companies.
I personally like the fact that everything is self contained, all the tools needed are present in that environment.  Though I understand the desire to not have the bloat, especailly when someone is cloning VMs on a per application basis and may have several apps being worked on in parallel.


Extend Cypress E2E Blocks Page Test

As mentioned in this PR we should extend this tests suite.

We can even reassign for @valfaro123 or @Thistle-Strum


feature request: Add the option to provide a where condition

It would increase userfriendliness if an optional filter condition could be passed to a comparator (eg the SqlCompyreComparator) that allows to prefilter the two tables before comparing them

Should the condition be a SQLAlchemy condition (e.g. sa.column("col_name") == 2) or rather raw sql (e.g. col_name = 2)?


rmt can not exit when sync redis data to rdb files

firstly, show my rmt.conf as follows:
[source]
type: single
servers:
-<IP_ADDRESS>:6379
-<IP_ADDRESS>:6380

[target]
type: rdb file

[common]
listen: <IP_ADDRESS>:8888
step: 1
mbuf_size: 4096
source_safe: true
dir: data

When rmt completes its job,  the rmt process suspended and did not halt. By rmt.log, I noticed that both the read thread read_thread_run and the write thread write_thread_run did not terminate when the rob files have been saved.
To use rmt, I clone a fork and try to modify it to let it run by my rmt.conf. But it can not run If the value of source_safe is false.
Hope u check my code and fix this bug. Thanks.

The same as pr #27.


Takang03:Welcome-to -JS: 3 weeks

my fork of module repository

Learning Objectives
1. What is Programming
What is a program? What is a programming language? How do programs and people
fit together?

[x] Data in, Data Out: You understand that computer programs are used to
transform data, and can explain a JS program from this module in terms of
the data that goes in and the data that comes out.
[x] Three Audiences: You can explain how a single file of code is used to
communicate with 3 different audiences:
[x] Developers: You can explain how code formatting, comments, logs and
variable names make it easier (or harder!) for a developer to understand a
program.
[x] Computers: You can explain how a computer follows your instructions to
store, read and modify data in program memory.
[x] Users: You can explain how the computer creates a dynamic user
experience by following different executions paths depending on user
input.
[x] Tracing Variables: You can complete a trace table for a program that
uses only variables, and can check your work using the "trace" button.

2. Just Enough JavaScript
Go in depth on JavaScript you need to know for writing interactive text-based
programs in the browser. Along the way you will learn how each language feature
works in small programs.

[x] JavaScript Syntax: Given a program, you can identify these parts of
JavaScript syntax:
[x] Primitives
[x] Operators
[ ] Identifiers
[ ] Keywords
[ ] Checks
[ ] Blocks
[ ] Function Calls
Listening and Reading: You can read code out loud, and understand your
classmates when they read code to you. You don't need to understand how a
program works to master these learning objectives!
[ ] Listening You can exactly re-write a program that a classmate has read
[ ] Reading You can read a program out loud and guide your classmates to
re-write exactly the same code without them seeing the program. Every
indentation, semi-colon, comment and spelling in their program must be
identical to yours.
[ ] Static vs. Dynamic Analysis: You can explain and use these two ways of
studying a program, each can help you understand different aspects of your
code. To help understand this concept, the options panel in Study Lenses
is organized into static and dynamic study options:
[ ] Static: Studying the text in a code file without running it. Some
static study methods are creating a flowchart, analyzing variables,
filling out a trace table, and drawing on code.
[ ] Dynamic: Running code and studying the computer's behavior. Some
dynamic study methods are running code and reading console logs, using the
trace button, and stepping through in the debugger or JS Tutor.
[ ] Tracing Execution: You can complete a "steps" trace table for all JS
language features in Just Enough JavaScript, and can correct your table
using console output from the "trace" button.
[x] Analyzing Variables: You can list all the variables in a program, and
answer these 5 questions for each variable:

Where is the variable declared?
What is the variable's scope?
Is the variable initialized with a value?
How many times is its value used (read) in the program?
How many times is the variable assigned a new value?
What types are assigned to this variable during the program's execution?

[ ] Completing Programs: You can successfully fill in blanks for a program
when the missing words are provided, including distractors.
[ ] Translating Pseudo Code: Given a program written in Pseudo Code, you
can translate it to working JavaScript.
[ ] Comparing Programs: You can compare two programs with similar code and
explain if they have the same behavior or not. If they do not, you can
explain how they behave differently and why.
[ ] Constructing Programs: You can reconstruct a program's lines and
indentation, successfully ignoring distractor lines.

3. Understanding Programs
Learn how to understand a larger programs by finding connections between the
details and the big picture. By the end of this chapter you will know how to
read a new program and do a simple code review.

[x] Stepping Through: You can pause a script in a your browser's debugger,
arrange the debugger, collapse extra panels, and step through a script
written with Just Enough JS. At each point in execution you can make a
prediction of the next line before executing, and can check your
prediction using the scopes panel.
[ ] Imperative Programming: You can explain what the Imperative
Programming paradigm is, and can explain how you know the programs in
Welcome to JS are Imperative.
[ ] Program Goals: You understand that a full JavaScript program can be
explained as a series of smaller goals, and can write names for the goals
in a simple working program.
[ ] Logging: You can tracing specific aspects of a program's execution and
log them to the console.
[ ] Tracing Backwards You can trace backwards from a program's output to
it's input.
[ ] Naming Variables: You can analyze how a variable is used in a program
and give it two names:

Generic: You can give a generic name to a variable based on how it is
used in the program.
Specific: You can give a specific name to a variable based on how it's
used and the program's domain (the program's specific data and use-case).

[ ] Describing Programs: You can read a program and describe it with
comments using to the methodology from /describing-programs:

Zoom Out
Zoom In
Find Connections
Describe Goals

[ ] Code Review: Given a working program you can review the code for
clarity, correctness and style.
[ ] Same Behavior, Different Code: You can study simple programs with the
same behavior (data in, data out) but different source code and explain
how the differences matter for each audience.

4. Developing Programs
Learn to modify and write larger programs in JavaScript. You'll cover many of
the hidden skills necessary to develop quality software and to work
collaboratively on a code base.

[ ] Linting: You can find and fix simple linting errors in JavaScript
programs.
[ ] Program Life Cycle: You can explain the two phases of a program's life
cycle.

Creation Phase
Execution Phase

[ ] Fixing Errors: You can use the structured comment to describe an error
in your program, and can make several educated guesses at how to fix the
error.
[ ] Fixing Bugs: You can use the structured comment to describe and fix a
bug in small programs.
[ ] Modifying Programs: You can make small changes in a program to change
its behavior without breaking it.
[ ] Refactoring: Given a working program, you can make changes to the code
without changing the program's behavior.
[ ] Writing Programs: Given a description of a program's behavior (user
story + test cases), you can plan goals for the program and write code to
pass the tests.
Reverse Engineering: Given a working program with unreadable code, you
can:
[ ] Give the program a name.
[ ] Describe the program's behavior with a user story, acceptance criteria and
test cases.
[ ] Plan goals for the program.
[ ] Develop your own working program with the exact same behavior.
Imagining Programs: Given an empty page, you can imagine and develop your
own programs using Just Enough JavaScript. This includes:
[ ] A title.
[ ] A description with a user story, acceptance criteria and test cases.
[ ] Commented goals.
[ ] Fully working Code.

Week 1
I Need Help With:
I need help in understanding JS
What went well?
The topic was well taught and collaboration was great with classmates.
What went less well?
Understanding the logical approach of JS
Lessons Learned
clone and fork from the master to my github repository
Sunday Prep Work
Looking forward for the next step in JS inside-js
Week 2
I Need Help With:
I need help in understanding JS
What went well?
The topic was well taught and collaboration was great with classmates.
What went less well?
Understanding the logical approach of JS
Lessons Learned
clone and fork from the master to my github repository
Sunday Prep Work
Looking forward for the next step in JS inside-js

@Takang03  do you have any questions we can help?

@Takang03 Week 1 and week 2 are the same.

@Takang03  you need to be more specific, with what concepts do you need help with?

There are parts that are the same in all the 3 weeks, for example, 'Lessons Learned' and 'What went less well'.


WAI-ARIA group is missing a name

I understand from reading https://reach.tech/router/accessibility that the intention of the line of code below is to manage focus for accessibility. Thank you for your effort toward better accessibility. Unfortunately, that line of code generates an accessibility error when testing in Siteimprove.

The issue is that when applying a WAI-ARIA landmark with the role="group", a name must also be provided. The element can be named by applying the WAI-ARIA aria-label attribute or aria-labelledby in conjunction with visible text.
https://www.w3.org/TR/WCAG20-TECHS/ARIA17
https://www.w3.org/TR/wai-aria-practices-1.1/#carousel

Also, the role="group" is a bit cumbersome or irregular if it is wrapping, for example, a page , , and .  I suggest: ```
Focus is now at just before new content
```
That screen-reader-only text technique is from https://webaim.org/techniques/css/invisiblecontent/ and has best cross-browser compatibility.

focus must work for sighted keyboard only users as well, not just screen reader users. but visual focus indication combined with the screen-reader only technique may work.

Yeah I was just thinking about that. Also I expect that some automated testing suites may soon check for visible focus indicators having the newly-required minimum 3:1 luminance contrast ratio (https://knowbility.org/blog/2018/WCAG21-1411Contrast/).  Frequently I have encountered some friction with designers regarding the presence of any focus indicators on non-interactive elements in these usage scenarios. Also I think setting focus on an invisible target when new content is drawn is low-risk if pressing tab is the safest and most likely outcome, though it might not be super-friendly.  But for a minimalist conformant approach you could do something like this:
. style="clip: rect(1px, 1px, 1px, 1px);
clip-path: inset(50%); height: 1px; width: 1px; margin: -1px; overflow: hidden; padding: 0; position: absolute;" >Focus is now at a point just before new content.

So that's a period that turns grey on focus and invisible on blur.
I just remembered that using outline: transparent will ensure that an outline is visible in Windows High Contrast mode. Also the href="javascript:void(0)" will avoid a different automated testing warning.

If there is any concern about using the phrase I have suggested above, I'd suggest a simple "Ready." as an alternative.  But a blank target (depending on the role) may not tell a screen reader user that anything has changed vs. when the router was triggered.  In other contexts we have used "Ready." to indicate when a full-pay loading indicator is removed and the user again has interactive control. I think this is analogous.

Any updates on this? I started a Gatsby project today and was disappointed to see that a). this is the only a11y error I have on this project, and b). this issue is still open with no response from the developers.

Perhaps this article by @marcysutton can be useful: https://www.gatsbyjs.org/blog/2019-07-11-user-testing-accessible-client-routing/
She's done user research on accessible routing with screen reader users, low vision-, keyboard-, voice control- and switch users

I'm also having this issue! Would be very nice to fix it to make our site more accessability


Broken link to mariadb mirror

Describe the bug
The installation of the docker files fails due to the link of the mariadb mirror being broken

To Reproduce
Steps to reproduce the behavior:

Follow clone instructions for the repository
Run ./run.sh

System Information

OS: macOS Sequoia 15.1
Kernel version: Darwin 24.1.0
System architecture: x86_64
Airflow version used: v2.10.1 && v.2.9.2
aws-mwaa-docker-images commit ID: 370be7a (https://github.com/aws/amazon-mwaa-docker-images/commit/370be7a3b2d8671822095b6f56cb8c3cf9913e39#diff-5dee78965fae3480487338f55a7ab31185be3d4fc0f50de0be2bc931e7dbfff5R14)

Expected behavior
To continue the installation without problems

Screenshots

Docker error

Mirror with missing distribution

Additional context
Problem was solved locally by modifying <AirflowVersion>/Dockerfile.base.j2:20 from
ARG MARIADB_DOWNLOAD_BASE_URL=https://mirror.mariadb.org/yum/11.1/fedora38-

to
ARG MARIADB_DOWNLOAD_BASE_URL=https://archive.mariadb.org/yum/11.1/fedora38-

The mariadb version was updated here:
https://github.com/aws/amazon-mwaa-docker-images/pull/183
Please let us know if you have any other issues.