Error “Reading State"

Hi, there seems to be a error that causes the entire module to stop responding. Log shows repeated copies of this message:
Reading 'state' to '0x000d6ffffeff6164' failed: 'Error: Read 0x000d6ffffeff6164/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Cannot request when znp has not been initialized yet)’

Also in the log is repeated:
Rejecting unresolved promise after 7255ms ("0x086bd7fffe519524|1”)

This seems to be a repeated issue requiring a restart of the server (raspberry pi), restarting the service is not working.

Can you tell me which dongle are you using (and firmware)? Also, which device did you pair?

Sure:
Dongle: CC2531
Firmware: CC2531ZNP-2018090201.hex (as specified here)
And I paired an Ikea socket
The socket works (I have about 8 paired) and is functional ~80% of the time. This error shows up about 2/3 times a week and requires a hard reboot of the server.

Uhm, I think that one is a bit outdated, can you try reflashing with this?
https://github.com/Koenkk/Z-Stack-firmware/tree/master/router/CC2531

I will give updating the stick firmware a go. (hopefully I wont have to re-pair everything!)
I think I have managed to make the error slightly more reproducible. I have a scene set in apple home (called “night”) that turns everything in the house off but it also turns off “allow Zigbee join” and “Zigbee Touchlink”. It seems to be that when I run this scene the plug-in dies!
I was able to catch the log right as it happened:
[10/10/2020, 23:49:38] [ZigBee] Starting touchlink factory reset...
[10/10/2020, 23:49:47] [ZigBee] Writing 'state' to '0x000d6ffffeff6164' failed: 'Error: Command 0x000d6ffffeff6164/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (AREQ - AF - dataConfirm after 9000ms)'
[10/10/2020, 23:49:47] [ZigBee] Writing 'state' to '0x086bd7fffe519524' failed: 'Error: Command 0x086bd7fffe519524/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (AREQ - AF - dataConfirm after 9000ms)’```

Ah! Tochlink should not be "touched" until you really want to factory reset some device, because it changes the status of the dongle and set it to a different mode. I would suggest to move out from the scene the two virtual buttons

Hi! I'm confused here... I'm having a lot of troubles and I thought that reflashing the dongle would solve it. I saw your suggestion @madchicken about the new version, however you point to a "router" version and not  to a "coordinator". And coordinator in that repository is the old one. I flashed with the router version and it is not recognized now, so I will go back to the previous version. Can you clarify this for me?

Hi! I still running with problems. After one or two days the raspberry start receiving errors from the Zigbee. The only way to recover is to unplug the raspberry (no command makes it work, even reboot).
Node version 12.19
Plugin version 1.0.5
UI version 4.31.0
Log:
[11/4/2020, 18:26:32] [ZigBee Hub] Cannot configure device TRADFRI ON/OFF switch: Bind 0x14b457fffec8d738/1 genOnOff from '901' failed (SREQ '--> ZDO - bindReq - {"dstaddr":50395,"srcaddr":"0x14b457fffec8d738","srcendpoint":1,"clusterid":6,"dstaddrmode":1,"dstaddress":"0x0000000000000385","dstendpoint":255}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))
[11/4/2020, 18:26:43] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:27:12] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:27:18] [ZigBee Hub] New state for 0xec1bbdfffea92099 { state: 'ON', brightness: 125 }
[11/4/2020, 18:27:36] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:27:42] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:28:01] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:28:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:28:11] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON' }
[11/4/2020, 18:28:22] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no resources' (26))'
[11/4/2020, 18:28:30] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:28:49] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:28:55] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
Rejecting unresolved promise after 8651ms ("0x00124b001f79d7f0|11")
Rejecting unresolved promise after 8646ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:29:14] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:29:20] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:29:38] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:29:43] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255 }
[11/4/2020, 18:29:46] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:29:46] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON', brightness: 255 }
[11/4/2020, 18:29:56] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no resources' (26))'
Rejecting unresolved promise after 9287ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:30:08] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
Rejecting unresolved promise after 9918ms ("0x00124b001f79d7f0|11")
Rejecting unresolved promise after 9900ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:30:21] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:30:33] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:30:46] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
Rejecting unresolved promise after 8095ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:30:58] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:03] [ZigBee Hub] Can't find message in queue for key 0xec1bbdfffea92099|1 [
  {
    timestamp:<PHONE_NUMBER>582,
    message: '0x00124b001f79d7f0|11',
    promise: DeferredPromise {
      resolve: [Function],
      reject: [Function],
      promise: [Promise]
    }
  },
  {
    timestamp:<PHONE_NUMBER>587,
    message: '0x00124b001f79d7f0|11',
    promise: DeferredPromise {
      resolve: [Function],
      reject: [Function],
      promise: [Promise]
    }
  }
]
[11/4/2020, 18:31:03] [ZigBee Hub] Device state (GL-C-009):  {}
[11/4/2020, 18:31:07] [ZigBee Hub] Device state (GL-C-009):  { state: 'ON' }
[11/4/2020, 18:31:07] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:31] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:31] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:56] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:31:56] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON', brightness: 255, brightness_percent: NaN }
Rejecting unresolved promise after 6125ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:32:04] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:06] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no resources' (26))'
[11/4/2020, 18:32:29] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:37] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":61,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,241,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] Writing 'state' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":63,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,243,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:32:54] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:32:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:02] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:18] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] Writing 'state' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":87,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,253,1]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:33:23] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:33:23] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":8,"transid":88,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[1,254,4,254,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:33] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'Timeout' (9999))'
[11/4/2020, 18:33:33] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:33:47] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:33:57] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:34:13] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:34:21] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:34:42] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:34:46] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:35:07] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
Rejecting unresolved promise after 6761ms ("0x00124b001f79d7f0|11")
Rejecting unresolved promise after 6754ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:35:10] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:35:31] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:35:33] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:35:58] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:36:08] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
Rejecting unresolved promise after 5554ms ("0x00124b001f79d7f0|11")
[11/4/2020, 18:36:23] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:36:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:36:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:36:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:13] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:14] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:37] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:39] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:39] [ZigBee Hub] Reading 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":8,"transid":229,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,35,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:37:39] [ZigBee Hub] Writing 'state' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":230,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,36,1]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:37:39] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:37:39] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":8,"transid":231,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[1,37,4,254,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:37:40] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:40] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:40] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:37:40] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:40] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:37:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:03] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:06] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:38:19] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:30] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":27,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,58,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:38:44] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":28,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,59,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:38:44] [ZigBee Hub] Reading 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":8,"transid":29,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,60,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:38:44] [ZigBee Hub] Writing 'state' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":30,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,61,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:38:44] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:44] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:38:58] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":47,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,70,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:39:00] [ZigBee Hub] Writing 'state' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":18121,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":48,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,71,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
[11/4/2020, 18:39:00] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:38] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:49] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:52] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:39:59] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:40:17] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:40:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:40:42] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:40:49] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:03] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:03] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:03] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:17] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:28] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:41:31] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'ON', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:41:41] [ZigBee Hub] Writing 'brightness' to '0x00124b001f79d7f0' failed: 'Error: Command 0x00124b001f79d7f0/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no resources' (26))'
[11/4/2020, 18:41:42] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:04] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:05] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:34] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:51] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:59] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:42:59] [ZigBee Hub] New state for 0x00124b001f79d7f0 { state: 'OFF', brightness: 255, brightness_percent: NaN }
[11/4/2020, 18:43:16] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:43:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:43:40] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:43:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:05] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:19] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:30] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:32] [Broadlink RM] Projector getSwitchState: false
Rejecting unresolved promise after 6857ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 6853ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 6844ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 6840ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 6823ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 6818ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 6814ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 6810ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 6806ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 6801ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 6798ms ("0xec1bbdfffe951e3f|1")
Rejecting unresolved promise after 6794ms ("0xec1bbdfffe951e3f|1")
[11/4/2020, 18:44:43] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:44:48] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:12] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:12] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:45:35] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:00] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:15] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:24] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:39] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:46:40] [Broadlink RM] Projector getSwitchState: false
Rejecting unresolved promise after 8165ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 8161ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 8152ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 8148ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 8144ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 8140ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 8136ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 8132ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 8128ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 8109ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 8105ms ("0xec1bbdfffe951e3f|1")
Rejecting unresolved promise after 8101ms ("0xec1bbdfffe951e3f|1")
[11/4/2020, 18:46:56] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:03] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:21] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:29] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:46] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:47:54] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:48:01] [ZigBee Hub] No response from Zigbee LED controller dimmer. Is it online?
[11/4/2020, 18:48:19] [ZigBee Hub] No response from TRADFRI LED bulb GU10 400 lumen, dimmable. Is it online?
[11/4/2020, 18:48:31] [ZigBee Hub] Reading 'state' to '0xec1bbdfffe9ea5ff' failed: 'Error: Read 0xec1bbdfffe9ea5ff/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:48:44] [ZigBee Hub] Reading 'state' to '0xec1bbdfffe9cdbbd' failed: 'Error: Read 0xec1bbdfffe9cdbbd/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:48:55] [ZigBee Hub] Reading 'brightness' to '0xec1bbdfffe9ea5ff' failed: 'Error: Read 0xec1bbdfffe9ea5ff/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:49:09] [ZigBee Hub] Reading 'brightness' to '0xec1bbdfffe9cdbbd' failed: 'Error: Read 0xec1bbdfffe9cdbbd/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:49:21] [ZigBee Hub] Reading 'state' to '0xec1bbdfffe1b8410' failed: 'Error: Read 0xec1bbdfffe1b8410/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:49:24] [Broadlink RM] Projector getSwitchState: false
Rejecting unresolved promise after 9626ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 9622ms ("0xec1bbdfffe1cab14|1")
Rejecting unresolved promise after 9614ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 9610ms ("0xec1bbdfffe9cdbbd|1")
Rejecting unresolved promise after 9606ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 9603ms ("0xec1bbdfffe1b8410|1")
Rejecting unresolved promise after 9598ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 9594ms ("0xec1bbdfffe1c9011|1")
Rejecting unresolved promise after 9589ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 9585ms ("0xec1bbdfffe9ea5ff|1")
Rejecting unresolved promise after 9566ms ("0xec1bbdfffe951e3f|1")
Rejecting unresolved promise after 9562ms ("0xec1bbdfffe951e3f|1")
[11/4/2020, 18:49:34] [ZigBee Hub] Reading 'state' to '0xec1bbdfffe1c9011' failed: 'Error: Read 0xec1bbdfffe1c9011/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:49:45] [ZigBee Hub] Reading 'brightness' to '0xec1bbdfffe1b8410' failed: 'Error: Read 0xec1bbdfffe1b8410/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
[11/4/2020, 18:49:59] [ZigBee Hub] Reading 'brightness' to '

