psmoveservice pairing process gone strange

Hi, whenever I go to the "Pair controller" button, it goes through the process, but when it gets to 7/7, it just goes to the controller settings screen with no controller paired. I will put the logs, hopefully this is a fixable problem, thank you!
[2020-04-29 19:02:11.593]: main - Starting PSMoveService v0.9-alpha 9.0.1 (protocol v0.9-alpha 9.0.0)
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\USBManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\USBManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\NetworkManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\NetworkManagerConfig.json"
[2020-04-29 19:02:11.636]: USBAsyncRequestManager::startup - Requested LibUSBApi
[2020-04-29 19:02:11.637]: USBAsyncRequestManager::startup - Creating LibUSBApi
[2020-04-29 19:02:11.639]: USBAsyncRequestManager::startup - Initialized USB API
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\DeviceManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\DeviceManagerConfig.json"
[2020-04-29 19:02:11.654]: DeviceManager::startup - Platform Hotplug API is ENABLED
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\ControllerManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\ControllerManagerConfig.json"
[2020-04-29 19:02:11.692]: bluetooth_get_host_address - Found a bluetooth radio
[2020-04-29 19:02:11.693]: bluetooth_get_host_address - Retrieved radio info
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\TrackerManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\TrackerManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\HMDManagerConfig.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\HMDManagerConfig.json"
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2020-04-29 19:02:11.742]: PSMoveController::open - Opening PSMoveController(\?\hid#vid_054c&pid_0c5e&col01#7&1a0b18b0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2020-04-29 19:02:11.744]: PSMoveController::open -   with EMPTY serial_number
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\a4_53_85_d7_29_09.json"
[2020-04-29 19:02:11.747]: WorkerThread::start - Starting worker thread: PSMoveSensorProcessor
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\a4_53_85_d7_29_09.json"
[2020-04-29 19:02:11.756]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSMove) opened
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2020-04-29 19:02:11.764]: TrackerDeviceEnumerator - Skipping device (USB\VID_1415&PID_2000\b2_p13.4.2) - Operation not supported or unimplemented on this platform
[2020-04-29 19:02:11.767]: PS3EyeTracker::open - Opening PS3EyeTracker(USB\VID_1415&PID_2000\b2_p13.4.1, camera_index=0)
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
ps3eye::PS3EYECam::getDevices() found 2 devices.
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\PS3EyeTrackerConfig_ps3eye_b2_p13.4.1.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\PS3EyeTrackerConfig_ps3eye_b2_p13.4.1.json"
[2020-04-29 19:02:12.33]: SharedMemory::initialize() - Allocating shared memory: tracker_view_0
[2020-04-29 19:02:12.460]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSEYE) opened
[2020-04-29 19:02:12.462]: PS3EyeTracker::open - Opening PS3EyeTracker(USB\VID_1415&PID_2000\b2_p13.4.2, camera_index=1)
ps3eye::PS3EYECam::getDevices() found 2 devices.
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\PS3EyeTrackerConfig_ps3eye_b2_p13.4.2.json"
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\PS3EyeTrackerConfig_ps3eye_b2_p13.4.2.json"
[2020-04-29 19:02:12.701]: SharedMemory::initialize() - Allocating shared memory: tracker_view_1
[2020-04-29 19:02:12.710]: DeviceTypeManager::update_connected_devices - Device device_id 1 (PSEYE) opened
[2020-04-29 19:02:14.23]: ClientConnection::start - Starting client connection id 0
[2020-04-29 19:02:14.23]: ClientConnection::send_connection_info - Sending connection id to client 0
[2020-04-29 19:02:16.936]: PSMoveSensorProcessor::doWork - HID ERROR: The device is not connected.
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2020-04-29 19:02:16.998]: DeviceTypeManager::update_connected_devices - Closing device 0 (PSMove) since it's no longer in the device list.
[2020-04-29 19:02:17.0]: PSMoveController::close - Closing PSMoveController(\?\hid#vid_054c&pid_0c5e&col01#7&1a0b18b0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2020-04-29 19:02:17.2]: WorkerThread::stop - Stopping worker thread: PSMoveSensorProcessor
[2020-04-29 19:02:17.4]: WorkerThread::stop - Worker thread stopped: PSMoveSensorProcessor
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2020-04-29 19:02:20.121]: PSMoveController::open - Opening PSMoveController(\?\hid#vid_054c&pid_0c5e&col01#7&1a0b18b0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2020-04-29 19:02:20.134]: PSMoveController::open -   with EMPTY serial_number
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\a4_53_85_d7_29_09.json"
[2020-04-29 19:02:20.153]: WorkerThread::start - Starting worker thread: PSMoveSensorProcessor
Config file name: "C:\Users\Matth\AppData\Roaming\PSMoveService\a4_53_85_d7_29_09.json"
[2020-04-29 19:02:20.192]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSMove) opened
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2020-04-29 19:02:21.666]: AsyncBluetoothPairDeviceRequest - Found a bluetooth radio
[2020-04-29 19:02:21.668]: AsyncBluetoothPairDeviceRequest - Retrieved radio info
[2020-04-29 19:02:21.670]: AsyncBluetoothPairDeviceRequest - Assigned host address 00:1a:7d:da:71:13 to controller id 0
[2020-04-29 19:02:21.671]: ServerRequestHandler - Async bluetooth request([Pair] ID: 0 Conn: 0) started.
[2020-04-29 19:02:23.21]: AsyncBluetoothPairDeviceRequest - No Bluetooth device found matching the given address: a4:53:85:d7:29:09
[2020-04-29 19:02:24.433]: AsyncBluetoothPairDeviceRequest - Bluetooth device found matching the given address: a4:53:85:d7:29:09
[2020-04-29 19:02:24.436]: AsyncBluetoothPairDeviceRequest - Bluetooth device matching the given address is the expected controller type
[2020-04-29 19:02:24.955]: BluetoothAuthCallback - Not authenticated
[2020-04-29 19:02:24.956]: BluetoothAuthenticateDevice - Failed to authenticate!
[2020-04-29 19:02:26.370]: AsyncBluetoothPairDeviceRequest - Bluetooth device found matching the given address: a4:53:85:d7:29:09
[2020-04-29 19:02:26.373]: AsyncBluetoothPairDeviceRequest - Bluetooth device matching the given address is the expected controller type
[2020-04-29 19:02:33.887]: BluetoothAuthCallback - Bluetooth device authenticated!
[2020-04-29 19:02:33.890]: BluetoothAuthenticateDevice - Successfully paired.
[2020-04-29 19:02:35.299]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:35.301]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:35.302]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:35.304]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:35.305]: AsyncBluetoothPairDeviceRequest - HID service not enabled, attempting to enable
[2020-04-29 19:02:38.312]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:38.322]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:38.326]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:38.334]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:38.335]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:38.336]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:38.338]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:38.339]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:38.340]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:38.641]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:38.643]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:38.945]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80
[2020-04-29 19:02:38.949]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:38.950]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:38.951]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:38.955]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:38.959]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:38.960]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:38.965]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:38.966]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:39.268]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:39.270]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:39.271]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:39.274]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:39.276]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:39.277]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:39.282]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:39.584]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:39.585]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:39.887]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80
[2020-04-29 19:02:39.888]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:40.196]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80
[2020-04-29 19:02:40.205]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:40.516]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80
[2020-04-29 19:02:40.534]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:40.837]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80
[2020-04-29 19:02:40.840]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:41.141]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80
[2020-04-29 19:02:41.142]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:41.446]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80
[2020-04-29 19:02:41.450]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:41.751]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80
[2020-04-29 19:02:41.755]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:42.56]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80
[2020-04-29 19:02:42.57]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:42.359]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80
[2020-04-29 19:02:42.366]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:42.668]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80
[2020-04-29 19:02:42.670]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:42.972]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80
[2020-04-29 19:02:42.974]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:43.274]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80
[2020-04-29 19:02:43.276]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:43.582]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80
[2020-04-29 19:02:43.584]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:43.885]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80
[2020-04-29 19:02:43.887]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:44.188]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80
[2020-04-29 19:02:44.189]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:44.491]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80
[2020-04-29 19:02:44.492]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:44.799]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80
[2020-04-29 19:02:44.802]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:45.105]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80
[2020-04-29 19:02:45.107]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:45.408]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80
[2020-04-29 19:02:45.410]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:45.714]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80
[2020-04-29 19:02:45.716]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:46.17]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80
[2020-04-29 19:02:46.21]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:46.338]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80
[2020-04-29 19:02:46.673]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:46.978]: AsyncBluetoothPairDeviceRequest - Connection attempt: 24/80
[2020-04-29 19:02:46.980]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:46.984]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:46.985]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:46.987]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:46.989]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:46.991]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:46.998]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:46.999]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:47.301]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:47.304]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:47.306]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:47.307]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:47.308]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:47.310]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:47.315]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:47.635]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:47.889]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:47.899]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:47.905]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:47.906]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:47.922]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:47.931]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:47.932]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:47.937]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:48.251]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:48.252]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:48.254]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:48.255]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:48.256]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:48.257]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:48.259]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:48.563]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:48.564]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:48.565]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:48.567]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:48.568]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:48.569]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:48.570]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:48.571]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:48.573]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:48.876]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:48.877]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:48.881]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:48.882]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:48.883]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:48.884]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:48.886]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:49.188]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:49.189]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:49.491]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80
[2020-04-29 19:02:49.492]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:49.799]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80
[2020-04-29 19:02:49.800]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:50.102]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80
[2020-04-29 19:02:50.104]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:50.105]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:50.106]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:50.107]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:50.115]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:50.116]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:50.117]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:50.119]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:50.420]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:50.422]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:50.423]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:50.424]: AsyncBluetoothPairDeviceRequest - HID service not enabled
[2020-04-29 19:02:50.425]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection
[2020-04-29 19:02:50.426]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80
[2020-04-29 19:02:50.433]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:50.734]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80
[2020-04-29 19:02:50.736]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:51.37]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80
[2020-04-29 19:02:51.39]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:51.340]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80
[2020-04-29 19:02:51.341]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:51.648]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80
[2020-04-29 19:02:51.649]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:51.951]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80
[2020-04-29 19:02:51.952]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:52.254]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80
[2020-04-29 19:02:52.256]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:52.557]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80
[2020-04-29 19:02:52.559]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:52.865]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80
[2020-04-29 19:02:52.866]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:53.167]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80
[2020-04-29 19:02:53.169]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:53.472]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80
[2020-04-29 19:02:53.474]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:53.775]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80
[2020-04-29 19:02:53.781]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:54.83]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80
[2020-04-29 19:02:54.84]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:54.386]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80
[2020-04-29 19:02:54.389]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:54.690]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80
[2020-04-29 19:02:54.692]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:54.994]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80
[2020-04-29 19:02:54.996]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:55.298]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80
[2020-04-29 19:02:55.300]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:55.602]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80
[2020-04-29 19:02:55.605]: AsyncBluetoothPairDeviceRequest - Device not connected
[2020-04-29 19:02:55.913]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80
[2020-04-29 19:02:55.958]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:55.965]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:55.966]: AsyncBluetoothPairDeviceRequest - Checking HID service
[2020-04-29 19:02:55.967]: AsyncBluetoothPairDeviceRequest - HID service not enabled, attempting to enable
[2020-04-29 19:02:58.989]: AsyncBluetoothPairDeviceRequest - Patching the registry ...
[2020-04-29 19:02:58.990]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist
[2020-04-29 19:02:58.991]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5
[2020-04-29 19:02:58.993]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:58.995]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:58.996]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:58.997]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:59.299]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5
[2020-04-29 19:02:59.301]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:59.301]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:59.302]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:59.304]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:59.606]: AsyncBluetoothPairDeviceRequest - Verification attempt 2 / 5
[2020-04-29 19:02:59.607]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:59.608]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:59.609]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:59.609]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:02:59.916]: AsyncBluetoothPairDeviceRequest - Verification attempt 3 / 5
[2020-04-29 19:02:59.917]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:02:59.918]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:02:59.919]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:02:59.921]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:03:00.223]: AsyncBluetoothPairDeviceRequest - Verification attempt 4 / 5
[2020-04-29 19:03:00.225]: AsyncBluetoothPairDeviceRequest - Device Connected
[2020-04-29 19:03:00.226]: AsyncBluetoothPairDeviceRequest - Device Remembered
[2020-04-29 19:03:00.226]: AsyncBluetoothPairDeviceRequest - HID service enabled
[2020-04-29 19:03:00.227]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled
[2020-04-29 19:03:00.228]: AsyncBluetoothPairDeviceRequest - Verified connection!
[2020-04-29 19:03:00.234]: ServerRequestHandler - Async bluetooth request([Pair] ID: 0 Conn: 0) completed.
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [init_device] device '\.\USB#VID_258A&PID_1007&MI_01#6&2B94D18B&0&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent

