FastlaneRunner lane swiftServerPort 2000 Killed: 9

New Issue Checklist

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

Issue Description

I use Fastlane with swift, on Mac intel and m1, on this both machines I have the same failure
bundle exec fastlane updateProvisioning
bundle      fastlane updateProvisioning
[✔] 🚀
[07:52:36]: loading manifest: /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/swift/upgrade_manifest.json
[07:52:36]: FastlaneSwiftRunner project is up-to-date
[07:52:36]: $ ./fastlane/FastlaneRunner lane updateProvisioning swiftServerPort 2000 > /dev/null
[07:52:36]: ▸ sh: line 1:  2110 Killed: 9               ./fastlane/FastlaneRunner lane updateProvisioning swiftServerPort 2000 > /dev/null
#<Thread:0x0000000107e7a510 /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/swift_lane_manager.rb:96 run> terminated with exception (report_on_exception is true):
/Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': Exit status of command './fastlane/FastlaneRunner lane updateProvisioning swiftServerPort 2000 > /dev/null' was 137 instead of 0. (FastlaneCore::Interface::FastlaneShellError)
sh: line 1:  2110 Killed: 9               ./fastlane/FastlaneRunner lane updateProvisioning swiftServerPort 2000 > /dev/null
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/helper/sh_helper.rb:80:in `sh_control_output'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/helper/sh_helper.rb:12:in `sh'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/swift_lane_manager.rb:97:in `block in cruise_swift_lane_in_thread'
#<Thread:0x0000000107e8aeb0 /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/swift_lane_manager.rb:220 run> terminated with exception (report_on_exception is true):
/Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in `user_error!': fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down (FastlaneCore::Interface::FastlaneError)
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:151:in `rescue in listen'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:146:in `listen'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:38:in `start'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/swift_lane_manager.rb:223:in `block in start_socket_thread'
/Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:148:in `accept': execution expired (Timeout::Error)
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:148:in `block in listen'
	from /Users/amine/.rvm/rubies/ruby-3.0.1/lib/ruby/3.0.0/timeout.rb:112:in `timeout'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:147:in `listen'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/server/socket_server.rb:38:in `start'
	from /Users/amine/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/gems/fastlane-2.185.1/fastlane/lib/fastlane/swift_lane_manager.rb:223:in `block in start_socket_thread'
+-----------+--------------------+
|          Lane Context          |
+-----------+--------------------+
| LANE_NAME | updateProvisioning |
+-----------+--------------------+
[07:52:41]: fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down
[07:52:41]: fastlane finished with errors

[!] fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down

Command executed

I just excuse my lane `bundle exec fastlane updateProvisioning
Complete output when running fastlane, including the stack trace and command used
✅ fastlane environment ✅
Stack

Key
Value

OS
11.4

Ruby
3.0.1

Bundler?
true

Git
git version 2.32.0

Installation Source
~/Projects/ios/intech-consulting-match/.vendor/ruby/3.0.0/bin/fastlane

Host
macOS 11.4 (20F71)

Ruby Lib Dir
~/.rvm/rubies/ruby-3.0.1/lib

OpenSSL Version
OpenSSL 1.1.1k  25 Mar 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
12.5

Swift Version
5.4

System Locale

Variable
Value

LANG
fr_FR.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile.swift`
// This file contains the fastlane.tools configuration
// You can find the documentation at https://docs.fastlane.tools
//
// For a list of all available actions, check out
//
//     https://docs.fastlane.tools/actions
//

import Foundation

func environment(get key: String) -> String {
	ProcessInfo.processInfo.environment[key] ?? ""
}

class Fastfile: LaneFile {
	private lazy var s3Region: String = { environment(get: "S3_REGION") }()
	private lazy var s3AccessKey: String = { environment(get: "S3_ACCESS_KEY") }()
	private lazy var s3SecretAccessKey: String = { environment(get: "S3_SECRET_ACCESS_KEY") }()
	private lazy var s3Bucket: String = { environment(get: "S3_BUCKET") }()

	private func getAppIdentifiers(withOptions options:[String: String]?) -> [Constants.AppIdentifiers] {
		guard let options = options,
			  let app = options[Constants.appIdentifiersOption],
			  let appIdentifier =  Constants.AppIdentifiers(rawValue: app) else { return Constants.AppIdentifiers.allCases }
		return [appIdentifier]
	}

	private func getOutputPath(withOptions options:[String: String]?) -> String? {
		guard let options = options,
			  let outputPath = options[Constants.outputPathOption] else { return nil }
		return outputPath
	}

	func fetchProvisioningLane(withOptions options:[String: String]?) {
		desc("Fetch provisiong profiles")

		let appIdentifiers = getAppIdentifiers(withOptions: options)
		let outputPath = getOutputPath(withOptions: options)

		appIdentifiers.forEach { key in
			key.appIdentifiers.forEach { appIdentifier in
				appIdentifier.types.forEach { type in
					appIdentifier.platforms.forEach { platform in
						match(
							type: type.rawValue,
							readonly: true,
							appIdentifier: appIdentifier.identifiers,
							username: .userDefined(appleID),
							teamId: .userDefined(teamID),
							teamName: .userDefined(key.rawValue),
							storageMode: Constants.storageMode,
							s3Region: .userDefined(s3Region),
							s3AccessKey: .userDefined(s3AccessKey),
							s3SecretAccessKey: .userDefined(s3SecretAccessKey),
							s3Bucket: .userDefined(key.s3Bucket ?? s3Bucket),
							s3ObjectPrefix: .userDefined(key.s3ObjectPrefix),
							platform: platform.rawValue,
							deriveCatalystAppIdentifier: .userDefined(appIdentifier.includeMacCatalyst),
							outputPath: .userDefined(outputPath)
						)
					}
				}
			}
		}
	}

	// fastlane [lane] key:value key2:value2
	func updateProvisioningLane(withOptions options:[String: String]?) {
		desc("Update provisiong profiles")

		let appIdentifiers = getAppIdentifiers(withOptions: options)
		let outputPath = getOutputPath(withOptions: options)

		appIdentifiers.forEach { key in
			key.appIdentifiers.forEach { appIdentifier in
				appIdentifier.types.forEach { type in
					appIdentifier.platforms.forEach { platform in
						match(
							type: type.rawValue,
							readonly: false,
							generateAppleCerts: false,
							appIdentifier: appIdentifier.identifiers,
							username: .userDefined(appleID),
							teamId: .userDefined(teamID),
							teamName: .userDefined(key.rawValue),
							storageMode: Constants.storageMode,
							s3Region: .userDefined(s3Region),
							s3AccessKey: .userDefined(s3AccessKey),
							s3SecretAccessKey: .userDefined(s3SecretAccessKey),
							s3Bucket: .userDefined(key.s3Bucket ?? s3Bucket),
							s3ObjectPrefix: .userDefined(key.s3ObjectPrefix),
							platform: platform.rawValue,
							deriveCatalystAppIdentifier: .userDefined(appIdentifier.includeMacCatalyst),
							outputPath: .userDefined(outputPath)
						)
					}
				}
			}
		}
	}

	func nukeDevelopmentLane(withOptions options:[String: String]?) {
		desc("Clear developement certificates & provioning profiles")

		let appIdentifiers = getAppIdentifiers(withOptions: options)

		appIdentifiers.forEach { key in
			key.appIdentifiers.forEach { appIdentifier in
				appIdentifier.types.forEach { type in
					matchNuke(
						type: type.rawValue,
						appIdentifier: appIdentifier.identifiers,
						username: .userDefined(appleID),
						teamId: .userDefined(teamID),
						storageMode: Constants.storageMode,
						gitUrl: "",
						s3Region: .userDefined(s3Region),
						s3AccessKey: .userDefined(s3AccessKey),
						s3SecretAccessKey: .userDefined(s3SecretAccessKey),
						s3Bucket: .userDefined(key.s3Bucket ?? s3Bucket),
						s3ObjectPrefix: .userDefined(key.s3ObjectPrefix)
					)
				}
			}
		}
	}
}

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.185.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.5.0

pathname
0.1.0

tsort
0.1.0

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.7.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.1

aws-partitions
1.469.0

aws-sigv4
1.2.3

jmespath
1.4.0

aws-sdk-core
3.114.3

aws-sdk-kms
1.44.0

aws-sdk-s3
1.96.1

babosa
1.0.4

bundler
2.2.15

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.2

excon
0.82.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-net_http
1.0.1

faraday-net_http_persistent
1.1.0

multipart-post
2.0.0

ruby2_keywords
0.0.4

faraday
1.4.2

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.4

gh_inspector
1.1.3

jwt
2.2.3

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.15.0

googleauth
0.16.2

httpclient
2.8.3

mini_mime
1.1.0

trailblazer-option
0.1.1

uber
0.1.0

representable
3.1.1

retriable
3.1.2

rexml
3.2.5

webrick
1.7.0

google-apis-core
0.3.0

google-apis-androidpublisher_v3
0.6.0

google-apis-playcustomapp_v1
0.3.0

google-apis-iamcredentials_v1
0.4.0

google-apis-storage_v1
0.4.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

google-cloud-storage
1.31.1

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-06-21

I have seen this report before but I'm unable to reproduce it because it seems to be related to M1 chip.

Is there any news on this? we are having a similar issue with M1 chips

Still don't have an M1 machine to fix this

This can be closed as duplicate from #18502.
Both will be fixed when PR https://github.com/fastlane/fastlane/pull/19555 gets merged, which will happen soon.

Hello, theoretically this issue has been solved in #19555 and should be available in fastlane 2.204.0, but I'm still reproducing the issue in my M1 laptop:
[09:51:13]: $ set -o pipefail && xcodebuild -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj -destination 'generic/platform=macOS' build | tee /Users/roisg/Library/Logs/gym/App-FastlaneRunner.log | xcpretty
[09:51:17]: FastlaneSwiftRunner project is up-to-date
[09:51:17]: $ ./fastlane/FastlaneRunner lane beta swiftServerPort 2000 > /dev/null
[09:51:17]: ▸ sh: line 1: 42822 Killed: 9               ./fastlane/FastlaneRunner lane beta swiftServerPort 2000 > /dev/null
#<Thread:0x00000001072f2a58 /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:99 run> terminated with exception (report_on_exception is true):
/opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in shell_error!': Exit status of command './fastlane/FastlaneRunner lane beta swiftServerPort 2000 > /dev/null' was 137 instead of 0. (FastlaneCore::Interface::FastlaneShellError) sh: line 1: 42822 Killed: 9               ./fastlane/FastlaneRunner lane beta swiftServerPort 2000 > /dev/null 	from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/helper/sh_helper.rb:80:in sh_control_output' 	from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/helper/sh_helper.rb:12:in sh'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:104:in block in cruise_swift_lane_in_thread' #<Thread:0x00000001072d94b8 /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:228 run> terminated with exception (report_on_exception is true): /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down (FastlaneCore::Interface::FastlaneError)
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' 	from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:151:in rescue in listen'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:146:in listen' 	from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in block in start_socket_thread' /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in accept': execution expired (Timeout::Error)
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in block in listen' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/timeout.rb:112:in timeout'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:147:in listen' 	from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /opt/homebrew/Cellar/fastlane/2.204.1/libexec/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in `block in start_socket_thread'
Anyone has been able to make it work now with the new version? Is there anything else that I should be updating?

