Seems to exit before selecting character.

I used to manually log in to a couple of accounts before i found this tool but so far it doesn't seem to trigger the daily chests. I skipped logging in to one account manually for a day and just used alternator but the next day it had fallen behind a day on the achievement tab. I also kept an eye on the inventory using the api on another account with stacked chests and logging in doesn't deposit the chest to the inventory.
It seems like it exits the game too fast. When i click on login with an account selected, the launcher opens, logs in, "auto play" counts down, the screen flashes and it says "Completed".
Here's from the metrics log:
Started	2022-05-03	21:23:31
Total Time	14,4510399	s
Account	Start	Authenticate	Login	Enter	Exit
Alt 1	0.420833	2.0357994	7.332667	2.4397757	0.2081271

Here's the relevant part from the debug-log:
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|Max GW2 Instances=5
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=1 SC=1 CS=1 FC=0 CF=0)
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=3222,8935563
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN Priority=90 (R=0 C=1 CP=90 MA=10)
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|1 launch sets found
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|No VPN Chosen with 1 accounts
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|Launching client for Account Alt 1
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=1 SC=1 CS=1 FC=0 CF=0)
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=-377,1064437
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|Launching 1 clients
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.ClientController|1 launch tasks primed.
2022-05-03 23:23:31.5136|INFO|guildwars2.tools.alternator.Launcher|Alt 1 login attempt=1
2022-05-03 23:23:31.5136|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 login semaphore entry, count=0
2022-05-03 23:23:31.7240|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Login slot Free
2022-05-03 23:23:31.7240|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt 1 .dat file linked to: C:\Users\...\AppData\Roaming\Gw2 Launchbuddy\Loginfiles\3.dat
2022-05-03 23:23:31.7240|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt 1 .xml file linked to: C:\Users\...\AppData\Roaming\gw2-alternator\GW2 Custom GFX-Fastest.xml
2022-05-03 23:23:31.9337|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 exe semaphore entry, count=5
2022-05-03 23:23:31.9337|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Exe slot Free
2022-05-03 23:23:31.9337|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt 1 Authentication Semaphore Entered
2022-05-03 23:23:31.9337|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Started Login
2022-05-03 23:23:32.1420|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to Started because Normal start
2022-05-03 23:23:32.1420|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from NotRun to Started
2022-05-03 23:23:33.0651|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Killed Mutex
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to Authenticated because Module winnsi.dll loaded
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from Started to Authenticated
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 login semaphore release
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt 1 LoginDone Login
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 login semaphore released, count=1
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt 1 launchCount=2
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=2 SC=1 CS=1 FC=0 CF=0)
2022-05-03 23:23:33.9702|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt 1 Authentication No VPN release delay=5s
2022-05-03 23:23:38.9771|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt 1 Authentication Semaphore Released
2022-05-03 23:23:41.3027|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to ReadyToPlay because Memory threshold
2022-05-03 23:23:41.3027|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from Authenticated to ReadyToPlay
2022-05-03 23:23:41.3027|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Send ENTER
2022-05-03 23:23:41.5269|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to CharacterSelectReached because Module userenv.dll loaded
2022-05-03 23:23:41.5269|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from ReadyToPlay to CharacterSelectReached
2022-05-03 23:23:41.5269|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Send ENTER
2022-05-03 23:23:43.7425|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to CharacterSelected because Memory increased
2022-05-03 23:23:43.7425|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from CharacterSelectReached to CharacterSelected
2022-05-03 23:23:43.9507|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 Change State to Exited because Process.Exit event
2022-05-03 23:23:43.9507|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 Status changed from CharacterSelected to Exited
2022-05-03 23:23:43.9507|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt 1 GW2 process exited
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.Launcher|Alt 1 exe semaphore released, count=5
2022-05-03 23:23:45.9620|INFO|guildwars2.tools.alternator.ClientController|All launch tasks finished.
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.ClientController|Restore login semaphore=1
2022-05-03 23:23:45.9620|INFO|guildwars2.tools.alternator.ClientController|GW2 account files restored.
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.ClientController|Metrics being saved
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.ClientController|Client Alt 1 1 2022-05-03 21:23:31
2022-05-03 23:23:45.9620|INFO|guildwars2.tools.alternator.ClientController|Metrics saved to C:\Users\...\AppData\Roaming\gw2-alternator\gw2-alternator-metrics_2022-05-03_21-23-45.txt
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Saving Accounts to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Saving VPNs to C:\Users\...\AppData\Roaming\gw2-alternator\vpnconnections.json
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Accounts saved to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json
2022-05-03 23:23:45.9620|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|VPNs saved to C:\Users\...\AppData\Roaming\gw2-alternator\vpnconnections.json

Let me know if you need any other information.

Thanks that is really helpful. This is the problem with only having one machine to tune on. I have added a shutdown delay (default 0.5s) that should help here, you can change it in the settings. Also extra logging added. Rewarded chest don't always go into inventory, they stack up until a limit is reached.
Try V1.0.17 and let me know

Thank you for your work, but upps, i am a little bit wondering, i downloaded the 1.0.17 but it got instantly deleted and Chrome says "Error - Virus found". Windows Defender reported it as Virus too: Trojan:Win32/Wacatac.B!ml