Ok, same problem appeared in the Zigbee2Mqtt and it was solved in 1.15.0 version. I'm trying to figure out what is the reason and how to solve it.
https://github.com/Koenkk/zigbee2mqtt/issues/4307

It seems there is a firmware that is more stable now (source routing). We should definitely try it. I will updated dependencies in the meanwhile

I’ve already tested changing the router fw but does not solves the problem, also in the z2m thread they tested with original fw.
The problem was solved in the z2m code but I cannot figure out how.
Manuel Portela, PhD
Cel Es. +34 600 851 104
Follow me: @Portela_Man
manuchis.net
El 7 nov 2020 13:26 +0100, Pierpaolo Follia<EMAIL_ADDRESS>escribió:

It seems there is a firmware that is more stable now (source routing). We should definitely try it. I will updated dependencies in the meanwhile
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I can confirm that I am still having this issue every 2/3 days. Still not 100% sure what is causing it but avoiding the touchlink buttons doesn't seem to have resolved it. Further error messages:
[11/11/2020, 16:26:10] [ZigBee] Reading 'state' to '0x680ae2fffe7d5012' failed: 'Error: Read 0x680ae2fffe7d5012/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SRSP - AF - dataRequest after 6000ms)'

It seems that zigbee2MQTT doesn't face this issue but I would like to continue using this plugin due to the ease of adding devices.

I can confirm that I am still having this issue every 2/3 days. Still not 100% sure what is causing it but avoiding the touchlink buttons doesn't seem to have resolved it. I can confirm that rebooting the server reoslves the issue but restarting homebridge does not. Perhaps power cycling the dongle is what is required? Further error messages:
[11/11/2020, 16:26:10] [ZigBee] Reading 'state' to '0x680ae2fffe7d5012' failed: 'Error: Read 0x680ae2fffe7d5012/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SRSP - AF - dataRequest after 6000ms)'

It seems that zigbee2MQTT doesn't face this issue but I would like to continue using this plugin due to the ease of adding devices. Unfortunately, I don't think I am able to offer any technical support with this one!

I have my zigbee devices turned off for a week now...
My last errors were:
[11/12/2020, 14:00:44] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'

It's looks like that I have to map everything again, but I don't know at this point if it would work to take the time to do it.
I'm also thinking on changing strategies because keep this plugin running is a lot of effort. I found "homebridge-z2m" plugin that would directly connect it to z2m but I don't know yet how stable is it.

I'll take a look at this later today. I am having a lot of trouble upgrading and maintaining this plugin for lack of time 😞

Can some of you test the branch v1.0.6? It is just an update of dependencies...