I am having the same problem. I sadly do not have any coding experience though. Registry key is messing up. Though after trying again it doesn't seem to want to connect anymore. Hoping this gets fixed soon!

Ive been trying to pair this for 1 year now and no luck so I am just going to order a oculus rift s. Fingers crossed this gets fixed :)


Configuration pending

I agree to the following

[X] I have read the documentation
[X] I am aware of the latest release notes
[X] The Backend (CCU/Homegear/...) is working as expected and connected devices are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
I'm not able to add the integration.
The message which is shown while trying to add the Integration is:
Bitte warten, Konfigurationsassistent für homematicip_local wird gestartet
I waited already over 20min.
I also can't see anything in the HomeAsssistant log files.
What version of HomematicIP (local) has the issue?
newest
What was the last working version of HomematicIP (local)?
no one
What type of installation are you running?
Home Assistant Supervised
What type of installation are you running for your homematic backend?
RaspberryMatic Standalone
Which version of your homematic backend are you running?
No response
What hardware are you running for your system?
Homeassistant RPI3-Arm64 bit installation
Which config details do you use

[ ] Username and password
[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[ ] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

while trying to add the Integration

This is a problem with Home Assistant before the integration starts. Since I also can't reproduce the problem myself, I can't help.
Maybe a restart of HA is helpful.


[BUG] Pearl Module Preset "stop" action does not work on Recorder/Publisher

Describe the bug:
When using the latest Companion build with an Original Pearl the preset companion buttons on recorder or publisher to  trigger the "start" action work fine but fail on the "stop" action.
The companion feedback stays true to the hardware state, but the action does not send the correct information to the hardware to stop recording or streaming. After "unlatching" the button to stop recording/streaming the red stop icon shows in the top right corner of the button and the instance on the connections tap shows an error.  The debug log shows "21.06.01 12:48:45 instance(PEARL REC A): The was called for a unknow action: 0".
To Reproduce:
Add Preset Recorder/Publisher button for a connected Original Pearl Hardware interface to a button
Click on the button to trigger down action (Start) (works fine to start recording)
Click on the button to trigger up action (Stop) (does not work and sends error to instance when trying to stop recording)
Expected behavior:
The unlatch click of a button should correctly stop the recorder or publisher.
Desktop:
OS: Win10 Pro 21H1 19043.985
Browser: Chrome Version 91.0.4472.77 (Official Build) (64-bit)
Companion Version: (Latest 6/1/21) v2.2.0 (24a2d29d-3352)
Pearl Version: ESP1002 – Epiphan Systems Pearl Rackmount Twin (Original, not Pearl 2)
Pearl Firmware Version: 4.12.01 (50513_1830)
Pearl Hardware Version: CPU Board: D53427RKE (G87790-407) BIOS: 11/05/2014
I can give someone willing to troubleshoot access to our system and pearl if that would help in debugging the issue.  I've reset our APP DATA folder and tried reinstalling and starting from scratch and tried several versions of the beta builds with the same broken "stop" action.  Thank you in advance.

Hi there,
Thanks for the detailed description. If i need more info i'l ask here.

So quick update, i see what's happening, but in kinda lost why.
The unknow action: 0 is wierd because 0 is a valid action.
I'll have to dig deeper.

Thank you @MarcHagen for taking a look.  Let me know if we can help test or provide more information.

Okay yeah i found it, simple bug from my side. Will update the module and get it in the latest release.


Background color selectable

Hi,
Make background color selectable (with an option to depend on the syntax color) :)
Thank you !