Thanks for the quick turnaround, unfortunately it still doesn't seem to work in my quick testing. I'm testing on an account where i know the stack limit is reached so the chest go into the inventory.
I've changed the shutdown delay to 1000ms in the settings and now i can see the gray box of the game window for about a second until it disappear but the chest still doesn't trigger.
Metrics:
´´´´
Started	2022-05-04	06:49:27
Total Time	22,5469729	s
Account	Start	Authenticate	Login	Enter	Exit
Alt1	0.4241733	2.0065794		16.8804753	1.2308647
´´´´
Debug-log:
´´´´
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|Max GW2 Instances=5
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=4 SC=3 CS=1 FC=1 CF=0)
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=3176,0226798
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN Priority=90 (R=0 C=1 CP=90 MA=10)
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|1 launch sets found
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|No VPN Chosen with 1 accounts
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|Launching client for Account Alt1
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=4 SC=3 CS=1 FC=1 CF=0)
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=-423,9773202
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|Launching 1 clients
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.ClientController|1 launch tasks primed.
2022-05-04 08:49:27.3115|INFO|guildwars2.tools.alternator.Launcher|Alt1 login attempt=4
2022-05-04 08:49:27.3115|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore entry, count=0
2022-05-04 08:49:27.5267|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Login slot Free
2022-05-04 08:49:27.5267|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt1 .dat file linked to: C:\Users...\AppData\Roaming\Gw2 Launchbuddy\Loginfiles\1.dat
2022-05-04 08:49:27.5267|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt1 .xml file linked to: C:\Users...\AppData\Roaming\gw2-alternator\GW2 Custom GFX-Fastest.xml
2022-05-04 08:49:27.7348|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 exe semaphore entry, count=5
2022-05-04 08:49:27.7348|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Exe slot Free
2022-05-04 08:49:27.7348|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication Semaphore Entered
2022-05-04 08:49:27.7393|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Started Login
2022-05-04 08:49:27.9430|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Started because Normal start
2022-05-04 08:49:27.9430|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from NotRun to Started
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Killed Mutex
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gw2-64.exe
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ntdll.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernel32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernelbase.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: apphelp.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: user32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: win32u.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdi32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdi32full.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msvcp_win.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ucrtbase.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: advapi32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msvcrt.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: sechost.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rpcrt4.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ws2_32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wintrust.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: psapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: version.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ole32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wtsapi32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: combase.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winmm.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: oleaut32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shell32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msacm32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: crypt32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdiplus.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: comctl32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winmmbase.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: usp10.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msimg32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: secur32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptbase.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: sspicli.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: imm32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msasn1.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: bcryptprimitives.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dbghelp.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: windows.storage.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wldp.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shcore.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shlwapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: profapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernel.appcore.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: bcrypt.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: uxtheme.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxgi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxcore.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cfgmgr32.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: clbcatq.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ntmarta.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: napinsp.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: pnrpnsp.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wshbth.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: nlaapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: iphlpapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mswsock.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dnsapi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: nsi.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winrnr.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: fwpuclnt.dll
2022-05-04 08:49:28.8536|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rasadhlp.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msctf.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: textinputframework.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coremessaging.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coreuicomponents.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wintypes.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: windowscodecs.dll
2022-05-04 08:49:29.0860|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: textshaping.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coherentui64.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d9.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dwmapi.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptsp.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rsaenh.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: imagehlp.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gpapi.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptnet.dll
2022-05-04 08:49:29.5350|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winnsi.dll
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Authenticated because Module winnsi.dll loaded
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from Started to Authenticated
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore release
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 LoginDone Login
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore released, count=1
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 launchCount=5
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=5 (SuccessFail: CC=5 SC=3 CS=1 FC=1 CF=0)
2022-05-04 08:49:29.7422|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication No VPN release delay=5s
2022-05-04 08:49:30.4065|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dpapi.dll
2022-05-04 08:49:34.7641|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication Semaphore Released
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: aticfx64.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amdxn64.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: setupapi.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amdihk64.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amd_ags_x64.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: atiadlxx.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: propsys.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: pdh.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: devobj.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxdiagn.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d12.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d11.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wmiclnt.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: powrprof.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: umpdc.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemprox.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemcomn.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemsvc.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: fastprox.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amsi.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: userenv.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mpoav.dll
2022-05-04 08:49:44.1916|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dsound.dll
2022-05-04 08:49:44.4079|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelectReached because Module userenv.dll loaded
2022-05-04 08:49:44.4099|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from Authenticated to CharacterSelectReached
2022-05-04 08:49:44.4099|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Send ENTER
2022-05-04 08:49:46.6225|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelected because Memory increased by 10464 > 100
2022-05-04 08:49:46.6225|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelectReached to CharacterSelected
2022-05-04 08:49:47.8532|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Exited because Process.Exit event
2022-05-04 08:49:47.8532|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelected to Exited
2022-05-04 08:49:47.8532|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 GW2 process exited
2022-05-04 08:49:49.8557|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 exe semaphore released, count=5
2022-05-04 08:49:49.8557|INFO|guildwars2.tools.alternator.ClientController|All launch tasks finished.
2022-05-04 08:49:49.8557|DEBUG|guildwars2.tools.alternator.ClientController|Restore login semaphore=1
2022-05-04 08:49:49.8557|INFO|guildwars2.tools.alternator.ClientController|GW2 account files restored.
2022-05-04 08:49:49.8557|DEBUG|guildwars2.tools.alternator.ClientController|Metrics being saved
2022-05-04 08:49:49.8557|DEBUG|guildwars2.tools.alternator.ClientController|Client Alt1 4 2022-05-04 06:49:27
2022-05-04 08:49:49.8626|INFO|guildwars2.tools.alternator.ClientController|Metrics saved to C:\Users...\AppData\Roaming\gw2-alternator\gw2-alternator-metrics_2022-05-04_06-49-49.txt
2022-05-04 08:49:49.8626|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection1|Saving Accounts to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json 2022-05-04 08:49:49.8626|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection1|Saving VPNs to C:\Users...\AppData\Roaming\gw2-alternator\vpnconnections.json
2022-05-04 08:49:49.8626|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection1|Accounts saved to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json 2022-05-04 08:49:49.8626|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection1|VPNs saved to C:\Users...\AppData\Roaming\gw2-alternator\vpnconnections.json
´´´´

Hmmm. That is strange. The logs look correct. I need to run it on my machine to ensure something else didn't break.
CharacterSelectReached => Send Enter [To select top character] => CharacterSelected => Wait 1000ms => Forced Exit
This is the flow I am expecting and seems to be verified in the log

There is a lot of guesswork involved in trying to track the GW2 process state :)