Hi @madchicken thanks for your effort. I  would like to help but I'm not enough expert here.
v1.0.6 its failinng to compile
yarn run v1.22.5
warning<EMAIL_ADDRESS>The engine "homebridge" appears to be invalid.
$ yarn clean && yarn build-ts
warning<EMAIL_ADDRESS>The engine "homebridge" appears to be invalid.
$ rimraf dist/
warning<EMAIL_ADDRESS>The engine "homebridge" appears to be invalid.
$ tsc
src/zigbee/zigbee.ts:273:26 - error TS2554: Expected 2 arguments, but got 0.

273     return this.herdsman.touchlinkFactoryReset();
                             ~~~~~~~~~~~~~~~~~~~~~~~

  node_modules/zigbee-herdsman/dist/controller/controller.d.ts:48:27
    48     touchlinkFactoryReset(ieeeAddr: string, channel: number): Promise<boolean>;
                                 ~~~~~~~~~~~~~~~~
    An argument for 'ieeeAddr' was not provided.

Found 1 error.

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I found "homebridge-z2m" plugin that would directly connect it to z2m but I don't know yet how stable is it.

I spoke to the developer of that and it currently does not support switches or a "add to zigbee" button.

@EdwardChamberlain I fix the compilation issue. Testing it now on my local raspberry.

@EdwardChamberlain @manuchis I spend a couple of hours trying to understand if zigbee2mqtt has differences with this plugin. I did not find many different things in the code between the two. I fixed a couple in the v1.0.6 branch, but I doubt they will make differences for your problem. I have the plugin up and running here and I don't see any issue. Did you try the new branch?

It is weird because I still get the network error and I believe I have to pair everything again, however I cannot delete devices from cache. After doing so, I restart the homebridge but they come up again. I understand that the zigbee DB doessn’t exist anymore, right? do I have to do anything else?
[11/17/2020, 19:28:05] [ZigBee Hub] Reading 'state' to '0x00124b001f79d7f0' failed: 'Error: Read 0x00124b001f79d7f0/11 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'

Manuel Portela, PhD
Cel Es. +34 600 851 104
Follow me: @Portela_Man
manuchis.net
El 17 nov 2020 17:22 +0100, Pierpaolo Follia<EMAIL_ADDRESS>escribió:

@EdwardChamberlain @manuchis I spend a couple of hours trying to understand if zigbee2mqtt has differences with this plugin. I did not find many different things in the code between the two. I fixed a couple in the v1.0.6 branch, but I doubt they will make differences for your problem. I have the plugin up and running here and I don't see any issue. Did you try the new branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

The database is stored into the homebridge config folder. To remove old devices you need to delete the db and do a factory reset of them. I would also clear the homebridge accessories cache

Yes, to unlink them you need to factory reset them unfortunately

So if they are linked, I don’t know why I get the network error.
Manuel Portela, PhD
Cel Es. +34 600 851 104
Follow me: @Portela_Man
manuchis.net
El 18 nov 2020 17:04 +0100, madchicken/homebridge-zigbee-nt<EMAIL_ADDRESS>escribió:

Yes, to unlink them you need to factory reset them unfortunately

Si, I’ve re linked all the devices today and everything is working. Let’s see what happens during this week.
Manuel Portela, PhD
Cel Es. +34 600 851 104
Follow me: @Portela_Man
manuchis.net
El 18 nov 2020 17:19 +0100, Manuel Portela<EMAIL_ADDRESS>escribió:

So if they are linked, I don’t know why I get the network error.
Manuel Portela, PhD
Cel Es. +34 600 851 104
Follow me: @Portela_Man
manuchis.net
El 18 nov 2020 17:04 +0100, madchicken/homebridge-zigbee-nt<EMAIL_ADDRESS>escribió:

Yes, to unlink them you need to factory reset them unfortunately

Well, after some days running 1.0.6 it seems that everything is stable. I got some warnings and "no response" but the homebridge service doesn't crash.

I seem to still be getting the issue with an "unresolved promise" on 1.0.6 sadly.

Please, try 1.0.9

This issue is been (finally) solved in 1.1.0 version (still in unstable state ATM). You can try it by doing
`npm I homebridge-zigbee-nt@unstable -g`

This issue is been (finally) solved in 1.1.0 version (still in unstable state ATM). You can try it by doing
`npm I homebridge-zigbee-nt@unstable -g`

I haven't seen this issue since I have been running on 1.1.0 and in general, the whole system seems more responsive. Looks promising! Will keep an eye on it.

I haven't seen this issue since I have been running on 1.1.0 and in general, the whole system seems more responsive. Looks promising! Will keep an eye on it.

Fixed in v1.1.0

Fixed in v1.1.0

Running on 1.1.2 I have picked up a few unresolved promises which could be related to slow performance:
Rejecting unresolved promise after 9935ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 9920ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 9886ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 9412ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 9409ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 9405ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 9401ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 9381ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 6414ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 6408ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 6402ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 6396ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 6371ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 5906ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 5901ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 5897ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 5893ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 5861ms ("0x680ae2fffe770c4f|1”)

This is the following log (incase its any use):
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:55:02] [ZigBee] Decoded state from incoming message { occupancy: false }
[1/6/2021, 19:55:02] [ZigBee] Updating state of device TRADFRI motion sensor:  { occupancy: false }
[1/6/2021, 19:57:33] [ZigBee] Zigbee message from 0xec1bbdfffed0a229 commandOn
[1/6/2021, 19:57:33] [ZigBee] Decoded state from incoming message { action: 'on' }
[1/6/2021, 19:57:33] [ZigBee] Updating state of device TRADFRI shortcut button:  { action: 'on' }
[1/6/2021, 19:57:34] [ZigBee] Reading 'state' from '0x680ae2fffe7d5012, message in queue 0x680ae2fffe7d5012|1'
[1/6/2021, 19:57:34] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/6/2021, 19:57:34] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse

Running on 1.1.2 I have picked up a few unresolved promises which could be related to slow performance:
Rejecting unresolved promise after 9935ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 9920ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 9886ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 9412ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 9409ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 9405ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 9401ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 9381ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 6414ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 6408ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 6402ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 6396ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 6371ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 5906ms ("0x000d6ffffeff6164|1")
Rejecting unresolved promise after 5901ms ("0x086bd7fffe519524|1")
Rejecting unresolved promise after 5897ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 5893ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 5861ms ("0x680ae2fffe770c4f|1”)

This is the following log (incase its any use):
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:36] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe519524 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x086bd7fffe3521ed readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse
[1/6/2021, 19:52:37] [ZigBee] Zigbee message from 0x680ae2fffe770c4f readResponse
[1/6/2021, 19:55:02] [ZigBee] Decoded state from incoming message { occupancy: false }
[1/6/2021, 19:55:02] [ZigBee] Updating state of device TRADFRI motion sensor:  { occupancy: false }
[1/6/2021, 19:57:33] [ZigBee] Zigbee message from 0xec1bbdfffed0a229 commandOn
[1/6/2021, 19:57:33] [ZigBee] Decoded state from incoming message { action: 'on' }
[1/6/2021, 19:57:33] [ZigBee] Updating state of device TRADFRI shortcut button:  { action: 'on' }
[1/6/2021, 19:57:34] [ZigBee] Reading 'state' from '0x680ae2fffe7d5012, message in queue 0x680ae2fffe7d5012|1'
[1/6/2021, 19:57:34] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/6/2021, 19:57:34] [ZigBee] Zigbee message from 0x680ae2fffe7d5012 readResponse