Hi
I will :) It is actually already on my todo!
I was trying to find out why the background had sometimes white lines here and there the other day, and to solve it, put all elements' background colors to transparent (except the main one). I found out that the ui looked great even with one background color.

There are some enhancements coming to the background color in the next update. Now practically every color is tinted :) I also switched the editor to be translucent so it blends in better.


v1.1.0 seems to be trying to use incorrect static files

django-json-widget version: v1.1.0
Django version: 3.1
Python version: 3.7
Operating System: Linux

Description
Just upgrade to Django v3.1 and with it, to django-json-version 1.1.0. After I run collectstatic, I get the following two files under my statics directory

dist/jsoneditor.min.css
dist/jsoneditor.min.js

which seems to be the same as version v1.0.1.
The problem is that when running the server, the page fails to load. Looking at the browser console, I can see it is erroring out trying to find dist/jsoneditor.css and dist/jsoneditor.js (see how it is not the .min. version)

What I Did
I didn't do anything different, so unless something changed in the way Django 3.1 works, this may be a problem with the new v1.1.0 version

Seems like the bug was introduced here:
https://github.com/jmrivas86/django-json-widget/commit/1e7b0470727a567aa60d1459853423bdb4d6c75c#diff-c92ce623c95bf852173e45c7aa3fdbecb97463b16a1a9a6834a2d9edd87e5a8dR11
See how the defaults are no longer .min files

Would be nice to add the optional (not so optional with this bug) settings to the README:
JSON_EDITOR_JS = 'https://cdnjs.cloudflare.com/ajax/libs/jsoneditor/9.1.9/jsoneditor.min.js'
JSON_EDITOR_CSS = 'https://cdnjs.cloudflare.com/ajax/libs/jsoneditor/9.1.9/jsoneditor.min.css'

Hello. I found the same problem. Thanks for reporting it @dkarchmer. I revert it back to version 1.0.1.

We're having the same issue

same issue 😢

This is fixed in version 1.1.1 - https://github.com/jmrivas86/django-json-widget/releases/tag/v1.1.1

Fixed in version 1.1.1 by @StevenMapes 👏  in https://github.com/jmrivas86/django-json-widget/pull/52


Overly complex instructions could benefit from a link to a simpler way

This page has a convoluted approach which may serve some more general cases, but there is a simpler way to just get a shell in a K8s container. This is not specific to AKS, and is documented here:
https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/
The only missing piece to that is the need to know the name of the running pod, which can be acquired from the kubectl get pods command.

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

ID: 3b81a147-db1c-b92f-88d1-6dd0991a72fe
Version Independent ID: f5a2c949-498f-5848-d89c-031d1a757120
Content: SSH into Azure Kubernetes Service (AKS) cluster nodes - Azure Kubernetes Service
Content Source: articles/aks/ssh.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@rspiewak47 We are checking this and we will get back to you.

We appreciate your valuable feedback. Since this document is specific to AKS, we would leave the doc as is for now. However, this GitHub issue will stay with the document for others to reference. As we get similar feedback from other customers, we would consider updating the document with your feedback to simplify it.
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

