No homebridge 1.0 Support

After updating to homebridge 1.0.1, I got the following error message:

4/27/2020, 3:35:06 PM] [Loxone] Platform - Retrieving initial config from http://NodeRed:HHL%24AQpCeN6qmkuYik@<IP_ADDRESS>:35000/data/LoxApp3.json
[4/27/2020, 3:35:06 PM] [Loxone] Platform - The widget 'Lichtsteuerung' of type LightControllerV2 is an item not handled.
[4/27/2020, 3:35:06 PM] [Loxone] Platform - The widget 'Master-Schalter of Lichtsteuerung' of type Lightbulb was skipped.
[4/27/2020, 3:35:06 PM] TypeError: Class constructor PlatformAccessory cannot be invoked without 'new'
at LightbulbItem.AbstractItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/AbstractItem.js:22:25)
at LightbulbItem.SwitchItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/SwitchItem.js:12:23)
at new LightbulbItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/LightbulbItem.js:6:26)
at exports.Factory.parseSitemap (/homebridge/node_modules/homebridge-loxone-ws-adv/libs/ItemFactory.js:66:29)
at Request._callback (/homebridge/node_modules/homebridge-loxone-ws-adv/index.js:88:38)
at Request.self.callback (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:185:22)
at Request.emit (events.js:223:5)
at Request. (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1154:10)
at Request.emit (events.js:223:5)
at IncomingMessage. (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1076:12)
[4/27/2020, 3:35:06 PM] Got SIGTERM, shutting down Homebridge...

Running in an DS718+II Container with a Loxone Miniserver.

+1. same error messages. Run on a Synology DS218+, Loxone Miniserver. Everything up to date.

same here. with the loxone-ws-adv (successor plugin) too

@Sroose you current "inherit" your AbstractItem from PlatformAccessory.
Your using a so called "StaticPlatformPlugin" (exposing a method accessories, which returns a array of AccessoryPlugin objects). Your accessories returns an array of AbstractItem. They do NOT need to inherit from PlatfromAccessory. This inheritance is completely unnecessary. The only thing what is required by homebridge is that those "accessory objects" (so AbstracItem instances) define a method getServices and return all services which should be added. Nothing more. You may have a look at the homebridge-examples repo on how such a plugin should be implemented.
So to fix that you could correctly inherit from PlatfromAccessory, or just remove the inheritance altogether as there is not benefit, it's not used and it's just wasting memory. I don't know which mechanics you may abuse from the inhertiance, so other parts of the code may need to the adjusted.

+1 same error here
new setup on rpi 3b+
with loxone version <IP_ADDRESS>
i am not that experienced programmer to find out myself how to solve this in your code
if you have questions, feel free, i try to help you
but afterwards, explain me how to solve the problem
thanks for all you guys efforts, fantastic piece of software you are making here

@keuninkske if you really want to rollback. You probably need to rollback to some 0.4.x version.

pff, i had  an old instalation, stopped working somewhere in november or december (issue unknown, probably due to an update of the UI plugin)
now i took the time to reinstall, but i'm not able to get it finished
i am hobby python programmer
i took a look to the java code for this already, but seems above my level...
nobody who can help us out?

@keuninkske if you really want to rollback. You probably need to rollback to some 0.4.x version.

I tried to rollback to 0.4.x - working - but due to dependencies or somewhat else the loxone plugin does not work.

Just got this bug overnight... any news? Has someone found any solution?

Hi, I have updated this loxone plugin to the latest v1.0.9 (just committed) and i have homebridge v1.0.4 and i am still getting the looping/restarting error with the Platform Accessory error (below)
[5/5/2020, 6:31:33 PM] [Loxone] Platform - Retrieving initial config from http://homebridge:xxxx@<IP_ADDRESS>:7777/data/LoxApp3.json
[5/5/2020, 6:31:33 PM] TypeError: Class constructor PlatformAccessory cannot be invoked without 'new'
at DimmerItem.AbstractItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/AbstractItem.js:22:25)
at new DimmerItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/DimmerItem.js:12:23)
at exports.Factory.parseSitemap (/usr/lib/node_modules/homebridge-loxone-ws-adv/libs/ItemFactory.js:66:29)
at Request._callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/index.js:88:38)
at Request.self.callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request. (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at IncomingMessage. (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:416:28)
[5/5/2020, 6:31:34 PM] [Family Room TV] Opening handshake has timed out
[5/5/2020, 6:31:38 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[5/5/2020, 6:31:43 PM] [HB Supervisor] Restarting Homebridge...

This plugin needs an update. As already explained. Homebridge can’t really fix this.

This plugin needs an update. As already explained. Homebridge can’t really fix this.

Yes that is why we are posting on here to assist Sroose with the issues and to inform him that we are having problems still with the latest updates he has committed today  as he is the author. If it was an issue with homebridge we would post on the main homebridge pages?

so, what you are explaining is that:
-the homebridge platform is has an update who causes problems!
-the loxone-ws plugin is updated?
-i have only one other plugin installed, and that is google gsh
what is very strange, i have only the loxone plugin metioned in the error i am having

TypeError: Class constructor PlatformAccessory cannot be invoked without 'new'
at PushbuttonItem.AbstractItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/AbstractItem.js:22:25)
at PushbuttonItem.SwitchItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/SwitchItem.js:12:23)
at new PushbuttonItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/PushbuttonItem.js:6:27)
at exports.Factory.parseSitemap (/usr/lib/node_modules/homebridge-loxone-ws-adv/libs/ItemFactory.js:66:29)
at Request._callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/index.js:88:38)
at Request.self.callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request. (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at IncomingMessage. (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1076:12)

Same here...

[5/5/2020, 9:19:31 PM] [Loxone] LOXONE WS: connect
[5/5/2020, 9:19:39 PM] [Loxone] Platform - Retrieving initial config from http://:@192.168..:*****/data/LoxApp3.json
[5/5/2020, 9:19:39 PM] [Loxone] Platform - The widget 'Lichtsteuerung' of type LightControllerV2 is an item not handled.
[5/5/2020, 9:19:39 PM] [Loxone] Platform - The widget 'Master-Schalter of Lichtsteuerung' of type Lightbulb was skipped.
[5/5/2020, 9:19:39 PM] TypeError: Class constructor PlatformAccessory cannot be invoked without 'new'
at LightbulbItem.AbstractItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/AbstractItem.js:22:25)
at LightbulbItem.SwitchItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/SwitchItem.js:12:23)
at new LightbulbItem (/homebridge/node_modules/homebridge-loxone-ws-adv/items/LightbulbItem.js:6:26)
at exports.Factory.parseSitemap (/homebridge/node_modules/homebridge-loxone-ws-adv/libs/ItemFactory.js:66:29)
at Request._callback (/homebridge/node_modules/homebridge-loxone-ws-adv/index.js:88:38)
at Request.self.callback (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:185:22)
at Request.emit (events.js:223:5)
at Request. (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1154:10)
at Request.emit (events.js:223:5)
at IncomingMessage. (/homebridge/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1076:12)
[5/5/2020, 9:19:39 PM] Got SIGTERM, shutting down Homebridge...

Lumoc was so kind to update homebridge-loxone-ws-adv, but his update did not work yet.
I think it would help if @Sroose supports. He did not update since 2018 :-/

It seems that there's a new version of Lumoc's ported plugin (1.0.17?), but I am not able to install it. Can someone confirm it that version is working? Thanks in advance

I uninstalled the plugin (1.0.7) and reinstalled it (UI said 1.0.11?).
Did not work.
I saw that Lumoc updated and I assume that he is still working on it.
It would really help if we got any feedback from @Sroose :-/

I just installed a fresh Homebridge and homebridge-loxone-adv (.17) and it does not work.
"TypeError: Class constructor PlatformAccessory cannot be invoked without 'new' "

There were several updates from Lumoc yesterday i tried each one that came in, some threw new errors, one of them did connect to Loxone but couldn't handle any of the accessories & the latest version 1.0.17 still doesn't work with the same error (TypeError: Class constructor PlatformAccessory cannot be invoked without 'new' at PushbuttonItem.AbstractItem) looks like Lumoc is still working on it from all the updates so i'm going to wait a few days/week before i downgrade homebridge to get back up and running

I guess that there are no good news yet... I was afraid that this may eventually happend...

You can have multiple instances of homebridge bridges running under HomeKit, and one instance only supports 100 accessories anyway so i was going to have to add another for loxone anyway soon as I have around 90 accessories in my loxone setup. For the sake of £40-60 you can buy another Pi and install homebridge v0.4.53 with loxone-we-adv which works fine, then use the other homebridge instance for the most up to date homebridge version for all other plugins ... this is what I’m going to do it is a relatively cheap way to get around the problem until this is fixed. Hope this helps

It’s a bit of a hack, but I believe you can run multiple homebridge instances on the same server.

Yes you can but I’m not sure if you can ru. Different versions of homebridge as multiple instances, for example I have the ring doorbell plugin which requires homebridge v1+ so I don’t think I can home that aswell as homebridge v0.4.53 on the same server (easily) ?

I've seen that homebridge has updated to version 1.1.0. Has someone tried, or has someone any good news?
Regards,

Just tried it. Same issue.
Loading Loxone for a while and then the error pops up... 👎

Fix is here with v1.0.18 of my plugin

sudo -E -n npm install homebridge-loxone-ws-adv@latest

thanks allot to @lumoc and @geilername for helping out

Fix is here with v1.0.18 of my plugin

sudo -E -n npm install homebridge-loxone-ws-adv@latest

Awesome! It worked. Thanks for your effort @Lumoc !!

Fix is here with v1.0.18 of my plugin

sudo -E -n npm install homebridge-loxone-ws-adv@latest

I just installed it with a fresh homebridge. It works and I’m testing before replacing the main system.  I’ve seen a few disconnects from the miniserver but I’ll advise of any problems.
Thanks for your work!