Azure.Security.KeyVault.Secrets Readme issue

Section link

Suggestion:
Add hyperlink for Conduct FAQ  https://opensource.microsoft.com/codeofconduct/faq/
@jongio for notification

PR merged.


After failing BgSave once, the system won't persist any changes

If the background save fails once, the system continues to respond. However any changes are not persisted anymore by redis. This problem seem to appears randomly when under heavy load.
Log file:
[5936] 12 Jun 15:30:09.399 # BeginForkOperation: system error caught. error code
=0x00000000, message=Forked Process did not respond in a timely manner.: unknown
error
[5936] 12 Jun 15:30:09.399 # Can't save in background: fork: Invalid argument
Client response:
<IP_ADDRESS>:6379> bgsave
(error) ERR Background save already in progress
<IP_ADDRESS>:6379> save
(error) ERR Background save already in progress
PS. I'm using the code as of 12 june 9 GMT

I have also been experiencing this problem on 2.8.12.
It seems to occur randomly under periods with lots of writes, potentially also when the CPU for our VM is under a heavy load.
It seems like the fork timeout is occurring after around 14 seconds.


Readiness probe failed for both Admin and MS

Upon the deployment of domain, both admin and ms server readiness probe are failing.
The domain is active but the readiness probe never recovers, thus it is difficult to integrate with Istio.
Warning  Unhealthy  27s (x4 over 42s)  kubelet, <IP_ADDRESS>  Readiness probe failed: Get http://<IP_ADDRESS>:8001/weblogic/ready: dial tcp <IP_ADDRESS>:8001: connect: connection refused
Warning  Unhealthy  4m14s  kubelet, <IP_ADDRESS>  Readiness probe failed: Get http://<IP_ADDRESS>:7001/weblogic/ready: dial tcp <IP_ADDRESS>:7001: connect: connection refused
Deployment Type: Model in image (base version: weblogic:<IP_ADDRESS>-dev)
Cluster: Openshift Cluster

Can you take a look at the logs of the pods (admin server and managed servers) to see if the WLS servers have reached RUNNING state.  Would like to see the state of the servers.

@abinashkd  What version of istio are you using?  istio 1.6.x is broken with headless service and will never work with WKO.

It was an configuration issue with istio readiness port, which is default to 8888, but I have configured it for 7001. Now pointing to 8888 got it working. Thanks @lennyphan @jshum2479


Updated FWLink Id for Clear-RecycleBin

PR Summary
PR #10909 added Clear-RecycleBin back into PS v7. This PR updates the FWLink to point to the v7 help content.
PR Context
This is related to #10909
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@sdwheeler you need to update https://github.com/PowerShell/PowerShell/blob/master/test/powershell/engine/Help/assets/HelpURI/V3Cmdlets.csv#L64


Add release notes for 0.3.0.

Codecov Report

Merging #11 (fdc548a) into main (13f45c7) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head fdc548a differs from pull request most recent head f838f5a. Consider uploading reports for the commit f838f5a to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   98.56%   98.56%
=======================================
  Files           9        9
  Lines         488      488
=======================================
  Hits          481      481
  Misses          7        7


How to provide multiple confidence interval in prophet?

As, of now it's something like this : m <- prophet(df, interval.width = 0.95)
Can I give multiple confidence interval values like : m <- prophet(df, interval.width = c(0.75,.95))  ?