I get that this is AKS specific. But you shoukd acknowledge that K8s has platform independent features that may be useful to Azure users.
-------- Original message --------From: Karishma Tiwari - MSFT<EMAIL_ADDRESS>Date: 12/11/20  7:48 PM  (GMT-05:00) To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: rspiewak47<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Overly complex instructions could
benefit from a link to a simpler way (#67424)
We appreciate your valuable feedback. Since this document is specific to AKS, we would leave the doc as is for now. However, this GitHub issue will stay with the document for others to reference. As we get similar feedback from other customers, we would consider updating the document with your feedback to simplify it.
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.


Create better description of quarantine notification settings

https://docs.microsoft.com/microsoft-365/security/office-365-security/quarantine-policies#configure-global-quarantine-notification-settings-in-the-microsoft-365-defender-portal
I read the documentation and tried to configure the quarantine notification settings but it is poorly described.
Could you please improve the description?
What does the setting "Default" for language mean?

You can select multiple languages by clicking Add after each one.

This is not correct, you can only configure a maximum of three languages.
When you configure the same sender name for different languages you the message:

It is labeled as a warning and uses the term "should".
However you cannot continue without changing the name.
So this is not a warning but an error and it should use the term "must" instead of should.

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

ID: faf5c5df-c3ab-8448-aef0-af05977db9b9
Version Independent ID: adade895-f42b-1029-9948-5ddb5b038257
Content: Quarantine policies - Office 365
Content Source: microsoft-365/security/office-365-security/quarantine-policies.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@joergrenn, thanks for the feedback. It appears that the UI has changed in that Global Settings flyout of quarantine policies. I updated it to match currently reality, and clarified it based on your suggestions. See the pull request linked to this issue.
I'll notify the product team about the string change from "should" to "must" in that dialog box.
After you've verified that you like the changes (after 4:00 PM F 5/6 GMT-7), feel free to close this issue.

@joergrenn Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Hello @yogkumgit,
thanks for providing the update.
However even with the update it is still not clear what means "Default" Language.
The text now says:

Select the language from the Choose language box. The default value is Default, which means English.

However there is the default setting and also an English setting. If default means English why are there two settings?
Also they are not the same. If I enter something in default it does not show up in the English setting:

Also I can Add English and Default together. What is the usecase for this if default means English?

best regards
Joerg

@joergrenn, unless you can prove to the contrary, I still contend that English and Default are equivalent. It's just a quirk of the UI design that you can select both.

Hello @chrisda ,
its not just that you can select both, as you can see in my screenshots. The text that you can enter in Display Name and Disclaimer it stored differently.
If it were just the UI, it would still store the text in the same place an show the same in both selections.
But I also don't understand why we have to guess about it or I have to proof something.
You are a Microsoft employee and this is a Microsoft product, so it should be possible to find a developer that can look into the design documentation or even the source code and then we know how its implemented.

@joergrenn, my apologies. I did not mean to imply that you need to prove anything. I just thought you might have the results of your testing that would show what's actually happening.

According to old correspondence that I found but apparently never implemented, Default means the default language of the Microsoft 365 organization. I'll update the topic accordingly.
But, it doesn't really matter what the Default language value is, because, as you've described, you can still pick Default + two other languages, one of which might also be the Default, so why do that?

Regarding the Warning and should vs. must, I'd swear that I either brought this up or it was shown to me about the same time I corrected the 'max 3 languages' thing.

I'll seek clarification on these issues and report my findings.

@chrisda, I am also sorry I apparently took the reply the wrong way.

Default means the default language of the Microsoft 365 organization.

That definitively makes more sense then: default equals English.
But I still don't really understand what this default setting is for, because I agree with you that it makes little sense to select default and another language which might be the same as the default.


Factorized use of sine and cosine functions by using FastMath.sinCos().

Fixes #108

The compilation error is due to a change I pushed on master before this PR.
I have fixed this problem now, so it should compile properly now.
Could you recheck it against current master? If it works, +1 for the merge.

Everything is green. I merge the branch!


Missing kernel feature - debugging processes

Hi,

The Apple Swift REPL cannot run on BashOnWindows because of a missing kernel feature - I believe the missing feature is the one associated with debugging processes.
Expected results:

$ swift
  >

Actual results:

$ swift
  error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8

Windows Build number: 14393.0
How to reproduce: Install the latest swift snapshot for Ubuntu 14.04 on https://swift.org with required dependencies (clang and libicu-dev), add swift to path, then try to run swift. Compiling a file does work correctly though, but not the REPL.

Thanks for reporting the issue.  Can you please collect an strace of the failing process so we can see why the application is failing?

#555 dup

@therealkenc Indeed, I believe it is the same issue. You can mark it as duplicate.

@stehufntdev providing an strace and a couple very verbose lldb logs, since lldb produces the same error.
Hopefully this will help determine if this is the same problem as what is occurring in #555 or is something different. As a side note gdb does work for the same circumstances.
If you need anything else, let me know. I'm on windows build14393.82

lldb -- jsc testscript1.js
(lldb) target create "jsc"
Current executable set to 'jsc' (x86_64).
(lldb) settings set -- target.run-args  "testscript1.js"
(lldb) log enable -vtgT -f lldb_log.txt lldb all
(lldb) log enable -vtgT -f lldb_gdb_remote_log.txt gdb-remote all
(lldb) process launch
error: process launch failed: 'A' packet returned an error: 8
(lldb) quit

Here are the logs it generated:
lldb_gdb_remote_log.txt
lldb_log.txt
Excerpt from lldb_gdb-remote_log:
1472252855.132365000 GDBRemoteCommunication::CheckForPacket adding 7 bytes: $E08#ad
1472252855.132365000 <   7> read packet: $E08#ad
1472252855.132365000 failed to connect to debugserver: 'A' packet returned an error: 8
1472252855.134366000 ProcessGDBRemote::MonitorDebugserverProcess (baton=0xc79720, pid=8327, signo=2 (0x2), exit_status=-1)

Strace (similiar workflow, sans lldb logging)

strace -o strace.log lldb -- jsc testscript1.js
(lldb) target create "jsc"
Current executable set to 'jsc' (x86_64).
(lldb) settings set -- target.run-args  "testscript1.js"
(lldb) process launch
error: process launch failed: 'A' packet returned an error: 8
(lldb) quit

Here is the strace log:
strace_log.txt

Strace(lldb-server loging)
strace -o lldb-server-log.txt lldb-server platform --listen *:1234

lldb
(lldb) platform select linux-remote
error: unable to find a plug-in for the platform named "linux-remote"
(lldb) platform select remote-linux
Platform: remote-linux
Connected: no
(lldb) target create jsc
Current executable set to 'jsc' (x86_64).
(lldb) process launch testscript1.js
error: process launch failed: Lost debug server connection
(lldb) platform connect connect://<IP_ADDRESS>:1234
Platform: remote-linux
Triple: x86_64-*-linux
OS Version: 3.4.0 (3.4.0+)
Kernel: #1 PREEMPT Thu Aug 1 17:06:05 CST 2013
Hostname: MACBOOKAIR
Connected: yes
WorkingDir: /home/gl/remote-debug-logs
(lldb) target create jsc
Current executable set to 'jsc' (x86_64).
(lldb) process launch testscript1.js
error: process launch failed: 'A' packet returned an error: 8
(lldb) quit

Strace log for lldb-server http://s000.tinyupload.com/index.php?file_id=56190828631857628254 (tinyupload links since github didn't let me upload zip file of it)

The failing syscall appears to be:
ptrace(PTRACE_TRACEME, 0, 0, 0) = -1 EPERM (Operation not permitted)

I've the same issue on Windows 10, with Ubuntu 14.04.5 LTS

Marking it duplicate as per the above comments.

Note this issue is PTRACE_TRACEME which is still outstanding (unless something changed). #1692 is PTRACE_OLDSETOPTIONS. The #1692 application (UML) will also eventually fail on PTRACE_TRACEME, but it is marked as fixinbound because the other (easier) ptrace() option was fixed.

I've the same issue on Windows 10, with Ubuntu 18.04 swift 5.0.1

Still having this issue, it would be nice to see if something could be done about it

Any update on this?

This was fixed with WSL2 using a virtual machine instead of rewriting system calls.

Hi, @jhoareau !
Do you have a link I can follow to update this? O native Windows it does nothing. It runs and returns to the command prompt. On Ubuntu 20.04 on WSL2 it hangs.


Touchstart and Touchend Support

Hey there!
First off, fantastic library, we'd been using this for a project and it was working great!
We did notice that touch events were all janky (fire up Chrome Web Dev and go to mobile dev mode using, say, an iPad). Specifically, X and Y coordinates were not getting returned properly because those properties exist in the .touches collection of a touchstart. As a result, the elementBehindCursor would always resolve to our leftmost div on our site (the X and Y coords from getCoords would evaluate as nulls).
I added some code that seems to make it work, and also went ahead and added what looked to be a missing dependency in the package.json (jshint-stylish).
This gets drag-n-drop working for touch devices from what I can tell. Let me know if this code works for you, or if you'd like to discuss further and refine it a bit.
Many thanks again for the great work on Dragular, looking forward to seeing future releases!
~ Eric Nograles

I am sorry I was few days away finishing some projects. I didnt have time for dragular. But now I am back, thanks for solving issue. Could you update your PR, so I can merge it? Thanks ;)

Hi there, thanks for the reply! Certainly, I'll send it over when I've got the conflict resolved.

Should be all set! You may need to rebuild dragular.min.js with the small change I dropped into getCoord, but otherwise, we're green.

Ok, thank you very much.. I will merge it soon. :)
On Sep 25, 2015 12:14 PM, "Eric Nograles"<EMAIL_ADDRESS>wrote:

Should be all set! You may need to rebuild dragular.min.js with the small
change I dropped into getCoord, but otherwise, we're green.
—
Reply to this email directly or view it on GitHub
https://github.com/luckylooke/dragular/pull/41#issuecomment-143181124.

MErged.. I will make release later.. thanks for contribution ;)