Yep it seems like it thinks that it gets to CharacterSelectReached before it really does
If i change the delay to the max (5000ms) the grey box shows a blank character select screen for a split second before it closes.
Here's a debug-log when clicking collect instead of login and letting the map load. The first CharacterSelectReached seems to be a false positive with the real one appearing 9sec later: (i've marked the parts)
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|Max GW2 Instances=2
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=20 (SuccessFail: CC=10 SC=12 CS=12 FC=0 CF=0)
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=3448,0943966
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN Priority=91 (R=0 C=1 CP=90 MA=10)
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|1 launch sets found
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|No VPN Chosen with 1 accounts
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|Launching client for Account Alt1
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=20 (SuccessFail: CC=10 SC=12 CS=12 FC=0 CF=0)
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN offset=-151,9056034
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|Launching 1 clients
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.ClientController|1 launch tasks primed.
2022-05-04 12:08:57.4395|INFO|guildwars2.tools.alternator.Launcher|Alt1 login attempt=3
2022-05-04 12:08:57.4395|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore entry, count=0
2022-05-04 12:08:57.6441|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Login slot Free
2022-05-04 12:08:57.6441|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt1 .dat file linked to: C:\Users\...\AppData\Roaming\Gw2 Launchbuddy\Loginfiles\1.dat
2022-05-04 12:08:57.6441|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt1 .xml file linked to: C:\Users\...\AppData\Roaming\gw2-alternator\GW2 Custom GFX-Fastest.xml
2022-05-04 12:08:57.8522|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 exe semaphore entry, count=2
2022-05-04 12:08:57.8522|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Exe slot Free
2022-05-04 12:08:57.8522|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication Semaphore Entered
2022-05-04 12:08:57.8522|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Started Collect
2022-05-04 12:08:58.0583|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Started because Normal start
2022-05-04 12:08:58.0583|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from NotRun to Started
2022-05-04 12:08:58.9853|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Killed Mutex
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gw2-64.exe
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ntdll.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernel32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernelbase.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: user32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: win32u.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdi32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdi32full.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msvcp_win.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ucrtbase.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: advapi32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msvcrt.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: sechost.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rpcrt4.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ws2_32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wintrust.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: psapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: version.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wtsapi32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ole32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winmm.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: combase.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: oleaut32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shell32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msacm32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: crypt32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gdiplus.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: comctl32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winmmbase.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msimg32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: usp10.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: secur32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptbase.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: sspicli.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: imm32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msasn1.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: bcryptprimitives.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dbghelp.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: windows.storage.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wldp.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shcore.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: shlwapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: profapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: kernel.appcore.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: bcrypt.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: uxtheme.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxgi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxcore.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cfgmgr32.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: clbcatq.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ntmarta.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: napinsp.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: pnrpnsp.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wshbth.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: nlaapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: iphlpapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mswsock.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dnsapi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: nsi.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winrnr.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: fwpuclnt.dll
2022-05-04 12:08:58.9933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rasadhlp.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msctf.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: textinputframework.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coremessaging.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coreuicomponents.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wintypes.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: windowscodecs.dll
2022-05-04 12:08:59.2123|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: textshaping.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coherentui64.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d9.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dwmapi.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptsp.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: rsaenh.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: imagehlp.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: gpapi.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: cryptnet.dll
2022-05-04 12:08:59.6613|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winnsi.dll
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Authenticated because Module winnsi.dll loaded
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from Started to Authenticated
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore release
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 LoginDone Collect
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 login semaphore released, count=1
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 launchCount=11
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.MVVM.model.VpnDetails|No VPN delay=20 (SuccessFail: CC=11 SC=12 CS=12 FC=0 CF=0)
2022-05-04 12:08:59.8658|DEBUG|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication No VPN release delay=20s
2022-05-04 12:09:00.7545|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dpapi.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: aticfx64.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amdxn64.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: setupapi.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amdihk64.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amd_ags_x64.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: atiadlxx.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: propsys.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: pdh.dll
2022-05-04 12:09:15.4403|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: devobj.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dxdiagn.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d12.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wmiclnt.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: powrprof.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d11.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: umpdc.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemprox.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemcomn.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wbemsvc.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: fastprox.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: amsi.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: userenv.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mpoav.dll
2022-05-04 12:09:15.6687|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dsound.dll
-2022-05-04 12:09:15.8841|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelectReached because Module userenv.dll loaded
-2022-05-04 12:09:15.8841|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from Authenticated to CharacterSelectReached
-2022-05-04 12:09:15.8841|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Send ENTER
-2022-05-04 12:09:18.1028|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelected because Memory increased by 215900 > 100
-2022-05-04 12:09:18.1028|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelectReached to CharacterSelected
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: devrtl.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: spinf.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: drvstore.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3d12core.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: d3dscache.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: twinapi.appcore.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: apphelp.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ddraw.dll
2022-05-04 12:09:18.1262|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: dciman32.dll
2022-05-04 12:09:19.8841|INFO|guildwars2.tools.alternator.AuthenticationThrottle|Alt1 Authentication Semaphore Released
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: winsta.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mmdevapi.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: wdmaud.drv
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: ksuser.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: avrt.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: audioses.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: msacm32.drv
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: midimap.dll
2022-05-04 12:09:20.1627|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: resourcepolicyclient.dll
2022-05-04 12:09:20.3775|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Playing because Module mmdevapi.dll loaded
2022-05-04 12:09:20.3798|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelected to Playing
2022-05-04 12:09:22.4157|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: lglcdapi.dll
2022-05-04 12:09:24.4458|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: mscms.dll
2022-05-04 12:09:24.4458|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: coloradapterclient.dll
2022-05-04 12:09:24.4458|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: icm32.dll
2022-05-04 12:09:24.4458|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: xinput9_1_0.dll
-2022-05-04 12:09:24.6586|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelectReached because Module mscms.dll loaded
-2022-05-04 12:09:24.6608|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from Playing to CharacterSelectReached
-2022-05-04 12:09:24.6608|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Send ENTER
-2022-05-04 12:09:26.8933|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to CharacterSelected because Memory increased by 247992 > 100
-2022-05-04 12:09:26.8933|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelectReached to CharacterSelected
2022-05-04 12:09:39.1161|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: xinput1_4.dll
2022-05-04 12:09:39.1161|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Module: inputhost.dll
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 Change State to Exited because Process.Exit event
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 Status changed from CharacterSelected to Exited
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.MVVM.model.Account|Alt1 Fetching details from GW2 API
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.MVVM.model.Client|Alt1 GW2 process exited
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.Launcher|Alt1 exe semaphore released, count=2
2022-05-04 12:09:41.1300|INFO|guildwars2.tools.alternator.ClientController|All launch tasks finished.
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.ClientController|Restore login semaphore=1
2022-05-04 12:09:41.1300|INFO|guildwars2.tools.alternator.ClientController|GW2 account files restored.
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.ClientController|Metrics being saved
2022-05-04 12:09:41.1300|DEBUG|guildwars2.tools.alternator.ClientController|Client Alt1 3 2022-05-04 10:08:57
2022-05-04 12:09:41.1459|INFO|guildwars2.tools.alternator.ClientController|Metrics saved to C:\Users\...\AppData\Roaming\gw2-alternator\gw2-alternator-metrics_2022-05-04_10-09-41.txt
2022-05-04 12:09:41.1459|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Saving Accounts to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json
2022-05-04 12:09:41.1459|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Saving VPNs to C:\Users\...\AppData\Roaming\gw2-alternator\vpnconnections.json
2022-05-04 12:09:41.1459|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|Accounts saved to C:\Users\...\AppData\Roaming\gw2-alternator\accounts.json
2022-05-04 12:09:41.1459|DEBUG|guildwars2.tools.alternator.MVVM.model.JsonCollection`1|VPNs saved to C:\Users\...\AppData\Roaming\gw2-alternator\vpnconnections.json

Thanks I'll compare that with what I see on my machine

Did a quick experiment and removed userenv.dll from Client.cs, that seems to have solved the issue, the game now exits at the loading screen and triggers new chests. Not sure if it breaks anything else though.

I was going to try something like that, much faster for you to try it. Thanks. I will check it still works for me and push a new version

Looks great, I had a nice clean run with your change: https://docs.google.com/spreadsheets/d/1wrKWp_2dLXHZrtC2WtUN2d-j0Z8Fl4EqnV_mO9Up72E/edit?usp=sharing
will do a bit more testing tonight

All looks good: https://github.com/SamMackrill/gw2-alternator/releases/tag/V1.0.19

Thanks for your let, let me know any features you would like to see.

Thank you, will do after i had time to try it a bit more.


[Feature Request:] brew formulae for kubeshark

Contact Details
<EMAIL_ADDRESS>Is your feature request related to a problem? Please describe.
Unable to install and update kubeshark via homebrew package manager.
Original Thread
No response
Describe the solution you'd like to see
I'd like to run brew install --cask kubeshark to install kubeshark on my Apple Silicon (currently there's Intel and ARM/Apple-Silicon) Macbook.
Provide additional context
This might be helpful:

https://docs.brew.sh/Formula-Cookbook

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I've opened the following PR for this issue.
https://github.com/kubeshark/kubeshark/pull/1258


Add function to run c9sdk inside of a container

@fjakobs
Add a run command to run c9sdk inside of a container for testing.

please also update the README


can you add mkv output ,webm not good for other encoder

like cudacoder ,can not add webm input,and MediaInfo_CLI_22.12 can add to tools?

Thank you for using.
Regarding the issue in your title, I will add the option for you to manually change the format to save as MKV during the save process. Basically, WebM is an extension of MKV, so other software may also add support in the future.
As for the content of your message, I'm not quite sure what you're trying to express. Could you please provide more information so I can better understand what you want to know?

Hello, I have released a new version that may or may not meet your needs. Now, after the analysis is complete, you can click Browse and manually change the file name to .mkv, and the GUI will save it in standard mkv format. Although I haven't thoroughly tested it, if you are interested, you can try the new version.

thank you


ai-duet

https://github.com/googlecreativelab/aiexperiments-ai-duet

Added in 8ba5ae211cad38814af6c26a324141b408f13681


Create wired-git AUR package

A wired-git AUR package in addition to the current wired package would be great for users who want to be on the newest version of wired.

Oops, referenced the wrong issue there.  It's meant to be #6 .

This is now up: https://aur.archlinux.org/packages/wired-git/


Docker support

Hi,
Does this project plans to a have a docker image ready to be used such as bashly?
Since Ubuntu 18.04 does not support ruby>2.7 via packager manager, I currently cannot use such project out-of-the box as compared to bashly.
Thanks.

I wasn't planning on it, since I did not think there was demand.
I will make one later today, no problem.
Will post here again when it is ready.

Done.
Updated the installation instructions as well.

@DannyBen Thanks a lot for your fast reply.
I'll try and let you know.

My pleasure. Thanks for taking the time to request it.

@DannyBen that's an awesome option for rapid prototyping. However, I cannot find the image, yet. Have you pushed it?

@DannyBen indeed, i think that dannyben/completely is not public since I got the following after running the completely alias:
Unable to find image 'dannyben/completely:latest' locally
docker: Error response from daemon: pull access denied for dannyben/completely, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.


shelley-test: stop trying to generate transactions once UTxO is exhausted

Fixes #2557. Fixes #2462.
We recently extended the length of the RealTPraos tests. This increased two probabilities, which together lead to Issue #2557:

The probability that the total UTxO dwindles to zero during the test.
The probability that the arbitrary Shelley transactions include a successful protocol parameter update that increase the minimum transaction fees from A=0 B=0.

This PR accepts the above event, and simply stops generated transactions while it appears that we cannot (cheaply) find one that the UTxO can afford.
This PR depends on the upstream PR input-output-hk/cardano-ledger-specs#1824. Thus it is Draft for now. But I think the content is simple enough to review already, so please have at it. Thanks!

bors r+

bors r+


Executable python files are not scanned

A file with a shebang of #!/usr/bin/env python and no .py extension are not scanned by this tool.

Released a new version. Now you can use --extra-file-paths option to include files that do not contain .py or .pyi extension.


Translate: Guides > Security vulnerability detection

Translate: Guides > Security vulnerability detection

Can you open a draft PR and link this issue to it? Because it's currently not easy to check how it's coming along.

Branch merged https://github.com/quarkusio/pt.quarkus.io/pull/186

Branch merged https://github.com/quarkusio/pt.quarkus.io/pull/186


compatibility with magicgui v0.2.0

Description
magicgui v0.2.0 (https://github.com/napari/magicgui/pull/43) is close to being ready.  The biggest change for napari is that a magicgui widget is no longer a QWidget directly.  Rather, (like vispy), it is composed of a backend widget which is available at widget.native.  This PR makes napari compatible with both the current version of magicgui and the future version (if you want to try out https://github.com/napari/magicgui/pull/43, you'll also need this).
I'll post a more thorough comment over there about all the changes, but I've been very careful to make sure that all (or as much as possible) of the previous API continues to work (with warnings), for now.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
https://github.com/napari/magicgui/pull/43
How has this been tested?

[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Amazing @tlambert03! This is very exciting.

This PR makes napari compatible with both the current version of magicgui and the future version (if you want to try out napari/magicgui#43, you'll also need this).

That's great. I have a couple minor questions. When we add the add_function_widget method in #1856 I think we're going to need to start depending on magicgui. Do we want to add that dependency in this PR? Would it then be >=0.2.0 or no need? Does that change some of the backwards compatibility stuff? Do we need to think about coordinating releases?

When we add the add_function_widget method in #1856 I think we're going to need to start depending on magicgui. Do we want to add that dependency in this PR? Would it then be >=0.2.0 or no need?

technically no need. this PR should work with either 0.2.0 or before.  So I'd say let's wait for 0.2.0 to be on PyPI, and then depend on >=0.2.0 ... but since this PR is cross-compatible, it might be easier to just merge this, and then depend on 0.2.0 when it's ready (perhaps in #1856, perhaps later).

Does that change some of the backwards compatibility stuff? Do we need to think about coordinating releases?

hopefully not.  Either combination (new napari, old magicgui, or vice versa) should be fine.  The user will get different warnings in either case, but if I did it right, it should still work.  Rather than juggle coordinating releases, let's go piecewise, and then add magicgui>=0.2.0 to napari when we're happy with it.

I've just approved the magicGui PR43, which is truly incredible, and so am happy to merge this now. I will merge later tonight unless I hear from @tlambert03 that you'd like to make additional changes before then. I think we can clean up the comments etc when we add magicGui as an actual dependency in follow up PRs

I will merge later tonight unless I hear from @tlambert03 that you'd like to make additional changes before then.

I'm happy to have this merged.  it's minimal and should be cross-compatible


Add DICOM SR support for Angle

We're cleaning up issues as we prepare to announce the OHIF Viewer's version 2 release. This, and the other DICOM SR issues have been moved to this roadmap card:
https://github.com/OHIF/Viewers/projects/3#card-21713351


Animating percentages from/to px

Seems to be a bug at first:
animate({
  el: 'div',
  translateX: ['100%', 0]
})

or
animate({
  el: 'div',
  translateX: '100%',
  direction: 'reverse'
})

I expect an animation from 100% to 0, but got from 100px to 0. See: http://jsbin.com/fitezotivo/edit?js,output
It seems to occur when animating percentages from/to px (as no unit is converted to px). Using translateX: ['100%', '0%'] fix the first case, but we're still facing the issue when using direction: reverse

Fixed in v2.0.0


AWARENESS: AIB VHD Output Change

We are making a small breaking to the VHD Output, where we will not return a SAS URI, but a BLOB URI. We are planning to roll this change out in phases starting on May 25, 2021, and continuing into the first week of June. Some parts of the service will return SAS and others will return SAS-less URI, so your automation/code needs to be able to handle both cases.
Existing behavior:
When you specify a VHD output the VHD is placed in the staging resource group, you then query the runOutput:
az resource show \

    --ids "/subscriptions/$subscriptionID/resourcegroups/$imageResourceGroup/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName/runOutputs/$runOutputName"  \

    --api-version=2020-02-14 | grep artifactUri

This then would return a SAS URI, for example:
https://kqqtojmjy3fid5w2u3zukw1j.blob.core.windows.net/vhds/Tmp1_20210312111014.vhd?se=2021-04-11T19%3A10%3A15Z\u0026sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\u0026sp=r\u0026spr=https\u0026sr=b\u0026sv=2018-03-28
You could immediately download this.
New behavior:
Instead of returning the SAS URI, we will just return the BLOB URI:
https://kqqtojmjy3fid5w2u3zukw1j.blob.core.windows.net/vhds/Tmp1_20210312111014.vhd
If you wish to download them, you will need to either:

Generate a SAS URI as a post-build step
Use an Azure storage client to download the VHD.

Documentation for how to generate a SAS URI as a post-build step: https://github.com/Azure/azvmimagebuilder/blob/main/vhdUpdate2021.md#accomodating-the-change-example-steps-to-generate-a-sas-token-as-a-post-build-step
Please let us know if you have any questions or concerns.

Added doc for how to generate a SAS URI as a post-build step: https://github.com/Azure/azvmimagebuilder/blob/main/vhdUpdate2021.md#accomodating-the-change-example-steps-to-generate-a-sas-token-as-a-post-build-step


Nan in summary histogram when running facenet_train_classifier.py

I have the following problem when i use my own dataset to run  facenet_train_classifier.py. All parameters are the same except the dataset path:
Epoch: [0][1/100]	Time 4.541	Loss 44.833	RegLoss 24.607
Epoch: [0][2/100]	Time 2.765	Loss 46.207	RegLoss 24.736
Epoch: [0][3/100]	Time 0.412	Loss 45.358	RegLoss 24.623
Epoch: [0][4/100]	Time 0.412	Loss 46.909	RegLoss 24.945
Epoch: [0][5/100]	Time 0.411	Loss 43.843	RegLoss 24.535
.....
InvalidArgumentError (see above for traceback): Nan in summary histogram for: Logits/biases/gradients
[[Node: Logits/biases/gradients = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](Logits/biases/gradients/tag, gradients/Logits/BiasAdd_grad/tuple/control_dependency_1/_2081)]]
Anybody can solve this problem? many thanks!

For some reason the gradients become NaN. It's difficult to say what's the reason for this, but in general it could be due to that the training becomes instable du to too high learning rate etc. But in this case I don't know.


[e2e]: generic workflow_dispatch main workflow_inputs slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11247519043
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.workflow_inputs.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.workflow_inputs.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Oct  9 03:19:09 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11266740522
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.workflow_inputs.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.workflow_inputs.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Oct 10 03:15:11 UTC 2024
Tests are passing now. Closing this issue.


Can't build esp-rfid

Similar to issue #18
Where did you place the git version of the esp8266 Arduino core?
Mine is located here (osx):
/Users/ersin/Library/Arduino15/packages/arduino/hardware/esp8266com/esp8266/
I guess it is the correct path according to the manual:
https://github.com/esp8266/Arduino#using-git-version
but unfortunately I still see the same error

I do not use mac, maybe @rneurink may help on this.

One of my testers has a mac but i haven't been building on it. If you go
into the arduino settings and put the url in additional board manager. You
are able to select the right version for the arduino core in the library
manager
On 27 September 2017 at 12:34, omersiar<EMAIL_ADDRESS>wrote:

I do not use mac, maybe @rneurink https://github.com/rneurink may help
on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/omersiar/esp-rfid/issues/21#issuecomment-332480533,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-qZTCLxg1cDwormgydOBbSuzzERlPXks5smiS9gaJpZM4PegVX
.

Plz provide working video or detailed operation of process


tests: threads: fix issue#219656

In the file variable val is not initialized,
causing the variable stack_ptr, pos, points to uninitialized data.
Initialize the variable val according to the code and commits.
Fix #219656

@naiyuantian You need to add into message body, not into title "Fixes #Github_Issue_Number". Use a Github issue number, not a Coverity issue number.

@naiyuantian I think Coverity wants you to initialize val in its declaration like uint8_t val=0;


critical HTTPError Forbidden on $ nuxt generate coming from node_modules/ky/

Version
@nuxtjs/strapi: v0.3.1
nuxt: v2.15.4
I fear this is specific to my use case so I cannot deliver a minimal reproduction, only a screenshot and the code that's causing it.

Generating with $ nuxt generate went fine until I added this in nuxtServerInit()
const strapiResult = await $strapi.find('upload/files');
const lottieFiles = strapiResult.filter(x => x.ext === '.json').map((x) => {
  return {
    id: x.id,
    name: x.name,
    url: `https://cms.my-domain.com${x.url}`,
    alt: x.alternativeText,
    mimeType: x.mime,
    hash: x.hash,
  };
});