Looks like the FastlaneRunner Xcode project is still not updated.
Could you provide logs executing bundle exec fastlane?
It should be updated in that moment, adding a changes that will sign the binary, which is the reason it's still killed.

@kikeenrique I'm not sure if this can be related, but since I upgraded to 2.204.1 (also in 1.204.0) I keep seeing the message:
It looks like your FastlaneSwiftRunner project is not up-to-date
f you don't update it, fastlane could fail
We can try to automatically update it for you, usually this works 🎈 🐐
Should we try to upgrade just your FastlaneSwiftRunner project? (y/n)
Even after I already clicked y key and it said it was updated.
I can only reproduce this locally, it's not happening in our CircleCI jobs.

@rserentill could you provide a bundle exec fastlane --verbose or whatever command you use adding the verbose flag?
It could be an upgrade check not working as expected.

@kikeenrique Sure, here is the logs until the message appears. Let me know if you require the logs after it also:
[✔] 🚀
INFO [2022-02-03 10:48:55.82]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/abstract_module_frameworks.rb'.
INFO [2022-02-03 10:48:55.82]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/set_localization_strings.rb'.
INFO [2022-02-03 10:48:55.82]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/generate_app_icon_assets.rb'.
INFO [2022-02-03 10:48:55.82]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/set_localized_changelog.rb'.
INFO [2022-02-03 10:48:55.83]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/upload_ipa_to_s3.rb'.
INFO [2022-02-03 10:48:55.83]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/erase_module_frameworks.rb'.
INFO [2022-02-03 10:48:55.83]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/abstract.rb'.
INFO [2022-02-03 10:48:55.83]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/embed_module_frameworks.rb'.
INFO [2022-02-03 10:48:55.83]: Successfully loaded custom action '/Users/roger/Developer/iOS/newsstand/app/fastlane/actions/get_unlocalized_keys.rb'.
DEBUG [2022-02-03 10:48:55.83]: Checking if there are any plugins that should be loaded...
INFO [2022-02-03 10:48:56.09]: loading manifest: /Users/roger/.rvm/gems/ruby-2.6.5/gems/fastlane-2.204.1/fastlane/swift/upgrade_manifest.json
DEBUG [2022-02-03 10:48:56.21]: No missing groups found, so we don't need to worry about adding new groups
DEBUG [2022-02-03 10:48:56.21]: Actions.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 10:48:56.21]: Fastlane.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.150/0.9.150
DEBUG [2022-02-03 10:48:56.21]: DeliverfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.97/0.9.97
DEBUG [2022-02-03 10:48:56.22]: GymfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.100/0.9.100
DEBUG [2022-02-03 10:48:56.22]: MatchfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.94/0.9.94
DEBUG [2022-02-03 10:48:56.22]: Plugins.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 10:48:56.22]: PrecheckfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.93/0.9.93
DEBUG [2022-02-03 10:48:56.22]: ScanfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.105/0.9.105
DEBUG [2022-02-03 10:48:56.22]: ScreengrabfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.95/0.9.95
DEBUG [2022-02-03 10:48:56.22]: SnapshotfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.89/0.9.89
DEBUG [2022-02-03 10:48:56.22]: LaneFileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: ControlCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: RubyCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: RubyCommandable.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: Runner.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: SocketClient.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: SocketClientDelegateProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: SocketResponse.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: main.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.23]: ArgumentProcessor.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.24]: RunnerArgument.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 10:48:56.24]: FastlaneRunner project has been updated and can be written back to disk
INFO [2022-02-03 10:48:56.24]: It looks like your FastlaneSwiftRunner project is not up-to-date
INFO [2022-02-03 10:48:56.24]: If you don't update it, fastlane could fail
INFO [2022-02-03 10:48:56.24]: We can try to automatically update it for you, usually this works 🎈 🐐
[2022-02-03 10:48:56.24]: Should we try to upgrade just your FastlaneSwiftRunner project? (y/n)

