Req: Quake Champions suppot

The latest version of Quake Champions just launched with Razer Chroma support built in, it would be great if you could add that to Aurora so that those with Corsair Strafe RGB and similar non Razer products could have lighting effects as well :o)

I've tried just using the Razer Chroma wrapper, and though the game appears to lock the razer .dll files in the same folder as the game exe, aurora doesn't seem to do anything.
Aurora's desktop profiles are working with my keyboard so it's not that.
I've tested the current release version or Aurora and also v0.6.1-dev3 ( tip for anyone reverting from the beta back to the production release, I had to delete %appdata%\Aurora\   or the production build crashed on launch)

Could you post the log file after trying to get it work?

"[ERROR] 09/10/2017 04:59:43: Razer device, Exception! Message:System.Exception: No Chroma SDK available"
Do end users have to install the Razer SDK as well then? I don't recall seeing this mentioned anywhere
Here's the full log:
`========================================
Operation System: Windows 10 Pro
System Architecture: 64 bit
Environment OS Version: Microsoft Windows NT 6.2.9200.0
System Directory: C:\WINDOWS\system32
Processor Count: 8
User DomainName: -------
User Name: Yakumo
SystemPageSize: 4096
Environment Version: 4.0.30319.42000
Is Elevated: True
Aurora Assembly Version: <IP_ADDRESS>
Aurora File Version: <IP_ADDRESS>
09/10/2017 04:58:17: An error occured while trying to load script C:\Program Files\Aurora\Scripts\Devices\example_py_script.py. Exception: System.Exception: Provided script, does not meet all the requirements
at Aurora.Devices.ScriptedDevice.ScriptedDevice..ctor(Object script) in D:\Repositories\Git\Aurora\Project-Aurora\Devices\ScriptedDevice\ScriptedDevice.cs:line 32
at CallSite.Target(Closure , CallSite , Type , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at Aurora.Devices.DeviceManager..ctor() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\DeviceManager.cs:line 57
09/10/2017 04:58:18: An error occured while trying to load script C:\Program Files\Aurora\Scripts\Devices\example_script.cs. Exception: System.Exception: Provided script, does not meet all the requirements
at Aurora.Devices.ScriptedDevice.ScriptedDevice..ctor(Object script) in D:\Repositories\Git\Aurora\Project-Aurora\Devices\ScriptedDevice\ScriptedDevice.cs:line 32
at CallSite.Target(Closure , CallSite , Type , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at Aurora.Devices.DeviceManager..ctor() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\DeviceManager.cs:line 71
[INFO] 09/10/2017 04:58:18: Loading Configuration
[INFO] 09/10/2017 04:58:19: Loading Device Manager
[ERROR] 09/10/2017 04:58:19: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:58:19: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:58:19: Corsair device, Initialized with x64-SDK
[INFO] 09/10/2017 04:58:19: Device, Corsair, was initialized
[INFO] 09/10/2017 04:58:19: No Chroma SDK available
[ERROR] 09/10/2017 04:58:19: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:58:19: Device, Razer, was not initialized
[INFO] 09/10/2017 04:58:19: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:58:19: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:58:19: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:58:19: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:58:19: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:58:19: Device, AtmoOrb, was initialized
[INFO] 09/10/2017 04:58:19: Loading KB Layouts
[INFO] Baseline X = 0
[INFO] Baseline Y = 37
[INFO] 09/10/2017 04:58:19: Input Hooking
[INFO] 09/10/2017 04:58:19: Starting GameEventHandler
[INFO] 09/10/2017 04:58:19: Starting GameStateListener
[INFO] 09/10/2017 04:58:19: Device, Corsair, was shutdown
09/10/2017 04:58:19: Listening for game integration calls...
09/10/2017 04:58:19: Loading WinApp...
09/10/2017 04:58:19: Loaded WinApp
09/10/2017 04:58:19: Loading ResourceDictionaries...
09/10/2017 04:58:19: [AuroraCommandsServerIPC] Pipe created 36610825
09/10/2017 04:58:19: [IPCServer] Pipe created 7995840
[INFO] 09/10/2017 04:58:19: Device, AtmoOrb, was shutdown
09/10/2017 04:58:19: Loaded ResourceDictionaries
09/10/2017 04:58:19: Loading ConfigUI...
[ERROR] 09/10/2017 04:59:22: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:59:22: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:59:22: Corsair device, Initialized with x64-SDK
[INFO] 09/10/2017 04:59:22: Device, Corsair, was initialized
[INFO] 09/10/2017 04:59:22: No Chroma SDK available
[ERROR] 09/10/2017 04:59:22: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:59:22: Device, Razer, was not initialized
[INFO] 09/10/2017 04:59:22: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:59:22: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:59:22: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:59:22: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:59:22: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:59:22: Device, AtmoOrb, was initialized
[INFO] 09/10/2017 04:59:29: Device, Corsair, was shutdown
[INFO] 09/10/2017 04:59:29: Device, AtmoOrb, was shutdown
[ERROR] 09/10/2017 04:59:33: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:59:33: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:59:33: Corsair device, Initialized with x64-SDK
[INFO] 09/10/2017 04:59:33: Device, Corsair, was initialized
[INFO] 09/10/2017 04:59:33: No Chroma SDK available
[ERROR] 09/10/2017 04:59:33: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:59:33: Device, Razer, was not initialized
[INFO] 09/10/2017 04:59:33: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:59:33: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:59:33: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:59:33: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:59:33: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:59:33: Device, AtmoOrb, was initialized
[INFO] 09/10/2017 04:59:33: Retrying Device Initialization
[ERROR] 09/10/2017 04:59:33: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:59:33: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:59:33: No Chroma SDK available
[ERROR] 09/10/2017 04:59:33: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:59:33: Device, Razer, was not initialized
[INFO] 09/10/2017 04:59:33: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:59:33: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:59:33: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:59:33: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:59:33: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:59:38: Retrying Device Initialization
[ERROR] 09/10/2017 04:59:38: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:59:38: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:59:38: No Chroma SDK available
[ERROR] 09/10/2017 04:59:38: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:59:38: Device, Razer, was not initialized
[INFO] 09/10/2017 04:59:38: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:59:38: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:59:38: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:59:38: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:59:38: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:59:43: Retrying Device Initialization
[ERROR] 09/10/2017 04:59:43: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 04:59:43: Device, Logitech, was not initialized
[INFO] 09/10/2017 04:59:43: No Chroma SDK available
[ERROR] 09/10/2017 04:59:43: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 04:59:43: Device, Razer, was not initialized
[INFO] 09/10/2017 04:59:43: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 04:59:43: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 04:59:43: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 04:59:43: Cooler Master device control could not be initialized
[INFO] 09/10/2017 04:59:43: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 04:59:44: Device, Corsair, was shutdown
[INFO] 09/10/2017 04:59:44: Device, AtmoOrb, was shutdown
[ERROR] 09/10/2017 05:00:06: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 09/10/2017 05:00:06: Device, Logitech, was not initialized
[INFO] 09/10/2017 05:00:06: Corsair device, Initialized with x64-SDK
[INFO] 09/10/2017 05:00:06: Device, Corsair, was initialized
[INFO] 09/10/2017 05:00:06: No Chroma SDK available
[ERROR] 09/10/2017 05:00:06: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 54
[INFO] 09/10/2017 05:00:06: Device, Razer, was not initialized
[INFO] 09/10/2017 05:00:06: Could not connect to Clevo WMI Interface
[ERROR] 09/10/2017 05:00:06: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in D:\Repositories\Git\Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 65
[INFO] 09/10/2017 05:00:06: Device, Clevo Keyboard, was not initialized
[ERROR] 09/10/2017 05:00:06: Cooler Master device control could not be initialized
[INFO] 09/10/2017 05:00:06: Device, Cooler Master, was not initialized
[INFO] 09/10/2017 05:00:06: Device, AtmoOrb, was initialized
09/10/2017 05:00:13: [IPCServer] Pipe connection established
09/10/2017 05:03:44: [IPCServer] Pipe connection lost
09/10/2017 05:03:44: [IPCServer] Pipe created 56251872
[INFO] 09/10/2017 05:03:44: Device, Corsair, was shutdown
[INFO] 09/10/2017 05:03:44: Device, AtmoOrb, was shutdown
`

If there's anything further needed please let me know :)

I just tried this game on the latest bleeding-edge build and got a similar result. The only relevant lines were these:
[INFO] 22:58:20: [IPCServer] Pipe connection established
[INFO] 23:01:59: [IPCServer] Pipe connection lost
[INFO] 23:01:59: [IPCServer] Pipe created 38583594
I'd also like to add that the first line appears when i open the game, but the following two appear when i close it. I don't know how relevant this is but I don't really have any good info. The chroma effects are enabled in-game and I know from a friend of mine with a razer keyboard that they indeed do work.
I'm glad to help if more testing is needed.

quake champions appears to work with the updates to the wrapper. please test this and get back to me. https://ci.appveyor.com/project/antonpup/aurora/build/0.6.2b-442

Further changes have been made to the wrapper and now quake works as it's supposed to.