No, but you can get finer grained information about the posterior using the predictive_samples function from the v0.2 branch (see documentation here: https://github.com/facebookincubator/prophet/blob/v0.2/R/R/prophet.R#L939). You pass this the same inputs as predict, but it will return all of the posterior samples rather than quantiles. You can then compute quantiles as you wish.
You can install the v0.2 branch from github using devtools:
devtools::install_github('facebookincubator/prophet', subdir='R', ref='v0.2')

This is now available in v0.2 in CRAN.


TAJO-1967: Replace 'try finally' with 'try' with resources

Reports try finally statements which can use Automatic Resource Management of Java 7 or higher.

@jihoonson Thanks for your review. I apply your comment. Please review this PR again.

+1 LGTM!


Added ctx object to all system struct's methods

The idea behind this commit is to set the stage for the following features:

logging - by adding context Values for logging purposes
timeout/cancellation - move this up the stack and slowly add support for all resources where this makes sense

Checklist

[ ] make test-all (UNIX) passes. CI will also test this
[ ] unit and/or integration tests are included (if applicable)
[ ] documentation is changed or added (if applicable)

Description of change

Busy PR, lots of boring work to wire this up.. but hopefully this opens the door for some future features/flexibility.
One thing I wasn't 100% sure on is whether to have Validate() take ctx, or it instantiates it based on the yaml config.
My high level thoughts are:

Validate() - creates a new context and sets the timeout based on the value in yaml (or default)
ValidateValue(..) - adds some values to the ctx object for logging purposes
command.Stdout(ctx) - the system/ struct will then be able to log with the values from ValidateValue, and will timeout when the context is cancelled.

Possible alternatives
Pass ctx only to the constructors, that would bring a lot of simplicity to the codebase as most of it would remain unchanged. Also, don't think any of the system resources have methods that require different timeouts.
I'll create another simpler PR with that approach and we can discuss how they compare.

went with #837 instead


[TypeScript] Namespace 'Phaser.Types.Renderer.WebGL' has no exported member 'WebGLPipelineUniformsConfig'

Version

Phaser Version: 3.55.0

Operating system: Linux

Browser: -

Description

There is an error in the TypeScript definitions:
Namespace 'Phaser.Types.Renderer.WebGL' has no exported member 'WebGLPipelineUniformsConfig'

I don't find any file with the WebGLPipelineUniformsConfig name in the Phaser code.

I think the problem is here: https://github.com/photonstorm/phaser/blob/5552079c9d23a883e10bef7318f6b924c9538c96/src/renderer/webgl/WebGLShader.js#L139

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Great! That's fixed. But I get another error now :(

../../../types/phaser.d.ts(10112,13): error TS2416: Property 'destroy' in type 'GameObject' is not assignable to the same property in base type 'EventEmitter'.
  Type '(fromScene: boolean) => void' is not assignable to type '() => void'.

I think if the fromScene parameter is set as optional then it fixes the error.


[WIP] Extract vendors

This is a work in progress branch exploring the issues / design for extracting vendor code: google, aqt, pasqal into separate modules within the repo.
RFC: http://bit.do/cirq-packaging-strategy
Roadmap item: #3228.
I will break this up into smaller PRs as things clarify.
TODOs before final design:

[X] create separate packages, and import them to cirq.google, cirq.aqt, cirq.pasqal
[X] make CI pass (coverage, readthedocs, etc.)
[ ] confirm that Google protos still work

[x] experiment with notebooks shows that they do
[ ] have @dstrain115 look at this branch and play with it

[x] collect feedback on a second round of design / strategy discussions and incorporate it into a plan of execution
[x] add OWNERS file structure
[x] dedupe version handling
[ ] test out release process

[x] figure out what to do with "unstable" packages - are we going to have cirq-google-unstable, cirq-aqt-unstable and cirq-pasqal-unstable? I guess so.
[ ] test / automate the release process, so that things are released together - and figure out what happens when something goes wrong in the middle - as we can't make this atomic, and also pypi versions can't be reused / mutated

Things to do after the merge:

[ ] add devsite config for API docs (although this can come) to get to a similar setup as tft and tft_beam

I'm going to close this and start with the extraction of the riskiest module: cirq.google instead. Also it's outdated so it's a bit painful to keep merging it. I do have answers to most of the questions now except for cirq.google's internal testings.


Reduce likelihood of malformed SOTemplate

During the code review of https://github.com/ripple/rippled/pull/2854, @mellery451 asked about the consequences of some added throws.  It was noted that those throws could result in a malformed SOTemplate being left behind.  This pull request sits atop https://github.com/ripple/rippled/pull/2854 and does its best to address that issue.
Formerly an SOTemplate was default constructed and, later, its elements added using push_back().  This left open the possibility of a malformed SOTemplate if adding one of the elements caused a throw.
With this commit the SOTemplate requires an initializer_list of its elements at construction.  Elements may not be added after construction.  With this approach either...

The SOTemplate is fully constructed with all of its elements or
The constructor throws, which prevents an invalid SOTemplate from even existing.

This change requires all callers of the SOTemplate constructor to be adjusted at the call site.  Those changes are also in this commit.
The SOE_Flags enum is also renamed to SOEStyle, which harmonizes the name with other uses of the enum in the code base.  SOEStyle enumerators are renamed (slightly) to have an soe prefix rather than SOE_.  This heads toward reserving identifiers with all upper case for macros.  The new style also aligns with other prominent enums in the code base like the collection of TER identifiers.
SOElement is adjusted so it can be stored directly in an STL container (by using std::reference_wrapper).  Previously SOElement needed to be stored in a std::unique_ptr which could be stored in an STL container.  As a result of this change unique_ptr usage is removed from both SOTemplate and KnownFormats.
Only the top-most commit needs to be reviewed. That commit sits atop two other unmerged pull requests:

https://github.com/ripple/rippled/pull/2854 (its immediate predecessor) and
https://github.com/ripple/rippled/pull/2770 (which underlies https://github.com/ripple/rippled/pull/2854 ).

I'm assuming that both of the underlying pull requests will be merged and the top-most commit of this branch can be merged afterwards (assuming it passes code review).

Jenkins Build Summary
Built from this commit
Built at 20190228 - 00:51:44
Test Results

Build Type
Log
Result
Status

msvc.Debug
logfile
1142 cases, 0 failed, t: 625s
PASS :white_check_mark:

gcc.Release -Dassert=ON, MANUAL_TESTS=true
logfile
915 cases, 0 failed, t: 6m9s
PASS :white_check_mark:

docs, TARGET=docs
logfile
1 cases, 0 failed, t: 0m2s
PASS :white_check_mark:

gcc.Debug -Dcoverage=ON, TARGET=coverage_report, SKIP_TESTS=true
logfile
1145 cases, 0 failed, t: 17m17s
PASS :white_check_mark:

clang.Debug
logfile
1145 cases, 0 failed, t: 3m15s
PASS :white_check_mark:

msvc.Debug, NINJA_BUILD=true
logfile
1142 cases, 0 failed, t: 638s
PASS :white_check_mark:

rpm
logfile
1145 cases, 0 failed, t: n/a
PASS :white_check_mark:

gcc.Debug
logfile
1145 cases, 0 failed, t: 3m29s
PASS :white_check_mark:

clang.Debug -Dunity=OFF
logfile
1145 cases, 0 failed, t: 10m48s
PASS :white_check_mark:

clang.Release -Dassert=ON
logfile
1145 cases, 0 failed, t: 5m43s
PASS :white_check_mark:

gcc.Debug -Dunity=OFF
logfile
1145 cases, 0 failed, t: 10m30s
PASS :white_check_mark:

msvc.Debug -Dunity=OFF
logfile
1142 cases, 0 failed, t: 1288s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF
logfile
1145 cases, 0 failed, t: 3m28s
PASS :white_check_mark:

gcc.Release -Dassert=ON
logfile
1145 cases, 0 failed, t: 6m11s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF -DBUILD_SHARED_LIBS=ON
logfile
1145 cases, 0 failed, t: 3m26s
PASS :white_check_mark:

gcc.Debug, NINJA_BUILD=true
logfile
1145 cases, 0 failed, t: 3m4s
PASS :white_check_mark:

msvc.Release
logfile
1142 cases, 0 failed, t: 414s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=address, PARALLEL_TESTS=false, DEBUGGER=false
logfile
1145 cases, 0 failed, t: 1m12s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=undefined, PARALLEL_TESTS=false
logfile
1145 cases, 0 failed, t: 5m17s
PASS :white_check_mark:

Even though this pull request has three passing reviews, I won't mark it as passed until the two underlying pull requests (https://github.com/ripple/rippled/pull/2770 and https://github.com/ripple/rippled/pull/2854) are passed and/or merged.

Rebased to the most recent develop and also built on top of the most recent (and passed) versions of https://github.com/ripple/rippled/pull/2770 and https://github.com/ripple/rippled/pull/2854.  Those two pull requests will shortly be marked closed not due to any problems with them, but to prevent accidentally merging them into develop twice.


airdrops.rb

FILE
ActiveAdmin.register Airdrop do
 actions :all, except: :destroy

 includes :store

 menu parent: 'Stores', label: 'Airdrops'

 permit_params :store_id, :airdrop_type, :name, :description, :blockchain, :token_symbol, :currency, :exchange_rate,
               :status, :active, :completed_at,
               :recipients_csv

 action_item :admin_send_airdrop_tokens, only: :show do
   if resource.pending? && resource.active
     a 'Send Tokens to Airdrop Recipients', href: admin_send_airdrop_tokens_admin_airdrop_path(resource)
   end
 end

 member_action :admin_send_airdrop_tokens do
   resource.send_airdrop_tokens
   flash[:notice] = "Sending airdrop tokens to recipients has been scheduled"
   redirect_to [:admin, resource]
 end

 form  html: { multipart: true } do |f|
   f.semantic_errors *f.object.errors.attribute_names
   f.inputs do
     panel 'Airdrop Status' do
       f.input :status, as: :select, collection: Airdrop::AIRDROP_STATUS
       f.input :completed_at, as: :datepicker, datepicker_options: { min_date: 1.day.ago.to_date, max_date: "+0" }
     end
     panel 'Airdrop Info' do
       para ''
       f.input :airdrop_type, as: :select, collection: Airdrop::AIRDROP_TYPES
       f.input :name
       f.input :store, as: :select, collection: Store.active
       f.input :description
       para ''
       f.input :blockchain, as: :select, collection: WalletAddress::BLOCKCHAINS
       para ''
       f.input :token_symbol, as: :select, collection: WalletAddress::CRYPTOCURRENCIES.keys
       para 'cryptocurrency symbol'
       f.input :currency, as: :select, collection: ['USD']
       para ''
       f.input :exchange_rate
       para '1 <token_symbol> = exchange_rate X <Currency> (1 OPAIG = 0.01 USD)'
       para "
".html_safe
       f.input :active
     end

     panel 'Airdrop Recipients', 'data-panel': :collapsed do
       para 'Upload csv file and save to import airdrop recipients. To import more recipients, simply replace the file'
       para ''
       f.input :recipients_csv, as: :file
       para ''
       para 'CSV Format must include these headers with data:'
       para "participation, ref1, balance, wallet_address, token_balance".html_safe
       para "5,0,5,wallet_address, 500".html_safe
     end
   end
   f.actions
 end
end

This code configures the admin interface for managing Airdrop records in an ActiveAdmin panel within a Ruby on Rails application. Here's a detailed explanation of what's happening:
File: airdrop.rb
1. ActiveAdmin.register Airdrop do

Registers the Airdrop model with ActiveAdmin, creating an admin interface for managing Airdrop records.

2. actions :all, except: :destroy

Enables all default CRUD actions except for the destroy action, preventing users from deleting Airdrop records via the admin interface.

3. includes :store

Eager loads the associated store when querying Airdrop records, improving performance by reducing the number of database queries.

4. menu parent: 'Stores', label: 'Airdrops'

Places the Airdrop resource under the Stores menu with the label Airdrops in the ActiveAdmin interface, helping to organize the admin panel by grouping related resources together.

5. permit_params :...

Specifies the parameters allowed to be mass-assigned through the ActiveAdmin interface. This includes attributes like store_id, airdrop_type, name, description, blockchain, token_symbol, currency, exchange_rate, status, active, completed_at, and recipients_csv.
This ensures only permitted attributes can be modified, protecting against mass-assignment vulnerabilities.

6. action_item :admin_send_airdrop_tokens, only: :show do ... end

Adds a custom action button to the show page for sending airdrop tokens to recipients.
The button is only shown if the Airdrop is in a pending state and is active.
The button is labeled "Send Tokens to Airdrop Recipients" and links to a custom action (admin_send_airdrop_tokens).

7. member_action :admin_send_airdrop_tokens do ... end

Defines a custom action for sending airdrop tokens.
Calls the send_airdrop_tokens method on the Airdrop model, which likely handles the process of distributing tokens to recipients.
Sets a flash message "Sending airdrop tokens to recipients has been scheduled" and redirects back to the show page for the Airdrop.

8. form html: { multipart: true } do |f| ... end

Customizes the form for creating and editing Airdrop records.
The form is configured to support file uploads (multipart: true).

The form is divided into several panels:

Airdrop Status:

Inputs for status (a dropdown with the AIRDROP_STATUS options) and completed_at (a datepicker for selecting the completion date).
The datepicker is restricted to dates from the previous day up to the current date.

Airdrop Info:

Inputs for airdrop_type (a dropdown with AIRDROP_TYPES), name, store (a dropdown with active stores), description, blockchain (a dropdown with blockchain options), token_symbol (a dropdown with cryptocurrency symbols), currency (a dropdown with currencies, here only 'USD'), exchange_rate, and active.
The form also includes some descriptive text (para) to guide the admin on how to fill in the fields, especially concerning the exchange_rate.

Airdrop Recipients:

A file input (recipients_csv) for uploading a CSV file containing the airdrop recipients.
The panel includes instructions on how to format the CSV file, specifying the required headers (participation, ref1, balance, wallet_address, token_balance).

Summary:

This file configures the ActiveAdmin interface for managing Airdrop records, including customizations for the form, listing, and actions.
It provides a way to send tokens to airdrop recipients via a custom action, ensuring that only active and pending airdrops can initiate this process.
The form is carefully structured to collect all necessary data for an airdrop, including file uploads for recipient data and options for setting the status, blockchain, and other important fields.

This setup offers a comprehensive and user-friendly interface for managing airdrop campaigns within the application, with all necessary controls and validations in place.


Trim the indentation on macros which heuristically appear to use block-style indentation

Fixes https://github.com/rust-lang-nursery/rustfmt/issues/3174.
Avoids re-introducting issues similar to https://github.com/rust-lang-nursery/rustfmt/issues/1712.

In Issue 1712 an example is presented where trimming the leading whitespace on lines of an unparsable macro provides undesirable behavior.
It appears to me that the issues of the sort will most frequently be a result in differences in indentation strategy between the macro's grammar and rust's grammar.  I would imagine over time that macro grammar's would diverge more and more from rust given the new function-like proc macro support, for things like sql!(SELECT * FROM example).
Implemented Solution
This change uses a heuristic to determine whether the macro uses C-like delimiters and rustfmt-like "Block" indent-style and applies a de-dent if it matches (reusing existing behavior for brace! {} macros; which handles all the edge-cases like string literals).
Specifically it checks that the last line of the macro (after being trimmed) contains only a sequence of ), ], or } characters and no other characters or whitespace.