Hi,
I'm trien to get Loxone Ws Adv 1.0.18 running.
We are using:
Node.js Version v14.16.0
Npm Version: v7.6.2
So, basicly it will first connect once, show rooms and accessories, but after 1 sec it starts spamming:
`Loading logs using native method...
File: /var/lib/homebridge/homebridge.log
r: undefined ERR_STREAM_WRITE_AFTER_END
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:33:59] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:01] TypeError: Cannot read property 'closeDescription' of undefined
at Connection. (/usr/local/lib/node_modules/homebridge-loxone-ws-adv/node_modules/node-lox-ws-api/lib/Connection.js:62:62)
at WebSocketClient.emit (events.js:315:20)
at WebSocketClient.failHandshake (/usr/local/lib/node_modules/homebridge-loxone-ws-adv/node_modules/websocket/lib/WebSocketClient.js:339:10)
at ClientRequest. (/usr/local/lib/node_modules/homebridge-loxone-ws-adv/node_modules/websocket/lib/WebSocketClient.js:278:18)
at ClientRequest.emit (events.js:315:20)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:641:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
at HTTPParser.execute ()
at Socket.socketOnData (_http_client.js:509:22)
at Socket.emit (events.js:315:20)
[13/03/2021, 13:34:01] Got SIGTERM, shutting down Homebridge...
 Code: 143, Signal: null
[13/03/2021, 13:34:11] [HB Supervisor] Restarting Homebridge...
[13/03/2021, 13:34:11] [HB Supervisor] Starting Homebridge with extra flags: -I
[13/03/2021, 13:34:11] [HB Supervisor] Started Homebridge v1.3.3 with PID: 939
Initializing HAP-NodeJS v0.9.3...
[13/03/2021, 13:34:12] Loaded config.json with 0 accessories and 2 platforms.
[13/03/2021, 13:34:12] Loaded 0 cached accessories from cachedAccessories.
[13/03/2021, 13:34:12] ---
[13/03/2021, 13:34:13] Loaded plugin<EMAIL_ADDRESS>[13/03/2021, 13:34:13] Registering platform 'homebridge-config-ui-x.config'
[13/03/2021, 13:34:13] ---
[13/03/2021, 13:34:13] Loaded plugin<EMAIL_ADDRESS>homebridge API version: 2.7
[13/03/2021, 13:34:13] Registering platform 'homebridge-loxone-ws-adv.LoxoneWs'
[13/03/2021, 13:34:13] ---
[13/03/2021, 13:34:13] Loading 2 platforms...
[13/03/2021, 13:34:13] [Config] Initializing config platform...
[13/03/2021, 13:34:13] [Config] Running in Service Mode
[13/03/2021, 13:34:13] [Loxone] Initializing LoxoneWs platform...
[13/03/2021, 13:34:13] [Loxone] Info: rooms array not configured. Adding every room.
[13/03/2021, 13:34:13] [Loxone] object
New WS: <IP_ADDRESS>:49000
[13/03/2021, 13:34:13] [Loxone] Platform - Waiting 8 seconds until initial state is retrieved via WebSocket.
[13/03/2021, 13:34:13] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1000 normally closed
[13/03/2021, 13:34:15] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:15] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:17] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:17] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:20] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:20] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:21] [Loxone] Platform - Retrieving initial config from http://hannes:mypass@<IP_ADDRESS>:49000/data/LoxApp3.json
[13/03/2021, 13:34:21] [Loxone] Platform - There was a problem connecting to Loxone.
[13/03/2021, 13:34:22] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:22] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:24] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:24] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:25] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:25] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:26] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:26] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:28] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:28] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:28] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:28] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
Websocket Connection closed:  4003 Forbidden - IP <IP_ADDRESS> temporarily blocked, too many failed login attempts (120)
[13/03/2021, 13:34:30] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:30] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:30] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:30] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:32] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:32] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:32] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:32] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:32] [Homebridge UI] Rebooting linux server with command: "sudo -n shutdown -r now"
[13/03/2021, 13:34:33] [HB Supervisor] Stopping services...
[13/03/2021, 13:34:33] Got SIGTERM, shutting down Homebridge...
[13/03/2021, 13:34:33] [homebridge-loxone-ws-adv] This plugin is taking long time to load and preventing Homebridge from starting. See https://git.io/JtMGR for more info.
[13/03/2021, 13:34:34] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:34] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:34] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:34] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
Websocket Connection closed:  4003 Forbidden - IP <IP_ADDRESS> temporarily blocked, too many failed login attempts (114)
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:36] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[13/03/2021, 13:34:38] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[13/03/2021, 13:34:38] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[13/03/2021, 13:34:58] [HB Supervisor] OS: Linux 5.10.17-v7l+ arm
[13/03/2021, 13:34:58] [HB Supervisor] Node.js v14.16.0 /usr/local/bin/node
[13/03/2021, 13:34:58] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[13/03/2021, 13:34:58] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[13/03/2021, 13:35:03] [Homebridge UI] Homebridge Config UI X v4.40.0 is listening on :: port 8581
[13/03/2021, 13:35:04] [HB Supervisor] Starting Homebridge with extra flags: -I
[13/03/2021, 13:35:04] [HB Supervisor] Started Homebridge v1.3.3 with PID: 763
Initializing HAP-NodeJS v0.9.3...
[13/03/2021, 13:35:05] Loaded config.json with 0 accessories and 2 platforms.
[13/03/2021, 13:35:05] Loaded 0 cached accessories from cachedAccessories.
[13/03/2021, 13:35:05] ---
[13/03/2021, 13:35:06] Loaded plugin<EMAIL_ADDRESS>[13/03/2021, 13:35:06] Registering platform 'homebridge-config-ui-x.config'
[13/03/2021, 13:35:06] ---
[13/03/2021, 13:35:07] Loaded plugin<EMAIL_ADDRESS>homebridge API version: 2.7
[13/03/2021, 13:35:07] Registering platform 'homebridge-loxone-ws-adv.LoxoneWs'
[13/03/2021, 13:35:07] ---
[13/03/2021, 13:35:07] Loading 2 platforms...
[13/03/2021, 13:35:07] [Config] Initializing config platform...
[13/03/2021, 13:35:07] [Config] Running in Service Mode
[13/03/2021, 13:35:07] [Loxone] Initializing LoxoneWs platform...
[13/03/2021, 13:35:07] [Loxone] Info: rooms array not configured. Adding every room.
[13/03/2021, 13:35:07] [Loxone] object
New WS: <IP_ADDRESS>:49000
[13/03/2021, 13:35:07] [Loxone] Platform - Waiting 8 seconds until initial state is retrieved via WebSocket.
[13/03/2021, 13:35:07] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1000 normally closed
[13/03/2021, 13:35:09] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:12] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:29] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:30] [Loxone] Platform - Retrieving initial config from http://hannes:mypass@<IP_ADDRESS>:49000/data/LoxApp3.json
[13/03/2021, 13:35:30] [Loxone] Platform - There was a problem connecting to Loxone.
[13/03/2021, 13:35:31] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:33] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:35] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:37] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1000 normally closed
[13/03/2021, 13:35:40] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
[13/03/2021, 13:35:42] [Loxone] LOXONE WS: connect
Websocket Connection closed:  1002 Control frames must not be fragmented.
`
Then after a while it will loop like this:
 [13/03/2021, 13:31:58] [Loxone] LOXONE WS: connect WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006 [13/03/2021, 13:31:58] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END [13/03/2021, 13:31:58] [Loxone] LOXONE WS: connect WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006 [13/03/2021, 13:31:58] [Loxone] LOXONE WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END Websocket Connection closed:  4003 Forbidden - IP <IP_ADDRESS> temporarily blocked, too many failed login attempts (1) [13/03/2021, 13:31:59] [Loxone] LOXONE WS: connect Websocket Connection closed:  1002 Control frames must not be fragmented. Websocket Connection closed:  1002 Control frames must not be fragmented. Websocket Connection closed:  4003 Forbidden - IP <IP_ADDRESS> temporarily blocked, too many failed login attempts (105) Websocket Connection closed:  4003 Forbidden - IP <IP_ADDRESS> temporarily blocked, too many failed login attempts (105)

@Masegi I have the same issue. Do you have solved it?