commit('SET_LOTTIE_FILES', lottieFiles);

gentle push.
This issue still remains and I have no idea what to do :(

I have the same issue, it's down to a lack of credentials or API key so Strapi is rejecting the API call.
The documentation covers authentication of an actual user using the site, but not to call the API to generate the static pages (in my case)
If one of the authors can give an example of config to allow nuxt generate to access the API I'll update the docs.

Closing this as the module has been rewritten in Nuxt3.
Also, you shouldn't generate pages that requires authentication, you can exclude those pages with generate.exclude.
Feel free to reopen if the issue persists.


Remove existing SQL DB and move pointers to the new one

This is the second of two PRs migrating the domain SQL database to the new Terraform module based on the azurerm_mssql_database resource.
This PR removed the old resources and the pointers from the application infrastructure now uses the new resources.
The above is done in agreement with members of all product teams on January 26th.

How about the web API (app-webapi.tf)? I think there are some important changes missing.

I have changed the value of "CHARGE_DB_CONNECTION_STRING" to point to the connection string of new database. Am I missing anything else?

How about the web API (app-webapi.tf)? I think there are some important changes missing.

I have changed the value of "CHARGE_DB_CONNECTION_STRING" to point to the connection string of new database. Am I missing anything else?

Good question. When looking at your PRs I wondered why you chose to change the naming of the connection string environment variable names? You actually cannot do that without changing the function host endpoints too. And that will lead you directly further into our domain tests - and that's something you wouldn't wanna mess with. So as-is I believe this PR will break the domain on deployment.


Adding new ambiants

To be merged after elementals

Just marking these as draft until #3134 is merged, it's unreviewable before then due to file count anyway.


npm test fails on windows at NODE_ENV=TEST

G:\Projects\aws-api-gateway-for-cloudformation>npm test

><EMAIL_ADDRESS>test G:\Projects\aws-api-gateway-for-cloudformation
> npm install && npm run eslint && npm run unittest && npm run checkcoverage

><EMAIL_ADDRESS>eslint G:\Projects\aws-api-gateway-for-cloudformation
> eslint --max-warnings 0 lib

><EMAIL_ADDRESS>unittest G:\Projects\aws-api-gateway-for-cloudformation
> NODE_ENV=TEST  istanbul cover --include-all-sources true -x "_scripts/**/*" ./node_modules/mocha/bin/_mocha ./tests/unit -- --recursive

'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "G:\\Program Files\\nodejs\\node.exe" "G:\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "unittest"
npm ERR! node v4.2.2
npm ERR! npm  v3.4.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>unittest: `NODE_ENV=TEST  istanbul cover --include-all-sources true -x "_scripts/**/*" ./node_modules/mocha/bin
/_mocha ./tests/unit -- --recursive`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>unittest script 'NODE_ENV=TEST  istanbul cover --include-all-sources true -x "_scripts/**/*" ./no
de_modules/mocha/bin/_mocha ./tests/unit -- --recursive'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the AWS-APIGateway-for-CloudFormation package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=TEST  istanbul cover --include-all-sources true -x "_scripts/**/*" ./node_modules/mocha/bin/_mocha ./tests/unit -- --recursive
npm ERR! You can get their info via:
npm ERR!     npm owner ls AWS-APIGateway-for-CloudFormation
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     G:\Projects\aws-api-gateway-for-cloudformation\npm-debug.log
npm ERR! Test failed.  See above for more details.

I've added npm run testWindows and npm run unittestWindows and they both seem to work.
It did involve a bit of duplication so if you have any good ideas on how to get rid of that it'd be appreciated :)


Dropping multiple files only adds one on Chrome

Describe the bug
Using go-ipfs 0.4.19 & Chrome stable 74 drop multiple individual files... only 1 file is added.
To Reproduce
Steps to reproduce the behavior:

Go to files
Drop two or more files on the page
Only one file appears added

Firefox is not affected. The files are all added as expected.
Desktop (please complete the following information):

OS: macOS
Browser: Chrome (and electron)
Version: 74

@hacdias we really need that test suite for adding files!

@olizilla I'll start working on them as soon as I can. I'll use the #1034 PR because it's related.

@hacdias let's keep the test suite seperate from work that changes how files get added. Please make a new branch off master for the suite, and then when we're happy with it, merge it in, and pull it into those branches. Step 1 is add file tests for webui.

Only one files get detected. Here's the issue for that: https://github.com/grabantot/datatransfer-files-promise/issues/1
It seems that person found the fix, but the creator just closed the issue and didn't fix it.


add ingress secret field support

add ingress secret field support to remove and add fields

go run examples/container/V2containers/IngressV2/main.go --field-crn crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:d151bd36-2815-45e5-92b8-5b70dcdad684:secret:e1bd1187-c418-4765-5868-bcc06e0c6c3f --instance-crn crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:0470669d-9873-4bab-9f33-df67387335ef:: --clusterNameOrID chrlmpl20n0bn1v97b0g
[DEBUG] REQUEST: [2023-05-31T16:47:20-05:00] POST /identity/token HTTP/1.1
Host: iam.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Original-User-Agent:

apikey=[PRIVATE DATA HIDDEN]&grant_type=urn%3Aibm%3Aparams%3Aoauth%3Agrant-type%3Aapikey&response_type=cloud_iam
[DEBUG] RESPONSE: [2023-05-31T16:47:21-05:00] Elapsed: 282ms HTTP/1.1 200 OK
Content-Length: 3402
Akamai-Grn: 0.0a931ab8.1685569641.5acffec4
Cache-Control: no-cache, no-store, must-revalidate
Connection: keep-alive
Content-Language: en-US
Content-Type: application/json
Date: Wed, 31 May 2023 21:47:21 GMT
Expires: 0
Pragma: no-cache
Strict-Transport-Security: max-age=31536000; includeSubDomains
Transaction-Id: d3FzajI-abff0f2bbb744ee188483090efd2c9bc
X-Content-Type-Options: nosniff
X-Correlation-Id: d3FzajI-abff0f2bbb744ee188483090efd2c9bc
X-Proxy-Upstream-Service-Time: 55
X-Request-Id: 4902f777-803f-47c4-b24f-b3c95585226e

{"access_token":"[PRIVATE DATA HIDDEN]","refresh_token":"[PRIVATE DATA HIDDEN]","token_type":"[PRIVATE DATA HIDDEN]","expires_in":1200,"expiration":1685570838,"refresh_token_expiration":1685656041,"scope":"ibm openid","session_id":"C-fc559322-0efc-431d-85f8-4eface9585cd"}
[DEBUG] REQUEST: [2023-05-31T16:47:21-05:00] POST /ingress/v2/secret/registerInstance HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

{"cluster":"chrlmpl20n0bn1v97b0g","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:0470669d-9873-4bab-9f33-df67387335ef::","isDefault":false,"secretGroupID":""}
[DEBUG] RESPONSE: [2023-05-31T16:47:23-05:00] Elapsed: 1804ms HTTP/1.1 200 OK
Content-Length: 328
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:22 GMT
Expires: Wed, 31 May 2023 21:47:22 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=35
Server-Timing: origin; dur=1623
Server-Timing: ak_p; desc="468213_388971387_668547088_165762_2632_24_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-rj4mv
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: 92903527-f9d9-492f-bb44-5d155e04d38f
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"fvt-ingress-sm-2","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:0470669d-9873-4bab-9f33-df67387335ef::","secretGroupID":"","secretGroupName":"","callbackChannel":"","userManaged":true,"isDefault":false,"type":"secrets-manager","status":"created"}
[DEBUG] REQUEST: [2023-05-31T16:47:23-05:00] GET /ingress/v2/secret/getInstance?cluster=chrlmpl20n0bn1v97b0g&name=fvt-ingress-sm-2 HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