I removed all traces of aurora's install folder,  %appdata%\Aurora and any installed wrapper files, installed Aurora-setup-v0.6.2b-442.exe from your post 10 days ago, made sure iCUE had the SDK enabled.
Check my keyboard is set correcting in the Devices and Wrappers tab.
Installed the Razer wrapper into "Steam\steamapps\common\quakechampions\client\bin\pc"   so the RzChromaSDK64.dll file was in the same folder as quakechampions.exe
Added a profile for QuakeChampions, added a layer of the type "Wrapper Lighting Layer"
Clicking through the other profiles Aurora clearly has control of the keyboard lighting as the lights change and respond if on the desktop profile.
Starting QuakeChampions (with Chroma support enabled in game) the keyboard just goes black and stays that way.
Full log file :
`[INFO] 01:03:20:
Operation System: Windows 10 Pro
System Architecture: 64 bit
Environment OS Version: Microsoft Windows NT 6.2.9200.0
System Directory: C:\WINDOWS\system32
Executing Directory: C:\Program Files\Aurora
Launch Directory: C:\Program Files\Aurora
Processor Count: 8
SystemPageSize: 4096
Environment Version: 4.0.30319.42000
Is Elevated: True
Aurora Assembly Version: <IP_ADDRESS>
Aurora File Version: 0.6.2b-442
[INFO] 01:03:20: Loading Configuration
[INFO] 01:03:20: Loading Plugins
[INFO] 01:03:20: Loading KB Layouts
[INFO] 01:03:20: Loading Input Hooking
[INFO] 01:03:20: Loading Applications
[INFO] 01:03:21: Loading Device Manager
[ERROR] 01:03:21: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 01:03:21: Device, Logitech, was not initialized
[INFO] 01:03:21: Corsair device, Initialized with x64-SDK
[INFO] 01:03:23: Device, Corsair, was initialized
[ERROR] 01:03:23: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 64
[INFO] 01:03:23: Device, Razer, was not initialized
[ERROR] 01:03:23: Roccat device, Exception! Message:System.Exception: No devices connected
at Aurora.Devices.Roccat.RoccatDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Roccat\RoccatDevice.cs:line 213
[INFO] 01:03:23: Device, Roccat, was not initialized
[ERROR] 01:03:24: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 71
[INFO] 01:03:24: Device, Clevo Keyboard, was not initialized
[INFO] 01:03:24: No Cooler Master devices successfully Initialized!
[INFO] 01:03:24: Device, Cooler Master, was not initialized
[INFO] 01:03:24: Device, AtmoOrb, was initialized
[ERROR] 01:03:24: SteelSeries GameSense SDK could not be initialized: System.IO.FileNotFoundException: Core Props file could not be found at "C:\ProgramData/SteelSeries/SteelSeries Engine 3/coreProps.json"
at SteelSeries.GameSenseSDK.GameSenseSDK.init(String sseGameName, String sseGameDisplayname, Byte iconColorID) in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\GameSenseSDK.cs:line 58
at Aurora.Devices.SteelSeries.SteelSeriesDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\SteelSeriesDevice.cs:line 55
[INFO] 01:03:24: Device, SteelSeries, was not initialized
[INFO] 01:03:24: Device, SteelSeriesHID, was not initialized
[INFO] 01:03:24: No Wooting devices successfully Initialized!
[INFO] 01:03:24: Device, Wooting, was not initialized
[INFO] 01:03:24: Starting GameStateListener
[INFO] 01:03:24: Retrying Device Initialization
[ERROR] 01:03:24: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 01:03:24: Device, Logitech, was not initialized
[ERROR] 01:03:24: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 64
[INFO] 01:03:24: Device, Razer, was not initialized
[INFO] 01:03:24: Listening for game integration calls...
[INFO] 01:03:24: Loading ResourceDictionaries...
[ERROR] 01:03:24: Roccat device, Exception! Message:System.Exception: No devices connected
at Aurora.Devices.Roccat.RoccatDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Roccat\RoccatDevice.cs:line 213
[INFO] 01:03:24: Device, Roccat, was not initialized
[ERROR] 01:03:24: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 71
[INFO] 01:03:24: Device, Clevo Keyboard, was not initialized
[INFO] 01:03:24: No Cooler Master devices successfully Initialized!
[INFO] 01:03:24: Device, Cooler Master, was not initialized
[ERROR] 01:03:24: SteelSeries GameSense SDK could not be initialized: System.IO.FileNotFoundException: Core Props file could not be found at "C:\ProgramData/SteelSeries/SteelSeries Engine 3/coreProps.json"
at SteelSeries.GameSenseSDK.GameSenseSDK.init(String sseGameName, String sseGameDisplayname, Byte iconColorID) in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\GameSenseSDK.cs:line 58
at Aurora.Devices.SteelSeries.SteelSeriesDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\SteelSeriesDevice.cs:line 55
[INFO] 01:03:24: Device, SteelSeries, was not initialized
[INFO] 01:03:24: [IPCServer] Pipe created 21647132
[INFO] 01:03:24: [AuroraCommandsServerIPC] Pipe created 6451435
[INFO] 01:03:24: Loaded ResourceDictionaries
[INFO] 01:03:24: Loading ConfigUI...
[INFO] 01:03:24: Device, SteelSeriesHID, was not initialized
[INFO] 01:03:24: No Wooting devices successfully Initialized!
[INFO] 01:03:24: Device, Wooting, was not initialized
[DEBUG] 01:03:24: Trying to get game path for: 570
[DEBUG] 01:03:24: Trying to get game path for: 730
[DEBUG] 01:03:24: Trying to get game path for: 219150
[DEBUG] 01:03:24: Trying to get game path for: 257510
[DEBUG] 01:03:24: Trying to get game path for: 209870
[DEBUG] 01:03:24: Trying to get game path for: 49470
[DEBUG] 01:03:24: Trying to get game path for: 241930
[DEBUG] 01:03:24: Trying to get game path for: 41070
[DEBUG] 01:03:24: Trying to get game path for: 270450
[DEBUG] 01:03:24: Trying to get game path for: 200510
[DEBUG] 01:03:24: Trying to get game path for: 43160
[DEBUG] 01:03:24: Trying to get game path for: 239140
[DEBUG] 01:03:24: Trying to get game path for: 200010
[DEBUG] 01:03:24: Trying to get game path for: 232090
[INFO] 01:03:29: Retrying Device Initialization
[ERROR] 01:03:29: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 01:03:29: Device, Logitech, was not initialized
[ERROR] 01:03:29: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 64
[INFO] 01:03:29: Device, Razer, was not initialized
[ERROR] 01:03:29: Roccat device, Exception! Message:System.Exception: No devices connected
at Aurora.Devices.Roccat.RoccatDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Roccat\RoccatDevice.cs:line 213
[INFO] 01:03:29: Device, Roccat, was not initialized
[ERROR] 01:03:29: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 71
[INFO] 01:03:29: Device, Clevo Keyboard, was not initialized
[INFO] 01:03:29: No Cooler Master devices successfully Initialized!
[INFO] 01:03:29: Device, Cooler Master, was not initialized
[ERROR] 01:03:29: SteelSeries GameSense SDK could not be initialized: System.IO.FileNotFoundException: Core Props file could not be found at "C:\ProgramData/SteelSeries/SteelSeries Engine 3/coreProps.json"
at SteelSeries.GameSenseSDK.GameSenseSDK.init(String sseGameName, String sseGameDisplayname, Byte iconColorID) in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\GameSenseSDK.cs:line 58
at Aurora.Devices.SteelSeries.SteelSeriesDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\SteelSeriesDevice.cs:line 55
[INFO] 01:03:29: Device, SteelSeries, was not initialized
[INFO] 01:03:29: Device, SteelSeriesHID, was not initialized
[INFO] 01:03:29: No Wooting devices successfully Initialized!
[INFO] 01:03:29: Device, Wooting, was not initialized
[INFO] 01:03:34: Retrying Device Initialization
[ERROR] 01:03:34: Logitech LED SDK could not be initialized. (LogiLedSetTargetDevice or LogiLedSaveCurrentLighting failed)
[INFO] 01:03:34: Device, Logitech, was not initialized
[ERROR] 01:03:34: Razer device, Exception! Message:System.Exception: No Chroma SDK available
at Aurora.Devices.Razer.RazerDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Razer\RazerDevice.cs:line 64
[INFO] 01:03:34: Device, Razer, was not initialized
[ERROR] 01:03:34: Roccat device, Exception! Message:System.Exception: No devices connected
at Aurora.Devices.Roccat.RoccatDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Roccat\RoccatDevice.cs:line 213
[INFO] 01:03:34: Device, Roccat, was not initialized
[ERROR] 01:03:34: Clevo device, Exception! Message:System.Exception: Could not connect to Clevo WMI Interface
at Aurora.Devices.Clevo.ClevoDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\Clevo\ClevoDevice.cs:line 71
[INFO] 01:03:34: Device, Clevo Keyboard, was not initialized
[INFO] 01:03:34: No Cooler Master devices successfully Initialized!
[INFO] 01:03:34: Device, Cooler Master, was not initialized
[ERROR] 01:03:34: SteelSeries GameSense SDK could not be initialized: System.IO.FileNotFoundException: Core Props file could not be found at "C:\ProgramData/SteelSeries/SteelSeries Engine 3/coreProps.json"
at SteelSeries.GameSenseSDK.GameSenseSDK.init(String sseGameName, String sseGameDisplayname, Byte iconColorID) in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\GameSenseSDK.cs:line 58
at Aurora.Devices.SteelSeries.SteelSeriesDevice.Initialize() in C:\projects\aurora\Project-Aurora\Project-Aurora\Devices\SteelSeries\SteelSeriesDevice.cs:line 55
[INFO] 01:03:34: Device, SteelSeries, was not initialized
[INFO] 01:03:34: Device, SteelSeriesHID, was not initialized
[INFO] 01:03:34: No Wooting devices successfully Initialized!
[INFO] 01:03:34: Device, Wooting, was not initialized
[INFO] 01:07:12: [IPCServer] Pipe connection established
[INFO] 01:09:26: [IPCServer] Pipe connection lost
[INFO] 01:09:26: [IPCServer] Pipe created 36736776
[INFO] 01:09:48: Device, Corsair, was shutdown
`

Sorry if that wasn't clear. Further commits have been made and quake has now proper support in the UI. Here: https://ci.appveyor.com/project/antonpup/aurora/build/0.6.2b-451/artifacts . Please get back to me if it works

Aurora-setup-v0.6.2b-451.exe works !! thank you so much =)

Works for me too! Cheers everyone involved!!


Update xfails for swift-testing

Pull Request Description

Update the xfails file for swift-testing.

Filed:

https://github.com/apple/swift/issues/69278
https://github.com/apple/swift/issues/69279

@swift-ci test


#156 - Multi-release jar with logging via System.Logger and JUL

This isn't fully satisfactory yet.

Not going to merge this, instead just going to use System.Logger with a bump to Java 11.


Win+CapsLock enables/disables Switchy

I found that in games, when Switchy is on, I can't use CapsLock as my in-game button. Therefore I have added Win+Caps Lock that enables/disables Switchy, so I don't have to kill it through Task Manager every time I enter game that has Caps Lock binding in it.

Hey, sorry, I didn't see your pull request. I added the ability to enable/disable Switchy with Alt+CapsLock. Win+CapsLock causes some weird bugs for me.


Is Rbatch excute operation atomic?

