Aqara motion sensor не работает

дано: raspbian lite, homebridge, sprut stick, sensor (http://joxi.ru/xAeBg6jTp89yzr)
добавление проходит, но сенсор не появляется в ХБ и ХК. При срабатывании сенсор в логе ХБ пишет
[ZigBee] Received message from unknown device: 0x00158d0002006d6a
притом что розетка сяоми залетела без проблем, работает, управляется.
zigbee.db:
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d0002006d6a","nwkAddr":64637,"manufId":4151,"epList":[1],"status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":263,"inClusterList":[0,1,3,1024,1030,1280,65535],"outClusterList":[0,25],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{}},"genPowerCfg":{"dir":{"value":1},"attrs":{}},"genIdentify":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}},"msIlluminanceMeasurement":{"dir":{"value":1},"attrs":{}},"msOccupancySensing":{"dir":{"value":1},"attrs":{}},"ssIasZone":{"dir":{"value":1},"attrs":{}},"manuSpecificCluster":{"dir":{"value":1},"attrs":{}}}}},"_id":"4WWSpeMKXJkl734q"} {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0012013e66","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1541807570,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"2":{"profId":257,"epId":2,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"3":{"profId":261,"epId":3,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"4":{"profId":263,"epId":4,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"5":{"profId":264,"epId":5,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"6":{"profId":265,"epId":6,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}}},"_id":"91uwy8C01VLH8Cab"} {"id":3,"type":"Router","ieeeAddr":"0x00158d0002328c4f","nwkAddr":11921,"manufId":4447,"manufName":"LUMI","powerSource":"Mains (single phase)","modelId":"lumi.plug","epList":[1,2,3,100],"status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,1,2,3,4,5,6,10,16],"outClusterList":[10,25],"clusters":{"genBasic":{"dir":{"value":1},"attrs":{"zclVersion":1,"appVersion":22,"stackVersion":2,"hwVersion":18,"manufacturerName":"LUMI","modelId":"lumi.plug","dateCode":"02-28-2017","powerSource":1}},"genPowerCfg":{"dir":{"value":1},"attrs":{"mainsVoltage":2244,"mainsAlarmMask":0}},"genDeviceTempCfg":{"dir":{"value":1},"attrs":{"currentTemperature":29,"lowTempThres":55,"highTempThres":60}},"genIdentify":{"dir":{"value":1},"attrs":{"identifyTime":0}},"genGroups":{"dir":{"value":1},"attrs":{"nameSupport":0}},"genScenes":{"dir":{"value":1},"attrs":{"count":0,"currentScene":0,"currentGroup":0,"sceneValid":0,"nameSupport":0,"lastCfgBy":"0xffffffffffffffff"}},"genOnOff":{"dir":{"value":1},"attrs":{"onOff":0}},"genTime":{"dir":{"value":3},"attrs":{}},"genBinaryOutput":{"dir":{"value":1},"attrs":{"activeText":"","inactiveText":"","outOfService":0,"presentValue":0,"statusFlags":0}},"genOta":{"dir":{"value":2},"attrs":{}}}},"2":{"profId":260,"epId":2,"devId":9,"inClusterList":[12],"outClusterList":[4,12],"clusters":{"genGroups":{"dir":{"value":2},"attrs":{}},"genAnalogInput":{"dir":{"value":3},"attrs":{"261":0,"262":0,"maxPresentValue":0,"outOfService":0,"presentValue":0,"statusFlags":0,"applicationType":589824}}}},"3":{"profId":260,"epId":3,"devId":83,"inClusterList":[12],"outClusterList":[12],"clusters":{"genAnalogInput":{"dir":{"value":3},"attrs":{"261":0,"262":0,"maxPresentValue":0,"outOfService":0,"presentValue":0.000027561110982787795,"statusFlags":0,"applicationType":720896}}}},"100":{"profId":260,"epId":100,"devId":263,"inClusterList":[15],"outClusterList":[4,15],"clusters":{"genGroups":{"dir":{"value":2},"attrs":{}},"genBinaryInput":{"dir":{"value":3},"attrs":{}}}}},"_id":"h7H34C7YHKRy4r7V"} {"$$indexCreated":{"fieldName":"id","unique":true,"sparse":false}} {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0012013e66","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1541807702,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"2":{"profId":257,"epId":2,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"3":{"profId":261,"epId":3,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"4":{"profId":263,"epId":4,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"5":{"profId":264,"epId":5,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"6":{"profId":265,"epId":6,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}}},"_id":"91uwy8C01VLH8Cab"} {"id":4,"type":"EndDevice","ieeeAddr":"0x00158d0002006d6a","nwkAddr":64637,"manufId":4151,"epList":[1],"status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":263,"inClusterList":[0,1,3,1024,1030,1280,65535],"outClusterList":[0,25],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{}},"genPowerCfg":{"dir":{"value":1},"attrs":{}},"genIdentify":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}},"msIlluminanceMeasurement":{"dir":{"value":1},"attrs":{}},"msOccupancySensing":{"dir":{"value":1},"attrs":{}},"ssIasZone":{"dir":{"value":1},"attrs":{}},"manuSpecificCluster":{"dir":{"value":1},"attrs":{}}}}},"_id":"4WWSpeMKXJkl734q"} {"id":3,"type":"Router","ieeeAddr":"0x00158d0002328c4f","nwkAddr":11921,"manufId":4447,"manufName":"LUMI","powerSource":"Mains (single phase)","modelId":"lumi.plug","epList":[1,2,3,100],"status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,1,2,3,4,5,6,10,16],"outClusterList":[10,25],"clusters":{"genBasic":{"dir":{"value":1},"attrs":{"zclVersion":1,"appVersion":22,"stackVersion":2,"hwVersion":18,"manufacturerName":"LUMI","modelId":"lumi.plug","dateCode":"02-28-2017","powerSource":1}},"genPowerCfg":{"dir":{"value":1},"attrs":{"mainsVoltage":2244,"mainsAlarmMask":0}},"genDeviceTempCfg":{"dir":{"value":1},"attrs":{"currentTemperature":29,"lowTempThres":55,"highTempThres":60}},"genIdentify":{"dir":{"value":1},"attrs":{"identifyTime":0}},"genGroups":{"dir":{"value":1},"attrs":{"nameSupport":0}},"genScenes":{"dir":{"value":1},"attrs":{"count":0,"currentScene":0,"currentGroup":0,"sceneValid":0,"nameSupport":0,"lastCfgBy":"0xffffffffffffffff"}},"genOnOff":{"dir":{"value":1},"attrs":{"onOff":0}},"genTime":{"dir":{"value":3},"attrs":{}},"genBinaryOutput":{"dir":{"value":1},"attrs":{"activeText":"","inactiveText":"","outOfService":0,"presentValue":0,"statusFlags":0}},"genOta":{"dir":{"value":2},"attrs":{}}}},"2":{"profId":260,"epId":2,"devId":9,"inClusterList":[12],"outClusterList":[4,12],"clusters":{"genGroups":{"dir":{"value":2},"attrs":{}},"genAnalogInput":{"dir":{"value":3},"attrs":{"261":0,"262":0,"maxPresentValue":0,"outOfService":0,"presentValue":0,"statusFlags":0,"applicationType":589824}}}},"3":{"profId":260,"epId":3,"devId":83,"inClusterList":[12],"outClusterList":[12],"clusters":{"genAnalogInput":{"dir":{"value":3},"attrs":{"261":0,"262":0,"maxPresentValue":0,"outOfService":0,"presentValue":0.000027561110982787795,"statusFlags":0,"applicationType":720896}}}},"100":{"profId":260,"epId":100,"devId":263,"inClusterList":[15],"outClusterList":[4,15],"clusters":{"genGroups":{"dir":{"value":2},"attrs":{}},"genBinaryInput":{"dir":{"value":3},"attrs":{}}}}},"_id":"h7H34C7YHKRy4r7V"}
Лог установки:
[2018-11-10 02:15:23] [ZigBee] [PermitJoinAccessory] time left: 108 spinlock: false [] [2018-11-10 02:15:24] [ZigBee] [PermitJoinAccessory] time left: 107 [2018-11-10 02:15:39] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:39] [ZigBee] [PermitJoinAccessory] time left: 92 [2018-11-10 02:15:40] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 1 of 8 [2018-11-10 02:15:40] [ZigBee] [PermitJoinAccessory] time left: 91 [2018-11-10 02:15:40] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:40] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:40] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 2 of 8 [2018-11-10 02:15:41] [ZigBee] [PermitJoinAccessory] time left: 90 [2018-11-10 02:15:42] [ZigBee] [PermitJoinAccessory] time left: 89 [2018-11-10 02:15:43] [ZigBee] [PermitJoinAccessory] time left: 88 [2018-11-10 02:15:44] [ZigBee] [PermitJoinAccessory] time left: 87 [2018-11-10 02:15:45] [ZigBee] [PermitJoinAccessory] time left: 86 [2018-11-10 02:15:46] [ZigBee] [PermitJoinAccessory] time left: 85 [2018-11-10 02:15:46] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 3 of 8 [2018-11-10 02:15:47] [ZigBee] [PermitJoinAccessory] time left: 84 [2018-11-10 02:15:48] [ZigBee] [PermitJoinAccessory] time left: 83 [2018-11-10 02:15:49] [ZigBee] [PermitJoinAccessory] time left: 82 [2018-11-10 02:15:50] [ZigBee] [PermitJoinAccessory] time left: 81 [2018-11-10 02:15:51] [ZigBee] [PermitJoinAccessory] time left: 80 [2018-11-10 02:15:52] [ZigBee] [PermitJoinAccessory] time left: 79 [2018-11-10 02:15:52] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:52] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:53] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 4 of 8 [2018-11-10 02:15:53] [ZigBee] [PermitJoinAccessory] time left: 78 [2018-11-10 02:15:54] [ZigBee] [PermitJoinAccessory] time left: 77 [2018-11-10 02:15:55] [ZigBee] [PermitJoinAccessory] time left: 76 [2018-11-10 02:15:56] [ZigBee] [PermitJoinAccessory] time left: 75 [2018-11-10 02:15:57] [ZigBee] [PermitJoinAccessory] time left: 74 [2018-11-10 02:15:58] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:58] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:15:58] [ZigBee] [PermitJoinAccessory] time left: 73 [2018-11-10 02:15:59] [ZigBee] [PermitJoinAccessory] time left: 72 [2018-11-10 02:16:00] [ZigBee] [PermitJoinAccessory] time left: 71 [2018-11-10 02:16:01] [ZigBee] [PermitJoinAccessory] time left: 70 [2018-11-10 02:16:02] [ZigBee] [PermitJoinAccessory] time left: 69 [2018-11-10 02:16:03] [ZigBee] [PermitJoinAccessory] time left: 68 [2018-11-10 02:16:04] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 5 of 8 [2018-11-10 02:16:04] [ZigBee] [PermitJoinAccessory] time left: 67 [2018-11-10 02:16:05] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:05] [ZigBee] [PermitJoinAccessory] time left: 66 [2018-11-10 02:16:06] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 6 of 8 [2018-11-10 02:16:06] [ZigBee] [PermitJoinAccessory] time left: 65 [2018-11-10 02:16:07] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:07] [ZigBee] [PermitJoinAccessory] time left: 64 [2018-11-10 02:16:08] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 7 of 8 [2018-11-10 02:16:08] [ZigBee] [PermitJoinAccessory] time left: 63 [2018-11-10 02:16:09] [ZigBee] [PermitJoinAccessory] time left: 62 [2018-11-10 02:16:09] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:10] [ZigBee] [PermitJoinAccessory] time left: 61 [2018-11-10 02:16:10] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 8 of 8 [2018-11-10 02:16:10] [ZigBee] Device announced incoming and is added, id: 0x00158d0002006d6a [2018-11-10 02:16:12] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:12] [ZigBee] Unrecognized device: 0x00158d0002006d6a undefined undefined [2018-11-10 02:16:14] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:15] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:15] [ZigBee] Received message from unknown device: 0x00158d0002006d6a [2018-11-10 02:16:21] [ZigBee] Received message from unknown device: 0x00158d0002006d6a