[DEBUG] RESPONSE: [2023-05-31T16:47:23-05:00] Elapsed: 179ms HTTP/1.1 200 OK
Content-Length: 328
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:23 GMT
Expires: Wed, 31 May 2023 21:47:23 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=14
Server-Timing: origin; dur=135
Server-Timing: ak_p; desc="468213_388971387_668549625_15238_3094_32_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-v6kbf
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: ca412a3e-7b49-4a6b-8dd9-c70b481d5556
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"fvt-ingress-sm-2","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:0470669d-9873-4bab-9f33-df67387335ef::","secretGroupID":"","secretGroupName":"","callbackChannel":"","userManaged":true,"isDefault":false,"type":"secrets-manager","status":"created"}
[DEBUG] REQUEST: [2023-05-31T16:47:23-05:00] POST /ingress/v2/secret/unregisterInstance HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

{"cluster":"chrlmpl20n0bn1v97b0g","name":"fvt-ingress-sm-2"}
[DEBUG] RESPONSE: [2023-05-31T16:47:24-05:00] Elapsed: 945ms HTTP/1.1 200 OK
Content-Length: 314
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:24 GMT
Expires: Wed, 31 May 2023 21:47:24 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=11
Server-Timing: origin; dur=893
Server-Timing: ak_p; desc="468213_388971387_668550023_91507_2070_30_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-wdxld
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: 80b9b879-4098-49f1-b9ff-19afec7c33de
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"fvt-ingress-sm-2","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:0470669d-9873-4bab-9f33-df67387335ef::","secretGroupID":"","secretGroupName":"","callbackChannel":"","userManaged":false,"isDefault":false,"type":"","status":"deleted"}
[DEBUG] REQUEST: [2023-05-31T16:47:24-05:00] POST /ingress/v2/secret/createSecret HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"","crn":"","persistence":true,"type":"Opaque","add":[{"name":"","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:d151bd36-2815-45e5-92b8-5b70dcdad684:secret:e1bd1187-c418-4765-5868-bcc06e0c6c3f","append_prefix":false}]}
[DEBUG] RESPONSE: [2023-05-31T16:47:27-05:00] Elapsed: 2962ms HTTP/1.1 200 OK
Content-Length: 511
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:27 GMT
Expires: Wed, 31 May 2023 21:47:27 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=145
Server-Timing: origin; dur=2773
Server-Timing: ak_p; desc="468213_388971387_668551536_293642_2053_28_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-rj4mv
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: fad724a3-8048-4bfe-b27a-c90bf3ef2472
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"ibm-cert-store","domain":"","crn":"","expiresOn":"","status":"created","userManaged":true,"persistence":true,"type":"Opaque","secretType":"","lastUpdatedTimestamp":"","fields":[{"name":"key","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:d151bd36-2815-45e5-92b8-5b70dcdad684:secret:e1bd1187-c418-4765-5868-bcc06e0c6c3f","expiresOn":"","secretType":"kv","lastUpdatedTimestamp":"2023-05-31T21:47:26+0000"}]}
[DEBUG] REQUEST: [2023-05-31T16:47:27-05:00] GET /ingress/v2/secret/getSecret?cluster=chrlmpl20n0bn1v97b0g&name=testabc123&namespace=ibm-cert-store HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

