App crashes on startup

Just got v0.52 installed, followed SETUP.md to create the LoopBe device and then figured I need to specially approve the app in Privacy & Security and then finally managed to open it and pointed to the multiDevice.xml file (that dialog was a bit confusing and only found out about it by searching for the filename and finding #1).
Everything seems to be in order, but I can't even get the app to start, just get this unhelpful error message that is not covered in troubleshooting.
I have an M1 Mac.
Any idea what's going on?
Wait, does it only work with MK2?

<?xml version="1.0"?>
<DeviceInfoList version="1" useSoftwareInput="1">
	<InputDevice version="1" name="KOMPLETE KONTROL S49 Port 1" enabled="1" />
	<InputDevice version="1" name="KOMPLETE KONTROL S49 Port 2" enabled="0" />
	<InputDevice version="1" name="Komplete Kontrol DAW - 1" enabled="0" />
	<InputDevice version="1" name="IAC Driver Bus 1" enabled="0" />
	<InputDevice version="1" name="IAC Driver LoopBe" enabled="0" />
	<OutputDevice version="1" name="Built-in MIDI Synthesizer" enabled="0" />
	<OutputDevice version="1" name="KOMPLETE KONTROL S49 Port 1" enabled="0" />
	<OutputDevice version="1" name="KOMPLETE KONTROL S49 Port 2" enabled="0" />
	<OutputDevice version="1" name="Komplete Kontrol DAW - 1" enabled="0" />
	<OutputDevice version="1" name="IAC Driver Bus 1" enabled="0" />
	<OutputDevice version="1" name="IAC Driver LoopBe" enabled="1" userNotes="0" backgroundNotes="0" metronome="0" percussion="0" lightChannel="-2" />
</DeviceInfoList>

Wait, this is a bit different from the screenshot in the setup, maybe a new version of Synthesia broke it?

If I have the keyboard turned off I do get a different error message:

Managed to capture the full app launch and crash lifecycle in the logs, see below.
Maybe this is the problem?
TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement

Does the app need some accessibility functionality that it's trying to generate a prompt for?
Full logs:
default	13:24:55.932945+0100	runningboardd	Launch request for app<application.tillt.KompleteSynthesia.55148837.55148842(501)> is using uid 501 (divined from auid 501 euid 501)
default	13:24:55.933007+0100	runningboardd	Acquiring assertion targeting app<application.tillt.KompleteSynthesia.55148837.55148842(501)> from originator [app<application.com.runningwithcrayons.Alfred.52534129.52534172(501)>:4058] with description <RBSAssertionDescriptor| "LS launch tillt.KompleteSynthesia" ID:627-4058-124291 target:app<application.tillt.KompleteSynthesia.55148837.55148842(501)> attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"LaunchRoleUserInteractive" sourceEnvironment:"(null)">
	]>
default	13:24:55.933065+0100	runningboardd	Assertion 627-4058-124291 (target:app<application.tillt.KompleteSynthesia.55148837.55148842(501)>) will be created as active
default	13:24:55.933248+0100	runningboardd	Executing launch request for app<application.tillt.KompleteSynthesia.55148837.55148842(501)> (LS launch tillt.KompleteSynthesia)
default	13:24:55.933269+0100	runningboardd	Checking PreventLaunch: global:0 exPath:/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia predicates:(null) allow:(null)
default	13:24:55.933294+0100	runningboardd	Creating and launching job for: app<application.tillt.KompleteSynthesia.55148837.55148842(501)>
default	13:24:55.933432+0100	runningboardd	_mutateContextIfNeeded called for tillt.KompleteSynthesia
default	13:24:55.934393+0100	runningboardd	app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: -[RBPersonaManager personaForIdentity:context:personaUID:personaUniqueString:] required 0.000000 ms (wallclock); resolved to {4294967295, (null)}
default	13:24:55.934550+0100	runningboardd	'app<application.tillt.KompleteSynthesia.55148837.55148842(501)>' Constructed job description (context <RBSLaunchContext: 0x118011550>):
<dictionary: 0x10f73dd80> { count = 22, transaction: 0, voucher = 0x0, contents =
	"Platform" => <int64: 0xa52f94be14ba7807>: 1
	"ProcessType" => <string: 0x10f754d90> { length = 3, contents = "App" }
	"EnableTransactions" => <bool: 0x1e77dc3f0>: false
	"_ManagedBy" => <string: 0x11f77ed40> { length = 22, contents = "com.apple.runningboard" }
	"CFBundleIdentifier" => <string: 0x10f7642b0> { length = 23, contents = "tillt.KompleteSynthesia" }
	"_ResourceCoalition" => <string: 0x10f755e70> { length = 63, contents = "app<application.tillt.KompleteSynthesia.55148837.55148842(501)>" }
	"_DisablePointerAuth" => <bool: 0x1e77dc3d0>: true
	"ThrottleInterval" => <int64: 0xa52f94bdeb4587f7>:<PHONE_NUMBER>
	"MachServices" => <dictionary: 0x10f729060> { count = 0, transaction: 0, voucher = 0x0, contents =
	}
	"EnablePressuredExit" => <bool: 0x1e77dc3f0>: false
	"LimitLoadToSessionType" => <array: 0x10f763f30><…>
default	13:24:55.952167+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Memory Limits: active 0 inactive 0
 <private>
default	13:24:55.952218+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] This process will not be managed.
default	13:24:55.952337+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] HOME is <private>
default	13:24:55.952397+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] TMPDIR is <private>
default	13:24:55.952630+0100	runningboardd	Now tracking process: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:55.953061+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractive)
default	13:24:55.954169+0100	runningboardd	Using default underlying assertion for app: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:55.954380+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] with description <RBSAssertionDescriptor| "RB Underlying Assertion" ID:627-627-124292 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.underlying" name:"defaultUnderlyingAppAssertion" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:55.954560+0100	runningboardd	Assertion<PHONE_NUMBER>92 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:55.954668+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:55.954864+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:55.954912+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] reported to RB as running
default	13:24:55.955005+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Set darwin role to: UserInteractive
default	13:24:55.955358+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:55.955743+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:55.956449+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractive)
default	13:24:55.958151+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.coreservices.launchservicesd>:559] with description <RBSAssertionDescriptor| "foregroundApp:16646" ID:627-559-124293 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"RoleUserInteractiveNonFocal" sourceEnvironment:"(null)">
	]>
default	13:24:55.958450+0100	runningboardd	Assertion<PHONE_NUMBER>93 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:55.959260+0100	Alfred	LAUNCH: 0x0-0xe83e83 tillt.KompleteSynthesia starting stopped process.
default	13:24:55.971780+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractive)
default	13:24:55.972543+0100	runningboardd	Invalidating assertion 627-4058-124291 (target:app<application.tillt.KompleteSynthesia.55148837.55148842(501)>) from originator [app<application.com.runningwithcrayons.Alfred.52534129.52534172(501)>:4058]
default	13:24:55.975370+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:55.975385+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:55.975404+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:55.975425+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:55.975442+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:55.975454+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:55.975466+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:55.975487+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:55.975492+0100	runningboardd	Successfully acquired underlying assertion for [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:55.976273+0100	loginwindow	-[PersistentAppsSupport applicationReady:] | App: KompleteSynthesia.app, ready, updating active tracking timer
default	13:24:55.976320+0100	loginwindow	-[ApplicationManager checkInAppContext:eventData:] | ApplicationManager: Checked in app : KompleteSynthesia.app
default	13:24:55.982928+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=16646.1, attribution={requesting={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, },
default	13:24:55.983963+0100	distnoted	register name: com.apple.sharedfilelist.change object: com.apple.LSSharedFileList.ApplicationRecentDocuments/tillt.kompletesynthesia token: 9e0000004f pid: 1226
default	13:24:55.987236+0100	tccd	AUTHREQ_SUBJECT: msgID=16646.1, subject=tillt.KompleteSynthesia,
default	13:24:55.988006+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x146edc6b0 at /Applications/KompleteSynthesia.app
default	13:24:55.992999+0100	KompleteSynthesia	server port 0x00003007, session port 0x00003007
default	13:24:55.993904+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=587.1312, attribution={accessing={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, requesting={TCCDProcess: identifier=com.apple.WindowServer, pid=587, auid=88, euid=88, binary_path=/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer}, },
default	13:24:55.993947+0100	tccd	requestor: TCCDProcess: identifier=com.apple.WindowServer, pid=587, auid=88, euid=88, binary_path=/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer is checking access for accessor TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia
default	13:24:55.995362+0100	tccd	AUTHREQ_SUBJECT: msgID=587.1312, subject=tillt.KompleteSynthesia,
default	13:24:55.996270+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x1457a98a0 at /Applications/KompleteSynthesia.app
default	13:24:56.002077+0100	KompleteSynthesia	Received configuration update from daemon (initial)
default	13:24:56.003181+0100	KompleteSynthesia	New connection 0x17d44f main
default	13:24:56.006253+0100	KompleteSynthesia	CHECKIN: pid=16646
default	13:24:56.011837+0100	KompleteSynthesia	CHECKEDIN: pid=16646 asn=0x0-0xe83e83 foreground=1
default	13:24:56.011738+0100	launchservicesd	CHECKIN:0x0-0xe83e83 16646 tillt.KompleteSynthesia
default	13:24:56.012090+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.coreservices.launchservicesd>:559] with description <RBSAssertionDescriptor| "foregroundApp:16646" ID:627-559-124294 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"RoleUserInteractiveNonFocal" sourceEnvironment:"(null)">
	]>
default	13:24:56.012152+0100	runningboardd	Assertion<PHONE_NUMBER>94 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.012484+0100	runningboardd	Invalidating assertion<PHONE_NUMBER>93 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) from originator [osservice<com.apple.coreservices.launchservicesd>:559]
default	13:24:56.012927+0100	KompleteSynthesia	FRONTLOGGING: version 1
default	13:24:56.012943+0100	KompleteSynthesia	Registered, pid=16646 ASN=0x0,0xe83e83
default	13:24:56.013205+0100	loginwindow	-[ApplicationManager checkInAppContext:eventData:] | ApplicationManager: Checked in app : Komplete Synthesia
default	13:24:56.014533+0100	KompleteSynthesia	BringForward: pid=16646 asn=0x0-0xe83e83 bringForward=1 foreground=1 uiElement=0 launchedByLS=1 modifiersCount=1 allDisabled=0
default	13:24:56.014595+0100	KompleteSynthesia	BringFrontModifier: pid=16646 asn=0x0-0xe83e83 Modifier 0 hideAfter=0 hideOthers=0 dontMakeFrontmost=0 mouseDown=0/0 seed=0/0
default	13:24:56.014682+0100	KompleteSynthesia	BringForward: pid=16646 asn=0x0-0xe83e83
default	13:24:56.014700+0100	KompleteSynthesia	SetFrontProcess: asn=0x0-0xe83e83 options=0
default	13:24:56.015384+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.coreservices.launchservicesd>:559] with description <RBSAssertionDescriptor| "frontmost:16646" ID:627-559-124295 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"RoleUserInteractiveFocal" sourceEnvironment:"(null)">
	]>