Hi @daspru, it looks like your device didn't provide information about mode and manufacturer, or the plugin didn't read this information properly, so you caught such error. I recommend you to try to add this device again, but don't forget to wake up device every 2-3 seconds by pressing on reset button. Also I can recommend you reboot your device (inject and insert battery).

Hi @qavk, it seems like you are doing something wrong, maybe you forgot to wake up your device during pairing? Please read recommendations in previous comment and try again.

Hi @qavk, it seems like you are doing something wrong, maybe you forgot to wake up your device during pairing? Please read recommendations in previous comment and try again.

Да, забыл про это, спасибо)
Но на этом проблемы не закончились: появилась проблема, как у человека выше..
Сделал, как вы и посоветовали: вытащил батарейку, попробовал привязать заново, получилось раза с третьего после вытаскивания батарейки (устройство привязывалось, но не определялось). Пока пытался подключить датчик движения малинка дважды уходил в ребут, один из них - в бесконечный. Причины падения неизвестны, образ полностью ваш, только к wifi подключился.
До этого подключил розетку, датчик температуры и влажности и кубик - никаких проблем не возникло. Ниже приложу логи. Как я понял из них, стик не мог подключиться к малине и переподключался, а про датчик движения - просто выдавало ошибку, что устройство не определено.
Расписал поподробнее, может, вам и кому-то еще будет полезно)
`[11/12/2018, 1:23:44 PM] Homebridge is running on port 51826.
[11/12/2018, 1:37:16 PM] [ZigBee] Retrying connect to hardware
[11/12/2018, 1:37:21 PM] [Config] Authentication Disabled
[11/12/2018, 1:37:21 PM] [Config] Console v3.8.11 is listening on port 80.
[11/12/2018, 1:37:23 PM] [ZigBee] Retrying connect to hardware
[11/12/2018, 1:37:30 PM] [ZigBee] Retrying connect to hardware
[11/12/2018, 1:37:37 PM] [ZigBee] Retrying connect to hardware
[11/12/2018, 1:37:44 PM] [ZigBee] error: Error: request timeout
at CcZnp. (/home/pi/.npm-global/lib/node_modules/homebridge-zigbee/node_modules/cc-znp/lib/ccznp.js:255:22)
at Object.onceWrapper (events.js:273:13)
at CcZnp.emit (events.js:182:13)
at Timeout. (/home/pi/.npm-global/lib/node_modules/homebridge-zigbee/node_modules/cc-znp/lib/ccznp.js:234:18)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
[11/12/2018, 1:37:44 PM] [ZigBee] Retrying connect to hardware
[11/12/2018, 1:37:50 PM] [ZigBee] ZigBee platform initialized, info:
[11/12/2018, 1:37:50 PM] [ZigBee] ------------------------------------
[11/12/2018, 1:37:50 PM] [ZigBee] channel: 11
[11/12/2018, 1:37:50 PM] [ZigBee] pan id: 0x0dc6
[11/12/2018, 1:37:50 PM] [ZigBee] extended pan id: 0xdddddddddddddddd
[11/12/2018, 1:37:50 PM] [ZigBee] ieee address: 0x00124b0012023301
[11/12/2018, 1:37:50 PM] [ZigBee] nwk address: 0
[11/12/2018, 1:37:50 PM] [ZigBee] firmware version: 2.6.3
[11/12/2018, 1:37:50 PM] [ZigBee] firmware revision:<PHONE_NUMBER>
[11/12/2018, 1:37:50 PM] [ZigBee] ------------------------------------
[11/12/2018, 1:37:51 PM] [ZigBee] Registered device: 0x00158d00028f6faa LUMI lumi.sensor_cube
[11/12/2018, 1:37:51 PM] [ZigBee] Registered device: 0x00158d0002454b6b LUMI lumi.sens
[11/12/2018, 1:37:51 PM] [ZigBee] Registered device: 0x00158d0002468dd3 LUMI lumi.plug
[11/12/2018, 1:37:51 PM] [ZigBee] Unrecognized device: 0x00158d000223c4e6 undefined undefined
[11/12/2018, 1:21:36 PM] [ZigBee] Received message from unknown device: 0x00158d000223c4e6`


Addresses SAM issue 1224

goes with https://github.com/NREL/wex/pull/175

An example from: https://hub.alfresco.com/t5/alfresco-content-services-blog/tldr-the-lgpl-license-explained/ba-p/314998

A good way to do that is to add a short text in the readme and in the file headers, something like: "Please notice that this ‘foo’ program is a modified version of program ‘bar’ version x.x.x", with links and details to the original version. It must be easy for the end users to understand.

I didn't see a readme in lpsolve - is it just V5?

The changes themselves look good, but we need some additional changes to be compliant with nlopt and lpsolve's licenses. Specifically the bolded line below:

You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application.  Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)

Can you add painfully obvious comments to the top of each file and the README describing the changes?

Changes added in

The changes themselves look good, but we need some additional changes to be compliant with nlopt and lpsolve's licenses. Specifically the bolded line below:

You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application.  Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)

Can you add painfully obvious comments to the top of each file and the README describing the changes?

Header for each file added in https://github.com/NREL/ssc/commit/76d6c00db9125ca4dce352e57e755032e569918f
Readme added with header message for both nlopt and lpsolve

An example from: https://hub.alfresco.com/t5/alfresco-content-services-blog/tldr-the-lgpl-license-explained/ba-p/314998

A good way to do that is to add a short text in the readme and in the file headers, something like: "Please notice that this ‘foo’ program is a modified version of program ‘bar’ version x.x.x", with links and details to the original version. It must be easy for the end users to understand.

I didn't see a readme in lpsolve - is it just V5?
We may need to include a longer history of changes with this using the commit history https://github.com/NREL/ssc/commits/patch/lpsolve

Thanks for noting the licensing issues.
Addressed in https://github.com/NREL/ssc/commit/76d6c00db9125ca4dce352e57e755032e569918f
Review requested.


Automatic Replica Discovery Behavior When Region Is Down

https://learn.microsoft.com/en-us/azure/azure-app-configuration/howto-geo-replication?tabs=dotnet#automatic-replica-discovery
If my application is pointing to a single Azure App config resource in South Central US and it has replicas across many regions, if the entire South Central US region is down, is the "Automatic replica discovery" going to be down as well since the Azure App config connection string I have is to the regional service in South Central US?
Or is there some sort of global load balancer that the connection string is pointing to instead that will still be alive during a region outage?

The replica discovery is built based on the DNS, so no, it won't be impacted if a region is down.


Add compile x- attributes

This pr adds a compiler for dynamic attribtues for tags that are not starting with <x-:
Usage:

Will be compiled to:

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


stuff just wont work (Building issue)

Describe your bug here.
i have everything in the read me installed including all of the base funkin stuff.
Command Prompt/Terminal logs (if existing)
Windows

