text:
Realtime state of Hue controlled by TRADFRI remote

Issue

When using TRADFRI remote to control Hue (E14 color), their state is not updated on Homekit.
Am I missing something?
Log Messages

Debug Files

Is the light state updated in the Phoscon app or in the old web app?  Do you update the lights through gateway rules, or did you add them to the remote’s group?  What version of deCONZ are you on?  When you change the light through the API or Phoscon app or old web app, is that reflected in HomeKit?

In addition, when using the remote, then in the Phoscon app it is not updated.

It would seem that deCONZ doesn’t update its cache of the light states when the remote controls the lights in the group.  As Hue lights don’t do attribute reporting, you’ll have to wait for deCONZ to poll the lights before it will reflect the actual light state.  Depending on the number of lights in your network, this might take anywhere from 1 second to 1 minute.
deCONZ should eavesdrop on the communication between the remote and the group.  Could you please double-check the the lastupdated attribute of the remote’s ZHASwitch sensor resource is indeed updated when pressing a button?  The remote sends a Toggle command, I’m not sure if deCONZ actually uses that to invert the light states.
If you were to use gateway rules instead of/in addition to the group, deCONZ would send out a group command to control the lights itself, for which it does update the light states.  These rules are created through the REST API, see http://dresden-elektronik.github.io/deconz-rest-doc/rules/.  I use the phcommand from homebridge-hue-utils to interact with the API.  I’ve scripted most of my rules, see https://github.com/ebaauw/ph.sh.