Thanks!


UI Graph Disturbed for turned on "Lograthmic" and "Uniform" options

Describe the bug
UI graph labels are disturbed for the graph
To Reproduce

Turn on the toggle for "Lograthmic" and  "Uniform"
Overlap Y-axis Labels is disturbed. Also the graph line comes above the numbers
Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Browser
13.1.1 Safari

/available

/claim


Not yet perfect

And - I suspect - not likely to ever be.... I don't know where you're at physically, but in the US, we sometimes talk of whack-a-mole. You can look it up, but it basically relates to situations (I'm sure this is ONE SUCH) where no sooner do you provide something USEFUL ... but which Instagram HATES ... than they do something to make it fail. I'm glad I installed it and it definitely works some of the time. You have a screenshot of an Asian girl, and her images download beautifully. Here's my "fail" - https://www.instagram.com/frankinjection/p/CwAb4TEoRE_/?img_index=1
I tried it on both Chrome & Firefox & no down arrow appears. Feel free to email me at peter [at] mossandfreud.com
Very minor thing. The extension name on Chrome & Firefox is different. Maybe, you cannot control that, but if you can, you should. You have the makings of a beautiful brand AND a great product! (I'm using it to collect some great photos of Prague, and it's working great on at least one of those.)

I have searched whack-a-mole, you are right, I have to keep the extension updated when Instagram change their pages or api.

https://www.instagram.com/frankinjection/p/CwAb4TEoRE_/?img_index=1

The reason why the extension doesn't work at this link is that I have't encountered a post detail url with a username in it 🤷♀. Usually when I open a post from the user profile page, there is no username in the url. So I didn't write code to be compatible with this situation. But because of your feedback, this problem has been fixed in the latest version(1.5.0).
As for why the extension name on Chrome & Firefox is different, well, they are same from the beginning and that's what I want. But on Chrome, it was taken down by the complaint from Instagram, so I had no choice but to put a different name on it.

I wanted to keep the same name, but I couldn't think of anything related to Instagram downloads that wouldn't get complaints.

THANK you so very much.... Your English is so extraordinarily excellent
that I have to think that you either have an English-speaking parent ... or
you're amazing at languages ... or translation software has gone from
awfully ragged to first rate in 40 (?) years.
But mostly, I'm impressed that you solved it (and "published") so very
quickly. You have a great deal to be proud of with this extension. Whoever
employs you is very fortunate to have someone so good on their staff!!
There seem to be at least 2 other similar extensions out there, and it
occurs to me that they - which also didn't work on my target site - may not
be as bad as I thought they were. You're right about its being tough to
operate in a world where Instagram can certainly make life difficult for
people like you - in at least 2 ways. It's also the case that, I'm sure,
"reviews" are pretty arbitrary. I think at least 1 person each said that
those 2 extensions were "garbage." That's why I - fortunately - looked even
harder and found yours!
ONE of the 2 alternative extensions has a nice feature you might be
interested in replicating. They provide a single down-arrow as you do, but
the other author also has an icon with 3 such arrows next to one another,
and ITS function is to download ALL the images in a given "reel." I've done
enough coding to know that "easy to say" is often very far from "easy to
do," but my "experience" with you and what turned out to be a minor bug is
such that I imagine you could accomplish this in no more than an hour or 2.
AGAIN, thanks ... and a very happy & healthy 2024 to you!
-JC
On Sat, Jan 6, 2024 at 11:23 PM konka @.***> wrote:

I have searched whack-a-mole, you are right, I have to keep the extension
updated when Instagram change their pages or api.
https://www.instagram.com/frankinjection/p/CwAb4TEoRE_/?img_index=1
The reason why the extension doesn't work at this link is that I have't
encountered a post detail url with a username in it 🤷♀. Usually when I
open a post from the user profile page, there is no username in the url. So
I didn't write code to be compatible with this situation. But because of
your feedback, this problem has been fixed in the latest version(1.5.0).
As for why the extension name on Chrome & Firefox is different, well, they
are same from the beginning and that's what I want. But on Chrome, it was
taken down by the complaint from Instagram, so I had no choice but to put a
different name on it.
Luckily, there weren't too many complaints on Firefox.
image.png (view on web)
https://github.com/TheKonka/instagram-download-browser-extension/assets/22173084/e05de5b6-8634-4486-b0d1-7d14eff74f0d
I wanted to keep the same name, but I couldn't think of anything related
to Instagram downloads that wouldn't get complaints.
—
Reply to this email directly, view it on GitHub
https://github.com/TheKonka/instagram-download-browser-extension/issues/15#issuecomment-1879933411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFE4CULYBTOVE2W4PPLM2BTYNIPNRAVCNFSM6AAAAABBPSYDDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZHEZTGNBRGE
.
You are receiving this because you authored the thread.Message ID:
@.***
.com>

I may have to take back some of my praise. That is - YOU WERE FAST, ... but
either Instagram is even faster (VERY UNLIKELY) or you missed something.
With both Firefox & Chrome - a different machine, so there can be no
question of my using something other than 1.5 - one gets "download failed"
when clicking on your arrow on the site in question:
Prague is really one of the most beautiful & picturesque cities in the
world. I was stoked to be back and have some downtime to explore… |
Instagram
https://www.instagram.com/frankinjection/p/CwAb4TEoRE_/?img_index=1
I hope you CAN fix this, of course. I'll be looking for an email from you
to that effect, but please - DO TEST any patch you think addresses the
issue.
On Sat, Jan 6, 2024 at 11:23 PM konka @.***> wrote:

I have searched whack-a-mole, you are right, I have to keep the extension
updated when Instagram change their pages or api.
https://www.instagram.com/frankinjection/p/CwAb4TEoRE_/?img_index=1
The reason why the extension doesn't work at this link is that I have't
encountered a post detail url with a username in it 🤷♀. Usually when I
open a post from the user profile page, there is no username in the url. So
I didn't write code to be compatible with this situation. But because of
your feedback, this problem has been fixed in the latest version(1.5.0).
As for why the extension name on Chrome & Firefox is different, well, they
are same from the beginning and that's what I want. But on Chrome, it was
taken down by the complaint from Instagram, so I had no choice but to put a
different name on it.
Luckily, there weren't too many complaints on Firefox.
image.png (view on web)
https://github.com/TheKonka/instagram-download-browser-extension/assets/22173084/e05de5b6-8634-4486-b0d1-7d14eff74f0d
I wanted to keep the same name, but I couldn't think of anything related
to Instagram downloads that wouldn't get complaints.
—
Reply to this email directly, view it on GitHub
https://github.com/TheKonka/instagram-download-browser-extension/issues/15#issuecomment-1879933411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFE4CULYBTOVE2W4PPLM2BTYNIPNRAVCNFSM6AAAAABBPSYDDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZHEZTGNBRGE
.
You are receiving this because you authored the thread.Message ID:
@.***
.com>

rs-1704718354140-664057249.webm
This is strange. I can download the media without any errors. 🤷♀
I can only suspect that the page structure is different for different users.
For the time being, you can try to see if you can save the image by right clicking on it.
I'll try to fix the problem later.

Any idea why it won't work on the following:  https://www.instagram.com/philsnelgrove/reel/B5GeRJoBAc1/
Works as expected on the link in the OP, so the plugin is definitely enabled.

Any idea why it won't work on the following: https://www.instagram.com/philsnelgrove/reel/B5GeRJoBAc1/
Works as expected on the link in the OP, so the plugin is definitely enabled.

The reason is similar to the above, I haven't tested the reel page with username on the route.
This issue has been fixed in latest version (1.5.1) . Thanks for the feedback!
The chrome version has been updated, the Firefox version is still under review.

Appreciated, looking forward to the update!


Fix backup/restore for the embedded server

This PR addresses improper internal port configuration at embedded DB startup. We received a user report (https://github.com/weaviate/weaviate/issues/6570) that backups created with the embedded DB always fail.
I was able to reproduce this for all versions >= 1.25.0, indicating that this issue was somehow related to Raft (which was introduced in 1.25.0)
The wrongly-configured internal cluster communication ports resulted in the raft port for the node being set to the same port as the gossip protocol data_bind_port (which is used to transmit data from node to node). This caused all intra cluster comms to fail. We never noticed this before because the embedded DB does not support multi-node mode. However, backups are an edge case here, because all backups are treated as if they were distributed, so all backup comms require making requests to the intra cluster server.
So now this is fixed, and if we ever decide to support clustering for embedded DB, we are one step closer :)

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

Project coverage is 90.03%. Comparing base (dee9f6b) to head (9d4f948).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1485      +/-   ##
==========================================
+ Coverage   89.94%   90.03%   +0.08%
==========================================
  Files         174      174
  Lines       14919    14940      +21
==========================================
+ Hits        13419    13451      +32
+ Misses       1500     1489      -11

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


WIP: New Audio (seek/stream)

This will update a few things, but is not complete (will update this PR when I finish it)

sokol_args had extra semicolons that were preventing web-build on Linux
void pntr_seek_sound(pntr_sound* sound, int timeMs) that will allow you to set the time-offset of sounds
void pntr_set_audio_stream_handler(pntr_audio_stream_handler* cb) that will allow you to make audio-stream (with callback) for more advanced usecases (custom instruments and dynamic-out, like making a music-tracker)
Currently, all sound stuff uses audio elements, but it could be also done with an AudioContext (similar to callback setup) for gapless looping & better management, overall.

These API changes can serve as a prototype for similar changes on other backends, and will not change any other part of the audio API.

I think I have the basic system worked out, but there appears to be a new unrelated problem that happens due to security-change, so it is hard to get a test build going to see if it worked:
index.js:1396 Uncaught ReferenceError: SharedArrayBuffer is not defined
    at UTF8ArrayToString (index.js:1396:65)
    at UTF8ToString (index.js:1445:20)
    at _emscripten_set_window_title (index.js:5679:22)
    at index.wasm:0x46e5
    at index.wasm:0x44c8
    at index.wasm:0xb64b
    at index.wasm:0xb196
    at index.js:870:12
    at callMain (index.js:6380:15)
    at doRun (index.js:6437:23)

I am going to drop this in favor or #120 merging, and I can work out the rest after that.


fix(radio): fix the baseline of radio buttons

Fix the ngModel on the checkbox as well.
Fixes #357, #638.

R: @jelbourn @robertmesserle @kara

Also added a new demo page for baseline. Please use it :)