C:\a - Copy>lime build windows
source/Achievements.hx:132: characters 30-54 : Warning : `FlxCamera.defaultCameras` is deprecated, use `FlxG.cameras.setDefaultDrawTarget` instead

For HTML5 i get this error

C:\a - Copy>lime build html5
source/FunkinLua.hx:3104: characters 23-28 : Type not found : State
source/CoolUtil.hx:18: lines 18-141 : ... Defined in this class
source/PlayState.hx:3760: characters 40-68 : Class<FunkinLua> has no field getPropertyLoopThingWhatever
source/PlayState.hx:4903: characters 8-12 : FunkinLua has no field call
source/PlayState.hx:4904: characters 8-12 : FunkinLua has no field stop

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Just the Name of the applaction in the project.xml file

there's no error in the windows log
pretty sure html5 was fixed, it works fine for me


Run acceptance tests on bionic stemcell

Fixes #60

auditd and harden_sshd jobs fail on bionic, looking further into the issue:
Running Suite: OsConfAcceptanceTests Suite
Random Seed:<PHONE_NUMBER>
Will run 16 of 17 specs
Task 19 | 16:46:02 | Preparing deployment: Preparing deployment (00:00:01)
Task 19 | 16:46:03 | Preparing deployment: Rendering templates (00:00:00)
Task 19 | 16:46:03 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 19 | 16:46:03 | Creating missing vms: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (00:01:36)
Task 19 | 16:47:39 | Updating instance os-conf: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:40 | L executing pre-stop: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:40 | L executing drain: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:41 | L stopping jobs: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:42 | L executing post-stop: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:43 | L installing packages: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:45 | L configuring jobs: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary)
Task 19 | 16:47:45 | L executing pre-start: os-conf/e2623a0a-cf06-4623-b2cb-f645b3cbf7fd (0) (canary) (00:00:08)
L Error: Action Failed get_task: Task 5168a77a-9506-411a-409b-1eb8bd637d91 result: 2 of 14 pre-start scripts failed. Failed Jobs: auditd, harden_sshd. Successful Jobs: pre-start-script, login_banner, sysctl, modprobe, monit, limits_not_recommended, ntpdate, tcp_keepalive, limits, resolv, user_add, ca_certs.
Task 19 | 16:47:48 | Error: Action Failed get_task: Task 5168a77a-9506-411a-409b-1eb8bd637d91 result: 2 of 14 pre-start scripts failed. Failed Jobs: auditd, harden_sshd. Successful Jobs: pre-start-script, login_banner, sysctl, modprobe, monit, limits_not_recommended, ntpdate, tcp_keepalive, limits, resolv, user_add, ca_certs.
Updating deployment:
Expected task '19' to succeed but state is 'error'
Exit code 1
Failure [107.006 seconds]

Thanks @yatzek!


fix lambda erorring on buckets that have no grants whatsoever

Fixed edge case in which lambda errors out when a user creates a bucket that nobody, not even themselves, has permissions to.
TypeError: Cannot read property 'length' of undefined
at publicPermissions (/var/task/publicBucketACL/function.js:20:29)
at module.exports.fn (/var/task/publicBucketACL/function.js:7:23)

Added test, thanks for the review! How's it look now?


How would I load multiple reducers in app.module?