no actually not :(

I've did a clean install and having this issue too. Any fixes?

well, I switched to another loxone plugin, that's working fine.

@Masegi which one?

https://github.com/ActiveByte/homebridge-loxone-connect


Motivation
In https://github.com/apache/pulsar/pull/20068 we changed the way that the AuthorizationService is implemented. I think this approach could have unintended consequences. Instead, I think we should change the Consumer and the Producer logic to call the correct AuthorizationService method. I propose an update to the Consumer and Producer logic here #20142.
Given that our goal is to deprecate the AuthorizationService methods for canProduce and canConsume, I think we should not change their implementations.
Modifications

Revert https://github.com/apache/pulsar/pull/20068

Verifying this change
This change is trivial. It removes certain test changes that were only made to make the previous PR work.
Documentation

[x] doc-not-needed

Matching PR in forked repository
PR in forked repository: Skipping PR as I ran tests locally.

Thank you for your point, you are right!
In #20068, I have only considered the default authorization provider, so it looks like the correct implementation. If the custom authorization didn't handle TopicOperation, which introduces unintended consequences.

After revert, the test cases modification should be added later.

@michaeljmarshall
To avoid conflicts, I cherry-picked all three patches into branch 3.1.

https://github.com/apache/pulsar/pull/20068
https://github.com/apache/pulsar/pull/20142
https://github.com/apache/pulsar/pull/20143


MSID: 88670 Version: 2 DOI: 10.1101/2<IP_ADDRESS>6933

MSID: 88670
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6933
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88670
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6933

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88670v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6933
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88670/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Hi @fred-atherden, @acollings this one was in todays list in the tracker so I've uploaded the PR/AR but I'm wondering if it was actually a duplicate because it isn't in the awaiting reviews column and now has 2 lots of reviews/responses.

Yes @KJT08 this is duplicated. Can you investigate what happened, and clean this up, deleting the ones we don't need, being sure to add them to the deleted spreadsheet, and removing the duplicate entry? Many thanks.


now foreign key is work right

Now foreign key is work right, because in the past it did not work correctly.
I have not come to create a working migration, so I had to edit your code.

Your PR seems it will fix the issue but there is still an issue.
You used unsigned as column type but unsigned is a column modifier not type so we need to use like that
--fields="owner_id#integer#unsigned
I'll add it soon.

Fixed at #84e3a5071

well done


sheets:v4 metadataId is int, no as_bytes() method

Hi Lewin,
The Sheet v4 API is generally working well. In the generated code there are two compilation errors, both this same issue:
let rel_path = format!(
     "v4/spreadsheets/{spreadsheetId}/developerMetadata/{metadataId}",
     spreadsheetId = percent_encode(params.spreadsheet_id.as_bytes(), NON_ALPHANUMERIC),
     metadataId = percent_encode(params.metadata_id.as_bytes(), NON_ALPHANUMERIC)
);

Here params.metadata_id is type i32, not String, so there is no as_bytes() method. Inserting .to_string() fixes it.
I looked only briefly at generate.py and didn't see the parameters types obviously available. Is this available somewhere and the right fix? I suppose a Rust-level conversion would work as well. Either way, it's a minor issue and the code is working well.

Thank you for reporting this! I will be taking a look shortly.

Thank you for reporting this! I will be taking a look shortly.

To my knowledge, ddf224ef4cb447a85ae4caa536f99dff221316e7 fixes this. Can you regenerate and try again from git head?

To my knowledge, ddf224ef4cb447a85ae4caa536f99dff221316e7 fixes this. Can you regenerate and try again from git head?

Works great! Thanks for the quick fix.

Works great! Thanks for the quick fix.


For code

Your work is wonderful and very helpful to me in multi-modal image registration. I want to know when the code will be made public? Thank you author.

您的工作很棒，对我在多模态图像配准方面非常有帮助。我想知道代码何时公开？谢谢作者。

a week

您的工作很棒，对我在多模态图像配准方面非常有帮助。我想知道代码何时公开？谢谢作者。

one week

It’s worth to learn. Thank you, hope the code will be soon public

您的工作很棒，对我在多模态图像配准方面非常有帮助。我想知道代码何时公开？谢谢作者。

one week

Excuse me, about the code it's very worth to learning. Can you share it please.

Excuse me, about the code it's very worth to learning. Can you share it please? Thank you very much!


Update Swift Set/Dictionary formatters in preparation of upcoming changes

https://github.com/apple/swift/pull/19213 will change the internal layout of Set/Dictionary. Prepare for this by adding lldb support for the new storage layouts.
Bonus change: fix the new synthetic children frontend so that enumerating all children takes linear time. (It was quadratic with the old formatters.)

This PR keeps support for old layouts. This can be removed in a followup PR later.


Add option to chose "run mode"

Add option to UI to run locally in Docker or iin ACA in Dynamic Sessions.

solved in https://github.com/yanivvak/dream-team/pull/22

implemented


KeyVault: Batch Operations

Item out of date, closing as there are no plans in the future for this


button.tertiary padding set to 0

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after), along with a short summary of changes:
Issue
Fixes #533
Changelog:
Small change on columns block styling
Test URLs:

Original: https://www.sunstar.com/jp/about
Before: https://main--sunstar--hlxsites.hlx.live/jp/about
After: https://issue-533--sunstar--hlxsites.hlx.live/jp/about

Library

[ ] New Blocks introduced in this PR
If yes, please provide details below
Block Name : For e.g. cards

[ ] Documented in sidekick library

[ ] New variations introduced in this PR
Variation Name :  For e.g. cards (grid)

[ ] Documented in sidekick library

[ ] New mixins introduced in this PR
Mixin Name :  For e.g. compact, white

[ ] Documented in sidekick library

Hi @ehrro, I confirmed all pages with columns block, this change won't impact any existing pages. Please have a check.


Login with something other than Graph

I'm trying to retrieve a token a use to login Dynamics (via a Teams Messaging extension). I have a v1 AAD App that I gave delegated permission. I expected to be able to just set the resource as my Dynamics and then use the token once I retrieved it, but I keep getting permissions errors. Are there steps that are missing to have it work with something other than than Graph? Also when I do get the token via my Messaging Extension in Teams and then pass it into jwt.ms the aud value is graph.com but when I test the connection via the Bot service the aud is Dynamics

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

ID: a9a43e68-83a3-1adc-0c55-e277ddb98c6b
Version Independent ID: 5c46848d-bc20-480e-4571-00a283d930a2
Content: Add authentication to your bot via Azure Bot Service - Bot Service - Bot Service
Content Source: articles/v4sdk/bot-builder-authentication.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

*** I solved the Issue by recreating my connection. It appears that the connections can't really be edited? I originally created it with Graph as the resource and then went back and updated it to dynamics after I'd gotten the sample working. I tried changing the resource multiple times with no success. I don't know if it is a bug in the portal or something else but it was very frustrating.

Closing since the issue was resolved.


Pulling shared-with-me folder

Hi,
How can one pull shared folders with drive pull without having to specify every id of the shared content ?
Regards,
Nic

Hello there @nvanheuverzwijn. Thank you for the question and welcome to drive.
So the last time I checked, you have to actually add the shared folder to your Google Drive and once it is part of yours, then you can pull it normally by name or by file-id e.g
$ drive pull assn3

Please see the screenshots below

Ah, ok I see.
Thanks for your answer.

This is ok unless you're going to use a service account to push files in a no-prompt cronjob.
I'm stucked in the middle as I can push content but no way to share this to the owner of the shared drive..

It does not work. Today, there is no such thing than "Add to my drive" option, there is only an "Add shortcut to my drive" option. It creates a link to the shared content.
The tool downloads the link as a zero-byte file and nothing can be done with it.


Bug Report: are sequences ints check in Python API

Hi,
In commit f2689a1, in lines 179 and 320 a new condition was introduced of the form:
# 'AC' will be type string. But potentially the original 'AC' were ints.
if type(next(sequences.keys())) == int:

and it results in the following error:
TypeError: 'dict_keys' object is not an iterator

I have implemented locally an easy enough solution that I hope may be helpful for you:
if type(list(sequences.keys())[0]) == int:

Thanks! I'll add the fix.


[Feature request] Possibility to kill ports without restarting them

Added a --kill-only flag to exit the script after killing the tunnels!

Thanks for the quick fix!

Nerds


No such driver found