When I press remote's buttons I see the it jumps on the home app, so it being reported to Homekit.
If it is OK, I'm more than happy to use rules instead group.
Would it behave as it is when using group? in terms of response speed, and functionality (brightness/colour)?
Do you know if this is gonna fixed on the deCONZ side anytime?
Will this issue will be happened with other ZB bulbs?
Another question, how can I solve the issue which cause my lights to turn on after power failure?
I can code it, but where is the trigger which tells me the light is powered back?
Another question (Sorry if I'm making this too long, and thanks!!!), Can you provide me an example on how would I set my lights to not get lost from Homekit after power cycle of the deconz SW? It wasn't clear to mean how should I do this...
Again, thank you so much.

BTW, for your records, here's what I get with your ph:
{
"config": {
"UTC": "2018-07-11T18:37:41",
"apiversion": "1.0.9",
"backup": {
"errorcode": 0,
"status": "idle"
},
"bridgeid": "00212EFFFF0178F2",
"datastoreversion": "60",
"devicename": "RaspBee",
"dhcp": true,
"factorynew": false,
"fwversion": "0x261f0500",
"gateway": "192.168.1.1",
"internetservices": {
"remoteaccess": "disconnected"
},
"ipaddress": "192.168.1.39",
"linkbutton": false,
"localtime": "2018-07-11T21:37:41",
"mac": "b8:27:eb:3c:a3:88",
"modelid": "deCONZ",
"name": "Phoscon-GW",
"netmask": "255.255.255.0",
"networkopenduration": 60,
"panid": 11055,
"portalconnection": "disconnected",
"portalservices": false,
"portalstate": {
"communication": "disconnected",
"incoming": false,
"outgoing": false,
"signedon": false
},
"proxyaddress": "none",
"proxyport": 0,
"replacesbridgeid": null,
"rfconnected": true,
"starterkitid": "",
"swupdate": {
"checkforupdate": false,
"devicetypes": {
"bridge": false,
"lights": [],
"sensors": []
},
"notify": false,
"text": "",
"updatestate": 0,
"url": ""
},
"swupdate2": {
"autoinstall": {
"on": false,
"updatetime": ""
},
"bridge": {
"lastinstall": "",
"state": "allreadytoinstall"
},
"checkforupdate": false,
"install": false,
"lastchange": "",
"lastinstall": "",
"state": "allreadytoinstall"
},
"swversion": "2.5.31",
"timeformat": "12h",
"timezone": "Etc/GMT-3",
"uuid": "9afe6e50-8aa4-495b-b380-8382e9590201",
"websocketnotifyall": true,
"websocketport": 443,
"whitelist": {
"0D86929499": {
"create date": "2018-06-29T15:06:53",
"last use date": "2018-07-11T18:37:37",
"name": "homebridge-hue#raspberrypi"
},
"3578ACBA1E": {
"create date": "2018-07-11T18:35:47",
"last use date": "2018-07-11T18:37:41",
"name": "ph#raspberrypi"
},
"570DAC2806": {
"create date": "2018-07-01T01:01:38",
"last use date": "2018-07-03T18:25:33",
"name": "Phoscon#B1024x653"
},
"99D2ADF803": {
"create date": "2018-06-29T14:59:44",
"last use date": "2018-07-11T18:37:24",
"name": "Phoscon#B1324x885"
}
},
"zigbeechannel": 25
},
"groups": {
"1": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"hidden": false,
"id": "1",
"lights": [
"1"
],
"lightsequence": [],
"multideviceids": [],
"name": "Group 1",
"scenes": [],
"state": {
"all_on": false,
"any_on": false
},
"type": "LightGroup"
},
"2": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "779c414645f4be4200e772650d1b33d6",
"hidden": false,
"id": "2",
"lights": [
"2",
"3",
"4"
],
"lightsequence": [],
"multideviceids": [],
"name": "House Entry Candelabra",
"scenes": [],
"state": {
"all_on": true,
"any_on": true
},
"type": "LightGroup"
},
"3": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "ab6432cb8d47f408dd93a86e70fb7d3f",
"hidden": false,
"id": "3",
"lights": [
"5"
],
"lightsequence": [],
"multideviceids": [],
"name": "Test Group",
"scenes": [],
"state": {
"all_on": true,
"any_on": true
},
"type": "LightGroup"
},
"12884": {
"action": {
"bri": 127,
"colormode": "ct",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [
"8"
],
"etag": "f49fa65b821d67468f1a4a3eb5015f25",
"hidden": false,
"id": "12884",
"lights": [
"5"
],
"lightsequence": [],
"multideviceids": [],
"name": "TRADFRI remote control 8",
"scenes": [],
"state": {
"all_on": true,
"any_on": true
},
"type": "LightGroup"
},
"27265": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [
"5"
],
"etag": "779c414645f4be4200e772650d1b33d6",
"hidden": false,
"id": "27265",
"lights": [
"2",
"3",
"4"
],
"lightsequence": [],
"multideviceids": [],
"name": "TRADFRI remote control 5",
"scenes": [],
"state": {
"all_on": true,
"any_on": true
},
"type": "LightGroup"
},
"46483": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [
"7"
],
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"hidden": false,
"id": "46483",
"lights": [],
"lightsequence": [],
"multideviceids": [],
"name": "TRADFRI remote control 7",
"scenes": [],
"state": {
"all_on": false,
"any_on": false
},
"type": "LightGroup"
},
"58307": {
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"scene": null,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [
"6"
],
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"hidden": false,
"id": "58307",
"lights": [],
"lightsequence": [],
"multideviceids": [],
"name": "TRADFRI remote control 6",
"scenes": [],
"state": {
"all_on": false,
"any_on": false
},
"type": "LightGroup"
}
},
"lights": {
"1": {
"etag": "7aac1f05f6118f99dd1aba9ee7f56a5d",
"hascolor": false,
"manufacturername": "ubisys",
"modelid": "D1 (5503)",
"name": "Light 1",
"state": {
"alert": "none",
"bri": 254,
"on": false,
"reachable": true
},
"swversion": null,
"type": "Dimmable light",
"uniqueid": "00:1f:ee:00:00:00:2b:d7-01"
},
"2": {
"ctmax": 500,
"ctmin": 153,
"etag": "84d680909cba2cd39fcbbf8b991fa9d6",
"hascolor": true,
"manufacturername": "Philips",
"modelid": "LCT012",
"name": "Light 2",
"state": {
"alert": "none",
"bri": 254,
"colormode": "ct",
"ct": 410,
"effect": "none",
"hue": 8023,
"on": true,
"reachable": true,
"sat": 176,
"xy": [
0.484597,
0.416014
]
},
"swversion": "1.15.2_r19181",
"type": "Extended color light",
"uniqueid": "00:17:88:01:03:b8:35:2b-0b"
},
"3": {
"ctmax": 500,
"ctmin": 153,
"etag": "84d680909cba2cd39fcbbf8b991fa9d6",
"hascolor": true,
"manufacturername": "Philips",
"modelid": "LCT012",
"name": "Light 3",
"state": {
"alert": "none",
"bri": 254,
"colormode": "ct",
"ct": 410,
"effect": "none",
"hue": 8023,
"on": true,
"reachable": true,
"sat": 176,
"xy": [
0.484597,
0.416014
]
},
"swversion": "1.15.2_r19181",
"type": "Extended color light",
"uniqueid": "00:17:88:01:03:b8:35:30-0b"
},
"4": {
"ctmax": 500,
"ctmin": 153,
"etag": "279a7a8f95d3f17702e3b6a9cc364b65",
"hascolor": true,
"manufacturername": "Philips",
"modelid": "LCT012",
"name": "Light 4",
"state": {
"alert": "none",
"bri": 254,
"colormode": "ct",
"ct": 410,
"effect": "none",
"hue": 8023,
"on": true,
"reachable": true,
"sat": 176,
"xy": [
0.484597,
0.416014
]
},
"swversion": "1.15.2_r19181",
"type": "Extended color light",
"uniqueid": "00:17:88:01:03:ba:12:b3-0b"
},
"5": {
"ctmax": 500,
"ctmin": 153,
"etag": "59ebff1391bab293208958c46e953e6a",
"hascolor": true,
"manufacturername": "Philips",
"modelid": "LCT012",
"name": "Light 5",
"state": {
"alert": "none",
"bri": 250,
"colormode": "ct",
"ct": 334,
"effect": "none",
"hue": 8418,
"on": true,
"reachable": true,
"sat": 140,
"xy": [
0.459137,
0.411633
]
},
"swversion": "1.15.2_r19181",
"type": "Extended color light",
"uniqueid": "00:17:88:01:03:ba:13:0c-0b"
}
},
"resourcelinks": {},
"rules": {
"1": {
"actions": [
{
"address": "/groups/27265/action",
"body": {
"ct_inc": -32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/5/state/buttonevent",
"operator": "eq",
"value": "4002"
},
{
"address": "/sensors/5/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T15:09:59",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-cw-5",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
},
"2": {
"actions": [
{
"address": "/groups/27265/action",
"body": {
"ct_inc": 32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/5/state/buttonevent",
"operator": "eq",
"value": "5002"
},
{
"address": "/sensors/5/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T15:09:59",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-ww-5",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
},
"5": {
"actions": [
{
"address": "/groups/46483/action",
"body": {
"ct_inc": -32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/7/state/buttonevent",
"operator": "eq",
"value": "4002"
},
{
"address": "/sensors/7/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T21:20:14",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-cw-7",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
},
"6": {
"actions": [
{
"address": "/groups/46483/action",
"body": {
"ct_inc": 32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/7/state/buttonevent",
"operator": "eq",
"value": "5002"
},
{
"address": "/sensors/7/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T21:20:14",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-ww-7",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
},
"7": {
"actions": [
{
"address": "/groups/12884/action",
"body": {
"ct_inc": -32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/8/state/buttonevent",
"operator": "eq",
"value": "4002"
},
{
"address": "/sensors/8/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T21:21:39",
"etag": "f3c55d7f8aa3e7c6f530f2512488afc8",
"lasttriggered": "2018-07-11T18:24:35",
"name": "default-ct-cw-8",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 8
},
"8": {
"actions": [
{
"address": "/groups/12884/action",
"body": {
"ct_inc": 32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/8/state/buttonevent",
"operator": "eq",
"value": "5002"
},
{
"address": "/sensors/8/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-10T21:21:39",
"etag": "59ebff1391bab293208958c46e953e6a",
"lasttriggered": "2018-07-11T18:24:40",
"name": "default-ct-ww-8",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 7
},
"9": {
"actions": [
{
"address": "/groups/58307/action",
"body": {
"ct_inc": -32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/6/state/buttonevent",
"operator": "eq",
"value": "4002"
},
{
"address": "/sensors/6/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-11T14:51:40",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-cw-6",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
},
"10": {
"actions": [
{
"address": "/groups/58307/action",
"body": {
"ct_inc": 32,
"transitiontime": 4
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/sensors/6/state/buttonevent",
"operator": "eq",
"value": "5002"
},
{
"address": "/sensors/6/state/lastupdated",
"operator": "dx"
}
],
"created": "2018-07-11T14:51:40",
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"lasttriggered": "none",
"name": "default-ct-ww-6",
"owner": "deCONZ",
"periodic": 0,
"status": "enabled",
"timestriggered": 0
}
},
"schedules": {},
"sensors": {
"1": {
"config": {
"configured": true,
"on": true,
"sunriseoffset": 30,
"sunsetoffset": -30
},
"etag": "888dcc13bc8b82dd21a25632c1a198b3",
"manufacturername": "Philips",
"modelid": "PHDL00",
"name": "Daylight",
"state": {
"dark": true,
"daylight": false,
"lastupdated": "2018-07-11T18:29:14",
"status": 230
},
"swversion": "1.0",
"type": "Daylight",
"uniqueid": "00:21:2e:ff:ff:01:78:f2-01"
},
"2": {
"config": {
"group": null,
"mode": "momentary",
"on": true,
"reachable": true
},
"ep": 2,
"etag": "7aac1f05f6118f99dd1aba9ee7f56a5d",
"manufacturername": "ubisys",
"mode": 1,
"modelid": "D1 (5503)",
"name": "Switch 2",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "00:1f:ee:00:00:00:2b:d7-02-0006"
},
"3": {
"config": {
"on": true,
"reachable": true
},
"ep": 4,
"etag": "d99c8f648b2b01080a7486b324fb3470",
"manufacturername": "ubisys",
"modelid": "D1 (5503)",
"name": "Consumption 3",
"state": {
"consumption": 10995,
"lastupdated": "2018-07-11T18:37:14",
"power": 0
},
"type": "ZHAConsumption",
"uniqueid": "00:1f:ee:00:00:00:2b:d7-04-0702"
},
"4": {
"config": {
"on": true,
"reachable": true
},
"ep": 4,
"etag": "6a3ab93e5b694f400cc900674d0a66f7",
"manufacturername": "ubisys",
"modelid": "D1 (5503)",
"name": "Power 4",
"state": {
"current": 40,
"lastupdated": "2018-07-11T18:37:24",
"power": 0,
"voltage": 230
},
"type": "ZHAPower",
"uniqueid": "00:1f:ee:00:00:00:2b:d7-04-0b04"
},
"5": {
"config": {
"alert": "none",
"battery": 87,
"group": "27265",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "05a1880bd9b7ff2cca434cf1fff0c259",
"manufacturername": "IKEA of Sweden",
"mode": 3,
"modelid": "TRADFRI remote control",
"name": "TRÅDFRI remote control",
"state": {
"buttonevent": 1002,
"lastupdated": "2018-07-11T16:32:56"
},
"swversion": "1.1.1.1-5.7.2.0",
"type": "ZHASwitch",
"uniqueid": "00:0b:57:ff:fe:bb:15:62-01-1000"
},
"6": {
"config": {
"alert": "none",
"battery": 100,
"group": "58307",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "a4cbe8d803912c6762a498462121087a",
"manufacturername": "IKEA of Sweden",
"mode": 3,
"modelid": "TRADFRI remote control",
"name": "TRÅDFRI remote control (2)",
"state": {
"buttonevent": 1001,
"lastupdated": "2018-07-11T14:51:40"
},
"swversion": "1.1.1.1-5.7.2.0",
"type": "ZHASwitch",
"uniqueid": "00:0b:57:ff:fe:bd:d5:dc-01-1000"
},
"7": {
"config": {
"alert": "none",
"battery": 100,
"group": "46483",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "1dc11ffcebc742af602ef2848db2a96c",
"manufacturername": "IKEA of Sweden",
"mode": 3,
"modelid": "TRADFRI remote control",
"name": "TRÅDFRI remote control (3)",
"state": {
"buttonevent": 1002,
"lastupdated": "2018-07-11T14:51:36"
},
"swversion": "1.1.1.1-5.7.2.0",
"type": "ZHASwitch",
"uniqueid": "00:0b:57:ff:fe:b1:fc:95-01-1000"
},
"8": {
"config": {
"alert": "none",
"battery": 100,
"group": "12884",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "5c6ad0505fc235d528bf9fb098987800",
"manufacturername": "IKEA of Sweden",
"mode": 3,
"modelid": "TRADFRI remote control",
"name": "TRÅDFRI remote control (4)",
"state": {
"buttonevent": 1002,
"lastupdated": "2018-07-11T18:24:47"
},
"swversion": "1.1.1.1-5.7.2.0",
"type": "ZHASwitch",
"uniqueid": "00:0b:57:ff:fe:bd:e3:16-01-1000"
}
}
}

For me it seems that deCONZ are automatically setup the rules, since it seems to be configured already.
Is that possible? Am I missing something?
If the rules are set, then why Homekit is not updated?

Would it behave as it is when using group? in terms of response speed, and functionality (brightness/colour)?

In theory there's a bit of a delay (10s-100s of ms), because now the sensor command is sent to the RaspBee, and the RaspBee sends a new command to the light.  In practice, you'll hardly notice.  Functionally, rules are far more flexible.  I'm actually using both groups and gateway rules for my Hue dimmer switches, so I can still control my lights when deCONZ is down.  Alternatively, you can use HomeKit automations, but be careful when controlling a larger number of lights from a single HomeKit scene: this might cause delays in response times.  I'm actually using my Trådfri remotes to control my Sonos speakers through HomeKit automations.

Do you know if this is gonna fixed on the deCONZ side anytime?

Best open an issue with deCONZ.  @manup started implementing a fast-poll of the lights in a group, when receiving a group or scene command, but that's not yet working.  Currently, light states are updated only for On and Off commands and on recalling scenes (I checked the code - not on Toggle, nor on Level commands).

Will this issue will be happened with other ZB bulbs?

Depends on the bulb: if it reports attribute reporting (IKEA, OSRAM), the state will be updated immediately when the light reports its new state.  If it doesn't (Philips, innr), you'll have to wait for the next polling cycle (which in my test even longer than a minute - there's still something rotten in the poll manager).

how can I solve the issue which cause my lights to turn on after power failure?
I can code it, but where is the trigger which tells me the light is powered back?

Effectively, there's no trigger to tell you when a light is powered back.  You cannot set rules on state.reachable, and even if you could, it would take quite some time before deCONZ reports it as false, so you wouldn't even register a brief power cycle.  See #41.
However, when you have a power failure, deCONZ restarts: that's recognised easily, see https://github.com/ebaauw/ph.sh/blob/9ee46f9a3fde586c8306941e4f6a36f748024fdb/ph_rules.sh#L306.  Alternatively, you could implement an el-cheapo UPS for your Raspberry using a pass-through USB power bank, see https://github.com/ebaauw/homebridge-hue/issues/41#issuecomment-387698046.

Can you provide me an example on how would I set my lights to not get lost from Homekit after power cycle of the deconz SW? It wasn't clear to mean how should I do this...

Run ph lightlist once all your lights have been discovered, and homebridge-hue will delay starting up homebridge, until all lights are available.  See #246.

For me it seems that deCONZ are automatically setup the rules, since it seems to be configured already.  If the rules are set, then why Homekit is not updated?

Only for the change in colour temperature (Next and Previous buttons or buttonevents 5002 and 4002).  You need to setup rules for the other buttons.  For the On/Off button you'll need two rules, each with an additional condition on the light or group state (not very reliable) or on a CLIPGenericFlag to turn the lights on when they're off or off when they're on.  The REST API doesn't have a toggle command.

Aha, I see the point.
deCONZ create rules for the color temp actions, since it is a kind of custom to the TRADFRI remote, and after checking in the Phoscon app, it gets updated when im changing the ct using the remote.
OK, so I've got the idea.

If the bulb was off by ZB, and a power outage happened, and then returns, isn't the bulb report its new power on state to the ZB network?

BTW, for your records, here's what I get with your ph

Only five lights - polling should be relatively fast.  The ubisys D1 does support attribute reporting - if you'd control that from the remote, you should see its state updated in HomeKit.

I'm using my ubisys only for testing now, since they have an issue with some led bulbs that even on power off, the bulbs are glowing, which is annoying.

Is the double action of using rules and group together makes issues? such as increasing the brightness twice?
And for my previous question, If the bulb was powered off by ZB, and a power outage happened, and then returns, isn't the bulb report its new power on state to the ZB network?

Is the double action of using rules and group together makes issues? such as increasing the brightness twice?

You're right.  You need idempotent commands.  I only implemented On and Off in rules, and use only the group for brightness increase/decrease.  For Toggle and On or Off, you'd really need a CLIPGenericFlag to keep track of the current state.

If the bulb was powered off by ZB, and a power outage happened, and then returns, isn't the bulb report its new power on state to the ZB network?

Again, this depends on whether the bulb supports attribute reporting.  Philips lights will only announce their presence on the network (which only sets state.reachable to true, which cannot be used in rules).  If lucky, deCONZ fast polls the light on receiving the announcement, but that will probably take too long for comfort.  Try with your traditional wall switch to see how Phoscon reacts to power cycles.  Even then, you cannot recognise in the API whether the light was turned on by a traditional wall switch, by a power restore, or by another app.

First I want to thank you again for your support.
Now to the point.
I don't really know what CLIPGenericFlag is, can you explain me a bit more?
As for the power outage stuff, if I will use Homekit to control the lights (or even customise your Homebridge plugin to do it regardless Homekit itself), then once I see "power on" state from outside of my loop, I will be able to know it is a outage restore.
Do you think about some other issues which might occur this way?
(I used to do it with my lifx bulbs, so after a few seconds which wifi connection completed, they go off to their last state.
In addition, I built my flic plugin which toggled the bulbs power regardless Homekit loop.)
Do you know about a good ZigBee (tunable whites, but I prefer full color) bulbs with lumen output above 1000 lm? (I know the Ikea tradfri 980lm)

I see now another issue.
When I change the color from Homekit, it Is not applied until is toggle the power of the bulb.

I don't really know what CLIPGenericFlag is, can you explain me a bit more?

See https://github.com/ebaauw/homebridge-hue/wiki/Getting-Started#24-clip-sensors.  I still need to re-organise the Wiki...

As for the power outage stuff, if I will use Homekit to control the lights (or even customise your Homebridge plugin to do it regardless Homekit itself), then once I see "power on" state from outside of my loop, I will be able to know it is a outage restore.
Do you think about some other issues which might occur this way?

If you only control your lights from HomeKit it'll work.  Once you'll be using motion sensors, schedules, remotes, other apps to control your lights it won't.  See the scenarios in #41.

Do you know about a good ZigBee (tunable whites, but I prefer full color) bulbs with lumen output above 1000 lm? (I know the Ikea tradfri 980lm)

No, sorry.

When I change the color from Homekit, it Is not applied until is toggle the power of the bulb.

What HomeKit app?  What does the homebridge-hue log say?  You cannot change colour (or brightness or colour temperature) while the light is off (this is a ZigBee limitation).

I'm using the Home app from the App Store and Apple's home app.
I'm trying to set the color while the light is powered on.
This is the log from the Homebridge-hue:
[2018-7-11 23:20:53] [Phillips Hue] Light 5: homekit color temperature changed from 468 mired to 342 mired
[2018-7-11 23:20:53] [Phillips Hue] Light 5: homekit color temperature changed from 342 mired to 184 mired
[2018-7-11 23:20:54] [Phillips Hue] Light 5: homekit color temperature changed from 184 mired to 153 mired
[2018-7-11 23:20:59] [Phillips Hue] Light 5: homekit color temperature changed from 153 mired to 192 mired
[2018-7-11 23:21:01] [Phillips Hue] Light 5: homekit color temperature changed from 192 mired to 266 mired
[2018-7-11 23:21:01] [Phillips Hue] Light 5: homekit color temperature changed from 266 mired to 348 mired
[2018-7-11 23:21:03] [Phillips Hue] Light 5: homekit color temperature changed from 348 mired to 496 mired
[2018-7-11 23:21:03] [Phillips Hue] Light 5: homekit color temperature changed from 496 mired to 464 mired
[2018-7-11 23:21:06] [Phillips Hue] Light 5: homekit saturation changed from 75% to 29%
[2018-7-11 23:21:06] [Phillips Hue] Light 5: homekit hue changed from 0˚ to 281˚
[2018-7-11 23:21:06] [Phillips Hue] Light 5: homekit saturation changed from 29% to 69%
[2018-7-11 23:21:06] [Phillips Hue] Light 5: homekit hue changed from 281˚ to 249˚
[2018-7-11 23:21:10] [Phillips Hue] Light 5: homekit saturation changed from 69% to 2%
[2018-7-11 23:21:10] [Phillips Hue] Light 5: homekit hue changed from 249˚ to 205˚
[2018-7-11 23:21:10] [Phillips Hue] Light 5: homekit saturation changed from 2% to 8%
[2018-7-11 23:21:10] [Phillips Hue] Light 5: homekit hue changed from 205˚ to 139˚
[2018-7-11 23:21:10] [Phillips Hue] Light 5: homekit saturation changed from 8% to 9%
[2018-7-11 23:21:11] [Phillips Hue] Light 5: homekit saturation changed from 9% to 16%
[2018-7-11 23:21:11] [Phillips Hue] Light 5: homekit hue changed from 139˚ to 111˚
[2018-7-11 23:21:11] [Phillips Hue] Light 5: homekit saturation changed from 16% to 17%
[2018-7-11 23:21:11] [Phillips Hue] Light 5: homekit hue changed from 111˚ to 73˚
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit saturation changed from 17% to 22%
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit hue changed from 73˚ to 46˚
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit saturation changed from 22% to 12%
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit hue changed from 46˚ to 18˚
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit saturation changed from 12% to 15%
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit hue changed from 18˚ to 359˚
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit saturation changed from 15% to 16%
[2018-7-11 23:21:12] [Phillips Hue] Light 5: homekit hue changed from 359˚ to 354˚
[2018-7-11 23:21:14] [Phillips Hue] Light 5: homekit saturation changed from 16% to 0%
[2018-7-11 23:21:14] [Phillips Hue] Light 5: homekit hue changed from 354˚ to 0˚
[2018-7-11 23:21:14] [Phillips Hue] Light 5: set homekit hue from 0˚ to 222˚
[2018-7-11 23:21:15] [Phillips Hue] Light 5: set homekit hue from 222˚ to 226˚
[2018-7-11 23:21:21] [Phillips Hue] Light 5: homekit saturation changed from 0% to 40%
[2018-7-11 23:21:21] [Phillips Hue] Light 5: homekit hue changed from 226˚ to 346˚
[2018-7-11 23:21:22] [Phillips Hue] Light 5: homekit saturation changed from 40% to 70%
[2018-7-11 23:21:22] [Phillips Hue] Light 5: homekit hue changed from 346˚ to 8˚
[2018-7-11 23:21:22] [Phillips Hue] Light 5: homekit saturation changed from 70% to 96%
[2018-7-11 23:21:22] [Phillips Hue] Light 5: homekit hue changed from 8˚ to 13˚
On all this, the light didn't applied any effect.
Only after power toggle it show the new light color (toggle even using the remote). weird.

Very odd, I don’t know what’s happening.  From the log, Home does send the updates to homebridge / homebridge-hue.  I don’t see the toggle, though.
Does this also happen for your other lights?  If no, what happens after you power cycle the light.  If yes, just to humour me, could you please stop deCONZ, remove and re-insert the ConBee, power cycle all lights and the D1, start deCONZ, restart homebridge, and check whether this still occurs.
If so, could you please attach the debug log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file) and debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file)?
Not sure if related, but there’s newer firmware available for your lights.  Unfortunately, you can only update this through the Hue bridge and Hue app.

authors: aryelevin ebaauw

repo: ebaauw/homebridge-hue


text:
Plugin RangeError

Hi! Tried connecting this to my Pi Zero W, which isn't running any GPIO stuff at all. (Just want to monitor the temperature for now.) But it keeps throwing an error that kills HB, then reboots it over and over.
Here's the pertinent part of the error log:
[8/29/2020, 7:17:28 PM] [RPi] 192.168.7.143: connected to 192.168.7.143:22
[8/29/2020, 7:17:28 PM] RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 7. Received 12
at boundsError (internal/buffer.js:77:9)
at Buffer.readInt32LE (internal/buffer.js:381:5)
at PigpioClient._onCmdData (/usr/local/lib/node_modules/homebridge-rpi/lib/PigpioClient.js:466:16)
at Socket.emit (events.js:315:20)
at addChunk (_stream_readable.js:295:12)
at readableAddChunk (_stream_readable.js:271:9)
at Socket.Readable.push (_stream_readable.js:212:10)
at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
[8/29/2020, 7:17:28 PM] Got SIGTERM, shutting down Homebridge...
Not sure if I borked something by not adding a GPIO device or what...

What’s your config.json?  You seem to be connecting tossh (port 22) instead of pigpiod.

Ah, OK, this is my bad. Since I wasn't trying to pull anything from the GPIO, I thought I should just connect to SSH. I didn't give the installation instructions a third look and made some assumptions! When I hook it all back up again, I'll connect to pigpiod instead. (Can't show the config because I had to uninstall the plugin to keep it from restarting HB over and over.)
Thanks!

source: gharchive/issue

repo: ebaauw/homebridge-rpi

license_type: permissive

license_source: github-api


text:
can support SMS spam for Vietnam country?

can support SMS spam for Vietnam country?

Unfortunately sms spam does not work for this country

authors: datlmhg ebankoff


text:
McCormack-Human-10x3pv2

Project short name: McCormack-Human-10x3pv2
Primary Wrangler: @anu-shiva
Secondary Wrangler: @Wkt8

Associated files

Google Drive

Published study links

Paper: Xu_2020

Accessioned data: GSE135851

Ingest
Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[ ] Are the analysis files suitable for CellxGene? If something is missing get in touch with the authors to request it
[x] Upload sheet to validate metadata
[x] Transfer raw files to ingest to validate data files
[x] Check linking using ingest graph validator
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

Hey Anu, looks good! Just a couple things that I wasn't sure where you got the information from.
Project_Cell_Count

seems really low, where did you get this number from?
12374 cells?
In the paper just the LAM cells are already 21,964 cells

Dissociation_protocol

Optional, but consider splitting up the "Tissue pieces were dounced 40 times with a loose pestle followed by 20 times with a tight pestle and transferred to a 15 mL conical tube to which 2 mL of Nuclei EZ lysis buffer was added." into a

mechanical and
non-enzymatic chemical dissociation nuclei extraction step

Enrichment_protocol

Why are they using uM as the units? micromolar? Shouldn't it be micrometers...
Should the maximum size for enrichment_single_nuclei_size be 30um?
There is a typo in the cell markers for (enrichment_single_nuclei_facs) 'DAPI + s'

Cell_suspension

cell viability should be 'pass'
There aren't any dissociation or enrichment protocols for the normal single-cell lung

We could potentially assume here that as a control it underwent the same protocols as the LAM scRNA-seq lungs. Or we could send an email checking this.

Sequencing_protocol

For some reason, the GEO page states that a number of the samples were sequenced using Illumina HiSeq 2500 even though it's not mentioned anywhere in the paper

Hi Wei! Thanks for the comments, I have made the changes.

So the cell count of 12374 was generated by Ingest. Corrected it to 21,964.
enrichment - ya I think they misspelled it as uM in the supplemental info  instead of um. I have changed this,
for seq protocol- I could not find Illumina HiSeq 2500 anywhere - it might be a mistake on the SRA.

As mentioned in #1205 an update on the linking needs to be done (cell suspension is linked directly to donors)

Link update was done through ingest UI, exporting

Closing as last update was verified in browser.

authors: Wkt8 anu-shiva arschat

repo: ebi-ait/hca-ebi-wrangler-central


text:
Prepare slides for "Bioinformatics for PIs" course

Description of the task:
@gabsie and I have been asked to help with a talk on the "Bioinformatics for PIs" course that is being held Wed-Fri
We need to prepare the slides created by claire, melanie and Henriette for last years' talk
Acceptance criteria for the task:

[ ] Slides are updated
[ ] Slides are reviewed and sent to the course

@ESapenaVentura and @gabsie working on this from today.


text:
feat: add summit 2022 banner

This PR brings a banner for the eBPF 2022 summit

@xmulligan I've updated the button text
@qmonnet thanks for the review!
The formatting changes are my bad, I've failed to notice these linter-introduces changes before commiting, won't do so next time (or will add them in a separate PR).
Please note that we have also updated the banner mobile layout, so that the date would still be visible on small screens.

source: gharchive/pull-request


text:
🐛 Bug ➾ script test:unit:deno fails with error :  Relative import path ...  not prefixed with / or ./ or ../

🚥 Status (Internal Taqueria Team Use Only)

[ ] 🔬 Investigated and Verified
[ ] ⚗ Solution Identified and Designed
[ ] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
michael@debian11 ~/taqueria (mk-taq-stryker)$ npm run test:unit:deno -w tests

@taqueria/tests@0.24.2 test:unit:deno
TEST=true deno test unit/ --allow-all --unstable --import-map ../import_map.json

error: Module not found "file:///home/michael/taqueria/tests/unit/helpers".
at file:///home/michael/taqueria/tests/unit/plugins.test.ts:10:28
🆘 Steps to Reproduce?

run  npm run test:unit:deno:with-coverage
[error](error: Relative import path "@taqueria/protocol/InstalledPlugin" not prefixed with / or ./ or ../)

🪵 Relevant log output
No response
🐘 How impactful is this bug?
🤯 Major disruption
⏱ Prevalance
if you try to run test coverage
💻 Operating System
Windows -> Linux VM
🕸 System Architecture
x64
🌮 Taqueria Version
v0.23.24
🌿 Node.js Version
v18.4.0 and others
☎ Contact Details
michaelkernaghan@ecadlabs.com
Code of Conduct

[X] I agree to follow this project's Code of Conduct

this was fixed by doing some local setup. not a bug.

repo: ecadlabs/taqueria


text:
Bug: Landscape and portrait crashes app

I have noticed this before on mobile app. It seems if I watch a video and try full screen it in portrait it works but if I try turn the screen for a full screen video then the Ecency app freezes and I need to restart it.

Duplicate issue. Refer here https://github.com/ecency/ecency-mobile/issues/2093#issuecomment-1065894479

authors: aliseyalvi feruzm

repo: ecency/ecency-mobile

license: MIT


text:
How to start an AAS server in development-v2

I've tried to start a AAS server on the development-v2 branch, as I need to aim for as much AAS Spec. v3 support as possible.
Porting an v1 application hasn't proofed to difficult, however I can't seem to find out how I'm supposed to start the AAS Server component. Registry still exists.
The corresponding files were deleted in #6 and since as far as I can tell no substitute has been added.
How do I start an AAS server on the develpoment-v2 branch?

The development-v2 branch is only providing the content for the registry in a preview stage since we're planning to restructure the SDK and Components in the process of preparing the v2 release.
Thus, right now there no AAS Server provided for v2. However, feel free to use the AAS Server of v1 with the Registry of v2. Please note that this may not work out of the box.
I will update this ticket as soon as the AAS Server is available in v2.

We have started the work on the AAS Repository and Submodel Repository in the following branch:
https://github.com/eclipse-basyx/basyx-java-components/tree/development-v2

authors: FrankSchnicke OParczyk

repo: eclipse-basyx/basyx-java-components


text:
Need to be able to review GH inputs on JHU deploy actions

Production runs of Publish to SNS Topic: Triggers Deployment to AWS and Deploy PASS Services and Data Loaders to ECS AWS need to show input values so they are available for the reviewer

Changed gh workflows to use run-name so the name of the workflow action when running will show the input values of the workflow.

repo: eclipse-pass/main


text:
refactor: remove ember data deprecate array like deprecation

This one involves removing the following deprecation:
https://api.emberjs.com/ember-data/4.12/classes/currentdeprecations/properties?anchor=DEPRECATE_ARRAY_LIKE

closing in favor of #1275

repo: eclipse-pass/pass-ui


text:
docs: update installation steps

Closes #97
Updated installation steps in INSTALL.md file

I also noticed that https://github.com/eclipse-tractusx/sd-factory/blob/main/charts/sdfactory/README.md is out of date due to the change from #93 and #91 Please update it and please also reference the README in the charts directory in the install.md here

Updated this as well.

repo: eclipse-tractusx/sd-factory


text:
docs: fix #980, #537

WHAT

docs: point to deployment properties in charts folder
docs: harmonize file naming
docs: remove operation view
docs: reorganize docs folder structure
docs: correct links in mgmt-api-walkthrough

FURTHER NOTES
completes the content that #987 introduced
followup to #993
non redundant to #984
Closes #980, #537

TIL: the blank line at the end of the DEPENDENCIES file is mission-critical.

repo: eclipse-tractusx/tractusx-edc


text:
libnd4j: Conv1d_bp causal mode fails for both CUDA and CPU

Built locally on current master with MKLDNN (no libnd4j CUDNN).
Essentially same stack trace on both ("Can't find requested...")
Pulled out of CNN1DGradientCheckTest.testCnn1dCausal
    @Test
    public void test(){

        DynamicCustomOp op = DynamicCustomOp.builder("conv1d_bp")
                .addInputs(
                        Nd4j.create(DataType.FLOAT, 2,2,12),
                        Nd4j.create(DataType.FLOAT, 3,2,3),
                        Nd4j.create(DataType.FLOAT, 2,3,6)
                )
                .addOutputs(
                        Nd4j.create(DataType.FLOAT, 2,2,12),
                        Nd4j.create(DataType.FLOAT, 3,2,3))
                .addIntegerArguments(3,2,0,1,2,0)
                .build();

        Nd4j.exec(op);

    }

java.lang.RuntimeException: Op [conv1d_bp] execution failed

	at org.nd4j.linalg.cpu.nativecpu.ops.NativeOpExecutioner.exec(NativeOpExecutioner.java:1662)
	at org.nd4j.linalg.factory.Nd4j.exec(Nd4j.java:6521)
	at org.deeplearning4j.Temp.test(Temp.java:25)
...
Caused by: java.lang.RuntimeException: Can't find requested variable by index
	at org.nd4j.linalg.cpu.nativecpu.ops.NativeOpExecutioner.exec(NativeOpExecutioner.java:1968)
	at org.nd4j.linalg.cpu.nativecpu.ops.NativeOpExecutioner.exec(NativeOpExecutioner.java:1641)
	... 29 more

Fixed


text:
TCK has wrong group id

The coordinates for the TCK should be org.eclipse.microprofile.health:microprofile-health-tck  there's a tck in the group ID that shouldn't be there.

Corrected the group id in 4d525b5

repo: eclipse/microprofile-health


text:
Issue 180 Replace InvalidLRAParticipantDefinitionException with any u…

…nspecified RuntimeException
resolves #180
Signed-off-by: xstefank xstefank122@gmail.com

This is good to go from my point of view. I do wonder if we have to force the deployment to fail at the spec level or instead leave it up to vendor to perhaps log a warning/error?  Was that option discussed at the time?

I believe it was. The issue is that signatures are specified in the specification, so anything else will result in RTE when the invalid participant method is called for the first time. Why would someone require such behavior?

It's a reasonable question, I was asking as there is an ongoing similar discussion on https://github.com/eclipse/microprofile-lra/pull/174/files#diff-06aca14982a5ee1e4547e9ec14b41bbbR806 so it would be useful to make these two consistent.
I was thinking if the (for instance compensate) method already existed and was a boolean would that be such a big deal to ignore the return type?
Note that this discussion doesn't have to hold up this pull as it stands it looks good to go.
Also, I am not sure why we allow javax.ws.rs.core.Response for non-JAX-RS participants but I suppose that is not really a big deal.

@tomjenkinson We can say in the spec that in case the return type is not specified (void, ParticipantStatus, Response or CompletionStage right now) then we treat it as if it was void. Is that what you are asking?

It sort of is. I am really saying do we have to fail the deployment but actually your point is adding further weight to the idea of failing the deployment as if we leave it unspecified things could get quite confusing what should happen with signature that is not valid!

I am thinking we should maybe consider not mandating that vendors throw an RTE and rather categorise this cause the deployment to fail?

Exactly Tom, that is my original thinking, fail as soon as you detect something is wrong.

I am thinking we should maybe consider not mandating that vendors throw an RTE and rather categorise this cause the deployment to fail?

This can certainly be done. I can create another PR after #181 is merged.

I am not able to approve the PR - hopefully @mmusgrov or @rdebusscher are able to do so.
For context this removes the extra exception that we don't believe we need. We would also consider that the wording change from throwing an exception to halting deployment for more definitive outcome but that can be discussed async of this PR

authors: tomjenkinson xstefank

repo: eclipse/microprofile-lra


text:
Revamp projects pages on microprofile.io

On the microprofile.io under all projects, it lists all of the projects and disaply the readme for the relevant project. The readme doc is often static and contains old info. We need to revisit the readme and introduce a template so that all of the readme flles adopt the same format.
Here is the draft page for MP config.

@Emily-Jiang did you read the forum thread: https://groups.google.com/forum/?pli=1#!topic/microprofile/7xEB4PO9Zqs yet?
Work in progress!

This ticket is related to automatication using back & front end work (currently being investigated with the help of Summers)
Closing it b.c it doesn't require human adjustments or maintenance as other pages in MP site.

authors: Emily-Jiang aeiras

repo: eclipse/microprofile-marketing


text:
Content not readable on microprofile.io  home page

Sorry but I must again point out that the official microprofile.io homepage has very bad layout problems.
I came across the problem when I just wanted to read something about the Metric API myself. There is sill the problem that the .adoc files are not correctly displayed on the home page.
If you as a user didn't  know the Github source you will not be able to learn something useful about the different projects. And I think this is really really bad.  Because you all do so much good work creating a awesome microservice framework but users who want to learn something about all this starting with microprofile.io will be frustrated after a few minutes.
Just to to point it out once again please compare the following two links which should show the same content:

https://github.com/eclipse/microprofile-metrics/blob/master/spec/src/main/asciidoc/app-programming-model.adoc
https://microprofile.io/project/eclipse/microprofile-metrics/spec/src/main/asciidoc/app-programming-model.adoc

This is how the content should look like (and is shown on Github):

And this is what the user see on microprofile.io

I have tried to point to this problem several times. All Microprofile Projects are affected. It is not a Problem form the different projects. It is only a Problem form how microprofile.io is rendering the README and .adoc files form the project.
I fear that the problem can only be solved with a very great deal of effort. So I can understand that this can not be solved over night. Therefore, I suggest that we refer directly to the corresponding Github projects from the Microprofile.io project overview. This allows us to avoid unnecessarily frustrating or deterring new users.
One could easily stick to the conspiracy theory that someone here is trying to boycott the project....  ;-)

Also #334  is related to the overall situation of microprofile.io

@rsoika did you read the forum thread: https://groups.google.com/forum/?pli=1#!topic/microprofile/7xEB4PO9Zqs yet?
Work in progress!

Thank you for the link.

Hola @rsoika,
I will close this ticket based on your follow up. I hope you are able to provide help on the current work being tackled with the website. See you in that thread.

Hola @rsoika,
I will close this ticket based on your follow up. I hope you are able to provide help on the current work being tackled with the website. See you in that thread.

There are still server errors if I click through the projects:

I wonder why this is not recognized by someone else.
Just to point it out once again: The website https://microprofile.io/ is not working since more than 6 months
Maybe that this error is only reproduceable from Europe and did not occur in the states?
Try to click through all projects in short time - There is still a very have server problem as you can see in the screenshot

There are still server errors if I click through the projects:

I wonder why this is not recognized by someone else.
Just to point it out once again: The website https://microprofile.io/ is not working since more than 6 months
Maybe that this error is only reproduceable from Europe and did not occur in the states?
Try to click through all projects in short time - There is still a very have server problem as you can see in the screenshot

I deeply appreciate your follow up on the thread Ralph!
The Project page is going to be re-done. See you in the forum:)

I deeply appreciate your follow up on the thread Ralph!
The Project page is going to be re-done. See you in the forum:)

Thank you @rsoika for following up with us! We need to fix this pages as soon as possible. I'll put this on the marketing agenda to have this discussed further on 31st Jan. @rsoika here is the calendar if you would like to attend the call.

@Emily-Jiang yes, I will join the 'Marketing call'

Hello @aeiras,
in yesterdays marketing call you were not able to hear me. I am sorry about that. So let me explain it:
I ask you all to go on microprofile.io and then click on big technology buttons like "metrics 4.0" or "health".

How is such information supposed to help someone decide whether Microprofile is the right technology? @Emily-Jiang has written a whole book about microprofiles. Can't you put a short explanation about the technologies there instead of linking to the Github release pages?
Please - I just want to help to improve the project. @aeiras please put yourself in the position of a project manager read the information about the Microprofile technologies and try to understand it -  It is impossible!
I am not a fan of spring, but if you do not understand what I am talking about, do the same on this page: https://spring.io/
I also suggest to remove the [project section[(https://microprofile.io/projects/) completely. It does not improve the project form a marketing perspective.

Here is my suggestion for the Metrics section
Metrics 4.0
Metrics 4.0 gives you a great way to monitor your runntime and your application. Microprofile 4.0 is collecting custom metrics and provides them in the common prometheus format. This makes it easy to visualize and monitor any kind of application parameters. Also it allows you to setup a alerting with the help of Grafana in just a view minutes.

To add your own metrics within your project you can use the Microprofile MetricRegistry:
@ApplicationScoped
public class MetricService {
	@Inject
	@RegistryType(type = MetricRegistry.Type.APPLICATION)
	MetricRegistry metricRegistry;

	public void onExportEvent(exportEvent) {
		// build a counter metric
		Metadata metadata = Metadata.builder().withName("my-metric")
			.withDescription("Invoice Export").withType(MetricType.COUNTER).build();
		List<Tag> tags = new ArrayList<Tag>();
		tags.add(new Tag("method", "export"));
		tags.add(new Tag("mandant", exportEvent.mandantID));
		Counter counter = metricRegistry.counter(metadata,  tags.toArray(new Tag[tags.size()]));
		counter.inc(exportEvent.count);
	}
}

@rsoika let's discuss here.

Here is my suggestion for the Metrics section
Metrics 4.0
Metrics 4.0 gives you a great way to monitor your runntime and your application. Microprofile 4.0 is collecting custom metrics and provides them in the common prometheus format. This makes it easy to visualize and monitor any kind of application parameters. Also it allows you to setup a alerting with the help of Grafana in just a view minutes.

To add your own metrics within your project you can use the Microprofile MetricRegistry:
@ApplicationScoped
public class MetricService {
	@Inject
	@RegistryType(type = MetricRegistry.Type.APPLICATION)
	MetricRegistry metricRegistry;

	public void onExportEvent(exportEvent) {
		// build a counter metric
		Metadata metadata = Metadata.builder().withName("my-metric")
			.withDescription("Invoice Export").withType(MetricType.COUNTER).build();
		List<Tag> tags = new ArrayList<Tag>();
		tags.add(new Tag("method", "export"));
		tags.add(new Tag("mandant", exportEvent.mandantID));
		Counter counter = metricRegistry.counter(metadata,  tags.toArray(new Tag[tags.size()]));
		counter.inc(exportEvent.count);
	}
}

Thank you, Emily for transferring the ticket to the WG repo.
@rsoika,
I hope you continue joining the Marketing hangouts in the future.
I think you wish for MP Specs to have more description, based on your wonderful example. If that is the case, please submit PRs directly to each repo with your write-ups.
That write ought to be found in the Repo for each spec.
I hope we continue to join us on the new ticket. This one is closing because any adjustments that deal with Specs require front-end and back-end work, not marketing.

authors: Emily-Jiang aeiras rsoika


text:
Bump version to 3.1.9

Bump version to 3.1.9
TODOs

[ ] Tests
[ ] Documentation

The failing job is due to the URL check in the documentation (that worked in the other Travis check)

repo: eclipse/steady


text:
Fix/issue 171 - No icons shown in the palette

[ ] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request. Especially, we require a single commit
[x] Ensure that the commit message is a good commit message
[x] Ensure to use auto format in all files
[x] Ensure that you appear in NOTICE at Copyright Holders
[ ] Tests created for changes
[x] Screenshots added (for UI changes)

Could not reopen the PR, so the follow up is at https://github.com/eclipse/winery/pull/310.

authors: ghareeb-falazi koppor

repo: eclipse/winery


text:
Local resources (images) should trigger a console warning if not found

See #455

I think there should be issues for the individual platforms. There is nothing we can do in JS.

authors: jonek tbuschto

repo: eclipsesource/tabris-js

license_source: bigquery


text:
Enriched call .name reverts to procedure symbol defined in explicit interface

If an explicit interface for a subroutine/function is present, the relevant call's .name points to the defined ProcedureSymbol once the subroutine is parsed. If we then call subroutine.enrich_calls, we update call.name to point to the actual subroutine rather than the symbol defined in the interface.
However this update doesn't seem to be permanent. If we ever later access the symbols inside the Interface, then call.routine again reverts to pointing to that symbol rather than the actual subroutine. (demonstrator attached)
I think the fundamental problem here is that we have now introduced two symbols with the same name to a single scope. Given it's such a fundamental issue, I'm at a loss for a proper solution. A quick and dirty fix would be to set scope=None if the symbol already exists when updating call.name in subroutine.enrich_calls.
enrich_calls_bug.txt

That quick fix falls apart as soon as we hit the first rescope_symbols. Hmm....

repo: ecmwf-ifs/loki


text:
Nan values in dewpoint_from_specific_humidity

What happened?
When the t_from_es  function gets called by dewpoint_from_specific_humidity, the np.log is called on a division where the denominator can be zero. It raises a silent error and produces nans in the result (es=0 and v is -inf).
If the specific humidity is zero, nans are systematically produced.
However, shouldn't the dewpoint temperature from a specific humidity of 0.0 be defaulted to some meaningful value, representing the dewpoint temperature of dry air, very low, like 0K? It can be that the specific humidity is very close to 0 and due to rounding, datasets end up with nans, which can reveral rather painful when the data is intended to be used for training of ML models.
def t_from_es(self, es):
        v = np.log(es / self.c1)
        return (v * self.c4w - self.c3w * self.t0) / (v - self.c3w)

What are the steps to reproduce the bug?
Call thermo.dewpoint_from_specific_humidity(q=y, p=x) with some 0 values in y and any pressure in Pa.
Version
v0.6.2
Platform (OS and architecture)
Linux balfrin-ln002 5.14.21-150400.24.81_12.0.87-cray_shasta_c
Relevant log output
No response
Accompanying data
No response
Organisation
No response

@OpheliaMiralles, thank you for reporting this issue. What do you suggest as the value for dewpoint temperature when the specific humidity is 0? Probably it should be a user provided value.

@OpheliaMiralles, please see #23 providing a fix for it.

Many thanks, I think letting the user chose a value is the right way to do it indeed.

Thanks for the feedback. The fix has been released as version 0.2.0.

@OpheliaMiralles, upon further review of this change we decided it introduced too much complexity and had the potential to reduce performance. Therefore we have reverted this change and released version 0.3.0 without the extra parameters.
The simplest solution for your case is just to replace nans with the required value in the results:
from earthkit.meteo import thermo
import numpy as np

q = np.array([0.01, 0])
p = np.array([100000., 100000.])

td = thermo.dewpoint_from_specific_humidity(q, p)
np.nan_to_num(td, copy=False, nan=100.)
td

array([287.16144849, 100.        ])

Alternatively, if the input data can contain nans a mask can be used:
from earthkit.meteo import thermo
import numpy as np

q = np.array([0.01, 0])
p = np.array([100000., 100000.])

mask = q < 1e-10

# prevent RuntimeWarning issued due to calling log with zero
q[mask] = np.nan

td = thermo.dewpoint_from_specific_humidity(q, p)

td[mask] = 100.
td

array([287.16144849, 100.        ])

authors: OpheliaMiralles sandorkertesz

repo: ecmwf/earthkit-meteo


text:
Added code for R package development

@rqthomas @cboettig Here are the first round of updates I made for the R package development

Cool! I'll merge which should trigger our first action build.

(now that we have an action on main, future PRs will also automatically run the R-CMD-Check action too.

authors: addelany cboettig


text:
堆积Bar图设置显示数据Label,最下面的Series的Label会被上面的Series Bar覆盖，导致数据Label显示不全。

下面是个Sample:
option = {
tooltip : {
trigger: 'axis',
axisPointer : {            // 坐标轴指示器，坐标轴触发有效
type : 'shadow'        // 默认为直线，可选为：'line' | 'shadow'
}
},
legend: {
data:['直接访问','邮件营销','联盟广告','视频广告','搜索引擎','百度','谷歌','必应','其他']
},
toolbox: {
show : true,
orient: 'vertical',
x: 'right',
y: 'center',
feature : {
mark : {show: true},
dataView : {show: true, readOnly: false},
magicType : {show: true, type: ['line', 'bar', 'stack', 'tiled']},
restore : {show: true},
saveAsImage : {show: true}
}
},
calculable : true,
xAxis : [
{
type : 'category',
data : ['周一','周二','周三','周四','周五','周六','周日']
}
],
yAxis : [
{
type : 'value'
}
],
series :
[
{
name:'直接访问',
type:'bar',
data:[320, 332, 301, 334, 390, 330, 320],
itemStyle:{
normal:{
label:{
show:true,
formatter: function(param){
return param.value;
}
}
}
}
},
{
name:'邮件营销',
type:'bar',
stack: '广告',
data:[120, 132, 101, 134, 90, 230, 210],
itemStyle:{
normal:{
label:{
show:true,
formatter: function(param){
return param.value;
}
}
}
}
},
{
name:'联盟广告',
type:'bar',
stack: '广告',
data:[220, 182, 191, 234, 290, 330, 310],
itemStyle:{
normal:{
label:{
show:true,
formatter: function(param){
return param.value;
}
}
}
}
},
{
name:'视频广告',
type:'bar',
stack: '广告',
data:[150, 232, 201, 154, 190, 330, 410],
itemStyle:{
normal:{
label:{
show:true,
formatter: function(param){
return param.value;
}
}
}
}
},
{
name:'搜索引擎',
type:'bar',
data:[862, 1018, 964, 1026, 1679, 1600, 1570],
markLine : {
itemStyle:{
normal:{
lineStyle:{
type: 'dashed'
}
}
},
data : [
[{type : 'min'}, {type : 'max'}]
]
},
itemStyle:{
normal:{
label:{
show:true,
formatter: function(param){
return param.value;
}
}
}
}
},
{
name:'百度',
type:'bar',
barWidth : 5,
stack: '搜索引擎',
data:[620, 732, 701, 734, 1090, 1130, 1120]
},
{
name:'谷歌',
type:'bar',
stack: '搜索引擎',
data:[120, 132, 101, 134, 290, 230, 220]
},
{
name:'必应',
type:'bar',
stack: '搜索引擎',
data:[60, 72, 71, 74, 190, 130, 110]
},
{
name:'其他',
type:'bar',
stack: '搜索引擎',
data:[62, 82, 91, 84, 109, 110, 120]
}
]
};

你可以设置label的位置，比如inner，但我觉得如果是超过2条数据，就不要显示label而应该用tootltip了。不然体验很差。

repo: ecomfe/echarts


text:
y轴计算坐标的最大值算法具体是怎么实现？

怎么根据数据的最大值，得到Y轴的最大值呢？或者每个刻度的间隔值？

看代码


text:
使用地图联动以后，hover地图弹出的提示框显示在地图下面，而不是跟随鼠标移动

问题简述 (One-line summary)
版本及环境 (Version & Environment)

ECharts 版本 (ECharts version):
浏览器类型和版本 (Browser version):
操作系统类型和版本 (OS Version):

重现步骤 (Steps to reproduce)

期望结果 (Expected behaviour)
可能哪里有问题 (What went wrong)
ECharts配置项 (ECharts option)

option = {

}

其他信息 (Other comments)

请提供 option


text:
关于ng2动态更新echarts数据

One-line summary [问题简述]
ng2动态更新echarts图表数据
我看介绍说要再一次setOption
我不知道怎么再继续绑定
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:    npm包的    3.5.4
Browser version [浏览器类型和版本]:  chrome
OS Version [操作系统类型和版本]:   window10

Expected behaviour [期望结果]
实现echarts图表数据更新
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

echarts 的数据更新就是 setOption，ng 相关的问题可以去相关社区询问

谢谢


text:
echart gl line3D 数据隔得太近线变成虚线了,怎解决呢

One-line summary [问题简述]
echart gl line3D 数据隔得太近线变成虚线了,怎解决呢
怎样能使先不虚化呢,求解
ECharts option [ECharts配置项]

var data = [];
// Parametric curve
for (var t = 0; t < 100; t +=1) {
    var x = t;
    var y = t;
    var z = 0;
    if(t%2==0){
       z = 1000;
    }
    data.push([x, y, z]);
}
console.log(data.length);

option = {
    tooltip: {},
    backgroundColor: '#fff',
    visualMap: {
        show: false,
        dimension: 2,
        min: 0,
        max: 30,
        inRange: {
            color: ['#313695', '#4575b4', '#74add1', '#abd9e9', '#e0f3f8', '#ffffbf', '#fee090', '#fdae61', '#f46d43', '#d73027', '#a50026']
        }
    },
    xAxis3D: {
        type: 'value'
    },
    yAxis3D: {
        type: 'value'
    },
    zAxis3D: {
        type: 'value'
    },
    grid3D: {
        viewControl: {
            projection: 'orthographic'
        }
    },
    series: [{
        type: 'line3D',
        data: data,
        lineStyle: {
            width: 4
        }
    }]
};

Other comments [其他信息]

求解

原因知道了，是因为数据点分布不均导致的。如果数据点分布均匀，线是不会变细甚至变成虚线的。
解决方法是在数据上做文章。如果两个数据点之间距离大于某个值（自己根据实际情况设置），就插入点（在两点之间的直线上，具体多少个自己根据实际情况设置）。

authors: sdzhihao shArpyYAo


text:
为什么升级以后 package.json 没了.

RT
是否可以加上?

如果没有的话 通过 github 地址安装 zrender 会有错误..  是否可以考虑加回来呢?

repo: ecomfe/zrender


text:
🛑 NAS is down

In 9861f47, NAS (https://ddns.ecwuuuuu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NAS is back up in e25af9f.

repo: ecwu/uptime


text:
[Feature Request] Use plugin from API definition

Hello,
Is it possible to add the ability to add a plugin directly from the API definition instead of the client definition with the use method ?
I am at a point that I need some plugins for just one endpoint and the code got splited.
Thanks

Hello Zehir,
Thank you for the suggestion, unfortunately that is not possible.
Zodios is a fullstack framework. API definition is like openapi for typescript and can be used on frontend and backend.
Adding frontend plugins to backend code would make no sense.
Zodios v11 will also be client agnostic (meaning you will be able to make axios specific plugins or fetch specific plugins) so adding plugins to zodios api definition will make even less sense.

ok I see thanks

authors: Zehir ecyrbe

repo: ecyrbe/zodios


text:
Use of interfaces

Does the library support using an interface type within a class? Say my class User has a property "animal" of type Animal, which is an interface? I didnt figure out how I can do that. It seems like I cannot use @JsonType(Animal)

The issue is that interfaces aren't a thing in Javascript - Typescript is compiled by using type erasure so all interfaces get deleted. Since they don't exist in Javascript, ta-json isn't able to use them when casting, as they're no longer there - which is why you need to use classes for everything. Hope that makes sense!

Oh ok. Thank you very much.

authors: edcarroll mustafaekim

repo: edcarroll/ta-json

license: mit


text:
Small typo

In your recent update you have
I don't work on this integration sins my inverter died, can't test changes, sorry.
It should be
I don't work on this integration since my inverter died, can't test changes, sorry.

Thank you :)

authors: eddso ziogref


text:
Problem on IL

Request-ID: 86bff519-211e-4dbc-8e8c-49ed9064090c#113091
In order to see all logs with this request-id, run:
gcloud logging read 'jsonPayload.request_id="86bff519-211e-4dbc-8e8c-49ed9064090c#113091"' --format json --project ehealth-production

From logs (provided by @AlexKovalevych):
** (MatchError) no match of right hand side value: {:error, %{"error" => %{"invalid" => [%{"entry" => "$.client_id", "entry_type" => "json_data_property", "rules" => [%{"description" => "is invalid", "params" => ["Elixir.Ecto.UUID"], "rule" => "cast"}]}], "message" => "Validation failed. You can find validators description at our API Manifest: http://docs.apimanifest.apiary.io/#introduction/interacting-with-api/errors.", "type" => "validation_failed"}, "meta" => %{"code" => 422, "request_id" => "sih6uikuj2lsnpv6jb0d9l5m8utgbqm6", "type" => "object", "url" => "http://api-svc.mithril/admin/users/4fedb53e-32ab-4af5-9027-316e8803697f/roles"}}}
    (ehealth) lib/ehealth/web/controllers/user_role_controller.ex:11: EHealth.Web.UserRoleController.index/2
    (ehealth) lib/ehealth/web/controllers/user_role_controller.ex:1: EHealth.Web.UserRoleController.action/2
    (ehealth) lib/ehealth/web/controllers/user_role_controller.ex:1: EHealth.Web.UserRoleController.phoenix_controller_pipeline/2
    (ehealth) lib/ehealth/endpoint.ex:1: EHealth.Web.Endpoint.instrument/4
    (phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
    (ehealth) lib/plug/error_handler.ex:64: EHealthWeb.Router.call/2
    (ehealth) lib/ehealth/endpoint.ex:1: EHealth.Web.Endpoint.plug_builder_call/2
    (ehealth) lib/ehealth/endpoint.ex:1: EHealth.Web.Endpoint.call/2

Closing this one. We haven't seen the issue for a while. We'll continue to monitor, and will re-open if this re-appears.

delivered o prod

authors: gmile lymychp


text:
Error 505 when InitOTPVerification method is called, #J400, Prod

виклик InitOTPVerification
в декларації телефон у дитини зазначений той самий, що і в раніше укладеній декларації у його батьків
подробиці тут https://drive.google.com/drive/u/1/folders/1KQGO6yj59uexprWg53Y2VkcW_NALvddD?ogsrc=32

won't fix

authors: ehealthua-tech svetavedmed


text:
Google Plus is wrong

New style G is needed - see https://play.google.com/store/apps/details?id=com.google.android.apps.plus
Not that anyone uses it.

Why is there no ziiiiiiing GitHub Reaction icon yet?
(This should make the SVG way smaller too, since the new shape is so much less complex.)

I saved a few bytes by making the "+" two overlapping rects (saves the four concave corners)...
Mostly just sour that you managed to push this so quick while I was still working on mine! :)

If it's smaller - please raise a PR :-)

repo: edent/SuperTinySocialIcons


text:
Modify support-notifications tests to reflect Return New Notification ID Instead of Slug

https://github.com/edgexfoundry/edgex-go/issues/1329 updated core but not blackbox tests.

fixed by #225

repo: edgexfoundry/blackbox-testing


text:
Device not register in edgex metadata after auto-discovery setup and console error.

🐞 Bug Report
Rest API use to check device list.
curl -X GET http://localhost:59881/api/v2/device/all | jq .
EdgeX Version [REQUIRED]:
latest- from main branch, edgex-compose repo. V2.
Anything else relevant?
after some time ERROR logs in console -
level=INFO ts=2022-07-26T21:04:49.897574986Z app=device-usb-camera source=async.go:104 msg="Adding discovered device UVC_Camera_(046d_0825)-61C0AE50 to Metadata"
level=ERROR ts=2022-07-26T21:04:49.901876666Z app=device-usb-camera source=async.go:120 msg="failed to create discovered device UVC_Camera_(046d_0825)-61C0AE50: request failed, status code: 400, err: {"apiVersion":"v2","message":"AddDeviceRequest.Device.Name field only allows unreserved characters which are ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_~","statusCode":400}\n"
level=DEBUG ts=2022-07-26T21:04:49.902006461Z app=device-usb-camera source=async.go:127 msg="Filtered device addition finished"

Auto-discovery setup, services are up through Edgex Latest main branch(non secure mode). Device is discovered but not showing the device list through edgex command, and not in metadata device profile.

The device name UVC_Camera_(046d_0825)-61C0AE50 has the ( and ) characters which are not valid for device names.

Look like the code here needs to include the open/close parenthesis
https://github.com/edgexfoundry/device-usb-camera/blob/fa6315a9dc6abe5875e1ce461ca165c4afc43fa4/internal/driver/device.go#L90-L93
device.go
func buildDeviceName(cardName, serialNumber string) string {
cardName = strings.ReplaceAll(strings.ReplaceAll(cardName, " ", ""), ":", "")
serialNumber = strings.ReplaceAll(strings.ReplaceAll(serialNumber, ":", ""), ".", "")
return fmt.Sprintf("%s-%s", cardName, serialNumber)
https://github.com/[edgexfoundry/device-usb-camera](https://github.com/edgexfoundry/device-usb-camera)|edgexfoundry/device-usb-cameraedgexfoundry/device-usb-camera | Added by GitHub

authors: lenny-intel surajitx-pal

repo: edgexfoundry/device-usb-camera


text:
Add dockerfile to build snap

This provides a simple Dockerfile (and script which builds the docker image) that is to be used by CI to build the snap. This removes the need to build the snap on Ubuntu 16.04, and the build for the snap may be run on any OS that runs docker.
To test, clone this branch and just run:
snap/build.sh

After a while you should see output similar to this:
[[ lots of other log output ]]
Staging mongo-config
Staging mongodb
Priming config-common
Priming go
Priming consul
Priming curl
Priming glide
Priming edgex-go
Priming mongo-config
Priming mongodb
Determining the version from the project repo (version-script).
The version has been set to '0.5.2-20180917+11f7d4b'
Snapping 'edgexfoundry' ...

Snapped edgexfoundry_0.5.2-20180917+11f7d4b_amd64.snap

The build is currently entirely done inside the container, and whether or not to do the release is determined by a few Jenkins specific environment variables, i.e. JENKINS_URL and JOB_NAME. If JENKINS_URL exists, then we copy the snap store login file into the container. Then we check if the JOB_NAME matches a stage job, and if it does then set a environment variable so the entrypoint script will attempt to release the snap on the specified snap channel.
See the associated ci-management job: https://github.com/edgexfoundry/ci-management/pull/211
This fixes #557

@anonymouse64 I didn't think of this before, but we will need a docker image that is both x86 and ARM compatible.

Hmm, you are right, and the snapcore/snapcraft image is only published for amd64. I will ask and see if there are plans to support additional architectures for the image, if not it's not too hard for us to roll our own.

@JPWKU one thing I would like for you to take a particular look at is how the snap store login file is handled here. I need to copy it into the git root for it to be accessible during the build process for the container image. After the image is built I delete this file, and then after the container has finished running the job I delete the image locally so it doesn't persist. Let me know if this is sufficiently secure handling of the login file, because that file effectively gives full control over any snaps that the edgexfoundry account has access to.

Also, I just spoke with @tonyespy about this, but I think this is simple enough that we can backport this change to california builds so that we have a snap that works on arm64 for california as well.
If we agree that's what we want to do, then after this has been merged to master I will open another PR to california.
If however we decide not to do this for california I will need to go back to the ci-management PR and undo my changes to the california jobs

This looks generally good too.  I think we can copy from $HOME, but the container doesn't know what it is, so we will have to pass it in as a docker arg.

I don't think we can copy from $HOME when building, at least it didn't work when I tried it locally. The docs have this to say about it:

Note: docker build will return a no such file or directory error if the file or directory does not exist in the uploaded context. This may happen if there is no context, or if you specify a file that is elsewhere on the Host system. The context is limited to the current directory (and its children) for security reasons, and to ensure repeatable builds on remote Docker hosts. This is also the reason why ADD ../file will not work.

(from the NOTE blurb under this section: https://docs.docker.com/engine/reference/commandline/build/#specify-a-dockerfile--f )

@anonymouse64 Ah that makes sense
We use config files in other places as well; we just have to be careful about not setting a verbose flag or cat'ing the file.

@JPWKU what are your thoughts on adapting the california jobs for this?

@anonymouse64 I suppose since it is not an edgex-go feature, then it would be ok to port to cali.  I'd like to get others thoughts as well though.

@JPWKU I agree, it is a bit of a chicken/egg problem with the arm snap verify job, as the snap will never successfully build natively on anything other than Ubuntu 16.04, and it is currently running a modified version of 17.10 IIRC.
One thing we could try is that I could revisit my ci-management PR and change it so that only the x86 builds are run on docker for now, merge that and if it succeeds then go back and open another ci-management PR enabled docker builds on x86. Or we could do the other way around, trying arm first and then doing x86.

recheck

recheck

Looking as these verify's complete.  We may force merge one if it fails on ARM like I think it will.

repo: edgexfoundry/edgex-go


text:
Add initial Xiaomi Mi Max 3 (nitrogen) support

Description
Initial support for nitrogen.
eMMC works only in UEFI and UEFI Shell, Windows PE boots with no access to eMMC. Buttons, USB and touch do not work.
Checklist

[x] Have you tested the change you are submitting?
[x] Is the commits history nice and clean?

Windows PE boots with no access to eMMC

Just a crazy idea... maybe dwcsdhc driver could be reused here, which was added for Rockchip's eMMC.

authors: AistopGit binarymaster


text:
error when start on window 10

hi team:
When I start on windows 10, I got below error. any clue I can fix? thanks a lot
2019-03-21 22:16:55.167 INFO 11084 --- [ main] org.quartz.core.QuartzScheduler : Scheduler schedulerFactoryBean_$NON_CLUSTERED started.
2019-03-21 22:16:55.386 ERROR 11084 --- [ main] e.davinci.runner.CustomDataSourceRunner : Cannot construct instance of edp.core.model.CustomDataSource (although at least one Creator exists): no String-argument constructor/factory method to deserialize from String value ('com.mysql.jdbc.Driver')
at [Source: UNKNOWN; line: -1, column: -1]
2019-03-21 22:16:55.402 INFO 11084 --- [ main] org.quartz.core.QuartzScheduler : Scheduler schedulerFactoryBean$NON_CLUSTERED paused.
2019-03-21 22:16:55.474 INFO 11084 --- [ main] org.quartz.core.QuartzScheduler : Scheduler schedulerFactoryBean$NON_CLUSTERED shutting down.
2019-03-21 22:16:55.478 INFO 11084 --- [ main] org.quartz.core.QuartzScheduler : Scheduler schedulerFactoryBean$NON_CLUSTERED paused.
2019-03-21 22:16:55.481 INFO 11084 --- [ main] org.quartz.core.QuartzScheduler : Scheduler schedulerFactoryBean$_NON_CLUSTERED shutdown complete.
2019-03-21 22:16:55.502 INFO 11084 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} closed
2019-03-21 22:16:55.590 INFO 11084 --- [ main] e.davinci.runner.CustomDataSourceRunner : Server shutdown
2019-03-21 22:16:55.603 INFO 11084 --- [ main] e.davinci.runner.CustomDataSourceRunner : Load custom datasource finish
2019-03-21 22:16:55.683 ERROR 11084 --- [ main] edp.davinci.runner.CronJobRunner : nested exception is org.apache.ibatis.exceptions.PersistenceException:
Error querying database. Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is com.alibaba.druid.pool.DataSourceClosedException: dataSource already closed at Thu Mar 21 22:16:55 CST 2019
The error may exist in edp/davinci/dao/CronJobMapper.java (best guess)
The error may involve edp.davinci.dao.CronJobMapper.getStartedJobs
The error occurred while executing a query
Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is com.alibaba.druid.pool.DataSourceClosedException: dataSource already closed at Thu Mar 21 22:16:55 CST 2019
2019-03-21 22:16:55.684 INFO 11084 --- [ main] edp.davinci.runner.CronJobRunner : Load cron job finish
Here is my datasource_driver.yml. Could you lease help to let me know any clue?
mysql:
name: mysql
desc: mysql
driver: com.mysql.jdbc.Driver
keyword_prefix:
keyword_suffix:
alias_prefix:
alias_suffix:

i also have wrong
server:
protocol: http
address: 127.0.0.1
port: 8080
phantomjs_home: E:\phantomjs-2.1.1-windows\bin\phantomjs.exe   #/usr/local/bin/phantomjs

@JiaNan-168
Hello, I have the same problem
① when I make an address with 127.0.0.1 , the DavinciAppliciatoin will be running, but I can't connect with my chrome.
② when I make address with my real IP , there will be wrong like this

2019-12-26 11:02:34.427 ERROR 10656 --- [main] o.apache.catalina.core.StandardService   : Failed to start connector [Connector[HTTP/1.1-8090]]
org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-8090]]
please hellp me

https://edp963.github.io/davinci/docs/zh/1.1-deployment#241-server-配置


text:
🛑 Portal-DGE is down

In d6e70fe, Portal-DGE (https://www.mendoza.edu.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal-DGE is back up in e1f7e4f after 13 minutes.

repo: edu-red/DGE-GOV


text:
Create Oi

Oi edurdo

Opa Cristovão (pelo nome da conta assumo q é tu) blz? Fico feliz q tu sabe faze uma Pull Request. Se quiser implementar qualquer coisa no projeto pode fazer que eu aceito merge aqui. Se preferir também eu te incluo como contribuidor pra você colocar direto na main.


text:
Document the need to add HTTPoison to mix dependencies.

Add documentation in README for including HTTPoison to the deps list.

Thanks!

authors: edubkendo psfblair

repo: edubkendo/datomex


text:
screenshot

There's no screenshot in the readme


text:
Class fxlauncher/Launcher not found

Hello, when I try to install program on another system , after installation it throws this error

How to fix that?
My pom.xml
`

4.0.0
<groupId>MyProject</groupId>
<artifactId>MyProject</artifactId>
<version>1.0</version>

<build>
    <plugins>
        <!-- Compile project jar to appdir -->
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-jar-plugin</artifactId>
            <version>3.1.2</version>
            <configuration>
                <outputDirectory>${app.dir}</outputDirectory>
            </configuration>
        </plugin>
        <!-- Copy dependencies to appdir -->
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-dependency-plugin</artifactId>
            <version>3.1.1</version>
            <configuration>
                <excludeScope>provided</excludeScope>
                <outputDirectory>${app.dir}</outputDirectory>
                <stripVersion>true</stripVersion>
            </configuration>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>copy-dependencies</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
        <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>exec-maven-plugin</artifactId>
            <version>1.6.0</version>
            <!-- Generate app.xml manifest -->
            <executions>
                <execution>
                    <id>create-manifest</id>
                    <phase>package</phase>
                    <goals>
                        <goal>java</goal>
                    </goals>
                    <configuration>
                        <mainClass>fxlauncher.CreateManifest</mainClass>
                        <arguments>
                            <argument>${app.url}</argument>
                            <argument>${app.mainClass}</argument>
                            <argument>${app.dir}</argument>
                            <!--<argument>--cache-dir=${app.cacheDir}</argument>-->
                            <argument>--accept-downgrade=${app.acceptDowngrade}</argument>
                            <argument>--include-extensions=jpg</argument>
                            <!--<argument>${app.parameters}</argument>-->
                        </arguments>
                    </configuration>
                </execution>
                <!-- Embed app.xml inside fxlauncher.xml so we don't need to reference app.xml to start the app -->
                <execution>
                    <id>embed-manifest-in-launcher</id>
                    <phase>package</phase>
                    <goals>
                        <goal>exec</goal>
                    </goals>
                    <configuration>
                        <executable>jar</executable>
                        <workingDirectory>${app.dir}</workingDirectory>
                        <arguments>
                            <argument>uf</argument>
                            <argument>fxlauncher.jar</argument>
                            <argument>app.xml</argument>
                        </arguments>
                    </configuration>
                </execution>
                <!-- Optional step to include custom UI, see https://github.com/edvin/fxlauncher-custom-ui -->
                <execution>
                    <id>embed-custom-ui-in-launcher</id>
                    <phase>package</phase>
                    <goals>
                        <goal>exec</goal>
                    </goals>
                    <configuration>
                        <executable>jar</executable>
                        <workingDirectory>${app.dir}</workingDirectory>
                        <arguments>
                            <argument>uf</argument>
                            <argument>fxlauncher.jar</argument>
                            <argument>-C</argument>
                            <argument>C:/Users/Xiaomi/Desktop/fxlauncher-custom-ui-master/target/classes</argument>
                            <argument>.</argument>
                        </arguments>
                    </configuration>
                </execution>
                 <!--Create native installer. Feel free to add more arguments as needed.-->
                 <!--https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javapackager.html-->

                <execution>
                    <id>installer</id>
                    <phase>install</phase>
                    <goals>
                        <goal>exec</goal>
                    </goals>
                    <configuration>
                        <executable>javapackager</executable>

                        <arguments>
                            <argument>-deploy</argument>
                            <argument>-native</argument>
                            <argument>-outdir</argument>
                            <argument>${app.installerdir}</argument>
                            <argument>-outfile</argument>
                            <argument>${app.filename}</argument>
                            <argument>-srcdir</argument>
                            <argument>${app.dir}</argument>
                            <argument>-srcfiles</argument>
                            <argument>fxlauncher.jar</argument>
                            <argument>-appclass</argument>
                            <argument>fxlauncher.Launcher</argument>
                            <argument>-name</argument>
                            <argument>${project.name}</argument>
                            <argument>-title</argument>
                            <argument>${project.name}</argument>
                            <argument>-vendor</argument>
                            <argument>IzzyBot</argument>
                            <argument>-BappVersion=${app.version}</argument>
                            <argument>-Bidentifier=${project.groupId}.${project.artifactId}</argument>
                        </arguments>
                    </configuration>
                </execution>
                <!-- Copy application artifacts to remote site using scp (optional) -->
                <execution>
                    <id>deploy-app</id>
                    <goals>
                        <goal>exec</goal>
                    </goals>
                    <configuration>
                        <executable>scp</executable>
                        <arguments>
                            <argument>-r</argument>
                            <argument>target/app/.</argument>
                            <argument>${app.deploy.target}</argument>
                        </arguments>
                    </configuration>
                </execution>
            </executions>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.8.0</version>
            <configuration>
                <source>1.8</source>
                <target>1.8</target>
            </configuration>
        </plugin>

    </plugins>
</build>

<properties>
    <!-- Installer Filename without suffix -->
    <app.filename>IzzyBot</app.filename>

    <!-- The JavaFX Application class name -->
    <app.mainClass>controllers.Main</app.mainClass>

    <!-- Optional override to specify where the cached files are stored. Default is current working directory -->
    <!--<app.cacheDir>USERLIB/FxlDemo</app.cacheDir>-->

    <!-- Optional parameters to the application, will be embedded in the launcher and can be overriden on the command line -->
    <!--<app.parameters>--myOption=myValue --myOtherOption=myOtherValue</app.parameters>-->

    <!-- The Application vendor used by javapackager -->
    <app.vendor>IzzyBot</app.vendor>

    <!-- The Application version used by javapackager -->
    <app.version>1.0</app.version>

    <!-- Base URL where you will host the application artifacts -->
    <app.url>http://lab4.std-763.ist.mospolytech.ru/getdown/</app.url>

    <!-- Optional scp target for application artifacts hosted at the above url -->
    <app.deploy.target>http://lab4.std-763.ist.mospolytech.ru/getdown/</app.deploy.target>

    <!-- The app and launcher will be assembled in this folder -->
    <app.dir>${project.build.directory}/app</app.dir>

    <!-- Native installers will be built in this folder -->
    <app.installerdir>${project.build.directory}/installer</app.installerdir>

    <!-- Should the client downgrade if the server version is older than the local version? -->
    <app.acceptDowngrade>false</app.acceptDowngrade>

    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependencies>
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>4.0.0-alpha-1</version>
    </dependency>
    <dependency>
        <groupId>com.google.code.gson</groupId>
        <artifactId>gson</artifactId>
        <version>2.8.5</version>
    </dependency>
    <dependency>
        <groupId>com.jfoenix</groupId>
        <artifactId>jfoenix</artifactId>
        <version>8.0.1</version>
    </dependency>
    <dependency>
        <groupId>org.jetbrains</groupId>
        <artifactId>annotations</artifactId>
        <version>RELEASE</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-htmlunit-driver</artifactId>
        <version>2.52.0</version>
    </dependency>

    <dependency>
        <groupId>no.tornado</groupId>
        <artifactId>fxlauncher</artifactId>
        <version>1.0.21</version>
    </dependency>
    <dependency>
        <groupId>org.controlsfx</groupId>
        <artifactId>controlsfx</artifactId>
        <version>8.40.11</version>
    </dependency>

</dependencies>

`

I was able to verify that from fxlauncher.jar and up, everything is in order. As you can see from the attached screenshot, your app ran perfectly and I got both the custom launcher ui and the login screen, no problem. Nice work!
I suspect there might be an issue with your executable. Can you perhaps post either the executable itself or the command and output used to build it?

for build i use mvn install command , it builds me exe installer from javafxpackager
there is my exe
https://drive.google.com/open?id=1BeXaumhz_XSVBrN_5X48oKu1azGJlnfM
this output of install command [INFO] --- maven-install-plugin:2.4:install (default-install) @ IzzyBot --- [INFO] Installing C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\app\IzzyBot-1.0.jar to C:\Users\Xiaomi\.m2\repository\IzzyBot\IzzyBot\1.0\IzzyBot-1.0.jar [INFO] Installing C:\Users\Xiaomi\Downloads\SupremeDesignv2\pom.xml to C:\Users\Xiaomi\.m2\repository\IzzyBot\IzzyBot\1.0\IzzyBot-1.0.pom [INFO] [INFO] --- exec-maven-plugin:1.6.0:exec (installer) @ IzzyBot --- No base JDK. Package will use system JRE. No base JDK. Package will use system JRE. Creating app bundle: IzzyBot in C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Result application bundle: C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Installer (.exe) saved to: C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Bundler MSI Installer skipped because of a configuration problem: Can not find WiX tools (light.exe, candle.exe). Advice to fix:   Download WiX 3.0 or later from http://wix.sf.net and add it to the PATH. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time:  02:45 min [INFO] Finished at: 2019-08-19T16:49:32+03:00 [INFO] ------------------------------------------------------------------------ [INFO] --- maven-install-plugin:2.4:install (default-install) @ IzzyBot --- [INFO] Installing C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\app\IzzyBot-1.0.jar to C:\Users\Xiaomi\.m2\repository\IzzyBot\IzzyBot\1.0\IzzyBot-1.0.jar [INFO] Installing C:\Users\Xiaomi\Downloads\SupremeDesignv2\pom.xml to C:\Users\Xiaomi\.m2\repository\IzzyBot\IzzyBot\1.0\IzzyBot-1.0.pom [INFO] [INFO] --- exec-maven-plugin:1.6.0:exec (installer) @ IzzyBot --- No base JDK. Package will use system JRE. No base JDK. Package will use system JRE. Creating app bundle: IzzyBot in C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Result application bundle: C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Installer (.exe) saved to: C:\Users\Xiaomi\Downloads\SupremeDesignv2\target\installer\bundles Bundler MSI Installer skipped because of a configuration problem: Can not find WiX tools (light.exe, candle.exe). Advice to fix:   Download WiX 3.0 or later from http://wix.sf.net and add it to the PATH. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time:  02:45 min [INFO] Finished at: 2019-08-19T16:49:32+03:00 [INFO] ------------------------------------------------------------------------

Even the installer is working perfectly for me. Can you verify that C:\Users\Xiaomi\AppData\Local\IzzyBot\app contains all the app jars, including fxlauncher.jar, on the system where it fails? Replace Xiaomi with the current username on the relevant system of course :)

Yes, I check that app folder contains fxlauncher.jar , also i find that this error throws on new windows user or on clean windows

I don't have any good ideas why this would fail though, everything seems to be in order. You could also try to run java -jar fxlauncher.jar from the app folder to verify that all files have been downloaded intact.

I found solution, reason of this error was cyrillic symbols in installation path

Ah! Thanks for reporting back :)

authors: XUYVSMETANE edvin

repo: edvin/fxlauncher


text:
[Bug]: Trait method 'activities' will not be applied because it collides with 'LogsActivity'

What happened?
Trait method 'activities' will not be applied because it collides with 'LogsActivity' when adding the trait to user model
How to reproduce the bug
add the trait to user model
Package Version
2
PHP Version
8.2
Laravel Version
10
Which operating systems does with happen with?
macOS
Notes
https://github.com/edwink75/filament-user-activity/issues

Can you give me a little more details about the conflicting plugin you're using? And more details about the error?

z3d0x/filament-logger

Thanks for reporting. I added the package to the conflict section of composer.

Added to composer


text:
Show or hide handouts tab depending if its available or not

Description
OSPR-1609
This PR shows or hide the handouts tab depending if its available or not.
Reviewers

[ ] Code review: @danialzahid94
[ ] Code review: @saeedbashir

Thanks for the pull request, @jagonzalr! I've created OSPR-1609 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.
If you like, you can add yourself to the AUTHORS      file for this repo, though that isn't required.     Please see the CONTRIBUTING     file for more information.

@jagonzalr Thanks for your PR. I've pinged product and UX to see if this is what we want. Stay tuned.

Sweet. No configuration necessary, just: show if available / not empty, is that correct @jagonzalr ?
👍  from a product standpoint. on to engineering review queue.

@marcotuts yes

Current coverage is 22.94% (diff: 50.00%)

Merging #869 into master will increase coverage by 0.03%

@@             master       #869   diff @@
==========================================
  Files           675        675
  Lines         56269      56342    +73
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          12888      12925    +37
- Misses        43381      43417    +36
  Partials          0          0

Powered by Codecov. Last update 09bfc19...a030b6e

I believe we should be able to add a test for this
https://github.com/edx/edx-app-ios/blob/master/Test/CourseDashboardViewControllerTests.swift

If hiding the handouts is the default behaviour, we can also remove the fullscreen error logic for the handouts screen.

@BenjiLee the what?

My last comment was dependent on if the course_handout's value could be null or not.
I'm not sure if course_handouts: null or "". Originally, I thought the intention of this PR was to remove handouts if the URL returned let to an empty handouts page.

@BenjiLee no, it just checks the handouts url, so if its null or "" I just don't show it.

Ah, I found the code. https://github.com/edx/edx-platform/blob/master/lms/djangoapps/mobile_api/course_info/views.py#L84
It is possible to have a null link. I couldn't remember if we always automatically generated the code and then handled empty handouts on the mobile side or not.

Just the pending comment on adding a snapshot test. https://github.com/edx/edx-app-ios/blob/master/Test/CourseDashboardViewControllerTests.swift

@BenjiLee added the test

authors: BenjiLee codecov-io edx-webhook jagonzalr marcotuts

repo: edx/edx-app-ios


text:
Pretty print

Disclaimer: I haven't actually tried this, but look reasonable in principle? 😅

solving this in a different way


text:
cugr doesn't support inout ports

This was noticed in issue https://github.com/efabless/openlane/issues/167
[   0.006] ------------------------------------------------------------------------------
[   0.015]                      ICCAD 2019 - Global Routing Contest
[   0.015]                              Team number : 15
[   0.015]                              Team name : CU-GR
[   0.015]         Members: Jinwei Liu, Chak-Wa Pui, Fangzhou Wang,
[   0.015]                  Evangeline F.Y. Young
[   0.015]         Affiliation: The Chinese University of Hong Kong
[   0.015] ------------------------------------------------------------------------------
[   0.021] Input .lef file   : /openLANE_flow/designs/icache/runs/24-01_19-07/tmp/merged_unpadded.lef
[   0.021] Input .def file.  : /openLANE_flow/designs/icache/runs/24-01_19-07/tmp/routing/23-addspacers.obs.def
[   0.021] # of threads      : 32
[   0.021] Output file name  : /openLANE_flow/designs/icache/runs/24-01_19-07/tmp/routing/24-fastroute.guide
[   0.021]
terminate called after throwing an instance of 'Rsyn::Exception'
  what():  Only in and out direction are supported right now.

Just bringing those in here:

multiply_4.tar.gz
merged_unpadded.lef.gz
17-addspacers.obs.def.gz

Just bringing those in here:

multiply_4.tar.gz
merged_unpadded.lef.gz
17-addspacers.obs.def.gz

repo: efabless/openlane


text:
🛑 Almacén BioPandora is down

In 454ccbb, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in 3fed2d7 after 39 minutes.

repo: efecear/upptime


text:
🛑 Almacén BioPandora is down

In 38fb33f, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in 4698d45 after 1 hour, 42 minutes.


text:
🛑 Tierra Firme is down

In 80d7b06, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in f417def.


text:
🛑 Nodo UTT Morón is down

In b81c2c2, Nodo UTT Morón (https://www.nodouttmoron.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Morón is back up in a0165b4.


text:
🛑 Nodo UTT Ramos Mejia is down

In 4b00e1d, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 9d6f436.


text:
monitoring: Add option to disable cadvisor

Cadvisor is important to get container metrics. However, it requires various directories, which might be different on different OS-es causing it to fail. For example when using WSL (https://github.com/google/cadvisor/issues/2648#issuecomment-1049215354).
Without cadvisor we still can have a lot of metrics from runtimes running in containers (e.g Go app), so we can add option to disable cadvisor so users can be unblocked if they can't make cadvisor running.

Done: https://github.com/efficientgo/e2e/pull/56