How would I load multiple reducers in app.module?
   providers: [
        StoreModule.provideStore({authorization, goals, currentGoal, user, currentPurchase, settings, navInterrupts}),
        {
            ....
        },

Each has his own reducer, too. (named the same)

You can pass an object to the provideStoremethod that looks like this:
let rootReducer = {
    authorization: authorizationReducer,
    goals: goalsReducer,
   currentGoal: currentGoalReducer,
   ...
}

Internally, NGRX/store will call the combineReducers method to create a meta-reducer which calls the reducers with the correct state slice.

Thanks for this extraordinary fast reply, @KwintenP !
I am doing now:

    providers: [
        StoreModule.provideStore({authorization: authorization}),

but get:

What version of store are you using, isn't it outdated by any chance?
{authorization: authorization}

is literally the same as
{authorization}

in typescript, so that's probably not the problem.

+1
Problem was I put it into providers key in ngModule and not imports, this is working now:
imports: [
        IonicModule.forRoot(MyApp),
        HttpModule,
        TranslateModule.forRoot({
            provide: TranslateLoader,
            useFactory: (http: Http) => new TranslateStaticLoader(http, "../../www/assets/i18n", ".json"),
            deps: [Http]
        }),
        StoreModule.provideStore(rootReducer)
],

I moved my provideStore code to a separate file.
import {ModuleWithProviders}  from '@angular/core';
import {StoreModule} from '@ngrx/store';
import {authStateReducer} from "./states/auth-state/auth-state.reducer";
import {navStateReducer} from "./states/nav-state/nav-state.reducer";

const appReducers: any = {
    authState: authStateReducer,
    navState: navStateReducer
};

const appInitialState: any = {

};

export const StateStore: ModuleWithProviders = StoreModule.provideStore(appReducers, appInitialState);

Then imported StateStore in app.module.ts.
I got the idea from how Angular 2 has their routing set up. All the routing code is in its own file, then you export the end result and use that inside app.module.ts.

Ok, thanks for this. I am trying it now. Could you explain what is inside initial state? And could you please show how you use this in app.module ?

Looks to me like initial state is just the initial shape of the entire state, i.e. {} or [], etc. At least that is what worked for me (designating an initial state of {}). Spent all day today tracking this down. Would love to see it added to the README!

Well, it almost worked. Does each child store need to use its own reducer function? I have multiple models that need to be in separate child stores so their ids don't overwrite each other, but they all have the same reducer functionality.

Okay, in app.module.ts, I've got:
imports: [
...
  StoreModule.provideStore({
    Book: apiReducer,
    Author: apiReducer,
  }, {
    Book: {},
    Author: {},
  }),
...
]

and apiReducer.ts looks like this:
export const addOrUpdate = 'ADD_OR_UPDATE';
export const destroy = 'DESTROY';

export const apiReducer: ActionReducer<any> =
(state: {} = {}, action: Action) => {
  switch (action.type) {
    case addOrUpdate:
      return Object.assign({}, state, action.payload);

    case destroy:
      let newState = Object.assign({}, state);
      delete newState[action.payload.id];
      return newState;

    default:
      return state;
  }
};

And in a component, I do this:
  ...
  constructor (private store: Store<{}>) {
    this.store.dispatch({
      type: addOrUpdate,
      payload: {
        21: {
          id: 21,
          title: 'The Hobbit',
          author: 19,
        },
        34: {
          id: 34,
          title: 'The Fellowship of the Ring',
          author: 19,
        },
      }
    });

    this.store.select('Author').subscribe(authorStore => {
      console.log(authorStore);
    });
  }
  ...

I'm not surprised that authorStore is just the whole store--which contains the two book objects previously dispatched. I've search all the intros and examples and I cannot find any examples that show registering multiple reducer stores, much less how to dispatch to the correct store. @robwormald, @MikeRyan52, @btroncone: What am I missing?

Got it! It's the action types that are used to match up stores/reducers, right? Sorry about the conversation with myself. I hope it benefits others, because like I said this is not readily apparent in the intro docs or examples. Although it's been kind of a pain to figure all the pieces out that I need, I think I'm going to love reactive redux with angular2. Thank you!

Seems like this has been resolved. Please reopen and leave a comment if it is not.


NIFI-5916 Added an option to enable empty flowfiles to be sent if the…

…re are no results from a query.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[ ] Is your initial contribution a single, squashed commit?

For code changes:

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

For documentation related changes:

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

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

Lookin pretty good, left one comment, also please rebase while incorporating any changes, thanks!

@mattyb149 we're ready to merge.

+1 LGTM, ran unit and integration tests, and tested with a live NiFi instance, both with and without incoming flow files and with "output empty" set to both true and false. Thanks for the improvement! Merging to master

Hello,
This behavior (NIFI-5916) was not extended to FetchGridFS. Is it possible to add it?
Thanks.

@Damien60 yes, please feel free to write up a Jira case to add this feature to FetchGridFS


Doesnt work for me

I did everything you told me, but it just comes up with a 1 host and it's not even me, there's 6 other people on the wifi please help me with this

plz help me with dis

it also asks me for the gateway ip which i do then i enter the mac address but it says 1 hosts are up.


Proposal: Strong-typed queries

This is going to sound a bit crazy, but hear me out. There are currently a number of issues with this proposal, but it exists solely for the sake of demonstration. We can probably get around the limitations.
I have been experimenting with making the query function strong-typed, so that queries are validated at compile-time.
Features

Validates that type names are correct in the query.
Validates that the projection contains valid property names.
Validates the criteria section (where), including.

Checking for valid property names.
Checking for valid operators for particular types.

string only allows:

= and is.
!= and is_not.
in and not_in.
like and not_like.

number only allows:

= and is.
!= and is_not.
in and not_in.
>, after and greater_than.
<, before and less_than.
>= and <=.

boolean only allows:

= and is.
!= and is_not.
in and not_in.

object only allows:

has.
any.

Checking for valid where values.

If the property name does not exist, it gives a compile error.
If for instance the property name being queried is a string, it must be wrapped in quotes.
If the property name being queried is a number, it must be numeric.

Current limitations
If you like where this is headed, I am willing to invest in trying to resolve these limitations. So please don't see them as direct show-stoppers. Let's have a discussion about it.

I'd like this to work with infer, so that instead of writing strongTypedQuery<Foo>('select fooProperty1 from Foo'), it can just be inferred from strongTypedQuery('select fooProperty1 from Foo'), since Foo is already a valid type name. This would be awesome, and would automatically add types for all queries, especially in combination with the type generator project.
Right now, has and any is not being validated. Can easily add this.
Right now, the Whitespace string literal only accepts a single whitespace. So an arbitrary amount of whitespaces between for instance the property names is not allowed. This could be a problem with multiline etc. And adding more might impact the type checking performance.
and and or is not supported in the where clause. This is easy to add, but only with a specific maximum amount of potential properties being selected (due to TypeScript not supporting recursive string literal types). There may be ways to work around this.
The projection part can only contain one property. This is easy to fix, but only with a specific maximum amount of potential properties being selected (due to TypeScript not supporting recursive string literal types). There may be ways to work around this.
Right now, date types are not supported, but again very easy to add and even validate.

The code
Here's the code. Notice the strongTypedQuery function. That's where the magic happens. For every call to that, I've commented particular cases that the strong-typings catch.
type Foo = {
    fooProperty1: string,
    fooProperty2: number,
    fooProperty3: boolean
}

type Bar = {
    barProperty1: string,
    barProperty2: number,
    barProperty3: boolean
}

interface EntityTypeMap {
    Foo: Foo,
    Bar: Bar
}

type EntityTypes = EntityTypeMap[keyof EntityTypeMap];

type EntityTypeProperty<TEntityType extends EntityTypes, TPropertyType> = {
    [K in keyof TEntityType]: TEntityType[K] extends symbol ?
        never :
        TEntityType[K] extends TPropertyType ?
            K :
            never
}[keyof TEntityType];

type EntityType<TEntityType extends EntityTypes> = keyof EntityTypeMap;

type Whitespace = ` `;

type OptionalWhitespace = Whitespace | "";

type Projections<TEntityType extends EntityTypes, TPropertyType> =
    `${EntityTypeProperty<TEntityType, TPropertyType>}`;

type ProjectionPrefix<TEntityType extends EntityTypes> =
    `select${Whitespace}${Projections<TEntityType>}${Whitespace}from${Whitespace}` |
    "";

type CriteriaOperator<T> =
    T extends string ?
        (
            `${'='|'is'}` |
            `${'!='|'is_not'}` |
            `${'in'}` |
            `${'not_in'}` |
            `${'like'}` |
            `${'not_like'}`
        ) :
        T extends number ?
            (
                `${'='|'is'}` |
                `${'!='|'is_not'}` |
                `${'in'}` |
                `${'not_in'}` |
                `${'>'|'after'|'greater_than'}` |
                `${'<'|'before'|'less_than'}` |
                `${'>='}` |
                `${'<='}`
            ) :
            T extends boolean ?
                (
                    `${'='|'is'}` |
                    `${'!='|'is_not'}` |
                    `${'in'}` |
                    `${'not_in'}`
                ) :
                T extends Object ?
                    (
                        `${'has'}` |
                        `${'any'}`
                    ) :
                    never;

type CriteriaValue<T> =
    T extends number ?
        `${number}` :
        T extends boolean ?
            `${boolean}` :
            T extends string ?
                `'${string}'` :
                never;

type CriteriaAndValue<TEntityType, TPropertyType> =
    `${EntityTypeProperty<TEntityType, TPropertyType>}${Whitespace}${CriteriaOperator<TPropertyType>}${Whitespace}${CriteriaValue<TPropertyType>}`

type Criteria<TEntityType extends EntityTypes> = {
    [K in keyof TEntityType]:
        `${CriteriaAndValue<TEntityType, TEntityType[K]>}`
}[keyof TEntityType];

type CriteriaSuffix<TEntityType extends EntityTypes> =
    `${Whitespace}where${Whitespace}${Criteria<TEntityType>}` |
    ``;

type Query<TEntityType extends EntityTypes> =
    `${ProjectionPrefix<TEntityType>}${EntityType<TEntityType>}${CriteriaSuffix<TEntityType>}`

function strongTypedQuery<TEntityType extends EntityTypes>(query: Query<TEntityType>) {
    return null!;
}

//valid, because "Foo" is a known type.
strongTypedQuery<Foo>("Foo");

//gives compile error, because "Blah" is not a valid type.
strongTypedQuery<Blah>("Blah");

//valid, because fooProperty1 exists on Foo
strongTypedQuery<Foo>("select fooProperty1 from Foo");

//gives compile error, because fooProperty1 does not exist on bar.
strongTypedQuery<Bar>("select fooProperty1 from Bar");

//valid, because fooProperty1 exists on Foo, and fooProperty1 is of type string.
strongTypedQuery<Foo>("Foo where fooProperty1 = 'abc'");

//gives compile error, because fooProperty1 is of type string, not number, so the value has to be wrapped in quotes.
strongTypedQuery<Foo>("Foo where fooProperty1 = 2388");

//gives compile error, because fooProperty1 is of type string, not boolean.
strongTypedQuery<Foo>("Foo where fooProperty1 = true");

//valid, because fooProperty2 is a number.
strongTypedQuery<Foo>("Foo where fooProperty2 = 24");

//gives compile error, because fooProperty2 is a number, not a string, so the value can't be wrapped in quotes.
strongTypedQuery<Foo>("Foo where fooProperty2 = 'abc'");

//gives compile error, because fooProperty2 is a number, not a boolean.
strongTypedQuery<Foo>("Foo where fooProperty2 = true");

//valid, because fooProperty3 is of type boolean.
strongTypedQuery<Foo>("Foo where fooProperty3 = false");

//gives compile error, because fooProperty3 is a boolean, so quotes are not allowed.
strongTypedQuery<Foo>("Foo where fooProperty3 = 'abc'");

//gives compile error, because fooProperty3 is a boolean, so numbers are not allowed.
strongTypedQuery<Foo>("Foo where fooProperty3 = 28");

//valid, because fooProperty1 exists on Foo, and fooProperty1 is of type string.
strongTypedQuery<Foo>("Foo where fooProperty1 = 'abc'");

//gives compile error, because fooProperty1 is a string, so the "<=" operator is not allowed.
strongTypedQuery<Foo>("Foo where fooProperty1 <= 'abc'");

//gives compile error, because fooProperty1 is a string, so the "has" operator is not allowed.
strongTypedQuery<Foo>("Foo where fooProperty1 <= 'abc'");

//long query syntax can also be used.
strongTypedQuery<Foo>("select fooProperty1 from Foo where fooProperty1 = 'abc'");

Playground link
Play around with it here. Right now it gives an error in line 90, but it doesn't seem to be a valid error. I think it actually might be a bug in TypeScript.

This is super cool and absolutely crazy. I love it. I've spent the hour reading and processing it.
Could you elaborate more on what the goal for this is and what use cases you see?
I think some of the errors of the playground link might come from mixups between the keyof EntityTypeMap (That you call EntityTypes) and the EntityTypeMap[keyof EntityTypeMap] (That you call EntityTypes). In the type generator, we call them EntityType and EntityData to make them easier to distinguish from each other.

I also had some concerns and did some quick experiments in the same vein to flesh out my thinking.
First of all I don't think TypeScript is designed for this kind of string parsing and has a high risk of leading to some of the issues you highlight in the limitations section. Specifically, I think that there is a high risk for performance problems and the brittleness might be a big issue.
Handling non-primitive types will also present issues. Mainly when using nested selects (Child.GrandChild), but there might be other issues as well.
The return values of the queries won't be more strongly typed than before. We will only validate that it's not an invalid query, but we still won't know if the API has the information to return or if the property will return empty.
A final problem is that the logic needed to get this to work will be too complicated which causes issues both with maintaining and also, for hypothetical future users, tracking back and parsing why they get the dreaded red squigglies will require really good code comments and would probably still take some effort.
All in all, I really like the idea and attempt but I have a hard time seeing that the practical applications (Unless I'm failing to imagine big practical uses) will be worth investing the time and effort that would be required to finalize this.

Thank you for chiming in.
I agree with your assessment. It makes a lot of sense, and makes me think the same.
The reason I'd be interested in this is due to us often changing our schema. We'd like to potentially catch errors in that regard that might happen at runtime.
But I think e2e tests are better suited for that at second glance.
Oh well, it was fun to experiment with! 😁

In individual projects, besides e2e tests, it could be a good idea to look into something like Zod or lizod for runtime validation of the results. It validates and strongly types the resulting data.

Thank you.
What about a builder pattern approach?
Something like:
session.query(q => q
    .from(f => f.Foo)
    .withProjections(
        p => p.fooProperty1,
        p => p.fooProperty2,
        p => p.fooProperty3
    )
    .withCriteria(c => c
        .and(
            a => a
                .property(p => p.fooProperty1)
                .is("hello world"),
            a => a
                .property(p => p.fooProperty2)
                .lessThan(42),
            a => a
                .property(p => p.fooProperty2)
                .notIn([56, 57])
        )
    )
    .build()
)

We could strong-type it, and even retain backwards compatibility by checking if the query is typeof "function".
You may be thinking "but wait, property names of non-classes (interfaces, types) are not available at runtime". But that's actually fixable:
https://www.npmjs.com/package/@fluffy-spoon/name-of
This package (under the hood) uses EcmaScript (and Node's) Proxy object (see more here to infer names of types not available at runtime. Perfectly safe and stable.
Full code is here (look at how simple it is:
function getPropertyNameInternal<T = unknown>(expression: (instance: T) => any, options: {
    isDeep: boolean
}) {
    let propertyThatWasAccessed = "";
    var proxy: any = new Proxy({} as any, {
        get: function(_: any, prop: any) {
            if(options.isDeep) {
                if(propertyThatWasAccessed)
                    propertyThatWasAccessed += ".";

                propertyThatWasAccessed += prop;
            } else {
                propertyThatWasAccessed = prop;
            }
            return proxy;
        }
    });
    expression(proxy);

    return propertyThatWasAccessed;
}

export function getPropertyName<T = unknown>(expression: (instance: T) => any) {
    return getPropertyNameInternal(expression, {
        isDeep: false
    });
}

export function getDeepPropertyName<T = unknown>(expression: (instance: T) => any) {
    return getPropertyNameInternal(expression, {
        isDeep: true
    });
}

And here's usage example:
import { getPropertyName, getDeepPropertyName } from '@fluffy-spoon/name-of';

interface SomeType {
  foo: boolean;

  someNestedObject: {
      bar: string;
  }
}

console.log(getPropertyName<SomeType>(x => x.foo)); //prints "foo"
console.log(getPropertyName<SomeType>(x => x.someNestedObject)); //prints "someNestedObject"
console.log(getPropertyName<SomeType>(x => x.someNestedObject.bar)); //prints "bar"

console.log(getDeepPropertyName<SomeType>(x => x.foo)); //prints "foo"
console.log(getDeepPropertyName<SomeType>(x => x.someNestedObject)); //prints "someNestedObject"
console.log(getDeepPropertyName<SomeType>(x => x.someNestedObject.bar)); //prints "someNestedObject.bar"

It could also help alleviate #137 and therefore be an alternative to #139.

I tried making this in the playground. In my opinion, it works quite well.
Here is the link.

as @gismya mentioned in the PR, this is cool but not within the scope of the api client

Yeah. Good call on cleaning it up.


[Wait for other PR] [MQTT] replace glib queue

Replace g-async-queue to internal queue in MQTT functions.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #75. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


DefaultPromise reduce thread local access cleanup

Motivation:
b3c56d5f694b281f986916cbe623be1cba258c11 introduced code which unconditionally writes to a thread local twice where it may not be necessary to write to a thread local at all. If there are no delayed promise objects queued then we don't need to change the thread local tracking the stack depth.
Modifications:

Check if the delayed promises queue is empty before setting the stack depth thread local

Result:
If no delayed promises are queued we don't have to touch the stack depth thread local.

This will be obsolete after StackOverFlowError protection code is simplified in DefaultPromise.


BigQuery table labels not retrieved from getTable

"Labels" field has been added in the issue #2865 but no Field selector "Labels" is defined in the TableField enum.
So, there is no way to retrieve the labels of a table.
Environment details

cloud java version : 0.49.0

Thanks for bringing this to our attention! #3879 should have resolved this, please reopen if you still have any issues


Decoding image from Base 64 string and passing it to the matting server

Hi,
In my use case, in the inference.py file I am supposed to receive image in base 64 string which I have to decode and pass it to the matting server. Could you please tell me how do I pass the decoded base 64 image to the matting server since it is different from reading image from its path. Thank you

You can use base64 library of python to convert numpy matrix of image into
base64. Also, you will have to add the shape of the matrix also while
passing so that you can get to the same shape of image by reshaping the
decoded vector.
On Wed, 25 Aug, 2021, 2:58 pm Mohsin Mushtaq, @.***>
wrote:

Hi,
In my use case, in the inference.py file I am supposed to receive image
in base 64 string which I have to decode and pass it to the matting server.
Could you please tell me how do I pass the decoded base 64 image to the
matting server since it is different from reading image from its path.
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/harsh2912/Background-removal/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENHXFZNMFGLXT5RBF5VYETT6SZTRANCNFSM5CYUQG2Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Quickfix for elements sharing the same memory address

This PR attempts to fix a memory issue, which resulted in errors like this: https://github.com/Unstructured-IO/unstructured/issues/2931
The root cause seems to be in how ListItems are being combined, not in how hashes or parent IDs are updated.
When assign_and_map_hash_ids() is called and elements (or elements' metadata) do not have unique memory addresses, then updating the parent_id of one element will also overwrite the parent_id of some other element.

I checked out to your branch and verified this does not raise the KeyError, but can you add a test? I suppose it could be a follow-up PR. Approving in advance

https://github.com/Unstructured-IO/unstructured/actions/runs/8850164463/job/24304063524
=========================== short test summary info ============================
FAILED test_unstructured/partition/pdf_image/test_pdf.py::test_partition_pdf_word_bbox_not_char - assert 18 == 17
 +  where 18 = len([<unstructured.documents.elements.Header object at 0x7ff8e4d241d0>, <unstructured.documents.elements.Header object at ...NarrativeText object at 0x7ff8e4d0eb10>, <unstructured.documents.elements.NarrativeText object at 0x7ff8f8a89ad0>, ...])
= 1 failed, 2231 passed, 13 skipped, 2 deselected, 2 xfailed, 9 xpassed, 8 warnings in 1170.99s (0:19:30) =

. either this test was incorrect before, or the def _combine_list_elements change broke something.
let's make this a real release (not -dev) when tests pass.

Amazing. Thank you for the quick turnaround on this fix @micmarty-deepsense @cragwolfe! 🙇 🙏
I can confirm that unstructured 0.13.5 fixes the issue in #2931.


Corrupted umlaut symbols

Instead of characters like "Ü", a question mark "?" is displayed for TextButton, Label etc.

Is your development machine running Windows or OS X?  The compiler relies on the Java code page.  I think you may have to set (or export) JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8
If you are using an IDE, you may have to convince the IDE to start up with those options.

In my case it is Windows and Visual Studio Code with has by default "files.encoding": "utf8"

Royale uses a different compiler than Apache Flex and calls third-party JS optimization code.  It is great that Visual Studio Code is configured to output UTF-8, but if VSCode isn't a Java process and/or is forking a process to run the compiler, the compiler may not be running in a JRE configured for UTF-8.  AIUI, the JAVA_TOOL_OPTIONS sets the configuration for the JRE.

C:\>set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8

restart VSC, run project, still lost chars.
It should be dash in "UTF-8" ?
C:\>set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8

restart VSC, run project, still lost chars.
In Terminal output there is one and UTF-8 related error:

com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: ERROR - Cannot read file C:/dev/royale-projects/royale-test/bin/js-debug/HelloFlexJS.js: Failed to read: C:\dev\royale-projects\royale-test\bin\js-debug\HelloFlexJS.js, is this input UTF-8 encoded?
com.google.javascript.jscomp.LoggerErrorManager printSummary
WARNING: 1 error(s), 0 warning(s)
The project 'HelloFlexJS' has been successfully compiled and optimized.
4.472022255 seconds
Terminal will be reused by tasks, press any key to close it.

NOTE: Probably related issue.

As I understand google closure is used, and "is this input UTF-8 encoded?" string is found here in SourceFile.java
Maybe that can help in fixing this issue.

Tried copy first line from Terminal and running it from command line:
C:\dev\royale-projects\royale-test>C:\ProgramData\Oracle\Java\javapath\java.exe -Dfile.encoding=UTF-8 -jar .......
but no help. Noticed there is no "is this input UTF-8 encoded?" error when runned from cmd.
Files build but still no UTF-8 chars. After manually checking files encoding noticed:
js-debug/index.html is UTF-8, but
js-debug/HelloFlexJS.js is ANSI encoded.

If you used the JAVA_TOOL_OPTIONS environment variable, then when running from the command line, you should see console output that says: "Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8"
If you are seeing that and the output is still ANSI then attach your source file and I will try it on my Windows computer.

It works ok when JAVA_TOOL_OPTIONS is set, and run from command line.

But how to set it for VSC? Anyway shouldn't this be fixed somehow within tooling, and not to request all users to set this environment variable in order to use UTF-8 which is world wide common standard?

Are you building some example or just created tests APP ?

I'm wondering if in Moonshine it will work, because we are just using CMD to launch things.

@piotrzarzycki21 I am using code posted above. I just tried to test it in Moonshine but can't set SDK..

@aharui Thanks for info and help. IMHO to avoid current and future encoding problems (been there many times) UTF-8 should be used 'everywhere'.

@neminovno what folder of downloaded SDK are you pointing ? You should point royale-asjs.
I just tested it in Moonshine and all components displays good text with JAVA_TOOL_OPTIONS set.

@piotrzarzycki21 I have set SDK, run it, and same as in VSC, UTF-8 chars are lost, so it looks JAVA_TOOL_OPTIONS must be set.

It looks like released version Moonshine 1.10.0 do not pickup for some reason JAVA_TOOL_OPTIONS, but upcoming version 1.11.0 is working fine. At least what is happened on my machine.

We will release 1.11.0 probably this week.

Thanks, I use Flash Builder 4.7 as IDE and I added "JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8" to the environment variables and umlauts now displayed correctly.

As test shows, this is fixed in latest VSCode. No need to set JAVA_TOOL_OPTIONS.

It looks like we have a solution. I'm closing that one.


Tweaks on relogin screen

Left-aligns user dropdown on desktop and mobile
Brings new input to password field on mobile (@MarcoPolo has to check on Android)
Better "Create an account" button and placement
blueGrey background

cc @adamjspooner

Looks good to me on Android!


PPOTrainer ignores limit_val_batches when running validation

There's an inconsistency between PPOTrainer and SFT and DPO trainers causing PPOTrainer to always test just a single (same) validation batch on every run, while ignoring the rest of the validation set. The goal originally was to have validation track the same set of held out samples throughout training, thus resetting the validation iterator on every validation run.
Expected behavior is to allow the user to control the size of the validation set to use for testing. One possible solution is to have the validation dataloader return mbs*dp size and have the user control how many he'd like to use for validation with the limit_val_batches as done with other trainers.

Duplicate of #27?

Yep. Missed it.
Sorry, closing.


feat(api): add deploy hooks

closes #1153.

There doesn't seem to be any way to authenticate the hooks, is that going to be a future feature?

From the trello ticket which I'm working from:

Operators should be able to configure webhooks URLS that would receive release events from Workflow. Let's start cluster-wide to start, rather than per-application.

There were no requirements to authenticate the hooks. Can you describe in more detail how that would be sussed out? As it stands right now these hooks are injected by the administrator through the chart so it's generally accepted to be trusted URLs, but if there's a way to add that sorta functionality I can quickly hack it up in here.

As a server that's receiving the webhook, it's important to be able to verify that the hook actually came from deis. Otherwise $EVIL_USER could send a fake post request to your server and mimic a deis deployment.
One method is using a secret to create a HMAC digest of body, like github.
Another method is signing the web hooks with a private key, then verify it using the public key, which can be retrieved from the controller, like travis-ci does.

Current coverage is 87.55% (diff: 69.56%)

Merging #1168 into master will decrease coverage by 0.17%

@@             master      #1168   diff @@
==========================================
  Files            42         42
  Lines          3716       3729    +13
  Methods           0          0
  Messages          0          0
  Branches        646        648     +2
==========================================
+ Hits           3260       3265     +5
- Misses          299        307     +8
  Partials        157        157

Powered by Codecov. Last update 3b6d094...458a426

I think I'll do the dumb approach of a secret passphrase shared by both the controller and the deploy hook. Thanks for the feedback, @Joshua-Anderson :)

done, now just need to update the documentation to and write a blog post to demonstrate the HMAC-SHA1 signing process.

Also realized I should handle the use case when one of the deploy hook URLs are not responding correctly

That use case is now being handled as of 47cabd8.

@vdice mentioned to me it might be better to roll the secret key into a secret rather than an envvar. I'll fix that right up!


In wellness.html module the imgbx class images path is not working so…

In wellness.html module the imgbx class img tag path is not working so , I have modified and fixed the issue you can pull it.

okay great! Thank you for your contribution


We may miss "disconnected" event on socket

When connection is established, connection object is returned back to DeltaManager. During this transition time, nobody listens on "disconnected" event, make it possible to miss it.
Add proper handling for such cases, as well as validation that if connection object it not disposed, socket itself should be connected.
We had someone similar behavior earlier for "error" handler, but it was not fully correct. Extending it to "disconnect" event and fixing issues.

@vikagrawal - FYI, this PR was picked up by Gary in 5pm run. One of the asserts you mentioned was caused by it, so I've added commit to address it.

Ping.
Needs server changes (https://github.com/microsoft/FluidFramework/pull/7006), as we fake socket and do not fully implement it.


[WiP] Welcome screen

fixes #453

TODOs / questions :

find out if we want to change the font for the <SimpleButton> element across the whole application or create a different button element for this particular case in the meantime.
where do we store the hideWelcomeBanner variable? Do we write to the store or do we attempt to use the config.json file mentioned by @pdelboca ?
Personal observation: The text next to the checkbox that says "Do not show this on next lauch" is very small / difficult o read.
How to manage the links?
My screen is not very big, with the current size of the banner, the banner has a vertical scroll in my screen, is this ok, has this been taken into account?

@guergana the hideWelcomeBanner variable needs to be persisted accross sessions so we need to store it somewhere in the disk.
Currently we are using a config.json file to store the value of the OpenAI Api Token so it makes sense to reuse it for this variable as well. This file is currently being stored in ~/.opendataeditor/config.json.
If you check the logic on how do we store the OpenAI API Key you should be able to extend it to store the value of this variable as well.
Does it make sense?

@guergana on How to manage the links?
I would say the expected behaviour is for it to open the link in the user's default web browser.

Closing this PR in favour of https://github.com/okfn/opendataeditor/pull/481 which works the zustand store.


table font_size is not applied for a| cells

Theme file snippet:
base:
  font_size: 12

table:
  border_color: a0a0a0
  border_width: $base_border_width
  font_size: 8.5

Asciidoctor snippet:
...
| `ORIGIN`
| `VARCHAR(100)`
| Source system code. `ice#dp_contact_official#denied_entity`

| `SOURCE_ID`
| `VARCHAR(200)`
| Identifier of the denied entity in the list of given type.

| `TYPE`
| `INT`
a|
Type of the entity:

- `1` -- Individual Person
- `2` -- Legal entity
- `3` -- Other
...

How it looks like:

I believe that font size specified for table should be applied to all cells.

Got it. Let us hope we will resolve it sometime in the future.

@mojavelinux: just replied to your remark in #852: making this a scale (%) in the yaml (for both adoc and non-adoc table content) would be great.

It took me a bit to figure out that this was the cause of my inability to format a table cells.
Is there a workaround? I'm trying to figure out if there's a way to add some specificity to the cells so that I can apply a small font_size to the a cells.

@mojavelinux Can you point me to the relevant code where the sub-document rendering is triggered? I'd like to try my hand at adding this feature.

Hi @DaneWeber,
Did you have the opportunity to look at this yet?
Maybe we can come up with a 'simple solution' (affecting only text-size...). Would be wonderful. Not Ruby-savvy here, but if I can help, I'd love to.

Are there any news or solutions for this issue?
I understand the difficulties that could arise when using sections, etc. inside the cell so maybe inheriting the font size could be optional via a separate setting in the theme. This would make it work at least when just simple formatting like lists or images are used.
Also the proposed scale factor would be fine.
It somehow works when using the docbook/FOP toolchain but I don't know to which extend.

If we ignore the style overrides from elements in the cell, this is rather easy to implement. I have submitted a proposal that merely inherits the font properties from the table (like other cells). See https://github.com/asciidoctor/asciidoctor-pdf/pull/1678

It somehow works when using the docbook/FOP toolchain but I don't know to which extend.

This is not a helpful statement since that's a completely different technology. You're comparing apples to oranges.

Thx, will test it as soon as it lands into master.

I think I can implement a very crude font scaling for elements that define their own font size. They would be scaled by the ratio of the table font size to the base font size. It may miss some cases, but we can deal with those.
Since this change is rather significant, I think we may need to consider a global setting to disable this behavior.

They would be scaled by the ratio of the table font size to the base font size. It may miss some cases, but we can deal with those.

Sounds good!

I think I can implement a very crude font scaling for elements that define their own font size. They would be scaled by the ratio of the table font size to the base font size. It may miss some cases, but we can deal with those.

This sounds good, thank you!

It somehow works when using the docbook/FOP toolchain but I don't know to which extend.

This is not a helpful statement since that's a completely different technology. You're comparing apples to oranges.

Yes, but maybe they should produce a rather similar output when using similar style/template settings and using the same asciidoc source. There are other features which work well with Asciidoctor-PDF but do not seem to work with docbook/FOP (e.g. column headers).

I'm glad you like the idea.

maybe they should produce a rather similar output when using similar style/template settings and using the same asciidoc source.

Aside from the AsciiDoc source, there's nothing similar about these technologies. They have completely different ways of working and of styling. You could say that you're able to do something with FOP and you'd like to be able to do it with Asciidoctor PDF. And that's useful. But just because it works in FOP doesn't mean it does or can work here in this converter.

Let's say that by default the font properties inherit from table (which also means the font of nested blocks will be scaled). To disable this behavior, you can set table_asciidoc_cell_style: initial in the theme. In this case, initial means to reset the styling back to what it would be initially, ignoring the table cell styles. In other words, initial means "don't inherit".

I think this PR is ready to go.

Thx, looks good for me
The only "issue" is that literal cells are not affected:

I will just stop using literal cells and for me issue is closed, thank you again!

You're right that literal cells are something entirely different. They take on the size of the code block, not the table cell (though it might be reasonable to consider scaling that font size too).

Thank you!

If you'd like to file that follow-up issue for literal table cells, go ahead.


[cherry-pick] pick improvements and bugfix to release-2.0 branch for release-2.0.2

Compile is failed.


Experimenting with Python 3

@russel with these patches I can run python3 bootstrap.py to completion. Running the tests is still a disaster but that is mainly because of byte vs string inconsistencies or generated python code not being compatible with python 3.
624 tests fail (out of 1181?) and 155 return no result.
There are still some items that seem to think they don't work on python3 (they have the standard scons header).

@timj This is sounding exciting :-)  The obvious question: do all the tests pass with this when run on Python 2.7.x  I am not sure what the minimum x is but I am sure it will be 8 or 9. Since we do not have CI support for PRs here, I will take a clone of your repository and run a few checks.

@timj It only just struck me that we are here on GitHub using Git, the SCons mainline repository is a Mercurial one, should we be ensuring there is a path back to a mercurial repository to create the pull request for final merging into the mainline?

@timj  It just struck me that I don't use bootstrap.py. I cannot remember what the argument/discussion was but to execute SCons directly from a repository (which is my standard set up) I use an alias:
alias scons='/usr/bin/python /home/users/russel/Repositories/Mercurial/SCons/src/script/scons.py'

I tried running this branch on python 2.7.11 and got a whole mass of errors such as:
Traceback (most recent call last):
  File "test/Climb/option-u.py", line 36, in <module>
    test = TestSCons.TestSCons()
  File "/home/users/russel/Repositories/Git/SCons_TimJ/QMTest/TestSCons.py", line 269, in __init__
    import SCons.Node.FS
  File "/home/users/russel/Repositories/Git/SCons_TimJ/src/engine/SCons/Node/__init__.py", line 345, in <module>
    class NodeInfoBase(object):
TypeError: Error when calling the metaclass bases
    __weakref__ slot disallowed: either we already got one, or __itemsize__ != 0

Right. My main focus was working out exactly what is involved in python 3 support. I've been ignoring python2 in this experiment but of course we need it to work with both. Metaclasses are one of the things that changed quite a lot between versions.

Thanks for doing this.
Too bad SCons is such a fan of opening files in binary mode. Luckly the % operator was added back to bytestrings.
Python Future has a great metaclass helper. http://python-future.org/what_else.html#metaclasses Where does SCons use them?

It seems that most of the python3 tests are failing do to str vs bytes issues. Can this be solved by not opening files in binary mode or does that cause other issues?

I have been pondering that. Ironically I think it's not helping that Scons has tried to fully support unicode in Python 2. Strings are the main porting headache. I am making some progress on getting this working with python 2 again but I'm having to enable unicode literals and a lot of the tests use repr and aren't expecting a u to turn up.
One problem I am finding is that python 2 literal strings (Without unicode literals enabled) do not play well with future str because that str is trying to use unicode semantics so isinstance("abc", str) returns false.
My current problem is that:
% python3 runtest.py src/engine/SCons/BuilderTests.py

passes all tests but:
% python2 runtest.py src/engine/SCons/BuilderTests.py
======================================================================
ERROR: test_emitter_TARGET_SOURCE (__main__.BuilderTestCase)
Test use of $TARGET and $SOURCE in emitter results
----------------------------------------------------------------------
Traceback (most recent call last):
  File "src/engine/SCons/BuilderTests.py", line 1343, in test_emitter_TARGET_SOURCE
    targets = builder(env, target = 'TTT', source ='SSS')
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Builder.py", line 633, in __call__
    return self._execute(env, target, source, OverrideWarner(kw), ekw)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Builder.py", line 554, in _execute
    tlist, slist = self._create_nodes(env, target, source)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Builder.py", line 532, in _create_nodes
    target=orig_tlist, source=orig_slist)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Environment.py", line 487, in arg2nodes
    v = node_factory(self.subst(v, **kw))
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Environment.py", line 518, in subst
    return SCons.Subst.scons_subst(string, self, raw, target, source, gvars, lvars, conv)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Subst.py", line 564, in scons_subst
    result = ss.substitute(strSubst, lvars)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Subst.py", line 528, in substitute
    result.append(self.conv(self.expand(a, lvars)))
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Util.py", line 459, in to_String_for_subst
    return str(s)
  File "/Users/timj/work/lsstsw/miniconda/lib/python2.7/site-packages/future/types/newstr.py", line 102, in __new__
    return super(newstr, cls).__new__(cls, value)
  File "/Users/timj/work/lsstsw/miniconda/lib/python2.7/site-packages/future/types/newobject.py", line 78, in __unicode__
    s = type(self).__str__(self)
  File "/Users/timj/work/lsst/scons/src/engine/SCons/Subst.py", line 258, in __str__
    return str(nl[0])
  File "/Users/timj/work/lsstsw/miniconda/lib/python2.7/site-packages/future/types/newstr.py", line 102, in __new__
    return super(newstr, cls).__new__(cls, value)
  File "/Users/timj/work/lsstsw/miniconda/lib/python2.7/site-packages/future/types/newobject.py", line 78, in __unicode__
    s = type(self).__str__(self)
TypeError: 'Delegate' object is not callable

Is that with github up-to-date or newer commits on your end? About 680 python3 tests fail for me mostly due to str vs bytes issues in QMTest/TestCmd.py when calling the match functions though there are some other issues.

I reread your message and it makes more sense now. I had the same issue with Future str in SCons.Util.is_string.

I have a couple of un-pushed patches. I'll push them in a bit.


[main] [RHPAM-4129] - Kogito Operator scorecard errors (#1155)

[RHPAM-4129] - Kogito Operator scorecard errors
Cherry-picks https://github.com/kiegroup/kogito-operator/pull/1155

Incorporate review comments

Co-authored-by: Vaibhav<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've ran make before-pr and everything is working accordingly
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

How to retest this PR or trigger a specific build:

Run operator BDD testing
Please add comment: /jenkins test

Run RHPAM operator BDD testing
Please add comment: /jenkins RHPAM test

/jenkins test

/jenkins RHPAM test

RHPAM PR job #34 was: FAILURE
Possible explanation: Pipeline failure or project build failure
You can find test error logs here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/rhpam-kogito-operator-PR-check-new/34//artifact/test/logs/error/
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/rhpam-kogito-operator-PR-check-new/34/display/redirect or see console log:

Console Logs
2022-03-18 20:38:52,758 cli.py:346        ERROR Image build failed, see logs above.Traceback (most recent call last):  File "/usr/local/lib/python3.6/site-packages/cekit/builders/podman.py", line 55, in run    subprocess.check_call(cmd)  File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call    raise CalledProcessError(retcode, cmd)subprocess.CalledProcessError: Command '['/usr/bin/podman', 'build', '--squash', '-t', 'rhpam-7/rhpam-kogito-operator:7.11.0', '-t', 'rhpam-7/rhpam-kogito-operator:latest', 'target/image']' returned non-zero exit status 125.During handling of the above exception, another exception occurred:Traceback (most recent call last):  File "/usr/local/lib/python3.6/site-packages/cekit/cli.py", line 339, in run    command.execute()  File "/usr/local/lib/python3.6/site-packages/cekit/builder.py", line 67, in execute    self.run()  File "/usr/local/lib/python3.6/site-packages/cekit/builders/podman.py", line 59, in run    raise CekitError("Image build failed, see logs above.")cekit.errors.CekitError: Image build failed, see logs above.make: *** [Makefile.rhpam:37: container-build] Error 1[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Push Operator Image(s) to Openshift Registry)Stage "Push Operator Image(s) to Openshift Registry" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Run BDD tests)Stage "Run BDD tests" skipped due to earlier failure(s)[Pipeline] stage[Pipeline] { (Running smoke tests)Stage "Run BDD tests" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] }[Pipeline] // script[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/rhpam-kogito-operator-PR-check-new/34/api/json[Pipeline] readJSON[Pipeline] sh

PR job #597 was: FAILURE
Possible explanation: Pipeline failure or project build failure
You can find test error logs here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/597//artifact/test/logs/error/
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/597/display/redirect or see console log:

Console Logs
    raise CalledProcessError(retcode, cmd)subprocess.CalledProcessError: Command '['/usr/bin/podman', 'build', '--squash', '-t', 'operator-runtime:1.0.0', '-t', 'operator-runtime:latest', 'target/image']' returned non-zero exit status 125.During handling of the above exception, another exception occurred:Traceback (most recent call last):  File "/usr/local/lib/python3.6/site-packages/cekit/cli.py", line 339, in run    command.execute()  File "/usr/local/lib/python3.6/site-packages/cekit/builder.py", line 67, in execute    self.run()  File "/usr/local/lib/python3.6/site-packages/cekit/builders/podman.py", line 59, in run    raise CekitError("Image build failed, see logs above.")cekit.errors.CekitError: Image build failed, see logs above.make: *** [Makefile:160: profiling-build] Error 1[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build Kogito CLI)Stage "Build Kogito CLI" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Push Operator Image(s) to Openshift Registry)Stage "Push Operator Image(s) to Openshift Registry" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Run BDD tests)Stage "Run BDD tests" skipped due to earlier failure(s)[Pipeline] stage[Pipeline] { (Running smoke tests)Stage "Run BDD tests" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] }[Pipeline] // script[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/597/api/json[Pipeline] readJSON[Pipeline] sh

I probably did something wrong, will revisit this on Monday.

/jenkins test

/jenkins test

yey, green
@vaibhavjainwiz @radtriste can you please take a look?

/approve


Local video

could you help me?
How to use a local video?
something like that:
            <video: VideoPlayer.Source>
                <video: ResourceVideoSource>
                    <video: ResourceVideoSource.Path>
                        <OnPlatform
                            x: TypeArguments = "x: String"
                            iOS = "Videos / video.mp4"
                            Android = "video.mp4">
                        </ OnPlatform>
                    </video:ResourceVideoSource.Path>
                </ video: ResourceVideoSource>
            </video:VideoPlayer.Source>

This is how I do it …
In c# ….
Video_Background.Source = VideoSource.FromResource(
"MobileApp.Images.video.video_sutf_intro.mp4",
typeof(OwnProfilePage).GetTypeInfo().Assembly);
with the variable set in XAML:
<video:VideoPlayer
x:Name="Video_Background"
AutoPlay="True"
DisplayControls="False"
Repeat="True"
BackgroundColor="Black"
AbsoluteLayout.LayoutBounds="0, 0, 1, 1"
AbsoluteLayout.LayoutFlags="All"
Margin="0"
IsVisible="False"/>

Thanks, I will try it

It works on iOS if you set the relative path of the video file, but not on Android. Currently the only way to play local files with a single codebase is to add your videos as embedded resources on your shared project and set the source as something like the following:
VideoPlayer.Source = VideoSource.FromResource("Videos.particles.mp4");


[Feature Request]: Is it possible to design a function in which agents can call each other?

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
No response
Describe the feature you'd like
Is it possible to design a function in which agents can call each other?
For example, I add another agent that I have designed to the flow diagram of an already designed agent
Describe implementation you've considered
No response
Documentation, adoption, use case
No response
Additional information
No response

+1. i also need this.


chore: add wdio detection test

@christian-bromann merging this with a note in the readme about running the wdio test: updated also the entry about wdio detection, will be detected only when using the browser runner.


Remove code_ref tags

These were from a custom jekyll plugin that is no longer in use.
Compiled documentation belongs in tut.

Interesting, travis fail on this PR due to what looks to be a bug in server-side events: https://travis-ci.org/http4s/http4s/jobs/155675655#L625

That bug is captured and fixed in #693.   This should be able to proceed.

👍


Bug Report: Issue in using policy Deny-MgmtPorts-From-Internet policy

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Policy Name: Deny-MgmtPorts-From-Internet
Policy definition - Deny-MgmtPorts-From-Internet.json

{
  "field": "Microsoft.Network/networkSecurityGroups/securityRules/destinationPortRange",
  "in": "[[parameters('ports')]"
 },

This is resulting in error The inner exception 'Evaluation result of language expression '[[parameters('ports')]' is type 'String', expected type is 'Array'.'. at policy creation.

Hey @jain-ranjith, thanks for the issue.
How did you deploy this policy? As if you copied it from this repo and didn't use one of our implementation options (portal, bicep or terraform modules) you will have some extra escaping characters present that you dont need.
If you just want the definition, use the "copy definition" button via AzAdvertizer here for this policy and it will remove the escaping characters https://www.azadvertizer.net/azpolicyadvertizer/Deny-MgmtPorts-From-Internet.html

details on the escaping is here: https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Contribution-Guide#escaping-policy-functions

Hi @jtracey93 ,
Thanks for the explanation.
I tried to "copy" the definition and used it Terraform.   My bad that I did not read the instructions.
I will close the issue :)


groups + talk: sidebar spacing fixes

Addresses some misalignments in the Talk sidebar for incoming DM requests
Addresses a misalignment in the empty Groups sidebar (first run)
Eliminates the blue [?] box for incoming multi-DM requests

Before:

After:

ty that was bothering me lol

LOL, let's ship it with 2.10.0 then. Pretty glaring


Data from Schofield lab to check

@mc-robinson - new single concentration assays form Schofield lab for you to check please. For once I cannot see anything wrong.
20200520_Schofield_single_conc_Shipment_5.xlsx
20200520_Schofield_single_conc_Shipment_4.xlsx

Looks good to me!

@mc-robinson - more Schofield data.
20200522_RapidFire_IC50_Shipment_ 4_5).xlsx