LGTM

LGTM


Sign up page and Login Page

[x] create a basic Layout  for Pages
[x] Start working on CSS and Responsiveness of Pages
[x] start on Functionality of Pages
[x] create the reducer for it and set up auth context if requires

Task Completed.


Phone number text field could open a number keyboard

In the gallery, we have text field demo. One of the fields is for a phone number. Currently, it opens a text keyboard. We could instead open a number keyboard.
This can then show the developer how to open different keyboards, and also how to configure an input widget as "only numbers".
From the gallery:

From the contacts app on android:

@mpcomplete not sure how easy this is to configure. If easy, let's try to do it for the first version. If it takes a bunch of plumbing, then we can move to the next release. Thanks!

The plumbing should all be there already.  You just need to supply the appropriate http://docs.flutter.io/flutter/material/Input/keyboardType.html

Great, thanks for the tip!

Oh duh.. that didn't even occur to me. Fixing.

Closed by https://github.com/flutter/flutter/pull/3983
Thanks for the quick turnaround!


NIFI-8195: add default connection settings to process group configura…

…tion

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Adds properties to the Process Group configuration setting the default values for all newly created connections. This facilitates easier configuration during flow creation especially with multi-tenancy in mind. There are 3 properties added: default flowfile expiration, default back pressure object threshold, default back pressure data size threshold.
See updated User Guide for additional information.
The new behavior includes a basic unit test. It was also tested extensively in a running NiFi as some features are heavily UI-dependent.
Verified the new elements of the Process Group (PG) DTO are populated into flow.xml.gz when NiFi is started using an older format, i.e. without the new elements included
Verified the values of the added elements are “0 sec” for FlowFile Expiration, and obtained from nifi.properties for back pressure settings
Verified PG settings are displayed as non-editable when user is not in the ‘modify the component’ policy.
Verified PG settings are displayed as “Unauthorized” when user is not in the ‘view the component’ policy.
Verified new connection defaults change as the PG settings change
Verified the settings of existing connections do not change as the PG settings change
Verified newly created PG inherits strings from parent
Verified settings of existing child PG do not change as parent PG settings change
Verified User Guide documentation updated and displays correctly
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[x] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Reviewing...