Hi there! We have problem with your change in getCoord.. It fails on touch devices at  if (host.type.indexOf('touch') < 0) { with error Uncaught TypeError: Cannot read property 'indexOf' of undefined. I cannot find 'type' property in (Touch event object)[https://developer.mozilla.org/en-US/docs/Web/API/TouchEvent]. So I think you were expecting some other object there. Could you look at it? Thanks

I have made quick fix:
if (!host.type || host.type.indexOf('touch') < 0) {
Please check if it didn't brake your usecase, thanks!


⚠ Bofrost.be has degraded performance

In 37412d1, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1014 ms

Resolved: Bofrost.be performance has improved in 5798ace after 2 hours, 7 minutes.


Allowing more flexibility for developer assertions

When using the library the following I thought of the following change.
Problem:
Currently the assertion to check if the data is correct is within the table_mocks.py when for a Mock you run assert_equal. When my assertion is not equal I don't receive more information about why they don't match.
Proposal:
It would be better to do the following:

Separate the assertion from the generation of the query and data.

Currently assert_equal also has responsibility over running _generate_query and _get_results. I see benefits from separating these. We could have a method called generate_results so that we can access the query and result directly from the Mock object.

Separate the cleaning logic in _assert_result and move it generate_results this way this usage could look like this:

# assuming we've successfully ran TableMock.from_mocks() we currently do

TableMock.assert_equal(expected_dict)

# I propose the following which allows de the developer to use other assertion tools
res_dict = TableMock.generate_result()

query = TableMock._sql_mock_data.last_query # I can inspect the query even before it fails if I want to

unittest.TestCase.assertDictEqual(res_dict, expected_dict) # I do my own assertion with whatever library I chose

In this case the more verbose unittest assertion solves my problem.
Conclusion
In a way I think BaseTableMock does not need an assert method within the object, you can expose the data and let the developers write their own assertion statement.

Good points. Thanks for flagging that.
I was wondering whether you set things up using the recommended Pytest setup including pytest-icdiff? This should already show a rich comparison of what is not equal in a git diff way.
Currently, the intended behavior is that the used query should be printed out when the assertion fails. Did this not happen to you?
I like the idea of being able to manually call generate_results if needed. However, your proposed solution adds some additional verbosity (at least 1 additional line needed to do the assertion). So I would love to keep the possibility to call assert_equal but maybe provide the feature to be able to only get the results and do something custom with them.

was wondering whether you set things up using the recommended Pytest setup including pytest-icdiff? This should already show a rich comparison of what is not equal in a git diff way.

I did not thanks, this would fix my main issue actually.

Currently, the intended behavior is that the used query should be printed out when the assertion fails. Did this not happen to you?

Yeah this works thanks! I guess the issue is that I have to copy the query and run it separately to get the answer. But as you said installing pytest-icdiff gives me better assertion error messages.

I like the idea of being able to manually call generate_results if needed. However, your proposed solution adds some additional verbosity (at least 1 additional line needed to do the assertion). So I would love to keep the possibility to call assert_equal but maybe provide the feature to be able to only get the results and do something custom with them.

The pattern I see in other libaries is that testing methods are not part of the main object you are working with, for example in pandas testing is in its own module:
https://pandas.pydata.org/docs/reference/testing.html


Remove incorrect statement about the disabled attribute on

You can disable every form element within a form with the disabled attribute on the <form>.

I really want to be mistaken, because this would be a very useful feature! But I don't believe it's true. I can't find anything about this on MDN Web Docs, and adding the disabled attribute to a <form> does nothing on any browser in my testing.
The disabled attribute on a <fieldset> does disable all descendant form controls – perhaps that's where the mixup has come from.

Perhaps, though in the context of that section which is specifically about the <form> element, it might not make sense to talk about <fieldset> right there.


[GOBBLIN-1602] Change hive table location and partition check to validate using FS r…

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

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

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

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

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

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

Codecov Report

Merging #3459 (c48b2c7) into master (0213b1e) will decrease coverage by 3.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3459      +/-   ##
============================================
- Coverage     46.63%   43.46%   -3.18%
+ Complexity    10342     2032    -8310
============================================
  Files          2074      404    -1670
  Lines         80962    17382   -63580
  Branches       9031     2124    -6907
============================================
- Hits          37759     7555   -30204
+ Misses        39728     8991   -30737
+ Partials       3475      836    -2639

Impacted Files
Coverage Δ

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0.00%> (-7.15%)
:arrow_down:

...in/java/org/apache/gobblin/cluster/HelixUtils.java
28.26% <0.00%> (-5.08%)
:arrow_down:

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
63.46% <0.00%> (-0.33%)
:arrow_down:

...ata/management/copy/hive/HiveCopyEntityHelper.java

...ata/management/copy/hive/HivePartitionFileSet.java

...anagement/copy/hive/UnpartitionedTableFileSet.java

...extractor/extract/google/GoogleDriveExtractor.java

.../apache/gobblin/crypto/EncryptionConfigParser.java

.../compaction/verify/CompactionWatermarkChecker.java

.../kafka/client/AbstractBaseKafkaConsumerClient.java

... and 1665 more

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 0213b1e...c48b2c7. Read the comment docs.

Thanks for the PR.
Please also add the description and other fields in the PR template.


Hooking exports

Hi,
is it even possible to hook exports of an library (EAT)? Or set an hook on a RVA of a dll?
Regads
Martin

@maddin123 yes to IAT / EAT hooking but EasyHook does not provide these features.


std.conv.emplace segfaults for nested types

mkline.on.d (@mrkline) reported this on 2015-04-03T08:27:09Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=14402
CC List

aliloko
bugzilla (@WalterBright)
mkline.on.d (@mrkline)
nick (@ntrel)
r9shackleford

Description
I came across this while doing work on std.typecons.Unique (see https://github.com/D-Programming-Language/phobos/pull/3139). Any class that accesses a local context seems to segfault when emplaced. A minimal test case follows:

import core.stdc.stdlib : malloc, free;
import std.conv : emplace;
import std.traits : classInstanceAlignment;

void main()
{
    int created;
    int destroyed;
    class Foo {
        this() { ++created; }
        ~this() { ++destroyed; }
    }

    immutable size_t size = __traits(classInstanceSize, Foo);

    void* m = malloc(size);
    assert(m);

    Foo f = emplace!Foo(m[0 .. size]);
    assert(created == 1);

    f.destroy();
    free(m);
    assert(destroyed == 1);
}

The problem doesn't seem to be the amount of memory I am allocating, given that it makes it past the testEmplaceChunk call in emplace. A stack trace from GDB is as follows:

Program received signal SIGSEGV, Segmentation fault.
0x000000000042afd4 in wat.main().Foo.this() (this=0x66d450) at wat.d:10
10	        this() { ++created; }
(gdb) where
#0  0x000000000042afd4 in wat.main().Foo.this() (this=0x66d450) at wat.d:10
#1  0x000000000042b167 in std.conv.emplace!(wat.main().Foo).emplace(void[]) (chunk=...)
    at /home/mrkline/src/dlang/phobos/std/conv.d:5005
#2  0x000000000042af76 in D main () at wat.d:19

where the relevant line in conv.d is
result.__ctor(args);

This was seen on 2.067 and the current master for dmd and phobos as of 2015-04-03 01:20 PST.

aliloko commented on 2016-10-14T21:22:04Z
Also rediscovered this bug.

mkline.on.d (@mrkline) commented on 2015-04-05T22:50:31Z
I just noticed that if you try to `new` a context-aware class or struct outside that context, you get a nice compiler warning indicating that you cannot do so. Can we, via template magic or something similar, issue a similar error when trying to emplace one?

nick (@ntrel) commented on 2017-05-08T12:54:15Z
(In reply to Matt Kline from comment #1)
> Can we, via template magic or something similar, issue a
> similar error when trying to emplace one?

I think so, I'm working on a PR. Basically the initializer args have to contain a type that has a usable context pointer. The remaining case is:

S s;
emplace(&s, S.init);

In solving that, I think disallowing rvalue initializers is too strict (as they could have a valid context pointer). Perhaps this can be detected at runtime instead.

nick (@ntrel) commented on 2017-05-08T15:14:13Z
https://github.com/dlang/phobos/pull/5379


How to setup composer with vercel-php

Question
I'm trying to deploy a very basic PHP project to Vercel using vercel-php.
The project relies on some composer dependencies - grpc/grpc and google/cloud-firestore
How exactly do I setup my project for these composer dependencies to be installed correctly and working.
I have tried following the example here - https://github.com/juicyfx/vercel-examples/tree/master/php-composer, although it's slightly unclear as to how exactly to achieve this.
Any advice greatly appreciated.

Hi All,
Some tinkering later and I seem to have cracked it -
the best way I have found is to have your composer.json in the root of your project, and in the file in your api folder (e.g. /api/index.js) do a require from $_SERVER["DOCUMENT_ROOT"] . "/vendor/autoload.php"


net.Listener support

Hi,
Is there a chance to have support of net.Listener? I wanted to try it out and I got the following error:
cannot use lis (type quic.Listener) as type net.Listener in argument to grpcServer.Serve:
    quic.Listener does not implement net.Listener (wrong type for Accept method)
        have Accept() (quic.Session, error)
        want Accept() (net.Conn, error)

The concepts behind quic (e.g. multiple [uni-directional] streams over one connection) don't map well to the current Go stdlib types, so we don't implement them exactly. Most of the API is similar though wherever possible.
In the end most people will likely just use QUIC as a drop-in replacement for HTTP, and that fortunately easy enough (look at the h2quic package).

I think the assertion they don't map well was premature. only pieces that would need to be special cased is the dialer and listener.
just repeatedly 'dial' a server to get mulitple conn's and each conn would have a duplex uni directional stream (which is what standard tcp connections have anyways)....
even if such an interface doesn't grant the full power of quic it'd still be handy for interop.


No get danger_head from git.commits in github actions

Report
What did you do?
Run danger pr <URL> and run in github actions
What did you expect to happen?
Message is not danger_head. I expect to output danger_head.
I've done the same thing before and it came back with a danger_head.
Refs: #1129
What happened instead?
Is this correct?
I am curious whether EnvironmentManager.danger_head_branch applies in running Danger.
Your Environment

Which CI are you running on?

Local and github actions

Are you running the latest version of Danger?

$ danger --version
8.2.1

What is your Dangerfile?

git.commits.to_a.each do |commit|
  message(commit.name)
end

In local
Messages:
- [ ] remotes/origin/feature/a
- [ ] remotes/origin/feature/a~1
- [ ] remotes/origin/feature/a~2
- [ ] remotes/origin/feature/a~3

GitHub Actions

I'm not sure I understand what you're asking (though I think danger pr isn't for running on CI I believe)

Sorry, I rewrote title and description. It occurs not only in CI.
I just wonder if it's no problem as Danger, because it has been behaving differently.


Top menu nav color and shadow

https://github.com/wintercms/wn-tailwindui-plugin/blob/cceeac90389a00e262d8af68f85c4fb11fbcbd1c/skins/tailwindui/layouts/_menu-top.php#L13-L17
1 - Why switch to a white background?
I find the bar not contrasting enough in the overall interface.
I would prefer even a light color:

2 - For me, the shadow is not visible.
For it to be visible, a relative position and z-index must be added to the .layout-topmenu element.
Also I would have chosen a wider shadow (shadow-md).
Actual - invisible shadow:

With shadow visible :

With shadow-md visible :

I would be pleased to hear your thoughts on this.

@damsfx I would agree with those assessments. As far as colour goes I actually want this plugin to have a light theme and a dark theme with the colour matching between the top bar and the side bar for each version, but for now fixing the shadow to show (the size of it seems fine to me without further changes for now).

I personally think the top bar serves no actual purpose when the menu is on the left. It breaks the otherwise great look of the backend layout.

@mjauvin it doesn't serve much of a purpose yet but it will. The plan is to have a backend-wide search bar in the top left of it as well as a few more additions on the right to the quick actions menu like a quick create button and notification management

I'm having a play around with this skin for a client at the moment. I can see the rationale for that user bar based on what @LukeTowers wants to do with it going forward, but to offer a counterpoint, the reason that some people prefer side menus (including myself) is the maximise the amount of vertical space for the actual page or function being used, and to take advantage of the amount of width modern monitors have.
Unfortunately, the user bar negates that benefit because it takes up the same amount of space as it would having the main nav at the top, whilst also decreasing the amount of space horizontally too.
See the following:
Top nav

Side nav

Effectively, the usable viewport for the Backend itself is shrunk a little bit if someone uses the side nav option.
Ideally, it would be nice to have the user functions condensed into the side nav, but I can understand if that might be difficult.

What I'd like to have is for the side menu layout to have the ability to collapse down to the icon only mode with the press of a button like a mobile menu and then re-show the full size version when hovering over it or clicking the button again.


Add newtypes for indices

There are different index spaces, and it would be awesome to have newtypes for each kind of index, to help folks write more correct code.
Would have been awesome if creating bugs like https://github.com/fitzgen/svelte/issues/24 weren't possible (unless you incorrectly construct an invalid index).
Ideally also have (fallible?) conversions from global indices into function indices, etc.

Yeah, that's sounds cool, here are some problems I encountered when thought about it

Sections publish Vec in it's API to allow the user to manipulate the entries. Users still have to use the raw indices to manipulate vec.
There is no way for users to get function by funcidx in parity-wasm. However, it's used everywhere to index entities.

These are solvable, for (1) we can publish some generaly useful subset of vector operations that would be indexable with newtypes and for (2) we can either provide some utilities which will return FuncOrImport if given functions (and/or code) and imports sections or leave it up to the user.
But my personal opinion is that wasm code manipulation analysis requires more high-level API than that provided by parity-wasm.


jupyter_ascending module not found in python even though installed with pip

I have always followed the instructions in the README.md and they have always worked for me but suddenly they don't:
conda activate env_name
pip install notebook
pip install jupyter_ascending

All work without error but then when I try:
$ python -m jupyter nbextension    install jupyter_ascending --sys-prefix --py
Traceback (most recent call last):
  File "/usr/bin/jupyter-nbextension", line 33, in <module>
    sys.exit(load_entry_point('notebook==6.4.8', 'console_scripts', 'jupyter-nbextension')())
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 264, in launch_instance
    return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line 846, in launch_instance
    app.start()
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 980, in start
    super().start()
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 253, in start
    self.subapp.start()
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 708, in start
    self.install_extensions()
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 679, in install_extensions
    full_dests = install(self.extra_args[0],
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 203, in install_nbextension_python
    m, nbexts = _get_nbextension_metadata(module)
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 1114, in _get_nbextension_metadata
    m = import_item(module)
  File "/usr/lib/python3/dist-packages/traitlets/utils/importstring.py", line 38, in import_item
    return __import__(parts[0])
ModuleNotFoundError: No module named 'jupyter_ascending'

Any reason why this would have stopped working?

I got the same problem.

Following information from https://stackoverflow.com/questions/76893872/modulenotfounderror-no-module-named-notebook-base-when-installing-nbextension I was able to solve the problem.
pip install --upgrade notebook==6.4.12
So it seems that jupyter-ascending is not compatible with the most recent versions of notebook. Is there plans to update this?


ForwardRef Error for "results_group" field in AssessmentResults

Describe the bug
When instantiating an AssessmentResults object the following error is shown:
Exception has occurred: ConfigError
field "results_group" not yet prepared so type is still a ForwardRef, you might need to call AssessmentResults.update_forward_refs().

To Reproduce
Steps to reproduce the behavior:

import trestle.oscal.assessment_results as assessment_results
Try write:  ar = assessment_results.AssessmentResults(      uuid=str(uuid4()), metadata=m, import_ap=ap, objectives=obj, results_group=results  ) (where all other parameters are valid trestle objects)

Expected behavior
ar should not return an error and generate a trestle object
Additional context
Using compliance-trestle==0.2.0

@fsuits - Can you have a look at this?


[5.1][Sema] Treat static methods as always applying their curried self param

Explanation: Currently areConservativelyCompatibleArgumentLabels treats a reference to a declaration as not having its curried self parameter applied if the choice doesn't have a base type. However this isn't correct for operators defined as static methods, which have their Self.Type parameter applied but their choice doesn't have a base type.
This PR changes areConservativelyCompatibleArgumentLabels to always treat static methods as having their Self.Type parameters applied, as there's currently no way to form an unapplied curried reference to them.

Scope: Resolves a 5.1 regression.

SR Issue: SR-10843.

Risk: Low, the fix is fairly narrow.

Testing: Added a regression test.

Reviewers: @slavapestov @xedin.

Ping @slavapestov @xedin

@swift-ci please test and merge

Test failures look unrelated as far as I can tell

@swift-ci please test and merge

Unrelated build failures this time... hopefully third time lucky!

@swift-ci please test and merge

Thanks @xedin!

No problem!

Thank you for fixing this!


Does Luckysheet support drop downs in a Cell?

Is there a way to have a drop down inside a Cell?
If it's not supported, is it possible to do this by inserting some html in a cell?

You can use cellDragStop hook


Changed examples to javascript

I think it's ok for the main codebase to be in CoffeeScript but the majority of people using this module are going to be writing javascript so it makes more sense for the examples to be Javascript so they can understand them.

:+1: for this, I was wondering about the same.
No real problem to understand it, tho (especially with ES6 syntax being a bit more alike)


Rotativa.AspNetCore 1.0.6 - ViewData is null in view

Hallo.
I'm trying your project: Rotativa.AspNetCore.Demo.
(AspNetCore 2)

Rotativa.AspNetCore.Demo.Controllers/HomeController
public IActionResult About()
{
ViewData["Message"] = "Your application description page.";
return new ViewAsPdf();
}

Rotativa.AspNetCore.Demo.Views/Home/About.cshtml
...
<h3>@ViewData["Message"]</h3>
...

Rotativa create pdf file, but:
@ViewData["Message"] is null.  The string is empty
Thank you for your response

@morvay  @ViewData["Message"] null issue has been resolved take latest pull.

And what is the answer?

I need ViewBag o ViewData?????HelpMeeeeeeeeee en Rotativo.IO

This is not resolved yet :(

I have the same problem, you found a solution


basic EC features

Hey @KennethNielsen and @kkrempl ,
Here I've flushed out the ECMeasurement class and made a CyclicVoltammagram class that adds a few features. The main focus of this PR is on how to make sure the essential data series (potential, current, and selector in this case, see class docstring to ECMeasurement) are always available by a standard name, even though they might be saved differently in different files or not present in all appended files. It proved slightly hair-pulling, even with the relative strengths of ixdat's structure.
The "front-panel" (user-facing) scripts I've been developing this with are development_scripts/ec_tools_dev.py and development_scripts/cv_tools_dev.py. They show how easy it is to manipulate and visualize a complex looped experiment with OCP, CVA and CP (ask me for the data, shared some of ec_tools_dev.py's plots in Slack yesterday).
The inside is a bit of a mess - I've used slightly different approaches to build and cache different variables, when it would be much better to have a general approach. One of @KennethNielsen 's ideas (see Slack) was to make it the Reader's responsibility to rename to the standard names and make place-holders for missing essential data. My instinct is that it is more natural to give the Technique Measurement class that responsibility, and only require the Reader to provide static lists of what things are called in the files it reads, but hope we can find the best solution while discussing the code.
It would also be nice to move a lot of the code that solves general problems to a build module or something to reduce the clutter in the technique class.
There are TODO's and FIXME's all over the code with problems and (suboptimal) ideas to improve, so especially loook at those. Hope you we can find better solutions to these problems!
Thanks!

This has been superceded by #11 . Closing.


Error when categories receive a multidimensional array

Description
When the categories receive a multidimensional array, the xaxis show duplicate data on two lines.
On the previous versions (like 3.34.0) this was working, but when i update to last version this stopped working well.
Hope you can help me with that.

Steps to Reproduce

Exemple: let categories = [
["Ter", "01/02"],
["Qua", "02/02"]
];

Expected Behavior

Actual Behavior

Reproduction Link
https://codepen.io/flopes-14/pen/VwQpPzy

I'm also having this problem, I had implemented the chart code last week and this Monday it had this bug, how do I have a link (Direct

I was testing last versions until find the desired version :D
https://www.npmjs.com/package/apexcharts?activeTab=versions

Do you used npm or direct link for html?

or
npm i apexcharts

npm i apexcharts
And i use Vue.js

Released 3.35.3 which fixes this

Thanks


Forced reindex command

On some websites I manage there are pages that are changing rather frequently.
It would be great if there was some command that forces indexing of selected page i.e. npm run reindex <url> even if this page is already known and indexed. While I can do that directly from Search Console, it's very slow.

@phenomen agreed, would be nice to have command to reindex.

I will soon add this feature 😉

I haven't forgotten, it's just that it's a bit more complicated than I thought, because we've totally changed our vision, since we've got the CLI, the command would be gis --urls=https://domain.com/page1,https://domain.com/page2 ? I'm a bit out of ideas...

It would be fine I guess. To make it a bit shorter, you can also use --domain=https://domain.com --url=/page1,/page2,/page3/subpath1

Done in #65


Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (__SwiftValue)

i want filter data when fetching with json,when i send all values app crashes
//1
case retailList(Int,Int)
//2
case .retailList(let cityId, let catId):
struct Filters {
var cityId: Int
var categoryId: Int
}
value["filter"] = Filters(cityId: cityId,categoryId: catId)
//3
case .retailList(let cityId, let catId):
value["filter"] = [{
value["cityId"] = cityId
value["categoryId"] = catId
}]
let request = javaNetworkProvider.request(.retailList(cityId, catId), callbackQueue: Queue, progress: nil, completion: { result in
if let value = result.value {
}

Hey @Ualikhan07, sorry for the late response. I'm trying to understand what actually happened, but I can't seem to connect the dots.
Can you post a code and point out which line crashed your project? Also the crash message would be awesome to have as well. For now I only see some lines of code that I can't really connect; is the value dictionary a dictionary that you pass as your request parameters? If so, you need to be careful when using value["filter"] = Filters(cityId: cityId,categoryId: catId) - this might not be encodable using json & url encoding and that might a culprit for the crash.

@sunshinejr guys I have already found a solution thanks you too much✌😉

@Ualikhan07 awesome! Do you remember what was the issue?

@sunshinejr
case .retailList(let cityId, let categoryId,let pageNumber):
        value["filter"] = ["cityId":cityId,"categoryId":categoryId]
        value["pageNumber"] = pageNumber;
        value["size"] = 10;
        break;

@Ualikhan07 perfect, thanks so much!


Remove -j2 to use less RAM in travis-ci

(whoops hit the return button by accident before typing everything in)
This PR removes the -j2 from cabal new-build in the .travis.yml file. This should make it use less RAM at the expense of a much longer build time.
See #36 for a failed build due to not enough RAM

Well... that's just strange.
The exact same commit built fine from my fork:
https://travis-ci.org/samdoshi/hledger-iadd/builds/442725193
Perhaps it's an issue with your Travis caches?

Hmm. I'm going to close this for now, since it seems that -j2 wasn't the actual problem. I'll debug this later (or wait if it magically fixes itself :-)

No worries, I can't say for definite that removing the -j2 will help. Sometimes (actually most of the time) Travis drives me up the wall.
I have had other projects where switching to -j1 definitely helped, so it might be something to remember for the future.

Thanks, I'll keep that in mind if builds start failing with OOM again.


Add types to errors [WIP]

Related with https://github.com/CartoDB/carto-vl/issues/1309 and https://github.com/CartoDB/carto-vl/issues/743
This PR adds a type parameter to our custom errors in order to display better errors from external applications.
This would be a simple example of displaying the errors in HTML:

try {
    init()
} catch (e) {
    const error$ = document.getElementById('error-container');
    const errors$ = error$.getElementsByTagName('span');

    errors$[0].innerHTML = e.name;
    errors$[1].innerHTML = e.type;
    errors$[2].innerHTML = e.message;
}

Could you please paste here a small example of the try / catch you're using this for?

This would be a simple example of displaying the errors in HTML:

try {
    init()
} catch (e) {
    const error$ = document.getElementById('error-container');
    const errors$ = error$.getElementsByTagName('span');

    errors$[0].innerHTML = e.name;
    errors$[1].innerHTML = e.type;
    errors$[2].innerHTML = e.message;
}

I think that right now it's good enough to the error types in the reference. If we add a guide, it'd be hard to maintain, and error handling is something that has to be handled from a

I think that right now it's good enough to have the error types in the reference. If we'd add a guide, in mi opinion it'd be hard to maintain, and error handling is something that's usually handled from a developer perspective, so I don't think we need to explain "How to handle errors".
Maybe we could add a link to the reference from one of the guides, how does it sound?


KAFKA-13374: update doc to allow read from leader/followers

After KIP-392, we allow consumers to fetch data from leader or followers. Update the doc.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mumrah @hachikuji , please take a look at the 1 line change PR. Thank you.

@mumrah @hachikuji @dajac , please take a look at the 1 line change PR. Thank you.

@hachikuji @mimaison , could you help check this 1 line change PR. Thanks.

@showuon Can you also open a PR against https://github.com/apache/kafka-site? Otherwise this will only be fixed when we release 3.2.0. Thanks


keyerror: Using your own configuration

Hello,
Here my second issue i have found.
regarding: http://serpscrap.readthedocs.io/en/latest/configuration.html
i can use own configuration. This is not working for me. I get error:
KeyError: 'executable_path'
i have solved this by adding a executable path, but then i get other keyerrors.
For the moment i have set all options so that there are no more keyerrors. But now i get:
scrapcore.scraper.selenium - ERROR - Message: Service /home/ubuntu/workspace/wp-content/themes/SerpScrap/phantomjs/phantomjs-2.1.1-linux-x86_64/bin/phantomjs unexpectedly exited. Status code was: 0
Exception in thread [google]SelScrape
So what can i do?
regards,
Toby.

Not a direct answer to your question, but since phantomjs developement has been discontinued. I'd rather use chrome with its headless feature.
I hope this workaround can solve your problem.


try_files functionality like nginx

try_files functionality like it in nginx to support react

A single sentence about a feature in some other server I don't know about isn't helpful. Please describe in detail the feature you're twisting l requesting.

in react, access index page, like http://localhost/index.html, when click the menu and rout to another page like /mgt/supplierList, if I click the fresh button of the browser, 404 exists because the server side has no /mgt/supplierList, however, nginx has the try_files directive to solve this problem like below:
location / {
root /home/sidney/html;
index index.html;
try_files $uri /index.html;
}
if the uri not exists in server side, so redirect to /index.html

spring.cloud.gateway.routes[13].id=index2
spring.cloud.gateway.routes[13].uri=forward:///mgt/index.html
spring.cloud.gateway.routes[13].predicates[0]=Path=/mgt
these lines do the thing for try_files, no need to implement now, thanks.


refactor: Force tests onto v3 endpoint, set up test utils, fix test-core-sdk.js

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary
This is the first PR in a larger effort to break up https://github.com/mParticle/mparticle-web-sdk/pull/507 into more bite sized pieces. That PR has been approved, but since PR 507 touches all test files, it constantly needed to be rebased.  To avoid this, rather than remove the V2 path, which all tests depend on, I will update all tests to be on the V3 path and then update a few test files in each PR.  This PR starts with refactoring a lot of the test-utils functions (identical to the changes here).  In order to confirm these are all working, I am refactoring tests-core-sdk.js first.
Each subsequent PR will uncomment a few test/src/ files, until all are uncommented.  Then a final PR will remove the V2 code path.
Testing Plan

[x] Was this tested locally? If not, explain why.
{explain how this has been tested, and what, if any, additional testing should be done}

Reference Issue (For mParticle employees only.  Ignore if you are an outside contributor)

Closes https://go.mparticle.com/work/SQDSDKS-5341

LGTM. My only gripe is that I would like us to replace var with const but I agree that it is out of scope at this point.


Removing AppEngine restriction on Java version.

AppEngine uses Java 8 now.

Please update the description and name of the PR.

AppEngine restriction on Java version has been removed and replaced with an SecurityException check when trying to rename the thread or set it as a daemon thread.

/cc @rghetia may be related to the recent AppEngine issue.

thanks @songy23 . This issue doesn't fix #1954.


Adding support for outer/cross apply

This PR adds apply, outer_apply and cross_apply to mssql flavor select.

Can you please tell me when its planned to be made available. I really need this...

Any news on this? I understand this is open source, and you don't have all the time in the world for this, but that's what PR's are for...


The application start and give this bad result

The application after first two steps has a bad result , see the video .
The output is :
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 0
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 1
[SDK] LogEOSAuth | FAccountPortalBrowserManager::completeScopeConsentLogin: Received
[SDK] LogEOSAuth | FAccountPortalBrowserManager::FAccountPortalBrowserStateData::Finish: [Login] Finishing with result: EOS_Success
[SDK] LogEOSAuth | LaunchAccountPortalWithOverlay: Overlay returned success
[SDK] LogEOSAuth | UserAuthGenerated: Account Portal overlay succeeded without an auth code; falling back to continuation token
[SDK] LogEOSOverlay | Closing browser [InstanceId=xxxxxx, BrowserId=28, TabId=0]
[SDK] LogEOS | Error response received from backend. ServiceName=[OAuth], OperationName=[TokenGrantv2], Url=[<Redacted>], HttpStatus=[400], ErrorCode=[errors.com.epicgames.oauth.corrective_action_required], NumericErrorCode=[18206], ErrorMessage=[Corrective action is required to continue.], CorrId=[EOS----xxxxx]
[SDK] LogEOSAuth | FTokenGrantRequestTask: Received ResultCode: EOS_Auth_CorrectiveActionRequired
[SDK] LogEOSOverlay | Closing active browser [InstanceId=xxxxx, BrowserId=28, TabId=0]
[SDK] LogEOSAuth | UserAuthGenerated: Received FCorrectiveActionRequired ContinuationUrl=<Redacted> ContinuationToken=<Redacted>
[SDK] LogEOSAuth | LaunchAccountPortalWithOverlay: Launching with overlay: <Redacted>
[SDK] LogEOSOverlay | Overlay loading <Redacted> in instance xxx
[SDK] LogEOSOverlay | LoadURL result received. [Success=1, BrowserID=29]
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Load: 0
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 0
[SDK] LogEOSOverlay | Received new texture handle. [Type=0, InstanceId=xxx, BrowserId=29, TabId=0, Previous=0000000000000000, New=00000000C0xxxx]
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 1
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 0
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 1
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 0
[SDK] LogEOSAuth | FAccountPortalBrowserManager::Login: Status: 1

This is how applications try to connect
godot_epic.webm

Have you bootstrapped the executable as mentioned in the readme. Also what is the code you used for the login?

I install the addon . I used your login gdscript https://github.com/3ddelano/eosg-tutorial/blob/main/scenes/Login/Login.gd
because I don't use an .env file I change the EOSCredentials.gd I changed like this:
class_name EOSCredentials

# Put your Epic Games Product details here

const PRODUCT_NAME  = "godot_test_auth"
...

During development use the Dev Auth tool login method. If you want to use account portal login you have to bootstrap the executable as mentioned here bootstrap executable

I read that but I don't understand, is need to create the executable application and then use that bootstrap executable to fix ... what

@catafest this is not an issue with the plugin or the sample. Please read about the bootstrapping process here. https://dev.epicgames.com/docs/epic-account-services/crossplay/redistributable-installer#bootstrapper-tool


Start/Continue Debug with F5

I wanted to set F5 instead of F9 to start debugging, but if I reach a breakpoint and press F5 again,
it wants to start a debugging session on current file again.
Would it be possible to use the default key bindings for debugging?

I found a solution :)
I deactivated all AHK Keybindings, and wrote a new configuration in launch.json:
"configurations": [
    {
      "name": "AutoHotkey launch MenuToolsTest",
      "type": "autohotkey",
      "request": "launch",
      "program": "path to \\script.ahk",
      "args": [],
      "port": "9002-9010",
      "variableCategories": "recommend",
      "useDebugDirective": true,
      "useAutoJumpToError": true,
      "runtime" : "path to \\AutoHotkey64.exe"
    }
]

I found a solution :)
I deactivated all AHK Keybindings, and wrote a new configuration in launch.json:
"configurations": [
    {
      "name": "AutoHotkey launch MenuToolsTest",
      "type": "autohotkey",
      "request": "launch",
      "program": "path to \script.ahk",
      "args": [],
      "port": "9002-9010",
      "variableCategories": "recommend",
      "useDebugDirective": true,
      "useAutoJumpToError": true,
      "runtime" : "path to \\AutoHotkey64.exe"
    }
]


All subsystems and classes must accept an allocator

I want every class and subsystem that allocates memory to explicitly accept a memory allocator in its constructor or startup function.
It clarifies:

which classes and subsystems are allocating memory.
where that is supposed to source its memory from.

It enables:

tracking of memory by zone.

This is largely going away in favor of shifting priorities.