[DEBUG] RESPONSE: [2023-05-31T16:47:27-05:00] Elapsed: 747ms HTTP/1.1 200 OK
Content-Length: 511
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:27 GMT
Expires: Wed, 31 May 2023 21:47:27 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=149
Server-Timing: origin; dur=551
Server-Timing: ak_p; desc="468213_388971387_668555983_73351_2719_27_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-599kl
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: ae211732-b58b-4545-9819-7f87aa4418cb
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"ibm-cert-store","domain":"","crn":"","expiresOn":"","status":"created","userManaged":true,"persistence":true,"type":"Opaque","secretType":"","lastUpdatedTimestamp":"","fields":[{"name":"key","crn":"crn:v1:staging:public:secrets-manager:eu-gb:a/8c18c7b678fb46db900ea9f5815ac2e2:d151bd36-2815-45e5-92b8-5b70dcdad684:secret:e1bd1187-c418-4765-5868-bcc06e0c6c3f","expiresOn":"","secretType":"kv","lastUpdatedTimestamp":"2023-05-31T21:47:26+0000"}]}
[DEBUG] REQUEST: [2023-05-31T16:47:27-05:00] POST /ingress/v2/secret/removeField HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"ibm-cert-store","crn":"","add":null,"remove":[{"name":"key"}]}
[DEBUG] RESPONSE: [2023-05-31T16:47:29-05:00] Elapsed: 1842ms HTTP/1.1 200 OK
Content-Length: 242
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Content-Type: application/json; charset=utf-8
Date: Wed, 31 May 2023 21:47:29 GMT
Expires: Wed, 31 May 2023 21:47:29 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=110
Server-Timing: origin; dur=1676
Server-Timing: ak_p; desc="468213_388971387_668557181_182126_2085_26_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-zjzbw
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: 78e205dd-b699-4b39-bba7-28b4cf080128
X-Xss-Protection: 1; mode=block

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"ibm-cert-store","domain":"","crn":"","expiresOn":"","status":"created","userManaged":true,"persistence":true,"type":"","secretType":"","lastUpdatedTimestamp":"","fields":null}
[DEBUG] REQUEST: [2023-05-31T16:47:29-05:00] POST /ingress/v2/secret/deleteSecret HTTP/1.1
Host: origin.containers.test.cloud.ibm.com
Accept: application/json
Accept-Language: en
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: Bluemix-go SDK 0.1 / darwin
X-Auth-Refresh-Token: [PRIVATE DATA HIDDEN]
X-Original-User-Agent:

{"cluster":"chrlmpl20n0bn1v97b0g","name":"testabc123","namespace":"ibm-cert-store"}
[DEBUG] RESPONSE: [2023-05-31T16:47:31-05:00] Elapsed: 2239ms HTTP/1.1 204 No Content
Content-Length: 0
Cache-Control: max-age=0, no-cache, no-store
Connection: keep-alive
Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'
Date: Wed, 31 May 2023 21:47:31 GMT
Expires: Wed, 31 May 2023 21:47:31 GMT
Pragma: no-cache
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=14
Server-Timing: origin; dur=2140
Server-Timing: ak_p; desc="468213_388971387_668560047_220705_2170_25_-";dur=1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Hostname: armada-ingress-secret-mgr-6f7649ffb6-mwxxd
X-Permitted-Cross-Domain-Policies: master-only
X-Request-Id: e482ded6-c5bf-4535-8539-8863abcaad41
X-Xss-Protection: 1; mode=block


Add link to latest version if browsing an older version

Added new properties: LatestRelease, LatestPreRelease
Added link to the newest version

Addresses https://github.com/NuGet/NuGetGallery/issues/8823

Hi, @GKotfis! This seems the same PR as https://github.com/NuGet/NuGetGallery/pull/8860. Do we use the wrong branch here? By the way, we recommend you to always use dev as the base branch. Thanks!

@GKotfis I'll close this now as it's a duplicate of https://github.com/NuGet/NuGetGallery/pull/8860. Please let us know if you think this is in error--we can reopen if necessary. I'd also like to see a resolution on https://github.com/NuGet/NuGetGallery/pull/8860 and I've commented there to try to move this forward.


Create file setting

Add new FileSetting and corresponding FileValidator.

I like it :+1:

Thank you all for your contributions :tada:


CIV-10257 Added 2 templates variable for spec 1v1 journey when Update claimant …

https://tools.hmcts.net/jira/browse/CIV-10257
https://tools.hmcts.net/jira/browse/CIV-10287

@asthamalviya  Please fix these:
  Dependency-Analyze Failure:   One or more dependencies were identified with vulnerabilities that have a CVSS score greater than '0.0': CVE-2023-41080, CVE-2023-34040   See the dependency-check report for more details.


nuget push should block when pushing the same ID and version

We need to add a -Force flag to nuget.exe and an api on the server side that accepts the force flag and allows the overwrite.

This seems defunct.  We will continue to think about what it means to allow overwriting packages, but this particular issue can be closed.


[GOBBLIN-2130] avoid race condition b/w add dag node and delete dag

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

[x] Here are some details about my PR, including screenshots (if applicable):
avoid race condition b/w add dag node and delete dag. race condition can happen when deadlinedagproc update the dag node after cancelling it and reevaluate dag proc that was generated by the same cancelling tries to delete dag (/dag node)

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
difficult to add tests, this change is only changing the order of execution

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 38.80%. Comparing base (e501b62) to head (f12981e).
Report is 3 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (e501b62) and HEAD (f12981e). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (e501b62)
HEAD (f12981e)

2
1

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #4021      +/-   ##
============================================
- Coverage     45.86%   38.80%   -7.06%
+ Complexity     3257     1599    -1658
============================================
  Files           707      388     -319
  Lines         27865    15995   -11870
  Branches       2796     1585    -1211
============================================
- Hits          12779     6207    -6572
+ Misses        14008     9290    -4718
+ Partials       1078      498     -580

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Conditions link on page points to 404

Under successCriteria, this paragraph:

Example: For response {"status" : "successful"}, the expression can be eq(root['status'], 'successful'). Learn more about specifying conditions.

