Mobiflight not recognizing MSFS has started automatically in version 9.1

Describe the bug
Running windows 11 with WASM, FSUIPC 7 and SIM update 6 and now 7 Mobiflight does not recognise the flight sim is running. However a work around to kick start Mobiflight to recognize the sim is active is to go into settings and change randomly the FSUIPC rate either faster or slower and hit OK. Mobiflight then automatically finds the sim is working and runs correctly.
Steps To Reproduce
Steps to reproduce the behavior:

Open MSFS with the FSUIPC short cut
Open Mobiflight
Once MSFS has started Mobiflight still has not detected the sim.
Go to Settings in Mobiflight and change FSUIPC poll rate to any new value and hit ok. Now Mobiflight works ok.

Expected behavior
Previous version would automatically detect MSFS running and connected
Actual behavior
User needs to force Mobiflight to look to see if Sim is running
Details

MobiFlight Version: 9.1.0
FlightSim: MSFS 2020 both sim update 6 and now with sim update 7
AddOn: FSUIPC v7.2.13
Operating System: Windows 11

Additional context
This bug is not a big issue as Mobiflight works ok with the work around but the previous version (8) did automatically work

Now removed FSUIPC and I can confirm the issue is still there as is the work around

there are hundreds of people using it including me - there must be something special about your case.
why are you still using fsuipc for MSFS2020?
when you say the sim is not detected, what is what you see? In the status bar you can click on the sim status to see more details.
Also, it can take up to 10 seconds for Mobiflight to detect the sim and especially the sim connect connection can take longer. Because it's not active from the beginning but i think once the flight gets loaded.