I have keys in array of ByteArray (ByteArray for each key) and I am wondering if redisson enable returning value/timeout/null(miss) for different key with batch execute. Would batch support this? Or batch.execute() is just an atomic operation and will fail for all batch once a key is missed?
eg:
val batch = redissonClient.createBatch();
keys.foreach(key -> batch.getBucket(key).async.get();
val vals = batch.excute().getResponse()

Would batch support this? Or batch.execute() is just an atomic operation and will fail for all batch once a key is missed?

RBatch execution depends on BatchOptions.executionMode setting. If any batched command executes with error it won't cancel execution of other succeeded commands.


evaluate.py

Hi nice work.
Coud u tell me pls. Whats wrong with this, after run python evaluate.py I have error.
python evaluate.py  --data_path /Users/kgkozlov/Downloads/img_4.png --dataset matterport3d --load_weights_dir /Users/UniFuse-Unidirectional-Fusion/PretrainedModels/
File "/UniFuse-Unidirectional-Fusion/UniFuse/datasets/matterport3d.py", line 83, in __getitem__
    rgb = cv2.cvtColor(rgb, cv2.COLOR_BGR2RGB)
cv2.error: OpenCV(4.5.3) /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-req-build-z9mn802i/opencv/modules/imgproc/src/color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cvtColor'

fpath = os.path.join(os.path.dirname(__file__), "datasets", "{}_{}.txt")

But you add txt file with RGB and DEPTH, But shouldn't we just add one RGB image ?

The  evaluate.py is used for performing evaluation on the 4 datasets, not for a single image. If you want to test on an image, you have to modify the code.


Add support for remembering prior searches

This makes the up and down keys useful.

That's great, thanks!


Improve the maxLength validation message

Hi @pipermerriam I found something that seems an error
amount:
    type: string
    maxLength: 2

But when I send an amount of 5 characters, I got the validation message:
flex.exceptions.ValidationError: 'response':
    - 'body':
        - 'schema':
            - '$ref':
                - 'amount':
                    - 'maxLength':
                        - 'value must be no greater than 5 characters in length.'

The message should be something like value must be no greater than 2 characters in length
I am using the last version of flex.

@nicolastrres you should be able to get 4.2.1 of pypi


RuntimeException: Unable to start activity --> Binary XML file line #11: Error inflating class im.delight.android.webview.AdvancedWebView

Hi..
I have an xml using AdvancedWebView but when ever I start activity it crashes with the above exception. Here is complete error:
Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.yaramobile.digitoon/com.yaramobile.digitoon.presentation.player.PlayerActivity}: android.view.InflateException: Binary XML file line #11: Binary XML file line #11: Error inflating class im.delight.android.webview.AdvancedWebView
at android.app.ActivityThread.performLaunchActivity + 2666(ActivityThread.java:2666)
at android.app.ActivityThread.handleLaunchActivity + 2727(ActivityThread.java:2727)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage + 1478(ActivityThread.java:1478)
at android.os.Handler.dispatchMessage + 102(Handler.java:102)
at android.os.Looper.loop + 154(Looper.java:154)
at android.app.ActivityThread.main + 6121(ActivityThread.java:6121)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 889(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main + 779(ZygoteInit.java:779)

Caused by android.view.InflateException: Binary XML file line #11: Binary XML file line #11: Error inflating class im.delight.android.webview.AdvancedWebView

Caused by android.view.InflateException: Binary XML file line #11: Error inflating class im.delight.android.webview.AdvancedWebView ```

Are you sure you’ve actually added the dependency?
https://github.com/delight-im/Android-AdvancedWebView#installation

I am also getting the same issue in some of my device.

I think is related https://stackoverflow.com/questions/46810118/exception-on-new-webview-on-lollipop-5-1-devices

Hi, i have same issue, but I noticed that the crash is mostly on a device with Android 5.
Any solution?

I'm getting this when running UI tests on an Android 5.0.2 emulator.
android.view.InflateException: Binary XML file line #23: Error inflating class im.delight.android.webview.AdvancedWebView 	at android.view.LayoutInflater.createView(LayoutInflater.java:633)

solved by this comment 30#

https://issuetracker.google.com/issues/141132133


Merging Tutorials posted at Develop to Master

Merging tutorial folders with currently posted GEDI and HLS tutorials to master.

@sumantjha now I recall this PR, I was suggesting @spa0002 should be the reviewer.
Review:

[ ] Content renders correctly on https://docs.maap-project.org/en/develop/
[ ] Verify content applies to the version of MAAP that users have access to.

[ ] GEDI L2B lacks subheadings (minor) should not be a blocker.
[ ] HLS tutorial is lacking screenshots/visualizations

Do we consider these blockers, or should we simply open tickets to address these, but go ahead with the PR?

I can address these before we review it again.

When running HLS_search.ipynb and Search_GEDI.ipynb on ade.ops.maap-project.org, I receive the following error:

When running GEDI_L4A_Example.ipynb on ade.ops.maap-project.org, there is a similar issue where geopandas is not found.
I receive the following error for the first code block in the 'Generate contour lines" section:

When running HLS_search.ipynb and Search_GEDI.ipynb on ade.ops.maap-project.org, I receive the following error:

@spa0002 You need to install geopandas in your environment.

I think we need to discuss the approach at the next Architecture meeting (pip vs conda, code or just a list, etc...). If the requirements are stated at the top of the notebook that should not block this PR. TODO: enhancement - resolve how to best to inform and guide users to installing the correct requirements.

@sumantjha @anisbhsl in a meeting we agreed to list he python libraries at the top of each notebook, in a block that can be copied/pasted for use with conda or pip. Is someone working on that change?

I will do it. It is a small change.

[ ]  GEDI L2B lacks subheadings (minor) should not be a blocker.
[x]  HLS tutorial is lacking screenshots/visualizations

Do we consider these blockers, or should we simply open tickets to address these, but go ahead with the PR?

https://docs.maap-project.org/en/latest/tutorials/HLS/HLS_search.html

The code is all pythonic and is not interacting with any external component. So, what screenshots are we looking for exactly in the above?
That said, I do not think it is a blocker but an enhancement request which can be done in its own ticket.


Change similarity metric

If you take a look at the example provided here https://npm.io/package/string-similarity, similar strings would be 'sealed' and 'healed'. I don't think this is the kind of similarity that @JessieWang0706 had in mind. I think a conversation about what makes 2 items similar is needed and it seems like https://www.tensorflow.org/hub/tutorials/semantic_similarity_with_tf_hub_universal_encoder would do a better job at calculating this similarity. For now I am approving so that we can get some kind of similarity metric in since all we need to do in a future PR is replace the string similarity calculating with this encoder's calculation.
Originally by @chalo2000 in #53

Is the issue closed now that similar item algo is out?

yes this is the similarity metric I wanted. i am satisfied


multi-gpu horovod

With multi-GPU training by horovod，the value of examples/sec  is for one gpus or for allgpus?? I found that the value of multi-gpu is lower than one-gpu. Thanks

@tianuna , where did you see that?

@tianuna , where did you see that?
This is the results of 4 gpus

@tianuna , where did you see that?

This is one gpu's results.

@tianuna , where did you see that?

This is one gpu's results.

This is 4-gpu's results with horovod. I think the trained examples per second should be 44*4=176. But I can not find the code which defines this.


Reflex and Trendflex Question

I was comparing the implementations of Reflex and Trendflex in pandas-ta to their implementations on https://www.prorealcode.com/prorealtime-indicators/reflex-and-trendflex-indicators-john-f-ehlers/. There appears to have been an extra 0.5 * added in front of close[i - 1] here, https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/trend/trendflex.py#L67. Also, the original implementation of both Reflex and Trendflex used 10 for smooth, instead of 20. Did you find 20 to provide better results?

I would have to check on that again. On the first look it is simply a multiplication instead of a division by 2, but there are other deviations in the super smoother part. I will have a look at that, hopefully some time soon.

Sorry for the delayed reply, I thought that at first as well. However, line 17 here, https://www.prorealcode.com/prorealtime-indicators/reflex-and-trendflex-indicators-john-f-ehlers/, is the same for Reflex and Trendflex. However, https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/cycles/reflex.py#L66 and https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/trend/trendflex.py#L67 are different, with the latter, https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/trend/trendflex.py#L67, adding an extra 0.5 in front of close[i - 1]. Also, the smooth parameter, https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/cycles/reflex.py#L47 and https://github.com/twopirllc/pandas-ta/blob/development/pandas_ta/trend/trendflex.py#L47, default to 20 instead of the standard 10. Did you find 20 to provide better results?

 I'll take a look as soon as I can. Apologies in advance.
KJ

@twopirllc, if I'm wrong let me know. If not, let me know if you want me to put in a pull request or if @rengel8 should do it. Also, no need to apologize. Your library is amazing. Thanks for all the time you've put into making it what it is!

I once made a comparison based on output data coming from Trading View I think (SPY_D_REFLEX_TRENDFLEX.csv). Maybe we should do that again or with output from prorealcode (default parameters) to check where we are?
@CMobley7 Better results is very dependend on the situation (market etc). I would prefer to have a state that is close to the originating code and which is working like expected.

@rengel8 , it appears that the extra 0.5 in front of close[i - 1] was adding in the following commit, https://github.com/twopirllc/pandas-ta/commit/36ab37a1eca449478a45f67a191499cca494484a#diff-0c0c06628224d80ef2e133c513e0d14c7aa0b3d63797e3509cdf11b3022a8a92. If you want to keep Trendflex as close to the original code as possible, I also suggest that we remove the extra 0.5 and change the smooth parameter to 10 instead of 20. In regard to trading view, I've never used it. Is it free? If you give me a date range and a security name, I can upload the Trendflex numbers for both the current implementation and what I'm suggesting for you to review.

@CMobley7,
Sorry, needed to finish up the lingering PRs. I will look into these now.
KJ

Hello @CMobley7,
This should be fixed if you want to test it out. Let me know otherwise.
$ pip install -U git+https://github.com/twopirllc/pandas-ta
Thanks for the catch!
KJ

Hi @CMobley7,
Oops! Please try the development branch instead. Speed improvements, docs, typing, et al.
$ pip install -U git+https://github.com/twopirllc/pandas-ta.git@development

Thanks,
KJ


Menu doesn't work with UBlock

The menu seems to get blocked by UBlock - any fixes for this?

What is UBlock?

UBlock is an ad blocker - https://www.ublock.org/

If UBlock blocks content it shouldn't block, I'd contact UBlock.

Works for me, are you using this one?
https://github.com/chrisaljoudi/uBlock


Update lab1.md for test commands in makefile

Follow . /tinykv/makefile to adjust the make parameters

maybe you can modify the title "Lab2" to "Lab1" together.


ninja: Have the bundle resources be a dependency of their target

Bundle resources were added to the "all" target which made it really hard to have OSX bundle resources copied when generating a specific target.
This change adds a dependency on the resources to the target using them.

My guess is that it's too late for 3.6.0 (hence I'm sending to next).
I'm not sure if that's the right way to fix it but it works for me!
Related bug reported 4 years ago: https://cmake.org/Bug/view.php?id=13816
Note that the Xcode and Make generators copy the resources when building the target directly and didn't have that issue (they have other issues though, namely not being Ninja).