I am getting the following error in version 1.3.0:
     Error: No such driver found, please try to install it via npm install db-migrate-pg or npm install -g db-migrate-pg
      at Object.exports.connect (node_modules/db-migrate/lib/driver/index.js:77:11)
      at Object.exports.connect (node_modules/db-migrate/connect.js:15:10)
      at /home/vinicius/Luizalabs/Projects/fat-copy/faturamento-api/node_modules/db-migrate/lib/commands/up.js:15:13
      at tryCatcher (node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromiseCtx (node_modules/bluebird/js/release/promise.js:641:10)
      at _drainQueueStep (node_modules/bluebird/js/release/async.js:97:12)
      at _drainQueue (node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues [as _onImmediate] (node_modules/bluebird/js/release/async.js:15:14)
      at processImmediate (internal/timers.js:461:21)

Until version 1.2.2 it was working perfectly, but after new versions were published the lib is showing an error.
Any solution?

its your setup. There is nothing that changed around this at all. Something is wrong on your side. Just try setting it up again.

@wzrdtales why did you close the issue? The problem persists.
The error is not on my side, since until yesterday in version 1.2.2 everything was working perfectly.
After the publication of the new versions (yesterday, May 4th) the library is no longer working.
My node version is v12.22.12

I downgraded to 1.2.2 and it works again.

@wzrdtales, are you sure? This is happening for me and was never an issue in the past.

yes sure. I tried to reproduce and its impossible to reproduce for me.
further its impossible that the version change causes this. the change was literally this:
https://github.com/db-migrate/pg/commit/24e231e01adf50cf260636cd50212d91e137b49d
and nothing else. This can't cause your described issues. please provide a full repository reproducing this issue

My node version is v12.22.12

your node version is not supported. please upgrade to node 14, node 12 is long out of support and is a security hazard.

please refer to https://github.com/nodejs/release#release-schedule for actually supported node versions, we don't support any node version that effectively shouldn't be used anymore since it doesn't receive any security patches anymore.

I can confirm the Node version is the issue. I was running a pipeline job on v12 and it didn't work. I switched to 16 and it is working. Thanks for clarifying.

@wzrdtales I think it's a good practice to put this information on the minimum version of node both in the readme and in the package.json (engine -> node)
Because there is no such information anywhere in the project


PCA post-processing removes gradient from embeddings

As the tensorflow code uses numpy to PCA the output embeddings, it is not possible to take advantage of this when adding torch-vggish to other networks (the usecase for this is relatively small). It would be useful to reimplement the PCA algorithm so that it can operate on Torch tensors.

https://github.com/harritaylor/torchvggish/commit/4bb86592ff8df6a1bdb00de7157d699f516bd130 Addresses this.


Fix firing twice per key event on Windows (and kitty?)

https://github.com/crossterm-rs/crossterm/issues/797
A recent change in Crossterm has causes Kitty and Windows key events to fire twice, once on press and again on release. We need to start explicitly ignoring release events (or upgrade to a crossterm version that allows opting out of this feature, PR ongoing: https://github.com/crossterm-rs/crossterm/pull/778)
Until this is fixed it is unusable on windows.

Fix applied and released. Still not tested on windows, but it seems to work well on kitty now at least.


searchPath for ocaml pkgs

While trying to use Ocaml packages provided by nixpkgs I found that we need to export some environment variables, so I could add these environment variables to searchPath but these env vars are associated with an ocaml version folder which depends on fetchNixpkgs, for instance, nixpkgs stable: lib/ocaml/4.12.0/site-lib
Should I create something as ocamlPath412? or maybe, if it's possible, we could allow the use of globing in searchPath to use something like lib/ocaml/*/site-lib to keep ocamlPath
On the other hand, we could forget ocamlPackages and give support to the packages using opam as with ruby gems

Does this allow you to do what you need?
$ cat -n makes/nested/main.nix
     1	{ __nixpkgs__
     2	, makeSearchPaths
     3	, ...
     4	}:
     5	let
     6	  ocaml = __nixpkgs__.ocaml_4_03;
     7	  ocamlPackages = __nixpkgs__.ocamlPackages_4_03;
     8	in
     9	makeSearchPaths {
    10	  ocamlBin = [ ocamlPackages.wtf8 ];
    11	  ocamlLib = [ "${ocamlPackages.wtf8}/lib/ocaml/${ocaml.version}/site-lib" ];
    12	}

$ just m . /nested
"$(nix-build --show-trace --no-out-link)/bin/m" . /nested
Makes v21.10-linux

/nix/store/96nqnrdli3arypki129j81djkhgkvhdj-make-template-for-make-search-paths
export PATH="/nix/store/ixj4gm1ynjgh7bmfh5xk6hdkm5afnv6p-ocaml4.03.0-wtf8-1.0.2/bin${PATH:+:}${PATH:-}"
export OCAMLPATH="/nix/store/ixj4gm1ynjgh7bmfh5xk6hdkm5afnv6p-ocaml4.03.0-wtf8-1.0.2/lib/ocaml/4.03.0/site-lib${OCAMLPATH:+:}${OCAMLPATH:-}"

this works perfect, I'm adding an additional PATH with this syntax


[do not merge] Test execute notebooks CI

Do not merge, this PR is to try if CI breaks executing the modified notebook

This is failing due to #1552, not because of a problem with your script. I'm not sure how this notebook made it into the repo... maybe before we started testing with Python 3.9?

Oh, I see. Thanks for looking into this Frank! I can make the changes if you want, so feel free to assign the issue to me.
I found that /run/save-jobs.ipynb also fails with the message Unable to retrieve result for job csnfd2mp1vzg008ab670. Job was cancelled. as you can see in 3606f1b.


Log output for core specs

Fixes #10837.

Opened https://github.com/atom/atom/issues/10840 about the flaky TextEditorPresenter spec.


https://www.internalfb.com/intern/bug-bounty/get-canary-token

These guidelines are to help understand the payout decisions for each focus area and the methodology we apply when awarding bounty payouts. Each guideline provides a maximum payout for a particular bug category and describes what mitigating factors would prompt a deduction from that amount. In general, the more mitigating factors that exist, the lower the bounty will be.
The triage team will apply these guidelines when assessing reports submitted to our program, however as these are only guidelines, it is within the team’s sole discretion to assess the mitigating factors and deduction amounts on a case-by-case basis.

ร้างความพยายาม SSRF แล้ว
สร้างความพยายาม SSRF ใหม่<PHONE_NUMBER>110490 แล้วด้วย URL: https://www.internalfb.com/intern/bug-bounty/get-canary-token/57a2204927f94e6094aa1b599680461b/


Update LOCALIZATION_CONTRIBUTORS

Summary
Details and comments

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for your interest in contributing to Qiskit translations. Please go ahead and follow steps 4, 5 and 6 in the Contributing to Qiskit documentation.

I’m just waiting the adding of italian language. Afterwards, I’ll continue asap.

Added the On Hold label until Italian is added.


1.3.0 release pre-built package contains a buggy openblas version.  Causing gluon data loader with large num_workers to crash

Description
In latest mxnet pip prebuilt packages, when using gluon data loader with num_worker > certain number, it may raise error:
 OpenBLAS : Program will terminate because you tried to start too many threads.

Related issue: https://github.com/xianyi/OpenBLAS/issues/1735
Environment info (Required)
Ubuntu 16
pip install mxnet==1.3.0

from mxnet import gluon
dataset = xxx
batch_size = 16
loader = gluon.data.DataLoader(dataset, batch_size, num_workers=16)

@szha

Looks like we just need to upgrade the openblas dependency to 0.3.3. Since it doesn't require code change in mxnet I will prepare a post-release to include the upgrade shortly.

@mxnet-label-bot[Bug, BLAS]

@ankkhedia @Roshrini @lupesko - this may impact the windows instructions since we're currently having people use OpenBLAS v0.2.19 when building from source. WDYT @szha ?

@aaronmarkham both versions should work. It's up to the user to decide which version of dependency to include.

is impact the windows? Windows need to upgrade openblas?

i am only receiving report on ubunutu so far

ok,not upgrade now,wait report.

@zhreshold the 1.3.0.post0 releases contain the upgrade. Please verify.

Thanks @szha.
@yajiedesign are you waiting for a confirmation before you publish the windows pip package for 1.3.0?

@szha Verified with same code, 1.3.0 failed and 1.3.0.post0 passed. Thanks for the timely fix!

@lupesko At present, I have uploaded 1.3.0, waiting for report.


Proposal  of unifying the the merged brances into one cohesive story.

added typography
merged and extended the two existing stories

Great work!


Testing with Azure on Windows

Implement at least subbattery of tests that do not rely on latex distribution.
Do some more research on whether there is any possibility to get latex in azure on windows.

https://github.com/QCoDeS/Qcodes/blob/master/azure-pipelines.yml

We should bump the minimum required conda version in the docs then, too. I  am at 4.7.12 now.

There is also recent failures on the other platforms due to conda / some setuptools dependency:
RemoveError: 'setuptools' is a dependency of conda and cannot be removed from
conda's operating environment.

Quick googling suggests to me that this may be due to azure's conda being dated, so it may be worth just waiting for a little bit. No big cause of concern ATM.

Seems to be a more general issue https://github.com/conda/conda/issues/9337 - let's wait for a couple of days for what is happening there.
Although this approach https://github.com/conda/conda-prefix-replacement/blob/master/.travis.yml#L9-L14 is apparently more more robust on Travis -- would it also work on Azure? @tobiasraabe?

I used the hotfix explained in the same thread which uninstalls setuptools via pip first and then installs it again using conda. This is only necessary on Linux and MacOS. Windows seems fine.
Team Windows: 1
Team Rest: 0
:)
https://github.com/OpenSourceEconomics/respy/pull/260/files

Perfect, thanks!
In the grand scheme of things in terms of CI, this seems closer to our experience, though :-)

Team Windows: 1
Team Rest: ~0~ 5

error does not occur anymore, still action required?

The RemoveError -- probably no action required, seems like it was a general issue and hopefully they solved it on the conda (?) side, but I did not follow up on it.

We fixed the error in #70. I bookmarked the conda issue and report back if there is indeed a cleaner solution in the future.

Haha, thanks for the reminder, that's what happens my memory if I am doing 7 things at once...

Fixed in #74 but without Latex testing.


Fix Nvidia driver build for RHEL 9.4

This was failing with the out of beta kernel naming on RHEL 9.4

LGTM


An incorrect and unused function in class Model/Model

Function "insert" is unused and have a bug:
    public function insert($class, $key_array, $value, $key = null)
    {
        if (property_exists('Jikan\Model\\'.$class, $key)) {
            if (is_null($key)) {
                $this->{$key_array}[] = $value;
            } else {
                $this->{$key_array}[$key] = $value;
            }
        }
    }

if (property_exists('Jikan\Model\\'.$class, $key)) {
$key is element id in $key_array.
Solution:
  public function insert($class, $key, $value, $key_array = null):void
  {
   if (property_exists('Jikan\Model\\'.$class, $key)) {
      if (null === $key_array) {
        $this->{$key}[] = $value;
      } else {
        $this->{$key}[$key_array] = $value;
      }
    }
  }

And why used $class and 'Jikan\Model\\'.$class,  in function property_exists, this does not overcomplicate the code? It can be replaced by:
(property_exists(\get_class($this), ...))

Hey, you're right! That's pretty old code actually - from last year. I've removed the unused method - will add (property_exists(\get_class($this), ...)) after a few tests.
We're currently working on a rewrite of the Jikan API. https://github.com/jikan-me/jikan/tree/2.0.0-dev

Ok, I just decided to improve my programming skills, so I started to disassemble the various libraries on GitHub, and I found this old code.
I close the issue. Thanks for answer.

Thanks for finding that! :)

So, i noticed in v2.0.0 abstract model class with get/set functions was replaced with a single 'set' static function in model (like setProperties or fromParser) and 'get' function for each attribute (like getUrl or getTitle), why is it better than the previous solution?
I do not ask to waste time explaining to me, but would be grateful for a link to the article :)

Hi @tizis,
We're making a huge effort to use return types everywhere and make sure you can autocomplete anything that comes out of the lib in v2.
When using public properties we have no control over what users might put in it and possibly breaks the autocompletion.
Here is an article that talks about this and other good OOP practices that explains it a bit:
https://www.ibm.com/developerworks/opensource/library/os-php-7oohabits/index.html?ca=drs-tp4408


CONTRIBUTING.md is not available

https://github.com/zendframework/zendframework/blob/master/CONTRIBUTING.md
as well as
https://github.com/zendframework/zendframework/blob/master/CONDUCT.md
but you have links to them on https://github.com/zendframework/zendframework

@kaurov  thank you for letting us know


Thoughts on separate out HidDevice traits publish for mocking read/writes?

Does anyone have a good mocking/testing strategy around HidDevice.read/write?
It seems like one solution is separating the HidDevice traits so I can make a fake one myself and pass into my function by trait instead of concrete.
Thoughts?

You can always define your own trait, and implement it for the read HidDevice, and for your mock.
Example:
use hidapi::HidDevice;