Hi
I remove FSUIPC as it was not needed.  I will try waiting longer and see if it does connect. But just changing the FSUIPC rate in any direction causes Mobiflight to connect straight away.
Thanks will report back when I have experimented with it.
Thanks for getting back to me.
Nigel
From: Sebastian @.>
Sent: 16 December 2021 13:49
To: MobiFlight/MobiFlight-Connector @.>
Cc: Fellstone7 @.>; Author @.>
Subject: Re: [MobiFlight/MobiFlight-Connector] Mobiflight not recognizing MSFS has started automatically in version 9.1 (Issue #615)
there are hundreds of people using it including me - there must be something special about your case.
why are you still using fsuipc for MSFS2020?
when you say the sim is not detected, what is what you see? In the status bar you can click on the sim status to see more details.
Also, it can take up to 10 seconds for Mobiflight to detect the sim and especially the sim connect connection can take longer. Because it's not active from the beginning but i think once the flight gets loaded.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/MobiFlight/MobiFlight-Connector/issues/615#issuecomment-995834320 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AW5ITP2ARHH7LEKD6Z74OLTURHU4BANCNFSM5KAKITBA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .   https://github.com/notifications/beacon/AW5ITPYZMRTCWGTLXCDY6STURHU4BA5CNFSM5KAKITBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHNNTTUA.gif

Hi @Fellstone7 , asking about FSUIPC was really out of curiosity, i simply wanted to understand your requirement for it. If you don't need, switch to SimConnect. It is so much more straightforward.

Hi Sebastian
I have hi removed FSUIPC (which was the MSFS version) off the PC. Mobiflight is still working as before. I am also using SPAD.next as well to control my Saitek panels if that could be a culpit?
What is interesting is after I kick start mobiflight by changing the FSUIPC time sampling rate in the settings mobiflight recognises MSFS is working but I still get a warning about SIMCONNECT ? see screen grab below.
I have also included the log file when I start mobiflight and after I have then kick started it with the setting change. If that help to under stand whats happening. I have also reinstalled Mobiflight as well. That has made no difference.
From: Sebastian @.>
Sent: 16 December 2021 23:58
To: MobiFlight/MobiFlight-Connector @.>
Cc: Fellstone7 @.>; Mention @.>
Subject: Re: [MobiFlight/MobiFlight-Connector] Mobiflight not recognizing MSFS has started automatically in version 9.1 (Issue #615)
Hi @Fellstone7 https://github.com/Fellstone7  , asking about FSUIPC was really out of curiosity, i simply wanted to understand your requirement for it. If you don't need, switch to SimConnect. It is so much more straightforward.
—
Reply to this email directly, view it on GitHub https://github.com/MobiFlight/MobiFlight-Connector/issues/615#issuecomment-996285213 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AW5ITP6H43R6WX4E3466FELURJ4HXANCNFSM5KAKITBA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AW5ITP44ZID4M62EGDVXGJLURJ4HXA5CNFSM5KAKITBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHNRBWHI.gif Message ID: @.*** @.***> >
17/12/2021 14:38:10(561): MainForm() : Logger initialized Debug
17/12/2021 14:38:11(178): Found attached DirectInput Device: Bravo Throttle Quadrant, Type: FirstPerson, SubType: 259
17/12/2021 14:38:11(185): Adding attached Joystick Device: Bravo Throttle Quadrant Buttons 48, Axis: 6
17/12/2021 14:38:11(191): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:0:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(192): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:4:Usage:48:Axis: X Axis
17/12/2021 14:38:11(192): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:8:Usage:53:Axis: Z Rotation
17/12/2021 14:38:11(193): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:12:Usage:52:Axis: Y Rotation
17/12/2021 14:38:11(194): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:16:Usage:51:Axis: X Rotation
17/12/2021 14:38:11(194): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:20:Usage:50:Axis: Z Axis
17/12/2021 14:38:11(196): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:24:Usage:1:Button: Button 0
17/12/2021 14:38:11(196): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:25:Usage:2:Button: Button 1
17/12/2021 14:38:11(197): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:26:Usage:3:Button: Button 2
17/12/2021 14:38:11(198): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:27:Usage:4:Button: Button 3
17/12/2021 14:38:11(199): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:28:Usage:5:Button: Button 4
17/12/2021 14:38:11(200): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:29:Usage:6:Button: Button 5
17/12/2021 14:38:11(201): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:30:Usage:7:Button: Button 6
17/12/2021 14:38:11(202): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:31:Usage:8:Button: Button 7
17/12/2021 14:38:11(203): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:32:Usage:9:Button: Button 8
17/12/2021 14:38:11(204): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:33:Usage:10:Button: Button 9
17/12/2021 14:38:11(205): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:34:Usage:11:Button: Button 10
17/12/2021 14:38:11(206): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:35:Usage:12:Button: Button 11
17/12/2021 14:38:11(207): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:36:Usage:13:Button: Button 12
17/12/2021 14:38:11(208): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:37:Usage:14:Button: Button 13
17/12/2021 14:38:11(209): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:38:Usage:15:Button: Button 14
17/12/2021 14:38:11(210): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:39:Usage:16:Button: Button 15
17/12/2021 14:38:11(211): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:40:Usage:17:Button: Button 16
17/12/2021 14:38:11(212): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:41:Usage:18:Button: Button 17
17/12/2021 14:38:11(214): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:42:Usage:19:Button: Button 18
17/12/2021 14:38:11(219): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:43:Usage:20:Button: Button 19
17/12/2021 14:38:11(220): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:44:Usage:21:Button: Button 20
17/12/2021 14:38:11(221): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:45:Usage:22:Button: Button 21
17/12/2021 14:38:11(223): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:46:Usage:23:Button: Button 22
17/12/2021 14:38:11(224): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:47:Usage:24:Button: Button 23
17/12/2021 14:38:11(225): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:48:Usage:25:Button: Button 24
17/12/2021 14:38:11(226): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:49:Usage:26:Button: Button 25
17/12/2021 14:38:11(228): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:50:Usage:27:Button: Button 26
17/12/2021 14:38:11(230): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:51:Usage:28:Button: Button 27
17/12/2021 14:38:11(231): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:52:Usage:29:Button: Button 28
17/12/2021 14:38:11(233): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:53:Usage:30:Button: Button 29
17/12/2021 14:38:11(234): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:54:Usage:31:Button: Button 30
17/12/2021 14:38:11(236): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:55:Usage:32:Button: Button 31
17/12/2021 14:38:11(238): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:56:Usage:33:Button: Button 32
17/12/2021 14:38:11(240): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:57:Usage:34:Button: Button 33
17/12/2021 14:38:11(242): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:58:Usage:35:Button: Button 34
17/12/2021 14:38:11(243): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:59:Usage:36:Button: Button 35
17/12/2021 14:38:11(245): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:60:Usage:37:Button: Button 36
17/12/2021 14:38:11(247): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:61:Usage:38:Button: Button 37
17/12/2021 14:38:11(249): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:62:Usage:39:Button: Button 38
17/12/2021 14:38:11(251): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:63:Usage:40:Button: Button 39
17/12/2021 14:38:11(252): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:64:Usage:41:Button: Button 40
17/12/2021 14:38:11(254): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:65:Usage:42:Button: Button 41
17/12/2021 14:38:11(256): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:66:Usage:43:Button: Button 42
17/12/2021 14:38:11(258): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:67:Usage:44:Button: Button 43
17/12/2021 14:38:11(260): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:68:Usage:45:Button: Button 44
17/12/2021 14:38:11(262): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:69:Usage:46:Button: Button 45
17/12/2021 14:38:11(264): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:70:Usage:47:Button: Button 46
17/12/2021 14:38:11(266): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:71:Usage:48:Button: Button 47
17/12/2021 14:38:11(271): Found attached DirectInput Device: Alpha Flight Controls, Type: Joystick, SubType: 257
17/12/2021 14:38:11(275): Adding attached Joystick Device: Alpha Flight Controls Buttons 35, Axis: 2
17/12/2021 14:38:11(278): EnumerateDevices: Alpha Flight Controls: Aspect : Position:Offset:0:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(281): EnumerateDevices: Alpha Flight Controls: Aspect : Position:Offset:4:Usage:48:Axis: X Axis
17/12/2021 14:38:11(285): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:12:Usage:1:Button: Button 0
17/12/2021 14:38:11(287): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:13:Usage:2:Button: Button 1
17/12/2021 14:38:11(289): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:14:Usage:3:Button: Button 2
17/12/2021 14:38:11(291): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:15:Usage:4:Button: Button 3
17/12/2021 14:38:11(294): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:16:Usage:5:Button: Button 4
17/12/2021 14:38:11(296): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:17:Usage:6:Button: Button 5
17/12/2021 14:38:11(298): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:18:Usage:7:Button: Button 6
17/12/2021 14:38:11(300): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:19:Usage:8:Button: Button 7
17/12/2021 14:38:11(303): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:20:Usage:9:Button: Button 8
17/12/2021 14:38:11(305): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:21:Usage:10:Button: Button 9
17/12/2021 14:38:11(309): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:22:Usage:11:Button: Button 10
17/12/2021 14:38:11(312): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:23:Usage:12:Button: Button 11
17/12/2021 14:38:11(314): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:24:Usage:13:Button: Button 12
17/12/2021 14:38:11(317): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:25:Usage:14:Button: Button 13
17/12/2021 14:38:11(319): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:26:Usage:15:Button: Button 14
17/12/2021 14:38:11(322): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:27:Usage:16:Button: Button 15
17/12/2021 14:38:11(324): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:28:Usage:17:Button: Button 16
17/12/2021 14:38:11(327): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:29:Usage:18:Button: Button 17
17/12/2021 14:38:11(330): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:30:Usage:19:Button: Button 18
17/12/2021 14:38:11(333): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:31:Usage:20:Button: Button 19
17/12/2021 14:38:11(335): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:32:Usage:21:Button: Button 20
17/12/2021 14:38:11(338): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:33:Usage:22:Button: Button 21
17/12/2021 14:38:11(341): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:34:Usage:23:Button: Button 22
17/12/2021 14:38:11(344): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:35:Usage:24:Button: Button 23
17/12/2021 14:38:11(347): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:36:Usage:25:Button: Button 24
17/12/2021 14:38:11(349): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:37:Usage:26:Button: Button 25
17/12/2021 14:38:11(352): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:38:Usage:27:Button: Button 26
17/12/2021 14:38:11(355): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:39:Usage:28:Button: Button 27
17/12/2021 14:38:11(358): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:40:Usage:29:Button: Button 28
17/12/2021 14:38:11(361): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:41:Usage:30:Button: Button 29
17/12/2021 14:38:11(364): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:42:Usage:31:Button: Button 30
17/12/2021 14:38:11(367): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:43:Usage:32:Button: Button 31
17/12/2021 14:38:11(370): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:44:Usage:33:Button: Button 32
17/12/2021 14:38:11(373): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:45:Usage:34:Button: Button 33
17/12/2021 14:38:11(376): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:46:Usage:35:Button: Button 34
17/12/2021 14:38:11(380): Found attached DirectInput Device: T-Rudder, Type: Joystick, SubType: 257
17/12/2021 14:38:11(384): Adding attached Joystick Device: T-Rudder Buttons 0, Axis: 3
17/12/2021 14:38:11(388): EnumerateDevices: T-Rudder: Aspect : Position:Offset:0:Usage:50:Axis: Z Axis
17/12/2021 14:38:11(391): EnumerateDevices: T-Rudder: Aspect : Position:Offset:4:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(395): EnumerateDevices: T-Rudder: Aspect : Position:Offset:8:Usage:48:Axis: X Axis
17/12/2021 14:38:11(464): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
17/12/2021 14:38:11(471): MobiFlightCache.LookupAllConnectedArduinoModulesAsync: Start
17/12/2021 14:38:11(477): ^(VID_1B4F&PID_9206|VID_2341&PID_8036|VID_2341&PID_8037|VID_2341&PID_0010|VID_2341&PID_0042|VID_2341&PID_0001|VID_8087&PID_0024|VID_1A86&PID_7523|VID_2A03&PID_0042|VID_0403&PID_6001|VID_0403+PID_6001+.+|VID_2A03&PID_0010|VID_2341&PID_0210|VID_2341&PID_0242|VID_10C4&PID_EA60|VID_2341&PID_0043|VID_2A03&PID_0043)
17/12/2021 14:38:11(480): Checking for compatible module: ROOT_HUB30
17/12/2021 14:38:11(483): Checking for compatible module: VID_0000&PID_0002
17/12/2021 14:38:11(488): Checking for compatible module: VID_03F0&PID_0580
17/12/2021 14:38:11(491): Checking for compatible module: VID_0416&PID_A0F8
17/12/2021 14:38:11(495): Checking for compatible module: VID_0416&PID_A0F8&MI_00
17/12/2021 14:38:11(498): Checking for compatible module: VID_0416&PID_A0F8&MI_01
17/12/2021 14:38:11(501): Checking for compatible module: VID_044F&PID_B679
17/12/2021 14:38:11(505): Checking for compatible module: VID_045E&PID_0659
17/12/2021 14:38:11(508): Checking for compatible module: VID_045E&PID_0659&MI_02
17/12/2021 14:38:11(512): Checking for compatible module: VID_045E&PID_0659&MI_03
17/12/2021 14:38:11(515): Incompatible module skipped: HoloLens Sensors - VID/PID: VID_045E&PID_0659&MI_03
17/12/2021 14:38:11(519): Checking for compatible module: VID_045E&PID_0659&MI_04
17/12/2021 14:38:11(522): Incompatible module skipped: HP Reverb Virtual Reality Headset G2 - VID/PID: VID_045E&PID_0659&MI_04
17/12/2021 14:38:11(526): Checking for compatible module: VID_046D&PID_082C
17/12/2021 14:38:11(531): Checking for compatible module: VID_046D&PID_082C&MI_00
17/12/2021 14:38:11(534): Incompatible module skipped: HD Webcam C615 - VID/PID: VID_046D&PID_082C&MI_00
17/12/2021 14:38:11(538): Checking for compatible module: VID_046D&PID_082C&MI_02
17/12/2021 14:38:11(542): Incompatible module skipped: HD Webcam C615 - VID/PID: VID_046D&PID_082C&MI_02
17/12/2021 14:38:11(545): Checking for compatible module: VID_04B4&PID_6504
17/12/2021 14:38:11(549): Checking for compatible module: VID_04B4&PID_6506
17/12/2021 14:38:11(553): Checking for compatible module: VID_058F&PID_6362
17/12/2021 14:38:11(556): Checking for compatible module: VID_05AC&PID_12A8
17/12/2021 14:38:11(560): Incompatible module skipped: @oem52.inf,%iPhone.AppleUSB.DeviceDesc%;Apple Mobile Device USB Composite Device - VID/PID: VID_05AC&PID_12A8
17/12/2021 14:38:11(564): Checking for compatible module: VID_05AC&PID_12A8&MI_00
17/12/2021 14:38:11(567): Incompatible module skipped: Apple iPhone - VID/PID: VID_05AC&PID_12A8&MI_00
17/12/2021 14:38:11(572): Checking for compatible module: VID_05AC&PID_12A8&MI_01
17/12/2021 14:38:11(576): Incompatible module skipped: @oem52.inf,%iPhone.AppleUsbMux.DeviceDesc%;Apple Mobile Device USB Device - VID/PID: VID_05AC&PID_12A8&MI_01
17/12/2021 14:38:11(580): Checking for compatible module: VID_05AC&PID_12AB
17/12/2021 14:38:11(583): Incompatible module skipped: @oem52.inf,%iPhone.AppleUSB.DeviceDesc%;Apple Mobile Device USB Composite Device - VID/PID: VID_05AC&PID_12AB
17/12/2021 14:38:11(587): Checking for compatible module: VID_05AC&PID_12AB&MI_00
17/12/2021 14:38:11(592): Incompatible module skipped: Apple iPad - VID/PID: VID_05AC&PID_12AB&MI_00
17/12/2021 14:38:11(595): Checking for compatible module: VID_05AC&PID_12AB&MI_01
17/12/2021 14:38:11(599): Incompatible module skipped: @oem52.inf,%iPhone.AppleUsbMux.DeviceDesc%;Apple Mobile Device USB Device - VID/PID: VID_05AC&PID_12AB&MI_01
17/12/2021 14:38:11(603): Checking for compatible module: VID_05E3&PID_0608
17/12/2021 14:38:11(607): Checking for compatible module: VID_05E3&PID_0610
17/12/2021 14:38:11(612): Checking for compatible module: VID_05E3&PID_0612
17/12/2021 14:38:11(616): Checking for compatible module: VID_05E3&PID_0736
17/12/2021 14:38:11(621): Checking for compatible module: VID_06A3&PID_0D05
17/12/2021 14:38:11(625): Checking for compatible module: VID_06A3&PID_0D06
17/12/2021 14:38:11(629): Checking for compatible module: VID_0764&PID_0501
17/12/2021 14:38:11(633): Checking for compatible module: VID_0B05&PID_185C
17/12/2021 14:38:11(638): Checking for compatible module: VID_0B05&PID_1867
17/12/2021 14:38:11(642): Checking for compatible module: VID_0BDA&PID_0411
17/12/2021 14:38:11(647): Checking for compatible module: VID_0BDA&PID_4C15
17/12/2021 14:38:11(651): Checking for compatible module: VID_0BDA&PID_4C15&MI_00
17/12/2021 14:38:11(655): Incompatible module skipped: Realtek USB2.0 Audio - VID/PID: VID_0BDA&PID_4C15&MI_00
17/12/2021 14:38:11(660): Checking for compatible module: VID_0BDA&PID_4C15&MI_03
17/12/2021 14:38:11(664): Checking for compatible module: VID_0BDA&PID_5411
17/12/2021 14:38:11(669): Checking for compatible module: VID_154B&PID_005B
17/12/2021 14:38:11(673): Checking for compatible module: VID_1A40&PID_0101
17/12/2021 14:38:11(678): Checking for compatible module: VID_1B1C&PID_1B2E
17/12/2021 14:38:11(682): Checking for compatible module: VID_1B1C&PID_1B2E&MI_00
17/12/2021 14:38:11(687): Checking for compatible module: VID_1B1C&PID_1B2E&MI_01
17/12/2021 14:38:11(691): Checking for compatible module: VID_1B1C&PID_1B38
17/12/2021 14:38:11(696): Checking for compatible module: VID_1B1C&PID_1B38&MI_00
17/12/2021 14:38:11(701): Checking for compatible module: VID_1B1C&PID_1B38&MI_01
17/12/2021 14:38:11(706): Checking for compatible module: VID_2109&PID_0822
17/12/2021 14:38:11(710): Checking for compatible module: VID_2109&PID_2822
17/12/2021 14:38:11(715): Checking for compatible module: VID_2341&PID_0042
17/12/2021 14:38:11(719): Found potentially compatible module (Mega 2560): @.***
17/12/2021 14:38:11(724): Checking for compatible module: VID_294B&PID_1900
17/12/2021 14:38:11(728): Checking for compatible module: VID_294B&PID_1901
17/12/2021 14:38:11(733): Checking for compatible module: VID_F182&PID_0003
17/12/2021 14:38:11(738): Checking for compatible module: VID_F182&PID_0003&MI_00
17/12/2021 14:38:11(743): Incompatible module skipped: Leap Dev Kit - VID/PID: VID_F182&PID_0003&MI_00
17/12/2021 14:38:11(749): ExecutionManager.AutoConnectStart:Started auto connect timer
17/12/2021 14:38:11(764): MobiflightModule.connect: Connected to Default at COM4 of Type Arduino Mega 2560 (DTR=>True)
17/12/2021 14:38:13(152): MobiFlightModule.GetInfo: MobiFlight Mega, Mega Msfs ,1.11.3, SN-157-2f2
17/12/2021 14:38:13(230): MobiflightModule.disconnect: Disconnected Mega Msfs  at COM4
17/12/2021 14:38:13(240): MobiFlightCache.LookupAllConnectedArduinoModulesAsync: End
17/12/2021 14:38:13(245): MobiFlightCache.connect: Clearing modules
17/12/2021 14:38:13(250): MobiFlightCache.RegisterModule(Default:COM4)
17/12/2021 14:38:13(255): MobiflightModule.connect: Connected to Default at COM4 of Type MobiFlight Mega (DTR=>True)
17/12/2021 14:38:14(215): No config found for Encoder: Baro Knob @.***/a
17/12/2021 14:38:14(629): MobiFlightModule.GetInfo: MobiFlight Mega, Mega Msfs ,1.11.3, SN-157-2f2
17/12/2021 14:38:14(652): SimConnectCache::ClearSimVars . SimVars Cleared
17/12/2021 14:38:14(932): CheckForUpdate : Checking for RELEASE update...
17/12/2021 14:38:15(216): CheckForUpdate : MobiFlight is up to date.
17/12/2021 14:38:15(224): ExecutionManager.TestModeStop:Stopped test timer
17/12/2021 14:38:15(229): SimConnectCache::ClearSimVars . SimVars Cleared
17/12/2021 14:38:10(561): MainForm() : Logger initialized Debug
17/12/2021 14:38:11(178): Found attached DirectInput Device: Bravo Throttle Quadrant, Type: FirstPerson, SubType: 259
17/12/2021 14:38:11(185): Adding attached Joystick Device: Bravo Throttle Quadrant Buttons 48, Axis: 6
17/12/2021 14:38:11(191): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:0:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(192): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:4:Usage:48:Axis: X Axis
17/12/2021 14:38:11(192): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:8:Usage:53:Axis: Z Rotation
17/12/2021 14:38:11(193): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:12:Usage:52:Axis: Y Rotation
17/12/2021 14:38:11(194): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:16:Usage:51:Axis: X Rotation
17/12/2021 14:38:11(194): EnumerateDevices: Bravo Throttle Quadrant: Aspect : Position:Offset:20:Usage:50:Axis: Z Axis
17/12/2021 14:38:11(196): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:24:Usage:1:Button: Button 0
17/12/2021 14:38:11(196): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:25:Usage:2:Button: Button 1
17/12/2021 14:38:11(197): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:26:Usage:3:Button: Button 2
17/12/2021 14:38:11(198): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:27:Usage:4:Button: Button 3
17/12/2021 14:38:11(199): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:28:Usage:5:Button: Button 4
17/12/2021 14:38:11(200): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:29:Usage:6:Button: Button 5
17/12/2021 14:38:11(201): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:30:Usage:7:Button: Button 6
17/12/2021 14:38:11(202): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:31:Usage:8:Button: Button 7
17/12/2021 14:38:11(203): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:32:Usage:9:Button: Button 8
17/12/2021 14:38:11(204): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:33:Usage:10:Button: Button 9
17/12/2021 14:38:11(205): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:34:Usage:11:Button: Button 10
17/12/2021 14:38:11(206): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:35:Usage:12:Button: Button 11
17/12/2021 14:38:11(207): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:36:Usage:13:Button: Button 12
17/12/2021 14:38:11(208): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:37:Usage:14:Button: Button 13
17/12/2021 14:38:11(209): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:38:Usage:15:Button: Button 14
17/12/2021 14:38:11(210): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:39:Usage:16:Button: Button 15
17/12/2021 14:38:11(211): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:40:Usage:17:Button: Button 16
17/12/2021 14:38:11(212): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:41:Usage:18:Button: Button 17
17/12/2021 14:38:11(214): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:42:Usage:19:Button: Button 18
17/12/2021 14:38:11(219): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:43:Usage:20:Button: Button 19
17/12/2021 14:38:11(220): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:44:Usage:21:Button: Button 20
17/12/2021 14:38:11(221): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:45:Usage:22:Button: Button 21
17/12/2021 14:38:11(223): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:46:Usage:23:Button: Button 22
17/12/2021 14:38:11(224): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:47:Usage:24:Button: Button 23
17/12/2021 14:38:11(225): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:48:Usage:25:Button: Button 24
17/12/2021 14:38:11(226): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:49:Usage:26:Button: Button 25
17/12/2021 14:38:11(228): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:50:Usage:27:Button: Button 26
17/12/2021 14:38:11(230): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:51:Usage:28:Button: Button 27
17/12/2021 14:38:11(231): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:52:Usage:29:Button: Button 28
17/12/2021 14:38:11(233): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:53:Usage:30:Button: Button 29
17/12/2021 14:38:11(234): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:54:Usage:31:Button: Button 30
17/12/2021 14:38:11(236): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:55:Usage:32:Button: Button 31
17/12/2021 14:38:11(238): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:56:Usage:33:Button: Button 32
17/12/2021 14:38:11(240): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:57:Usage:34:Button: Button 33
17/12/2021 14:38:11(242): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:58:Usage:35:Button: Button 34
17/12/2021 14:38:11(243): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:59:Usage:36:Button: Button 35
17/12/2021 14:38:11(245): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:60:Usage:37:Button: Button 36
17/12/2021 14:38:11(247): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:61:Usage:38:Button: Button 37
17/12/2021 14:38:11(249): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:62:Usage:39:Button: Button 38
17/12/2021 14:38:11(251): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:63:Usage:40:Button: Button 39
17/12/2021 14:38:11(252): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:64:Usage:41:Button: Button 40
17/12/2021 14:38:11(254): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:65:Usage:42:Button: Button 41
17/12/2021 14:38:11(256): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:66:Usage:43:Button: Button 42
17/12/2021 14:38:11(258): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:67:Usage:44:Button: Button 43
17/12/2021 14:38:11(260): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:68:Usage:45:Button: Button 44
17/12/2021 14:38:11(262): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:69:Usage:46:Button: Button 45
17/12/2021 14:38:11(264): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:70:Usage:47:Button: Button 46
17/12/2021 14:38:11(266): EnumerateDevices: Bravo Throttle Quadrant: Aspect : 0:Offset:71:Usage:48:Button: Button 47
17/12/2021 14:38:11(271): Found attached DirectInput Device: Alpha Flight Controls, Type: Joystick, SubType: 257
17/12/2021 14:38:11(275): Adding attached Joystick Device: Alpha Flight Controls Buttons 35, Axis: 2
17/12/2021 14:38:11(278): EnumerateDevices: Alpha Flight Controls: Aspect : Position:Offset:0:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(281): EnumerateDevices: Alpha Flight Controls: Aspect : Position:Offset:4:Usage:48:Axis: X Axis
17/12/2021 14:38:11(285): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:12:Usage:1:Button: Button 0
17/12/2021 14:38:11(287): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:13:Usage:2:Button: Button 1
17/12/2021 14:38:11(289): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:14:Usage:3:Button: Button 2
17/12/2021 14:38:11(291): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:15:Usage:4:Button: Button 3
17/12/2021 14:38:11(294): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:16:Usage:5:Button: Button 4
17/12/2021 14:38:11(296): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:17:Usage:6:Button: Button 5
17/12/2021 14:38:11(298): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:18:Usage:7:Button: Button 6
17/12/2021 14:38:11(300): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:19:Usage:8:Button: Button 7
17/12/2021 14:38:11(303): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:20:Usage:9:Button: Button 8
17/12/2021 14:38:11(305): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:21:Usage:10:Button: Button 9
17/12/2021 14:38:11(309): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:22:Usage:11:Button: Button 10
17/12/2021 14:38:11(312): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:23:Usage:12:Button: Button 11
17/12/2021 14:38:11(314): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:24:Usage:13:Button: Button 12
17/12/2021 14:38:11(317): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:25:Usage:14:Button: Button 13
17/12/2021 14:38:11(319): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:26:Usage:15:Button: Button 14
17/12/2021 14:38:11(322): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:27:Usage:16:Button: Button 15
17/12/2021 14:38:11(324): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:28:Usage:17:Button: Button 16
17/12/2021 14:38:11(327): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:29:Usage:18:Button: Button 17
17/12/2021 14:38:11(330): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:30:Usage:19:Button: Button 18
17/12/2021 14:38:11(333): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:31:Usage:20:Button: Button 19
17/12/2021 14:38:11(335): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:32:Usage:21:Button: Button 20
17/12/2021 14:38:11(338): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:33:Usage:22:Button: Button 21
17/12/2021 14:38:11(341): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:34:Usage:23:Button: Button 22
17/12/2021 14:38:11(344): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:35:Usage:24:Button: Button 23
17/12/2021 14:38:11(347): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:36:Usage:25:Button: Button 24
17/12/2021 14:38:11(349): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:37:Usage:26:Button: Button 25
17/12/2021 14:38:11(352): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:38:Usage:27:Button: Button 26
17/12/2021 14:38:11(355): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:39:Usage:28:Button: Button 27
17/12/2021 14:38:11(358): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:40:Usage:29:Button: Button 28
17/12/2021 14:38:11(361): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:41:Usage:30:Button: Button 29
17/12/2021 14:38:11(364): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:42:Usage:31:Button: Button 30
17/12/2021 14:38:11(367): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:43:Usage:32:Button: Button 31
17/12/2021 14:38:11(370): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:44:Usage:33:Button: Button 32
17/12/2021 14:38:11(373): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:45:Usage:34:Button: Button 33
17/12/2021 14:38:11(376): EnumerateDevices: Alpha Flight Controls: Aspect : 0:Offset:46:Usage:35:Button: Button 34
17/12/2021 14:38:11(380): Found attached DirectInput Device: T-Rudder, Type: Joystick, SubType: 257
17/12/2021 14:38:11(384): Adding attached Joystick Device: T-Rudder Buttons 0, Axis: 3
17/12/2021 14:38:11(388): EnumerateDevices: T-Rudder: Aspect : Position:Offset:0:Usage:50:Axis: Z Axis
17/12/2021 14:38:11(391): EnumerateDevices: T-Rudder: Aspect : Position:Offset:4:Usage:49:Axis: Y Axis
17/12/2021 14:38:11(395): EnumerateDevices: T-Rudder: Aspect : Position:Offset:8:Usage:48:Axis: X Axis
17/12/2021 14:38:11(464): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
17/12/2021 14:38:11(471): MobiFlightCache.LookupAllConnectedArduinoModulesAsync: Start
17/12/2021 14:38:11(477): ^(VID_1B4F&PID_9206|VID_2341&PID_8036|VID_2341&PID_8037|VID_2341&PID_0010|VID_2341&PID_0042|VID_2341&PID_0001|VID_8087&PID_0024|VID_1A86&PID_7523|VID_2A03&PID_0042|VID_0403&PID_6001|VID_0403+PID_6001+.+|VID_2A03&PID_0010|VID_2341&PID_0210|VID_2341&PID_0242|VID_10C4&PID_EA60|VID_2341&PID_0043|VID_2A03&PID_0043)
17/12/2021 14:38:11(480): Checking for compatible module: ROOT_HUB30
17/12/2021 14:38:11(483): Checking for compatible module: VID_0000&PID_0002
17/12/2021 14:38:11(488): Checking for compatible module: VID_03F0&PID_0580
17/12/2021 14:38:11(491): Checking for compatible module: VID_0416&PID_A0F8
17/12/2021 14:38:11(495): Checking for compatible module: VID_0416&PID_A0F8&MI_00
17/12/2021 14:38:11(498): Checking for compatible module: VID_0416&PID_A0F8&MI_01
17/12/2021 14:38:11(501): Checking for compatible module: VID_044F&PID_B679
17/12/2021 14:38:11(505): Checking for compatible module: VID_045E&PID_0659
17/12/2021 14:38:11(508): Checking for compatible module: VID_045E&PID_0659&MI_02
17/12/2021 14:38:11(512): Checking for compatible module: VID_045E&PID_0659&MI_03
17/12/2021 14:38:11(515): Incompatible module skipped: HoloLens Sensors - VID/PID: VID_045E&PID_0659&MI_03
17/12/2021 14:38:11(519): Checking for compatible module: VID_045E&PID_0659&MI_04
17/12/2021 14:38:11(522): Incompatible module skipped: HP Reverb Virtual Reality Headset G2 - VID/PID: VID_045E&PID_0659&MI_04
17/12/2021 14:38:11(526): Checking for compatible module: VID_046D&PID_082C
17/12/2021 14:38:11(531): Checking for compatible module: VID_046D&PID_082C&MI_00
17/12/2021 14:38:11(534): Incompatible module skipped: HD Webcam C615 - VID/PID: VID_046D&PID_082C&MI_00
17/12/2021 14:38:11(538): Checking for compatible module: VID_046D&PID_082C&MI_02
17/12/2021 14:38:11(542): Incompatible module skipped: HD Webcam C615 - VID/PID: VID_046D&PID_082C&MI_02
17/12/2021 14:38:11(545): Checking for compatible module: VID_04B4&PID_6504
17/12/2021 14:38:11(549): Checking for compatible module: VID_04B4&PID_6506
17/12/2021 14:38:11(553): Checking for compatible module: VID_058F&PID_6362
17/12/2021 14:38:11(556): Checking for compatible module: VID_05AC&PID_12A8
17/12/2021 14:38:11(560): Incompatible module skipped: @oem52.inf,%iPhone.AppleUSB.DeviceDesc%;Apple Mobile Device USB Composite Device - VID/PID: VID_05AC&PID_12A8
17/12/2021 14:38:11(564): Checking for compatible module: VID_05AC&PID_12A8&MI_00
17/12/2021 14:38:11(567): Incompatible module skipped: Apple iPhone - VID/PID: VID_05AC&PID_12A8&MI_00
17/12/2021 14:38:11(572): Checking for compatible module: VID_05AC&PID_12A8&MI_01
17/12/2021 14:38:11(576): Incompatible module skipped: @oem52.inf,%iPhone.AppleUsbMux.DeviceDesc%;Apple Mobile Device USB Device - VID/PID: VID_05AC&PID_12A8&MI_01
17/12/2021 14:38:11(580): Checking for compatible module: VID_05AC&PID_12AB
17/12/2021 14:38:11(583): Incompatible module skipped: @oem52.inf,%iPhone.AppleUSB.DeviceDesc%;Apple Mobile Device USB Composite Device - VID/PID: VID_05AC&PID_12AB
17/12/2021 14:38:11(587): Checking for compatible module: VID_05AC&PID_12AB&MI_00
17/12/2021 14:38:11(592): Incompatible module skipped: Apple iPad - VID/PID: VID_05AC&PID_12AB&MI_00
17/12/2021 14:38:11(595): Checking for compatible module: VID_05AC&PID_12AB&MI_01
17/12/2021 14:38:11(599): Incompatible module skipped: @oem52.inf,%iPhone.AppleUsbMux.DeviceDesc%;Apple Mobile Device USB Device - VID/PID: VID_05AC&PID_12AB&MI_01
17/12/2021 14:38:11(603): Checking for compatible module: VID_05E3&PID_0608
17/12/2021 14:38:11(607): Checking for compatible module: VID_05E3&PID_0610
17/12/2021 14:38:11(612): Checking for compatible module: VID_05E3&PID_0612
17/12/2021 14:38:11(616): Checking for compatible module: VID_05E3&PID_0736
17/12/2021 14:38:11(621): Checking for compatible module: VID_06A3&PID_0D05
17/12/2021 14:38:11(625): Checking for compatible module: VID_06A3&PID_0D06
17/12/2021 14:38:11(629): Checking for compatible module: VID_0764&PID_0501
17/12/2021 14:38:11(633): Checking for compatible module: VID_0B05&PID_185C
17/12/2021 14:38:11(638): Checking for compatible module: VID_0B05&PID_1867
17/12/2021 14:38:11(642): Checking for compatible module: VID_0BDA&PID_0411
17/12/2021 14:38:11(647): Checking for compatible module: VID_0BDA&PID_4C15
17/12/2021 14:38:11(651): Checking for compatible module: VID_0BDA&PID_4C15&MI_00
17/12/2021 14:38:11(655): Incompatible module skipped: Realtek USB2.0 Audio - VID/PID: VID_0BDA&PID_4C15&MI_00
17/12/2021 14:38:11(660): Checking for compatible module: VID_0BDA&PID_4C15&MI_03
17/12/2021 14:38:11(664): Checking for compatible module: VID_0BDA&PID_5411
17/12/2021 14:38:11(669): Checking for compatible module: VID_154B&PID_005B
17/12/2021 14:38:11(673): Checking for compatible module: VID_1A40&PID_0101
17/12/2021 14:38:11(678): Checking for compatible module: VID_1B1C&PID_1B2E
17/12/2021 14:38:11(682): Checking for compatible module: VID_1B1C&PID_1B2E&MI_00
17/12/2021 14:38:11(687): Checking for compatible module: VID_1B1C&PID_1B2E&MI_01
17/12/2021 14:38:11(691): Checking for compatible module: VID_1B1C&PID_1B38
17/12/2021 14:38:11(696): Checking for compatible module: VID_1B1C&PID_1B38&MI_00
17/12/2021 14:38:11(701): Checking for compatible module: VID_1B1C&PID_1B38&MI_01
17/12/2021 14:38:11(706): Checking for compatible module: VID_2109&PID_0822
17/12/2021 14:38:11(710): Checking for compatible module: VID_2109&PID_2822
17/12/2021 14:38:11(715): Checking for compatible module: VID_2341&PID_0042
17/12/2021 14:38:11(719): Found potentially compatible module (Mega 2560): @.***
17/12/2021 14:38:11(724): Checking for compatible module: VID_294B&PID_1900
17/12/2021 14:38:11(728): Checking for compatible module: VID_294B&PID_1901
17/12/2021 14:38:11(733): Checking for compatible module: VID_F182&PID_0003
17/12/2021 14:38:11(738): Checking for compatible module: VID_F182&PID_0003&MI_00
17/12/2021 14:38:11(743): Incompatible module skipped: Leap Dev Kit - VID/PID: VID_F182&PID_0003&MI_00
17/12/2021 14:38:11(749): ExecutionManager.AutoConnectStart:Started auto connect timer
17/12/2021 14:38:11(764): MobiflightModule.connect: Connected to Default at COM4 of Type Arduino Mega 2560 (DTR=>True)
17/12/2021 14:38:13(152): MobiFlightModule.GetInfo: MobiFlight Mega, Mega Msfs ,1.11.3, SN-157-2f2
17/12/2021 14:38:13(230): MobiflightModule.disconnect: Disconnected Mega Msfs  at COM4
17/12/2021 14:38:13(240): MobiFlightCache.LookupAllConnectedArduinoModulesAsync: End
17/12/2021 14:38:13(245): MobiFlightCache.connect: Clearing modules
17/12/2021 14:38:13(250): MobiFlightCache.RegisterModule(Default:COM4)
17/12/2021 14:38:13(255): MobiflightModule.connect: Connected to Default at COM4 of Type MobiFlight Mega (DTR=>True)
17/12/2021 14:38:14(215): No config found for Encoder: Baro Knob @./a
17/12/2021 14:38:14(629): MobiFlightModule.GetInfo: MobiFlight Mega, Mega Msfs ,1.11.3, SN-157-2f2
17/12/2021 14:38:14(652): SimConnectCache::ClearSimVars . SimVars Cleared
17/12/2021 14:38:14(932): CheckForUpdate : Checking for RELEASE update...
17/12/2021 14:38:15(216): CheckForUpdate : MobiFlight is up to date.
17/12/2021 14:38:15(224): ExecutionManager.TestModeStop:Stopped test timer
17/12/2021 14:38:15(229): SimConnectCache::ClearSimVars . SimVars Cleared
17/12/2021 14:40:10(923): Set Debug in ComboBox: logLevelComboBox
17/12/2021 14:40:15(788): Fsuipc2Cache::connect() - No FSUIPC found.
17/12/2021 14:40:15(826): SimConnectCache::ClearSimVars . SimVars Cleared
17/12/2021 14:40:15(920): SimConnectCache::Exception ALREADY_CREATED
17/12/2021 14:40:15(927): SimConnectCache::Exception ALREADY_CREATED
17/12/2021 14:40:15(933): SimConnectCache::Exception ALREADY_CREATED
17/12/2021 14:40:15(950): No config found for Button: Button 19 @.
17/12/2021 14:40:15(958): No config found for Button: Button 27 @.***
17/12/2021 14:40:15(964): No config found for Button: Button 28 @.***
17/12/2021 14:40:15(969): No config found for Button: Button 32 @.***
17/12/2021 14:40:15(975): No config found for Button: Button 35 @.***
17/12/2021 14:40:15(980): No config found for Button: Button 37 @.***
17/12/2021 14:40:15(986): No config found for Button: Button 39 @.***
17/12/2021 14:40:15(992): No config found for Button: Button 41 @.***
17/12/2021 14:40:15(997): No config found for Button: Button 43 @.***
17/12/2021 14:40:16(5): No config found for Button: Button 45 @.***
17/12/2021 14:40:16(13): No config found for Button: Button 47 @.***
17/12/2021 14:40:16(22): No config found for Button: Button 13 @.***
17/12/2021 14:40:16(28): No config found for Button: Button 15 @.***
17/12/2021 14:40:16(35): No config found for Button: Button 17 @.***
17/12/2021 14:40:16(41): No config found for Button: Button 19 @.***
17/12/2021 14:40:16(47): No config found for Button: Button 21 @.***
17/12/2021 14:40:16(54): No config found for Button: Button 24 @.***
17/12/2021 14:40:16(61): No config found for Button: Button 26 @.***
17/12/2021 14:40:16(67): No config found for Button: Button 27 @.***
17/12/2021 14:40:16(74): No config found for Button: Button 29 @.***
17/12/2021 14:40:16(80): No config found for Button: Button 32 @.***

@Fellstone7 can you please tell me if this problem persists in 9.2?

Its still the same. The wasm connection and the sim are only picked up when I change a setting or alter a setting so the ok button on settings cam be click. Its like this triggers a reset or a sim check. Mobiflight then connects and srinks into the background running icons in the toolbar.
From: Sebastian @.>
Sent: 29 December 2021 20:13
To: MobiFlight/MobiFlight-Connector @.>
Cc: Fellstone7 @.>; Mention @.>
Subject: Re: [MobiFlight/MobiFlight-Connector] Mobiflight not recognizing MSFS has started automatically in version 9.1 (Issue #615)
@Fellstone7 https://github.com/Fellstone7  can you please tell me if this problem persists in 9.2?
—
Reply to this email directly, view it on GitHub https://github.com/MobiFlight/MobiFlight-Connector/issues/615#issuecomment-1002759935 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AW5ITP4NOSM5GQZGJL3ZDFDUTNTUXANCNFSM5KAKITBA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AW5ITPY766MOVSN7UDQF4LDUTNTUXA5CNFSM5KAKITBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHPCON7Y.gif Message ID: @.*** @.***> >

@Fellstone7  please try latest beta or 9.3 release and let me know if it still is a problem

Hi Sebastian
I am still having to manually kick MF to connect  to MSFS via a setting change.
N
From: Sebastian M @.>
Sent: 07 March 2022 18:30
To: MobiFlight/MobiFlight-Connector @.>
Cc: Fellstone7 @.>; Mention @.>
Subject: Re: [MobiFlight/MobiFlight-Connector] Mobiflight not recognizing MSFS has started automatically in version 9.1 (Issue #615)
@Fellstone7 https://github.com/Fellstone7  please try latest beta or 9.3 release and let me know if it still is a problem
—
Reply to this email directly, view it on GitHub https://github.com/MobiFlight/MobiFlight-Connector/issues/615#issuecomment-1060998555 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AW5ITP26I6FRCYSAAEMKEYLU6ZDMFANCNFSM5KAKITBA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AW5ITP47B4OBOXC4MA2GSJDU6ZDMFA5CNFSM5KAKITBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH46Y3GY.gif Message ID: @.*** @.***> >

@Fellstone7 is this resolved in 9.3? The WASM connection method was changed and hopefully it is working for you now.

Hi Sebastian
I still have to go into settings and change any parameter and change back then press ok to kick start Mobiflight. It works perfectly after that.
Thanks for keeping though on this minor issue.
Regards
Nigel
From: Sebastian M @.>
Sent: 02 April 2022 21:02
To: MobiFlight/MobiFlight-Connector @.>
Cc: Fellstone7 @.>; Mention @.>
Subject: Re: [MobiFlight/MobiFlight-Connector] Mobiflight not recognizing MSFS has started automatically in version 9.1 (Issue #615)
@Fellstone7 https://github.com/Fellstone7  is this resolved in 9.3? The WASM connection method was changed and hopefully it is working for you now.
—
Reply to this email directly, view it on GitHub https://github.com/MobiFlight/MobiFlight-Connector/issues/615#issuecomment-1086712836 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AW5ITPYA2T3T5UU7WOSGW63VDCRSNANCNFSM5KAKITBA .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AW5ITP3P27ZGTGVVWCO6D4LVDCRSNA5CNFSM5KAKITBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIDC6YBA.gif Message ID: @.*** @.***> >

I can't reproduce it and it is nothing that other users are reporting. We can still have a screen share session some time but I will close this for now.


Activation with MacOS server network account

We have office365 Proplus Licences for our teachers and students.
The students have network server accounts (MacOS10.11server).
Activation is ok with local accounts (MacOS10.13) but not with network accounts.
Is it possible to use Proplus licences for network accounts?
Thanks

OK, thanks


Feature request: yalc watch

Would be amazing to have a yalc watch script that automatically watches your package during development, and essentially runs a yalc push on changes.
My use case: Currently running yalc push manually when I have made a significant change that I want to test in my main application (where it is linked)
Potentially this just watches the whole package, or perhaps could specify a key file or folder to watch, eg: yalc watch src/index.js
What do you think?

Hi, there was discussion about such requests https://github.com/whitecolor/yalc/issues/15
You can use something like nodemon -x 'yalc push'
I actually would not use this, but make more consistent changes to the package, then push it. If i'm actively developing the code that is used in the app, I maked it a part of the app first, then take it out into separate package.

If you build your packages using webpack, this is a simple recipe you can use.  This watches the upstream package and auto-pushes (to downstream) after each webpack build:
yarn add -D yalc webpack-shell-plugin
package.json:
  "scripts": {
    "watch": "npm run clean && WATCH=true YALC=true webpack --progress",

webpack.config.js:
const ShellPlugin = require("webpack-shell-plugin");
const postBuildScript = process.env.YALC === 'true' ? 'npx yalc push' : 'true';
...
   watch: process.env.WATCH === "true",
   plugins: [
      new ShellPlugin({ onBuildExit: postBuildScript }),
   ],

then:
~/upstreampkg $ npm run watch

I came here looking for such a feature, but in the end turns our I didn't need it. My current setup involves a UI library that I have as a separate repo, bundled with rollup.js in watch mode, then i have a nodemon that watches the output directory of rollup for changes and fires yalc push, finally, i have my actual app running with hot reloading. I can have all of those running at the same time, any change to the UI project gets pushed through this pipeline to my app in <2s. I'm actually thinking about writing a post about this setup, it works like magic.

Hello!
I'm bumping this idea because even though there are use cases where I could see this being inessential, there certainly are use cases where having a yalc watch would be extremely useful. For example, I am the primary developer of a Language Server, which has implementations in various clients; the Language Server, therefore, needs to be a separate package from each client, which also means a separate repo. Previously, things were a mess of copy file paths and manually starting servers. Yalc has simplified that significantly, and the only thing that would make it better would be a yalc watch. I currently use nodemon to simulate a yalc watch, but it isn't ideal.
I am very willing to put in the work to properly create this feature, if I could be pointed in the right direction to start.

Did you try to use existing watching solutions like nodemon -x 'yalc push'?
If you need something more custom you can easily create it on your own using some watching library. I don't see a reason to add such functionality to yalc itself.

I did and it works, but if one tries (like I am) to not require other devs to add anything to their PATH (the software is complicated enough as is, I don't need to scare off potential contributors with a confusing setup) then you end up creating a watch script like this:
		"testWatch": "concurrently --kill-others \"tsc --watch\" \"yalc publish && nodemon --exec npm run dev\"",
		"dev": "yalc push"

Which you know, hey that works, but it's still quite a confusing mess. Additionally, it watch compiles initially very strangely where error pop up as the watch slowly compiles, only to be erased as the compile finishes. Which is fine, but it catches people a bit off-guard.
Anywho, it's your repo and you seem determined. I've got a solution, albeit a messy one.

@matdru can you elaborate a bit more? Using rollup too....

There is also publish/push --changed flag was added that will publish only if the content of the package has really changed comparing to published version

@whitecolor Why wouldn't --changed be the default?

@whitecolor Why wouldn't --changed be the default?

Don't see the big reason to do it by default for manual publish.

I don't think it's resolved issue, while it's possible to use nodemon, it's not always fitting (eg. if you use typescript or some sort of other files like html/css/yaml etc files.
Each of those might require some custom setup, which takes development time.
I think something like yalc watch could work like

It'd watch current folder for changes (maybe only files not listed in .npmignore etc)
after every file change it'd run yarn publish
it could potentially rebuild the package
you'd be able to instantly check new changes in connected project

While I appreciate this package, I think it'd be very useful.
If you have to iterate a lot on some package before you're happy with the result - difference between 5s vs 30s of each iteration (and avoiding 20mins-1h of manual setup of watching files) is a big deal that could result in actually either keeping some package alive or making it slowly stale and dead because you'd prefer to workaround something rather then work on package with slow iteration speed / being aware you need some custom setup to improve iteration time

You can also update your yalc package by using tsc-watch and the onSuccess flag.
https://www.npmjs.com/package/tsc-watch
package.json
// ..
"scripts": {
    "dev-watch": "tsc-watch --onSuccess \"yalc push\""
  }
// ..

This works for me and hopefully also for you ;D

nodemon --watch dist --exec "yalc push "


(fix) change how PancakeSwap fetches V2 pools

Before submitting this PR, please make sure:

[X] Your code builds clean without any errors or warnings
[X] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:

Changes PancakeSwap V2 pool fetch to include all V2 pools, not just stable pools
Fixes https://github.com/hummingbot/gateway/issues/369

Tests performed by the developer:

Tested with CAKE-USDT and verified that /amm/price returned same buy and sell prices as PancakeSwap UI

{
    "chain": "{{chain}}",
    "network": "{{network}}",
    "connector": "pancakeswap",
    "base": "CAKE",
    "quote": "USDT",
    "amount": "1",
    "side": "SELL"
}

Tips for QA testing:

Test performed:

Cloned and installed PR371 + Client latest dev branch
connected pancakeswap_binance-smart-chain_mainnet and pancakeswap_ethereum_arbitrum successfully
checked balance successfully
checked amm/price : ok
amm/trade: ok


refac: simplify unknown client rejection

PR Type
Enhancement

Description

Centralized the reject_unknown_client check in the metrics_wrapper function, removing redundant checks from individual RPC methods.
Improved span handling in the eth_subscribe function for better performance and clarity.
Updated imports and function visibility for better code organization.
This refactoring simplifies the code, reduces duplication, and improves maintainability without changing the overall functionality.

Changes walkthrough 📝
Relevant filesEnhancement

mod.rsAdd import for reject_unknown_client

src/eth/rpc/mod.rs

Added import for reject_unknown_client function

+1/-0

rpc_method_wrapper.rsCentralize reject_unknown_client check in metrics_wrapper

src/eth/rpc/rpc_method_wrapper.rs
Moved reject_unknown_client check to the metrics_wrapper function  Updated imports to use more specific paths

+5/-2

rpc_server.rsSimplify RPC methods by removing redundant checks

src/eth/rpc/rpc_server.rs
Removed individual reject_unknown_client checks from various RPC methods  Updated eth_subscribe function to handle span clearing more efficiently  Changed visibility of reject_unknown_client function to pub(super)

+5/-17

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Final benchmark:
RPS Stats: Max: 909.00, Min: 772.00, Avg: 831.60, StdDev: 22.36
TPS Stats: Max: 897.00, Min: 772.00, Avg: 831.27, StdDev: 21.56
Plot: View Plot


Code splitting -> wrong order

This is my intent (choose one)

[ ] I want to report a bug
[x] I want to request a feature or change
[ ] I want to provide or change a feature

The problem
When using hops-react, the vendor chunk is loaded after the main chunk in production mode.
Development mode behaves correctly.
Proposed solution
In @untool/react/lib/template.js, we could change the renderCSS and renderJS function to reverse the array, before joining it. But maybe the issue lies already in the accumulation step of assetsByType...

This might be another option: https://github.com/untool/untool/blob/fc24e027db507914596370ba4cd25ce953a2a2c8/packages/webpack/lib/plugins/assets.js#L35

Thanks for this bug report, @tjwelde! The latest pre-release version of hops-react (11.0.0-rc.33) ought to already contain the upstream fix you linked to. Are you already running that version? If not, would you mind updating?

I am running an older version, indeed. Will try it out.

Thanks, it works!


Uncaught Error: Module did not self-register. During attempted rename of file

[Enter steps to reproduce:]

...
...

Atom: 1.46.0 x64
Electron: 4.2.7
OS: Unknown macOS version
Thrown From: Atom Core
Stack Trace
Uncaught Error: Module did not self-register.
At ELECTRON_ASAR.js:160

Error: Module did not self-register.
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
    at Function.Module._load (internal/modules/cjs/loader.js:533:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at customRequire (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:1:695134)
    at get_KeyboardLayoutManager (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2778162)
    at get_manager (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2778264)
    at Object.getCurrentKeyboardLayout (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2778390)
    at e.keystrokeForKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1081110)
    at KeymapManager.keystrokeForKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1253631)
    at KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1251616)
    at WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:284744)

Commands
     -0:49.5.0 tree-view:move (span.name.icon.icon-file-text)
     -0:26.6.0 tree-view:rename (div.title)

Non-Core Packages
ide-vue 0.1.9
language-vue 0.25.0
platformio-ide-terminal 2.9.1

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/20222. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Prepare 0.21.2 release

Summary
Details and comments
Waiting on #8415 (and its subsequent backport).

We're (Matthew and I) talking about what we want to do about the pins of setuptools in the build process (see #8530).  Ideally we'd release without any pins, but if we need to, at least they're only in the build process, which should be isolated from any other installation or build.


Adding skip + warning message for quesiton with badly formed xml from…

… ascirbe

This PR resolves #730.

Resolves #729.


Allow _.reduce and _.reduceRight to have an explicitly undefined initial value

Allow _.reduce and _.reduceRight to have an explicitly undefined initial value as the native fork allows.
Fixes the previous issues w/ the patch that caused it to be reverted.

This pull request may have merge conflicts w/ pull request #390. Let me know if there are issues and I will fix this one.


Fixed link to releases page

@veleek,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


enum class like in Rust

i think this nice feature to add, i think about this macro:
enum_class Op,
  Inc(val : Int32),
  Move(val : Int32),
  Loop(loop : Array(Op)),
  Print

which expanded to:
module Op
  record Inc, val : Int32
  record Move, val : Int32
  record Loop, loop : Array(Op::T)
  record Print

  alias T = Inc | Move | Loop | Print
end

but if it would possible that Op be resulted type, not Op::T (thats nicer)?
ops = [] of Op
ops << Op::Inc.new(1)

I may be wrong, but the languages that support it doesn't support union types as Crystal do. The functionality seems to overlap, only with different syntax. Do you have an user case where using this kind of enums would be significantly better than simply creating records/classes for each element and using them?

Also:
abstract struct Op; end
record Inc < Op, val : Int32
record Move < Op, val : Int32
record Loop < Op, loop : Array(Op)
record Print < Op

That's what you traditionally do in OOP languages. That has the benefit that you can use case op; when Inc, or you can add methods to Op to perform polymorphic dispatch.
What we do need is a way to have case check that all possible cases are covered. The same would apply to an enum. But that's a different issue (I think there's an existing issue for that).

i used it here: https://github.com/kostya/benchmarks/commit/a4f403fb1c6f003b4352075d608189677aa0e588 and it give 20% performance, comparing to symbols

@asterite #285 is the issue you refer to.
I think is a nice use case to have what @kostya propose. It's like a algebraic type in Haskell. Plain:
data Op = Inc Int | Move Int | Loop [Op] | Print
But is useful as long as you do not need to reopen each of those types. There you need to know what is the macro doing and is a leak of abstraction.
The fact that they are different types allow us to use method & cases to match the constructor. But it lacks of proper pattern matching. If we reach proper pattern matching then it might have more sense definitely.
Even so, the question is if it is a good idiom for crystal when used just as a bunch of records.
I don't know if in the compiler itself would be useful. But it seems like a nice helper to have IMO.

@kostya The performance improvement is probably because before the change you switched over the symbol, and then you used as, which does a check against a type id. So, two checks. Using case ...; when Inc just does one check.

i tried with two fields also record Op, op : Symbol, val : Int32, loop : Array(Op)?, but also slow


Feature #3137: allow sending attachments via Graph API

Type

[ ] Bug Fix
[x] New Feature
[ ] Sample

Related Issues?
Fixes #3137
What is in this Pull Request ?
Added attachments parameter to Send-PnPMail to allow sending attachments
Summary

copilot:summary
Details

copilot:walkthrough

🫡


TypeError: Cannot read property 'hash' of undefined

Bug report

What is the current behavior?
We are moving from Webpack 3 -> Webpack 5, and we have been able to (we believe) adjust the config files appropriately, however, the web app fails to compile. It keeps erroring out on compilation when we call devServer.start() within 'scripts/start.js' with:
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:3000/
<i> [webpack-dev-server] On Your Network (IPv4): {{ REDACTED FOR SECURITY PURPOSES }}
<i> [webpack-dev-server] Content not from webpack is served from '.../xui/public' directory
<i> [webpack-dev-server] 404s will fallback to '/index.html'
Starting the development server...

.../xui/node_modules/webpack/lib/NormalModule.js:1307
                hash.update(this.buildInfo.hash);
                                           ^

TypeError: Cannot read property 'hash' of undefined
    at NormalModule.updateHash (.../xui/node_modules/webpack/lib/NormalModule.js:1307:30)
    at Compilation._createModuleHash (.../xui/node_modules/webpack/lib/Compilation.js:3239:10)
    at Compilation.createModuleHashes (.../xui/node_modules/webpack/lib/Compilation.js:3210:10)
    at .../node_modules/webpack/lib/Compilation.js:2469:11
    at Hook.eval [as callAsync] (eval at create (.../xui/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (.../xui/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
    at .../xui/node_modules/webpack/lib/Compilation.js:2429:36
    at Hook.eval [as callAsync] (eval at create (.../xui/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (.../xui/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
    at Compilation.seal (.../xui/node_modules/webpack/lib/Compilation.js:2420:27)
error Command failed with exit code 1.

We've attempted to use even the default settings for getting webpack up and running and rebuilding everything from scratch.
If the current behavior is a bug, please provide the steps to reproduce.
Here is the slimmed-down version of the repo. The error still persists in the slimmed down version
https://github.com/mexicantexan/webpack-error-reproduction
Here is the Stackoverflow question as well:
Stack Overflow link
To reproduce:

install packages under "xui" with "yarn install"
start the application with "yarn start"
Notes: I kept the old package.json file for reference labeled as 'package-old.json'. I also left the old config files in "xui/config", the current config file is labeled as "xui/config/webpack.config.new.js"

What is the expected behavior?
The expected behavior is for the development server to finish compiling with react@^17 and webpack@^5.

Other relevant information:
webpack version:  5.52
Node.js version: 16.8.0
Operating System: Linux 20.04
Additional tools:

When you create reproducible test repo please avoid using private package, unfortunately nobody can test it:
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"401 Unauthorized\"".
info If you think this is a bug, please open a bug report with the information provided in "/path/to/webpack-error-reproduction/xui/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

You apply BundleTracker in wrong place, remove it from resolve.plugins, it is wrong place to put this in plugins for resolver, I recommend to use ts/jsdocs ts to avoid these problems in future

@alexander-akait Thank you, you just saved us a bunch of heartache! Very much appreciated


Option to turn off Image Feed

The image feed is always there on the upper right corner, pls add an option to hide it.

The option "Show Image On Menu" seems like it should be the setting to disable the button, but that option appears to do nothing.

This is fixed, the button will only show if the image feed is closed and never if the setting is set to hidden


[Event Request] Table 6651 OnInsertInvLineFromRetShptLineOnBeforeValidatePurchaseLine and 6661 OnInsertInvLineFromRetRcptLineOnBeforeValidateSalesLineQuantity

In the new trigger OnInsertInvLineFromRetShptLineOnBeforeValidatePurchaseLine in table 6651 we Need the PurchaseLine as VAR Argument. The same with the trigger OnInsertInvLineFromRetRcptLineOnBeforeValidateSalesLineQuantity in table 6661 and SalesLine.
See also table 111 OnInsertInvLineFromShptLineOnBeforeValidateQuantity, where this is already solved:
Table 6651
old:
LOCAL [IntegrationEvent] OnInsertInvLineFromRetShptLineOnBeforeValidatePurchaseLine(VAR ReturnShipmentLine : Record "Return Shipment Line";PurchaseLine : Record "Purchase Line";VAR IsHandled : Boolean)
New:
LOCAL [IntegrationEvent] OnInsertInvLineFromRetShptLineOnBeforeValidatePurchaseLine(VAR ReturnShipmentLine : Record "Return Shipment Line";VAR PurchaseLine : Record "Purchase Line";VAR IsHandled : Boolean)
Table 6661:
old:
LOCAL [IntegrationEvent] OnInsertInvLineFromRetRcptLineOnBeforeValidateSalesLineQuantity(VAR ReturnReceiptLine : Record "Return Receipt Line";SalesLine : Record "Sales Line";VAR IsHandled : Boolean)
new:
LOCAL [IntegrationEvent] OnInsertInvLineFromRetRcptLineOnBeforeValidateSalesLineQuantity(VAR ReturnReceiptLine : Record "Return Receipt Line";VAR SalesLine : Record "Sales Line";VAR IsHandled : Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Illuminate\Support\Collection is not deteced as Countable

Larastan Version: #.#.#
--level used: 2

Description
Access to an undefined property Illuminate\Support\Collection::$count.

namespace Illuminate\Support;

class Collection implements ArrayAccess, Arrayable, Countable, IteratorAggregate, Jsonable, JsonSerializable
{

http://php.net/manual/en/countable.count.php
Laravel code where the issue was found
        $results = DB::table('artworks')->selectRaw("
            ifnull(case
                when meta->\"$.price.{$currency}\" between 0 and {$step} then 1
                when meta->\"$.price.{$currency}\" between {$step} and ({$step} * 2) then 2
                when meta->\"$.price.{$currency}\" between ({$step} * 2) and ({$step} * 3) then 3
                when meta->\"$.price.{$currency}\" between ({$step} * 3) and ({$step} * 4) then 4
            end, 0) as category, count(id) as count"
        )->where('database_id', $this->database->id)
        ->whereNotNull('deleted_at')->groupBy('category')->get();

        while ($start < $max->price) {
            $data['labels'][] = $start . " - " . ($start + $step);
//   -------- HERE --------
            $data['datasets'][0]['data'][] = $results->firstWhere('category', $category)->count ?? 0;
            $category++;
            $start += $step;
        }

It turns out "count" is an SQL column: count(id) as count
What to do now?

The error is correct here. Collection does not have count property. It has count method.

@canvural Is there a laravelish way to tell phpstan what are the SQL fields?
Which later turn out to be PHP properties of the Collection.

I don't understand. What SQL fields are you talking about?

In the above code there is selectRaw("... as category, count(id) as count"), so category and count.
How can I tell phpstan that the Collection will have these properties?

But that's still not true. Collection will not have those properties. It will just have an array of objects. And those objects will have properties.
I don't know if PHPStan supports specifying properties on plain object Or you can create an object to represent that data, and typehint that.

I see!
I've just created such a class yesterday https://github.com/szepeviktor/phpstan-wordpress/blob/master/example/class-wp-nav-menu-item.php


linked-list:  verify ordering of actual/expected

In the Jasmine testing framework, it is convention to:
expect(actual).fn(expected)

But some test suites have the following:
expect(expected).fn(actual)

This causes the error messages to be confusing.
Please verify the linked-list exercise to make sure that the expectations are ordered correctly. If they are, then this can be closed.
This issue will help to close #111

Got it

This one is OK and can be closed.
I did find a test without an expectation while checking this, which I raised as issue #270

Thanks! Nice catch!


Write tagline(s) for the new GCtools brand, based on name and themes

Determine a tagline for the GCtools brand, if needed. The tagline should follow the chosen name and theme, and be aligned with our vision and mission statements.

Tagline will simply be "The open, accessible, digital workspace."


Fix journal shutdown deadlock

What changes are proposed in this pull request?
TakeSnapshot in JournalStateMachine calls a Ratis function that needs to acquire a lock in the RaftServerProxy.
When the raft server is shutting down it takes the lock in RaftServerProxy then waits for the state machine thread thread to finish while holding this lock. This causes a deadlock.
This PR fixes this by ensuring takeSnapshot will not take this lock once shutdown has started.
Does this PR introduce any user facing changes?
No

Thanks for the fix.
was there a manual validation or a test to validate this fix?  @tcrain

The RaftJournalTest tests will occasionally deadlock without this fix, especially the JoinCluster test, e.g. if you run it repeatedly you will pretty quickly see the deadlock.
The deadlock happens when the leading master needs to take a snapshot, and the shutdown is being called.
In this PR https://github.com/tcrain/alluxio/commit/94316d7ab9155e9b8a05b60702c173d5a59078cb I changed the RaftJournalTest so it was taking snapshots during the test, which is what exposed this deadlock.

alluxio-bot, merge this please

I guess I would also suggest that this is a design issue in Ratis and not necessarily in the Alluxio code, as the deadlock is embedded in the Ratis code, and Alluxio is just using the Ratis methods.


validate-config: check .packit.yaml content

multiple changes here:

we parse PackageConfig (PC) only once

we use PC's parsing mechanism as the form to validate

validation code is moved to a dedicated module

related tests are cleaned up and simplifed

Fixes #884

Thanks for working on this!
First thought :slightly_smiling_face:

PackitAPI is not used b/c we don't want PC (API needs it)

Is there a reason this being the case?
My way of thinking is that while PackitAPI needs packit configuration to function, it would need a package config only when actually working with a package. Decoupling things like this would allow us to do work on multiple packages using the same PackitAPI object.
It would also allow us to keep validate as part of the API, and remain consistent with the CLI.
I know, the above would be a completely different change to implement, still, I feel that this would be The Good Thing to do. What do you think?

Thanks for working on this!
First thought slightly_smiling_face

PackitAPI is not used b/c we don't want PC (API needs it)

Is there a reason this being the case?

There was when I started working on it. Now when I look how the PR evolved, the suggestion makes sense and gonna do it. :+1:

/packit build


Update changelog for 21.06 release [skip ci]

Signed-off-by: Sameer Raheja<EMAIL_ADDRESS>Draft changelog PR for review.  Will update after final PR merge.

Updated the changelog just for review, I can update it one more time before we are ready to freeze.


Android Chrome Browser

we are using input mask plugin in our project to get the formatted field from user as follows
xx-xxx-xx
when user delete the last two x using the backspace in chrome browser and still want to delete the remaining content it is not allowing the user to go beyond the hyphen even if we press the backspace key. I found that Android is not triggering any key up/down event for its back space key.
is there any solution for this issue?

is there any update?

Thank you for marking this to your next upcoming version 3.3, I appreciate your immediate response.

@kaarthikraajan ,
Can you retry with the latest version on github


command .net new project doesn't work.

URL
https://dotnet.microsoft.com/ru-ru/learn/dotnet/hello-world-tutorial/create
Operating system
windows
More information about your system
Windows 11, 64 bit, VSC.
Description
Hellow. When I try to write in the search of Visual Studio Code: ">.NET: New Project", I get an error: "Command '.NET: New Project...' resulted an error". I tried to use terminal "dotnet new console", but I got an error:
"The command could not be loaded, possibly because:

You intended to execute a .NET application:
The application 'new' does not exist.
You intended to execute a .NET SDK command:
No .NET SDKs were found."

I have already installed .NET from official site, c# and c# dev Kit from VSC. Help me, please.
dotnet --info
global.json file:
Not found
Host:
Version:      6.0.10
Architecture: x86
Commit:       5a400c212a
.NET SDKs installed:
No SDKs were found.
.NET runtimes installed:
Microsoft.NETCore.App 5.0.17 [C:\Program Files (x86)\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.10 [C:\Program Files (x86)\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files (x86)\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files (x86)\dotnet\shared\Microsoft.WindowsDesktop.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info

You indicated that your system is x64 but your dotnet --info shows it's trying to execute the x86 and that it has found other architectures. I think this is a problem with PATH.
Type the command where.exe dotnet and see if x86 is returned first. If so, follow the instructions at https://github.com/dotnet/core/issues/5962#issuecomment-780084535.
Let me know if this solves your issue!

I tried to do it but nothing changes. When I write: "where.exe dotnet" I get "C:\Program Files\dotnet\dotnet.exe
C:\Program Files (x86)\dotnet\dotnet.exe". Help me, please.

Can you share the version of VS Code and where did you run the command dotnet --info? Because where you ran that command is a x86 arch, so it's not finding the SDK.
adding @webreidi @smitpatel to see if they have other suggestions

Based on output, it looks like only .NET runtime is installed on the machine not SDK.


Bug in System.Text.Json number handling

The generated code for reading a value uses
options.NumberHandling == global::System.Text.Json.Serialization.JsonNumberHandling.AllowReadingFromString
to check if reading from strings is enabled. However JsonNumberHandling is a [Flags] enum and therefore this fails if multiple options are set (e.g. NumberHandling = JsonNumberHandling.AllowReadingFromString | JsonNumberHandling.WriteAsString).
This was originally raised by @MGRatEJOT

I don't that fixing this will be a breaking change because there should be nothing out there serialized as string and hence failing the incorrect reading logic (the reading logic currently says 'if it is exactly 'allow reading from string' and the token is a string).

Fixed in 4.0.5


Williamsburg, VA Police

To<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: [*** INSERT UNIQUE SUBJECT LINE***]
Message (Don't forget to replace the [x]'s with your information!)
Dear Mayor Freiling and City Council Members,
My name is [YOUR NAME] and I am a resident of [NEIGHBORHOOD/CITY/COLLEGE].
I am writing today in solidarity with the current global call to dismantle and restructure the racist history of police in the United States. The Williamsburg police department is a part of this system and, as your constituent, I am calling on you to meaningfully defund the police.
As elected city representatives, you must address the disproportionate policing of Black people happening in Williamsburg. Based on data from the Vera Institute of Justice, Black Americans make up 12% of the U.S population but account for an estimated 28% of all arrests nationally; according to the official 2019 police report for the city of Williamsburg, 47% of people the Williamsburg Police arrested were Black, despite the fact that only 14% of Williamsburg’s population is Black. This is an astronomical increase of an already biased and discriminatory national trend.
Recently, the police department’s spokesperson argued that the department maintains a bias-free police force through their training efforts. Heilman also claimed that the police exercise their duties, responsibilities, and obligations “in manner that does not discriminate based on race, sex, gender, national origin, ethnicity, age, or religion.” However, the disproportionate number of arrests of Black people in the community clearly shows that all this training is not working.
According to the 2018 Census, 19.4% of Williamsburg’s White population lived below the nationally-established poverty line while 30% of Williamsburg’s Black population lived in poverty. This matters when it comes to policing because, as reported by the Massachusetts Poverty Law Advocates group, two-thirds of people detained in US jails live in poverty. Overall, police-related death rates are highest in neighborhoods with the greatest concentrations of low-income residents and residents of color, as demonstrated in a 2019 study by the American Public Health Association.
In the proposed $57 million city budget for fiscal year 2021, the police department is allotted almost $12 million ($11,974,256), or approximately 20% of the total budget, while less than $3 million is allotted for public assistance and human services, including homeless intervention and Food Stamp applications ($2,936,270) -- 5% of the total budget. This misdirection of funds creates a city that is better equipped to harm its residents than help them. The average time spent on a waitlist to get into an HUD housing program is 11 months, and that time frame jumps to 18 months for Williamsburg public housing programs. In addition, 21% of police calls that resulted in the use of force in 2019 were for mental illness. The Williamsburg community deserves a balanced budget that takes the basic rights and needs of its citizens into its forefront consideration.
Your decision to fund the police instead of contributing to human services and public outreach programming actively puts Williamsburg’s Black population at risk. Both the past and the present prove that police “reform” is not enough. Williamsburg must defund the police department in order to meet the needs of its residents and actually protect the community.
Sincerely,
[YOUR NAME]
[YOUR ADDRESS]
[YOUR EMAIL]
[YOUR PHONE NUMBER]

closed by #1143

closed by #1143

closed by #1143

closed by #1143

closed by #1143


IGNITE-17251 Fix parsing of encrypted records by IgniteWalConverter

Please see the ticket's description for details: https://issues.apache.org/jira/browse/IGNITE-17251
Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[x] There is a single JIRA ticket related to the pull request.
[x] The web-link to the pull request is attached to the JIRA ticket.
[x] The JIRA ticket has the Patch Available state.
[x] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[x] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[x] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[x] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

The patch looks good to me, thanks!

I've re-run the basic tests: https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunBasicTests/6657118?buildTab=overview


ipcache: Skip conflict logging for tunnelpeer if native routing

See https://github.com/cilium/cilium/issues/26817 and specifically
https://github.com/cilium/cilium/issues/26817#issuecomment-1668628719
for more details.
In summary, it is safe to skip logging the tunnelpeer conflict if Cilium
is configured with native routing, because the tunnel is not used at all
anyway.
The log msg was triggered in the case that the router IP was configured
to be the same across all nodes, a la --local-router-ip, in native
routing mode.
Fixes: https://github.com/cilium/cilium/issues/26817
Suggested-by: Tamilmani Manoharan<EMAIL_ADDRESS>Signed-off-by: Chris Tarazi<EMAIL_ADDRESS>

cc @tamilmani1989

/test

Hi @christarazi, can this change be backported to cilium 1.14? Using cilium 1.14.4 with routing-mode:native and delegated ipam, and I was seeing the warning message in the logs


Consider setting panic to abort in teos

The panic behavior is set to unwind at the moment (default), however, this means that if an async task fails, the daemon may not crash but the task will. This can set the daemon in a weird state where some things are expected to be running but they are not.
An example to this is trying to run the daemon with tor support while the tor connection cannot be stablished:
> ./target/debug/teosd --torsupport
Loading configuration from file
2022-05-16T20:28:27.679Z INFO [teosd] tower_id: 02bd2b759dd8a4fcef0f7d9692c105da8400d5da7942ee039e869fbfb8738ffde4
2022-05-16T20:28:27.683Z INFO [teosd] Last known block: 489b5e533c960d070795bb49cdc9d8dad15aef3414d77449107a84beaeb41020
2022-05-16T20:28:27.690Z INFO [teosd] Bootstrapping from backed up data
2022-05-16T20:28:27.690Z INFO [teosd] Bootstrap completed. Turning on interfaces
2022-05-16T20:28:27.690Z INFO [teosd] Starting up hidden tor service
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: ConnectionRefused, error: Custom { kind: ConnectionRefused, error: "failed to connect to tor control port" } }', teos/src/main.rs:281:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2022-05-16T20:29:11.532Z INFO [teos::api::http] Received get_appointment request from <IP_ADDRESS>:53555
2022-05-16T20:29:11.553Z INFO [teos::api::http] Request failed, error_code=7
2022-05-16T20:29:11.985Z INFO [teos::api::http] Received get_appointment request from <IP_ADDRESS>:53556
2022-05-16T20:29:12.004Z INFO [teos::api::http] Request failed, error_code=7

We should consider changing the panic behavior or making this crash the daemon in some way.
Source: https://users.rust-lang.org/t/panic-in-tokio-task-does-not-end-the-program-execution/45731

@tee8z

In the Cargo.toml file we can configure the program to abort on panic instead by adding:
[profile.release]
panic = 'abort'

I'm not familiar with the entire codebase so I'm not sure if this will cause any other issues, though if it does we probably want to handle those panics differently as well.
Thoughts? I'd be happy to open a PR to fix this.

@booklearner I'm pretty sure I tried that back in the day but it didn't work. You're more than welcome to give it a go though.

Keeping an eye on this https://github.com/tokio-rs/tokio/issues/4516


Password error

I don't now the password in the grafical web site

There are two accounts, user and root. In both cases the password is password
In any case the system will automatically boot into a graphical session for the user user, the password is not required unless you need to become root using su


Add Tests for *-computer cmdlets

This PR also removes code protected by #!CORE in Computer.cs which removed a very large amount of code.
In order to test without actually rebooting the system, I implemented a number of InternalTestHooks to avoid making the call to actually calling the CIM method to actually reboot/halt the system. While I was in the code I simplified a number of parameters, especially throttling, which was way more complicated than it needed to be.

            throttlelimit = value;

Shouldn't this logic remain for cases where the cmdlet is called programmatically?

Refers to: src/Microsoft.PowerShell.Commands.Management/commands/management/Computer.cs:207 in e283582. [](commit_id = e28358202134177049fe78beba58357ff878b888, deletion_comment = True)

    [ValidateSet(ComputerWMIHelper.DcomProtocol, ComputerWMIHelper.WsmanProtocol)]

The ValidateSet should be updated as well.

Refers to: src/Microsoft.PowerShell.Commands.Management/commands/management/Computer.cs:102 in e283582. [](commit_id = e28358202134177049fe78beba58357ff878b888, deletion_comment = False)

    [ValidateSet(ComputerWMIHelper.DcomProtocol, ComputerWMIHelper.WsmanProtocol)]

I also think that validation should occur here, since it is removed from BeginProcessing.

In reply to: 332362109 [](ancestors = 332362109)

Refers to: src/Microsoft.PowerShell.Commands.Management/commands/management/Computer.cs:102 in e283582. [](commit_id = e28358202134177049fe78beba58357ff878b888, deletion_comment = False)

        switch (_transportProtocol)

Is the switch statement unnecessary? The transport can only be one value.

Refers to: src/Microsoft.PowerShell.Commands.Management/commands/management/Computer.cs:283 in e283582. [](commit_id = e28358202134177049fe78beba58357ff878b888, deletion_comment = False)

    [ValidateSet(ComputerWMIHelper.DcomProtocol, ComputerWMIHelper.WsmanProtocol)]

The same comments as above; the ValidateSet should be updated and validation inserted to ensure only WsmanProtocol

Refers to: src/Microsoft.PowerShell.Commands.Management/commands/management/Computer.cs:713 in e283582. [](commit_id = e28358202134177049fe78beba58357ff878b888, deletion_comment = False)

I hadn't intended a complete overhaul, but that's what it looks like is needed. I will update accordingly

Added issue this fixes


Update to 0.25.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

The autotick bot did not appear to catch the update on pypi, attempting to trigger an update manually.

@conda-forge-admin, please rerender


Can't connect my Nuki lock

System Health details
System Information

version
core-2023.10.1

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.5

os_name
Linux

os_version
6.1.45

arch
x86_64

timezone
America/Recife

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4355

Installed Version
1.33.0

Stage
running

Available Repositories
1376

Downloaded Repositories
47

AccuWeather

can_reach_server
ok

remaining_requests
42

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 10.5

update_channel
stable

supervisor_version
supervisor-2023.10.0

agent_version
1.5.1

docker_version
23.0.6

disk_total
30.8 GB

disk_used
11.3 GB

healthy
true

supported
true

board
ova

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.6.0), Mosquitto broker (6.3.1), Samba share (10.0.2), Home Assistant Google Drive Backup (0.111.1), Duck DNS (1.15.0), Advanced SSH & Web Terminal (15.0.8), AppDaemon (0.13.5), Node-RED (14.6.1), Zigbee2MQTT (1.33.1-1), Zigbee2MQTT Edge (edge), ESPHome (2023.9.3)

Dashboards

dashboards
1

resources
33

views
20

mode
storage

Recorder

oldest_recorder_run
30 de setembro de 2023 às 17:06

current_recorder_run
9 de outubro de 2023 às 14:04

estimated_db_size
2773.89 MiB

database_engine
mysql

database_version
10.11.5

Sonoff

version
3.5.2 (2ad1cd7)

cloud_online
1 / 2

local_online
1 / 1

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
I tried to mannually pair my nuki 2.0 lock, but I get a error without anything writen, only the OK button.
In the HA log I found this:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:103
First occurred: 14:07:36 (1 occurrences)
Last logged: 14:07:36
Detected integration that attempted to call BleakClient with an address instead of a BLEDevice. Please report issue to the custom integration author for hass_nuki_bt using this method at custom_components/hass_nuki_bt/config_flow.py, line 151: ret = await device.pair()
Reproduction steps

manually pair a nuki lock.
put the MAC address
click "pair lock automatic (recommended)"

Debug logs
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:103
First occurred: 14:07:36 (1 occurrences)
Last logged: 14:07:36

Detected integration that attempted to call BleakClient with an address instead of a BLEDevice. Please report issue to the custom integration author for hass_nuki_bt using this method at custom_components/hass_nuki_bt/config_flow.py, line 151: ret = await device.pair()

Diagnostics dump
No response

Did you try automatic pair?
If HA doesn't automatically recognizes there is a nuki device you can pair, it usually means that HA is not able to connect to that device via BT.
Anyway there is a small bug here in my code that i will fix for next version, but auto pair should still work in current version

It doesn't appear anything automatic....
I already use another custom component that use the BT dongle. Is it a problem?

if it uses the BT dongle directly than it might be a problem. if it uses HA's BT integration that both should be able to work togther.

It's that custom component: https://github.com/custom-components/ble_monitor

I found the problem. I need the HA bluetooth integration to work.
Now it appear automatic, but I still have a problem. I get a popup error without any text.
And the log is:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:103
First occurred: 14:45:52 (1 occurrences)
Last logged: 14:45:52
Detected integration that attempted to call BleakClient with an address instead of a BLEDevice. Please report issue to the custom integration author for hass_nuki_bt using this method at custom_components/hass_nuki_bt/config_flow.py, line 151: ret = await device.pair()

The log you are getting is only a warning. From looking at HA code, it should work even if you see this warning.
can you increase log-level and try it again?

fixed in 0.0.8


Sync eng/common directory with azure-sdk-tools for PR 2686

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2686  See eng/common workflow

/check-enforcer override


.EXE file ?

compiled it

Thank you for the help.
I compiled it in release, so now it works in the cmd line tool.
Is there any real UI?

Le 16 nov. 2018 à 09:22, ScyriusS<EMAIL_ADDRESS>a écrit :
When you compil' the project with visual studio code / you found .exe in
root folder so in CampaignSync folder.
Le jeu. 15 nov. 2018 à 16:13, caeypi<EMAIL_ADDRESS>a écrit :

Hi,
I couldn't find the CampaignSync.exe ?
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cumpstey/campaign-sync/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/Aby4nDRrAwHiMn-oxsr7drkVX9sxUj4vks5uvYSRgaJpZM4Yf_lt
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

No gui, if that's what you mean - it's just a commandline tool. The readme describes how to use it.

alright thx

Hello , no only commande line and coumentation given on github page.
Le ven. 16 nov. 2018 à 13:09, caeypi<EMAIL_ADDRESS>a écrit :

Thank you for the help.
I compiled it in release, so now it works in the cmd line tool.
Is there any real UI?

Le 16 nov. 2018 à 09:22, ScyriusS<EMAIL_ADDRESS>a écrit :
When you compil' the project with visual studio code / you found .exe in
root folder so in CampaignSync folder.
Le jeu. 15 nov. 2018 à 16:13, caeypi<EMAIL_ADDRESS>a écrit
:

Hi,
I couldn't find the CampaignSync.exe ?
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cumpstey/campaign-sync/issues/3, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/Aby4nDRrAwHiMn-oxsr7drkVX9sxUj4vks5uvYSRgaJpZM4Yf_lt

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cumpstey/campaign-sync/issues/3#issuecomment-439374608,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aby4nAZsY-nl3wBCJ2Y5-QE-0fdsMlfcks5uvqsFgaJpZM4Yf_lt
.