The link "specifying conditions" results in a 404. The link should be updated to point to the correct page. (I'm not sure what the correct URL is.)

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

ID: 038b734f-c824-15a1-f256-de92abce5dc3
Version Independent ID: 038b734f-c824-15a1-f256-de92abce5dc3
Content: InvokeRESTAPI@1 - Invoke REST API v1 task
Content Source: task-reference/invoke-rest-api-v1.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

@qJake -- Jake, I have updated the documentation and it should be live by tomorrow.


pull request for e2e test at 01/20/2017 11:26:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


migrate ResearchGroup to Project

This migrates existing ResearchGroup data into the Project model.

All ResearchGroup objects are saved as a Project model.
For collections and annotation, adds a context field to replace managing_group.

The intention is that after this migration, the ResearchGroup model can be worked out of the application (and replaced with Project). I'll add a PR for that in a bit.

How have you tested this with real data? Maybe I can test next week with the data from the production server (on a local installation, of course), if you haven't done so.

No, only on my local dataset.

Note: I've updated the URI format for projects to be consistent with #181. If you had already run the migration here, revert it and run it again.


Docker builds failing on MacOS

Platform: MacOS 10.14.6
Architecture: x64
Related: 1073
The command:
./makejdk-any-platform.sh --docker jdk8u

fails out of the box.
Adding --debug-docker and --ssh
causes the Docker container to start, but the build command now fails.
Setting:
build@cc958f466f61:/openjdk/build$ JAVA_HOME=/usr/lib/jvm/zulu-7-amd64/jre
build@cc958f466f61:/openjdk/build$ export JAVA_HOME
build@cc958f466f61:/openjdk/build$ java -version
openjdk version "1.7.0_232"
OpenJDK Runtime Environment (Zulu <IP_ADDRESS>-CA-linux64) (build 1.7.0_232-b6)
OpenJDK 64-Bit Server VM (Zulu <IP_ADDRESS>-CA-linux64) (build 24.232-b6, mixed mode)

enables the build to find a JVM, but this still fails:
build@cc958f466f61:/openjdk/build$ /openjdk/sbin/build.sh
/openjdk/sbin/common/common.sh: line 55: name: unbound variable
Running gradle with /usr/lib/jvm/zulu-7-amd64/jre
bash: ./gradlew: No such file or directory

this is probably because the pipelines directory required at https://github.com/AdoptOpenJDK/openjdk-build/blob/fd939c142a0370cda48eebca9f5dee9d22f0dfc1/sbin/build.sh#L46 is not brought into the docker container

@willsparker Perhaps we could include the testing of builds in docker as part of the playbook testing too


feat!: deprecate the module

I'm 99% sure we dropped all the relevant dependencies on this one.  I'd like to ship a semver major with the deprecation notice, then @bcoe have you do the npm deprecate dance if that's ok. I already submitted a PR to drop it from sloth so we stop managing updates.  After all that's done, I'll archive the repo.

synth.py should only matter if it's in repos.json :) Did that here:
https://github.com/googleapis/sloth/pull/521
Could use a stamp!


Run tests in actions

Because the previous test runner did not export DISPLAY,
the tests were never run.

Switches from JJ's Alpine zef container to Ubuntu latest
Installs gtk-3-dev and xvfb

xvfb allows headless running of X windows tests

Uses prove instead of zef test

zef requires a separate clone and install
prove is faster at running the tests

Note: Currently the zef based approach is still included
for consideration but is commented out.

This resolves #109


[pact-jvm-consumer-junit] Pact consumer performance

This is really more of a question than an issue...
Is it normal that one consumer test takes several seconds to execute?
Currently I am running the test via my machine's IDE (IntelliJ). [ windows 7 with intel i5 @2.60GHz with 8GB RAM]
And with 1 test, it takes between 5-15 seconds to execute. There was even one execution that took 30 seconds.
I currently have a very basic pact consumer based on the samples here:
        // Define the test data:
        String path = "/mypath/abc/";

        //Header data:
        Map<String, String> headerData = new HashMap<String, String>();
        headerData.put("Content-Type", "application/json");

        // Put as JSON object:
        JSONObject bodyExpected = new JSONObject();
        bodyExpected.put("name",myName);

        PactFragment pactFragment = ConsumerPactBuilder
                .consumer("test_consumer")
                .hasPactWith("test_provider")
                .uponReceiving("a request to get values")
                    .path(path)
                    .method("GET")
                .willRespondWith()
                    .status(200)
                    .headers(headerData)
                    .body(bodyExpected)
                .toFragment();

        MockProviderConfig config = MockProviderConfig.createDefault();
        VerificationResult result = pactFragment.runConsumer(config, new TestRun() {

            @Override
            public void run(MockProviderConfig config) {
                try {
                    new ProviderClient(config.url(),path).hello(bodyExpected);
                } catch (IOException e) {
                }
            }

        });

(I removed all the junit assertions to make sure it's not causing additional delays)
I was expecting the test to be as short as a normal Unit test. Currently on the same machine, 1 unit test takes less than 1 second to execute. So I am not sure if there is something I need to do on my pact consumer test ?

Running your test on a powerful laptop takes 02.265 seconds. But there is quite a bit happening behind the scenes for this test to work. Firstly, a new mock server is started for every test. On my laptop this accounted for 0.6 seconds. Then 0.1 seconds seems to be the time that the request is received by the server. Then a further 0.1 seconds to compare the request with the expected one. Then another 0.5 seconds for the server to be shut down and the pact file written to disk.
So the largest amount of time seems to be starting the HTTP mock server and shutting it down again afterwards.

Using a timer, it looks the the time for your test is measured as:

Stage
Time (ms)

Setup
9

Setup Fragment
597

Start of test function
1326

End of test function
2225

End of Test
2464

@uglyog thanks for the quick revert! :)
Do you have any ideas/suggestions how we can make further improvements?

I was quite surprised that setting up the pact was 0.5 seconds. That can be improved. And I've started working on a new mock server that should be quicker to startup and shutdown.


Fix AML/GitIgnore Flakiness

Description
This PR fixes two issues in the AML/GitIgnore exclusion logic:

The list of GitWildMatchPattern objects created in IgnoreFile._create_path_spec() was reading the lines from the ignore file as a set instead of list. This is an incorrect way to read the ignore file for two reasons:

A set guarantees no ordering of its elements. The ordering of lines in an ignore file determines how the inclusion/exclusion rules apply, so by casting the ignore file lines to a set, we've created a different set of rules for inclusions/exclusions.
Because of point 1., the set created by _create_pathspec() will not always have the same order. Each call to _create_pathspec() can create a different ordering of rules to apply, which can lead to a different set of files However, a list guarantees order, so by preserving the order of lines in the ignore file, we ensure that the inclusion/exclusion rules are always the same and are applied in the intended order.

The exclusion logic would return the first match, regardless of whether or not the file should be included or excluded, instead of looping through all patterns and returning the last match. The bug is addressed by looping through and exhausting all match patterns and returning a True or False for the last matching pattern.

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


#5724: Fix watcher server exit syncing

The issue here is that the syncing between watcher thread being killed from host, and host moving on was racy. My suspicion is that the fix I made recently to correct the watcher polling frequency perturbed this somehow.
The result is that if tests with watcher enabled + a long polling interval + a short test time are run back-to-back-to-back (as seen in the stress tests) then multiple watcher servers are alive at the same time. This appears to snowball the more tests that meet the criteria are run in a row, the more watcher servers we get. So the more tests that are run the slower it gets.
The fix is to properly sync the watcher server closing with the host thread detach function. Doing so, I can see locally for a subset of tests that the time with watcher enabled and without is virtually the same now. Previously it was longer with watcher enabled depending on ow many tests were ran (for example: python_api_unit_tests 46m->89m, python_model_tests 27m->32m). Now it's 46m->47m and 27m->27m respectively.
This also includes a fix for #5785 , the file wasn't being closed properly on watcher server shutdown, which combined with the above error caused a "too many files open" error.
CI run here: https://github.com/tenstorrent-metal/tt-metal/actions/runs/8088178340
Stress test CI run here: https://github.com/tenstorrent-metal/tt-metal/actions/runs/8088045995

CI passes: https://github.com/tenstorrent-metal/tt-metal/actions/runs/8088178340
Stress test is failing with the same error on main, hard to tell if it's running fast since it does fail on the first iteration. It definitely doesn't take 12 hours though: https://github.com/tenstorrent-metal/tt-metal/actions/runs/8088045995


🐛💻 – build-deploy job in docs workflow is skipped on main branch

Describe the problem

This line seems to limit this workflow to running on pull-requests, as a result, the last successful documentation build on main was July 14th.
Steps to reproduce

Merge any branch into main or manually trigger the workflow, it will be skipped.

@SorenSpicknall, after removing the line the documentation builds on main as expected, but we may need to find a new way to address the original issue. I thought there was a way to require workflow approvals for outside forks, or maybe the pull_request_target event is the key?

Could use the permissions key to grant write access to the PR itself, even when running on a fork.
permissions:
      pull-requests: write

Could also tweak the conditions in the if clause I just removed, return true if the event is anything other than 'pull_request', and check that the repo is this repo if 'pull_request'.

Could also tweak the conditions in the if clause I just removed, return true if the event is anything other than 'pull_request', and check that the repo is this repo if 'pull_request'. Maybe:
if: ${{ github.event_name != "pull_request" | github.event.pull_request.head.repo.full_name == github.repository }}

Something like this is my preferred option, I think. I'd prefer not to grant write permissions on the PR because of security risks associated with forks. Thank you for continuing to iterate on this!


Does it support Kotlin Native ?

I am currently looking for ORM for kotlin native, I'm wondering is this the one?

I'm sorry to say no. Ktorm is implemented based on JDBC. It can not run on Kotlin native.

@vincentlauvlwj I don't understand why being based off of JDBC imposes the limitation that Ktorm can not run on Kotlin Native. Can you add more detail on why?


Work 'available online' behind toggle

We're not ready to make this available quite yet, until we know how we're going to track the impact it has.
So reintroducing the the original previews and putting this behind a toggle.

@gestchild not sure what we're reviewing here after re-reading the explanation - is this a revert?

is this a revert?

More or less (putting back the two Preview components), but there are some new bits that are staying (such as changes to the Audio/Video/Downloads components) and the rest is going behind a toggle.

Going to jump out of this one, as I am missing a load of the context and talking out my nose.