trait HidMockable {
    fn my_write(&self, data: &[u8]) -> HidResult<usize>;
    fn my_read(&self, buf: &mut [u8]) -> HidResult<usize>;
    // etc...
}

impl HidMockable for HidDevice {
    fn my_write(&self, data: &[u8]) -> HidResult<usize> {
        self.write(data)
    }
    fn my_read(&self, buf: &mut [u8]) -> HidResult<usize> {
        self.read(buf)
    }
    // etc...
}

struct MyMock;

impl HidMockable for MyMock { ... }

You would then use the HidMockable trait to pass around your exchangeable implementation.
fn takes_hidmockable<T: HidMockable>(mock_or_real: &T) {
   // Do stuff with device
}

Thanks! that worked great. I was so close :) If future folks want to see what I came up with
https://github.com/jacobrosenthal/uf2-rs/blob/e9b633f7e7e83d1730a50987ef041b81e9741da5/src/lib.rs#L701
https://github.com/jacobrosenthal/uf2-rs/blob/e9b633f7e7e83d1730a50987ef041b81e9741da5/src/lib.rs#L701
Still a lot of boilerplate in the closures, but got my tests to pass and code to work :)
Thanks again


[1.0] Update Darwin API for 1.0 launch

Reproduction steps
No reproduction steps, just API updates.

Bug prevalence
API Updates
GitHub hash of the SDK that was being used
e535710fe92824b9ad6a902e560f763173a0bd03
Platform
darwin
Platform Version(s)
No response
Type
Platform Issue
Anything else?
No response

@woody-apple could you describe what 'API Updates' actually means?
This bug seems very vague. I guess that may be by desgined as it was written and assigned exclusively to Apple engineers, however some form of description would still be nice.

could you describe what 'API Updates' actually means?

We had some internal API reviews of Matter.framework to align it with some API best practices.  This issue is about turning the results of those reviews into code changes.

Closing this, as we've got this split up enough


GridInterpolator2d should be converted to a JodaBean

It is not serializable to XML/Json and has no property API.
Also, currently it has no javadoc.

Current implementation has been lifted from OG-Platform, but needs writing sensibly from scratch.

Class has been replaced. Issue no longer relevant.


Not possible to correctly reuse Cosmos view

Cosmos (12.0.1)
Hi
There's an issue when you use cosmos view inside reusable view, like tableview cell, with updateOnTouch turned on. When cell is being reused you won't be able to set the same rating which was in the cell before reuse. Because of "previousRatingForDidTouchCallback" private variable which stores previously selected rating.
I've slightly modified demo project to illustrate the issue:

Resetting previousRatingForDidTouchCallback value in didSet for rating solves this issue.

Hi @xrayman, thanks for reporting the issue. Can you attach the source code for the demo that you modified please?

@evgenyneu https://github.com/xrayman/Cosmos
I've created a fork and pushed modified demo there

That's a very good point, @xrayman. I've added a new function prepareToReuse to the CosmoView. Here is an example of usage. This update is released as version 15. Thanks for your help!
public class PerformanceTableViewCell: UITableViewCell {
  @IBOutlet var cosmosView: CosmosView!

  override public func prepareForReuse() {
    // Ensures the reused cosmos view is as good as new
    cosmosView.prepareForReuse()
  }
}

Great! Thank you!


Improve diagnostic view for cqld4 routing statistics

Scenario: You are testing a system with cqld4 and you want to know how the load balancing policy is selecting over the available nodes.
This can be easily implemented by wrapping the selected load balancing policy in a diagnostic facade.
At some interval, the following details should be logged to a dedicated logger named 'CQLROUTING".

The current view of the topology as seen by the policy
A histogram of node selections since the last time it was reported.

Some of this has been made possible by augmenting how CQL cluster configuration is built, inserting stub layers needed to observe these details only when asked.
As part of this, #1799 should be considered for cohesion with diagnostic terms and how diagnostic filters are specified.


collect and push graph in CI

plugin can be used to push. but it should be verified

prioritize scraping with a bot, but use CI for cross-check


My branch

It looks like tabs are being used.  Is that intentional?

No, but it doesn't really matter. This is just a toy project I created to demonstrate git commands.


Git Fundamentals Microbyte

Closes #37

Checklist:

[x] Added activities for learners
[x] Didn't give the solutions to the added activities straight away
[x] Followed a LearnByDoing approach
[x] Clean and well documented code (if source code files are involved)
[x] Added images for better understanding if deemed necessary

@Ak-Shaw Can you be more specific on what I should improve? I explained most of the git command while doing activities. I made this Microbyte for people who does not have any idea about git and Github. I am ready to improve this Microbyte!

@itherohit Kindly don't get me wrong.
A MicroByte is not a tutorial.
A MicroByte is an interactive activity/module based content.
When I say interactive, it means that the content virtually forces the learners to do the digging on their own, no spoon feeding.
So, how can you improve?
Well, you can work on giving activities in such a fashion in which learners can understand the concepts behind the working of Git.
You can add upon whats already there. By adding more activities/micro-activities in which learners try to learn the concepts behind Git. Don't try to feed them with information, but curiosity.
If you have further queries, you are free to reach me, or any of the other advocates, on slack. We'll be more than happy to help you out.

We'll be moving the contents over to the Demo-Repo repository of the org.


Toggle CI Comments

Does the plugin  support toggle CI comments right now?

@TommyLike: What do you mean exactly with "toggle CI comments"?

@uwolfer  well,Show/Hide comments from CI Server,it's the same as button at right-buttom of the page:
openstack

@TommyLike: Thanks for your feedback. This looks like an openstack customization to Gerrit.
See: https://review.openstack.org/95743

Such a feature is now integrated in Gerrit, with a toggle button "Only comments". What happens in PolyGerrit, is that it hides all comments with an (invisible) tag starting autogenerated:.
CI plugins like the one for Jenkins now posts comments that way by default - see e.g. https://github.com/jenkinsci/gerrit-trigger-plugin/pull/366


Overlay

WHEN I see the Projects section.
THEN I see a overlay applied onto each card, which disappears when I hover over a specific card.

DONE! Checked on live servers and it worked.


Error starting Alarmo

Alarmo Version
v1.9.14
HA Version
2024.1.5
Bug description
A few days ago i got an error on my Alarmo Card about the entity. I looked at the log (see attached log after a full removal/new installation). I tried restarting HA, uninstalling/installing Alarmo but to no avail.
Steps to reproduce
Uninstall/reinstalling Alarmo from Integrations and HACS. Reboot. Install in HACS, install in Integrations. Same problem.
Relevant log output
Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 15:26:07 (1 occurrences)
Last logged: 15:26:07

Error setting up entry Alarmo for alarmo
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/alarmo/__init__.py", line 56, in async_setup_entry
    store = await async_get_registry(hass)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/alarmo/store.py", line 691, in async_get_registry
    return cast(AlarmoStorage, await task)
                               ^^^^^^^^^^
KeyError: 'sensor_groups'

Duplicate of #882


a <svelte:script> comparable to Next.js Script tag?

Is it worthy to have a <svelte:script> comparable to Next.js Script tag?
<svelte:script
  // a strategy to early load to insert in head before all other script, or lazy load at end of body;
  strategy="beforeInteractive | afterInteractive | lazyOnload | worker | ..."
  async
  src="https://www.googletagmanager.com/gtag/js?id=G-xxxxxx"
  on:load={() => {
    window.dataLayer = window.dataLayer || [];
    function gtag() { dataLayer.push(arguments); }
    gtag('js', new Date());
    gtag('config', 'G-xxxxxx');
  }}
 />

or extend current <svelte:body> to allow a content, and just leave whatever inside to the end of html body?
<svelte:body
  on:mouseenter={handleMouseenter}
  on:mouseleave={handleMouseleave}
  use:someAction

  <!-- Google tag (gtag.js) -->
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-xxxxxx"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag() { dataLayer.push(arguments); }
    gtag('js', new Date());
    gtag('config', 'G-xxxxxx');
  </script>
/>

Originally posted by @tx0c in https://github.com/sveltejs/kit/discussions/8306#discussioncomment-4574813

You can already put scripts in your components - just make sure they're not at the top level (ie they need to be inside a wrapper element). But is there any reason you wouldn't put that in src/app.html?

when we want to share such code as reusable  component.
I felt I needed such capability, when I was implementing following component:
https://github.com/xmlking/svelte-starter-kit/blob/main/src/lib/components/Analytics.svelte
Otherwise I had to use some hacks document.currentScript.getAttribut

Gotcha. As I say, putting the script inside an element (like <svelte:head> in Analytics.svelte) is the intended solution, so I'll close this

but there's a reason in some cases better to be at end of body not head, and Svelte should have a solution for that
Quote from https://stackoverflow.com/a/38407984

In short and simple language:

Place script that impacts the render of the page at the end of the body

But is there any reason you wouldn't put that in src/app.html?

Yes, because src/app.html is only 1 global impacting all pages, but in my project only part of pages need a special script before end of body
Please re-open

just google search why put script end of body not head?
got many reasons, this is from https://levelup.gitconnected.com/all-about-script-87fea475b976

The best practice is to put JavaScript

I'm not going to reopen this issue. There's a variety of ways you can get the <script> to the bottom of the page, but in your case since you're using the async attribute it simply doesn't matter.

There's a variety of ways you can get the


Improved URLs

Use real URLs instead of hashes. Encode more information like timespan or nodes on map in those URLs

Fixed by c06db625f30a150f60ec302de750732a4587dc20


Not failing handlers when sensu-api is disabled

Hey,
Is there a reason to fail handlers if sensu-handler can't connect to the api?
Since not all use cases call for the api and since some handlers don't use it either, maybe it should be allowed for a handler to run when the api is disabled.

I believe #139 will solve this.


Fix stietljes on Line() with square root singularities

1/sqrt(x+im)