+1 LGTM, tried various PGs, downloaded the flow definition and ensured all connections looked as expected. Thanks for this feature! Merging to main

Thanks for the contribution and thanks for spending the time to review @mattyb149 . But I think this PR is problematic.
The Jira spells this out as adding a default backpressure at the Process Group level. I don't think this is necessary, but I don't necessarily have a problem with it. However, the PR doesn't appear to update VersionedProcessGroup, which means that after it's been pushed to the registry and then pulled out again, the newly created one will not function like the old one did - it won't have the default settings. That needs to be addressed.
However, more concerning is the introduction of the default FlowFile Expiration. We should not be introducing FlowFile Expiration without the user explicitly setting it. This was discussed at length previously in https://github.com/apache/nifi/pull/4800

I also saw some warnings about the unrecognized new fields:
Schema validation error parsing Flow Configuration at line 26, col 32:
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'defaultFlowFileExpiration'. One of '{processor, inputPort,
outputPort, label, funnel, processGroup, remoteProcessGroup,
connection, controllerService, template, variable,
parameterContextId}' is expected.
2021-06-24 14:13:10,369 WARN [main] org.apache.nifi.util.FlowParser
Schema validation error parsing Flow Configuration at line 1195, col
34: cvc-complex-type.2.4.a: Invalid content was found starting with
element 'defaultFlowFileExpiration'. One of
'{versionControlInformation, processor, inputPort, outputPort, label,
funnel, processGroup, remoteProcessGroup, connection,
controllerService, template, variable, parameterContextId}' is
expected.
2021-06-24 14:13:10,433 WARN [main] org.apache.nifi.util.FlowParser
Schema validation error parsing Flow Configuration at line 1915, col
34: cvc-complex-type.2.4.a: Invalid content was found starting with
element 'defaultFlowFileExpiration'. One of
'{versionControlInformation, processor, inputPort, outputPort, label,
funnel, processGroup, remoteProcessGroup, connection,
controllerService, template, variable, parameterContextId}' is
expected.```

At this point I think the PR needs to be reverted, we can continue discussions on Github and/or Jira, but it seems the PR wasn't ready as-is.