Hi @LizbeK,
Looks good. I just changed to 2 to the Canonical version of the ID because they are duplicates in the system.
20200522_RapidFire_IC50_Shipment_4_5_mcr_mapped.xlsx

@mc-robinson  - Schofield lab single point data for shipment 6 to check please.
20200526_Schofield_single_conc_shipment6.xlsx

Hi @LizbeK, this data is good to go!


Add support for linking GitHub accounts

Closes #603

:warning: The following controllers contain actions outside of the 7 resource actions (index, create, store, show, edit, update, destroy). For more details, review the docs or watch Cruddy by Design to see if you can rework these into resource controllers.

[ ] app/Http/Controllers/GitHubController.php

:x: PHP syntax errors were detected after running your Shift. Often these are simply differences between the PHP version of Shift and your project. Occasionally they are misplaced lines.
You can check the PHP syntax by running php -l on the following files:

[ ] app/Http/Controllers/GitHubController.php


Forms do not work in Dialogs

Sandbox
https://codesandbox.io/s/rmwc-typescript-sandbox-g63tq
Version of @rmwc/dialog
6.1.0
build system
Webpack (Create React App)
Description
When opening a Dialog and setting preventOutsideDismiss to true the dialog closes as soon as you hit ENTER on your keyboard when the focus is within a text field.
What happened, and what was supposed to happen
The dialog closes with a "cancel" event.
The dialog should not close. Because of the current behaviour, I can not use form submission within dialogs correctly. preventOutsideDismiss should not prevent to close the modal when clicking outside the scrim but also when submitting a form. It might be even incorrect behaviour regardless the value of preventOutsideDismiss.
Please fix this issue or you are forcing me to implement my own dialog :(
Additional note:
Submitting the form still works but I can not stop the Dialog from closing. But this is necessary if submitting returns with validation errors.

Removing the isDefaultAction from the second DialogButton seems to fix your problem:
<DialogButton action="accept">
    Sweet!
</DialogButton>

Hope this helps.

It does 🤯 How could I not see this one. Thanks for your help 👍


Emagged borgs, if emagged only once has a conflict in chassis vs. laws

Description

I was an emagged engineering borg after i changed chassis from being a roundstart borg, while a janitorial robot was also emagged after me. Both chassis's had their law-governing internals damaged when examined and my law 0 looked normal. However, when i went afk irl and came back (did NOT go SSD) they moved me into the janitorial borg. I noticed that i was not emagged, however when i checked my chassis i was still emagged. The previous person in the janitorial robot also said that they also noticed the issue of laws not showing up. Also important to note that the locking mechanism on the borg was broken (nothing showed up on right click relating to locking access).
Screenshots

Additional context

Round number #37871

@EmoGarbage404


Open Source

HI Rajasekhar..
Is this open source that I can use?
Do you know of any similar js as well which can draw north or south india horoscope charts?

Yes, it is free to use. I justed MIT license file. I am not aware of any other javascript libraries to generate north Indian style chart. If you happen to write one,  please contribute to this project.


[Bug]: create_final_documents.parquet  doesn't exist

Describe the bug
graphrag makes index successfully,  All workflows completed successfully include create_final_documents. but create_final_documents.parquet  doesn't exist , there is error in report:
21:16:45,439 graphrag.index.emit.parquet_table_emitter INFO emitting parquet table create_final_community_reports.parquet
21:16:45,443 graphrag.index.emit.parquet_table_emitter ERROR Error while emitting parquet table
Traceback (most recent call last):
File "/home/lile/graphrag/graphrag/index/emit/parquet_table_emitter.py", line 40, in emit
await self._storage.set(filename, data.to_parquet())
^^^^^^^^^^^^^^^^^
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pandas/util/decorators.py", line 333, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pandas/core/frame.py", line 3113, in to_parquet
return to_parquet(
^^^^^^^^^^^
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pandas/io/parquet.py", line 480, in to_parquet
impl.write(
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pandas/io/parquet.py", line 190, in write
table = self.api.Table.from_pandas(df, **from_pandas_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pyarrow/table.pxi", line 3874, in pyarrow.lib.Table.from_pandas
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pyarrow/pandas_compat.py", line 611, in dataframe_to_arrays
arrays = [convert_column(c, f)
^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pyarrow/pandas_compat.py", line 611, in
arrays = [convert_column(c, f)
^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pyarrow/pandas_compat.py", line 598, in convert_column
raise e
File "/home/ubuntu/mambaforge/envs/graphrag/lib/python3.11/site-packages/pyarrow/pandas_compat.py", line 592, in convert_column
result = pa.array(col, type=type, from_pandas=True, safe=safe)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pyarrow/array.pxi", line 339, in pyarrow.lib.array
File "pyarrow/array.pxi", line 85, in pyarrow.lib._ndarray_to_array
File "pyarrow/error.pxi", line 91, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: ('cannot mix struct and non-struct, non-null values', 'Conversion failed for column findings with type object')
21:16:45,451 graphrag.index.reporting.file_workflow_callbacks INFO Error emitting table details=None
Steps to reproduce
No response
Expected Behavior
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

Could you please tell me how was it solved?


Update vault to 3.1.0

Updates org.typelevel:vault from 3.0.4 to 3.1.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.0.4).
You might want to review and update them manually.
ember-server/js/yarn.lock
website/jvm/src/hugo/content/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "vault" } ]

labels: library-update, semver-minor, old-version-remains

This is included in #5152.  Assuming we get that finished, we won't need this.


Add support for parquet_writer_version session property

Allow the Presto session property parquet_writer_version, which is currently ignored by Velox, to toggle the parquet writer datapage version (V1 or V2). The value can be set as a session property or can be provided in the Hive config. Defaults to V2.

@yingsu00 @majetideepak Thank you for reviewing - made all necessary changes, please take a look!


Introduce our own TreeT monad

This PR completely removes WeightedList in favor of our own TreeT. This data type has been engineering to completely fit our purposes:

at each node we keep track of the state, so we can see how it changes,
when we branch we can attach a tag, so we can later see how it's used (for example, in symbolic evaluation we tag what is the constructor we use).

I've rebased this PR on top of the latest changes in dev, so it merges cleanly.

On my end, the O'Hearn Peano test successfully terminates in 60-75 seconds (I ran it a few times). So it seems the tree is making the test take much longer, but it looks like it is terminating at least.

I just noticed the existence of the gr/unstate branch from @0xd34df00d. How does the work in these two branches relate? It's good to communicate to make sure we're not overlapping work.

Great stuff @lucaspena, thank you! Besides having empirical evidence that the treet branch is doing additional work, it reinforces the idea that currently, in dev we are returning the first counterexample we find and looking no further! (#97)

The work of #137 will supersede this; this PR is stale and we decided not to move forward with it.


example: react-apollo-crm updates

@elitan I merged main and refactored the example a bit so it works in the monorepo, please have a look at it and undraft it when you want me to review the contents

Closing this PR for now until I have time to look at it again.