Just subtract out at infinity


Drawing a dotted line( Edge ) between 2 nodes which are in 2 different networks.

Hi,
I need to draw a dotted line between 2 nodes which are in 2 different networks.
Here is the jsfiddle link : https://jsfiddle.net/eshch/6mwtgf3u/
In that link you can see there are 4 nodes in network1 and 3 nodes in network2  ( all the node id's are same ) now i need to draw a dotted edge from node1 in network 1 to node 1 in network 2 is that possible. If not how can we do that.
Many many thanks in advance.

I'd suggest to take a look at the vis documentation (http://visjs.org/). They also have a lot of good example of many different configurations, and very good documentation on how to set different attributes of the lines etc...

There is no example to show an edge between 2 nodes in 2 different networks.

Hi, since you already asked this on the vis github page, let's focus the discussion there.

On 11 Mar 2016, at 08:35, Esh-ch<EMAIL_ADDRESS>wrote:
There is no example to show an edge between 2 nodes in 2 different networks.
—
Reply to this email directly or view it on GitHub.

Sure. Thank you.


PurchaseUpdateListners not being called on production iOS build

Hello everyone,
I am not sure what actually happen with my code. I integrated the react-native-iap plugin into my iOS application. And it was working fine on local build or testflight build but when i release the mobile version of application and i made the subscription but nothing happened next. I assumed that purchaseUpdateListeners are not working on production build then i removed the listeners and write the code just after the requestSubscription send the response. And released the next version of application but still the same issue even getReceiptIOS not called. I am stuck into this. Help me to find out from this.
Here is my code : -
const purchases = await RNIap.requestSubscription(productId);
console.log(purchases, "purchase...")
this.validateTransactionReceipt(purchases);
validateTransactionReceipt method : -
validateTransactionReceipt = (purchase) => {
const receipt = purchase.transactionReceipt;
if (receipt) {
AppEventsLogger.logEvent("Subscription transaction receipt validated", { type: 'owner' });
const receiptBody = {
'receipt-data': purchase.transactionReceipt,
'password': subscriptionSecret
};
        RNIap.validateReceiptIos(receiptBody, true).then(receipts => {
            let lastReceipt = receipts.latest_receipt_info[receipts.latest_receipt_info.length - 1];
            console.log(lastReceipt, "lastReceipt...")
            let params = {
                productId: purchase.productId,
                transactionId: purchase.transactionId,
                autoRenew: purchase.hasOwnProperty("originalTransactionDateIOS") ? true : false,
                // autoRenew: true,
                transactionDate: purchase.transactionDate,
                status: "success",
                transactionReceipt: lastReceipt,
                paymentMode: receipts.environment,
                originalTransactionDateIOS: purchase.hasOwnProperty("originalTransactionDateIOS") ? purchase.originalTransactionDateIOS : purchase.transactionDate,
                originalTransactionIdentifierIOS: purchase.hasOwnProperty("originalTransactionIdentifierIOS") ? purchase.originalTransactionIdentifierIOS : purchase.transactionId
            }

            console.log(params, "params-1");
            this.subscriptionSaveHandler(params);
        });
        if (Platform.OS === 'ios') {
            RNIap.finishTransactionIOS(purchase.transactionId).then(response => {
                console.log(response, "finish");
            });
        }
    }
}

Thanks

I think you need to initially call validateReceiptIos with a false parameter first, and then if that call returns a 21007 then you call it with true.  That way it will work in both prod and sandbox.  That's something I ran into.

I am having this same issue even with "isTest" set to "false" in calling RNIap.validateReceiptIos().
Testing on an actual device with "isTest" set to "true" seems to work but when pushed to production is does not work.
Some how Apple's testers approve my app which I am not sure how.

Definitely when you validate the receipt validate in production (use false param), then if that returns with a status of 21007, validate in the sandbox (use true param).
Then after calling finishTransactionIOS(), also call finishTransaction().
Hope that helps!

@the-dut awesome!  Going to give that configuration a try.
Will report back what happens :D.
I just wish Apple and Google had more solid abilities for devs to test before going through the process of release flows just to fined out our code doesn't work :/.

@the-dut ok now I am getting endless password / log in prompts after calling RNIap.requestSubscription([productId])

It could be all the previous requests coming through that were never finalized.  Could be hundreds or thousands based on how much you've tested. Maybe once you get through them you might be ok.
ALso, are you testing on a real device?  Local or TestFlight? Are you using a Sandbox user or a production id?   And if sandbox user, do you have that id set up in your phone as a Sandbox user?
I never saw that issue.  But I can try to help.

ALso, are you testing on a real device?
Real Device via XCode :: iOS 13.6.1
Local or TestFlight?
Local
Are you using a Sandbox user or a production id?
Sandbox User Id
And if sandbox user, do you have that id set up in your phone as a Sandbox user?
They are set up
here is my code
purchaseUpdatedListener():

await RNIap.clearTransactionIOS();
            let receipt = purchase.transactionReceipt;

            validatePurchase(receipt).then(async resp => {
                console.log('validated purchase');
                console.log(resp);
                // let iosTransactionFinished = await finishTransactionIOS(purchase.transactionId);
                let transactionFinished = await finishTransaction(purchase, false);
                let result = await successfullySubscribed(purchase);

                if (result.success && !fullFirstLaunchFlow) {
                    goTo('Home');
                }
            });

validatePurchase():
const receiptBody = {
                    'receipt-data': receipt,
                    'password': '<shared secret>'
                };

                console.log('validating purchase');

                let validReceipt = await RNIap.validateReceiptIos(receiptBody, false);
                console.log('valid receipt');
                console.log(validReceipt);
                if(validReceipt.status === 21007){
                    validReceipt = await RNIap.validateReceiptIos(receiptBody, true);
                    console.log('valid receipt was 21007');
                    console.log(validReceipt);
                }

Is there a reason you have the finishTransactionIOS commented out?  You should do both finishTransactionIOS() and then finishTransaction()

I could be confused but I thought this description in the README meant to only use "finishTransaction" if using v4.1.0 or later.
I am currently using v4.5.4.
iOS only
Finish a transaction. Use finishTransaction instead for both platforms since version 4.1.0 or later.

Great point!  I do both just in case.

well, either way it never gets to those lines yet, lol.
I will uncomment that line.  Anymore I am willing to try anything to get this working :D

Just upgraded to v5.0.0 hoping something might of changed but no dice.
Still getting multiple pwd prompts.
I am getting 2 at a time and after second prompt it errors out with "E_UNKNOWN" cannot connect to iTunes.

Does it all start happening right when you add your updatedpurchaselistener?  If so, you may need to just get through all of the unfinished transactions first.  Or.. use your real apple id instead of the test user.

it all happens right at "requestSubscription()".  I never see another console log after that.
The only console log I see after requestSubscription executes is "Purchase Started !".
The next console log is "Purchase Failed!!" followed by the "E_UNKNOWN" errors inside of "puchaseErrorListener".

Did you try with your real Apple ID?

I have not tried that yet.  Do I need to add my real Apple ID as a tester?

No.  You can just use it I would think.

Using my Apple ID it only prompts me once and gives the "E_UNKOWN" error immediately.

just tried testing with a newly created Sandbox User but no dice.
2 pwd prompts and error.

what's really odd and I know it's not suppose to be this way now, is I use to have "finishTransaction()" before validating the receipt and it worked that way.

Quick update.
@the-dut  I submitted a build with everything setup how you suggested and it worked!! So now I am throwing caution to the wind and submitted it for production.

That's great news!  Let us know how it goes!

Thanks to all having discussions and sharing benefits in the current thread ❤

Sorry for the delayed report.
Forgot to add it works in production!!
Next up....accepting promotions so I can give my app for free to friends and family 😁

@BStenfors9119 what was the problem at all? Can you share exactly how you solve the problem? Thank you very much.

@BStenfors9119 what was the problem at all? Can you share exactly how you solve the problem? Thank you very much.

let receipt = purchase.transactionReceipt;
does not return anything returns empty string


[Urgent] Split personality for researcher in Biblio

Story
Split personality for researcher in Biblio
Context
https://telefoonboek.prd.rad.ugent.be/nl/people/800000028572
https://telefoonboek.prd.rad.ugent.be/nl/people/802001357329
These two people are the same, the person in case let us know they have two personalities in Biblio right now. In GISMO however this person has two different birth dates, but we think they might have made a mistake there.

Back office
One of his profiles is connected to an older department (EB02), which makes it seem they are not active anymore:

Front office
When looking up the publications in the front-office for the older UGent ID, you can find publications, but for the newer ID you cannot find any publications:

@miet These are 2 different people

@nics thank you for investigating. There was a hunch there was a mistake in GISMO because of several reasons. Apparently some records have been added to the wrong person the reviewers noticed now, creating the illusion of being the same (a secretary assistant asked us). I'll keep an eye out.


add testing to trade module

Currently, the 'Trade Module' does not have any testing functionality, which makes it challenging to ensure the reliability and accuracy of trades executed through the module
add Spring Boot test to test the layers of the module with Mocking of the lower layers.
add test containers to add integration tests

#62 closed this issue


[Snyk] Upgrade semantic-ui-react from 1.0.0 to 1.3.1

Snyk has created this PR to upgrade semantic-ui-react from 1.0.0 to 1.3.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 6 versions ahead of your current version.
The recommended version was released 5 months ago, on 2020-09-29.

Release notes

Package name: semantic-ui-react

1.3.1 - 2020-09-29🐛 Bug Fix

#4079 fix(TextArea): update onChange type (@ foooomio)

🏠 Internal

#4072 chore: use lodash-es to improve bundle size (@ layershifter)
#4073 chore: remove usages of lodash/fp in customPropTypes (@ layershifter)
#4068 chore: bump update a package with Ref component (@ layershifter)

Committers: 2

Oleksandr Fediashov (@ layershifter)
foooomio (@ foooomio)

1.3.0 - 2020-09-22🚀 New Feature

#4029 feat: introduce children function to shorthands (@ layershifter)

🐛 Bug Fix

#4060 fix(Transition): schedule changes only on status change (@ layershifter)
#4047 fix(Dropdown): handle text as a content in renderLabel (@ layershifter)

Committers: 1

Oleksandr Fediashov (@ layershifter)

1.2.1 - 2020-08-19🐛 Bug Fix

#4037 fix(Pagination): set a default activePage in Pagination's state (@ gcalica)
#4041 fix(Dropdown): fix handling of "Space" key  (@ layershifter)
#4043 fix(FormField): fix aria-invalid on error false (@ aoelen)

📝 Documentation

#4040 docs(Placeholder): fix description of the component (@ eugenelim)
#4039 docs(Ref): restore docs for a component (@ layershifter)

🏠 Internal

#4023 chore: update Ref dependency to latest version (@ jluxenberg)

Committers: 5

Gian Paolo Calica (@ gcalica)
Jared Luxenberg (@ jluxenberg)
Oleksandr Fediashov (@ layershifter)
@ eugenelim
@ aoelen

1.2.0 - 2020-08-12🚀 New Feature

#1739 feat(Modal): impliment Dimmer shorthand (@ qoalu)

🐛 Bug Fix

#4026 fix(Popup): do not throw if context & trigger are missing (@ layershifter)
#4018 fix(Dropdown): update typings for defaultValue & value (@ zhongeric)
#4019 fix(Popup|Visibility): update types definitions for props (@ daigof)

📝 Documentation

#3794 docs(SearchExampleStandard): use React hooks (@ rpatelcode)
#3795 docs(SearchExampleStandardCustom): use React hooks (@ rpatelcode)

🏠 Internal

#4027 chore(MountNode): deprecate component (@ layershifter)

Committers: 5

Diego Fortes (@ daigof)
Eric Zhong (@ zhongeric)
Oleg (@ qoalu)
Oleksandr Fediashov (@ layershifter)
Ramesh Patel (@ rpatelcode)

1.1.1 - 2020-08-03🐛 Bug Fix

#4014 fix(Dropdown): update search prop typing (@ charliematters)

📝 Documentation

#4012 docs(Modal): improve examples, use React hooks (@ layershifter)

🏠 Internal

#4011 chore: improve bundle size (@ layershifter)

Committers: 2

Oleksandr Fediashov (@ layershifter)
@ charliematters

1.1.0 - 2020-07-30🚀 New Feature

#4003 feat(Dropdown): add support for images, icons and flags in selected values (@ layershifter)
#3996 feat(Flag): include "england" as a valid value (@ layershifter)

🐛 Bug Fix

#4006 fix(Dropdown): compute proper selectedIndex in multiple (@ layershifter)
#4004 fix(Dropdown): handle keyboard events for arrows, space and enter keys locally (@ layershifter)
#3938 fix(Search): fix an error when showNoResults=false and arrow down is pressed (@ ysugimoto)
#3785 fix(Search): merge nested shorthand props for the  element (@ noinkling)
#3998 fix(Portal): throw an error if React.Fragment passed as trigger (@ layershifter)
#3995 fix(Accordion): update typings to include AccordionPanel on static props (@ layershifter)
#3901 fix(FormFiled): pass id when contains child elements or has content prop (@ srotbart)

📝 Documentation

#4010 docs: improve CodeSandbox integration (@ layershifter)
#4008 docs(Responsive): deprecate component (@ layershifter)
#3957 docs(Tab): add note that grid prop only applies to vertical menu (@ swrobel)
#3964 docs(TableExampleSortable): your description (@ evcodes)
#3713 docs: make get started instructions around themes more clear (@ justsml)
#3898 docs(README): correct webpack example link (@ snitin315)
#3997 docs(SidebarExampleTransitions): fix look of the example (@ layershifter)
#3881 docs(LabelExampleImageColored): update example to match image names (@ isnifer)

🏠 Internal

#4009 docs: fix IE11 issues (@ layershifter)
#4001 chore:bump dependencies, minor fixes (@ layershifter)
#4000 chore:bump dependencies (@ layershifter)
#3999 chore:add bundle size metrics (@ layershifter)
#3993 chore:use CircleCI workflows (@ layershifter)
#3992 chore:add github action to check PR labels (@ layershifter)

Committers: 9

Anton Kuznetsov (@ isnifer)
Dan Levy (@ justsml)
Eddy Varela (@ evcodes)
Malcolm (@ noinkling)
Nitin Kumar (@ snitin315)
Oleksandr Fediashov (@ layershifter)
Sergey Rotbart (@ srotbart)
Stefan Wrobel (@ swrobel)
Yoshiaki Sugimoto (@ ysugimoto)

1.0.0 - 2020-07-21This release does not have any breaking changes. Versioning was changed to follow Semver.

docs: remove knobs usage #3988 (layershifter)
chore(Dropdown): remove deprecated lifecycle methods #3986 (layershifter)
chore: use react-intersection-observer in docs to improve perf #3985 (reefman001)
chore(Transition): remove deprecated lifecycle methods #3982 (layershifter)
chore(Sticky): remove usage of deprecated lifecycle methods #3974 (layershifter)
chore(Visibility): remove usage of deprecated lifecycle methods #3973 (layershifter)
chore(TransitionGroup): remove deprecated lifecycle methods #3970 (layershifter)
chore(Search): replace deprecated lifecycle methods #3968 (layershifter)
chore: use ModernAutoControlled component #3967 (layershifter)
chore(TransitionablePortal): remove usage of UNSAFE_* methods #3966 (layershifter)
fix(customProptypes): add a check for Element existance #3965 (layershifter)
docs(README.md): fix formatting #3958 (klunico)
docs(VisibilityExampleUpdateOn): Correcting Typo #3952 (mattorton)
fix(Input): add 'inputMode' attribute to input #3916 (RoyalHunt)

    from semantic-ui-react GitHub release notes

Commit messages

Package name: semantic-ui-react

aff25ee 1.3.1
9830ac6 fix(TextArea): fix textarea onChange type (#4079)
9399332 chore: use lodash-es to improve bundle size (#4072)
26daf99 chore: remove usages of `lodash/fp` in customPropTypes (#4073)
42f6e64 chore: bump update a package with `Ref` component (#4068)
2bc1275 docs: update CHANGELOG.md [ci skip]
30becd1 1.3.0
40903c2 feat: introduce `children` function to shorthands (#4029)
2d368b9 fix(Transition): schedule changes only on `status` change (#4060)
859146f fix(Dropdown): handle `text` as a content in `renderLabel` (#4047)
c3640e4 docs(changelog): update changelog [ci skip]
e94ccd9 1.2.1
d0dc3c4 fix(FormField): fix aria-invalid on error false (#4043)
1c24915 fix(Dropdown): fix handling of "Space" key (#4041)
e8d07f9 docs(Placeholder): fix description of the component (#4040)
b96e411 docs(Ref): restore docs for a component (#4039)
bf87dd2 chore: update Ref dependency to latest version (#4023)
4dba2f1 fix(Pagination): set a default activePage in Pagination's state (#4037)
ebdb893 docs(changelog): update changelog [ci skip]
e3862aa chore: fix lint-staged git add use [ci skip]
3e730d6 chore: remove changelog generator [ci skip]
bb4b00a 1.2.0
cb9fbb3 chore(MountNode): deprecate component (#4027)
ffaf2c1 fix(Popup): do not throw if `context` & `trigger` are missing (#4026)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Need to read firebase(firestore data)

Hi,
Can you upload a sample code to read firestore(Google's firebase storage) data??

Thank you for your feedback! We don't have any plan to make sample code for firestore. I can't provide the link however Google has good sample code on their document.


Fixed the conditional logic for SELECT, RADIO and CHECKBOX

The fix addresses issues related to conditional evaluation for SELECT, RADIO & CHECKBOX elements.
For SELECT fix, the tagName value is all caps as per https://developer.mozilla.org/en-US/docs/Web/API/Element/tagName.
For RADIO and CHECKBOX fix, there can be multiple elements in a group, hence they need to have a common group name.

@stackpond thanks for opening this PR, i planned to go through it tonight. Just curious why did you closed it?

Hi Kevin
I was not sure if anyone would look at the PR. I have reopened the PR for
you to have a look. Sorry for the trouble :)
Regards
Sushant
On Thu, Oct 31, 2019 at 10:31 AM Kevin Chappell<EMAIL_ADDRESS>wrote:

@stackpond https://github.com/stackpond thanks for opening this PR, i
planned to go through it tonight. Just curious why did you closed it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Draggable/formeo/pull/241?email_source=notifications&email_token=AJSXJS57JJC5UM4Q35NNXE3QRIKOPA5CNFSM4JGSHKX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWC72Y#issuecomment-548155371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJSXJS7LQTMUJBIDVALJKHDQRIKOPANCNFSM4JGSHKXQ
.

Thanks, @stackpond . im pretty slow getting to PRs but usually do get to them. Thanks again 👍

great work! merging

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add setting toggle insertspace for monaco editor

Is your feature request related to a problem? Please describe.
Add setting to toggle insertspace for monaco editor
Describe the solution you'd like
slider in settings

:tada: This issue has been resolved in version 2.23.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Perf: Account Exit routine for ZeroCopy/AccountLoader is redundantly called

Intro:
I have been diving deep in to the anchor lang/proc macro internals to optimise for another stack space related feature, during that i found a redundancy related to the calling of AccountExit exit method at the end of the instruction handler.
Problem:
Zero Copy Accounts are casted via bytemuck and as such no serialization framework is used, the only time anything that is written explicitly is the discriminator by the anchor lang framework, but the issue is this needs to be done once, the account exit impl of Account Loader : https://docs.rs/anchor-lang/latest/src/anchor_lang/accounts/account_loader.rs.html#236-248, writes the discriminator /overwrite exisitng discriminator everytime its called
Potential Solution :
Generate the account exit  or call the accountloader exit impl  when constraint #account(zero)] is called otherwise in side the parent derive account exit impl dont call the account loader exit function, this will help save on compute units.

Thanks for creating this issue. Yes, this has been a known issue for a while and should be fixed.
Happy to review PRs if you'd like to work on this.

Thanks for creating this issue. Yes, this has been a known issue for a while and should be fixed.
Happy to review PRs if you'd like to work on this.

Hey thanks for confirming the issue, happy to send in a pr addressing this and the stack space issue soo.

Happy to review PR if need be

Happy to review PR if need be

Alright will cook it up soon.


windows command specifically pwd

@domluna
this section in the readme.md

If you're on Windows:
docker run -it --rm -p 8888:8888 -v ${pwd}:/src udacity/carnd-term1-starer-kit

Actually I think the {pwd} is windows 10 specific.  It's docker for windows.  Windows <10 is docker toolbox, which has a bash terminal afaik
so that command should only be for win 10.  The other one for other versions...

So `pwd` works on all Windows except 10?

I think so, you should double check.  it's my understanding that windows for docker runs in cmd, which doens't have bash commands so you need {}  but the other windows get docker toolbox, which come with a bash, that accepts the pwd

https://carnd-udacity.atlassian.net/wiki/questions/18451525/answers/18454088 Looks like this guy used the backticks. He's on Windows 8.1.


prettier compat

We'd live to try this out and include it in our workflow. However, we are currently using prettier and would prefer to stick with that for now. Could we have a configuration with prettier compact?

There is the noStyle that will stop neostandard from caring about coding style and as such should behave well with eg prettier
I'm not a big user of prettier myself but would love for the combination to work well, can you elaborate on the addition you want? So that I'm sure I understand it 🙂

There's nothing to add to ensure neostandard works with prettier. It's just a matter of properly setting up the two:

neostandard style: run prettier first then eslint
prettier style: run eslint first then prettier

Eslint configuration should be able to replicate that behavior by ordering neostandard and eslint prettier plugin configuration properly.

There's nothing to add to ensure neostandard works with prettier

I’m interested to hear people’s thoughts and ideas on it nonetheless :)

If its the addition of eslint-config-prettier that you are asking about @ronag then the noStyle option is even better: It ensures no style rules gets added in the first place, so there's nothing for eslint-config-prettier to disable :)
This was extra easy now thanks to both ESLint itself and TypeScript-ESLint having deprecated their style rules and moved them to @stylistic/eslint-plugin, and setting noStyle: true disables the inclusion of @stylistic/eslint-plugin entirely

There's nothing to add to ensure neostandard works with prettier

I’m interested to hear people’s thoughts and ideas on it nonetheless :)

It's still an ESLint configuration issue, not an issue related to neostandard behavior. As I said in another issue: proposing a document compiling neostandard configuration with commonly used eslint plugins will address that kind of questions.

It's still an ESLint configuration issue, not an issue related to neostandard behavior.

For most scenarios users should not have to care about the specifics of ESLint, sadly one still needs to since #33 is not done

It's still an ESLint configuration issue, not an issue related to neostandard behavior.

For most scenarios users should not have to care about the specifics of ESLint, sadly one still needs to since #33 is not done

Since it's a coding style project coming after existing ones and requiring major code lint/format tooling upgrade, all real world migrations to it are currently requiring users to do ESLint configuration, with plumbing most of the time because of project specificity.
In the meantime, offering a kind of FAQ regarding neostandard configuration from GitHub issues will help migration to neostandard in most case.

Closing as the main issue question has been answered


API: Hazard Information and Hazard Hunt - Create Update and Delete Admin Role Check

Dependent on issue #19
Serves mobile application read-only lists of hazards as well as directives on what to do in case of the hazard(ie. earthquake).
Serves (tbd) admin app to allow for maintenance of hazard information (crud).
Function names, signatures, object names, and number of functions are not set in stone:
GetHazardInformationList() returns HazardInformation[]
GetHazardInformation(HazardInformationId) returns HazardInformation
CreateHazardInformation(Name, Description, Directive, Photo, Icon) returns HazardInformation
UpdateHazardInformation(HazardInformation) returns HazardInformation
DeleteHazardInformation(HazardInformationId) returns bool
Once complete, please document the final API/Classes in the Wiki

Create, Update, and Delete endpoints need to have the admin check - check out the BaseKitsApi as an example

These endpoints do have the admin check already.


Unable to destructure TypedArrays

TypeScript Version:  2.6.2
Code
const [ foo, bar ] = new Float64Array([42, -42])

Expected behavior:
foo and bar are destructured correctly
All JS engine with support for TypedArrays and destructuring handles this code without any problem
Actual behavior:
Error: error TS2461: Type 'Float64Array' is not an array type.

We could support this for non-rest destructuring; but the current ... emit uses slice which is not present on TypedArrays. @rbuckton thoughts?

Array.prototype.slice.call works on typed arrays, so we could change the helper.

On TS version 3.5.1 this will cause an error:
"Type 'Float64Array' is not an array type or a string type. Use compiler option '--downlevelIteration' to allow iterating of iterators.ts(2569)"
Same error will also produced from this code:
          var arr= new Float32Array(Float32Array.BYTES_PER_ELEMENT*5)            arr[2]=1;             var max= Math.max(...arr)
Expected output:
1
actual output:
Type 'Float32Array' is not an array type or a string type. Use compiler option '--downlevelIteration' to allow iterating of iterators.ts(2569)
Now adding

"downlevelIteration":true
into tsconfig.json will make this work, but it will increase complexity, as code the same code after compiled is:
var __read = (this && this.__read) || function (o, n) {     var m = typeof Symbol === "function" && o[Symbol.iterator];     if (!m) return o;     var i = m.call(o), r, ar = [], e;     try {         while ((n === void 0 || n-- > 0) && !(r = i.next()).done) ar.push(r.value);     }     catch (error) { e = { error: error }; }     finally {         try {             if (r && !r.done && (m = i["return"])) m.call(i);         }         finally { if (e) throw e.error; }     }     return ar; }; var __spread = (this && this.__spread) || function () {     for (var ar = [], i = 0; i < arguments.length; i++) ar = ar.concat(__read(arguments[i]));     return ar; }; var max = Math.max.apply(Math, __spread(arr));

TypedArrays are used for large density mathematical operations where a high performance is needed, so using that kind of compiled code really kills the benefits of using TypedArray.


Document Method for Rancher Users to Migrate from AWS In-Tree to Out-of-Tree Cloud Provider

SURE-6512

UI working on parts of this in these tickets:

ability to deploy AWS out-of-tree (external) provider: https://github.com/rancher/dashboard/issues/9110
removing in-tree if k8s 1.27+ in use: https://github.com/rancher/dashboard/issues/9204

For UI feature completeness, can we get a placeholder page URL ASAP? @btat who's the best person to provide that?

cc @nwmac

@martyav , Can you please take care of this in the absence of @btat this week?

@gaktive do you just need a URL or do you also need a live page for the user to click thru to? We can use https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/migrate-from-in-tree-to-out-of-tree-aws for now.
https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/migrate-from-in-tree-to-out-of-tree already exists as a published page, but it's vSphere specific (for now).

@martyav either is fine so the placeholder gives us something to work with. fyi @mantis-toboggan-md


[#5380] Update hydroshare repository mount to read-only

Resolves #5380

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]

http://ci.hydroshare.org:8080/job/hydroshare-pull-requests/configure
#docker exec hydroshare ./run-tests-jenkins

python -m pip install -U watchdog
watchmedo log --verbose --ignore-directories --ignore-pattern="watchdog.out" . >> watchdog.out 2>&1 &
docker exec hydroshare ./run-tests-jenkins
echo "~~~~WATCHDOG~~~~"
cat watchdog.out


fix: python3.7 eof

The minimum supported Python version will be 3.8 - Python3.7 is end of life and will no longer receive patches
Dependencies require >=

Tests are E2E against the Lacework API.  Will create a task to address these problems.


⚠ Mobitopup has degraded performance

In 1f55e19, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 27926 ms

Resolved: Mobitopup performance has improved in da036e2 after 417 days, 2 hours, 45 minutes.


When I toggle Between typing component it is not working

`class Home extends React.Component {
state = {
value: true
};
handleClick = () => {
console.log("value");
this.setState({
value: !this.state.value
});
};
render() {
return (

{this.state.value ? (

Eka where you can manage your expense

) : (

Eka is best solution for Your firm

)}

);
}
}
export default Home;
` When I am toggling second one does not show animation effect
Here is codesandbox link
https://codesandbox.io/s/kmqqy72n87

Why it is not showing typing component i don't know, Just check the codesandbox

Hey @karanshrm44, I'm going to close this because I'm not sure what the problem is. If you want to explain the problem in more detail and submit instructions on how to reproduce it, I will re-open the issue.


⚠ Spryr has degraded performance

In 7dd96db, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4116 ms

Resolved: Spryr performance has improved in 15f92b2 after 10 minutes.


Translate to HINDI

Hey,
I would like to take up the task to translate it to hindi.

Ok! You can open a PR, following the instructions in the translations.md file and the pattern established by our translators. Thank you!

Closing as it’s in progress 🙏


Add more requested folder icons.

Relates to #650
Changes proposed:

[x] Add

List of added folder icons:

client
include
plugin
private
public
server
tools

Also changed the coloring of the background folder of the script folder icon to improve visibility in light themes.

@robertoguertasm Feel free to push your icons on the branch.

I've modified the following icons to make the icons more visible:

Vagrant
Docker
Tools
Server
Public
Private
Plugin
Include

Great work @JimiC. If you feel that you don't like any of the changed files please let me know.

@robertohuertasm Whatever you are fine with, I'm OK.

Changed the tools and lib icons to flat ones.