[1.3] Can't commission device: CHIP Error 0x00000032: Timeout

Reproduction steps
Hello everyone,
I have the following setup:

OTBR running on RPI 4 with CHIP-tool and nRF52840 Dongle as RCP
Silicon Labs EFR32 Matter over Thread device

I have the devices succesfully connected in a thread network, I can check this by the HEX datasets matching and the state 'leader' and 'child' (or 'router'). When starting commission, I make sure ble adv is enabled on the EFR32 Matter device using a command (ble adv start).
Here is the following command I run on CHIP-tool where the Timeout error occurs:
./chip-tool pairing ble-thread 1301 hex:[LONGHEX] 20202021 3840
I have only once succeeded in this exact setup to commission a device. I really have no clue what I could have done different that time, I do not understand why it keeps failing. Once I send the command I can see in the Matter logs of the EFR32 device that it is receiving stuff. See attached logs below.
I must admit I'm not sure whether I am using 1.1 or 1.3. I am using the latest CHIP-tool version from a few days ago, for the EFR32 I am running the Light Example from the Silicon Labs Matter SDK.
(Furthermore (maybe this should be in a seperate issue) I can't commission the device through my Google Home app. I can see in the EFR32 logs that it is making a connection and the Google Home app can actually find the device, but it fails to commission it. Can't the Google Home app work with OTBR on a Raspberry Pi 4? My phone and the OTBR are connected to the same network).
Bug prevalence
All the time (commission did work only ONCE while using this exact same setup).
GitHub hash of the SDK that was being used
a40963d7d571c18f4da18205b918e0c1b4e788f5
Platform
efr32, nrf, raspi
Platform Version(s)
No response
Type
Platform Issue
Anything else?
Logs OTBR (CHIP-tool, RPI 4)
pi@nomatterwhat:~/CHIP_TOOL_BUILD$ ./chip-tool pairing ble-thread 1301 hex:[LONGHEX] 20202021 3840
[1692947111.491219][1770:1770] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1692947111.496655][1770:1770] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1692947111.496909][1770:1770] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1692947111.497050][1770:1770] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1692947111.497505][1770:1770] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-WwWv4B)
[1692947111.498190][1770:1770] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1692947111.498253][1770:1770] CHIP:DL: NVS set: chip-counters/reboot-count = 4 (0x4)
[1692947111.499322][1770:1770] CHIP:DL: Failed to get Ethernet interface
[1692947111.500108][1770:1770] CHIP:DL: Failed to reset Ethernet statistic counts
[1692947111.500464][1770:1770] CHIP:DL: Got WiFi interface: wlan0
[1692947111.502321][1770:1770] CHIP:DL: Found the primary WiFi interface:wlan0
[1692947111.502388][1770:1770] CHIP:IN: UDP::Init bind&listen port=0
[1692947111.502511][1770:1770] CHIP:IN: UDP::Init bound to port=57783
[1692947111.502534][1770:1770] CHIP:IN: UDP::Init bind&listen port=0
[1692947111.502610][1770:1770] CHIP:IN: UDP::Init bound to port=37367
[1692947111.502629][1770:1770] CHIP:IN: BLEBase::Init - setting/overriding transport
[1692947111.502646][1770:1770] CHIP:IN: TransportMgr initialized
[1692947111.502675][1770:1770] CHIP:FP: Initializing FabricTable from persistent storage
[1692947111.502861][1770:1770] CHIP:TS: Last Known Good Time: 2023-08-17T11:41:18
[1692947111.504573][1770:1770] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x248092C7195391ED, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1692947111.506970][1770:1770] CHIP:ZCL: Using ZAP configuration...
[1692947111.510247][1770:1770] CHIP:CTL: System State Initialized...
[1692947111.510354][1770:1770] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1692947111.510399][1770:1770] CHIP:CTL: Setting attestation nonce to random value
[1692947111.510449][1770:1770] CHIP:CTL: Setting CSR nonce to random value
[1692947111.510523][1770:1770] CHIP:IN: UDP::Init bind&listen port=5550
[1692947111.510636][1770:1770] CHIP:IN: UDP::Init bound to port=5550
[1692947111.510659][1770:1770] CHIP:IN: UDP::Init bind&listen port=5550
[1692947111.510750][1770:1770] CHIP:IN: UDP::Init bound to port=5550
[1692947111.510794][1770:1770] CHIP:IN: TransportMgr initialized
[1692947111.511122][1770:1772] CHIP:DL: CHIP task running
[1692947111.511226][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 32786
[1692947111.511572][1770:1772] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1692947111.511624][1770:1772] CHIP:CTL: Setting attestation nonce to random value
[1692947111.511782][1770:1772] CHIP:CTL: Setting CSR nonce to random value
[1692947111.512660][1770:1772] CHIP:CTL: Generating NOC
[1692947111.513574][1770:1772] CHIP:FP: Validating NOC chain
[1692947111.515429][1770:1772] CHIP:FP: NOC chain validation successful
[1692947111.515593][1770:1772] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1692947111.515624][1770:1772] CHIP:TS: Last Known Good Time: 2023-08-17T11:41:18
[1692947111.515644][1770:1772] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1692947111.515664][1770:1772] CHIP:TS: Retaining current Last Known Good Time
[1692947111.517720][1770:1772] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1692947111.519526][1770:1772] CHIP:TS: Committing Last Known Good Time to storage: 2023-08-17T11:41:18
[1692947111.521164][1770:1772] CHIP:CTL: Joined the fabric at index 1.  Attempting to connect.
[1692947112.174401][1770:1771] CHIP:DL: ConnectDevice complete
[1692947113.301181][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301232][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301260][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301277][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301300][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301317][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301336][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301353][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301371][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301388][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301411][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0001
[1692947113.301428][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301492][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0001
[1692947113.301510][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301528][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0001
[1692947113.301545][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301570][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301587][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301605][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301622][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301640][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service000e
[1692947113.301656][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301685][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301701][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301721][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301737][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301757][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301773][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301795][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301812][1770:1771] CHIP:DL: Char1 /org/bluez/hci0/dev_14_B4_57_5F_9E_56/service0015
[1692947113.301836][1770:1771] CHIP:DL: New BLE connection: conn 0xffff8805f060, device 14:B4:57:5F:9E:56, path /org/bluez/hci0/dev_14_B4_57_5F_9E_56
[1692947113.302060][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16385
[1692947113.302116][1770:1772] CHIP:DIS: Closing all BLE connections
[1692947113.302219][1770:1772] CHIP:IN: BleConnectionComplete: endPoint 0xaaaab9e18418
[1692947113.302681][1770:1772] CHIP:IN: SecureSession[0xffff80010b00]: Allocated Type:1 LSID:1347
[1692947113.302726][1770:1772] CHIP:SC: Assigned local session key ID 1347
[1692947113.302824][1770:1772] CHIP:EM: <<< [E:34373i S:0 M:218336557] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
[1692947113.302885][1770:1772] CHIP:IN: (U) Sending msg 218336557 to IP address 'BLE'
[1692947113.302911][1770:1772] CHIP:IN: Message appended to BLE send queue
[1692947113.302930][1770:1772] CHIP:SC: Sent PBKDF param request
[1692947113.732425][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1692947113.831944][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16388
[1692947113.832147][1770:1772] CHIP:BLE: subscribe complete, ep = 0xaaaab9e18418
[1692947113.833643][1770:1771] CHIP:DL: Indication received, conn = 0xffff8805f060
[1692947113.833942][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1692947113.834018][1770:1772] CHIP:BLE: peripheral chose BTP version 4; central expected between 4 and 4
[1692947113.834070][1770:1772] CHIP:BLE: using BTP fragment sizes rx 244 / tx 244.
[1692947113.834119][1770:1772] CHIP:BLE: local and remote recv window size = 5
[1692947113.835029][1770:1772] CHIP:IN: BLE EndPoint 0xaaaab9e18418 Connection Complete
[1692947113.927560][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1692947116.414819][1770:1771] CHIP:DL: Indication received, conn = 0xffff8805f060
[1692947116.415150][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1692947118.997398][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1692947121.484965][1770:1771] CHIP:DL: Indication received, conn = 0xffff8805f060
[1692947121.485604][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1692947121.559060][1770:1772] CHIP:DIS: Closing all BLE connections
[1692947121.559143][1770:1772] CHIP:IN: Clearing BLE pending packets.
[1692947121.559860][1770:1772] CHIP:BLE: Auto-closing end point's BLE connection.
[1692947121.559932][1770:1772] CHIP:DL: Closing BLE GATT connection (con 0xffff8805f060)
[1692947121.560163][1770:1771] CHIP:DL: BluezDisconnect peer=14:B4:57:5F:9E:56
[1692947124.167691][1770:1772] CHIP:IN: SecureSession[0xffff80010b00]: Released - Type:1 LSID:1347
[1692947124.167839][1770:1772] CHIP:TOO: Pairing Failure: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
[1692947124.167954][1770:1772] CHIP:BLE: BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
[1692947124.168037][1770:1772] CHIP:DL: HandlePlatformSpecificBLEEvent 16388
[1692947124.168098][1770:1772] CHIP:BLE: no endpoint for unsub complete
[1692947124.168546][1770:1770] CHIP:CTL: Shutting down the commissioner
[1692947124.168634][1770:1770] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1692947124.168889][1770:1770] CHIP:CTL: Shutting down the controller
[1692947124.169096][1770:1770] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1692947124.169235][1770:1770] CHIP:FP: Forgetting fabric 0x1
[1692947124.169386][1770:1770] CHIP:TS: Pending Last Known Good Time: 2023-08-17T11:41:18
[1692947124.169846][1770:1770] CHIP:TS: Previous Last Known Good Time: 2023-08-17T11:41:18
[1692947124.170004][1770:1770] CHIP:TS: Reverted Last Known Good Time to previous value
[1692947124.170165][1770:1770] CHIP:CTL: Shutting down the commissioner
[1692947124.170224][1770:1770] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1692947124.170481][1770:1770] CHIP:CTL: Shutting down the controller
[1692947124.170640][1770:1770] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1692947124.170598][1770:1771] CHIP:DL: Bluez disconnected
[1692947124.170813][1770:1771] CHIP:DL: Bluez notify CHIPoBluez connection disconnected
[1692947124.171239][1770:1770] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1692947124.171522][1770:1770] CHIP:FP: Shutting down FabricTable
[1692947124.171594][1770:1770] CHIP:TS: Pending Last Known Good Time: 2023-08-17T11:41:18
[1692947124.171820][1770:1770] CHIP:TS: Previous Last Known Good Time: 2023-08-17T11:41:18
[1692947124.171878][1770:1770] CHIP:TS: Reverted Last Known Good Time to previous value
[1692947124.172370][1770:1770] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-0ibPGG)
[1692947124.173665][1770:1770] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1692947124.173827][1770:1770] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1692947124.173888][1770:1770] CHIP:DL: Inet Layer shutdown
[1692947124.173937][1770:1770] CHIP:DL: BLE shutdown
[1692947124.177665][1770:1770] CHIP:DL: System Layer shutdown
[1692947124.178112][1770:1770] CHIP:TOO: Run command failure: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout

Logs EFR32 (Matter device)
[00:28:41.292][info  ][DL] Connect Event for handle : 4
[00:28:41.440][info  ][DL] evt_UNKNOWN id = 090600a0
[00:28:42.902][info  ][DL] Char Write Req, char : 23
[00:28:42.902][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 4, len 9)
[00:28:42.903][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
[00:28:42.903][info  ][BLE] local and remote recv window sizes = 5
[00:28:42.903][info  ][BLE] selected BTP version 4
[00:28:42.903][info  ][BLE] using BTP fragment sizes rx 244 / tx 244.
[00:28:43.000][info  ][DL] HandleTXcharCCCDWrite - Config Flags value : 2
[00:28:43.000][info  ][DL] CHIPoBLE subscribe received
[00:28:43.000][info  ][DL] _OnPlatformEvent kCHIPoBLESubscribe
[00:28:43.000][detail][IN] BLE EndPoint 0x200099e0 Connection Complete
[00:28:43.000][info  ][DL] _OnPlatformEvent default:  event->Type = 32775
[00:28:43.096][info  ][DL] Tx Confirmation received
[00:28:43.097][info  ][DL]  stop soft timer
[00:28:43.097][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
[00:28:43.098][info  ][DL] Char Write Req, char : 23
[00:28:43.098][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 4, len 73)
[00:28:43.099][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
[00:28:43.099][info  ][EM] >>> [E:46123r S:0 M:252510018] (U) Msg RX from 0:D43656EF5AC382A9 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
[00:28:45.680][info  ][DL] Tx Confirmation received
[00:28:45.681][info  ][DL]  stop soft timer
[00:28:45.681][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
[00:28:48.166][info  ][DL] Char Write Req, char : 23
[00:28:48.166][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 4, len 3)
[00:28:48.167][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
[00:28:50.750][info  ][DL] Tx Confirmation received
[00:28:50.750][info  ][DL]  stop soft timer
[00:28:50.751][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
[00:28:50.995][info  ][DL] HandleTXcharCCCDWrite - Config Flags value : 0
[00:28:50.995][info  ][DL] CHIPoBLE unsubscribe received
[00:28:50.995][info  ][DL] _OnPlatformEvent kCHIPoBLEUnsubscribe
[00:28:50.995][detail][IN] Clearing BLE pending packets.
[00:28:50.996][info  ][BLE] Releasing end point's BLE connection back to application.
[00:28:53.530][info  ][DL] Disconnect Event for handle : 4
[00:28:53.530][info  ][DL] BLE GATT connection closed (con 4, reason 4115)
[00:28:53.530][info  ][DL] _OnPlatformEvent kCHIPoBLEConnectionError
[00:28:53.530][detail][DL] Start BLE advertissement

From the Matter device:
[00:28:43.099][info  ][EM] >>> [E:46123r S:0 M:252510018] (U) Msg RX from 0:D43656EF5AC382A9 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)

but then it never sends a response.  You should look into why it's not doing that.

Thanks for your reply @bzbarsky-apple !
I have some interestings finds, but I am not sure whether this behaviour is expected. Since I was able to commission the device once, I was in the impression that I could either just re-commission it, or it would throw out an error that it was already commissioned. After a few days I was not able to send a cluster command nor unpair the Matter device, I think this is because I changed the Thread network credentials on both devices (even though they are the same credentials and they are still connected!).
Then I tried to factory reset (with the OT CLI) the Matter device and OTBR, still no luck. Then I completely erased the MCU memory flash of the Matter device, re-uploaded the Matter program and tried commissioning again, and it worked right away! I then changed the Thread credentials again on both devices, while they are still in the same Thread network(!), and I was unable to unpair the device nor send cluster commands, thus the device would get 'stuck' (since I can't unpair, nor commission).
Is this behaviour expected/known? Or is there going something wrong on my side?

Do you reuse the same node id when doing the next commissioning attempts? Could you provide a full log from the EFR32?

I then changed the Thread credentials again on both devices, while they are still in the same Thread network(!), and I was unable to unpair the device nor send cluster commands

So it I understand correctly:

You commission a Matter device onto a Thread network.
You modify the Thread credentials on the Matter device so that it is now on a different Thread network?
You change your controller to also be on the new Thread network.
You try to send a command to the Matter device and it fails.

Is that a correct description of what you are observing?  I am assuming that operational discovery fails when doing step 4?  Does the new Thread network have an SRP server?  Does the Matter device manage to register its operational advertisement with that SRP server?

@bzbarsky-apple correct. thanks for your reply. This is why I assume it fails to send Matter commands after. I'm only changing the Thread credentials by creating a new dataset on both devices (although they match). So for the SRP server, I haven't heard of that before (but I just did some reading about it), and I leave that all to the default.

If it is possible it would be great to get a full log from the EFR32.
After the credential changes I would assume it will need to reregister the SRP entry, so the log should state something like SRP update succeeded. In case this fails and the DUT is not able to register the SRP service the controller will not be able to resolve the node id and communication will fail.
My initial though was also related to SRP.

Hmm, not sure but it does look like bluez is complaining 🤔

@ReneJosefsen my bad, I forgot to re-enable sudo systemctl enable hciuart, it works now :). Here are the full EFR32 while I try another commission. The onoff toggle commands are not received at all in the logs.
00> [00:00:00.000][silabs ]==================================================
00> [00:00:00.000][silabs ]SiLabs-Light starting
00> [00:00:00.000][silabs ]==================================================
00> [00:00:00.000][silabs ]Init CHIP Stack
00> [00:00:00.000][info  ][DL] Setting device name to : "SiLabs-Light"
00> [00:00:00.000][silabs ]Initializing OpenThread stack
00> [00:00:00.000][info  ][DL] OpenThread ifconfig up and thread start
00> [00:00:00.000][info  ][DL] OpenThread started: OK
00> [00:00:00.000][info  ][DL] Setting OpenThread device type to ROUTER
00> [00:00:00.000][silabs ]Starting OpenThread task
00> [00:00:00.000][info  ][SVR] Subscription persistence not supported
00> [00:00:00.000][info  ][SVR] Server initializing...
00> [00:00:00.000][detail][FP] Initializing FabricTable [00:00:25.512][info  ][DL] _OnPlatformEvent default:  event->Type = 32777
00> [00:00:25.512][detail][DL] OpenThread State Changed (Flags: 0x10000040)
00> [00:00:31.536][info  ][DL] _OnPlatformEvent default:  event->Type = 32777
00> [00:00:31.536][detail][DL] OpenThread State Changed (Flags: 0x200012a4)
00> [00:00:31.536][detail][DL]    Device Role: CHILD
00> [00:00:31.536][detail][DL]    Partition Id: 0x730C92D3
00> [00:00:31.537][info  ][DL] _OnPlatformEvent default:  event->Type = 32777
00> [00:00:31.537][detail][DL] Thread Attached updating Multicast address
00> [00:00:31.537][info  ][SVR] Joining Multicast groups
00> [00:00:31.538][detail][DL] OpenThread State Changed (Flags: 0x00000001)
00> [00:00:31.538][detail][DL]    Thread Unicast Addresses:
00> [00:00:31.538][detail][DL]         fda0:a80:e5a4:1:cd18:4537:cfb7:acde/64 valid preferred
00> [00:00:31.539][detail][DL]         fd30:2557:1980:b79f:0:ff:fe00:bc01/64 valid rloc
00> [00:00:31.539][detail][DL]         fd30:2557:1980:b79f:bd17:2eb9:bb46:a113/64 valid
00> [00:00:31.539][detail][DL]         fe80:0:0:0:90a4:b5cc:4f3:66fc/64 va[00:00:34.541][info  ][SWU] Stopping the watchdog timer
00> [00:00:34.541][info  ][SWU] Starting the periodic query timer, timeout: 86400 seconds
00> [00:00:34.541][detail][DMG] Endpoint 0, Cluster 0x0000_002A update version to df580c9e
00> [00:00:34.542][info  ][ZCL] Cluster callback: 0x0000_002A
00> [00:00:34.542][detail][DMG] Endpoint 0, Cluster 0x0000_002A update version to df580c9f
00> [00:00:34.542][info  ][ZCL] Cluster callback: 0x0000_002A
00> [00:00:42.227][info  ][DL] SRP Client was started, detected server: fd30:2557:1980:b79f:42aa:ebd7:b3d1:11de
00> [00:00:42.227][info  ][DL] _OnPlatformEvent default:  event->Type = 32777
00> [00:00:42.227][detail][DL] OpenThread State Changed (Flags: 0x00000200)
00> [00:00:42.742][detail][DL] SRP update succeeded
00> [00:00:42.742][info  ][DIS] Setting operational delegate post init
00> [00:00:42.742][info  ][DL] _OnPlatformEvent default:  event->Type = 32784
00> [00:00:42.742][error ][SVR] Server initialization complete
00> [00:00:42.742][info  ][DIS] Updating services using commissioning mode 0
00> [00:00:42.743][detail][DL] Using Thread extended MAC for hostname.
00> [00:00:42.743][info  ][DIS] Advertise operational node 248092C7195391ED-0000000000000002
00> [00:00:42.743][info  ][DL] advertising srp service: 248092C7195391ED-0000000000000002._matter._tcp
00> [00:00:42.743][detail][DL] Using Thread extended MAC for hostname.
00> [00:00:42.744][info  ][DIS] Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=[00:00:44.335][detail][DL] SRP update succeeded
00> [00:00:49.021][detail][DL] Start BLE advertissement
00> [00:00:55.453][info  ][DL] Connect Event for handle : 1
00> [00:00:55.568][info  ][DL] evt_UNKNOWN id = 090600a0
00> [00:00:57.030][info  ][DL] Char Write Req, char : 23
00> [00:00:57.030][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 1, len 9)
00> [00:00:57.031][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
00> [00:00:57.031][info  ][BLE] local and remote recv window sizes = 5
00> [00:00:57.031][info  ][BLE] selected BTP version 4
00> [00:00:57.031][info  ][BLE] using BTP fragment sizes rx 244 / tx 244.
00> [00:00:57.127][info  ][DL] HandleTXcharCCCDWrite - Config Flags value : 2
00> [00:00:57.127][info  ][DL] CHIPoBLE subscribe received
00> [00:00:57.128][info  ][DL] _OnPlatformEvent kCHIPoBLESubscribe
00> [00:00:57.128][detail][IN] BLE EndPoint 0x200099e0 Connection Complete
00> [00:00:57.128][info  ][DL] _OnPlatformEvent default:  event->Type = 32775
00> [00:00:57.224][info  ][DL] Tx Confirmation received
00> [00:00:57.225][info  ][DL]  stop soft timer
00> [00:00:57.225][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
00> [00:00:57.226][info  ][DL] Char Write Req, char : 23
00> [00:00:57.226][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 1, len 73)
00> [00:00:57.227][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
00> [00:00:57.227][info  ][EM] >>> [E:26834r S:0 M:263958489] (U) Msg RX from 0:C8F66327FD0418E7 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
00> [00:00:59.809][info  ][DL] Tx Confirmation received
00> [00:00:59.809][info  ][DL]  stop soft timer
00> [00:00:59.809][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
00> [00:01:02.295][info  ][DL] Char Write Req, char : 23
00> [00:01:02.295][detail][DL] Write request/command received for CHIPoBLE RX characteristic (con 1, len 3)
00> [00:01:02.296][info  ][DL] _OnPlatformEvent kCHIPoBLEWriteReceived
00> [00:01:04.879][info  ][DL] Tx Confirmation received
00> [00:01:04.879][info  ][DL]  stop soft timer
00> [00:01:04.879][info  ][DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
00> [00:01:05.416][info  ][DL] HandleTXcharCCCDWrite - Config Flags value : 0
00> [00:01:05.416][info  ][DL] CHIPoBLE unsubscribe received
00> [00:01:05.416][info  ][DL] _OnPlatformEvent kCHIPoBLEUnsubscribe
00> [00:01:05.416][detail][IN] Clearing BLE pending packets.
00> [00:01:05.416][info  ][BLE] Releasing end point's BLE connection back to application.
00> [00:01:07.512][info  ][DL] Disconnect Event for handle : 1
00> [00:01:07.512][info  ][DL] BLE GATT connection closed (con 1, reason 4115)
00> [00:01:07.512][info  ][DL] _OnPlatformEvent kCHIPoBLEConnectionError
00> [00:01:07.512][detail][DL] Start BLE advertissement
00> [00:01:35.126][info  ][DL] _OnPlatformEvent default:  event->Type = 32777
00> [00:01:35.126][detail][DL] OpenThread State Changed (Flags: 0x00000064)
00> [00:01:35.126][detail][DL]    Device Role: ROUTER
00> [00:01:37.515][detail][DL] bleAdv Timeout : Start slow advertissment

The EFR32 does join the network and does report a successful SRP entry 🤔
00> [00:00:42.742][detail][DL] SRP update succeeded
Is the PI using a TH image ?

Thanks for your help. I'm not sure what you mean with a TH image? 😅
The Raspberry Pi runs on Ubuntu 22.04, I built the Matter SDK on it from scratch and that seems to run fine (apart from sometimes having to restart some Bluetooth services). No pre-built images.

Okay, I was wondering if it was based on the Test Harness (TH) images that are created for the specific matter releases.
I'm not super familiar with this setup, but it would be interesting to somehow verify if the routes in the network break when the thread dataset is changes.
Any chance you can generate a log of the whole scenario, so successful commissioning, toggle on/off, change dataset on EFR and OTBR and then the subsequent failure to communicate??


[EDA] Affiliation Settings Mappings Editing

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes

The changes look good and we've minimized scrolling. Approving this PR.

Approved again!


Character often visually displaying wrong weapon/equipment

Idk if there are other ways to reproduce this but one way I noticed how to glitch it was I was in bank and I deposit all worn items with the button on the bank and then exit the bank and I was still wearing the weapon (visually), but not really

Issue has been resolved with latest update


default security groups explicitly listed for each space

If I do an export-config
default security groups are listed under named-security-groups: in each spaceConfig.yml
I think only space specific security groups should be listed in spaceConfig.yml
is this a bug or has some purpose I don't see yet?

Currently there is no support for managing default security groups (https://github.com/pivotalservices/cf-mgmt/issues/67) This would appear to be a bug in export as would not want to list default security groups in the spaceConfig.yml as named security groups.  Will investigate and update with a fix.

Will be fixed with v0.0.84 which should be released shortly.


Added the missing 7 option from "Number of Digits" dropdown

The "Number of digits dropdown for LED display modules was missing the 7 option.

Fixes #638


fix(ui): connection form is not sending correct fields

Describe your changes :

I worked on the Closes: #10251
Issue:

some issue with AntD package that rjsf supports @rjsf/antd
Even trying with omitExtraData & Live omit it still holds the default value from schema and send it to formData which causes the issue
Finally version bump to latest and discarding AntD helps and it's working as expected, Refer attached video

ToDo:

Check how we can bring back AntD theme @chirag-madlani

Type of change :

[x] Bug fix

Frontend Preview (Screenshots):
https://user-images.githubusercontent.com/12962843/225630397-27f7a9d0-8191-4dfc-9b06-635f628c2a71.mov

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

TestPlan:

[ ] Need to verify all the connection form & it's validation
[ ] Verify via Cypress as well as Manually

Reviewers

We are not supporting changing OM connection details through UI. Hence closing this


fix: 🐛 don't fill truncated_cells w/ unsupported cols on /rows

See
https://github.com/huggingface/moon-landing/pull/6300#issuecomment-1547590109 for reference (internal link).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

CI is failing because the actions get 503 error when installing packages from http://azure.archive.ubuntu.com.


Guide iframe CSS affects live preview

I think the Guide CSS is affecting live preview due to it's global iframe css. Specifically having iframe set to position: absolute; globally forces the live preview window to narrow considerably.

Fixed in version 2.0.1


Question: how is the RabbitConsumerProperties changed?

Hi, I'm new to spring but how do I change the RabbitConsumerProperties from application.yml?

Hi,
The doc for this is available [here] (http://docs.spring.io/spring-cloud-stream/docs/Brooklyn.BUILD-SNAPSHOT/reference/htmlsingle/index.html#_rabbitmq_consumer_properties).
You can set the properties in your app's application.yml like this:
spring:
  cloud:
    stream:
      rabbit:
         bindings:
            <channelName>:
               consumer:
                   prefetch: 10

Great! Thanks


[Feature] More specific episode info

Like what characters were seen in the episode, what their role was in the episode, the episode title (english, romaji, japanese) and or alts, the episode summary or synopsis, etc.

This is more of a data issue, at the moment we don't really have the community/staff to support our current data set so adding stuff like this isn't something we can really do at the moment. There are plans to get episode information for streaming sites (crunchyroll, funimation etc) so that will provide some data such as images, titles, and episode descriptions but no eta for when that will be implemented.


Progress stash

Add's nodegit progress and command line progress bars to flex.
Please squash/remove the "merge to master" thing if possible @a-teammate

could we merge this please? :)
the littel fix Windows -> Darwin is required, otherwise merge and publish?

No, the download progress is actually broken/wrong for release downloads. Didn't dig in it for some days, needs to be fixed before we're ready


Update Links “tiktok-44”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: b2f86601840c7560d328b7727d9fb4756f6592e5
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/6135f1181ee92400076cf510


RSX parser suggestion: syn-rsx

Hey, your macro is probably feature complete and there's no interest in changing it – but in case you have to expand functionality: I just wanted to leave an hint for my syn-rsx crate here. I think it'd be great to combine efforts for that basic building block, and others like sauron and leptos are successfully using it.
Sorry for the shameless plug and obviously feel free to close this issue.

Realized that this repository is deprecated and opened https://github.com/DioxusLabs/dioxus/discussions/620 instead.


install Memcache deprecated

The install Memcache link in php-docs-samples/blob/master/appengine/wordpress/README.md to
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-memcache-on-ubuntu-12-04#install-memcache
goes to a page that says
Status: Deprecated
This article covers a version of Ubuntu that is no longer supported. If you are currently operate a server running Ubuntu 12.04, we highly recommend upgrading or migrating to a supported version of Ubuntu:

Upgrade to Ubuntu 14.04.
Upgrade from Ubuntu 14.04 to Ubuntu 16.04
Migrate the server data to a supported version

Also it's not clear if this is actually needed or not, and where we're installing it. Locally?
It doesn't seem to be needed for the initial install, but might be needed for the upgrade.

Also those instructions are only for Ubuntu. What about Mac OS X and Windows?

Fixed in https://github.com/GoogleCloudPlatform/php-docs-samples/pull/843


operators [N] mercury-operator (1.0.2)

Signed-off-by: Theodor Mihalache<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@tmihalac please add version in directory structure. Move it to operators/mercury-operator/1.0.2

/merge possible

/merge possible

/merge possible


Remove remaining dependency on apitools

apitools is deprecated and continued reliance on it is complicating Beam's dependency management. Previous work should have already removed our dependence on the clients it generates for us (see #25676, #25678, #25679, #25680 and (tracking issue:) #19073).
Delete these clients (if not already deleted) and remove the remaining references to apitools outside of the clients by either replacing them with calls to Google Cloud Python libraries or (for small things), by bringing them into the Beam codebase if acceptable external replacements can't be found.
Finally, remove Beam's dependency on apitools. The job is done when this can be done safely.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Including this into #25652 umbrella bug.


Can't not download Android Support Library 23.3.0

I'm in China,but I couldn't download 23.3.0 support library。。。

@irobotman That's nothing related to this library.

@irobotman I'm sorry for that. But not at all related to the MaterialDrawer.


Provider produced inconsistent final plan with automated logpush ownership challenge

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.9.2
on darwin_arm64
+ provider registry.terraform.io/cloudflare/cloudflare v4.37.0
+ provider registry.terraform.io/hashicorp/google v5.37.0
+ provider registry.terraform.io/hashicorp/google-beta v5.37.0

Affected resource(s)

cloudflare_logpush_job
cloudflare_logpush_ownership_challenge

Terraform configuration files
resource "google_storage_bucket" "cloudflare_logpush" {
  count = local.is_gcp ? 1 : 0
  name     = "${var.tenant_id}-cloudflare-logs"
  location = "US"
  project  = var.gcp_project_id
  force_destroy = true
  lifecycle_rule {
    condition {
      age            = var.retention_period_days
      matches_prefix = ["v2/"]
    }
    action {
      type = "Delete"
    }
  }
}

resource "google_storage_bucket_iam_member" "logpush_cloudflare" {
  count = local.is_gcp  ? 1 : 0
  bucket = google_storage_bucket.cloudflare_logpush[0].name
  role   = "roles/storage.objectAdmin"
  member =<EMAIL_ADDRESS>  depends_on = [ google_storage_bucket.cloudflare_logpush[0] ]
}

resource "cloudflare_logpush_ownership_challenge" "gcp_challenge" {
  zone_id          = var.cloudflare_zone_id
  destination_conf = "${local.destination_conf}/v2/spectrum/{DATE}"
  depends_on = [ google_storage_bucket_iam_member.logpush_cloudflare ]
}

data "google_storage_bucket_object_content" "challenge" {
  name   = cloudflare_logpush_ownership_challenge.gcp_challenge.ownership_challenge_filename
  bucket = google_storage_bucket.cloudflare_logpush[0].name
  depends_on = [ cloudflare_logpush_ownership_challenge.gcp_challenge ]
}

resource "cloudflare_logpush_job" "v2_spectrum" {
  enabled             = true
  zone_id             = var.cloudflare_zone_id
  name                = "Logpush-v2-${var.tenant_id}-Spectrum"
  logpull_options     = "fields=Application,ClientAsn,ClientBytes,ClientCountry,ClientIP,ClientMatchedIpFirewall,ClientPort,ClientProto,ColoCode,ConnectTimestamp,DisconnectTimestamp,Event,OriginBytes,OriginIP,OriginPort,OriginProto,Status,Timestamp,IpFirewall,ProxyProtocol,ClientTcpRtt,ClientTlsCipher,ClientTlsClientHelloServerName,ClientTlsProtocol,ClientTlsStatus,OriginTcpRtt,OriginTlsCipher,OriginTlsFingerprint,OriginTlsMode,OriginTlsProtocol,OriginTlsStatus&timestamps=rfc3339"
  destination_conf    = "${local.destination_conf}/v2/spectrum/{DATE}"
  ownership_challenge = data.google_storage_bucket_object_content.challenge.content
  dataset             = "spectrum_events"
  depends_on = [ data.google_storage_bucket_object_content.challenge, cloudflare_logpush_ownership_challenge.gcp_challenge ]
}

Link to debug output
https://gist.github.com/Kaitou786/2c4534a610b3abdb2ba167930dfb2f49
Panic output
No response
Expected output
Apply to proceed and create a logpush job without any problem.
Actual output
╷
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.cloudflare-logpush[0].cloudflare_logpush_job.v2_spectrum to include new values learned so far during apply, provider "registry.terraform.io/cloudflare/cloudflare" produced an invalid new value for .ownership_challenge: was null, but now
│ cty.StringVal("REDACTED_VALUE").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵

Steps to reproduce
The minimum steps required for reproducing this problem would be:

Create a ownership_challenge:

resource "cloudflare_logpush_ownership_challenge" "gcp_challenge" {
  zone_id          = var.cloudflare_zone_id
  destination_conf = "${local.destination_conf}/v2/spectrum/{DATE}"
}

Read that ownership challenge from the bucket, using the data block.

data "google_storage_bucket_object_content" "challenge" {
  name   = cloudflare_logpush_ownership_challenge.gcp_challenge.ownership_challenge_filename
  bucket = google_storage_bucket.cloudflare_logpush[0].name
  depends_on = [ cloudflare_logpush_ownership_challenge.gcp_challenge ]
}

Use the above data while creating the logpush job with explicitly depending on the above resources:

resource "cloudflare_logpush_job" "v2_spectrum" {
  enabled             = true
  zone_id             = var.cloudflare_zone_id
  name                = "Logpush-v2-${var.tenant_id}-Spectrum"
  logpull_options     = "fields=Application,ClientAsn,ClientBytes,ClientCountry,ClientIP,ClientMatchedIpFirewall,ClientPort,ClientProto,ColoCode,ConnectTimestamp,DisconnectTimestamp,Event,OriginBytes,OriginIP,OriginPort,OriginProto,Status,Timestamp,IpFirewall,ProxyProtocol,ClientTcpRtt,ClientTlsCipher,ClientTlsClientHelloServerName,ClientTlsProtocol,ClientTlsStatus,OriginTcpRtt,OriginTlsCipher,OriginTlsFingerprint,OriginTlsMode,OriginTlsProtocol,OriginTlsStatus&timestamps=rfc3339"
  destination_conf    = "${local.destination_conf}/v2/spectrum/{DATE}"
  ownership_challenge = data.google_storage_bucket_object_content.challenge.content
  dataset             = "spectrum_events"
  depends_on = [ data.google_storage_bucket_object_content.challenge, cloudflare_logpush_ownership_challenge.gcp_challenge ]
}

Additional factoids

The inital plan for creating the logpush job also doesn' have ownership_challenge i.e. comes to be null instead of known after apply

ref:

  + resource "cloudflare_logpush_job" "v2_spectrum" {
      + dataset          = "spectrum_events"
      + destination_conf = "gs://maintkhandelwal3rev-cloudflare-logs/v2/spectrum/{DATE}"
      + enabled          = true
      + frequency        = "high"
      + id               = (known after apply)
      + logpull_options  = "fields=Application,ClientAsn,ClientBytes,ClientCountry,ClientIP,ClientMatchedIpFirewall,ClientPort,ClientProto,ColoCode,ConnectTimestamp,DisconnectTimestamp,Event,OriginBytes,OriginIP,OriginPort,OriginProto,Status,Timestamp,IpFirewall,ProxyProtocol,ClientTcpRtt,ClientTlsCipher,ClientTlsClientHelloServerName,ClientTlsProtocol,ClientTlsStatus,OriginTcpRtt,OriginTlsCipher,OriginTlsFingerprint,OriginTlsMode,OriginTlsProtocol,OriginTlsStatus&timestamps=rfc3339"
      + name             = "Logpush-v2-maintkhandelwal3rev-Spectrum"
      + zone_id          = "REDACTED"
    }

For some weird reason it only happens when using GCS, it works fine when working with S3

References
The below issues describes the same issue, in the first one it is suggested to use the depends_on which I also have but still get the error,
fwiw, I have tried all the combination of depends_on array:
i.e.:
 depends_on = [ data.google_storage_bucket_object_content.challenge, cloudflare_logpush_ownership_challenge.gcp_challenge ]
 depends_on = [ cloudflare_logpush_ownership_challenge.gcp_challenge ]
  depends_on = [ data.google_storage_bucket_object_content.challenge ]

https://github.com/cloudflare/terraform-provider-cloudflare/issues/2752
https://github.com/cloudflare/terraform-provider-cloudflare/issues/2794

similar to the linked issues, this isn't a provider problem but an issue with the ordering and consistency in GCP. you'll need to either:

insert an artifact wait condition for the contents to be available; or
do it in two runs.

this works as expected with backends like S3 or R2 so unfortunately, there is little we can do here without using one of the above workarounds for GCP.


Error during system checks since wagtail 1.4.2

I just came across a strange error with wagtail 1.4.2 and 1.4.3. Everything is fine with wagtail 1.4.1. I may also say that I work with Django<1.9 (currently 1.8.12)
The stack is the following :
Unhandled exception in thread started by <function check_errors.<locals>.wrapper at 0x7f0f093eaea0>
Traceback (most recent call last):
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/db/models/options.py", line 552, in get_field
    return self.fields_map[field_name]
KeyError: 'body'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/utils/autoreload.py", line 229, in wrapper
    fn(*args, **kwargs)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/core/management/commands/runserver.py", line 114, in inner_run
    self.validate(display_num_errors=True)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/core/management/base.py", line 469, in validate
    return self.check(app_configs=app_configs, display_num_errors=display_num_errors)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/core/management/base.py", line 482, in check
    include_deployment_checks=include_deployment_checks,
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/core/checks/model_checks.py", line 28, in check_all_models
    errors.extend(model.check(**kwargs))
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailcore/models.py", line 571, in check
    edit_handler = cls.get_edit_handler()
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/utils/decorators.py", line 54, in __call__
    return self.value
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/utils/functional.py", line 59, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/utils/decorators.py", line 50, in value
    return self.fn(self.cls)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 743, in get_edit_handler
    return EditHandler.bind_to_model(cls)
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 311, in bind_to_model
    'children': [child.bind_to_model(model) for child in self.children],
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 311, in <listcomp>
    'children': [child.bind_to_model(model) for child in self.children],
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 332, in bind_to_model
    'children': [child.bind_to_model(model) for child in self.children],
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 332, in <listcomp>
    'children': [child.bind_to_model(model) for child in self.children],
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/wagtail/wagtailadmin/edit_handlers.py", line 779, in bind_to_model
    'block_def': model._meta.get_field(self.field_name).stream_block
  File "/home/arthur/.virtualenvs/lepinard/lib/python3.5/site-packages/django/db/models/options.py", line 554, in get_field
    raise FieldDoesNotExist('%s has no field named %r' % (self.object_name, field_name))
django.core.exceptions.FieldDoesNotExist: Page has no field named 'body'

I am preparing more infos. Stay tuned !

I've published a sample project : https://github.com/arthru/wagtail_issue2452. ./manage.py runserver triggers the error.

This could be related to #2428

Thanks for reporting
According to the traceback, the error is being raised from StreamFieldPanel.bind_to_model: https://github.com/torchbox/wagtail/blob/09878fcfd87f5b5ea67dd8d178667bce344c02e0/wagtail/wagtailadmin/edit_handlers.py#L779

Confirmed that I can reproduce this problem on the sample project. git bisect shows that the regression happened in https://github.com/torchbox/wagtail/commit/c823ace6a1c48aab9e93b4387adc30c0fd1d749a

OK, worked out what's going on here... the error is at the end of your models.py:
HomePage.content_panels += [
    StreamFieldPanel('body'),
    PageChooserPanel('contact_page', FormPage),
]

At this point HomePage.content_panels has not been overridden - it's the same object as Page.content_panels, and so this line causes Page.content_panels to be extended with the new panels too. So, this is actually a legitimate error, telling you that you've attempted to define StreamFieldPanel('body') on Page, which is a field that doesn't exist.
c823ace6a1c48aab9e93b4387adc30c0fd1d749a makes this error visible because it adds a system check that tries to construct all edit handlers on startup, but the same error would also have occurred on earlier versions if you'd tried to create a plain instance of Page.

Ok, my bad...
Sorry for this disturbing issue. And thank you for your nice work !


Variables values undefined when operator is primed

See undefined value of variable terminationDetected and priming of terminated operator:

---------------------- MODULE AsyncTerminationDetection ---------------------
EXTENDS Naturals

N == 2

ASSUME NIsPosNat == N \in Nat \ {0}

Node == 0 .. N-1

VARIABLES
  active,               \* activation status of nodes
  pending,              \* number of messages pending at a node
  terminationDetected

vars == << active, pending, terminationDetected >>

terminated == \A n \in Node : ~ active[n] /\ pending[n] = 0

-----------------------------------------------------------------------------

Init ==
    /\ active \in [ Node -> BOOLEAN ]
    /\ pending \in [ Node -> 0..1 ]
    /\ terminationDetected \in {FALSE, terminated}

Terminate(i) ==
    /\ active' \in { f \in [ Node -> BOOLEAN] : \A n \in Node: ~active[n] => ~f[n] }
    /\ pending' = pending
    /\ terminationDetected' \in {terminationDetected, terminated'}

SendMsg(i, j) ==
    /\ active[i]
    /\ pending' = [pending EXCEPT ![j] = @ + 1]
    /\ UNCHANGED << active, terminationDetected >>

Wakeup(i) ==
    /\ pending[i] > 0
    /\ active' = [active EXCEPT ![i] = TRUE]
    /\ pending' = [pending EXCEPT ![i] = @ - 1]
    /\ UNCHANGED << terminationDetected >>

DetectTermination ==
    /\ terminated
    /\ ~terminationDetected
    /\ terminationDetected' = TRUE
    /\ UNCHANGED << active, pending >>

-----------------------------------------------------------------------------

Next ==
    \/ DetectTermination
    \/ \E i \in Node, j \in Node:
        \/ Terminate(i)
        \/ Wakeup(i)
        \/ SendMsg(i, j)
=============================================================================

Should be fixed. See here, and test.


feat: unit-tests

Agreed with the suggestions.

Agreed with the suggestions.

For the sake of posterity:
While updating this, I did investigate alternate testing frameworks. I did not see a distinct advantage to be gained for the time required to migrate the test. Unless the hand-rolled framework causes some unexpected friction, I don't see an advantage to changing at this time.
These tests were designed to be pinning tests. When we plan to refactor the implementation, we should reconsider a new testing framework at that time, and write the implementation in a manner than lends itself to be tested.

For the sake of posterity:
While updating this, I did investigate alternate testing frameworks. I did not see a distinct advantage to be gained for the time required to migrate the test. Unless the hand-rolled framework causes some unexpected friction, I don't see an advantage to changing at this time.
These tests were designed to be pinning tests. When we plan to refactor the implementation, we should reconsider a new testing framework at that time, and write the implementation in a manner than lends itself to be tested.


retry failure in Lock.acquire() may lead to an AttributeError

I've hit on the following exception, on at least one occasion:
.../lib/python2.7/site-packages/kazoo/recipe/lock.py:123, self._delete_node(self.node)", "'AttributeError: 'Lock' object has no attribute 'node'
Calling Lock.acquire(), whilst unconditionally raising RetryFailedError under Retry.call() reproduces the bug.

Wanna submit a PR for this? Probably something simple missing.

The patch is simple enough, but I don't have a reliable test-case. There is an edge case we're triggering in production, but those are rare.

I have a diff essentially ready for this, but want to make sure that I understand the philosophy right before I submit.
The repro I have is that if I create a lock to a path without a leading slash (eg, "foo/bar") and if I set the lock timeout lock enough, then I get the above error. This comes from the fact that in the first call to _inner_acquire, node is computed incorrectly, and with a sufficiently small timeout, there's never a second call to _inner_acquire. The fix I have makes the calculation of node more robust.
But the question I have is: are paths without leading slashed supported? I've been using them without problems so far (the leading slash is automatically added at some level, I believe). If the philosophy is that they should be supported, then I think my diff is good. But if not, then it seems like I should write a diff that adds assertions that no paths without leading slashes are provided.

Actually, I figured I'd just submit the PR and then let people decide if this is the way to go.

I can reproduce the original issue fairly easily, by emulating packet loss to the Zookeeper service. There's another related issue, caused by the same root issue.
In the 'startup' case, the lock node has not yet been created, and the ZK connection happens to drop at the start of _inner_acquire. The ensure/create calls then causes a RetryFailedError to be raised. The handler in acquire tries _best_effort_cleanup, but then lets execution continue. The _delete_node call at the end of acquire then fails, as self.node is undefined. This case i can reproduce maybe 5% of the time with 50% packet loss. Here's a backtrace snippet:
...
  File "<redacted>/kazoo/recipe/lock.py", line 195, in acquire
    self._delete_node(self.node)
AttributeError: 'Lock' object has no attribute 'node'

The "running" case is very similar, it just additionally requires that Lock.release was called at some previous point, which means that self.node is set to None. Connection dropping in _inner_acquire now causes:
...
  File "<redacted>/kazoo/recipe/lock.py", line 195, in acquire
    self._delete_node(self.node)
  File "<redacted>/kazoo/recipe/lock.py", line 300, in _delete_node
    self.client.delete(self.path + "/" + node)
TypeError: Can't convert 'NoneType' object to str implicitly


Fix extensions undefined

Fix for #122

@nprizal Thanks for fix 👍
Released as<EMAIL_ADDRESS>🎉


REQUEST: New membership for @yash-nisar

GitHub Username @yash-nisar
Requirements

[x] I have reviewed the community membership guidelines (https://github.com/dapr/community/blob/master/community-membership.md)
[x] I have enabled 2FA on my GitHub account. See https://github.com/settings/security
[x] I have subscribed to the Dapr community Discord server
[x] I am contributing (any of the following apply: issues, discussions, PRs, reviews) to 1 or more Dapr repositories

List of contributions to the Dapr project

https://github.com/dapr/dotnet-sdk/pull/929
https://github.com/dapr/dotnet-sdk/pull/951
https://github.com/dapr/dotnet-sdk/pull/942
https://github.com/dapr/dotnet-sdk/pull/962
https://github.com/dapr/dotnet-sdk/pull/1001
https://github.com/dapr/dotnet-sdk/pull/974
https://github.com/dapr/dotnet-sdk/pull/1051
https://github.com/dapr/components-contrib/pull/2123
https://github.com/dapr/components-contrib/pull/2082
https://github.com/dapr/components-contrib/pull/2040

CC @berndverst @ItalyPaleAle @halspang

👍🏻 I support this.
Long overdue actually.

👍

+1 binding

+1

Invite sent


ubuntu:latest

Used the kitematic gui to download the ubuntu:latest image and it's in stopped mode. Clicking restart does not launch it.
iMac OS X Yosemite.

This is intended behavior.
The Ubuntu-upstart image should solve this problem.


bug of opt awq model

Hi @zhuohan123, I found two bugs of opt awq model in the latest code because of the code refactor.

in https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/models/opt.py#L215, some opt model may not use quantized linear in project_in/project_out,
in https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/models/opt.py#L254, project_in/project_out have two return value

And for bloom awq model, I got the following error
    param = params_dict[name]
KeyError: 'transformer.h.0.mlp.gelu_impl.scales'

Hi @irasin, thanks for reporting the issue.
Regarding

in https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/models/opt.py#L215, some opt model may not use quantized linear in project_in/project_out,

Could you let us know which OPT model does not use quantized linears for these layers?


Should we adjust extension permissions for quicker review?

In submitting this extension to the Chrome Web Store, the following message came up:

Because of the following issue, your extension may require an in-depth review:

Broad host permissions
Instead of requesting broad host permissions or content script site matches, consider specifying the sites that your extension needs access to, or use the activeTab permission. Both options are more secure than allowing full access to an indeterminate number of sites, and may help minimize review times.

The activeTab permission allows access to a tab in response to an explicit user gesture.
{
...
"permissions": ["activeTab"]
}
If your extension only needs to run on certain sites, simply specify those sites in the extension manifest:
{
...
"permissions": ["https://example.com/*"]
}

I don't think Type-X would work as well without these broad permissions, so I submitted it for review, without changing this. However, @RoelN, do you think narrower permissions would still be as effective?

It made it onto the store eventually, so it’s this is no longer relevant.


[Documentation]: Qdrant client comment is outdated

Documentation Issue Description
client = qdrant_client.QdrantClient(
    # you can use :memory: mode for fast and light-weight experiments,
    # it does not require to have Qdrant deployed anywhere
    # but requires qdrant-client >= 1.1.1
    location=":memory:"
    # otherwise set Qdrant instance address with:
    # uri="http://<host>:<port>"                                    <=====  THIS LINE
    # set API KEY for Qdrant Cloud
    # api_key="<qdrant-api-key>",
)

The way this is used has changed: https://qdrant.tech/documentation/quick-start/
client = qdrant_client.QdrantClient("localhost", port=6333)

The comment (with options) seems wrong in a few places
Documentation Link
https://docs.llamaindex.ai/en/stable/examples/vector_stores/QdrantIndexDemo.html

Hi, if this issue is still open.  I would like to work on it.

Seems so: https://github.com/run-llama/llama_index/blob/main/docs/examples/vector_stores/QdrantIndexDemo.ipynb


⚠ Bofrost.at has degraded performance

In 8319e86, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1477 ms

Resolved: Bofrost.at performance has improved in 3616dbb after 6 minutes.


Unable to run tests for Safari Firefox IE (attachFile broken)!

What are you trying to achieve?
I want to upload a file on IE, FIREFOX, SAFARI, CHROME for browserstack local
What do you get instead?
I am unable to upload file on IE, FIREFOX and SAFARI. CHROME is working fine but others are broken. This is really annoying and forcing me to think about changing codeceptjs but I don't want to. How Can this be resolved?
File can't be transferred to remote server. Set `remoteFileUpload: false` in config to upload file locally.
this.browser.uploadFile is not a function

  Scenario Steps:

  - I.attachFile("Add", "sample.pdf") at Object.fillDealData (src/pages/raiseDeal.js:62:7)

I am also having this issue with Saucelabs. Firefox, IE, and Safari are unable to upload files when I connect to saucelabs from my terminal to execute my tests. Chrome works just fine. To clarify as well, here are my configs for Safari Firefox, IE and Chrome:
{
    "multiple": {
        "safari":{
            "browsers": [
                {
                    "browser": "safari",
                    "remoteFileUpload": false,
                    "desiredCapabilities": {
                        "platformName": "macOS 10.13",
                        "browserVersion": "12.1",
                        "sauce:options": {
                            "name": "Safari Suite - macOS"
                        }
                    }
                }
            ]
        },
        "chrome": {
            "browsers": [
                {
                    "browser": "chrome",
                    "desiredCapabilities": {
                        "platformName": "macOS 10.14",
                        "browserVersion": "latest",
                        "sauce:options": {
                            "name": "Chrome Baseline - macOS "
                        }
                    }
                },
                {
                    "browser": "chrome",
                    "desiredCapabilities": {
                        "platformName": "Windows 10",
                        "browserVersion": "latest",
                        "sauce:options": {
                            "name": "Chrome Baseline - Windows 10"
                        }
                    }
                }
            ]
        },
        "internet-explorer": {
            "browsers": [
                {
                    "browser": "internet explorer",
                    "remoteFileUpload": false,
                    "desiredCapabilities": {
                        "platformName": "Windows 10",
                        "browserVersion": "11.285",
                        "sauce:options": {
                            "name": "IE 11 - Windows 10"
                        }
                    }
                },
                {
                    "browser": "internet explorer",
                    "remoteFileUpload": false,
                    "desiredCapabilities": {
                        "platformName": "Windows 7",
                        "browserVersion": "11.0",
                        "sauce:options": {
                            "name": "IE 11 - Windows 7"
                        }
                    }
                }
            ]
        },
        "firefox": {
            "browsers": [
                {
                    "browser": "firefox",
                    "remoteFileUpload": false,
                    "desiredCapabilities": {
                        "platformName": "macOS 10.14",
                        "browserVersion": "68.0",
                        "sauce:options": {
                            "name": "Firefox 68 - macOS"
                        }
                    }
                },
                {
                    "browser": "firefox",
                    "remoteFileUpload": false,
                    "desiredCapabilities": {
                        "platformName": "Windows 10",
                        "browserVersion": "68.0",
                        "sauce:options": {
                            "name": "Firefox 68 - Windows 10"
                        }
                    }
                }
            ]
        }
    }
}

despite the error message in @stychu's comment, setting remoteFileUpload: false does not work to resolve the issue.

https://webdriver.io/blog/2019/06/25/file-upload.html
If you automate a browser that is running on a remote machine this approach won't work anymore because the file that is located locally (or wherever the tests are running) does not exist on the remote machine where the browser is running. For these scenarios the Selenium project created a file that is currently only supported when running Chrome or using a Selenium Grid with the Selenium standalone server.


refactor: remove ARGraphQLQueryCache native module

Co-authored-by: Pavlos Vinieratos<EMAIL_ADDRESS>The type of this PR is: Enhancement

This PR resolves []
Description
more info can be found here

removed ARGraphQLQueryCache native ios dep in favor of RelayCache
updated tests

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

removed ARGraphQLQueryCache native ios dep in favor of RelayCache - pvinis, gkartalis

This PR contains the following changes:

Dev changes (removed ARGraphQLQueryCache native ios dep in favor of RelayCache - pvinis, gkartalis)

  Generated by :no_entry_sign: dangerJS against 17e1ca0fdc8b619d11fb31b2f1dd1575aa92062e

Any suggestion on how best to QA this?

good point. for this, I'd say "make sure the app doesn't crash on ios and android".
we identified that relay cache is broken, so this PR should just do away with the native code, and in a separate ticket/spike/PR we need to actually make the cache work. possibly with a relay upgrade that you were talking about.


fetch hangs with node 20 when using the global agent

Running the following program:
import assert from 'assert';
import { h1NoCache } from '@adobe/fetch';

const fetchContext = h1NoCache();
const { fetch } = fetchContext;

const res = await fetch('https://httpbin.org/status/401');
assert.strictEqual(res.status, 401);

causes it to hang with node 20,  but not with node 18. The program no longer hangs with node 20 as well, as soon as I change the options for the context:
4c4
< const fetchContext = h1NoCache();
---
> const fetchContext = h1NoCache({ h1: { keepAlive: false } });

The extra h1 options cause @adobe/fetch to use its own agent in https://github.com/adobe/fetch/blob/195959dade3e9ccc646098a4c819113dd2f5b44c/src/core/h1.js#L34-L38
My guess is that the global agent somehow changed its behaviour in node 20.
Note: resetting the fetch context does not change this behaviour.

fixed via #469


v4 dropdown-header should be focusable for accesibility

In order to allow screen readers to read out dropdown headings, they should be focusable (but not actionalable), as dropdown headers help convey meaning to the drop-down items below them.
Such as this situation:

Without being able to "read" the dropdown-header, the user wouldn't know which context the "user" dropdown-item's are for.
The current alternative workaround is to add .sr-only text to the items that replicate the header text in each dropdown-item.

Gut feeling is that they should not be focusable, but rather that there needs to be a programmatic relationship between the headers and their respective links/options. Simplest (but most verbose) thing I can think of off the top of my head is an aria-describedby attribute on all the items pointing back to their respective header.

Yeah, that would be another option (aria-describedby)

Maybe just mentioning it in the docs would be a good enough "fix"...

docs should also have a good example of the solution in action. but yes, this will boil down to advice prose as well. will do some experimenting/testing with AT.

I found another markup that works well for dropdown headers and ARIA semantic markup that doesn't need aria-describedby:

Header 1

    Action One
    Action Two

Header 2

    Action One
    Action Two

By nature of above the markup, the headers automatically get associated with their respective dropdown items.

Are these any changes we need to make here or is this safe to close?

Closing as stale.
I confirmed that the above example does indeed still work as intended with at least the styling of dropdown menu items. Unsure if we need this added as an example in the docs, but if so, please feel free to open a PR for main that we could backport into v4-dev. Otherwise, I think this is safe to close.
<3

Closing as stale.
I confirmed that the above example does indeed still work as intended with at least the styling of dropdown menu items. Unsure if we need this added as an example in the docs, but if so, please feel free to open a PR for main that we could backport into v4-dev. Otherwise, I think this is safe to close.
<3


feat: CURP WAL codec

Based on: #562
Please briefly answer these questions:

what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)
There will be 6 PRs of the CURP WAL implementation, this is the 2nd part.

what changes does this pull request make?
This PR implements the WAL codec

are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)

Rebased


Doesn't work after v2.0.0 update.

Sorry to leave such a short comment, but it simply doesn't launch a server, like it used to!

The same here :)

Keymaps have changed since v2.0.0, have you used the new ones?

it stopped working after update i also try the new hotkey and try to launch the server from the packages area but it Doesn't launch
if issue not solved have to uninstall it  :(

Same issue here. I press all keymaps but that does nothing. Anyway, if I press, for example, ctrl+alt+3 it write me #. I don't know if it is a problem with spanish keyboard. I tried to change keymaps, but still not working. I've also tried to launch server going to Packages > atom-live-server > Start server and nothing happens.

I too am having issues after the update.

I just created a new user account on my MacOS, then do a clean install and it worked.
What OS and Atom version are you using?

In my case, last Atom version in Windows 10.

Ok, I'll find a Win10 and test on it.

Have you installed Node.JS on your machine?

I just published v2.1.0, and it uses atom built-in Node.JS to run the server, please upgrade and give it a try!

that update worked for me. Thanks jas!

Failed to spawn command /resources/app/apm/bin/node. Make sure /resources/app/apm/bin/node is installed and on your PATH. It shows this error in v2.1.0 The server does not start. I have also manually checked and the node is there but then also it is not working. I am using Ubuntu 16.04LTS

Failed to spawn command /resources/app/apm/bin/node. Make sure /resources/app/apm/bin/node is installed and on your PATH

I am using ArchLinux (kernel 4.9.8-1-ARCH).

2.0 was working for me on win 10 x64, I have node installed. 2.0.1 still works.

Same issue and same SO of @chetangulati . Node installed and in the path.

issue seems to be the node path
const node = path.resolve(
  process.execPath,
  process.platform === 'win32' ? '..' : '../../../../..' ,'resources/app/apm/bin/node'
);

it's working on windows so it must be the '../../../../..' part
can someone on mac or linux edit ".atom\packages\atom-live-server\lib\atom-live-server.js" and test

@MaherFa what should I change?

path.resolve joins multiple parts into a path
process.execPath is the path of the atom executable.
every ../ goes up one directory
knowing this, open atoms console and type:
path = require('path')
path.resolve(
process.execPath,
  '../../../../..' ,'resources/app/apm/bin/node')

you should get the correct path of node, if not then my guess is right and you may compare the path in console to the real path where node is. and add or remove ../ accordingly

this:
path = require('path')
path.resolve(
process.execPath,
'../../../../..' ,'resources/app/apm/bin/node')
give me: > resources/app/apm/bin/node
so I remove all the "../" for test in and get this new error.

Just published v2.1.1, it should fix the problem.

No Problem remains same for ubuntu

Node.js v7.5.0
npm v4.2.0
kernel v4.9.8 (ArchLinux)

What... I tested v2.1.1 on an Ubuntu machine and it worked 😢 .
Linux users, can you find your node path for me? Although I don't think I can support all the Linux distributions.
Or there are other solutions:

Run server using system installed Node.JS on Linux(You have to install yourself).
Let Linux users to set node path manually.

Previously it worked. Why was it necessary to change something? Oh…
Where do I need to specify my path /usr/bin/node?

Not working for win7 64 bit . have node installed as well

it still works for me, never stopped working the last 3 releases.
I start the server using ctrl+alt+3 or using menu packages > live-atom-server
ctrl + alt + 1 does not work tho
Windows 10 x64, atom latest x64
Node.js installed
atom's node is located in C:\Users\Maher\AppData\Local\atom\app-1.14.1\resources\app\apm\bin

just tested on macOS Sierra v10.12, latest atom and latest live-atom-server. I confirm it works as expected.
live-atom-server
path = require('path');
path.resolve(process.env.NODE_PATH, '../../app/apm/bin/node');

return the correct path to node (tested in terminal with -v):
/private/var/folders/3_/z_wts9vj2wvd471kmyk2g8740000gn/T/AppTranslocation/F2461D81-97AE-4F29-B0F5-8C66DE6BC21A/d/Atom.app/Contents/Resources/app/apm/bin/node
seems to be a linux issue so far.

But @ashu9394 says it doesn't work in Win7, I will keep investigate it.

Reinstalled 2.1.1 twice on Ubuntu now and it started working again.

thanks for all the support @jas-chen , i have reverted back to 1.2.5 that is working perfectly

just tested on a Win 7 SP1 x64 2.1.1, works perfectly.
I'm not able to get my hands on a machine running linux atm but i'd suggest adding an fs.existsSync check for node  path on linux os and if it returns false the user is presented with an electron openFile dialog that stores the path for reuse
or with a message directing on how to add it manually, though a dialog would be much better.

I think i have the same issue using ATOM BETA as IDE. If you just start ATOM the server launches normally, but if u close the tab on your browser or if u have some runtime errors the server crashes and it does not launch again, u have to restart ATOM to get another server.
i'm using win 7 64bits.
latest version of atom-live-server.
I succesfully replicated the the error on another machine, by just updating the plugin and trying to run.
I suggest ppl to rollback while the issue is not fixed.

@Terroristadoomad I don't think server will shut down when you close the tab on browsers 😕
And I'd like to know how you crash the server. May be I can add a force close server feature?

Just tested atom-live-server v2.1.1 on atom v1.15.0-beta3 on macOS 10.12.3, everything works fine...

@jas-chen Are we still able to open multiple files in different ports? I can run one file fine, through whatever port I open with control+at+  on a Mac Sierra. But I seem to need to close the current port to open a different file simultaneously.
Great package!

@rgdonohue this is not the general way to use this package, I assume that each web project have it's own port. You may consider split different files into different web projects.
I am going to close this issue since the main problem was solved. Thanks for all your feedback and participation.

@jas-chen Yes, this is I mean. Currently, if I have two+ projects open in Atom, I can only serve one with atom-live-server through any port. Cntr+alt + <port #> doesn't work until I stop the Live server, move the other project to the top of the sidebar, and then relaunch Live Server.

is there is any way to preview PHP live or any other plugin ????

Still doesn't work on OSX, Atom 1.18.0, Node 8.2.1. I get the same Failed to spawn command.

Update
I got it working by removing "nuclide" from Atom. I didn't reinstall it to try to see if it continues to work then, but it should, maybe there were some files conflicts.

I managed to fix it by editing the script located in:
~/.atom/packages/atom-live-server/lib
I found the location of Node in my system by typing the following in the terminal:
where node
then updated this line in the script with the correct path:
const node = path.resolve('/usr/bin/node');
This did the trick for me.


Sprites swaps textures for a frame

There is some strange flickering with textures sometimes.
It happens on both map and battle.
More prominent with battlers.

Consistently happens when the map scrolls horizontally to X = 0

It still happens sometimes, right?
So there may be a problem there for now...

Yes, on webGL mode there are still other things flickering on the screen.
In canvas mode I didn't find anything else, but I haven't checked inside battles yet.
Canvas mode is currently running in stable 60fps, while webGL runs in 20~40fps for me.

Strange because after the tilemap plugin was made I am having an steady 60 fps.
We may need to considerer the specs of each pc in order to view if the tilemap made with shaders is fast. (of course, on intel chips without graphical acceleration it may be slower than a vanilla implementation)

Im a bit busy, but next time i'll be available, I'll fix EVERYTHING in this conversion.

Oh, I didn't use the tilemap plugin yet.

Try to use it, it will run better


running tfx extension --help using 0.6.4 tries to connect to internet

I just tried to upgrade to tfx-cli 0.6.4 and for some reason when I display help it's trying to connect to visualstudio.com.
tfx-cli 0.5.10 doesn't do this.  What's happening?

C:\Users\Paul.Abrams>tfx extension --help
TFS Cross Platform Command Line Interface v0.6.4
Copyright Microsoft Corporation
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 1)
(node:7196) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 2)
(node:7196) PromiseRejectionHandledWarning: Promise rejection was handled asynch
ronously (rejection id: 2)
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 4)
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 5)
Available commands and command groups in tfx / extension:

isvalid: Show the validation status of a given extension.

create: Create a vsix package for an extension.

publish: Publish a Visual Studio Marketplace Extension.

share: Share an Azure DevOps Extension with Azure DevOps Organizations.

show: Show info about a published Azure DevOps Services Extension.

init: Initialize a directory for development of a new Azure DevOps extension.

install: Install a Azure DevOps Extension to a list of Azure DevOps Organizat
ions.

unshare: Unshare a Azure Devops Extension with Azure DevOps Organizations.

resources: Commands for working with localization of extensions.

publisher: Commands for managing Visual Studio Marketplace Publishers.

For help with an individual command, type tfx extension  --help
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 6)
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 7)
(node:7196) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.v
ssps.visualstudio.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:7196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 8)
C:\Users\Paul.Abrams>

Sorry about that. We now make an http request to get the URL for the Marketplace. Since the --help option actually loads commands to figure out what their options are, it was making this request simply by loading these commands. Will have it fixed in the next update.


Update docker.js

Hey, I think this pull request may be better redirected to the following repo https://github.com/terra-rebels/oracle-feeder. Thank you for contribution, I encourage you to continue contributing !


Support multiple interface / network definitions

This is a partial solution to support multiple interfaces. Note that the PR does not enable a way to specify multiple interfaces in the spec (after all, we don't have any interface types but pod at this time). This PR merely makes virt-launcher to not panic when we will actually add support for additional types.
The reason why this PR does not include new integration tests is because we can't at the moment validate multiple interfaces end to end due to reasons described above. To facilitate testing, the PR includes some unit tests though. Later PRs to support additional interface types will need to include integration tests with multiple interfaces.
The reason why we don't want to hold off the PR before we have all code to validate multiple interfaces support end to end is because multiple authors will need to work on different new interface types in parallel (proxy, dp...), and this basic bit is commonly needed for all of them, and we don't want to duplicate it in these parallel efforts.

The latest upload covers all Roman's comment except the one about a better way to find a pod interface which I addressed with a comment in the thread. There is also a small TODO to cover, and maybe functional test failures, in case they show up.

retest this please

Since the default podNetwork will be added automatically, make sure that it gets a random name and not hard-coded "default" to avoid collisions.

It's getting added automatically if no other network (no network at all) is defined.
If at least one network is defined, then it will not be added.
Is this above true?
if it is, then we could stick to the defined named default, not?

It's getting added automatically if no other network (no network at all) is defined.
If at least one network is defined, then it will not be added.

We agreed on adding an explicit opt-out with a field: autoAttachPodInterface: false. See https://docs.google.com/document/d/10rXr91aqn8MvVcLgHw33WX8BaQwHPZERp25PHxoZGgw/edit

"
Default configuration
If not spec.domain.interfaces list is provided, then a default vNIC with a connection to the stock Kubernets pod network will be connected.
VM without network interfaces
The user can opt-out of the default connection mechanism by setting spec.domain.autoAttachPodInterface to false:
"
Thus in the current situation it would only be created if the list of interfaces is empty.
To opt out of the empty list behavior we have the switch.
IOW If there are interafces defined, then the default network would not be added.
I'm just quoting the doc - not saying it should stay like this.
I need to think a little baout it to make my mind up if we should (unconditionally) always add the default network, or just in case of an empty list.

Thus in the current situation it would only be created if the list of interfaces is empty.
To opt out of the empty list behavior we have the switch.

Then you don't need the random name.

I'm just quoting the doc - not saying it should stay like this.

It is fine. I misread it.

The latest upload has the following changes:

we now set alias for domain interfaces to corresponding spec interface names, and use the alias as a back reference to spec interface / network in podinterface.go instead of relying on clunky "br1" / "bridge" type matching;

fixed converter code to honor spec interfaces (and not add a pod network regardless of spec, as it did before);

we no longer add a pod interface if networks are explicitly defined in spec;

since we no longer add a default interface unless the spec list is empty, we no longer have a risk of name clash, so the code to randomize default interface names is ripped off (I still stored it in a private branch for if / when we decide it's a better path forward.)

The latest upload is just a rebase after VM -> VMI rename.

retest this please

The latest upload is another rebase to accommodate for new git conflicts. @rmohr @vladikr may I ask you to review the PR? Thanks!

retest this please


Adds 'errorResponseHandler' to HBApplication to allow HBHTTPResponseErrors to be intercepted and a custom response returned

As promised, this is the second PR. It introduces the ability to handle a HBHTTPResponseError and provide a custom response, falling back to the default implementation in HTTPResponder using HBHTTPResponseError if the errorResponseHandler is not provided.
The reason for this PR is that I wanted to continue using standard HBHTTPErrors e.g. HBHTTPError(.notFound) at the higher-levels of the application, but have the ability to create/manipulate a custom response in-place of the ones provided by HBHTTPResponseError itself at a global level.

Hi can I ask how you are using Hummingbird. Are you using hummingbird-core or are you just using the router elements of Hummingbird?
If it is the latter I have a minor change which will resolve this for you. The only reason I catch errors in HTTPResponder.respond is for a logging. Instead of converting them to an HBHTTPResponse at the that point I can return them as an error.
If it is the former you could use a Middleware to catch all the errors and process them eg
struct ErrorMiddleware: HBMiddleware {
    public func apply(to request: HBRequest, next: HBResponder) -> EventLoopFuture<HBResponse> {
        return next.respond(to: request).flatMapErrorThrowing { error in
            try processError(error)
        }
    }
}

Thanks Adam, I think the middleware might do the trick. I’m effectively using Hummingbird to proxy requests elsewhere that aren’t matched by the router (whilst still having some paths matched and handled by the router).

Thanks Adam, I think the middleware might do the trick. I’m effectively using Hummingbird to proxy requests elsewhere that aren’t matched by the router (whilst still having some paths matched and handled by the router).

Make sure it is the first middleware you add to ensure you catch errors from any other middleware

I think LambdaErrorMiddleware definitively points me in the right direction - thanks again!

The middleware approach worked perfectly - didn’t even need to change any of the code, just shifted it into the middleware. Thanks again Adam.


Support Django 2.2

Description: Describe in a couple of sentence what this PR adds
This PR adds support for Django 2.2 LTS
Dependencies: dependencies on other outstanding PRs, issues, etc.

https://github.com/vintasoftware/drf-rw-serializers/issues/14

Merge deadline: List merge deadline (if any)
None.
Installation instructions: List any non-trivial installation
instructions.
None.
Testing instructions:
None.
Reviewers:

[ ] tag reviewer
[ ] tag reviewer

Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[ ] Version bumped
[ ] Changelog record added
[ ] Documentation updated (not only docstrings)
[ ] Commits are squashed
[ ] PR author is listed in AUTHORS

Post merge:

[ ] Create a tag
[ ] Check new version is pushed to PyPi after tag-triggered build is
finished.
[ ] Delete working branch (if not needed anymore)

Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.

Hi, @hugobessa! That sounds pretty good, thanks a lot!