default	13:24:56.015476+0100	runningboardd	Assertion<PHONE_NUMBER>95 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.015901+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.015913+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.016468+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.016705+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.coreservices.launchservicesd>:559] with description <RBSAssertionDescriptor| "notification:16646" ID:627-559-124296 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"LSNotification" sourceEnvironment:"(null)">
	]>
default	13:24:56.016711+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Set darwin role to: UserInteractiveFocal
default	13:24:56.016799+0100	runningboardd	Assertion<PHONE_NUMBER>96 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.019236+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.WindowServer(88)>:587] with description <RBSAssertionDescriptor| "FUSBFrontmostProcess" ID:627-587-124297 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.fuseboard" name:"Frontmost" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:56.019300+0100	runningboardd	Assertion<PHONE_NUMBER>97 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.016818+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.020193+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.020204+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.020211+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.020699+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.020634+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.020787+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.020827+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.020848+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.020863+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.020876+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.020994+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.022629+0100	KompleteSynthesia	Current system appearance, (HLTB: 1), (SLS: 0)
default	13:24:56.024871+0100	KompleteSynthesia	Current system appearance, (HLTB: 1), (SLS: 0)
default	13:24:56.025459+0100	KompleteSynthesia	Post-registration system appearance: (HLTB: 1)
default	13:24:56.055800+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.055850+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.055901+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.055995+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.056730+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.066344+0100	distnoted	register name: com.apple.xctest.FakeForceTouchDevice object: tillt.KompleteSynthesia token: 1e00000021 pid: 16646
default	13:24:56.073368+0100	KompleteSynthesia	Registering for test daemon availability notify post.
default	13:24:56.073451+0100	KompleteSynthesia	notify_get_state check indicated test daemon not ready.
default	13:24:56.073522+0100	KompleteSynthesia	notify_get_state check indicated test daemon not ready.
default	13:24:56.073585+0100	KompleteSynthesia	notify_get_state check indicated test daemon not ready.
default	13:24:56.079843+0100	distnoted	register name: com.apple.nsquiet_safe_quit_give_reason object: tillt.KompleteSynthesia token: 230000001c pid: 16646
default	13:24:56.100948+0100	KompleteSynthesia	SignalReady: pid=16646 asn=0x0-0xe83e83
default	13:24:56.101324+0100	KompleteSynthesia	SIGNAL: pid=16646 asn=0x0x-0xe83e83
default	13:24:56.105659+0100	loginwindow	-[PersistentAppsSupport applicationReady:] | App: Komplete Synthesia, ready, updating active tracking timer
default	13:24:56.109344+0100	KompleteSynthesia	Initializing connection
default	13:24:56.109375+0100	KompleteSynthesia	Removing all cached process handles
default	13:24:56.109503+0100	KompleteSynthesia	Creating connection to com.apple.runningboard
default	13:24:56.109416+0100	KompleteSynthesia	Sending handshake request attempt #1 to server
default	13:24:56.110085+0100	runningboardd	Setting client for [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] as ready
default	13:24:56.110534+0100	KompleteSynthesia	Handshake succeeded
default	13:24:56.110551+0100	KompleteSynthesia	Identity resolved as app<application.tillt.KompleteSynthesia.55148837.55148842(501)>
default	13:24:56.110738+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] with description <RBSAssertionDescriptor| "AppNap adapter assertion" ID:627-16646-124298 target:16646 attributes:[
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"Enable" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"Inactive" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PreventDiskThrottle" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PreventSuppressedCPU" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PreventLowPriorirtyCPU" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PreventBackgroundSockets" sourceEnvironment:"(null)">,
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PreventTimerThrottleTier0" sourceEn<…>
default	13:24:56.110825+0100	runningboardd	Assertion 627-16646-124298 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.111190+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.111228+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.111273+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.111404+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.111469+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.111521+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Set AppNap state: <RBMutableProcessAppNapState|0x11801da20 enabled:Y active:N socket:N disk:N priority:N cpu:N timer:Tier0>
default	13:24:56.123827+0100	KompleteSynthesia	No persisted cache on this platform.
default	13:24:56.125034+0100	WindowManager	Connection activated | (16646) Komplete Synthesia
default	13:24:56.131011+0100	KompleteSynthesia	checking if com.native-instruments.NIHardwareService is active
default	13:24:56.132679+0100	KompleteSynthesia	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x6000014a9f00
 (
    "<NSAquaAppearance: 0x6000014aa100>",
    "<NSSystemAppearance: 0x6000014ac600>"
)>
default	13:24:56.133555+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x1457aa420 at /Applications/KompleteSynthesia.app
error	13:24:56.143884+0100	tccd	Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for accessing={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, requesting={TCCDProcess: identifier=com.apple.appleeventsd, pid=797, auid=55, euid=55, binary_path=/System/Library/CoreServices/appleeventsd},
default	13:24:56.145014+0100	KompleteSynthesia	com.native-instruments.NIHardwareService is not running
default	13:24:56.145452+0100	KompleteSynthesia	checking if com.native-instruments.NIHostIntegrationAgent is active
default	13:24:56.145819+0100	KompleteSynthesia	checking if com.native-instruments.NTKDaemon is active
default	13:24:56.146107+0100	KompleteSynthesia	com.native-instruments.NTKDaemon is not running
default	13:24:56.146477+0100	KompleteSynthesia	found com.native-instruments.NIHostIntegrationAgent and trying to kill NIHostIntegrationAgent.app ...
default	13:24:56.146779+0100	KompleteSynthesia	restart com.native-instruments.NIHostIntegrationAgent returned 1
default	13:24:56.147815+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=587.1313, attribution={accessing={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, requesting={TCCDProcess: identifier=com.apple.WindowServer, pid=587, auid=88, euid=88, binary_path=/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer}, },
default	13:24:56.147840+0100	tccd	requestor: TCCDProcess: identifier=com.apple.WindowServer, pid=587, auid=88, euid=88, binary_path=/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer is checking access for accessor TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia
default	13:24:56.148658+0100	tccd	AUTHREQ_SUBJECT: msgID=587.1313, subject=tillt.KompleteSynthesia,
default	13:24:56.149905+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x146aaa0b0 at /Applications/KompleteSynthesia.app
error	13:24:56.164294+0100	tccd	TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement
error	13:24:56.165786+0100	tccd	TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement
default	13:24:56.165914+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=16646.3, attribution={accessing={TCCDProcess: identifier=com.hegenberg.BetterTouchTool, pid=11774, auid=501, euid=501, binary_path=/Applications/BetterTouchTool.app/Contents/MacOS/BetterTouchTool}, requesting={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, },
default	13:24:56.190917+0100	KompleteSynthesia	stopped com.native-instruments.NIHostIntegrationAgent
default	13:24:56.192085+0100	KompleteSynthesia	Synthesia configuration was validated before
default	13:24:56.192400+0100	KompleteSynthesia	IOCreatePlugInInterfaceForService failed
default	13:24:56.192429+0100	KompleteSynthesia	IOCreatePlugInInterfaceForService failed
default	13:24:56.195240+0100	KompleteSynthesia	detected Komplete Kontrol S49 MK1 USB device
default	13:24:56.195468+0100	KompleteSynthesia	interface opened and async port setup
default	13:24:56.195485+0100	KompleteSynthesia	USB controller fully connected - up and running
default	13:24:56.195497+0100	KompleteSynthesia	detected Komplete Kontrol S49 MK1 USB device
error	13:24:56.195266+0100	kernel	KompleteSynthesi@(null): AppleUSBHostUserClient::openGated: failed to open KOMPLETE KONTROL S49@02110000: provider is already opened for exclusive access by pid 16458, MIDIServer
default	13:24:56.196022+0100	KompleteSynthesia	-[NSAlert alertWithError:] called with nil NSError. A generic error message will be displayed, but the user deserves better.
default	13:24:56.214044+0100	KompleteSynthesia	Set a breakpoint at SLSLogBreak to catch errors/faults as they are logged.
error	13:24:56.214060+0100	KompleteSynthesia	CGSWindowShmemCreateWithPort failed on port 0
default	13:24:56.217632+0100	distnoted	register name: com.apple.speech.synthesis.TalkingAlertsSyncWithPrefsNotification object: kCFNotificationAnyObject token:<PHONE_NUMBER> pid: 16646
error	13:24:56.219360+0100	KompleteSynthesia	CGSWindowShmemCreateWithPort failed on port 0
default	13:24:56.222517+0100	KompleteSynthesia	order window front conditionally: 1d66 related: 0
error	13:24:56.249602+0100	tccd	TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement
default	13:24:56.249696+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=16646.4, attribution={accessing={TCCDProcess: identifier=com.mschrage.fig, pid=4016, auid=501, euid=501, binary_path=/Applications/Fig.app/Contents/MacOS/fig_desktop}, requesting={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, },
default	13:24:56.256916+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.WindowServer(88)>:587] with description <RBSAssertionDescriptor| "AppDrawing" ID:627-587-124299 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"AppDrawing" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:56.256973+0100	runningboardd	Assertion<PHONE_NUMBER>99 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.257285+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.257314+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.257350+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.257390+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.257460+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.258363+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.WindowServer(88)>:587] with description <RBSAssertionDescriptor| "AppVisible" ID:627-587-124300 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"AppVisible" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:56.258409+0100	runningboardd	Assertion<PHONE_NUMBER>00 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.258938+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.258938+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.258982+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.259032+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.259079+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:56.291310+0100	runningboardd	Acquiring assertion targeting [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] from originator [osservice<com.apple.WindowServer(88)>:587] with description <RBSAssertionDescriptor| "FUSBProcessWindowState: visible" ID:627-587-124301 target:16646 attributes:[
	<RBSDomainAttribute| domain:"com.apple.fuseboard" name:"Visible" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:56.291382+0100	runningboardd	Assertion<PHONE_NUMBER>01 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) will be created as active
default	13:24:56.291780+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: running-active (role: UserInteractiveFocal)
default	13:24:56.291830+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring jetsam update because this process is not memory-managed
default	13:24:56.291872+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring suspend because this process is not lifecycle managed
default	13:24:56.291909+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring GPU update because this process is not GPU managed
default	13:24:56.291982+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] Ignoring memory limit update because this process is not memory-managed
default	13:24:58.971453+0100	Synthesia	                AUHAL.cpp:446   ~AUHAL: (0x12c080240) Selecting device 0 from destructor
default	13:24:58.971589+0100	Synthesia	                AUHAL.cpp:572   SelectDevice: -> (0x12c080240)
default	13:24:58.971610+0100	Synthesia	                AUHAL.cpp:629   SelectDevice: (0x12c080240) not already running
default	13:24:58.971626+0100	Synthesia	                AUHAL.cpp:634   SelectDevice: (0x12c080240) disconnecting device 68
default	13:24:58.971658+0100	Synthesia	                AUHAL.cpp:698   SelectDevice: (0x12c080240) destroying ioproc 0xb for device 68
default	13:24:59.004067+0100	Synthesia	                AUHAL.cpp:806   SelectDevice: (0x12c080240) nothing to setup
default	13:24:59.004106+0100	Synthesia	                AUHAL.cpp:822   SelectDevice: (0x12c080240) removing 6 device listeners from device 68
default	13:24:59.004364+0100	Synthesia	                AUHAL.cpp:831   SelectDevice: (0x12c080240) adding 0 device listeners to device 0
default	13:24:59.004379+0100	Synthesia	                AUHAL.cpp:822   SelectDevice: (0x12c080240) removing 0 device delegate listeners from device 68
default	13:24:59.004390+0100	Synthesia	                AUHAL.cpp:831   SelectDevice: (0x12c080240) adding 0 device delegate listeners to device 0
default	13:24:59.004398+0100	Synthesia	                AUHAL.cpp:844   SelectDevice: <- (0x12c080240)
default	13:24:59.006305+0100	runningboardd	Invalidating assertion<PHONE_NUMBER>31 (target:[app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460]) from originator [osservice<com.apple.powerd>:530]
default	13:24:59.008383+0100	Synthesia	                AUHAL.cpp:388   AUHAL: (0x12e82d040) Listening to HAL system property<PHONE_NUMBER>
default	13:24:59.008440+0100	Synthesia	                AUHAL.cpp:399   AUHAL: (0x12e82d040) Selecting device 68 from constructor
default	13:24:59.008452+0100	Synthesia	                AUHAL.cpp:572   SelectDevice: -> (0x12e82d040)
default	13:24:59.008462+0100	Synthesia	                AUHAL.cpp:629   SelectDevice: (0x12e82d040) not already running
default	13:24:59.008469+0100	Synthesia	                AUHAL.cpp:704   SelectDevice: (0x12e82d040) nothing to teardown
default	13:24:59.008476+0100	Synthesia	                AUHAL.cpp:708   SelectDevice: (0x12e82d040) connecting device 68
default	13:24:59.008572+0100	Synthesia	                AUHAL.cpp:3110  IsDeviceUsable: (0x12e82d040) Device ID: 68 (Input:No | Output:Yes): true
default	13:24:59.008663+0100	Synthesia	                AUHAL.cpp:718   SelectDevice: (0x12e82d040) created ioproc 0xc for device 68
default	13:24:59.008676+0100	Synthesia	                AUHAL.cpp:1454  UpdateStreamFormats: -> (0x12e82d040)
default	13:24:59.008743+0100	Synthesia	                AUHAL.cpp:1518  UpdateStreamFormats:
  output stream 0 [0x45]:  2 ch,  48000 Hz, Float32, interleaved
default	13:24:59.008754+0100	Synthesia	                AUHAL.cpp:1529  UpdateStreamFormats: 1 output streams; not all mono
default	13:24:59.008763+0100	Synthesia	                AUHAL.cpp:1539  UpdateStreamFormats:
  Output render format:  2 ch,  48000 Hz, Float32, interleaved
default	13:24:59.008773+0100	Synthesia	                AUHAL.cpp:1529  UpdateStreamFormats: 0 input streams; not all mono
default	13:24:59.008852+0100	Synthesia	                AUHAL.cpp:1604  UpdateStreamFormats: AUHAL(0x12e82d040) Calling PropertyChanged() for kAudioUnitProperty_StreamFormat, Scope:Output, Bus:Output
default	13:24:59.008863+0100	Synthesia	                AUHAL.cpp:1617  UpdateStreamFormats: <-
default	13:24:59.008943+0100	Synthesia	                AUHAL.cpp:822   SelectDevice: (0x12e82d040) removing 0 device listeners from device 0
default	13:24:59.008955+0100	Synthesia	                AUHAL.cpp:831   SelectDevice: (0x12e82d040) adding 6 device listeners to device 68
default	13:24:59.009097+0100	Synthesia	                AUHAL.cpp:822   SelectDevice: (0x12e82d040) removing 0 device delegate listeners from device 0
default	13:24:59.009108+0100	Synthesia	                AUHAL.cpp:831   SelectDevice: (0x12e82d040) adding 0 device delegate listeners to device 68
default	13:24:59.009115+0100	Synthesia	                AUHAL.cpp:844   SelectDevice: <- (0x12e82d040)
default	13:24:59.012474+0100	CAReportingService	    CAReportingService.mm:681   active reporting session { count=2, activeSessions="(
    "repID=5188320493569,sn=longformaudio,pid=1208,client=WhatsApp,app=WhatsApp,started=1,single=0,msg=68,smsg=0",
    "repID=2667174691069,sn=audiodeviceusage,pid=621,client=coreaudiod,app=com.synthesiallc.synthesia,started=1,single=0,msg=27,smsg=0"
)" }
default	13:24:59.014249+0100	Synthesia	                AUHAL.cpp:1713  SetStreamUsage: Output stream enables: Stream 0 is ENABLED
default	13:24:59.016117+0100	runningboardd	Acquiring assertion targeting [app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460] from originator [osservice<com.apple.powerd>:530] with description <RBSAssertionDescriptor| "App is holding power assertion" ID:627-530-124302 target:16460 attributes:[
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PowerAssertion" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	13:24:59.016191+0100	runningboardd	Assertion<PHONE_NUMBER>02 (target:[app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460]) will be created as active
default	13:24:59.027873+0100	runningboardd	Invalidating assertion 627-16460-124132 (target:[app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460]) from originator [app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460]
default	13:24:59.028002+0100	runningboardd	Acquiring assertion targeting [app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460] from originator [app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460] with description <RBSAssertionDescriptor| "AudioHAL" ID:627-16460-124303 target:16460 attributes:[
	<RBSDomainAttribute| domain:"com.apple.CoreAudio.HAL" name:"AudioHAL" sourceEnvironment:"(null)">
	]>
default	13:24:59.028059+0100	runningboardd	Assertion 627-16460-124303 (target:[app<application.com.synthesiallc.synthesia.55137401.55137407(501)>:16460]) will be created as active
default	13:24:59.038975+0100	CAReportingService	    CAReportingService.mm:681   active reporting session { count=3, activeSessions="(
    "repID=5188320493569,sn=longformaudio,pid=1208,client=WhatsApp,app=WhatsApp,started=1,single=0,msg=68,smsg=0",
    "repID=2667174691070,sn=audiodeviceusage,pid=621,client=coreaudiod,app=com.synthesiallc.synthesia,started=1,single=0,msg=1,smsg=0",
    "repID=2667174691069,sn=audiodeviceusage,pid=621,client=coreaudiod,app=com.synthesiallc.synthesia,started=1,single=0,msg=27,smsg=0"
)" }
default	13:24:59.343094+0100	KompleteSynthesia	order window: 1d66 op: 0 relative: 0 related: 0
default	13:24:59.358619+0100	runningboardd	Invalidating assertion<PHONE_NUMBER>00 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) from originator [osservice<com.apple.WindowServer(88)>:587]
default	13:24:59.359425+0100	runningboardd	Invalidating assertion<PHONE_NUMBER>01 (target:[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]) from originator [osservice<com.apple.WindowServer(88)>:587]
default	13:24:59.373018+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=7306.130, attribution={responsible={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, responsible_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, accessing={TCCDProcess: identifier=com.apple.open, pid=16654, auid=501, euid=501, binary_path=/usr/bin/open}, requesting={TCCDProcess: identifier=com.apple.sandboxd, pid=7306, auid=0, euid=0, binary_path=/usr/libexec/sandboxd}, },
default	13:24:59.382884+0100	tccd	AUTHREQ_SUBJECT: msgID=7306.130, subject=tillt.KompleteSynthesia,
default	13:24:59.384761+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x14567d350 at /Applications/KompleteSynthesia.app
default	13:24:59.392947+0100	tccd	AUTHREQ_ATTRIBUTION: msgID=7306.131, attribution={responsible={TCCDProcess: identifier=tillt.KompleteSynthesia, pid=16646, auid=501, euid=501, responsible_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia, binary_path=/Applications/KompleteSynthesia.app/Contents/MacOS/KompleteSynthesia}, accessing={TCCDProcess: identifier=com.apple.open, pid=16654, auid=501, euid=501, binary_path=/usr/bin/open}, requesting={TCCDProcess: identifier=com.apple.sandboxd, pid=7306, auid=0, euid=0, binary_path=/usr/libexec/sandboxd}, },
default	13:24:59.400290+0100	tccd	AUTHREQ_SUBJECT: msgID=7306.131, subject=tillt.KompleteSynthesia,
default	13:24:59.401578+0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier tillt.KompleteSynthesia, type: 0: 0x147220fc0 at /Applications/KompleteSynthesia.app
default	13:24:59.463967+0100	KompleteSynthesia	Entering exit handler.
default	13:24:59.463979+0100	KompleteSynthesia	Queueing exit procedure onto XPC queue. Any further messages sent will be discarded. activeSendTransactions=0
default	13:24:59.464020+0100	KompleteSynthesia	Cancelling XPC connection. Any further reply handler invocations will not retry messages
default	13:24:59.464621+0100	KompleteSynthesia	Exiting exit handler.
default	13:24:59.464634+0100	KompleteSynthesia	XPC connection invalidated (daemon unloaded/disabled)
default	13:24:59.464886+0100	WindowManager	Connection invalidated | (16646) Komplete Synthesia
default	13:24:59.470817+0100	runningboardd	[app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646] termination reported by launchd (0, 0, 0)
default	13:24:59.470940+0100	runningboardd	Removing process: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.471093+0100	runningboardd	Removing launch job for: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.471297+0100	runningboardd	Removed job for [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.472712+0100	runningboardd	Removing assertions for terminated process: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.472793+0100	runningboardd	Removed last relative-start-date-defining assertion for process app<application.tillt.KompleteSynthesia.55148837.55148842(501)>
default	13:24:59.509998+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: none (role: UserInteractiveFocal)
default	13:24:59.510535+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: none (role: None)
default	13:24:59.510806+0100	runningboardd	Calculated state for app<application.tillt.KompleteSynthesia.55148837.55148842(501)>: none (role: None)
default	13:24:59.512167+0100	runningboardd	XPC connection invalidated: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.512600+0100	launchservicesd	Hit the server for a process handle 177280e200004106 that resolved to: [app<application.tillt.KompleteSynthesia.55148837.55148842(501)>:16646]
default	13:24:59.518209+0100	loginwindow	-[PersistentAppsSupport applicationQuit:] | for app:Komplete Synthesia, _appTrackingState = 2
default	13:24:59.518248+0100	loginwindow	-[PersistentAppsSupport applicationQuit:] | App: Komplete Synthesia, quit, updating active tracking timer

pid 16458, MIDIServer
Can you try quitting that thing before trying KompleteSynthesia?

pid 16458, MIDIServer

Can you try quitting that thing before trying KompleteSynthesia?

I tried, but it's an Apple daemon and pops right back up.

Oh interesting - I'll look into that later...

Ok - I am just now realising that indeed MK2 is the problem.
#1st bug
The original intension was to allow for optional video mirroring for MK2 devices and beyond. The current code however makes its support mandatory. This isnt a big thing, I was tinkering with that just now until I realised...
#2nd never tested on MK1 and already know there will be issues
The control messages used for MK2 controllers differ from those for MK1 controllers when it comes to controlling buttons and their lighting. MK2 is there but MK1 never was implemented.
However, the basic lightguide support should be there - KompleteSynthesia should support MK1 and MK2 controllers alike.
I'll release a new version soon that makes the video support fully optional and thus might have a better chance working for you.

Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v0.53 and report back. Thanks a bunch for your help.

Oh, I made a bad mistake now - forget 0.53 - it is problematic.

Checkout https://github.com/tillt/KompleteSynthesia/releases/tag/v0.54 please...

Great, there's progress, the app launches now, detects the keyboard and I can see the notes coming up in the log:

Unfortunately, the lights still don't change on the keyboard though in any of the play modes 😿
I tried the troubleshooting steps like "Repair light configuration" and "Reset", but still no lights.
Is there a debug / verbose mode to get more logs? Or should I try to build the project in XCode so I can help debugging it?

Oh jeez - so sorry for that @daaain . I just never tested it with MK1 devices.
We see you receiving data from the LoopBe interface just fine. We also see no further error messages from the HID interface when detecting your controller or when sending an update of the lightguide to the controller; . That leaves us with a potential problem in the light-guide message itself. Are we using the correct command code for MK1 and are we encoding the colours correctly?  After now reviewing the code I once copied from, I can see the encoding KompleteSynthesia is using won't work for MK1 devices. This would need a slighty more involved update for the lightguide messages but also a more involved update for the colour selection in the preferences pane - as the MK1 devices did support a larger colour space. Worst part here is that I can't test things - so development will be slow. However, I would really love to support all breeds of Komplete Kontrol controllers, MK1,  MK2 and MK3.

Come on, no need to apologise, you don't owe me anything 😉
I can definitely try to contribute, haven't done Mac development, but it's a relatively simple app and I'm quite motivated to get it working with my keyboard 😸
I'll try to compile the app and see if I can get something going. Basically the job is to make sure the app is always in the right mode for each keyboard (and might need a bit of abstraction to make it work with MK3 in the future I guess?) and to double check the MK1 hex codes from the Python library, right?
One thing I noticed is that there's a ternary to choose between kCommandLightGuideUpdateMK2 and kCommandLightGuideUpdateMK1 here, but not here, could that be (part of) the problem?

There is hope; see https://github.com/tillt/KompleteSynthesia/pull/14.
I am now producing an alpha release for you to test. It definitely won't be perfect, but it might show some lightguide effect  for MK1 devices.
Things that I am already pretty sure that won't be perfect:

light intensity will be off: what should be darker, may be lighter and the other way around
initial rainbow swoosh won't work at all - possibly showing random appearing colors

Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v<IP_ADDRESS>

Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v<IP_ADDRESS>

Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v<IP_ADDRESS>

Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v<IP_ADDRESS>

This is it, with <IP_ADDRESS> I think the MK1 support is perfect (at least with my S49 and without the swoosh)!

A video might actually be super cool. I was also just wondering how we can point out this new feature. The video would have to be hosted somewhere - ie YouTube.
PR welcome!!! :D
Maybe you have a good idea on where to add your experience with a MK1 controller?
Then lastly, lets definitely add the following paragraph at the end of the README:
## Credits

Thanks for invaluable help in achieving MK1 compatibility and providing a demo, Daniel Demmel [@daaain].

Resolved by #14


Removed exclusion of tika-server-core from tika-server-classic

Was looking to spin a tika-docker for the 2.0.0-ALPHA (yay!) and saw the tika-server-classic isn't loading.
Good news is following this change my test suites in a couple of applications I use Tika in have pass nicely.
Updated tika-docker is ready to go once tika-server-classic is updated and republished.

Sorry @tballison - just noticed TIKA-3280 on the mailing list now. (I think I need more coffee!) If this change isn't helpful, just close the PR and I'll rebase to yours.

Sorry @tballison - just noticed TIKA-3280 on the mailing list now. (I think I need more coffee!) If this change isn't helpful, just close the PR and I'll rebase to yours.

Apologies are mine.  Go forth and fix!  Sorry and thank you!

Apologies are mine.  Go forth and fix!  Sorry and thank you!


[Impeller] Take advantage of pre-rotation in the Vulkan swapchain.

This is performance sensitive and we must follow the guidance in https://developer.android.com/games/optimize/vulkan-prerotation.

Followup from https://github.com/flutter/engine/pull/43214.


How to check or uncheck checkboxes inside an editor on button click

I have an editor with multiple columns..on that editor first column is checkbox column..and i have buttons like
'select all'-->when i click on selectall, all checkboxes should be checked
'deselect all'--->when i click on deselectall  all the checkboxes in the editor should be unchecked
can anyone suggest above behaviour on button clicks
thanks..

Checkboxes mixin for the grid has already this feature. Checkbox in upper left corner checks and unchecks all the rows.
I think you can get sample there?

Yes that was there...but how to achive that task on button clicks...because i have other buttons as well based
on each button click conditionally should load records


chore(deps): update wasmtime

Update to latest stable release of wasmtime
This time no API change affected us :partying_face:

@pkedy , @jsoverson: can you please take a look at this PR and, once merged do a bump and release of the wasmtime-provider?

Thanks as always @flavio 😊

@jsoverson no worries :smile:
Can you please tag a new release and publish it on crates.io?

thanks!


Styles prop or similar

This is a really sweet library, and works seamlessly with the MUI paging component.
The inner text on the low-res (mobile) view is very faint. It would not pass accessibility. It would be nice to be able to override this.

One solution is to override the styles with a css class
    ExpansionPanelDetailsTypographyProps=
    {
      {
        className: 'expanded-panel'
      }
    }


Memory leak

If you don't want to support the plugin, please write about it and I won't use your plugin that uses more than 6GB of RAM.

Please do not spam the same issue. You can check and download the latest version of JobsReborn.
This is not a bug, we can checked from the Spigot timings and tps and this plugin does not causes lag.


rewrote the friendly date range bonfire

This is a pretty extensive rewrite - changed test cases, solution code, and bonfire problem statement. But I think it's internally consistent and more clear now.
closes #1886

still trying to figure out how to pass tests...


Missing sound file

Just FYI, I get this when attempting to build the Swift example:
error: /Users/scottcondron/Developer/flomio_mw_releases/FlomioSDK/Assets/ScanSound.caf: No such file or directory

I think the issue might be bigger, though ... removed the reference and builds are still going haywire.

Are you still seeing this after https://github.com/flomio/flomio_mw_releases/issues/3 is resolved?

Nope -- might want to just add notes in your Readme for both these issues, that is:

Podfile can't include use_frameworks!
Need to run pod install on the downloaded example project

Oops ... I guess the second one is already there 😁

👍 Thanks for your suggestion. I will add "Podfile can't include use_frameworks!".


Problems with create-sst@latest

I've been having allsorts of problems running create-sst@latest, broken dependencies on fundamental things like @babel/core and quitting out in the middle of deployments with no error messages.
I tried different starter templates but all seemed to have different (but similar) issues.
I looked in npm and the latest tag is actually pointing at version 0.0.0-20221215185326. If I run<EMAIL_ADDRESS>which looks like the latest "proper" version number it all seems fine. I wondered if the tag is wrong?

I'm also facing the same problem.

Also facing issues

Oof thanks for pointing it out. Taking a look.

this has been fixed thanks for pointing it out


Fixes

Hello @swapsha96! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file setup.py:

Line 35:1: E402 module level import not at top of file


true is an unsupported argument for newer versions of Redis gem.

Newer version of the Redis gem don't support passing in TrueClass.
Previously the Redis client would change these into string "true"
Unsupported command argument type: TrueClass
/usr/local/bundle/ruby/2.7.0/gems/redis-client-0.17.0/lib/redis_client/command_builder.rb:75:in `block in generate'
/usr/local/bundle/ruby/2.7.0/gems/redis-client-0.17.0/lib/redis_client/command_builder.rb:68:in `map!'
/usr/local/bundle/ruby/2.7.0/gems/redis-client-0.17.0/lib/redis_client/command_builder.rb:68:in `generate'
/usr/local/bundle/ruby/2.7.0/gems/redis-client-0.17.0/lib/redis_client.rb:236:in `call_v'
/usr/local/bundle/ruby/2.7.0/gems/redis-5.0.7/lib/redis/client.rb:90:in `call_v'
/usr/local/bundle/ruby/2.7.0/gems/redis-5.0.7/lib/redis.rb:167:in `block in send_command'
/usr/local/bundle/ruby/2.7.0/gems/redis-5.0.7/lib/redis.rb:166:in `synchronize'
/usr/local/bundle/ruby/2.7.0/gems/redis-5.0.7/lib/redis.rb:166:in `send_command'
/usr/local/bundle/ruby/2.7.0/gems/redis-5.0.7/lib/redis/commands/strings.rb:169:in `msetnx'
/usr/local/bundle/ruby/2.7.0/gems/redis-namespace-1.11.0/lib/redis/namespace.rb:564:in `wrapped_send'
/usr/local/bundle/ruby/2.7.0/gems/redis-namespace-1.11.0/lib/redis/namespace.rb:521:in `call_with_namespace'
/usr/local/bundle/ruby/2.7.0/gems/redis-namespace-1.11.0/lib/redis/namespace.rb:395:in `block (2 levels) in <class:Namespace>'
/usr/local/bundle/ruby/2.7.0/gems/resque-2.6.0/lib/resque/data_store.rb:65:in `method_missing'
/usr/local/bundle/ruby/2.7.0/gems/resque-workers-lock-2.0.1/lib/resque/plugins/workers/lock.rb:62:in `before_perform_workers_lock'

@arianf Thanks for the PR and sorry for the slow reply! I have submitted this now as a new major version to rubygems: resque-workers-lock (3.0.0)
If you would be able to test if it all works now (it should autoload now as well: https://github.com/bartolsthoorn/resque-workers-lock/pull/11), that would be amazing!


Add avatar rotation facilities

Somehow the image on iPhone5 is rotated the wrong way, so adding rotation could help.

Actually, it would be better to take the EXIF data into account:
http://stackoverflow.com/questions/13971491/captured-photo-automatically-rotated-during-upload-in-ios-6-0-or-iphone
http://stackoverflow.com/questions/19463126/how-to-draw-photo-with-correct-orientation-in-canvas-after-capture-photo-by-usin
http://stackoverflow.com/questions/16336158/wrong-orientation-when-image-captured-by-html5-file-api-on-ios-6-0


Minor v5 release?

Would it be possible to potentially cut a 5.2.1 release of react-router-dom from what's currently on master? There's some accessibility changes that were merged to master back in July and we're hoping to get it included without having to lock the package to a commit hash.
Thank you.

Without tagging maintainers I'm just bumping this because there is a need for a new minor release if possible.

Sorry to tag you @timdorr, would it be possible to look at cutting a minor release of v5? Specifically looking to see if the PR you merged for me last summer might get a tag so that I can more cleanly close our an accessibility issue on a project I work on. Thank you.

Sorry to tag you @timdorr, would it be possible to look at cutting a minor release of v5? Specifically looking to see if the PR you merged for me last summer might get a tag so that I can more cleanly close our an accessibility issue on a project I work on. Thank you.

We do releases via CI and I'm not 100% sure if Travis is working at the moment (with all their OSS changes, in particular). I'd like to get that into GitHub Actions, but I don't have access to the token that's stored in Travis. My hands are kind of tied at the moment.

We do releases via CI and I'm not 100% sure if Travis is working at the moment (with all their OSS changes, in particular). I'd like to get that into GitHub Actions, but I don't have access to the token that's stored in Travis. My hands are kind of tied at the moment.

Thanks for the insights on that. Looks like I'll lock our packages file to a commit hash in the meantime.

Thanks for the insights on that. Looks like I'll lock our packages file to a commit hash in the meantime.

The last release on master was in May of last year and there have been more PRs merged to master since I last poked at this request for a minor release at 5.2.1. In addition, and something I hadn't noticed, @anied in #7794 noted that the updates on master are on the docs in prod despite not being included in a release as of yet causing expected behavior to not match actual behavior.
moved this comment here as I had originally posted it on the merged PR

@mjackson Do you have any updates? And maybe publish something which informs the community about the future of the project because currently it doesn't seem to be actively maintained anymore.

If there isn't a minor release coming could someone please point me in the direction on how to include the latest master commit into my project? Since there isn't an included set of built files on master it seems that I need to do some form of postinstall process to make it build the project for me and I cannot get it figured out. Thank you.

Closing because we've cut a few new releases for the v5 branch, and will continue doing so as the need arises.

@chaance thank you for the update!


chore: update incubator-kie-sonataflow-devmode image to latest

Former image on quay is 5 months old.

/lgtm


Method for checking autoincrement

Is there a method for checking if the column is autoincrement?

Done, solved it using query model in behaviors.


(trivial) fix several minor golint style issues

A list of golint issues fixed -
notifier:
notifier.go:45:1: comment on exported type Notifier should be of the form "Notifier ..." (with optional leading article)
notifier.go:64:1: comment on exported type Options should be of the form "Options ..." (with optional leading article)

promql:
lex.go:85:1: comment on exported const LowestPrec should be of the form "LowestPrec ..."
parse.go:515:9: if block ends with a return statement, so drop this else and outdent its block (move short variable declaration to its own line if necessary)

storage/remote/graphite:
client.go:54:9: should omit 2nd value from range; this loop is equivalent to `for l := range ...`

@fabxc

Thanks!


[DatePicker] Unable to handle lower case month names

Hi,
I've been trying for over a day to get the date picker to work and it's just not happening.
If I type in a date say "01-aug-2015" in a date picker field, the parser does not recognise this as a valid date. The regex is case sensitive it would seem on investigation of the code in version 0.13.3. So it doesn't recognise "aug" as being "Aug".
It's very frustrating! Any fixed, workaround or anything else for this. I notice even on the demo page when you type in a date without the upper case first character it also appears to find this invalid. Perhaps it's something straight forward?
Please help!

This uses the formats in SHORTMONTH, as found here in Angular.

I do not believe this is a bug, as this mirrors the behavior in Angular itself, and I am not sure this is something worth changing.
Note that the dateParser service can be overridden by the user to support any desired formatting rules, so one can override this on an app level basis.

+1
I am having the same issue, but in uppercase manual input format: 23NOV15. Date input is not validated.
It is strange that this is not configurable through the date-format="ddMMMyy". It's not that it's a 'bug', but rather a missing feature imho. Angular is too restrictive not supporting uppercase/lowercase date formats.
If overriding the dateParser does the trick, any suggestion on how to approach this?

:+1:
@wesleycho I do not think this should have been closed.  This seems like a valid use case.  People when typing into a datepicker are NOT going to type in proper capitalization the way the Angular developers typed in the Month short names (with a capital first letter and lower rest).  They're GOING to type in all lowercase (or uppercase if their caps lock is on).
The problem does NOT lie in Angular itself; the problem is the simple way in which dateParser builds its regex text for short month names (and also full names, too).  It simply takes the names from and joins them with pipes $locale.DATETIME_FORMATS.MONTH.join('|').  What it SHOULD do is act on each of those month texts and "massage" them into supporting case insensitivity.
I hacked in some extremely ugly code, just to prove it is possible:
in the formatCodeToRegex section for 'MMM' i made it call my function to massage the month names:
regex: makeArrayTextCaseInsensitiveForRegex($locale.DATETIME_FORMATS.SHORTMONTH).join('|'),
then here is that function
function makeArrayTextCaseInsensitiveForRegex(textArray) {
	var letters,
		letter,
		newArray = [];

	textArray.forEach(function (textArrayItem) {
		letters = '';
		for (var i = 0; i < textArrayItem.length; i++) {
			letter = textArrayItem.charAt(i);
			letters += '[' + letter.toLocaleUpperCase() + letter.toLocaleLowerCase() + ']';
		}
		newArray.push(letters);
	});

	return newArray;
}

For those who have the same problem, I managed to override the parser of uibDateParser to handle non-case sensitive month matching:
angular.module('app').run(['uibDateParser', function(uibDateParser) {
  var format = 'dd-MMM-yyyy';
  // Triggers creation of the parser
  uibDateParser.parse('01-Jan-2000', format);

  // Override parser
  var parser = uibDateParser.parsers[format],
      regex = '(' + [
        parser.map[0].matcher,
        parser.map[1].matcher + '|' + parser.map[1].matcher.toLowerCase(),
        parser.map[2].matcher
      ].join(')-(') + ')',
      apply = parser.map[1].apply;

  parser.map[1].apply = function(value) {
    value = value[0].toUpperCase() + value.substring(1);
    apply.call(this, value);
  };
  parser.regex = new RegExp('^' + regex + '$');
}]);


Convert CLJX to CLJC

It's a pretty straightforward change. I also updated some dependencies.

Can someone, @imikushin or @ptaoussanis maybe, check the cljs side of this? I've still yet to write a cljs hello world so I can't really verify appropriately. I'll check out the clj side though, and if that's good, I'm fine to merge.

I'm going to merge to make this easy to verify, and we'll do a release when I get the lgtm on cljs

@jaycfields Hi Jay, my apologies - won't be able to help you confirm. Don't have any Cljs projects setup for Expectations atm.

no worries @ptaoussanis, given the support to this point, I don't blame you. :)

No problem, might try again when I have some free time - would definitely like to see it working.
Good luck!

@plexus when I run lein expectations I can't seem to get it to pick up the success examples.
I opened things up in emacs and I am able to run there using expectations-mode, and I see a failing test:
failure in (success_examples.cljc:244) : success.success-examples
           expected: :a-rebound-val
                was: nil

I'll have a look. Which version of expectations-mode are you using? I tried this one earlier, but it seems to no longer work with present-day cider.
https://github.com/gar3thjon3s/expectations-mode

I have no idea honestly, probably one that's a few years too old.
It's probably better for everyone if we get it working with "lein-expectations "0.0.8"" and ignore expectations-mode :)

I'm a bit out of my depth figuring out how the test suite is set up...
This is what I get when I run lein expectations
± lein expectations
WARNING: success.success-examples:175 modified #'success.success-examples-src/an-atom from "atom" to "atom"
WARNING: success.success-examples:182 modified #'success.success-examples-src/an-private-atom from "private-atom" to "private-atom"
WARNING: success.success-examples:189 modified #'success.success-examples-src/an-atom from "atom" to "atom"
WARNING: success.success-examples:196 modified #'success.success-examples-src/an-private-atom from "private-atom" to "private-atom"
yeah, you're done.

Ran 70 tests containing 70 assertions in 56 msecs
0 failures, 0 errors.

I assumed those were all the tests. How many should I be seeing?
Is there a way to change the output format to see the names of all the tests that ran?
Is there a wrapper that runs failure-examples and checks that they all fail, or does one verify manually that none of those pass?
what's up with the JUnit stuff?

Sorry for the many questions! Any answers at all would be greatly appreciated!

lein-expectations seems to run fine, it picks up all tests in success.success-examples (59) and success.nested.success-examples (11).
The error indicates a missing in-context function which is defined in success.expectations-options, so it's probably that that namespace isn't being loaded by expectations-mode.
There are also tests in test/expectations/expectations_expectations.clj which are not being picked up, but they rely on a method that's been deleted for some time (compare-args), so I'm guessing they are vestigial?

I used to run things with lein expectations success.* and see everything passing, and then lein expectations failure.* and see a failure or error for each assertion. I got the failures running with https://github.com/jaycfields/expectations/commit/e2b1623d74a982d0b7085dd71dc6862bcda518e5
I'm not sure why I'm not seeing the successes. I'll try a fresh checkout.
output all namespaces: I think that's possible, but I honestly don't remember how and can't find the PR with the example.
ignore junit, if anyone ever reports it as broken I'm going to delete it. Until that happens I'm just assuming all is well. :)

There are also tests in test/expectations/expectations_expectations.clj which are not being picked up, but they rely on a method that's been deleted for some time (compare-args), so I'm guessing they are vestigial?

Correct. I just pushed a commit that at least gets everything green. (for that ns)

I just checked out a fresh copy and I'm still not seeing the success tests running
Ran 45 tests containing 45 assertions in 300 msecs
43 failures, 2 errors.

Those are all the failures. I'm trying to think of an environment change that I might have, but nothing comes to mind.

@jaycfields is this with expectations-mode or how are you running the tests? Could you try the aliases in #72?

I'm ignoring expectations-mode, I'm just running using lein expectations. At least I was, I just tried lein test and I get
lmp-jfields02:expectations jfields$ lein test

Ran 6 tests containing 6 assertions in 24 msecs
0 failures, 0 errors.

Even my fresh checkout gives that..

$ lein --version
Leiningen 2.5.1 on Java 1.8.0_45 Java HotSpot(TM) 64-Bit Server VM

It seems in your case it only ever picks up one namespace. No idea what could be causing that.
I did a rm -rf ~/.m2 and cleared out ~/.lein/profiles.clj, and it still runs ok...
I did have a type in the invocation of test-fail, I just repushed my branch.
$ lein test
<warnings>

Ran 76 tests containing 76 assertions in 75 msecs
0 failures, 0 errors.

$ lein test-fail
<failures>

Ran 45 tests containing 45 assertions in 339 msecs
43 failures, 2 errors.

$ lein -v
Leiningen 2.6.1 on Java 1.8.0_77 Java HotSpot(TM) 64-Bit Server VM

Maybe a third opinion would be good? Could someone try to run this and report back?
git clone -b run-test-alias git@github.com:plexus/expectations.git
cd expectations
lein test-fail
lein test

I have a second laptop here and it looks good there, so don't worry about it anymore.
Can you send me a PR for the typo fix?


Refactor some functions in Schwarzschild and Kerr class

🐞 Problem
calculate_trajectory() and calculate_trajectory_iterator() in both metric/schwarzschild.py and metric/kerr.py have become a mess. Refactoring is required.
🎯 Goal

Refactor them such that both cyclometic and cognitive complexity remains low.

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #113
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Can I take this issue?

Can I take this issue?

Could you discuss it here how you aim to tackle the problem?

@ritzvik I'd like to work on this issue. :) I'll think about how to implement this and get back to you. Meanwhile, can you please assign this to me?

Hi I hope to be a new contributor at some point but I was quite confused by this issue.  Why is there seperate geodesic solvers for each metric?  Wouldn't a generic solver which takes in a metric class be best?  I've implemented something similar in C in the past:
https://github.com/jaime-varela/Geodesic-solver

Hi I hope to be a new contributor and I was a bit confused on this issue.  Why is there a seperate ODE integrator for each metric?  Wouldn't a generic integrator which takes in a metric class be best?
I implemented basic prototype like this in C in the past:
https://github.com/jaime-varela/Geodesic-solver

Solving geodesic equations with arbitrary initial positions & velocity requires 2 things, Christoffel Symbols and a tensor which is differential of Metric Tensor w.r.t. each component(time and space). So we have to explicitly define these 2 tensors also, apart from the metric tensor.
Also calculating Schwarzschild Geodesics is much simpler because the Christoffel Symbols are 0 at most of the indices. Same for Kerr upto a lesser extent. A generic solver would not try to leverage these features.
These problems do not allow us to implement a generic solver.

Any idea how to generalize things without losing significant performance is welcome :)

Hi I hope to be a new contributor

Thanks for your interest @jman27182818 ! You are more than welcome :)

@jman27182818 Come, drop a hi at https://riot.im/app/#/room/#einsteinpy:matrix.org or https://gitter.im/EinsteinPy-Project/EinsteinPy . These are our community chatrooms and both are bridged!


Web API: closed_at field null even though ticket is closed.

Gitea version (or commit ref): bc42b3a
Git version: 2.11.0
Operating system:
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL): https://try.gitea.io/api/v1/repos/rakshith-ravi/test/issues/2
[ ] No
[ ] Not relevant

Log gist:

Description
When closing an issue, the closed_at field in the API request is null even though the issue inside the issue tracker is closed.
Example:
{"id":4321,"url":"https://try.gitea.io/api/v1/repos/rakshith-ravi/test/issues/2","number":2,"user":{"id":9467,"login":"Test","full_name":"","email":"test@noreply.example.org","avatar_url":"https://secure.gravatar.com/avatar/f10679d1743e9ff23ac5dd72d5bf71d8?d=identicon","language":"de-DE","username":"TestJinInQ"},"title":"test","body":"test","labels":[],"milestone":null,"assignee":null,"assignees":null,"state":"closed","comments":0,"created_at":"2018-12-02T15:25:48Z","updated_at":"2018-12-02T15:28:22Z","closed_at":null,"due_date":null,"pull_request":null}
closed_at == null.
Expected:
{"id":4321,"url":"https://try.gitea.io/api/v1/repos/rakshith-ravi/test/issues/2","number":2,"user":{"id":9467,"login":"Test","full_name":"","email":"test@noreply.example.org","avatar_url":"https://secure.gravatar.com/avatar/f10679d1743e9ff23ac5dd72d5bf71d8?d=identicon","language":"de-DE","username":"TestJinInQ"},"title":"test","body":"test","labels":[],"milestone":null,"assignee":null,"assignees":null,"state":"closed","comments":0,"created_at":"2018-12-02T15:25:48Z","updated_at":"2018-12-02T15:28:22Z","closed_at":2018-12-02T15:28:22Z,"due_date":null,"pull_request":null}
closed_at == updated_at == 2018-12-02T15:28:22Z

Could I take a look at this one if no is already working on it?


Allow user-defined values in the step_state to propagate across iterations

This change allows to take values which remain unchanged in comparison to the result of the previous iteration and pass them to the next iteration. It can be useful in cases, when custom loop handlers keep some data in training state (for instance, minimum or maximum loss).

Thanks! I think this is valuable. Can you please write a test or 2 ensuring user defined values are actually preserved?

Added a couple of tests for checking that user-defined values in step_state are actually propagated, but somewhy there are still failed checks. Unfortunately, the proposed solution only deals with numerical data for user-defined values; if we try to pass a value of another type (string, for instance), it will fail. Actually I have an idea on how to allow passing values of any types, but it would require more modifications not only in the axon library, but in the nx dependency as well. So, it's unclear would it be appropriate or not.

The failed checks seemed to be transient, thanks :D


Task/piv 259 replace request library

Replace deprecated request library with axios.
Related story: https://vasdvp.atlassian.net/browse/PIV-259

On-hold until we have cycles to review best-practices and to add more comprehensive tests.


Post-update hook unable to find vim-doge function

Post-update hook is unable to find doge#helpers#deepextend when using
Plug 'kkoomen/vim-doge', { 'do': { -> doge#install() } }

Manually running :call doge#install() afterwards works just fine.
This seems to be related to #964. See also my comment in a related issue on the vim-doge repo.

NVIM v0.6.0
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-prot
ector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/wo
rk/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az65-618

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/home/runner/work/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

Run :checkhealth for more info

Type:

[x] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[x] Linux
[ ] OS X
[ ] Windows

Vim:

[ ] Terminal Vim
[ ] GVim
[x] Neovim

It seems like a neovim bug. PlugInstall works well at vim.

It seems that recent nvim ignores paths that are not existent at the moment of setting rtp. So post-update hook fails for freshly installed plugins, while it works for updated plugins.
Refreshing rtp before running the post-update hook worked for me.
@@ -1031,6 +1031,7 @@ function! s:is_updated(dir)
 endfunction

 function! s:do(pull, force, todo)
+  let &rtp = &rtp
   for [name, spec] in items(a:todo)
     if !isdirectory(spec.dir)
       continue

Relevant neovim issue: https://github.com/neovim/neovim/issues/18822

Fixed by https://github.com/junegunn/vim-plug/commit/2f8f04cf79f424aab8c2372d8e0b89099e3dba65


Incorrect validation error after only changing the date

I have a component configured as follows
<px-rangepicker id="datetimePicker" date-format="YYYY/MM/DD" time-format="HH:mm:ss" range="{{range}}" hide-presets="true"></px-rangepicker>

where the range is 2016/11/11 16:07:00 to 2016/11/11 16:10:00
The following steps lead to an incorrect validation error:

Open the picker
Click 10th November. The range is correct flagged invalid as from > to.
Click 10th November a second time. The range is still marked as invalid even though from < to as shown below.

Thanks for your feedback, we'll have to prioritize this issue and investigate

Hi,
Thank you for helping us make Predix UI better.
We have fixed this issue on v0.5.6 of px-calendar-picker. https://github.com/PredixDev/px-calendar-picker/releases/tag/v0.5.6

Thanks


Align upstream 30-01-24 and merge

Aligning with cherry-picks and running a git merge to have the repo aligned with upstream.
From now on we can do merges instead of cherry picks (hopefully)

/retest

/retest


Rename state file; update state file after each CI system finishes

After this PR is merged, the git add command in the tinuous-inception workflow will need to be updated.

Codecov Report

Merging #100 (0204973) into master (b4f1a5e) will increase coverage by 1.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #100      +/-   ##
==========================================
+ Coverage   72.95%   74.15%   +1.20%
==========================================
  Files           9       10       +1
  Lines         821      863      +42
  Branches      121      127       +6
==========================================
+ Hits          599      640      +41
+ Misses        179      178       -1
- Partials       43       45       +2

Impacted Files
Coverage Δ

src/tinuous/__main__.py
58.19% <100.00%> (-0.45%)
:arrow_down:

src/tinuous/state.py
100.00% <100.00%> (ø)

src/tinuous/github.py
54.59% <0.00%> (-2.56%)
:arrow_down:

Continue to review full report at Codecov.

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


feat(helm:create): allow absolute paths when specifying starter template path [dev-v3]

What this PR does / why we need it:
If starter template path is an absolute path, it shouldn't be prefixed with c.home.Starters() but rather be used as is. This way we can use templates that might not be in home directory but inside a specific project.
PR to master branch is #5978
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@bacongobbler dev-v3 version of #5978

@mentos1386 Thanks for the contribution


Allow password to be specified for redis

Is your feature request related to a problem? Please describe.
https://github.com/apache/superset/blob/master/helm/superset/values.yaml says you can set a password for redis. (search for Redis password)
However, the superset helm chart does not appear to accept a redis password configuration.
See https://github.com/apache/superset/blob/master/helm/superset/templates/_helpers.tpl#L60 and
https://github.com/apache/superset/blob/master/helm/superset/templates/secret-env.yaml
Describe the solution you'd like
Helm chart modified to allow passwords.
Describe alternatives you've considered
Redis can be locked down in a VPC. This doesn't completely eliminate the need for passwords but it helps protect it.
Additional context
Related issue: https://github.com/apache/superset/issues/13541

Related PR: https://github.com/apache/superset/pull/8420/files (for just docker though, it doesn't include the helm chart)

You missed something: https://github.com/apache/superset/pull/14274/files#issuecomment-827038300

@robdiciuccio there's a minor change left (see above). Can this be reopened please? If you want I can create another ticket.


Signing option for ProductName argument

Signtool.exe has '/d' argument for ProductName that is being displayed in the UAC. What is the equivalent option for msbuild based signing task ? How and what argument do I need to pass to achieve this ?
Signtool.exe :
https://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.110).aspx
/d  Desc
Specifies a description of the signed content.

My build definition uses Signing Plugin and MSBuild 15.0 of microbuild toolset nuget package.

This issue doesn't repro anymore.


Checkpoints for Glove-Based and different Models

Hey, Thanks for creating such an amazing library. May I know if there are pretrained checkpoints or models available for Glove based APC models. If not I would be training them and would like to share the checkpoints as well

Hi, we dont provide GloVe based checkpoint yet, we will be appreciated for your contribution, e.g., shares of checkpoint and test code in many situations to help stabilize the code.

Thanks, will try to contribute to the project


Chorus

Added multiple channel support.
It's a bit messy at the moment with lots of setters all over the place. That'll be resolved easily.
For now spatializing the different channels is up to the user to do.
It might be prudent to add some simple modes that can spatialize for you.
Something like  Process(float in**, out**) as well as an interleaved version of the same.

Added multiple channel support.
It's a bit messy at the moment with lots of setters all over the place. That'll be resolved easily.
For now spatializing the different channels is up to the user to do.
It might be prudent to add some simple modes that can spatialize for you.
Something like  Process(float in**, out**) as well as an interleaved version of the same.

Examples seem good, but the changes to delay time are a bit noisy. They should get smoothed out with fonepole at audio rate. not all controls need this treatment; just the ones that are a bit scratchy while being turned. (Petal/Field).
While you're in there, I'd also say make the frequency control for the modulation LFO go a bit higher (maybe max 20Hz or something for now?).
Otherwise, seems good to go.


SSDs: wording, added information on form factors

SSDs: fixed wording, added information on form factors

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

@VegaDeftwing Thank you very much for submitting a PR! I have done some basic editing and merged your changes. Happy Hacktobefest! ☀


Use or delete error models

Currently error models are not used. Errors are raised with raw responses instead. Consider if using the models is beneficial. If so, implement the usage, otherwise delete the models.

The models will not be parsed, but used directly from the response contents. PlayerErrorReason remains.


JS error in example

When I load a msg file on the demo page: https://ykarpovich.github.io/msg.reader/examples/example.html
I get:

TypeError: fileData.body.substring is not a function[Learn More] example.html:141:33

Using FireFox 66.

It appears to only give the error with a particular email. I tried another email and it worked.

Weird.. I'm getting weird bugs. I'll try to supply a sample file, but I don't want to share the email that is giving the error....

It's so strange...
I've double-checked with Chrome 73 and Firefox 66.0.2. I have no one error.
I guess only email example (maybe dummy, but with error as original) helps us to solve the problem.

I'm sorry, I can't recreate the error with a non-confidential email. I'll post one if I can find one at a later date.

I'm also facing the same issue, Unit8Array is returned as body. please find attached for sample email with the issue.
3113.xlsx.zip

@jagant11 @adjenks
Please try this version
https://ykarpovich.github.io/msg.reader/examples/example.html

I think it appears to work. I'm not sure if I'm using the same email I tested with before, but I haven't had trouble with any. Before I had trouble with several.


Future builder enhancements

This PR adds three parameters to the FutureBuilder.
listen: Adds the ability to trigger side effects outside of the build cycle whenever the future state changes
onPending: Widget builder that is called when the future is pending
onError: Widget builder that is called when the future throws
Refer to issue https://github.com/flutter/flutter/issues/87399.
Pre-launch Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I signed the [CLA].
[X] I listed at least one issue that this PR fixes in the description above.
[X] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[X] All existing and new tests are passing.

so the builder is only called when there is data ?

@cedvdb If you use onPending and onError. It would be appropriate to also have onComplete there as well

Yes I agree but then it renders the original builder useless. Which honestly I find more readable.

@cedvdb It renders the original builder useless only if you use the onX methods. So you would be able to to use the FutureBuilder the way you preferred. Why do you find the builder more readable? I feel like onComplete, onPending, and onError are much easier to understand and read than various if statements comparing conditions on an AsyncSnapshot.
I agree that the Flutter team most likely would want to keep the builder method for various reasons, one primary reason is to be consistent with builder widget types. That is why it is not deprecated in the PR

I feel like onComplete, onPending, and onError are much easier to understand and read than various if statements comparing conditions on an AsyncSnapshot

That's what I meant

I don't think FutureBuilder needs this. while I don't like using Snapshots and ConnectionState I don't think changing FutureBuilders API is a good idea and having multiple ways of doing the same thing is overall a bad practice. maybe instead we need another more intuitive FutureBuilder widget.

@goderbauer Thanks for your review comments! The link above should give you some context about this PR. I also want to note that this PR is intended as a rough draft and as such does not have tests (one of the reasons I marked this as a draft PR).
@luca-venir Brought up two issues they were having with FutureBuilder. Which can be summed up as follows
1st: It is not straight forward on where to put business logic when using FutureBuilder. While it is possible to listen to the future outside of the build method initState for example, it is argued that a listen method on the FutureBuilder should be added as an easy way to add non-ui specific logic. This is the reasoning behind listen
2nd: The builder and AsyncSnapshot combo is confusing when first approaching FutureBuilder. The expected interface would be one that is more parallel to the possible states of a Future instead of a generic asynchronous representation (AsyncSnapshot). This is the reasoning behind onError, onComplete, and onPending.
I'd like to point out that while I have some opinions on the changes, I am not the originator of the ideas above. I was more interested in implementing them and possibly jumped the gun by creating a draft PR.

@goderbauer I worry that too many people are assuming that this PR is a source of truth and the intended implementation of https://github.com/flutter/flutter/issues/87399. It was merely a prospective first attempt and a place to discuss the specific implementation, thus the "draft" status. I think discussion on API design and use cases would be more appropriate at the https://github.com/flutter/flutter/issues/87399 thread. Unless you have any argument otherwise I will close this for the time being

listening to a future in the initState is inconvenient because you need a stateful widget.

listening to a future in the initState is inconvenient because you need a stateful widget and disposing of said future, while if you already have a future builder that logic is handled for you

Hello there,
this is another problem in FutureBuilder, I guess the best place to discuss this is #87399. Unluckily, when a Future has to be dealt with (i.e. fired) into a Provider state-management solution, the Widget has to be stateful from my understanding. Otherwise, if the future is fired inside the build method, the async call will be fired at every re-build.


Exercises are slow to Render due to high number of bookmarks

When we changed the scheduled bookmarks, I didn't look too much into the performance of the top_bookmarks_to_study but I was testing a user with about 1900 total bookmarks, and it takes around 30 seconds for us to render the first exercise in the web, which made me wonder what are the total number of "fit to study" bookmarks we are working with.

It does seem that our average user has 105 bookmarks, but there is quite a few (> 300) that have more than 200 bookmarks.
This makes me think that it might be better to limit the query and order it already from the database, rather than doing it in python. I would expect that to improve the speed of the query overall.

Doing everything in the DB and also adding indexes if needed should definitely be the way to go :)

Yes, I will look into it - I will try to write the query in SQLAlchemy and see how it improves the query speed,

one order of magnitude improvement. nobody can complain about that :)


Revert user id refactor

Summary of Changes
Revert the user id refactor as 1. the FE didn't change together; 2. backward incompatible change which requires version bump; 3. the follow/owner other api still refers user_id instead id which is inconsistent.
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #111 into master will decrease coverage by 0.57%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #111      +/-   ##
==========================================
- Coverage   70.45%   69.88%   -0.58%
==========================================
  Files          21       21
  Lines        1029     1016      -13
  Branches      106      106
==========================================
- Hits          725      710      -15
- Misses        277      279       +2
  Partials       27       27

Impacted Files
Coverage Δ

metadata_service/proxy/atlas_proxy.py
85.08% <100%> (+0.38%)
:arrow_up:

metadata_service/proxy/gremlin_proxy.py
44.61% <100%> (-0.17%)
:arrow_down:

metadata_service/proxy/base_proxy.py
67.3% <100%> (+0.03%)
:arrow_up:

metadata_service/api/user.py
71.42% <100%> (-28.58%)
:arrow_down:

metadata_service/proxy/neo4j_proxy.py
73.43% <100%> (-0.1%)
:arrow_down:

Continue to review full report at Codecov.

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


Update data-adapter-mixin.js

Fix incorrect docs about headersForRequest being used for ember-data versions >= 2.7.
This is on hold until https://github.com/emberjs/rfcs/pull/171 gets resolved

@marcoow you mean specifically pointing to https://github.com/emberjs/data/pull/3099 and not only to https://github.com/emberjs/rfcs/pull/171 ?

@bartocc: sorry for the delay - I meant linking to the feature flag: https://github.com/emberjs/data/blob/master/FEATURES.md#feature-flags

updated @marcoow

Argh, I messed up rebasing…
Can you rebase on master?

I've lost the commits ... and since I edited them on GH, I don't have the in a local repo. Would you have a previous SHA by any chance ?

Sorry for that - created a replacement: #1366


Change Intel Debug flags for MOM6

This PR changes the Intel Debug flags for MOM6 (and FMS). The issue seems to be that -check all,noarg_temp_created is "too much" for MOM6 (and FMS). So, this change "degrades" the Intel flags to be -check bounds,uninit which matches the Intel Debug flags GEOS used to use before ESMA_cmake v.3.14.
Note this has a companion PR in FMS as both need to degrade: https://github.com/GEOS-ESM/FMS/pull/16

Note to @sdrabenh I will be testing these PRs for the AMIP modes. @sanAkel will do some mom5 and mom6 tests. This should not affect either Release or Debug results for AMIP as far as I can tell. Not sure about mom5/6 but @sanAkel will let us know

Check following coupled model runs

debug build, not checking for zero-diff. (When debugging zero-diff is not needed.)

[ ] MOM5
[ ] MOM6

optim build:

MOM5:

[ ] runs
[ ] zero-diff

MOM6:

[ ] runs
[ ] zero-diff

I'll add my own checkbox tree. Checked box means zero-diff.

Release build

[ ] No Replay, 1 day, c48
[ ] Replay, 1 day c48

Debug build

[ ] No Replay, 1 day, c48

Agreed. All the AMIP tests seemed good as well. Even the Debug runs were zero-diff, so I guess none of the check flags affect the answers (as well they shouldn't!).

I'll get a new release of FMS out as well.

A new FMS has been released. I updated the FMS version in my meta "remove externals" PR (https://github.com/GEOS-ESM/GEOSgcm/pull/230) as I figure it's easier to pull in one PR rather than 4 or whatever. 😄