These are my logs after executing bundle exec fastlane --verbose:
[✔] 🚀
DEBUG [2022-02-03 11:01:56.30]: Checking if there are any plugins that should be loaded...
objc[46897]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77130) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1082742c8). One of the two will be used. Which one is undefined.
objc[46897]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77180) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x108274318). One of the two will be used. Which one is undefined.
INFO [2022-02-03 11:01:56.39]: loading manifest: /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/swift/upgrade_manifest.json
DEBUG [2022-02-03 11:01:56.42]: No missing groups found, so we don't need to worry about adding new groups
DEBUG [2022-02-03 11:01:56.42]: Actions.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 11:01:56.42]: Fastlane.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.150/0.9.150
DEBUG [2022-02-03 11:01:56.42]: DeliverfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.97/0.9.97
DEBUG [2022-02-03 11:01:56.42]: GymfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.100/0.9.100
DEBUG [2022-02-03 11:01:56.42]: MatchfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.94/0.9.94
DEBUG [2022-02-03 11:01:56.42]: Plugins.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 11:01:56.42]: PrecheckfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.93/0.9.93
DEBUG [2022-02-03 11:01:56.42]: ScanfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.105/0.9.105
DEBUG [2022-02-03 11:01:56.42]: ScreengrabfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.95/0.9.95
DEBUG [2022-02-03 11:01:56.42]: SnapshotfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.89/0.9.89
DEBUG [2022-02-03 11:01:56.42]: LaneFileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: ControlCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: RubyCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: RubyCommandable.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: Runner.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: SocketClient.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: SocketClientDelegateProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: SocketResponse.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: main.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: ArgumentProcessor.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: RunnerArgument.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:01:56.42]: FastlaneRunner project has been updated and can be written back to disk
INFO [2022-02-03 11:01:56.42]: It looks like your FastlaneSwiftRunner project is not up-to-date
INFO [2022-02-03 11:01:56.42]: If you don't update it, fastlane could fail
INFO [2022-02-03 11:01:56.42]: We can try to automatically update it for you, usually this works 🎈 🐐
[2022-02-03 11:01:56.42]: Should we try to upgrade just your FastlaneSwiftRunner project? (y/n)
y
DEBUG [2022-02-03 11:02:00.70]: No missing groups found, so we don't need to worry about adding new groups
DEBUG [2022-02-03 11:02:00.70]: Actions.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 11:02:00.70]: Fastlane.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.150/0.9.150
DEBUG [2022-02-03 11:02:00.70]: DeliverfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.97/0.9.97
DEBUG [2022-02-03 11:02:00.70]: GymfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.100/0.9.100
DEBUG [2022-02-03 11:02:00.70]: MatchfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.94/0.9.94
DEBUG [2022-02-03 11:02:00.70]: Plugins.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.56/0.9.56
DEBUG [2022-02-03 11:02:00.70]: PrecheckfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.93/0.9.93
DEBUG [2022-02-03 11:02:00.70]: ScanfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.105/0.9.105
DEBUG [2022-02-03 11:02:00.70]: ScreengrabfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.95/0.9.95
DEBUG [2022-02-03 11:02:00.70]: SnapshotfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.89/0.9.89
DEBUG [2022-02-03 11:02:00.70]: LaneFileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: ControlCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: RubyCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: RubyCommandable.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: Runner.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: SocketClient.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: SocketClientDelegateProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: SocketResponse.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: main.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: ArgumentProcessor.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: RunnerArgument.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2022-02-03 11:02:00.70]: FastlaneRunner project has been updated and can be written back to disk
DEBUG [2022-02-03 11:02:00.70]: FastlaneRunner project changes have been stored
INFO [2022-02-03 11:02:00.71]: Updated your FastlaneSwiftRunner project with the newest runner code
DEBUG [2022-02-03 11:02:00.71]: Building FastlaneSwiftRunner
WARN [2022-02-03 11:02:00.73]: Resolving Swift Package Manager dependencies...
INFO [2022-02-03 11:02:00.73]: $ xcodebuild -resolvePackageDependencies -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
INFO [2022-02-03 11:02:00.80]: ▸ objc[46899]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77130) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1086ac2c8). One of the two will be used. Which one is undefined.
INFO [2022-02-03 11:02:00.80]: ▸ objc[46899]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77180) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1086ac318). One of the two will be used. Which one is undefined.
INFO [2022-02-03 11:02:01.07]: ▸ Command line invocation:
INFO [2022-02-03 11:02:01.07]: ▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
INFO [2022-02-03 11:02:01.07]: ▸ User defaults from command line:
INFO [2022-02-03 11:02:01.07]: ▸     IDEPackageSupportUseBuiltinSCM = YES
INFO [2022-02-03 11:02:01.35]: ▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:
INFO [2022-02-03 11:02:01.35]: ▸ { platform:macOS, arch:arm64, id:00006000-001C30D80262801E }
INFO [2022-02-03 11:02:01.35]: ▸ { platform:macOS, arch:x86_64, id:00006000-001C30D80262801E }
INFO [2022-02-03 11:02:01.35]: ▸ { platform:macOS, name:Any Mac }
INFO [2022-02-03 11:02:01.35]: ▸ resolved source packages:
INFO [2022-02-03 11:02:01.35]: $ xcodebuild -showBuildSettings -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
objc[46905]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77130) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1084ac2c8). One of the two will be used. Which one is undefined.
objc[46905]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77180) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1084ac318). One of the two will be used. Which one is undefined.
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006000-001C30D80262801E }
{ platform:macOS, arch:x86_64, id:00006000-001C30D80262801E }
{ platform:macOS, name:Any Mac }
DEBUG [2022-02-03 11:02:02.07]: Parsing project file '/Users/roisg/Dev/workspaces/wisk-ios/Wisk/fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj' to find selected provisioning profiles
DEBUG [2022-02-03 11:02:02.07]: Finding provision profiles for 'Release'
DEBUG [2022-02-03 11:02:02.07]: Merging provisioning profile mappings
DEBUG [2022-02-03 11:02:02.07]: -------------------------------------
DEBUG [2022-02-03 11:02:02.07]: Primary provisioning profile mapping:
DEBUG [2022-02-03 11:02:02.07]: {}
DEBUG [2022-02-03 11:02:02.07]: Secondary provisioning profile mapping:
DEBUG [2022-02-03 11:02:02.07]: {}
DEBUG [2022-02-03 11:02:02.07]: Resulting in the following mapping:
DEBUG [2022-02-03 11:02:02.07]: {}
INFO [2022-02-03 11:02:02.08]: $ set -o pipefail && xcodebuild -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj -destination 'generic/platform=macOS' build | tee /Users/roisg/Library/Logs/gym/App-FastlaneRunner.log | xcpretty
INFO [2022-02-03 11:02:02.15]: ▸ objc[46919]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77130) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x107f002c8). One of the two will be used. Which one is undefined.
INFO [2022-02-03 11:02:02.15]: ▸ objc[46919]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x1e0c77180) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x107f00318). One of the two will be used. Which one is undefined.
INFO [2022-02-03 11:02:02.83]: ▸ Running script 'Run Script'
INFO [2022-02-03 11:02:02.84]: ▸ Build Succeeded
DEBUG [2022-02-03 11:02:02.85]: Checking for new user-provided tool configuration files
INFO [2022-02-03 11:02:02.85]: FastlaneSwiftRunner project is up-to-date
DEBUG [2022-02-03 11:02:02.85]: Waiting for 5 seconds for a connection from FastlaneRunner
INFO [2022-02-03 11:02:03.11]: $ ./fastlane/FastlaneRunner lane  logMode verbose swiftServerPort 2000
#<Thread:0x0000000101ca2040@/Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:99 run> terminated with exception (report_on_exception is true):
/Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in shell_error!': Exit status of command './fastlane/FastlaneRunner lane  logMode verbose swiftServerPort 2000' was  instead of 0. (FastlaneCore::Interface::FastlaneShellError) 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/helper/sh_helper.rb:80:in sh_control_output' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/helper/sh_helper.rb:12:in sh'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:101:in block in cruise_swift_lane_in_thread' #<Thread:0x0000000101c90430@/Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:228 run> terminated with exception (report_on_exception is true): /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down (FastlaneCore::Interface::FastlaneError)
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:151:in rescue in listen'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:146:in listen' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in block in start_socket_thread' /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in accept': execution expired (Timeout::Error)
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in block in listen' 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/timeout.rb:108:in timeout'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:147:in listen' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in block in start_socket_thread' WARN [2022-02-03 11:02:07.86]: Lane Context: INFO [2022-02-03 11:02:07.86]: {:LANE_NAME=>nil} ERROR [2022-02-03 11:02:07.86]: fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down ERROR [2022-02-03 11:02:07.87]: fastlane finished with errors bundler: failed to load command: fastlane (/Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/bin/fastlane) /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': [!] fastlane failed to receive a connection from the FastlaneRunner binary after 5 seconds, shutting down (FastlaneCore::Interface::FastlaneError)
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:151:in rescue in listen'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:146:in listen' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in block in start_socket_thread' /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in accept': execution expired (Timeout::Error)
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:148:in block in listen' 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/timeout.rb:108:in timeout'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:147:in listen' 	from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/server/socket_server.rb:38:in start'
from /Users/roisg/Dev/workspaces/wisk-ios/Wisk/vendor/bundle/ruby/2.6.0/gems/fastlane-2.204.1/fastlane/lib/fastlane/swift_lane_manager.rb:231:in `block in start_socket_thread'

I think I now why it's always asking for upgrade. I would consider a PR soon.
It's not checking properly if it needs to upgrade something inside FastlaneSwiftRunner.xcodeproj, even if it's properly upgraded. It's annoying but it should work as expected.
@roisg Can you see a build phase in FastlaneSwiftRunner.xcodeproj named FastlaneRunnerCopySigned?

@kikeenrique yes, I see that phase:

Hm, it's weird, the new phase is there, but the old, "Run Script" seems to be still there.
Maybe that phase is not exactly as expected by the upgrader and was not removed.
If that phase is a cd and then a cp, you can remove it manually.
The other change you could verify is related to signing.

Signed binaries in macOS can give problems due to caching, so other option is try removing the binary manually rm fastlane/FastlaneRunner and rebuilding.

I have just found out that just after restarting my laptop, the fastlane build works perfectly with the 2.204.2 version. Now, if the build fails, or even if it success, re-running the same fastlane build will throw the error:
Exit status of command './fastlane/FastlaneRunner lane betaAndStore swiftServerPort 2000 > /dev/null' was 137 instead of 0. (FastlaneCore::Interface::FastlaneShellError) sh: line 1: 18736 Killed: 9               ./fastlane/FastlaneRunner lane betaAndStore swiftServerPort 2000 > /dev/null
And it will be thrown forever until I restart my computer again. So it seems something is not being properly freed between executions?

That's what I meant with Signed binaries in macOS can give problems due to caching. I've read in an apple forums about this problems, check https://developer.apple.com/forums/thread/669145 or https://developer.apple.com/documentation/security/updating_mac_software.
But, the Code Sign on copy shall prevent these problems, at least I didn't manage to reproduce them again.
Did you remove the build phase "Run Script"?
That phases uses cp, which doesn't behave as expected with signed binaries, and may be the root of the problem.

Yes, @kikeenrique, you're right. After removing the "run script" phase that was doing a cp, I can run the fastlane build multiple times without getting the error.


Font.Color Property (PowerPoint)

Returns the color of the current Font object. Change [Read-only] to Read/Write.

Corrected. Will publish update today.


move toMap outside of the Polyfill class

toMap contains logic for displaying polyfill meta on the documentation site, which is not good. We should keep Polyfill wrapper class as simple as possible and move the logic out to somewhere else, possibly the controller for the webview?


[Bug] Helm times out

What are you really trying to do?
I want to install Temporal using helm. I've tried with an EKS cluster with either 1, 2 or 3 nodes.

Minimal Reproduction
~/Documents/Code/temporal/helm-charts > helm install temporaltest . --timeout 900s --debug
install.go:192: [debug] Original chart version: ""
install.go:209: [debug] CHART PATH: /Users/xxx/Documents/Code/temporal/helm-charts
client.go:128: [debug] creating 57 resource(s)
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job temporaltest-es-index-setup with timeout of 15m0s
client.go:568: [debug] Add/Modify event for temporaltest-es-index-setup: ADDED
client.go:607: [debug] temporaltest-es-index-setup: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:310: [debug] Starting delete for "temporaltest-es-index-setup" Job
Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condition
helm.go:84: [debug] failed post-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:141
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.5.0/command.go:872
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.5.0/command.go:990
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.5.0/command.go:918
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:250
runtime.goexit
runtime/asm_amd64.s:1594
Environment/Versions

OS and processor: Mac Intel
Temporal Version: as defined in the latest Helm chart
Are you using Docker or Kubernetes or building Temporal from source? AWS EKS. Cluster created with eksctl

Additional context
My EKS cluster has 3 subnets with /27 IP addresses. I see that EKS is super IP hungry and after running Helm there are only 4-5 IPs left for each subnet, at which point Helm stalls and timeouts.

Might be related: https://github.com/temporalio/helm-charts/pull/342
Please try again.

Might be related: #342 Please try again.

This works now. Thanks!


Virtus cannot be used in Modules

I wanted to try replacing parameters with Virtus. One of the features that Parameters has is being able to be used in Mixin modules, so that when the Mixin is included the parameters are added to the class. Virtus appears to only work with Classes.

module Test
  include Virtus

  attribute :name, String
end

NoMethodError: undefined method `superclass' for Test:Module
    /home/hal/.rvm/gems/ruby-1.9.3-p0/gems/virtus-0.0.9/lib/virtus/class_methods.rb:71:in `attributes'
    /home/hal/.rvm/gems/ruby-1.9.3-p0/gems/virtus-0.0.9/lib/virtus/class_methods.rb:115:in `virtus_add_attribute'
    /home/hal/.rvm/gems/ruby-1.9.3-p0/gems/virtus-0.0.9/lib/virtus/class_methods.rb:48:in `attribute'
    (ripl):7:in `'

