'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100

[homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
could you give me some information where to look for this to correct in the code?
It is awesome plugin and I am really happy to have ct200 and all radiator valves are in HomeKit, it is just super!

Hmm, that is a very strange bug. As far as I'm aware there isn't any endpoint that even returns such a high value.
Do you have any way of reproducing this issue? Is this something that happens constantly, or is it a one-time thing? Did the plugin continue to work normally after this warning, or did it break?
As for where in the code this could happen: platform.ts: lines 48-83
It's quite a far-fetched guess, BUT, it could be that radiator valves have different /zone/list output than regular ct200, which could explain the wrong value. Though that still doesn't explain how (anything) it returned reached a value of 1000.
It would be best if you run
bosch-xmpp easycontrol --serial="SERIAL" --access-key="ACCESS" --password="PASSWORD" get /zones/list and post the output here
(you might not have that tool, in which case, you can install it with sudo npm install -g bosch-xmpp

I have 8 of these valves, added them as zones. It was hard to identify which one is which on HomeKit but I think it exposes in the order of rooms in the easy control app (I have mymode app but it is the same) so bug just appeared 6:17 am 6:18 and 6:37 then it didn't appear again, this is my first day with valves, had just thermostat before and plugin continues to work after the error. I will give it another day to monitor.

{"id":"/zones/list","type":"zoneArray","writeable":0,"recordable":0,"value":[{"id":1,"name":"VGhlcm1vc3RhdA==","icon":"others","program":1,"temp":22.9,"status":"idle"},{"id":2,"name":"QmVkcm9vbQ==","icon":"guest room","program":2,"temp":21.6,"status":"idle"},{"id":3,"name":"QmF0aHJvb20=","icon":"bathroom","program":3,"temp":22.4,"status":"idle"},{"id":4,"name":"R2FsbGVyeQ==","icon":"study","program":3,"temp":22.6,"status":"idle"},{"id":5,"name":"TGl2aW5ncm9vbQ==","icon":"living room","program":1,"temp":23.05,"status":"idle"},{"id":6,"name":"TWVsaXNzYQ==","icon":"kids room","program":1,"temp":22.8,"status":"idle"},{"id":7,"name":"RW50ZXJhbmNl","icon":"storage","program":1,"temp":22.9,"status":"idle"}]}
I think i have seen this behavior before in another temperature related plugin, samsung AC to be precise. sometimes HomeKit is not getting the temperature from device via plugin and there has to be default value for that situation for HomeKit to expose like 21 or 15 and that removes this error. I might be completely wrong. I don't see anything unusual in my zone list, please see above.

after installing bosch xmpp and running to get zones, i got the below error on homebridge 4x.
Unhandled rejection Error: HTTP_TOO_MANY_REQUESTS
at /usr/lib/node_modules/homebridge-ct200/node_modules/bosch-xmpp/lib/base-client.js:213:25
at tryCatcher (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (node:internal/timers:464:21)

I'm pretty sure it's not due to default value, because there already is one. Regarding the HTTP_TOO_MANY_REQUESTS, that's due to Bosch having some API limits, though I don't know the exact amount.

understood, thanks, I will monitor and let you know. If it happens around the same time tomorrow then definitely something to do with my instance only.

Hi, I have just received the same error message. I'll keep you updated on this as well.

I have not seen this error today, i guess something has happened with my connectivity or from bosch xmpp response yesterday like a coincidence. I will monitor further but I don't think this is happening because of the plugin bug.
I have a another question, is there a way to reboot c200 thermostat via plugin or via bosch xmpp npm? I have a problem, sometimes that easy control or mymode app in my case is not opening with error "connection error retry", but during this time I can see the thermostat in my wifi and all HomeKit accessories working fine. Like it is fully working but iOS app, mymode (easy control) is failing to open because of connectivity or something. I have seen this few times already, the only way for me to fix this is to unplug the thermostat from wall and replug. Which is not good if I am not home, this is not possible basically. and there are many things I will have to do from main IOS app, HomeKit is limited. I am also sure this is nothing to do with your plugin but I would appreciate if you know a command to reboot the ct200 from bosch xmpp command line, this would solve my problem. Thanks a lot!

I finally have had this issue again, basically when ct200 loses connection to TRVs and this happens. Maybe due to updating ct200 or whatever reason when CT200 cannot communicate with TRVs, it throws 100 C or even higher and thus HB errors this but HomeKit was showing 100C. Something to do with the default values when not getting it from ct200 directly. I got tons of it until 10 minutes later my ct200 app tells me your device is restarted and then all went well.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.

I finally have had this issue again, basically when ct200 loses connection to TRVs and this happens. Maybe due to updating ct200 or whatever reason when CT200 cannot communicate with TRVs, it throws 100 C or even higher and thus HB errors this but HomeKit was showing 100C. Something to do with the default values when not getting it from ct200 directly. I got tons of it until 10 minutes later my ct200 app tells me your device is restarted and then all went well.
[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.

Hi, I used to get the same error message until I found out that one of my radiator thermostat have died and lost connection to the Bosch app. This is why homebridge is spitting out multiple error messages as it can’t read the room’s current temperature.

I finally have had this issue again, basically when ct200 loses connection to TRVs and this happens. Maybe due to updating ct200 or whatever reason when CT200 cannot communicate with TRVs, it throws 100 C or even higher and thus HB errors this but HomeKit was showing 100C. Something to do with the default values when not getting it from ct200 directly. I got tons of it until 10 minutes later my ct200 app tells me your device is restarted and then all went well.

[12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:19 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:09:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:27 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:10:39 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:11:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:12:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:13:35 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [12/24/2021, 12:14:29 PM] [homebridge-ct200] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 1000 exceeded maximum of 100. See https://git.io/JtMGR for more info.

Hi, I used to get the same error message until I found out that one of my radiator thermostat have died and lost connection to the Bosch app. This is why homebridge is spitting out multiple error messages as it can’t read the room’s current temperature.

Exactly, the same reason. My all TRVs lost connection I could tell from the original app, due to some update or reboot I don't know. Until they are connected again HB error was repeating itself. This is something, I guess, could ignored with the code or logs will be overloaded in case of some longer connection issues.

I'll change the code to ignore values over 100, should get rid of the errors.

Turns out I had this fixed since Dec 9th, but forgot to publish the changes 😄, new version is up. Closing.
Please re-open the issue if you still encounter this issue with the new version (2.1.4), since I don't have these radiator thermostats and can't test for myself.

Thanks a lot, i see you pushed two more updates :) it would be nice to see the versioning in the GitHub to see what are the changes. It is nice to have, not very important.

Didn't see a need in writing changelog, since commit log has version tags and commit messages, so it's easy to see what was changed between certain versions.

Ah can’t wait to see the update making this plugin better and more reliable.

After recent updates I am getting a lot of these, not sure if played with it too much so it exceeds limits or just a coincidence or really are there more requests generated via plugin after recent updates? :)
Unhandled rejection Error: HTTP_TOO_MANY_REQUESTS
at /usr/lib/node_modules/homebridge-ct200/node_modules/bosch-xmpp/lib/base-client.js:213:25
at tryCatcher (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (node:internal/timers:464:21)
Unhandled rejection Error: HTTP_TOO_MANY_REQUESTS
at /usr/lib/node_modules/homebridge-ct200/node_modules/bosch-xmpp/lib/base-client.js:213:25
at tryCatcher (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/node_modules/homebridge-ct200/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (node:internal/timers:464:21

Yeah I’m getting those messages as well.

If anything, the 2.1.4 should have reduced request count (zone status from every 1 min to every 2 min and humidity/localization from every 5 min to every 10 min). If I had to guess, when you have a lot of devices (e.g. 5 or more), then during initialization it sends out a huge amount of requests simultaneously. (4 + 2x, where x is number of devices), which triggers the request limit.
It's hard to judge what request limit the API has. With that info I could tweak the request timings.
If this HTTP_TOO_MANY_REQUESTS problem persists open a separate issue.


[SPARK-13977] [SQL] Brings back Shuffled hash join

What changes were proposed in this pull request?
ShuffledHashJoin (also outer join) is removed in 1.6, in favor of SortMergeJoin, which is more robust and also fast.
ShuffledHashJoin is still useful in this case: 1) one table is much smaller than the other one, then cost to build a hash table on smaller table is smaller than sorting the larger table 2) any partition of the small table could fit in memory.
This PR brings back ShuffledHashJoin, basically revert #9645, and fix the conflict. Also merging outer join and left-semi join into the same class. This PR does not implement full outer join, because it's not implemented efficiently (requiring build hash table on both side).
A simple benchmark (one table is 5x smaller than other one) show that ShuffledHashJoin could be 2X faster than SortMergeJoin.
How was this patch tested?
Added new unit tests for ShuffledHashJoin.

Test build #53437 has started for PR 11788 at commit 94c4004.

Test build #53437 has finished for PR 11788 at commit 94c4004.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53437/
Test FAILed.

Test build #53439 has started for PR 11788 at commit 3b6234a.

Test build #53439 has finished for PR 11788 at commit 3b6234a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53439/
Test FAILed.

Test build #53440 has started for PR 11788 at commit f771ec9.

Test build #53440 has finished for PR 11788 at commit f771ec9.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53440/
Test FAILed.

Test build #53441 has started for PR 11788 at commit f621725.

Test build #53441 has finished for PR 11788 at commit f621725.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53441/
Test FAILed.

Test build #53444 has started for PR 11788 at commit 2122986.

Test build #53444 has finished for PR 11788 at commit 2122986.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53444/
Test FAILed.

Test build #53450 has started for PR 11788 at commit 797fe2d.

Test build #53450 has finished for PR 11788 at commit 797fe2d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53450/
Test FAILed.

Test build #53451 has started for PR 11788 at commit 6385777.

Test build #53451 has finished for PR 11788 at commit 6385777.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53451/
Test PASSed.

Can we add a config option to allow turning off shuffle hash join?

@rxin Shuffle hash join should be turned using spark.sql.autoBroadcastThreshold, should we create another config for similar purpose?

I was thinking an option to prefer sort merge join. My main concern is that it is easier to oom when there are skew in hash joins.

spark.sql.join.preferSortMergeJoin = true ?

sgtm

Test build #53513 has started for PR 11788 at commit dea3615.

lgtm - please address the minor issues in ur next pr.

Test build #53513 has finished for PR 11788 at commit dea3615.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53513/
Test PASSed.

Merging this into master, those minor comments will be addressed in follow-up PRs.


Redesign

This is a complete redesign of the OmniBOR website, with a new look, new
content, and a blog. I've taken care to not break any links to the existing
site, and have tried to make sure it works correctly on mobile.
The site is not quite content complete, but it is now very close and should be ready for review!

Alright builds are failing, but it appears to be a Netlify issue. Their docs officially say they support Zola, but I'm just getting "command not found" errors. I think the build should work once they've fixed this issue, and we'll be able to see a preview of the site. In the meantime, if you want to see it locally, you'll need the latest Zola and a recent NPM toolchain, then run:
$ npm install
$ zola serve &
$ npx tailwindcss -i styles/main.css -o public/main.css -w &

This should serve the site locally at http://<IP_ADDRESS>:1111.

This PR is ready for review!  We'd discussed me making the Core Team name list order random, which I haven't done. Small update incoming!


standardized data discovery

A standardized data discovery function that takes Optional parameters frame_type and channel. If these aren't passed it automatically queries the open data

Bumping this issue. It sounds like ideas are either:

A separate project that only uses open data
A flag that can be set to query only open data

This issue is fixed with mldatafind


Migrate the production database to AWS RDS

The production OpCode db is currently in a container in Kubernetes. While this is super neat, it makes things a bit tricky in terms of backups.
Given the level of time that volunteers have to allocate to maintaining the infrastructure, putting the database in AWS RDS greatly reduces the maintenance burden, and will likely be more reliable.

[x]  Create the RDS database
[x]  Create a DB backup of the container
[ ]  Restore the DB backup into the RDS instance

Running into some issues with importing the database backup to the RDS instance, due to lack of superuser permissions.
Initial failures looked like
psql:opcode-prod-db.sql:28: ERROR:  must be owner of extension plpgsql

After doing a test to remove references to plpgsql from the dump, failures looked like
psql:opcode-prod-db.sql:70: ERROR:  must be owner of relation code_schools_id_seq

Dump was performed from within postgres container, copied to local, and then restore attempted with the following
# database container
su - postgres
pg_dump operationcode_production > /tmp/opcode.sql

# retrieved to local machine

# attempting restore
psql -f opcode.sql operationcode_production -h <servername> -U <superuser> -1

Database was initially created and managed by postgres user. In an attempt to utilize users/roles properly, we we're trying to import the DB on RDS with opcode_superuser instead of postgres, but had not updated the dump's references to postgres user for Table/Relationship ownerships.
Resolution:
Find and replace usages of postgres for opcode_superuser throughout dumpfile.
Next step:
Issue incoming on the creation and role establishment of an "application user" to safely handle data manipulation without risking schema shape or - god forbid - the entire destruction of our database.


Ability to turn on subtitles

Describe your suggested feature
The sites have both dubbing and subtitles. But Animiru doesn't turn on subtitles, so we can only watch dubbed and unsubtitled. It would be very helpful to have a subtitle activation feature.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

Currently, the (soft)subs are only shown during foreign text, when dubs are also present (see yomiroll,...)

Describe your suggested feature
The sites have both dubbing and subtitles. But Animiru doesn't turn on subtitles, so we can only watch dubbed and unsubtitled. It would be very helpful to have a subtitle activation feature.

You mean, like seeing the subtitle, while the dub is running?

This is usually due to extensions not providing said data for the specific video in question


[bugfix] check exception before create group-by result block

fix NPE when indexTable is not created but exception is thrown.

Codecov Report

Merging #10984 (44c68b4) into master (2d30e28) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #10984      +/-   ##
==========================================
- Coverage    0.11%    0.11%   -0.01%
==========================================
  Files        2190     2192       +2
  Lines      118056   118092      +36
  Branches    17873    17886      +13
==========================================
  Hits          137      137
- Misses     117899   117935      +36
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
0.00% <0.00%> (ø)

integration1temurin17
?

integration1temurin20
0.00% <0.00%> (ø)

integration2temurin11
?

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
0.00% <0.00%> (ø)

unittests2temurin11
0.11% <0.00%> (-0.01%)
:arrow_down:

unittests2temurin17
0.11% <0.00%> (-0.01%)
:arrow_down:

unittests2temurin20
0.11% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...operator/blocks/results/ExceptionResultsBlock.java
0.00% <0.00%> (ø)

.../core/operator/combine/GroupByCombineOperator.java
0.00% <0.00%> (ø)

...tor/streaming/StreamingGroupByCombineOperator.java
0.00% <0.00%> (ø)

... and 9 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

We don't really need to merge the exceptions since we don't return the result anyway. Early termination should be more desired. See #10988

+1


Dml batch update request priority

This PR creates a sample for DML batch update request with low priority.

LGTM.
Explore on how to sanitize the PR (only relevant commits/files should be there) and I left a question for you.


shared/tools-eskibana | Improvements and Optimization needed

What?

The number of shards (5) and replicas (1) by default is usually not the best;
it would be convenient to use a smaller number of shards and set the replicas to 0 because we only
have a single node cluster currently.

We'll to schedule a revision/optimization of the shards with certain periodicy.

Must enable monitoring in Kibana to have basic insights.

Some extra tool should be installed to facilitate the management of the indexes
(e.g.: https://github.com/ElasticHQ/elasticsearch-HQ)

Before and after adding workloads to the cluster you should check and tune the
fluentd config for better use of indexes and load on Elasticsearch, in order to better use the instance resources before considering any resizing or even the transfering ElasticSearch Engine to AWS ES.

Why?

Continuous improvement and optimization.

For the moment we'll close this issue till a project needs this improvement.


History Server

modifies image and defines deployments for history server
(some details here --> https://jaceklaskowski.gitbooks.io/mastering-apache-spark/spark-history-server.html)
spark history server works by having the driver nodes stream job progress logs out to json files, indicated where we update defaults with spark.eventLog.enabled = true and subsequently setting spark.eventLog.dir = file:/data/spark-events - the server then listens on that very same file path and allows us to view any logs stored there.
In most examples, the eventLog.dir value used in a distributed cluster points to an hdfs filesystem - instead, we plan to take advantage of kubernete's ability to share a PersistentVolume across multiple pods, so that we can have drivers write out to a mounted filesystem, and subsequently have a history server mounted and reading in from the same filesystem.
the eventLog.dir is created during image build, but here we will need to define PersistentVolume, PersistentVolumeClaim and a volume mount on both the history server deployments and the driver node deployments that we wish to make accessible.

 SOT crashes on prod k8s Spark cluster


remove trailing p from mock dependency version in pyproject toml

Hi,
I get an error when trying to install zipline-reloaded v2.3.0.  Poetry says this is due to the version string for mock.
This is the main part of the traceback:
#14 132.5         /tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
#14 132.5           warnings.warn(msg, _BetaConfiguration)
#14 132.5         configuration error: `project.optional-dependencies.{data__optionaldependencies_key}[{data__optionaldependencies_val_x}]` must be pep508
#14 132.5         DESCRIPTION:
#14 132.5             Project dependency specification according to PEP 508
#14 132.5
#14 132.5         GIVEN VALUE:
#14 132.5             "mock >=2.0.0p"
#14 132.5
#14 132.5         OFFENDING RULE: 'format'
#14 132.5
#14 132.5         DEFINITION:
#14 132.5             {
#14 132.5                 "$id": "#/definitions/dependency",
#14 132.5                 "title": "Dependency",
#14 132.5                 "type": "string",
#14 132.5                 "format": "pep508"
#14 132.5             }
#14 132.5         Traceback (most recent call last):
#14 132.5           File "/tmp/tmpx7u2hbu3_in_process.py", line 351, in <module>
#14 132.5             main()
#14 132.5           File "/tmp/tmpx7u2hbu3_in_process.py", line 333, in main
#14 132.5             json_out['return_val'] = hook(**hook_input['kwargs'])
#14 132.5           File "/tmp/tmpx7u2hbu3_in_process.py", line 118, in get_requires_for_build_wheel
#14 132.5             return hook(config_settings)
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in get_requires_for_build_wheel
#14 132.5             return self._get_build_requires(config_settings, requirements=['wheel'])
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 320, in _get_build_requires
#14 132.5             self.run_setup()
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 335, in run_setup
#14 132.5             exec(code, locals())
#14 132.5           File "<string>", line 106, in <module>
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 87, in setup
#14 132.5             return distutils.core.setup(**attrs)
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 159, in setup
#14 132.5             dist.parse_config_files()
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 867, in parse_config_files
[tool.poetry]
#14 132.5             pyprojecttoml.apply_configuration(self, filename, ignore_option_errors)
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py", line 62, in apply_configuration
#14 132.5             config = read_configuration(filepath, True, ignore_option_errors, dist)
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py", line 126, in read_configuration
#14 132.5             validate(subset, filepath)
#14 132.5           File "/tmp/pip-build-env-oglm4unr/overlay/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py", line 51, in validate
#14 132.5             raise ValueError(f"{error}\n{summary}") from None
#14 132.5         ValueError: invalid pyproject.toml config: `project.optional-dependencies.{data__optionaldependencies_key}[{data__optionaldependencies_val_x}]`.
#14 132.5         configuration error: `project.optional-dependencies.{data__optionaldependencies_key}[{data__optionaldependencies_val_x}]` must be pep508
#14 132.5         [end of output]

I am not aware of using p in version strings and since p is next to 0 on the keyboard, my suspicion is typo.  Might be missing something though
There's no lock file so I haven't built/updated one.  I tried looking at the contributing guidelines but the link didn't take me away from CONTRIBUTING.rst.  Let me know if there are other requirements for this pull request

Addressed by #158


added maximize and minimize to application

Signed-off-by: Aditya Chaterjee<EMAIL_ADDRESS>Description
Added maximize and minimize feature to application, might be nice to have. same approach as@Abhishek-kumar09
https://user-images.githubusercontent.com/53532328/135158817-5e23e4b5-2571-4d36-b0a0-2214ee99d70d.mov
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

@ramrodo tests are failing, https://github.com/meshery/meshery/pull/4268/checks?check_run_id=3737136488#step:13:170
and https://github.com/meshery/meshery/pull/4268/checks?check_run_id=3737136538#step:5:152

Codecov Report

Merging #4268 (c9ba691) into master (68564ce) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4268   +/-   ##
=======================================
  Coverage   27.89%   27.89%
=======================================
  Files          59       59
  Lines        5037     5037
=======================================
  Hits         1405     1405
  Misses       3215     3215
  Partials      417      417

Flag
Coverage Δ

gointegrationtests
10.14% <ø> (ø)

unittests
20.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

@warunicorn19 do you think you can do this same thing for Filters?

@leecalcote yup, at least I think I can 😅.

@ramrodo tests are failing, https://github.com/meshery/meshery/pull/4268/checks?check_run_id=3737136488#step:13:170 and https://github.com/meshery/meshery/pull/4268/checks?check_run_id=3737136538#step:5:152

Thanks for letting me know @warunicorn19. I'll fix them.


⚠ Bofrost.at has degraded performance

In 47d727e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1669 ms

Resolved: Bofrost.at performance has improved in c613644.


Fix unsigned comparison which could fail due to numeric overflow

Issue #, if available: Code Scanning 6
Description of changes:
This PR addresses a comparison that was highlighted by gh code scanning. The original code contained:
stream->size() - end_index > 0

Where both stream->size() and end_index are of type size_t, which is unsigned. If end_index is larger than stream->size(), the result will be a positive value, due to numeric overflow. If this were to happen, stream->at(end_index++) would throw an exception, if exceptions are enabled, or abort the process if not.
This PR re-words the comparison to highlight that we expect end_index to be less than the stream's size, and lessen the chance of overflow potential if the condition were to change later.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Need to update GHA for uploading ion-test-driver results, and MacOS tests (gcc 11 was removed from all MacOS images in August).

MacOS build addressed with #353.

ion-test-driver failures addressed in #354

Thank you @tgregg ! :)


Release 1.18.3

This is a draft of changelog for the 1.18.3 release.
Here you can find all related translations changes: 1.18.2...master.

⚠ Do not merge this pull request manually ⚠
You should approve this pull request instead. After approving, I will automatically update it (release date needs to be adjusted), merge, and tag a new release. You can read more about the process on forum.

Show release notes preview
1.18.3

Perubahan umum:

Memperbarui terjemahan untuk Flarum core.

Terjemahan terbaru untuk ekstensi:

acpl/my-tags
afrux/asirem
afrux/forum-widgets-core
akr/chevereto
antoinefr/flarum-ext-money
askvortsov/flarum-categories
askvortsov/flarum-help-tags
askvortsov/flarum-pwa
askvortsov/flarum-rich-text
blomstra/gdpr
blomstra/trello
clarkwinkelmann/catch-the-fish
clarkwinkelmann/flarum-ext-create-user-modal
clarkwinkelmann/flarum-ext-first-post-approval
clarkwinkelmann/flarum-ext-predefined-avatars
clarkwinkelmann/flarum-ext-shadow-ban
dalez/flarum-msemoji
dalez/flarum-twemoji
datlechin/flarum-chatgpt
datlechin/flarum-simple-tour-guide
datlechin/flarum-tag-passwords
datlechin/flarum-usercard-uid
davwheat/flarum-ext-ads
davwheat/custom-sidenav-links
davwheat/virtual-authors
extiverse/mercury
flamarkt/taxonomies
flarum/extension-manager
flarum/lock
flarum/markdown
flarum/tags
fof/ban-ips
fof/best-answer
fof/discussion-language
fof/doorman
fof/drafts
fof/filter
fof/follow-tags
fof/formatting
fof/gamification
fof/impersonate
fof/links
fof/merge-discussions
fof/polls
fof/prevent-necrobumping
fof/profile-image-crop
fof/share-social
fof/terms
fof/upload
fof/user-directory
foskym/flarum-oauth-center
ianm/follow-users
justoverclock/last-post-useravatar
katosdev/signature
kilowhat/flarum-ext-audit-free
kilowhat/flarum-ext-audit-pro
kilowhat/flarum-ext-cimaise
kilowhat/flarum-ext-custom-paths
kilowhat/flarum-ext-formulaire
kilowhat/flarum-ext-rich-embeds
litalino/flarum-more-bbcode
maicol07/flarum-ext-sso
michaelbelgium/flarum-discussion-views
michaelbelgium/mybb-to-flarum
migratetoflarum/fake-data
nearata/flarum-ext-cloudflare
nodeloc-referral
the-turk/flarum-flamoji
therealsujitk/flarum-ext-gifs
v17development/flarum-blog
widayn/flarum-avatar-cropper
xelson/flarum-ext-chat
yippy/flarum-tag-with-themes
ziiven/flarum-daily-check-in
ziiven/flarum-decoration-store
ziiven/flarum-money-leaderboard
ziiven/money-transfer
ziiven/flarum-pay-to-see

Semua perubahan: 1.18.2...1.18.3.

Success! Now you can announce new release on forum:
## Versi [`1.18.3`](https://github.com/flarum-lang/indonesian/releases/tag/1.18.3)

**Perubahan umum**:

* Memperbarui terjemahan untuk Flarum core.

**Terjemahan terbaru untuk ekstensi**:

* [`acpl/my-tags`](https://github.com/android-com-pl/my-tags)
* [`afrux/asirem`](https://github.com/afrux/asirem)
* [`afrux/forum-widgets-core`](https://github.com/afrux/forum-widgets-core)
* [`akr/chevereto`](https://github.com/AKR-Developers/flarum-chevereto)
* [`antoinefr/flarum-ext-money`](https://github.com/AntoineFr/flarum-ext-money)
* [`askvortsov/flarum-categories`](https://github.com/askvortsov1/flarum-categories)
* [`askvortsov/flarum-help-tags`](https://github.com/askvortsov1/flarum-help-tags)
* [`askvortsov/flarum-pwa`](https://github.com/askvortsov1/flarum-pwa)
* [`askvortsov/flarum-rich-text`](https://github.com/askvortsov1/flarum-rich-text)
* [`blomstra/gdpr`](https://github.com/blomstra/flarum-ext-gdpr)
* [`blomstra/trello`](https://github.com/blomstra/flarum-ext-trello)
* [`clarkwinkelmann/catch-the-fish`](https://github.com/clarkwinkelmann/catch-the-fish)
* [`clarkwinkelmann/flarum-ext-create-user-modal`](https://github.com/clarkwinkelmann/flarum-ext-create-user-modal)
* [`clarkwinkelmann/flarum-ext-first-post-approval`](https://github.com/clarkwinkelmann/flarum-ext-first-post-approval)
* [`clarkwinkelmann/flarum-ext-predefined-avatars`](https://github.com/clarkwinkelmann/flarum-ext-predefined-avatars)
* [`clarkwinkelmann/flarum-ext-shadow-ban`](https://github.com/clarkwinkelmann/flarum-ext-shadow-ban)
* [`dalez/flarum-msemoji`](https://github.com/DellZHackintosh/flarum-msemoji)
* [`dalez/flarum-twemoji`](https://github.com/DellZHackintosh/flarum-twemoji)
* [`datlechin/flarum-chatgpt`](https://github.com/datlechin/flarum-chatgpt)
* [`datlechin/flarum-simple-tour-guide`](https://github.com/datlechin/flarum-simple-tour-guide)
* [`datlechin/flarum-tag-passwords`](https://github.com/datlechin/flarum-tag-passwords)
* [`datlechin/flarum-usercard-uid`](https://github.com/datlechin/flarum-usercard-uid)
* [`davwheat/flarum-ext-ads`](https://github.com/davwheat/flarum-ext-ads)
* [`davwheat/custom-sidenav-links`](https://github.com/davwheat/flarum-ext-custom-sidenav-links)
* [`davwheat/virtual-authors`](https://flarum.org/extension/davwheat/virtual-authors)
* [`extiverse/mercury`](https://github.com/extiverse/mercury)
* [`flamarkt/taxonomies`](https://github.com/flamarkt/taxonomies)
* [`flarum/extension-manager`](https://github.com/flarum/extension-manager)
* [`flarum/lock`](https://github.com/flarum/lock)
* [`flarum/markdown`](https://github.com/flarum/markdown)
* [`flarum/tags`](https://github.com/flarum/tags)
* [`fof/ban-ips`](https://github.com/FriendsOfFlarum/ban-ips)
* [`fof/best-answer`](https://github.com/FriendsOfFlarum/best-answer)
* [`fof/discussion-language`](https://github.com/FriendsOfFlarum/discussion-language)
* [`fof/doorman`](https://github.com/FriendsOfFlarum/doorman)
* [`fof/drafts`](https://github.com/FriendsOfFlarum/drafts)
* [`fof/filter`](https://github.com/FriendsOfFlarum/filter)
* [`fof/follow-tags`](https://github.com/FriendsOfFlarum/follow-tags)
* [`fof/formatting`](https://github.com/FriendsOfFlarum/formatting)
* [`fof/gamification`](https://github.com/FriendsOfFlarum/gamification)
* [`fof/impersonate`](https://github.com/FriendsOfFlarum/impersonate)
* [`fof/links`](https://github.com/FriendsOfFlarum/links)
* [`fof/merge-discussions`](https://github.com/FriendsOfFlarum/merge-discussions)
* [`fof/polls`](https://github.com/FriendsOfFlarum/polls)
* [`fof/prevent-necrobumping`](https://github.com/FriendsOfFlarum/prevent-necrobumping)
* [`fof/profile-image-crop`](https://github.com/FriendsOfFlarum/profile-image-crop)
* [`fof/share-social`](https://github.com/FriendsOfFlarum/share-social)
* [`fof/terms`](https://github.com/FriendsOfFlarum/terms)
* [`fof/upload`](https://github.com/FriendsOfFlarum/upload)
* [`fof/user-directory`](https://github.com/FriendsOfFlarum/user-directory)
* [`foskym/flarum-oauth-center`](https://github.com/FoskyM/flarum-oauth-center)
* [`ianm/follow-users`](https://github.com/imorland/follow-users)
* [`justoverclock/last-post-useravatar`](https://github.com/justoverclockl/last-post-useravatar)
* [`katosdev/signature`](https://github.com/katosdev/signature)
* [`kilowhat/flarum-ext-audit-free`](https://github.com/kilowhat/flarum-ext-audit-free)
* [`kilowhat/flarum-ext-audit-pro`](https://flarum.org/extension/kilowhat/flarum-ext-audit-pro)
* [`kilowhat/flarum-ext-cimaise`](https://flarum.org/extension/kilowhat/flarum-ext-cimaise)
* [`kilowhat/flarum-ext-custom-paths`](https://flarum.org/extension/kilowhat/flarum-ext-custom-paths)
* [`kilowhat/flarum-ext-formulaire`](https://flarum.org/extension/kilowhat/flarum-ext-formulaire)
* [`kilowhat/flarum-ext-rich-embeds`](https://flarum.org/extension/kilowhat/flarum-ext-rich-embeds)
* [`litalino/flarum-more-bbcode`](https://github.com/Litalino/flarum-more-bbcode)
* [`maicol07/flarum-ext-sso`](https://github.com/maicol07/flarum-ext-sso)
* [`michaelbelgium/flarum-discussion-views`](https://github.com/MichaelBelgium/flarum-discussion-views)
* [`michaelbelgium/mybb-to-flarum`](https://github.com/MichaelBelgium/mybb_to_flarum)
* [`migratetoflarum/fake-data`](https://github.com/migratetoflarum/fake-data)
* [`nearata/flarum-ext-cloudflare`](https://github.com/Nearata/flarum-ext-cloudflare)
* `nodeloc-referral`
* [`the-turk/flarum-flamoji`](https://github.com/the-turk/flarum-flamoji)
* [`therealsujitk/flarum-ext-gifs`](https://github.com/therealsujitk/flarum-ext-gifs)
* [`v17development/flarum-blog`](https://github.com/v17development/flarum-blog)
* [`widayn/flarum-avatar-cropper`](https://github.com/WiDayn/flarum-avatar-cropper)
* [`xelson/flarum-ext-chat`](https://github.com/Xelson/flarum-ext-chat)
* [`yippy/flarum-tag-with-themes`](https://github.com/Yippy/flarum-tag-with-themes)
* [`ziiven/flarum-daily-check-in`](https://github.com/Ziiven/flarum-daily-check-in)
* [`ziiven/flarum-decoration-store`](https://flarum.org/extension/ziiven/flarum-decoration-store)
* [`ziiven/flarum-money-leaderboard`](https://github.com/Ziiven/flarum-money-leaderboard)
* [`ziiven/money-transfer`](https://github.com/Ziiven/ziven-money-transfer)
* [`ziiven/flarum-pay-to-see`](https://flarum.org/extension/ziiven/flarum-pay-to-see)

Semua perubahan: [1.18.2...1.18.3](https://github.com/flarum-lang/indonesian/compare/1.18.2...1.18.3).

Untuk memperbarui, jalankan perintah ini:

```console
composer update flarum-lang/indonesian
php flarum cache:clear
```


DBeaver MongoDB Update doesn't work

I tried to update some data in a document but it failed. When i try to use the JSON view get :

Can't find a codec for class com.jkiss.dbeaver.ent.mongodb.data.MongoMapValue.

When i try with the grid view i get :

com.mongodb.WriteConcernException: Write failed with error code 16837 and error message 'cannot use the part (recipients of recipients.address) to traverse the element ({recipients: [ { address<EMAIL_ADDRESS>name: "Fanny Fannie Pierce", _id: ObjectId('56be7774a67c63c41de2c528') } ]})' the problem seem to be related with the array update. I tried to edit an not array element and it worked.

Please post error stacktrace (both).
You can get it in Error Log view.

com.mongodb.WriteConcernException: Write failed with error code 16837 and error message 'cannot use the part (recipients of recipients.address) to traverse the element ({recipients: [ { address<EMAIL_ADDRESS>name: "Bessie Theresa Harmon", _id: ObjectId('570fa6be9aea6dd83337d634') } ]})'
at com.mongodb.operation.BaseWriteOperation.convertBulkWriteException(BaseWriteOperation.java:239)
at com.mongodb.operation.BaseWriteOperation.access$300(BaseWriteOperation.java:60)
at com.mongodb.operation.BaseWriteOperation$1.call(BaseWriteOperation.java:146)
at com.mongodb.operation.BaseWriteOperation$1.call(BaseWriteOperation.java:133)
at com.mongodb.operation.OperationHelper.withConnectionSource(OperationHelper.java:230)
at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:221)
at com.mongodb.operation.BaseWriteOperation.execute(BaseWriteOperation.java:133)
at com.mongodb.operation.BaseWriteOperation.execute(BaseWriteOperation.java:60)
at com.mongodb.Mongo.execute(Mongo.java:781)
at com.mongodb.Mongo$2.execute(Mongo.java:764)
at com.mongodb.DBCollection.executeWriteOperation(DBCollection.java:333)
at com.mongodb.DBCollection.updateImpl(DBCollection.java:495)
at com.mongodb.DBCollection.update(DBCollection.java:455)
at com.mongodb.DBCollection.update(DBCollection.java:432)
at com.mongodb.DBCollection.update(DBCollection.java:522)
at com.jkiss.dbeaver.ent.mongodb.exec.MongoUpdateStatement.executeStatement(MongoUpdateStatement.java:64)
at org.jkiss.dbeaver.model.impl.data.ExecuteBatchImpl.executeStatement(ExecuteBatchImpl.java:222)
at org.jkiss.dbeaver.model.impl.data.ExecuteBatchImpl.execute(ExecuteBatchImpl.java:134)
at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.executeStatements(ResultSetPersister.java:501)
at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.run(ResultSetPersister.java:367)
at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

10x for report


Add script to create and upload GCP deployment packages to bucket

Add script to create and upload GCP deployment packages to bucket
To be merged with https://github.com/kinvolk/PROJECT-flatcar-linux/pull/555

Closing this since https://github.com/flatcar/flatcar-maintainer-private/pull/11 has been merged and the script in this PR is now part of https://github.com/flatcar/flatcar-maintainer-private/tree/main/documentation/maintenance.


HTTPS doesn't work

In my bots, HTTPS doesn't work with urltitle.0.10.tcl .  If you need to load other scripts to get HTTPS to work, can you please write that documentation?

I need some more info about this. What version of TCL are you running? TclTLS? Specific URLS that aren't working?

The server I use has TCL 8.5, 8.6, and TclTLS 1.7.14.  I don't know which were needed to compile eggdrop 1.8.3.  NO HTTPS URL works... for example, https://google.com.

This seems like a configuration issue, but without knowing any specifics I can't say what could be the reason.

which specifics?


Standalone Repartition Function

A wrapper of dask repartition may be insufficient, we have extra requirement of needing lightcurves to not be split among partitions.

As part of #278, learned that repartition does account for a non-unique index, and will not split lightcurves among partitions. So the default repartition that we now have access to via #304 will be sufficient


[Perf_Analyzer]: took very long to exit, killing perf_analyzer.

I tried to run model_navigator on my onnx model and it stops by giving following error..
2022-04-22 18:56:36.187 INFO[perf_analyzer.py:214] perf_analyzer took very long to exit, killing perf_analyzer... 2022-04-22 18:56:41.700 INFO[server_local.py:121] Stopped Triton Server.
Traceback (most recent call last):   File "/usr/local/bin/model-analyzer", line 8, in <module>     sys.exit(main())   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/entrypoint.py", line 402, in main     analyzer.profile(client=client, gpus=gpus)   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/analyzer.py", line 125, in profile     self._model_manager.run_models(models=[model])   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/model_manager.py", line 79, in run_models     while not rcg.is_done() and not self._state_manager.exiting():   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/run_config_generator.py", line 60, in is_done     return (self._pacg.is_done() and   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 84, in is_done     return self._done_walking() or self._last_results_erroneous()   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 176, in _done_walking     and self._done_walking_concurrencies()   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 183, in _done_walking_concurrencies     1) or not self._throughput_gain_valid()   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 194, in _throughput_gain_valid     valid_gains = [self._calculate_throughput_gain(x) > THROUGHPUT_MINIMUM_GAIN \   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 194, in <listcomp>     valid_gains = [self._calculate_throughput_gain(x) > THROUGHPUT_MINIMUM_GAIN \   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 212, in _calculate_throughput_gain     throughput_after = self._get_throughput(self._all_results[after_index])   File "/usr/local/lib/python3.8/dist-packages/model_analyzer/config/generate/perf_analyzer_config_generator.py", line 217, in _get_throughput     return measurement.get_metric_value('perf_throughput') AttributeError: 'NoneType' object has no attribute 'get_metric_value'
Traceback (most recent call last):   File "/opt/model-navigator/model_navigator/cli/profile.py", line 130, in profile_cmd     checkpoint_path = profiler.run()   File "/opt/model-navigator/model_navigator/model_analyzer/profiler.py", line 100, in run     analyzer.run(mode=ModelAnalyzerMode.PROFILE, verbose=self._verbose)   File "/opt/model-navigator/model_navigator/model_analyzer/model_analyzer.py", line 73, in run     raise ModelNavigatorException( model_navigator.exceptions.ModelNavigatorException: Running model-analyzer with ['model-analyzer', 'profile', '-f', '/home/darvis-ml3/darvis_ml/xperiments/model_navigator/navigator_workspace/analyzer/config-profile.yaml'] failed with exit status 1 : None

@jkosek kindly look into this..

@sbmalik this error indicates that Triton Model Analyzer won't profile one of the configurations and was unable to collect results. We are aware of this error and this should be fixed with upcoming release of Triton Model Analyzer. I will update the information once new version is available.

Thank you for the details.

@sbmalik this error indicates that Triton Model Analyzer hadn't profiled one of the configurations and was unable to collect results. We are aware of this error and this should be fixed with upcoming release of Triton Model Analyzer. I will update the information once new version is available.

@sbmalik Please, try the latest version to see if the issues is still appearing.


Add config for GitHub Lock app

Add a configuration for https://github.com/apps/lock

Only for issues older than 180 days.

Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

:+1:

:+1:


ignore certain files (such as .swp)

Is it possible to tell skicka to ignore .swp files?

In the ~/.skicka.config file, you can set "ignored-regexp" in the [upload]
section. (There should be some commented-out examples in the default config
file generated the first time.)
Thanks,
Matt
On Tue, Apr 18, 2017 at 1:59 PM, Tri Nguyen<EMAIL_ADDRESS>wrote:

Is it possible to tell skicka to ignore .swp files?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/skicka/issues/118, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGQp7FCHhR8H-bGv2WYzmzeX_-Ka4Ysks5rxSQ-gaJpZM4NA45D
.

Thank you. Setting it as below works:
ignored-regexp=".*\\.swp"


Why isn't the new I2C API deemed as thread safe? (IDFGH-14050)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
According to the doc, only bus creation was deemed as thread safe. Tracing the source code I found that the API are all semaphore-guarded that prevent racing access on the same bus:
For example:
https://github.com/espressif/esp-idf/blob/ce6085349f8d5a95fc857e28e2d73d73dd3629b5/components/esp_driver_i2c/i2c_master.c#L898
If so, why are we recommended to put extra locks as per the doc?

Yes, the doc is wrong and it will be updated soon
The factory function :cpp:func:`i2c_new_master_bus` and :cpp:func:`i2c_new_slave_device` are guaranteed to be thread safe by the driver, which means that the functions can be called from different RTOS tasks without protection by extra locks.

I2C master operation functions are also guaranteed to be thread safe by bus operation semaphore.

- :cpp:func:`i2c_master_transmit`
- :cpp:func:`i2c_master_multi_buffer_transmit`
- :cpp:func:`i2c_master_transmit_receive`
- :cpp:func:`i2c_master_receive`
- :cpp:func:`i2c_master_probe`

@mythbuster5  Thank you for the confirmation


Improve Mio windows support

Mio is a low level abstraction on top of the operating system's evented I/O
APIs. It is used by Tokio to integrate with the operating system and perform the
I/O operations. The current Windows implementation is not ideal. A better
solution is outlined in
piscisaureus/wepoll.
Expected outcomes
The windows Mio implementation is rewritten using the strategy used by wepoll.
Skills

Rust
Windows networking

Difficulty level
Medium

Hey! I'm interested in taking part in the project, but I'm not sure what is meant by "the strategy used by wepoll." Are you planning to build a custom version of the epoll API?
I'm also extremely new to rust. Do you know any good places I can go to to learn more about the language?

@kingoftheconnors Yes, wepoll exposes an epoll-like API (epoll_create1, epoll_ctl, epoll_wait) with some differences (SOCKETs instead of int fds, and some restrictions like no edge-triggered events).
I don't speak for mio/tokio, but I assume the expectation is to implement it in pure Rust and then use it in mio instead of libc::epoll_* for Windows targets.
That way a lot of the IOCP and buffer-pool related code inside mio::windows can go away. It should also allow for something like EventedSocket to be exported (like EventedFd is for Unix targets), which would make it easy for out-of-tree socket implementations like mio-uds to work with the "system" selector.

General info about wepoll:
wepoll works by opening a handle to the AFD device, then uses NtDeviceIoControlFile(IOCTL_AFD_POLL) to receive events for individual sockets. The ioctl is undocumented (*), so it has to define it and the associated structs and constants itself.
The ioctl is essentially how the (public) WSAPoll is implemented (which is presumably where piscisaureus reversed it from), but by using it directly with NtDeviceIoControlFile wepoll is able to receive the events in an overlapped fashion - all events are send to the IOCP associated with the AFD handle instead of blocking at a WSAPoll call. For each socket registered with the epoll handle, it uses the ioctl to associate the socket with the AFD device handle. Inside epoll_wait, for each event that it receives over the IOCP, it uses the ioctl to requeue the corresponding socket again.
The AFD poll events map reasonably closely to the epoll events, so the library is able to translate one set of events to the other.
(I found it easier to understand how it works by reading the dist file at https://github.com/piscisaureus/wepoll/blob/dist/wepoll.c compared to the split files in master, and following the call graph down from epoll_wait.)
(*) I brought this up with the Windows networking team, and they were quite surprised to learn that libuv has been using it since 2012. It is important to note that it is not a public API, so there is no guarantee that it will continue to work.

I'm interested in this subject too, I'm reading up on lots of sources related to this subject and mio. And hope to find some common ground for both Mio and wepoll. Is there any time estimation for this project?

@TimonPost It is hard to really say how long as the answer will be very dependent on the student. However, it should take a minimum of a few weeks but be doable in a summer. The project is very "stretchy", so it should take up the entire summer :)

I came across those libraries, they are bindings for the wepoll library.
https://gitlab.com/yorickpeterse/wepoll-binding
https://gitlab.com/yorickpeterse/wepoll-sys

I'm also interested in this subject too. I made a pull request about this.
https://github.com/carllerche/mio/pull/868
But it is rather incomplete and hacky. The implementation needs a rewrite.


Add TestBench runner

Closes vim-test/vim-test#498
Make sure these boxes are checked before submitting your pull request:

[x] Add fixtures and spec when implementing or updating a test runner
[x] Update the README accordingly
[x] Update the Vim documentation in doc/test.txt

Thank you, Tom! ❤


Update CI URLs to point to new caching infrastructure

Hello there!
This is an automated pull request submitted by @staticfloat to help package authors transition their Julia installation CI setups to the new binary provider URL.  Please take a look at this PR, and if there is a problem or it doesn't download correctly when CI runs, feel free to ping @staticfloat

Codecov Report

Merging #163 into master will decrease coverage by 1.21%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #163      +/-   ##
=========================================
- Coverage   49.11%   47.9%   -1.22%
=========================================
  Files           7       7
  Lines         621     620       -1
=========================================
- Hits          305     297       -8
- Misses        316     323       +7

Impacted Files
Coverage Δ

src/types.jl
57.14% <0%> (-4.93%)
:arrow_down:

src/Source.jl
82.42% <0%> (-2.52%)
:arrow_down:

Continue to review full report at Codecov.

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