@bradking

And after reading the CONTRIBUTING.rst, I realize I should have pushed to master. Will make a new PR then!


createLocation is not present in your mudule any more

Hey man, I install latest version of you module, but, createLocation is not present any more. I try any ways, like import { createLocation } from 'history', or call from history.createLocation and nothing. Can U help me? Thank you.

The top-level one has been deprecated for a long time now. It's on history objects now.

you mean this project? https://www.npmjs.com/package/object-history or another thing?

https://github.com/mjackson/history/blob/master/modules/createHistory.js#L161

Thank you my friend =}

@darkfrontcode @chentsulin @taion How do we get createLocation for environments with no DOM? It's not present in the top level anymore.
It's also still listed in https://github.com/ReactJSTraining/history/blob/master/docs/Location.md#programmatic-creation

That's a docs bug then. Creating a location without a history object (which need not require a DOM, e.g. with memory history) has been deprecated for a while, because location creation depends on history enhancers/&c.

@taion thanks -- good to know!

For others that were wondering how to do this on server side:
const location = createLocation(req.url);
match({ routes, location }, (error, redirectLocation, renderProps) => {

becomes:
match({ routes, location: req.url }, (error, redirectLocation, renderProps) => {
Credits to @calvinl for referencing this issue in his commit.


R implementation is missing

R is heavily used in biostatistics and big data analysis.  An R implementation would enable access to a huge range of statistical tools, and also to a substantial number of people who have expertise in R but not other programming languages.
The implementation strategy should almost certainly be based around the R-Scala interface package rscala.  The way we should use it is documented at https://darrenjw.wordpress.com/2015/08/15/calling-scala-code-from-r-using-rscala/

That sounds great! Especially with a good Scala implementation now!

Resolved by https://github.com/openworm/tracker-commons/pull/109
Not very well, but kinda.


Travis: Check for gofmt issues.

The default test script is go test -v ./... (assuming a Makefile is not present) according to Travis docs at https://docs.travis-ci.com/user/languages/go/#Default-Test-Script.
Add an additional gofmt check to help catch formatting issues in PRs. This is motivated by a previous occurrence at https://github.com/google/go-cmp/pull/9#discussion_r127624347.
Also swap the order of Go versions 1.x and 1.6. 1.x is higher priority, so it makes more sense to run it first and report issues right away. 1.6 is lower priority, so it's better to prioritize it lower.
Use 2 space indent in the .yml file, which is consistent with the formatting in Travis documentation and examples.
/cc @dsnet

Thanks for the adjustments.


HNav Keyboarding & Gamepad updates + visual state fix

Part of Issue #2175
Description
This PR fixes several things:

Arrow key keyboard navigation for hierarchical navingation
Gamepad invocation for exapanding/collapsing (this is just removal of keyup handling which is no longer required)
When a NVI was being set to expanded on load, visual state was not being updated correctly

Note: Required Tab focus behavior still needs to be updated which is being tracked by the same issue linked above
Motivation and Context
Hierarchical NavigationView needs to support multi-level navigation via keyboard and gamepad
How Has This Been Tested?
Visually
(interaction test updates in progress, current state of PR will break some focus tests)

winrt::ItemsRepeater::GettingFocus_revoker m_leftNavRepeaterGettingFocusRevoker{};

can remove this since we are not using it anymore ?

Refers to: dev/NavigationView/NavigationView.h:395 in f6468e1. [](commit_id = f6468e18b691aad37c31131614d76bde14bbb20f, deletion_comment = False)

/azp run

@ojhad can you take a look at the test failures ?

/azp run

/azp run

/azp run


adding a plugin by default prettier-plugin-tailwindcss (cra, nextjs, vite)

https://github.com/tailwindlabs/prettier-plugin-tailwindcss
Please add this default plugin to as a dev-dependency. (cra, nextjs, vite)
Or as a suggestion - to add such an option.
How have you done to preserve CSS.   option('-p, --preserve', 'Preserve existing CSS') or whatever :)
Because a lot of people have to do it every time anyway.
Thanks.

@SergeITinc Released v.0.3.1

@tzsk  Thank you so much!


Multiple Toastr messages are not showing

I am calling toastr via my vb.net code in my code behind. I set up a vb.net method that I call. For some reason, it will not show multiple ones?
What am I doing wrong?
          MiscMethods.ShowToastr(radScriptManager, Page, "Information loaded!", "", ToastrTypeOption.Information)

       MiscMethods.ShowToastr(radScriptManager, Page, "Information loaded!", "", ToastrTypeOption.Information)

   Public Shared Sub ShowToastr(ByVal scriptManager As ScriptManager, ByVal page As Page, ByVal message As String, ByVal title As String, ByVal typeOption As ToastrTypeOption)
        Dim serializer As JsonSerializer = New JsonSerializer()
        Dim theToastrOptionInfo As ToastrOptionsDto = New ToastrOptionsDto()
        Dim json As String = JsonConvert.SerializeObject(theToastrOptionInfo)
        Dim scriptText As String = String.Format("toastr.{0}('{1}', '{2}', {3});", GetDefaultValueFromEnumValue(typeOption).ToLower(), message, title, json)
        ScriptManager.RegisterStartupScript(page, page.GetType(), "toastr_message", scriptText, True)
    End Sub

I think I have it fixed now. I set the key to DateTime.Now.Millisecond and it is working now.
    Public Shared Sub ShowToastr(ByVal page As Page, ByVal message As String, ByVal title As String, ByVal typeOption As ToastrTypeOption)
        Dim serializer As JsonSerializer = New JsonSerializer()
        Dim theToastrOptionInfo As ToastrOptionsDto = New ToastrOptionsDto()
        Dim json As String = JsonConvert.SerializeObject(theToastrOptionInfo)
        Dim scriptText As String = String.Format("toastr['{0}']('{1}', '{2}', {3});", GetDefaultValueFromEnumValue(typeOption).ToLower(), message, title, json)
        ScriptManager.RegisterStartupScript(page, page.GetType(), DateTime.Now.Millisecond.ToString(), scriptText, True)
    End Sub


Create model of views by Scaffold-DbContext

Hello everyone.
Is it possible to create model of views via Scaffold-DbContext?

@netbidev - At present there is no way.
There is some work-around posted by a user here https://github.com/aspnet/EntityFrameworkCore/issues/9854#issue-258984255
Duplicate of #1679

This seems to be an issue again with Core 3.1.


How to use environment vars in config files

I would like to get configuration options in the JSON files from environment varibles. Is there any way to do it?
TIA.

currently no, but please feel free to send a PR!


kubectl reference docs for 1.11

This is the doc generated using brodocs as we did in the past.
Will propose another testing PR for generated kubectl ref docs like we are doing for kube-components.

/assign @mistyhacks
/assign @steveperry-53

Holding for approval by @mistyhacks.
/hold
/lgtm

It's weird to have a landing page that is only a link to the API ref -- seems like we could just have the link in the TOC go straight there. But that's for another time.
Thanks for generating this.
/hold cancel
/approve


Unable to set focus back to the Calculator after minimizing using the title bar menu

Describe the Bug:
Sometimes we are unable to set focus back to the Calculator after minimizing using the title bar menu. This issue occurs when we are working in the Graphing mode. After opening the app again, we cannot press even a single button.
Steps to Reproduce:
This bug is intermittent. You may have a hard time reproducing this bug; I resetted this app several times in order to record a handful of occurences.
If someone is able to reproduce this, please leave a comment telling your observations so that the maintainers find it easier to debug.

Open the Calculator in Graphing mode.
In the expression box, type an incomplete expression as shown below:

x <

OR
x =

OR
x /

OR
x |

Right-click the title bar and select 'Minimize'.

Restore the app from the taskbar.
You will notice that you are unable to click any button or text field.

Expected Behaviour:
We should have been able to set focus to any button or text field.
Device and Application Info:
OS Build: 10.0.19041.264
Architecture: x64
Application Version: 10.2005.23.0
Region: India (en-US)
Dev-Version Installed: No
Requested Assignment:
I'm just reporting this problem. I don't want to fix it.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

The most reliable way to reproduce this is using:
x /

@Rahul-Dixit I am not able to reproduce this issue. You mention it is intermittent -- is it common (e.g., 1 in 3) or rare (e.g., 1 in 20)?

@grochocki This is indeed rare

@grochocki Here is the GIF showing the issue:

Note:

The bug seems easier to reproduce when the Calculator window is not in maximized mode. However it is possible to reproduce this issue in maximized mode.
In the later half of this GIF, I am clicking various areas of the screen. See that I am getting no response. The calculator is unable to set focus to those buttons when they are clicked.
If you maximize the window after the calculator has freezed, VisualStates no longer work.

You may not be able to reproduce this in your first attempt. Please close the window and try again!

I was still not able to reproduce this issue, but your GIF clearly shows the issue you describe, so approving.
For me, it always processes the first equation as an error and shows the second entry point:

@grochocki Yes, this happens in my case also. But in a few instances, this issue occurs.
I want to give you a measure of its rarity. So I am trying to reproduce this issue afresh. For this I am launching Windows Calculator inside Windows Sandbox.
First try: The expression is highlighted in red, which means I failed. So I am closing the Calculator window and then opening it again for the second try.
Second Try: Failed. Repeating the above steps.
Third try: Failed
Fourth try: Successfully reproduced the issue this time. The expression isn't highlighted in red and I'm unable to set focus to anything.
You may also succeed in a couple of tries. In fact, I discovered this issue when I minimized the Graphing calculator to change the music track.


Why the performance on CIFAR-10 is very low

Hello Xinyi, Many thanks for your great work.
I have a question regarding the model performance on the CIFAR-10 dataset.
Why the performance is so low for federated learning even the data samples are uniformly distributed? In centralized training, the model can easily achieve over 90% accuracy.
In the reported table 1, the Standalone and FedAvg are only 46% and 48%.
Looking forward to your reply. Thanks~

Hi @Bayesanctury, thanks for your interest in our work.
The performance discrepancy is due to a reduced data setting. In particular, in this repository if you look at main.py lines 89-92, you can see that each agent on average uses 2000 data points from the CIFAR-10 dataset which contains 50000 (training) + 10000 (test). So for 10 agents, the training only uses 20000 (40%) of the entire training dataset in CIFAR-10 and hence the lower accuracy. With this, I would like to point out that the purpose of this framework is not to achieve the absolute highest predictive performance possible but to provide a fair collaborative mechanism, which is why a reduced data setting is acceptable and also since it is less computationally costly.

Many thanks for your kind reply.
I followed your readme guideline and ran the experiments on cifar-10. I found the results are mismatched with what you report in Table.1. Could you please explain this?
Here is the last line result from the valid.csv
0.016409667	0.4111	0.016408276	0.41139999	0.01640928	0.411199987	0.016411796	0.411300004	0.01641012	0.411199987	0.016408097	0.4111	0.016409835	0.411000013	0.016422883	0.410899997	0.016409773	0.411300004	0.016408417	0.411300004	0.01640621	0.411000013
The average accuracy is 41.16, which is quite lower than 61 reported in the table.
 Thanks for your great work again.
Could you please help identify the reasons for the low performance? I use your code without any revisions.
Besides, I tried to increase the samples to 50000, but the performance is also lower (got 55) than your reported 61.

Hi there,
[To increase the average accuracy]: you can try increase the value of the degree of altruism, namely $\beta$. In the paper, the highest average accuracy is achieved with generally higher values of $\beta$. For instance, if you take a look at Table 1 in our paper, you will see that the accuracies (around 60) achieved for CIFAR-10 is when $\beta \in[1,2]$ where in your experiments $\beta=0.5$.
[As an explanation]: intuitively, as the name degree of altruism suggests, $\beta$ controls how altruistic the agents are. Specifically, the more altruistic they are, the more they are willing to allow the agents with lower contributions to receive better gradient rewards (thereby arriving at higher final accuracies, which in turn leads to higher average accuracies). For technical details, you can refer to our paper the discussion on Gradient Download Step on page 5 and for empirical results, you can refer to Table 1 and Section 4.2.

Many thanks for your kind explanations!
Sorry for not reporting all the results, actually, there is a $\beta$ loop ([0.5, 1, 1.2, 1.5, 2, 1e7]) in your code logic. I checked all the results with different $\beta$ values. Since the data distribution is UNI, each client performs similarly, so I listed the average results.

$\beta=0.5$: 41.16
$\beta=1.0$: 40.56
$\beta=1.5$: 41.38
$\beta=2.0$: 40.37
$\beta=2.0$: 40.37

The experiment settings and environments are exactly the same as the one in my last reply. Only the $\beta$ value changed. It seems $\beta$ does not change the final accuracy a lot. Have you validated that the results are reproducible with the current code version?

First of all, many thanks for the very thorough implementation and great research contribution!
I want to use your idea in my research project and could also not reproduce your results with the current settings. I get huge differences, especially in the fairness of e.g. the power law configuration. Are there any updates regarding this issue?


Add Promo image for Friendlyrb in the navbar.

This PR adds:

Promo image to assets/communities folder.
Adds a link to the existing nabvar with the image.
CSS to hide it on smaller screens.

The change looks like this locally. Please let me know if anything needs updating. Thanks!
https://user-images.githubusercontent.com/29284404/226300954-434e3122-e154-44a5-82dd-d4da7979b266.mov

Good to merge @lucianghinda!

@pratiktamang please send me an email at<EMAIL_ADDRESS>


(GH-15) Implement prm set|get backend

This PR is made up of multiple commits that:

Implement the prm set backend command
Fixes an issue with the .prm.yml not being instantiated by Viper (#30)
Generates sensible default values for the Puppet Runtime and Backend, if not set

The prm get commands will need more thorough test coverage, which has been ticketed: #28
Resolves: #15
Resolves: #30

I'm seeing issues with the cli not creating the config file:

Yikes...OK, I'll look in to that, cheers @da-ar . Good thing I'm working on #28 soon

Thanks for the catch @da-ar - needed to create the .config dir, if it doesn't exist already, but given my local system already had this, I didn't catch it.
Again, highlighting the need to get these acceptance tests running, sooner rather than later.
Should be fixed now 🤞


Remove knn install script

Signed-off-by: John Mazanec<EMAIL_ADDRESS>Description
Currently, the k-NN install script copies the library into the the plugins folder. With https://github.com/opensearch-project/k-NN/pull/163 and https://github.com/opensearch-project/k-NN/pull/164, I added this step to the build phase. So, there is no longer any reason to have the install script here. It can fall back to default.
Issues Resolved
#824
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #836 (49deb31) into main (e35513e) will decrease coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #836      +/-   ##
==========================================
- Coverage   91.55%   91.32%   -0.23%
==========================================
  Files          81       81
  Lines        2249     2249
==========================================
- Hits         2059     2054       -5
- Misses        190      195       +5

Impacted Files
Coverage Δ

src/system/temporary_directory.py
82.75% <0.00%> (-13.80%)
:arrow_down:

src/system/os.py
92.30% <0.00%> (-7.70%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix compilation error with Gettext v1.4

Fix issue report in #425. There are still some errors regarding to "translation is missing plural form 2" in the background, but the compilation is now passing through.

I fixed this under a separate commit


[Mobile] UI Updates on Phase 2 Answer (S.1.8)

Issue:
UI updates to more closely match Figma
Resolution:
Update relevant screen per comments on https://www.figma.com/file/PadzU8GqyhFLCjIt7rQkpE/RightOn-Apps?node-id=11957%3A373842&t=SGeD0ipYgjvbSbpc-0

Comments in figma above have been updated.


Implement From<AsRef> for godot strings.

This let one write:
let foo: GodotString = "foo".into();

Fixes #115.


Notification about approved/declined proposed place

As a registered user I want to receive email notifications when my proposed place(s) is approved or declined.
Acceptance Criteria:

Provided a proposed place was approved by admin, system shall send an email notification to the user who proposed the place with the following text:
"Your proposed place "[XXX]" has been approved. You can now view it in GreenCity."
where [XXX] is the name of proposed place.

Provided a proposed place was declined by admin, system shall send an email notification to the user who proposed the place with the following text:
"Your proposed place "[XXX]" has been declined."
where [XXX] is the name of proposed place.

Assumptions and Constraints:
out of scope of this story - add ability for admin to leave comments when declining a proposed place, so that user can understand why his place was declined - create a story for this
TBD:

Not relevant.


Enable schema in client's parameters

It creates tables by default in 'vecs' schema. It'd be great if users had flexibility to choose another schema when creating a client.Thanks

would be interested in this feature as well! happy to put in a PR if you are not planning on it @legaltextai

i am probably at great risk to sound too stupid, but what is 'PR'?

A PR is a pull request. It's a part of the GitHub workflow for contributing to a project. I was asking if you'd like to contribute the change that you're requesting

opened a PR here https://github.com/supabase/vecs/pull/63 would appreciate a review! :)
@olirice

Thank you so much @majamil16 !


Add "Implemented date"

It would be very helpful to have some mention in this (and all) documentation of when (in which version) the feature was added to Power BI.

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

ID: c379d7f1-f977-7906-c4ba-6f58ab47d785
Version Independent ID: 088a4f2c-e571-1282-b265-9b90d4995505
Content: Using buttons in Power BI - Power BI
Content Source: powerbi-docs/desktop-buttons.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @nicheplayer. This issue has been assigned to the doc author for review.

Thanks for your comment. We always recommend users run the most recent version of Power BI Desktop. Meanwhile, you can look through the latest updates article (and its friend, latest updates archive) to see about finding when a feature was released.

Thanks for your comment. We always recommend users run the most recent version of Power BI Desktop. Meanwhile, you can look through the latest updates article (and its friend, latest updates archive) to see about finding when a feature was released.

Thanks for your reply. I've been told by my on-prem server admin that I need to be running the version of desktop that coincides with our on-prem server version; perhaps this isn't actually the case? I appreciate you taking the time to reply. Thanks again.


Remove top margin from headings that are the first child of `.BlockText

Now that headings can be added in rich text, we're getting a double margin when they are the first element within .BlockText.
We need to remove the top margin of all headings that fit this use-case.

I think I added that top margin intentionally? I thought it was good back when we first added the ability to use headings in rich text, so I went back to look at my PRs. Take a look at #327.
Did some new margin get added elsewhere, perhaps?

I think I added that top margin intentionally? I thought it was good back when we first added the ability to use headings in rich text, so I went back to look at my PRs. Take a look at https://github.com/nasa-jpl/explorer-1/pull/327.

Yeah, it makes sense to add margins to headings within BlockText, but the issue is the margin on headings when they're the first child. You can see it happening here: https://www.jpl.nasa.gov/preview?content_type=information_pages.contentpage&token=id=131060:1swQ5C:19cXLl06EIeg3G75OaPz8vVFULWyQMDhECerNi-G5yw&path=/blended-worlds

Yeah, I just want to believe I would have thought to account for that before 😆 But very possible I did not.

Yeah, I just want to believe I would have thought to account for that before 😆 But very possible I did not.

Maybe the use-case at the time was predominantly wanting to add headings without stopping the flow of BlockText, and BlockHeading was always added first, separately?

In code review https://github.com/nasa-jpl/explorer-1/pull/649


Make executables to strictly contain .flatimage extension

This makes it clearer to the user in which app-format is the application he downloaded.
Else, there can be confusion when users think that it's the classic static binary or something.
If the executable doesn't contain .flatimage extension, warn the user in the logs.
Idk if .flatimage or .FlatImage naming is preferred, I find both good.
I maybe lean towards .flatimage more.

Thanks for the suggestion @fiftydinar! I'll consider adding something like this on the next updates (with an option to silence it the the user wants to). Currently the file type is determined by xdg metadata. In the file manager you should see something like:

@ruanformigoni Yeah, I see now in Nautilus file properties that it says "FlatImage Application" even when extension is removed.
However, Nautilus doesn't have app type column when using list view, so you have to go to properties to know what is it.
Just a nitpick, not a big deal.
I wouldn't add this option if the user can just disable it tbh.
I suggested this to improve user awareness, but I use grid view in Nautilus, so I didn't notice that you can see this info easily in list view (in Dolphin at least).
So I guess I will close this issue as not planned.


Refine error handling

This PR introduces a few changes to how we handle errors to better support the recent JS API changes from #14. I want to do some clean-up before publishing this package to npm.
We've got a few CLI-specific features that needed to find their way over to the JS API. Namely, we should be validating that the config is in the correct format when the proxy is created, rather than throwing an error on requests.
This PR moves config.js, which previously parsed environment variables, to a parse-env.js file. I think keeping this separate from the CLI makes sense, since we can test it more easily. Now, config.js is a function to validate the config and get default settings, regardless of how the handler is created.
Changes

[x] Split config.js into parse-env.js and config.js
[x] Validate that airtableApiKey and airtableBaseId exist in config
[x] Validate that allowedMethods is an array in config
[x] Catch all uncaught errors for CLI

Unrelated Changes

[x] Don't create a new proxy for every request
[x] Add clickable URL for CLI

@rosszurowski code changes looked good. I fixed three bugs that I noticed when I pulled this down to actually check functionality:

The dotenv package didn't work right after I moved the index file into the bin directory. That's my bad.
The package.json dev script also needed to be updated to use bin/index.js instead of the root index file.
The API key wasn't getting added as a header, so I updated the variable to make that happen.

Hope it's okay that I put these into the same PR. I figure since it's just the two of us we can be a little loose with our git flow, but if not, I can roll those back and make a separate PR.

Thanks for that fix!
The changes look good, but I just realized we still have dotenv as a dependency. It looks like it was part of the initial commit for this library, but I can't remember why at this point.
For now, I simply moved from the dotenv.config() line to the preloading approach suggested in their docs and moved the dependency to devDependencies. This keeps it out of the production code, which wouldn't even have a .env file to reference. Let me know if you see any issues with this!

Nope, that makes sense. I didn't think about it, but you're right, it's definitely better not to include it in prod.


Implement support for multi-arg functions & implement nroot/log

:warning: Note: this is based on #51 and thus a draft for now.
The motivation behind this change is to implement / change the following
functions:

nroot(x,y) returns the y-th root of x.
log(x,y) returns the logarithm of x for the base y.
log10(x) returns the logarithm of x for the base 10. This is a
breaking change as this is what log(x) was doing previously.

Internally, the following has changed:

Each relation of a Token::Function now has the signature
fn(Vec<f64>) -> f64 where Vec<f64> represents a list of arguments
from the REPL. Via the macros arity_{1,2}! it's still possible to
define functions with n arguments:
arity_2!(|x, y| x+y)

evaluates to a function which takes a Vec<f64> and evaluates x+y
with x being vec.get(0).unwrap() and vec.get(1).unwrap(). The
data-structure ensures previously that the size of the vector matches
the number of required arguments.

The parser now evaluates expressions starting from a closing bracket
back to the next left bracket (as before) or the next comma and
ensures that the latter case can only happen inside a function call.

Hi, sorry for the late reply.
Are you still looking into this?

Yeah, but it may take a while, kinda busy these days.

@Ma27 No worry, I did a version here in https://github.com/nerdypepper/eva/pull/56, just left that lexer part which I haven't figure out yet.

Fixed by #56, I didn't wait for reviewers but I guess should be good.


Daylight savings change issue?

Daylight savings changed today and I noticed a weird timestamp issue in a feed as per

This feed has been running for a while and the 23:00 date change issue has not been seen before.
Note the attributes for the first errant entry are

Will update tomorrow in case this is not a daylight savings change day issue (i.e the date doesn't jump ahead 24 hours for the last hour of the day)

The day roll over from 2017-04-02 to 2017-04-03 worked fine, so it appears this date aberration is limited to the day daylight savings changes.

This appears to be an issue with ClientDateUtil, i.e. a client only issue.

Hopefully fixed this issue but testing required.

Problem corrected with build version 5.0-beta.18. Thanks!


Unable to create react-native-app

Hi,
D:\Bally\ReactNativeApp>node -v v6.11.1
D:\Bally\ReactNativeApp>npm -v 5.3.0
D:\Bally\ReactNativeApp>create-react-native-app AweApp 'create-react-native-app' is not recognized as an internal or external command, operable program or batch file.
D:\Bally\ReactNativeApp>
Everything configured properly but commands not recognized...don`t know why
unable to create react native app by Node Plz provide step by step app creation process...

Did you npm install -g create-react-native-app ?

I too got the similar problem...when i m installing terminal shows success and when i access the command "create-react-native-app" terminal says command not found
i hv node 8
npm 5.0.2
yarn 0.27

@therovermind - if you look in README you will see that npm 5 is buggy and not supported. we recommend using npm 4.6.1


Fix fleet resources not having ID set on import

Fixed fleet objects not having an ID set when importing.
When creating a new resource, if the ID was not explicitly specified, then the *_id value is used from the schema. For all other modes (update, read, delete), the existing/provided ID is used. This resolves the issue where the *_id value (even if it was empty) would override the provided ID value (i.e., during import).
Update fleet documentation to remove kibana space id. Fleet objects aren't scoped by spaces, but rather use their own IDs.

Related issues:

Fixes #396
Fixes #369

Tested importing agent policy, fleet server host, and output:
$ TF_LOG=INFO terraform import elasticstack_fleet_agent_policy.docker_fleet_agent elastic-agent-managed-ep
2023-10-13T14:13:49.507-0500 [INFO]  Terraform version: 1.4.6
2023-10-13T14:13:49.508-0500 [INFO]  Go runtime version: go1.19.6
2023-10-13T14:13:49.508-0500 [INFO]  CLI args: []string{"terraform", "import", "elasticstack_fleet_agent_policy.docker_fleet_agent", "elastic-agent-managed-ep"}
2023-10-13T14:13:49.508-0500 [INFO]  Loading CLI configuration from /Users/tswanson/.terraformrc
2023-10-13T14:13:49.508-0500 [INFO]  CLI command args: []string{"import", "elasticstack_fleet_agent_policy.docker_fleet_agent", "elastic-agent-managed-ep"}
2023-10-13T14:13:49.518-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:13:49.868-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:13:49.868-0500
2023-10-13T14:13:49.912-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:13:49.935-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:13:49.935-0500
elasticstack_fleet_agent_policy.docker_fleet_agent: Importing from ID "elastic-agent-managed-ep"...
elasticstack_fleet_agent_policy.docker_fleet_agent: Import prepared!
  Prepared elasticstack_fleet_agent_policy for import
elasticstack_fleet_agent_policy.docker_fleet_agent: Refreshing state... [id=elastic-agent-managed-ep]
2023-10-13T14:13:50.051-0500 [WARN]  Provider "registry.terraform.io/hashicorp/elasticstack" produced an unexpected new value for elasticstack_fleet_agent_policy.docker_fleet_agent during refresh.
      - .name: was null, but now cty.StringVal("Elastic-Agent (elastic-package)")
      - .namespace: was null, but now cty.StringVal("default")
      - .monitor_logs: was null, but now cty.True
2023-10-13T14:13:50.052-0500 [INFO]  Writing state output to:

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

$ TF_LOG=INFO terraform import elasticstack_fleet_server_host.default_host fleet-default-fleet-server-host
2023-10-13T14:14:21.337-0500 [INFO]  Terraform version: 1.4.6
2023-10-13T14:14:21.337-0500 [INFO]  Go runtime version: go1.19.6
2023-10-13T14:14:21.337-0500 [INFO]  CLI args: []string{"terraform", "import", "elasticstack_fleet_server_host.default_host", "fleet-default-fleet-server-host"}
2023-10-13T14:14:21.337-0500 [INFO]  Loading CLI configuration from /Users/tswanson/.terraformrc
2023-10-13T14:14:21.338-0500 [INFO]  CLI command args: []string{"import", "elasticstack_fleet_server_host.default_host", "fleet-default-fleet-server-host"}
2023-10-13T14:14:21.346-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:14:21.379-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:14:21.379-0500
2023-10-13T14:14:21.417-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:14:21.438-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:14:21.438-0500
elasticstack_fleet_server_host.default_host: Importing from ID "fleet-default-fleet-server-host"...
elasticstack_fleet_server_host.default_host: Import prepared!
  Prepared elasticstack_fleet_server_host for import
elasticstack_fleet_server_host.default_host: Refreshing state... [id=fleet-default-fleet-server-host]
2023-10-13T14:14:21.499-0500 [WARN]  Provider "registry.terraform.io/hashicorp/elasticstack" produced an unexpected new value for elasticstack_fleet_server_host.default_host during refresh.
      - .name: was null, but now cty.StringVal("Default")
      - .default: was null, but now cty.True
      - .hosts: was null, but now cty.ListVal([]cty.Value{cty.StringVal("https://fleet-server:8220")})
2023-10-13T14:14:21.501-0500 [INFO]  Writing state output to:

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

$ TF_LOG=INFO terraform import elasticstack_fleet_output.default_output fleet-default-output
2023-10-13T14:14:27.709-0500 [INFO]  Terraform version: 1.4.6
2023-10-13T14:14:27.709-0500 [INFO]  Go runtime version: go1.19.6
2023-10-13T14:14:27.709-0500 [INFO]  CLI args: []string{"terraform", "import", "elasticstack_fleet_output.default_output", "fleet-default-output"}
2023-10-13T14:14:27.709-0500 [INFO]  Loading CLI configuration from /Users/tswanson/.terraformrc
2023-10-13T14:14:27.710-0500 [INFO]  CLI command args: []string{"import", "elasticstack_fleet_output.default_output", "fleet-default-output"}
2023-10-13T14:14:27.719-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:14:27.796-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:14:27.795-0500
2023-10-13T14:14:27.834-0500 [INFO]  provider: configuring client automatic mTLS
2023-10-13T14:14:27.868-0500 [INFO]  provider.terraform-provider-elasticstack: configuring server automatic mTLS: timestamp=2023-10-13T14:14:27.868-0500
elasticstack_fleet_output.default_output: Importing from ID "fleet-default-output"...
elasticstack_fleet_output.default_output: Import prepared!
  Prepared elasticstack_fleet_output for import
elasticstack_fleet_output.default_output: Refreshing state... [id=fleet-default-output]
2023-10-13T14:14:27.929-0500 [INFO]  Writing state output to:

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

@tobio,
I noticed when testing this that there seem to be some breaking changes around the provider schema, specifically when providing username and password for the kibana or fleet sections. This used to work, but not anymore, possibly due to #343?
provider "elasticstack" {
  fleet {
    endpoint = "https://localhost:5601"
    username = "elastic"
    password = "abcd1234"
    insecure = true
  }
}

Yields:
│ Error: Invalid Path Expression for Schema
│
│   with provider["registry.terraform.io/hashicorp/elasticstack"],
│   on /Users/tswanson/Workarea/terraform/elasticstack/test8/main.tf line 1, in provider "elasticstack":
│    1: provider "elasticstack" {
│
│ The Terraform Provider unexpectedly provided a path expression that does not match the current schema. This can happen if the path expression does not correctly follow the schema in structure or types. Please report this to the provider developers.
│
│ Path Expression: fleet.0.username
╵

╷
│ Error: Invalid Path Expression for Schema
│
│   with provider["registry.terraform.io/hashicorp/elasticstack"],
│   on /Users/tswanson/Workarea/terraform/elasticstack/test8/main.tf line 1, in provider "elasticstack":
│    1: provider "elasticstack" {
│
│ The Terraform Provider unexpectedly provided a path expression that does not match the current schema. This can happen if the path expression does not correctly follow the schema in structure or types. Please report this to the provider developers.
│
│ Path Expression: fleet.0.password
╵

Kibana has the same problem. If I move those to elasticsearch, then everything works fine.
Not sure if this was intentional or if you've seen anything with this, yet.

@tobio, @taylor-swanson would it be possible to have a new release including this fix, maybe v0.9.1?

@breml, that's what I was thinking, a v0.9.1 release for this and include #448 as well, which was just merged.
@tobio, would we be able to cut a new release soon? It'd be good to get these bug fixes out before the Protocol 6 work gets merged.

Yea, we get these two released. It feels worthwhile waiting for https://github.com/elastic/terraform-provider-elasticstack/pull/454 as well unless you think that one might get delayed?

@tobio, I'll see if I can get the changes turned around for #454. If it takes me more than 24 hours, feel free to cut the v0.9.1 release as is and #454 could go into a v0.9.2 or something equivalent. I mainly don't want to hold up the bug fixes as we have a number of people waiting on them.


Issue running code line-by-line in vscode: Cannot determine RHOME

Describe the bug
Hi! I'm getting an error of Cannot determine R HOME when trying to execute code line-by-line in VSCode. This is a new problem which hadn't happened to me before, so I think an update might have broken some settings in some weird and wonderful way?
To Reproduce
Steps to reproduce the behavior:

Open a random R script
command + enter on the first line (which happens to say library(tidyverse) but this is irrelevant)

Do you want to fix by self?
I wish I could
(If yes,) what kind of help do you want? (e.g. Which file should I fix, Survey (related documents)
(If related)setting.json

// R path for Mac OS X
"r.rterm.mac": "/Users/darya/anaconda3/bin/radian"

// R command line options (i.e: --vanilla)
"r.rterm.option": [],

// An optional encoding to pass to R when executing the file, i.e. 'source(FILE, encoding=ENCODING)'
"r.source.encoding": "UTF-8",

// Keeping focus when running
"r.source.focus": "editor",

// Use active terminal for all commands, rather than creating a new R terminal
"r.alwaysUseActiveTerminal": false,

// Use bracketed paste mode
"r.bracketedPaste": true,

// Enable R session watcher (experimental)
"r.sessionWatcher": true,

// Delay in milliseconds before sending each line to rterm (only applies if r.bracketedPaste is false)
"r.rtermSendDelay": 8,

Expected behavior
I was hoping the code would run line by line...
Environment (please complete the following information):

OS: macOS 10.15.7 (19H2)
VSCode Version: Version: 1.50.1
R Version: 4.0.2
vscode-R version: v1.5.1

Additional context
Running /Users/darya/anaconda3/bin/radian (or radian) from the zsh command line results in R happily launching, and the library(tidyverse) code working without errors (as does running the script from RStudio)
What's wrong with my Config? Thanks in advance!
PS I have seen the issue here - but can't seem to fix the R RHOME issue by using the tips there.

Looks like https://github.com/randy3k/radian/issues/219

@renkun-ken Thanks - yes, setting
"r.alwaysUseActiveTerminal": false
"r.bracketedPaste": false

Fixes the problem.
Why does this happen, though?

Looks like you haven't changed any settings?

Sorry I might have poorly grabbed the config. Biggest difference was that originally I had it set that I was NOT always using the active terminal and it didn't work.
Instead, when I set it to always use the active terminal, launched R from the vscode terminal, and then tweaked the brackets setting so no extra characters were being added it seems to work.

With "r.alwaysUseActiveTerminal": false, when you press ctrl+enter on an R document, it will run r.createRTerm command to launch an R session automatically.
In your settings, "r.rterm.mac": "/Users/darya/anaconda3/bin/radian" will make vscode-R launch radian instead of R. It seems that you could successfully run radian manually in VSCode terminal, but vscode-R cannot launch radian but fails with Cannot determine R HOME? You could simply verify this by pressing F1 and run R: Create R terminal command and it should produce the same error.

Yes, it does produce the same error. Any advice on how to fix it?

Looks like something is missing in the environment variables to launch radian by R: Create R terminal, something different from your zsh terminal in vscode. Not sure if this is a VSCode-specific problem?
@randy3k @andycraig any idea on why this could happen?

Where did you install R? It may be possible that you have a different PATH variable in VSCode. I recall that there is an option in VSCode to inherit the environment variables from the shell. You may want to check that out.

@dvanic Maybe you need to specify the following in your vscode settings?
"terminal.integrated.env.osx": {
  "R_HOME": "..."
}

@renkun-ken
Specifying that in the VSCode settings did indeed solve the problem!
It does generate a warning of :
Warning message:
requested TAR '/usr/bin/tar' does not exist; using 'internal' instead

But then libraries load and code executes.
I am curious, though, how to get it to properly
source("~/.Rprofile")

since I've got a few custom functions in that, and VSCode is clearly not picking them up...

It looks like some important environment variables are missing when vscode-R launches radian via window.createTerminal(termOptions). I guess we should use what https://github.com/ManuelHentschel/VSCode-R-Debugger/blob/master/src/installRPackage.ts#L26 does: sending R terminal command to the shell in vscode terminal.

@dvanic You might try installing the vsix from https://github.com/renkun-ken/vscode-R/actions/runs/334838489 and see if it works now.

I got this error and fixed it adding R to my PATH (it broke after I updated R)
Link: https://www.r-bloggers.com/2023/02/fixing-my-broken-vscode-setup-for-r/

@dvanic Maybe you need to specify the following in your vscode settings?
"terminal.integrated.env.osx": {
  "R_HOME": "..."
}

Note for an R installation (in linux) using a conda environment named r the path is like "/PATH/TO/CONDA/envs/r/lib/R"


Build steps currently fail on ARM (e.g., macOS M1) arch

I ran into a slight obstacle while trying to generate the v0.19 release.
Recording this so no one else spends time on it
https://github.com/open-telemetry/build-tools/issues/115

https://github.com/open-telemetry/build-tools/pull/116 :grin:


Bump GOV.UK Frontend to latest release

You can preview this change here:
Built with commit 7287317ceeaf9d4ac0782957cba6916747ba633e
https://deploy-preview-665--govuk-design-system-preview.netlify.com

There's a lot of changes to the package lock file – any ideas why?

The changes to the lock file have been resolved in #668 and this has been rebased to only include the changes to govuk-frontend.


TypeError: list indices must be integers or slices, not str

python3 cloudfail.py -t cdn.duzun.me

There was an error getting results
Traceback (most recent call last):
  File "cloudfail.py", line 285, in <module>
    dnsdumpster(args.target)
  File "cloudfail.py", line 84, in dnsdumpster
    if res['dns_records']['host']:
TypeError: list indices must be integers or slices, not str

Hi thanks for reporting,
can you confirm it is resolved in commit https://github.com/m0rtem/CloudFail/commit/a2ac2e075bb10d67d68d72c15309cd6efe4be71e for me please?

Hi @m0rtem!
python3 cloudfail.py -t codeby.net
[16:28:53] Testing for misconfigured DNS using dnsdumpster...   There was an error getting results Traceback (most recent call last):   File "/Users/amur/CloudFail/cloudfail.py", line 312, in <module>     dnsdumpster(args.target)   File "/Users/amur/CloudFail/cloudfail.py", line 86, in dnsdumpster     if res['dns_records']['host']: TypeError: list indices must be integers or slices, not str


feat(eip4844): include TxEip4844 in the primitive Transaction enum

Describe the feature
TxEip4844 has to be included in the primitive Transaction enum.
https://github.com/paradigmxyz/reth/blob/544c51cc9ff15d0626cdb63666ad3d195c806be0/crates/primitives/src/transaction/mod.rs#L40-L68
Additional context
No response

Fixed with #4074


BUG Report

I used the seventh layer and found no effect, only for the first few seconds
Ubuntu

Python 3.8.x

It got mitigated, nothing else, also don't use dstat.cc, they are hilariously inaccurate

Working


Update "getting started" articles for CodeQL CLI to use monospace font for file/directory names consistently

Code of Conduct

[x] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Historically, our style guide recommended using italic font to format file names and directory names in our documentation. Our current guidelines recommend using monospace font and it would be good to update more articles to follow the current guidelines. For more information, see: "File names and directory names"
What part(s) of the article would you like to see updated?
Files to review and check for file names and directory names that should be reformatted:

[x] About the CodeQL CLI
[x] Setting up the CodeQL CLI
[x] Preparing your code for CodeQL analysis
[x] Analyzing your code with CodeQL queries
[x] Customizing analysis with CodeQL packs
[x] Uploading CodeQL analysis results to GitHub

Additional information
No response

What exactly do you mean by monospace font?

@Manas-Kenge - thanks for showing an interest in fixing this issue. If you take a look at the link in the issue summary, to the information on file and directory names in our style guide, you should find more explanation about monospace font and how to format text in this way.

Code of Conduct
* [x]  I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/CODE_OF_CONDUCT.md)

What article on docs.github.com is affected?
Historically, our style guide recommended using italic font to format file names and directory names in our documentation. Our current guidelines recommend using monospace font and it would be good to update more articles to follow the current guidelines. For more information, see: "File names and directory names"
What part(s) of the article would you like to see updated?
Files to review and check for file names and directory names that should be reformatted:
* [ ]  [About the CodeQL CLI](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/about-the-codeql-cli)

* [ ]  [Setting up the CodeQL CLI](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli)

* [ ]  [Preparing your code for CodeQL analysis](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis)

* [ ]  [Analyzing your code with CodeQL queries](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries)

* [ ]  [Customizing analysis with CodeQL packs](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs)

* [ ]  [Uploading CodeQL analysis results to GitHub](https://docs.github.com/en/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github)

Additional information
No response

@felicitymay I reviewed all the linked articles but I couldn't find any misplaced <em> tag. Can you link any specific example of that?

@albbus-stack 👋🏻
Thanks for taking a look at this issue. I think you're right and there's nothing left to fix here. I guess either the changes were made as part of some other updates or maybe our script had some false positive results.
Thank you for taking the time to look at this and enabling us to close this issue with confidence.
I suggest that you check the tasks for all the articles you've looked at, and then we can close this issue as a Hacktoberfest contribution.

[X]  About the CodeQL CLI

[X]  Setting up the CodeQL CLI

[X]  Preparing your code for CodeQL analysis

[X]  Analyzing your code with CodeQL queries

[X]  Customizing analysis with CodeQL packs

[X]  Uploading CodeQL analysis results to GitHub

Many thanks for your help @albbus-stack I'll close this as a Hacktoberfest contribution.
I hope that this doesn't put you off looking at our other help-wanted issues.


Is the circular obstacle position in generated hires data is different than readme/paper figures?

I hope you are doing well today. I used the following instructions in the readme to generate the hi-resolution data:
make karman-fdt-hires-set      # Generate traning data set
make karman-fdt-hires-testset  # Generate test data set

The position of the circular obstacle in the data generated where I used your code appears to be at the position (1/2, 1/2) in the domain [0,1]x[0,2] as described in section B.1 of your Solver in the Loop paper. Here is a sample from the generated data below:

This differs from the images presented in the readme and paper in which the the circular obstacle is at the bottom of the domain.
Are the simulation images provided in the readme/paper cropped or did I somehow generate data that is different from what is being used to get your results in the paper?
Another reason I ask is because I computed the low-resolution simulation data then computed the average of the MAE for the 5 test simulations (i.e. $(1/5) sum_{i=1}^5 MAE(lo_res_sim_i, hi_res_sim_i)$) and got 0.178. However, Table 1 in your paper seems to indicate this value should be 0.146.
Any thoughts or insight on this would be appreciated. Thank you!

The obstacle is definitely centered in the half of the domain towards the inflow. The MAE differences potentially come from differences in the test cases, I can recommend to primarily look at improvements of the learned models relative to this MAE baseline.


Added additional information to make installing Hyuga easier.

Instructions on how to register Hyuga using lspconfig have been added, and instructions on the installation of Hyuga itself on Linux distributions that use externally managed Python environments (primarily Arch), where trying to pip3 install hyuga without --break-system-packages is literally impossible, have also been added (pipx, as mentioned in the aforementioned spec is the most common way of installing packages via pip on EME distros)
These additions are all hurdles I faced that I had to figure out myself. I'm hoping to include this information so that the next person doesn't have to go through the same 2 hour installation process I had to go through.
That, and lspconfig is generally the most popular way to deal with language servers in Neovim nowadays.
I hope this helps save someone from a future headache.

It's useful information. Thank you!


Map "SentTimestamp" to SqsMessageHeaders

When injecting MessageHeaders into a method annotated with @SqsListener, then in these headers the timestamp is missing.
Calling headers.getTimestamp() returns null. In the message from SQS there are the properties "SentTimestamp" and "ApproximateFirstReceiveTimestamp" available.
Would be nice if "SentTimestamp" was mapped into "timestamp" when creating MessageHeaders.
Otherwise would be also possible to add specific getters for the two different timestamp properties to SqsMessageHeaders. But at the moment it seems not possible to inject SqsMessageHeaders into the method, only MessageHeaders.

Can I look at this one?

@voytech go for it!

@maciejwalkowiak  @erikpetzold
The problem with null value in timestamp in MessageHeaders occurs when dispatching a message to handler. It is because there is a need of enriching existing  MessageHeaders with lookupDestination header. For that purpose MessageHeadersAccessor is used internally. MessageHeaderAccessors after adding new header, creates its own implementation of MessageHeaders -  **MessageHeaderAccessor.MutableMessageHeaders**, and this is runtime object which is always present in @SqsListener method. MessageHeaderAccessor is implemented in such a way that it makes ID and TIMESTAMP always nulls - it is because it is creating new MessageHeaders object, and its seems to be designed in such a way that ID and TIMESTAMP are meant to be tightly connected with SINGLE immutable instance of an MessageHeaders, that is why timestamp is always null. Looking at the code it can be also set to new current timestamp value, but never can contain original, externally provided timestamp.
So the question is, if timestamp header is designed to keep such external property like e.g. 'SentTimestamp', or by design it should contain a current time when MessageHeaders where instantiated ? If this is not the case, and If it should be possible to pass external value as timestamp - so this seems to be issue witch spring-messaging and the way how MessageHeadersAccessor works

Otherwise would be also possible to add specific getters for the two different timestamp properties to SqsMessageHeaders. But at the moment it seems not possible to inject SqsMessageHeaders into the method, only MessageHeaders.

Nevertheless I see following solutions for above:

Writing custom MethodArgumentResolver supporting SqsMessageHeaders as parameter to SqsListener handler method, and map runtime MessageHeaderAccessor.MutableMessageHeaders to new SqsMessageHeaders with timestamp populated from SentTimestamp and additionally providing convenient getters for ApproximateFirstReceiveTimestamp, and ApproximateReceiveCount.

Switching from AbstractMethodMessageHandler.handleMessage (which internally uses MessageHeaderAccessor)  - and creating new method (say - handleSqsMessage in QueueMessageHandler) which instead of using MessageHeaderAccessor will create SqsMessageHeaders instance directly. This solution makes handleMessage from AbstractMethodMessageHandler unused, and introduces sibling method with same responsibility (without MessageHeaderAccessor) in QueueMessageHandler - I think bad design. Also I think that I may not know everything about rationale for presence of MessageHeaderAccessor in here. It seems to be here for real reason, maybe it should be required for @SqsListener handler method to always have runtime type MessageHeaderAccessor.MutableMessageHeaders for consumers?

I think that more acceptable solution is first one, as long as this approach utilizes MethodArgumentResolvers, so I think we are using things the way they are designed to be used. It is not workaround (like second solution), It is just framework way of resolving arguments.
But still the question is.. Is it good to use timestamp header to hold external SentTimestamp which is timestamp the massage was sent to the queue ?

@maciejwalkowiak I have created pull request for this one here - https://github.com/spring-cloud/spring-cloud-aws/pull/584.  I see that there are plans to rewrite sqs integration, so not sure if this pull request is still valid.
I have also a little concern if this change should be allowed to go with ‚minor’ version change - it is enchancement which doesn’t break compile time backward compatibility, but changes runtime object injected as MessageHeaders (it is now SqsMessageHeaders).
Please let me know if you are going to review (If you want different approach I can also change implementation), or otherwise close. ;)

Hey @voytech! I had a quick look and I'll do deeper review this week. SQS is going to change but hopefully only internally and API remains the same. Your changes look good and if they are breaking they will just go with 2.3. But let me spend one evening with them first ;)


Fixes #545 - Addition of Auto-Assign Bot

Fixes #545

@shreyasbapat

Looks good. I'll need to install some app?

Looks good. I'll need to install some app?

Looks good. I'll need to install some app?

Yeah, this: https://probot.github.io/apps/auto-assign/

Looks good. I'll need to install some app?

Yeah, this: https://probot.github.io/apps/auto-assign/

I have requested an install for EinsteinPy: @shreyasbapat

I have requested an install for EinsteinPy: @shreyasbapat

@shreyasbapat Have you configured the bot or should I? I was thinking to give it access to just this repo.

@shreyasbapat Have you configured the bot or should I? I was thinking to give it access to just this repo.

@shreyasbapat Oh, actually, you have to configure it. I can't.

@shreyasbapat Oh, actually, you have to configure it. I can't.

@shreyasbapat Oh, actually, you have to configure it. I can't.

Okay. I think I did not configure it on the repo.

@shreyasbapat Oh, actually, you have to configure it. I can't.

Okay. I think I did not configure it on the repo.

Let's see how that works :P

Let's see how that works :P


Updated with fix for EJS templates rendering as document fragments

Worked with @justinbmeyer to come up with a solution to the [Object DocumentFragment] string being displayed on some instances where EJS was being used.

Add async to can-ajax
Copy the deferred "polyfill" into this repo and import and use it.
Move the .register call into can-ejs
Look for all other uses of can.X and if possible, import the method directly.
Add a test for calling can.view.renderer() .. does it render as a string?
Do other tests work?  Hopefully.
Is there any code paths that are not supported (like deferrreds stuff), remove and replace with an error warning.
Publish and celebrate.

Closing in favor of #38 (same but with extra fixes).


Added dev operations file for running on bosh-lite

What this PR does / why we need it:

How can this PR be verified?
Executing within a bosh-lite environment
Is there any change in kubo-release?
No
Is there any change in kubo-ci?
No
Does this affect upgrade, or is there any migration required?
N/A
Which issue(s) this PR fixes:
Release note:
Once you have a bosh-lite environment, deploy using the following:
./bin/deploy_cfcr_lite -o manifests/ops_files/dev.yml

Closing and reopening to rectify CLA


Fix TLD implementation and add tests.

Previously the tld method would ignore it's input and always return the
tld of the current host.
Also includes some style fixes and test improvements so that failures
are more descriptive than expected true === false.

cc @ndhoule @tsholmes