Ah ha, it does not support defining attributes on Objects (see #28).

As discussed in #6, something like ActiveSupport::Concern or https://github.com/rubyworks/facets/blob/master/lib/core/facets/module/class_extend.rb will be necessary to allow Virtus to work in modules, because of the combination of instance and class methods to be propagated.
This is probably obvious to all parties here; I mainly wanted to collect these notes on this issue in the event someone wants to follow up and implement this in Virtus.

@postmodern I'm closing this one becase a) it would need too much work b) it can be solved via module + included hook, see example below
module AddressAttributes
  def self.included(model)
    model.attribute :street, String
    model.attribute :zipcode, String
  end
end

class User
  include Virtus
  include AddressAttributes

  attribute :name, String
end

user = User.new :name => 'John', :street => 'Foo Bar Strasse', :zipcode => '12345'


[BUG] uui-color-area: Sometimes resets coordinates when selecting a color

[...] in inline color picker, it seems the handle is flickering while dragging, and dragging to bottom, the handle shortly jump to bottom left corner, which doesn't happen in the color area itself.
But it seems also to happen on uui.umbraco.com so probably another issue somewhere.
Originally posted by @bjarnef in https://github.com/umbraco/Umbraco.UI/issues/532#issuecomment-1638134383

The issue isn't specific in inline mode, but seems to happen in color picker. It may be a rounding issue.

The issue isn't specific in inline mode, but seems to happen in color picker. It may be a rounding issue.

Ok, I updated the title. The more we know the better. Anyway, I have marked this as up-for-grabs if you or anyone else would like to take a look at it, or maybe even just figure out a surefire way to reproduce it.

@iOvergaard it seems to be same issue when pointer events in color picker.
In color area it works smooth, in color picker dragging the handle is flickering a bit and dragging to bottom (black), the handle shortly jump to bottom left.
https://github.com/umbraco/Umbraco.UI/assets/2919859/fff543b2-5e16-430b-8144-30c2c151a146

@bjarnef probably due to the d.ts caching in Typescript, because we build incrementally. If you run npm run clean first that might fix things, otherwise go into packages/uui-base/lib and delete the .d.ts files in there and it should work (if the export exists in the source file).

When dragging around in color picker, the gridHandleX sometimes return zero and thus jump to left, although it shouldn't

It seems something may override/reset the current saturation while while dragging the handle.

@iOvergaard the gridHandleX is changed in value set, at parsed.toHsl(), where s returns 0.
It seems to be something similar with hue value.
https://github.com/umbraco/Umbraco.UI/pull/536


Refact graphics

Description of change

Current Graphics implementation doesn't support expandability as fact.
GraphicsGeometry and Geometry can't be extending from similar class because imports from internal utils is used, outside of PIXI namespaces.
Next problem - very heavy methods. They cannot be overridden without code duplication.
Looks this:
https://github.com/pixijs/pixi.js/blob/dev/packages/graphics/src/GraphicsGeometry.js#L549
https://github.com/pixijs/pixi.js/blob/dev/packages/graphics/src/GraphicsGeometry.js#L475
https://github.com/pixijs/pixi.js/blob/dev/packages/graphics/src/GraphicsGeometry.js#L25
Example (cannot be created without this refract) :
https://www.pixiplayground.com/#/edit/NWa_z1hMuF92Dwmyb3AEl
Pre-Merge Checklist

[x] Tests and/or benchmarks are included
[x] Documentation is changed or added
[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Codecov Report

Merging #6077 into dev will decrease coverage by 0.27%.
The diff coverage is 68.13%.

@@            Coverage Diff             @@
##              dev    #6077      +/-   ##
==========================================
- Coverage   71.04%   70.76%   -0.28%
==========================================
  Files         208      212       +4
  Lines       10624    10691      +67
==========================================
+ Hits         7548     7566      +18
- Misses       3076     3125      +49

Impacted Files
Coverage Δ

packages/graphics/src/Graphics.js
73.69% <ø> (ø)
:arrow_up:

packages/graphics/src/utils/index.js
100% <100%> (ø)

packages/graphics/src/utils/BatchPart.js
100% <100%> (ø)

packages/graphics/src/GraphicsGeometry.js
69.94% <56.71%> (-2.44%)
:arrow_down:

packages/graphics/src/utils/bezierCurveTo.js
0% <0%> (ø)

packages/graphics/src/utils/buildComplexPoly.js
0% <0%> (ø)

packages/ticker/src/Ticker.js
87.59% <0%> (+0.77%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update add2870...21c4236.  Will get round to it as soon as I can 👍

Ideally, yes, but we dont have visual tests in this repo.

So, VT is passed normal.
http://pixijs.io/v5-render-tests/?refact-graphics-geometry

I’m actually not talking just about rendering. Exercising the APIs is a good baseline. Just the basics. Part of this refactor involves creating new protected methods and making it easier to extend. Would love to see tests for that.


cdecl: 16.3 -> 16.4.1

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Please update the PR title and commit log message. The name of the package is cdecl, not cdelc. That's the reason why there are no CI checks.

typo


Default groups do not appear in Views

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 0.23.0
Python release (python3 --version): Python 3.4.2
Component/platform:
Description of problem: When the default groups such as "group.all_automations" or "group.all_devices" are used as the entities in a view, the view does not show the groups in the view. No errors or warnings appear in the logs.
Expected: When a default group is added to a view, it should show up in the view.
Problem-relevant configuration.yaml entries and steps to reproduce:
group:
  test:
    view: yes
    name: Test
    entities: group.all_automations, group.all_devices

Traceback (if applicable):
Additional info: This issue is mentioned and reproduced in the comments for https://github.com/home-assistant/home-assistant/pull/3664

The issue persists in 0.32.2
I am unable to add group.all_automations to any view.

Hi,
Have you tried to add the following in customization section:
group.all_automations
  hidden: false

@Molodax Indeed....hidden: false works. Did not realize that the default attribute for group.all_automations is true.

Default groups are hidden by design


⚠ Secret Website 2 has degraded performance

In d1ee824, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 15739 ms

Resolved: Secret Website 2 performance has improved in 9d75e10.


Gmail: links aren't open anywhere unless right-clicked (--internal-urls does not help)

Homework

[x] I looked at nativefier --help and https://github.com/jiahaog/nativefier/blob/master/docs/api.md
[x] I searched existing issues, open & closed. Yes, my bug is new.

Actually, similar bug report is open in nativefier-icons, but I'm not sure it's the right place to be: https://github.com/jiahaog/nativefier-icons/issues/45

[x] I'm using the latest version available at https://github.com/jiahaog/nativefier/releases

Bug description
Links in Gmail aren't open anywhere, internal-urls does not help.
Steps to reproduce
nativefier https://google.com/mail/ -i 200px-Gmail_Icon.png --user-agent 'Chrome/84' --internal-urls "mail.google.*?"

Preparing Electron app...

Converting icons...

Packaging... This will take a few seconds, maybe minutes if the requested Electron isn't cached yet...
Packaging app for platform darwin x64 using electron v9.2.0

Finalizing build...
App built to .../Gmail-darwin-x64

Expected behavior
When I left-click any external link inside the app, it should open a default browser with that link.
Actual behavior
Nothing. Left click on a link does nothing.
If I right-click and select 'Open Link in Default Browser' - everything works as expected.
Debug info
There are no relevant things to provide, console is empty, build is successful, no error messages anywhere.
Context

Nativefier: 9.2.0
Node.js: v14.4.0
Npm: 6.14.4
OS: MacOS
Is it a regression? Possibly, I think previously it worked, but I don't remember the version.

just confirming that, 10 months later, this bug is still alive and spreading sadness 😢

One piece of information that might help:
Here on Linux, when clicking a link in nativefied Gmail, I get an alert saying:

Grrr! A popup blocker may be preventing the application from opening the page. If you have a popup blocker, try disabling it to open the window.

We don't provide a way to allow the popup, and in a browser, this is accompanied by an infobar letting you enable popups, but we don't have one.

For added info, getting the issue with Google Calendar and Asana, but not on all links. Very possible it's related to some being straight  versus popups. Will try to investigate soon.

I believe we saw a similar issue here: https://github.com/nativefier/nativefier/issues/1193
The workaround there was to use a different user agent. Try rebuilding the app with --user-agent edge as this seems to have worked in the other ticket.

If this continues, we can dig deeper, but really boils down to something along the lines of what we fixed in https://github.com/nativefier/nativefier/issues/1197. Namely in these instances, Gmail is not trying to actually open a page, but rather it is trying to open and about:blank window and then inject JavaScript into it that will then cause it to go to the page. Which Electron prevents by default.

Some progress following instructions above, a few new bumps:
Gmail
nativefier "https://mail.google.com/"   --internal-urls "mail.google.*?" --single-instance --user-agent "edge"  --name "Gmail"
Looks like most links are working now, but are loading in a new tab within electron, even though they are external (confirmed by "copy link"). Something I'm doing wrong with --internal-urls ?
Gcal
nativefier "https://calendar.google.com"   --internal-urls "calendar.google.*?" --single-instance --user-agent "edge"  --name "Gcal"
Google Meet links are working (but loading in a different tab even though it's not an internal URL https://meet.google.com/...)
However no link within the event descriptions are working (unless ask to "open in external browser"). Note that those links are all wrapped in https://www.google.com/url?q=https://THE-ACTUAL-URL, which might hint at something weird google is doing here again (popup + inject)

Same problem here. Is there any workaround for Google popup + inject / redirect?

Would unloading whatever event handler Google has installed and replace it work here?

Even command-clicking a link in Gmail doesn't open it in the default browser for me. I have to right click for the contextual menu, and then click "Open link in default browser". It's not horrible, but it's two clicks instead of one.
Has anyone found another workaround?

@danielbachhuber, Kiwi for Gmail. Works great, never had a problem again, free for personal use. (Nativefier does work well with Google Keep, for some reason.)

@jboxman Lol, that's not a fix! 😁
The --strict-internal-urls flag worked great for me:
nativefier https://mail.google.com --icon ~/Documents/Icons/gmail-mac.png --strict-internal-urls

hey @danielbachhuber , what --user-agent are you using? Gmail keeps blocking login for me, blaming an unsecure browser.


refactored if-else ladder and started? method in spark module definition

@ondra-m Are you okay with commit message?

@ondra-m any comments please ?
I want to go ahead with more refactoring  and also will be try complete pendingTODO .


RabbitMQ channel leak when responding to temporary queue

When executing a request/response scenario with temporary queues on the client/request side, Masstransit is leaving a channel open after the temporary queue has been destroyed. When the server/response side is closed, the channel is closed. I see that there used to be an issue cleaning up exchanges for temporary queues, perhaps this is something similar? See this gist for a repro.

To clarify, sending multiple requests doesn't leak additional channels. Closing and re-launching the client application, leaving the server running, does.

So I've been browsing the source some more, and it seems obvious why this is happening, but I'm not sure how to resolve the issue.
When calling context.Respond on the server, a producer is created by the outbound rabbitmq transport and added to the collection of producers in the connection handler. Those producers are not cleaned up until the connection is disposed (I didn't dig into exactly where/when that happens).
So it seems like we need some way of disposing of these producers when the queue goes away, or some method of polling for and cleaning up producers for queues that no longer exist. Thoughts?

@phatboyg @drusellers I'm having a hard time determining if this is an upstream issue, or something that would need to be handled at the MT level. Thoughts?

hmm. what version of RabbitMQ and MassTransit?

Masstransit 2.9.9, tested against RabbitMQ 3.3.0/Erlang R16B03-1/Win32, RabbitMQ 3.4.2/Erlang R16B03-1/Win32, and RabbitMQ 3.4.2/Erlang 17.4/Win32. All exhibit the same behavior.

do you have a unit test by chance to repro?
On Mon, Jan 12, 2015 at 10:41 AM, Drew Peterson<EMAIL_ADDRESS>wrote:

Masstransit 2.9.9, tested against RabbitMQ 3.3.0/Erlang R16B03-1/Win32,
RabbitMQ 3.4.2/Erlang R16B03-1/Win32, and RabbitMQ 3.4.2/Erlang 17.4/Win32.
All exhibit the same behavior.
—
Reply to this email directly or view it on GitHub
https://github.com/MassTransit/MassTransit/issues/266#issuecomment-69599975
.

I created a gist that reproduces it.
I can also attach a full solution if you like, but creating a project for the client, the server, and a shared project for the message contracts is all that's needed to play around with it.
If you watch the open channels in rabbit, you can see them stay open after the client (and temporary queue) go away. They only close when the server app is closed.

Because it's caching the outbound endpoint for the temporary queue, it's not going to close that producer until the bus instance is stopped, which closes the RabbitMQ connection. The only solution would be to add a timeout to the producers that after some period of time it closes the channel and cleans up the producer.

Any ideas as to how we could reliably expire a producer that way? After a set time we somehow poll to see if the queue is still around and if not dispose of the producer?
In long-lived services I don't think you'd want to close a channel on a simple timeout.

This is still an issue with MT3, so it's necessary to setup a cleanup timer on the SendEndpointCache so that unused endpoints are shut down after a few minutes.

So I took a whack at this, and while quite involved, I think it's going to handle the case of lingering channels to RabbitMQ for endpoints that are no longer used.


Failed to create folder

Error: ENOENT: no such file or directory, mkdir '...\ClientTsNode\client\components...\ClientTsNode\client\components\SomeModule'
Seems to be some error with path joining.

In a multi folder workspace

Fixed in v2.0.2


ARROW-16358: [CI][Dev] Allow archery crossbow to generate a CSV report for nightly builds

This PR will allow us to generate a CSV with the nightly builds status. This will be used in order to generate a static page with the different builds information and will allow us to analyze historical information from the different builds like since when they have been failing, last successful build commit, some tags, etcetera.
An example of a CSV generated can be seen on the following gist:
https://gist.github.com/raulcd/1799c8499ef228dfdf1ab0d986367d2a

I am not storing the date as part of the CSV because the filename generated will be something like: nightly-packaging-2022-04-25-0.csv .

I think that is fine. But I am wondering, it might be useful to keep track of the exact commit that is being tested in the build? For example in case you want to check if a certain fix was already included in the run or not (currently only the date is not that informative, given a date is still a broad range and depending on when it is exactly scheduled on that day)

I am not generating a header row for the CSV.

It wouldn't be that hard to do, I think, and could improve usability a bit given that there are quite some columns in there? (eg another attribute rows_header that returns a single list that can be written first to the csv file)

It wouldn't be that hard to do, I think, and could improve usability a bit given that there are quite some columns in there? (eg another attribute rows_header that returns a single list that can be written first to the csv file)

I have added the CSV header and have updated the gist with the updated outcome of running the command locally:
$ archery crossbow -t $GITHUB_TOKEN report-csv --no-fetch --save nightly-packaging-2022-04-25-0


Adding Information on View Event Button .

Add information of events so whenever clicked on view event Button it will be redirected to that events information page.
Hacktober 2024

Thanks for creating the issue in WildGuard! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Don't forget to follow @anuragverma108 – Project Admin & @PriyaGhosal -Project Collaborator  – for more updates!
We're excited to see your contribution as part of Hacktoberfest 2024! 🎉
Happy open-source contributing!


Update golangci-lint config

Coverage remained the same at 73.276% when pulling ce329a118133853b0d60713276f8a67161bf7721 on update_golint into a33c09accf392a1f2e08628c4766074fc1d1abc1 on master.


resolve #857

Hi @rikschennink
This PR Closes #857
Changes

Add test for src\js_tests_\utils\getExtentionFromFilename.test.js
Change getExtentionFromFilename.js

Thank you! waiting for your reply 😊

Thanks, will look into this when I have some time

Thanks, will look into this when I have some time

Thank you!!


java.util.ConcurrentModificationException in ServerRequestQueue

using branch  'io.branch.sdk.android:library:1.10.2'
is this the same issue as this one
java.util.HashMap$HashIterator.nextEntry (HashMap.java:806) org.json.JSONArray.toString (JSONArray.java:574) io.branch.referral.ServerRequestQueue$1.run (ServerRequestQueue.java:81) java.lang.Thread.run (Thread.java:841)

@akki-123 Thanks for reaching out and sorry for the issue. It is caused by a  bug in 1.10.2. It is fixed from 1.10.4. Issue is caused by the same reason as https://github.com/BranchMetrics/Android-Deferred-Deep-Linking-SDK/issues/198


Can models be bound to sl-select?

Hey,
when using sl-select with complex (/remote) data you are required to use optionValuePath.
I am able to point it to the models id, but this has the downside that I need to fetch the model afterwards before saving the relation.
Especially when dealing with both, create and update, this can be a little bit frustrating.
Is there any other way to bind the ember-object as-is and not only it's id?

@joshforisha Can you lend any advice?

Currently, there is no alternative that I'm aware of, off the top of my head. We can likely improve the option handling with promise-based logic at some point. Whether that's a high enough priority to attempt now vs. waiting for the planned v0.12 larger refactor of sl-select, is up to you @notmessenger.

A change like that would be best addressed in the v0.12.0 milestone, in https://github.com/softlayer/sl-ember-components/issues/456.  @Suven if there are other features you would like to see supported by the sl-select component please let us know and we'll see about integrating them during the rewrite.


Open Sans font not working on Gmail web client

Short description of problem:
I've built an email template where all the text should be Open Sans.
When the email is opened in Gmail web client, the text appears to be rendered in the 'Times' system font.
Scenario

MJML template head:

  <mj-head>
    <mj-title>Hi {{fname}}</mj-title>
    <mj-font name="Open Sans" href="https://fonts.googleapis.com/css?family=Open+Sans:400,700" />
    <mj-attributes>
      <mj-text align="center" color="#555" />
      <mj-button background-color="#ee2245" color="white" font-weight="bold" />
      <mj-all font-family="Open Sans" />
    </mj-attributes>

  </mj-head>

MJML is processed using mjml package with default options:

fs.readFile(path.normalize(filePath), "utf8", (err, data) => {
  if (err) throw err;
  const { html, errors } = mjml2html(data);
  // ....
  fs.writeFileSync(resultPath, html);
});

The output is saved as a Mandrill template and sent by Mandrill.
In Gmail Web, I can see font-family: Open Sans set in the element's style but looking at the network tab, there is no request sent for the google font.

In Mac Mail app, Gmail for Android and Outlook I do see Open Sans.
Screenshots and GIFs
Gmail Web (bad):

Gmail app for iPhone (bad):

Mac Mail, when forwarding (bad):

Mac Mail (good):

MJML version:
mjml-core 4.1.1, via CLI
Email clients the bug is seen on:
Gmail Web on Chrome
Mac Mail (when forwarding) v11.4
Gmail app for iPhone
Email clients the bug is not seen on:
Gmail for Android v8.7.15
Mac Mail (when reading received email) v11.4

Hi,
Gmail doesn't support external fonts, so please use a decent fallback like Open Sans, Arial, ...

Yep Roboto is one of the fonts automatically imported in MJML. We take care of the compatibility across client so it shouldn't be armful to try to load it

@iRyusa but why is it loaded anyway even though it's not used? I mean wouldn't it be good style to only load required stuff instead of only caring about compatiblity and accepting that it's always loaded?

I don't think there will be any solution from a markup standpoint. Might be
able to configuring directly in JS with a reset of internal font stack
supported but nothing yet
On Sat, Aug 11, 2018 at 11:22 AM Helmi<EMAIL_ADDRESS>wrote:

Oh sorry. my fault. It's part of my font stack as it is the default font
on Android devices. Any chance to avoid loading it though? The system font
stack is meant to take installed fonts only so it would be good if there
was an option to not load any font automatically.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/1304#issuecomment-412263164, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAizzSJJt8-G6pLH1mTVB2oOxQAQluGFks5uPqJugaJpZM4Vxoi2
.

--
Cordialement,
Maxime BRAZEILLES

hey @vitordino, this is not related to that issue but Roboto will be imported only if it is used (explicitly or because the font of an element is not set so it falls back to Roboto).
If it is not used, it is not imported, so it's easy to avoid it. See here when setting it manually on all text elements, or here when setting the default font for all elements.

You can just disable the import by settings the options.fonts to an empty object when calling the mjml2html function. cf the definition here https://github.com/mjmlio/mjml/blob/master/packages/mjml-core/src/index.js#L43


Pass path arguments with spaces safely to the cl.exe

Hello! I'm the build bot for the Mono project.
I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.
Contributors can ignore this message.


Add Policy Tree class for learning policies based on IRM

With this PR I would like to add a Policy Tree implemenation.
Description

Adding a DoubleMLPolicyTree class that fits a weighted classification of arbitrary covariates on an orthogonal basis.
Adding a policy_tree() method to the IRM model, that fits and returns a Policy Tree based on the ATE score.
Adding unit tests for both the new class and the new method.

Reference to Issues or PRs
Development of new features.
PR Checklist

[x] The title of the pull request summarizes the changes made.
[x] The PR contains a detailed description of all changes and additions.
[x] References to related issues or PRs are added.
[x] The code passes all (unit) tests.
[x] Enhancements or new feature are equipped with unit tests.
[x] The changes adhere to the PEP8 standards.

Thank you for your review @SvenKlaassen
I adapted the following changes:

rename x_vars to features
set min_samples_leaf to 8
move policytree return type test from test_irm.py to test_doubleml_return_types.py
fixed minor spelling / documentation issues you mentioned


Escape keys and values for LABEL instruction.

Without escaping keys and values, an invalid Dockerfile might be written.

could you please update line 29 in that file because it would be pretty misleading once this is merged

Python 2's string.maketrans() is an entirely different thing to Python 3's str.maketrans. It is more like 'tr'.

Thanks Tim!


Creating a module deeper than src/app throws Invalid path

Please provide us with the following information:

OS?

Mac OSX El Capitan 10.11.4

Versions.

angular-cli: 1.0.0-beta.21
node: 6.7.0
os: darwin x64

Repro steps.

Create new project with ng new my-app
Create a new folder inside src/app (e.g. src/app/modules)
Go to new folder (cd src/app/modules)
Create new module (ng g module core)

The log given by the failure.
Invalid path: "/src/app/modules/modules"" is not a valid path.
Mention any other details that might be useful.
To summarise this issue. While creating a new module the cli tries to go into the same folder again, if the module is created deeper than /src/app. Creating an module inside /src/app works as expected.

Thanks! We'll be in touch soon.

I get this too !

I got this 22-1 today as well, same conditions:

Created Dashboard module: ng g module dashboard --routing true
Changed directory into dashboard: cd dashboard
Attempted to create nested module: ng g module ./my-projects --routing true

I received:  Invalid path: ".....app/dashboard/dashboard"" is not a valid path.

I have not been able to reproduce this issue. Can someone who was experiencing this please retry with the latest version of the CLI?

@Brocco just tested with .beta-24. ng g module module-name doesn't throw this error anymore. Though, using ng g module module-name  --routing does throw the error. This means the error occurs during component creation I guess.

I had the same issue on beta22-1 so I updated cli to 24. Now, the error's gone and the difference from the previous is that ng g module  command only generates module.
Can you please update Readme on generating module with added options? It confuses the old users when generating the modules.

The current behavior for generating modules is to only generate a component when the --routing argument is used. That's why you only get the module.
I'm working on the issue with component, not changing the routing behavior though.

The current behavior for generating modules is to only generate a component when the --routing argument is used. That's why you only get the module.
Added in https://github.com/angular/angular-cli/pull/3389
I'm working on the issue with component, not changing the routing behavior though.


HBASE-27314 Make index block be customized and configured

patch for branch-2

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 20s
branch-2 passed

+1 :green_heart:
compile
3m 31s
branch-2 passed

+1 :green_heart:
checkstyle
1m  3s
branch-2 passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 31s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 12s
the patch passed

+1 :green_heart:
compile
3m 29s
the patch passed

-0 :warning:
javac
0m 31s
hbase-common generated 3 new + 31 unchanged - 0 fixed = 34 total (was 31)

-0 :warning:
checkstyle
0m 31s
hbase-server: The patch generated 3 new + 18 unchanged - 1 fixed = 21 total (was 19)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m  7s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 40s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

35m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4763

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux aaa7b1f0f7d7 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0f29423cc5

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-common.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
65 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 47s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 24s
branch-2 passed

+1 :green_heart:
compile
1m  6s
branch-2 passed

+1 :green_heart:
shadedjars
3m 58s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  5s
the patch passed

+1 :green_heart:
compile
1m  4s
the patch passed

+1 :green_heart:
javac
1m  4s
the patch passed

+1 :green_heart:
shadedjars
3m 57s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 48s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 27s
hbase-common in the patch passed.

+1 :green_heart:
unit
2m 32s
hbase-client in the patch passed.

+1 :green_heart:
unit
191m  5s
hbase-server in the patch passed.

214m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4763

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9f5b3b63d807 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0f29423cc5

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/testReport/

Max. process+thread count
2385 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 36s
branch-2 passed

+1 :green_heart:
compile
1m 51s
branch-2 passed

+1 :green_heart:
shadedjars
5m 35s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 10s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 22s
the patch passed

+1 :green_heart:
compile
1m 36s
the patch passed

+1 :green_heart:
javac
1m 36s
the patch passed

+1 :green_heart:
shadedjars
5m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 38s
hbase-common in the patch passed.

+1 :green_heart:
unit
3m 15s
hbase-client in the patch passed.

+1 :green_heart:
unit
210m 42s
hbase-server in the patch passed.

243m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4763

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3213a5f5038d 5.4.0-109-generic #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0f29423cc5

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/testReport/

Max. process+thread count
2398 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4763/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

What is the difference comparing to the PR for master?

Master do not have class "HColumnDescriptor.java"， branch-2 have，and need to change this class，only this different。


[CSL-1444] Fix 'isInitialized' check in Issuers part of LRC DB

Apart from this fix I also performed a small refactoring during initial investigation.

Did you launch node with existing DB? does it work now?

Yes, yes.

Segodnya u kogo-to budet klaster cc @fersel


Updated some lines

There were some areas that were confusing for customers. Changing @FirewallAPI.dll,-28752 to Remote Desktop makes more sense. Also by running the Enable-PSRemoting command; in testing this enables this firewall rule as well (the Also WINRM-HTTP-In-TCP-PUBLIC does not exist). I also added the Azure platform message to further clarify WHY customers are hardcoding an IP address.

@DickTracyII : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@genlin - If you accept the proposed changes, the callouts will need to be indented three spaces so they won't break list numbering in the live article.
#label:"aq-pr-triaged"

@genlin
Can you review this old PR and determine whether it needs to be closed or merged?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team

This PR was approved in email by @cynthn .


fix(transactions)!: adds versioned transaction schema

Description
fix(transactions)!: adds versioned transaction schema
Updated bindings (1.2.0), walletd client (1.2.0) and web UIs
Fix clippies in latest stable rust
Motivation and Context
Allows us to make versioned changes to the transaction schema/model while still supporting older schemas.
V1 may include breaking changes until mainnet.
How Has This Been Tested?
Manually, existing tests
What process can a PR reviewer use to test or verify this change?
Should work as before
Breaking Changes

[ ] None
[x] Requires data directory to be deleted
[ ] Other - Please specify

The Web UI is failing to compile because the bindings are not published


Support for Health Check on Upstreams

Hello,
I have changed the code to add healthcheck support to upstreams, but I am not able to commit or create a new branch into this project. How should I do?

Hi there. The best thing you can do is to make a fork of this repo, and do the work on the code updates a branch in your own space. From there, you can create a pull request where the developers of this project can look at it, and hopefully have it merged into the main project.
There are a few tutorials on how to do all that, such as https://help.github.com/articles/creating-a-pull-request-from-a-fork/ & https://gist.github.com/Chaser324/ce0505fbed06b947d962

Thanks Alister.
Looking at it right now

Thank you very much.
https://github.com/mybuilder/kongfig/pull/137


BadMethodCallException - This cache store does not support tagging - hasRole in Controller

#Hi All !
I have a problem, i want to use hasRole method in my Controller but i have this error :

BadMethodCallException in Repository.php line 367:
This cache store does not support tagging.

My controller :
namespace App\Http\Controllers\Admin;

use Illuminate\Http\Request;

use App\Http\Requests;
use App\Http\Controllers\Controller;
use Auth;
use App\User;

class SchoolsController extends Controller
{
    public function index()
    {
        $user = Auth::user();

        $role = $user->hasRole('superadmin');
        dd($role);

        return view('admin.schools.index', array(
            'title' => 'Schools',
            'icon' => 'graduation-cap',
            'parent_title' => 'Contacts',
            'parent_icon' => 'accounts',
        ));
    }
}

Can you help me please ?
Thank's a lot !

Hi!
The current version of Entrust is not supporting the file cache driver, you should change it to something else.

I found my problem... The file cache driver is not compatible with tags. I change it to "Array" and it's works. I hope this issue can help anyone .. !

Thank's netpok, i write at the same moment ! It's ok, thank's a lot !

@netpok This works for me as well

when i add new user,edit and delete. this exception appear
BadMethodCallException in Repository.php line 367: This cache store does not support tagging.
but,  actually add,edit,delete when i go to the page of users ????


[INLONG-5231][Improve][CodeStyle] Add spotless to CI

see https://github.com/apache/inlong/issues/5231
At present, the AOSP format specification is selected for spotless, which should be consistent with the existing format as much as possible. Currently, only spotless apply the manager module.

checkstyle has a lot to adapt, and I'm still adapting...


Merge dev-zh into main(for Chinese localization live version)

Follow #987. Merge Chinese development branch into main.
Checklist to make localization live.

[x] Validate all files which are not in the localization directory (content/zh-cn/*)
[x] Insert empty lines before and after the header lines (most of the files already have these, but for example, content/zh-cn/platform_as_a_service.md requires this change.)
[x] Add semantic line breaks (this will make the review and maintain jobs easier)
[x] Rename markdown filenames (ref: https://github.com/cncf/glossary/commit/2832c5d13329297988223215dabf0f7bbd58db3d)
[x] Update relevant links (ref: https://github.com/cncf/glossary/commit/bba3069b8258f2d1fde1df573633b179dbf72b0c)
[x] Check Preview works

Hey, @jihoon-seo. Could you do me a favor? I got a question here. :)
This PR is blocked at the DCO check, so it might be difficult for me to solve alone. Could DCO be set to pass manually?

Thx a lot for your help, @jihoon-seo! Does this PR still need to be improved?

Why not use cncf:dev-zh as source branch, but Jacob953:dev-zh-merge.

About hold: please see https://github.com/cncf/glossary/pull/1090#issuecomment-1188689860.

The PR #1105 supersedes & closes this PR.

#1105 has been merged !
Let me close this PR :)


angular-cli: Extensibility

This is more like  feature and maybe this is already in the list.
Even all works great, I would like to extends angular-cli and have some hooks available, to I can plug in my custom-command that can be called everytime I spin a build, or anything while on ng serve I change something and the build refreshes.
ideally the command would be outside of node_modules/
Thanks,
-Fk

You can create scripts in package.json that chains multiple commands together. And live-reload on ng serve is already a thing...

Right lets say I can use package.json from where I will execute a command, but does not help with live-reload - when running ng serve

We plan to support addons in the future, yes. It's a post 1.0 concern at the moment.

As I understand the cli is based on ember-cli, which supports the install action for installing addons:
Ember CLI will detect the presence of an addon by inspecting each of your applications dependencies and search their package.json files for the presence of ember-addon in the keywords section

Is it possible to enable this?

Just wanted to give an update: 1.0 is currently released, and we are looking at the design of an addon system for future major versions.

This is good news!!  Is this going to be under wiki to look at ?

Are there any news on this ?

We just added customizable blueprints (https://github.com/angular/angular-cli/pull/7090, docs are still being created) so that bit is customizable, but there isn't any build step customization yet.

I see. I will just have to wait for this addons support that maybe allows me to extends or customize build steps. Any timeline for this?
But thanks for the prompt reply.

No time to share yet, no. But will try to share it as soon as we can.

I would like/recommend the team to be more open about the addon system. The feature has been postponed and delayed for several reason (you know them better) but let the community help you out! Trying to get it right just by yourselves will not produce as good results. Therefore, some recommendations:

An open process of whats the strategy in mind to allow extensibility, so people get an idea of what/how something can (or not) be done.

Open a space for discussion of it. Probably the community can provide some insights (particularly webpack-oriented folks) on how to make it better/simpler. If the addons ecosystem is for the community to populate, then hear what the community thinks/need and let us help you out on the design (implementation?) process.

Establish a public rough roadmap (with possible risks if needed). Some people exasperate (myself included in some stressful situations) when it hasn't been clear how much work/time is needed/used for the addon system. Since pre-1.0 release the standard response for extension issues has been "later". At least pinpointing which quarter of the year something is to be expected helps a lot.

I'm really enthusiastic to help on pug (jade) templating and service worker addons but I need you guys to be more open. Help me, help you, win-win :)

An addon system has been promised as solution for extending the default webpack configuration. Currently, I cannot even do such a simple thing as adding a loader for *graphql files without hacking<EMAIL_ADDRESS>If it will take too long to provide a proper addon system, it would be helpful to re-consider #1656 and at least provide an interim way of injecting webpack loaders using the angular-cli.json cofiguration. I really don't want to eject angular-cli just to be able to import *.graphql files.

Yeah. I am hacking too few files and next to  it I have to have my own CLI script that initialize a few things ;-(

@filipesilva
Any updates / branches I could look into?
I'm basically at a standstill on some authorization workflows I need to do...
I'm not sure if I should fork / maintain merges or... what.
Thanks - Chad

Wow! This is happening!? Woot! Woot! Godspeed @filipesilva 👍

Sucks not having an easy way to add a loader for .graphql files. ):

Having pre-build hooks would be really nice for compiling GRPC-Web stubs.

I'm going to close this as Architect and Schematics are covering those bases. Architect is going to be stable in 7.0.

@hansl great stuff by the way - congrats!


Improve score UX

Is your feature request related to a problem? Please describe.
Right now, the score UX has a few issues:

no visual indication of the score besides the text itself - a color and/or more meaningful shape indication would be good. this is important because a big mapping should be able to draw attention based on score values.
have to click a small, awkwardly-floating button to select a score
score button has unintuitively differing hover & click functionality

Some important other requirements:

without being interacted with, the score UX needs to fit in the corner of a node and on the center of an edge
when interacted with, the score UX can grow to fit more information and/or make it easier to further interact with. It likely would need to lay in front of anything around it.
edges will eventually also have some text on them (e.g. "solves" "causes"), so score UX needs to fit with this
should be able to remove score selection (right now there's a "-") to distinguish a low/average score from no score

Describe the solution you'd like
A separate button for viewing the child claim tree could address number 3 (and could use the outlined, single, multi versions of the icon to indicate how many children claims are in the tree too):

For addressing number 1, perhaps each number could change the button's color across some gradient. Color (same color?) could also be used with a shadow (scaling thickness/boldness?) around the relevant node/edge.
For addressing number 2, perhaps the button should expand into a slider (though I'm not sure how this would solve number 7)? Or a pie menu (ideally though we wouldn't use a component that's unpopular)?
Describe alternatives you've considered
Additional context
Technical ideas

Currently thinking that this with a pie menu for choice seems pretty good


remove moduleid

It looks like this is related to this RC5 issue. https://github.com/angular/angular-cli/issues/1665. I will publish the latest version with your changes today on NPM then close the issue. Thanks for your help.


Docs: typo

Signed-off-by: Hu Keping<EMAIL_ADDRESS>

Can one of the admins verify this patch?

@HuKeping Apologies, I added an extra builder in circleci for a test, and I think this has thrown it off a bit.  Can you make a small modification (such as to the commit message) and force-push?

@HuKeping Also, thanks for spotting this and fixing!  It LGTM once we can get the CI to pass.

It's OK, updated @cyli

Thanks @HuKeping!  LGTM!


Maxed out OneDrive webhook subscriptions - Unable to delete existing subscriptions

How am I supposed to delete a subscription when I don't have an id? I accidentally created a loop that maxed out my subscriptions and now I have no way of getting rid of them because I don't have the ids recorded anywhere.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 70301fdf-007d-834f-e5e3-cb2bfbbd2d84
Version Independent ID: 5bada6e0-9402-e46a-9f0a-4a9c9e181795
Content: Update a webhook subscription - OneDrive API - OneDrive dev center
Content Source: docs/rest-api/api/subscription_update.md
Product: onedrive
GitHub Login: @JeremyKelley
Microsoft Alias: JeremyKe

Sorry I thought this was done on the Delete page not the Update page. The issue still stands though.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Reduce calls to getDimensionsFromName by one for each datapoint

Reduce calls to getDimensionsFromName by one for each datapoint and makes things a bit more efficient
These numbers are after the PR  for making the  getDimensionsByName improvements and do not include them.
benchmark                   old ns/op     new ns/op     delta
BenchmarkNewDatapoint-8     22056         17297         -21.58%

benchmark                   old allocs     new allocs     delta
BenchmarkNewDatapoint-8     60             47             -21.67%

benchmark                   old bytes     new bytes     delta
BenchmarkNewDatapoint-8     4336          3088          -28.78%

Coverage remained the same at 100.0% when pulling 9fd0c255f8e381dbef0f1c6dca37854e552ea982 on enhancemoar into 5fa39d00a262256a3bd08c814e08dc3570325831 on master.

Thanks drew, updated.

Coverage remained the same at 100.0% when pulling 4438e77dd8337a1bb355b0ecfcee3ef62ee6ef04 on enhancemoar into 5fa39d00a262256a3bd08c814e08dc3570325831 on master.

So are we not getting dimensions out of type_instance anymore?

It looks like this change moves the getting dimensions out of type_instance into the new function pointTypeInstance.

That's pretty confusing in terms of code organization. Why wouldn't the same logic apply to getting dimensions out of plugin_instance? If the point is to avoid allocations because dimensions are most likely not in type_instance, can't apply the same logic for plugin_instance, and ultimately, metric?

No, type_instance becomes part of the metric name, plugin_instance and host do not.  I'll try to make this less confusing.

Coverage remained the same at 100.0% when pulling 05a2a6644fc311d399c56e058ccdf1701e45a190 on enhancemoar into d9f1796b9a33444de2c24556685c0fd2f3458070 on master.

Coverage remained the same at 100.0% when pulling 777c05244b49c7a9b329575fc22385e3aa7cfa83 on enhancemoar into d9f1796b9a33444de2c24556685c0fd2f3458070 on master.

Looks a lot more readable, LGTM. I'll let @tedoc2000 merge when happy.


[WIP]: Make the winkey function(s) work

Closing in favor of https://github.com/wavelog/wavelog/pull/787.


More ApplyStyle for UI

This exposes the woodpanel styling as a public method and adds styling for ScrollRect and Scrollbar components. Sometimes you may only need Scrollbar so both methods are public.

It failed to compile. I guess you used language features not supported by the dotnet version I use in the github workflow... I tried to update to a new version (even beta 6.0) but I could not get it to work. If you have any idea what to do (I think you use Linux, right?), I would be glad...

Hopefully it compiles now :)

Looks good. Still wondering how to achieve this ;) It does not like "SomeClass bla = new()", either...

I haven't worked with Github action jet so I have no idea

It's using ubuntu with this toolset:
sudo apt-get install -y mono-roslyn mono-complete mono-dbg msbuild unzip dirmngr dotnet-sdk-5.0 dotnet-runtime-5.0
And that doesn't like some new features.
Anyway, I will check out your PR soon.

looks good, thx