Error starting up the add-on after recent 1.5.1 update

zigbee2mqtt add-on version (if edge, please report commit hash): 1.5.1
Operating environment (HassOS, Virtual Machine, Device/platform running Hass.io):

Running HassIO v0.95.4 on a Ubuntu 18.04.2 LTS VM.
Description of problem:
Error starting up the addon with error TypeError: net.precfgkey should be an array with 16 uint8 integers. This configuration used to work before the update to 1.5.1. The json data below was also tweaked to support the new format (with nested objects instead of one flat json).
Note - I have not added devices yet (since I've recreated my VM recently and haven't gotten around to doing so).
Your entire configuration from the frontend (with sensitive fields redacted):
{
  "data_path": "/share/zigbee2mqtt",
  "devices": "[]",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://<IP_ADDRESS>:1883",
    "user": "~REDACTED~",
    "password": "~REDACTED~"
  },
  "serial": {
    "port": "/dev/ttyACM0"
  },
  "advanced": {
    "pan_id": "~REDACTED MAYBE?~",
    "channel": 11,
    "network_key": []
  }
}

Your logs from Hass.io
./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-20T18:35:43: PM2 log: Launching in no daemon mode
2019-07-20T18:35:43: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T18:35:43: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/20/2019, 6:35:44 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.18-35-44'
  zigbee2mqtt:info 7/20/2019, 6:35:45 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 6:35:45 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
                    throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
                    ^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
    at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
    at Object._.forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
    at Object._.forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
    at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
    at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
    at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
    at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
    at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
    at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
    at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
 ERR! code ELIFECYCLE
npm ERR! errno
 1
npm
 ERR<EMAIL_ADDRESS>start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-20T22_35_45_028Z-debug.log
2019-07-20T18:35:49: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T18:35:49: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T18:35:49: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.18-35-49'
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
                    throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
                    ^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
    at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
    at Object._.forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
    at Object._.forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
    at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
    at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
    at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
    at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
    at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
    at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
    at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
 ERR! code ELIFECYCLE
npm ERR!
errno 1
npm
ERR<EMAIL_ADDRESS>start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

It's difficult to get the logs from /share/zigbee2mqtt/log/2019-07-20.18-35-44 since they keep getting deleted while the add-on is enabled, and file is empty when the add-on is disabled.

I'm just setting up zigbee2mqtt.
Have more or less exactly the same problem and try to solve it now.
Hass.io on a VM: 96.2

zigbee2mqtt:info 7/21/2019, 12:52:55 AM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
ERR! code ELIFECYCLE
npm ERR!
errno 1
npm
ERR<EMAIL_ADDRESS>start: node index.js
npm ERR!
Exit status 1
npm ERR!
npm
ERR!
Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-20T22_52_55_727Z-debug.log
2019-07-21T00:52:59: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-21T00:52:59: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T00:52:59: PM2 log: App [npm:0] online
<EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
node index.js
zigbee2mqtt:info

I have the same issue
`><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1

node index.js
zigbee2mqtt:info 7/21/2019, 1:33:44 AM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.01-33-43'
zigbee2mqtt:info 7/21/2019, 1:33:44 AM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
zigbee2mqtt:info 7/21/2019, 1:33:44 AM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm ERR!
code ELIFECYCLE
npm ERR! errno 1
npm
ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-20T23_33_44_835Z-debug.log
2019-07-21T01:33:45: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-21T01:33:45: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T01:33:45: PM2 log: App [npm:0] online`

Same issue.  Log below.  Tried to roll back to an earlier version from a snapshot but still getting the same errors:
'''

node index.js
zigbee2mqtt:info 7/20/2019, 8:33:49 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.20-33-48'
zigbee2mqtt:info 7/20/2019, 8:33:49 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
zigbee2mqtt:info 7/20/2019, 8:33:50 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
ERR! code ELIFECYCLE
npm ERR! errno 1
npm
ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/logs/2019-07-21T00_33_50_079Z-debug.log
2019-07-20T20:33:54: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T20:33:54: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T20:33:54: PM2 log: App [npm:0] online
<EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
node index.js
zigbee2mqtt:info 7/20/2019, 8:34:00 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.20-33-59'
zigbee2mqtt:info 7/20/2019, 8:34:00 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
zigbee2mqtt:info 7/20/2019, 8:34:00 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/logs/2019-07-21T00_34_01_042Z-debug.log
2019-07-20T20:34:05: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T20:34:05: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T20:34:06: PM2 log: App [npm:0] online
<EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
node index.js
zigbee2mqtt:info 7/20/2019, 8:34:11 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.20-34-10'
zigbee2mqtt:info 7/20/2019, 8:34:11 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
zigbee2mqtt:info 7/20/2019, 8:34:11 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
ERR! code ELIFECYCLE
npm ERR! errno
1
npm ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm
ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-21T00_34_12_068Z-debug.log
2019-07-20T20:34:16: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T20:34:16: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T20:34:17: PM2 log: App [npm:0] online
<EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
node index.js
'''

Same issue here.

I've discovered the reason; 1.5.1 looks to be insistent on using a network_key.
Follow here to generate a key and apply the setting:
http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html
FYI, I did not have to re-pair devices.

I also have the above error

I also have same errors pair again all things?

The fix is to add a network_key and re-pair all devices.

Can any random 16 digit number be used? I've added a network_key but zigbee2shepherd still will not start.

Please follow this link:
http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html

I did with the exception of generating a key.  That is why I am asking if a random key can be used or if one has to be generated using the below which isn't the easy on hassio.
dd if=/dev/urandom bs=1 count=16 2>/dev/null | od -A n -t x1 | awk '{printf "["} {for(i = 1; i< NF; i++) {printf "0x%s, ", $i}} {printf "0x%s]\n", $NF}'

As long as you use 16 numbers between 0-255, you should be good. Yes it can be random.

Please follow this link:
http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html

I recovered thx for your guide

@danielwelch Maybe an smart idea to state this also in the component... as stated by messages above people need to repair all their devices, not a fun thing to do when you have a lot of them so i think it's an good idea to warn people about it.

I use Hass.io and add-on. I have the same issue and I look into the configuration document. It indicates that network_key is optional but when I remove the network_key:[], I can't save the config.

@krishuang92 you have to add 16 decimal numbers within the array to get it working. Something like:
network_key:[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16]
It took me 3 hours to get most of my stuff running again this morning as I had to re-connect every ducking lamp in the house. This was not cool!

Do someone bows if the network key can be disabled? I don’t need it and I don’t wanna pair again all my devices

Do someone knows if the network key can be disabled? I don’t need it and I don’t wanna pair again all my devices

You use default one here: https://github.com/Koenkk/zigbee2mqtt/blob/ac3b924065c6f2b9dd7433a6f193d1924b34bb7d/lib/util/settings.js#L88

This is an adapted command to generate 16 random unsigned decimal numbers since the addon doesn't accept hex values:
dd if=/dev/urandom bs=1 count=16 2>/dev/null | od -A n -t u1 | awk '{printf "["} {for(i = 1; i< NF; i++) {printf "%s, ", $i}} {printf "%s]\n", $NF}'

@dzungpv are you saying if users affected by this problem just insert
network_key: [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13],
then things will start working again? Cheers

@dzungpv tanks! I confirm that using default network key it starts working again !

@lancelon you download file .configuration.yaml.bk (configuration.yaml)to your computer, update to 1.5.1, after update just stop it, press "RESET TO DEFAULT" to get right config, after that just replace you information from old config file like mqtt info, port, channel and use the key above, press START, it will work just like before

instructions from @dzungpv works, thanks!
I copied the configuration info, "Reset to default", and retyped the settings from the old config. Used the default network_key: [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13].
No need to repair devices on my setup.

After also following @dzungpv and @ivanskj my Zigbee network also started working again through z2mqtt. Like @ivanskj I reset the configuration and just filled my user and password as well as the default network key. Everything worked as before right away. There has been a warning that there would be a breaking change for many weeks now, so it is not exactly a surprise that something like this was going to happen 😄 I am just grateful that others already found the simplest way to get things working again! 👍

Using default network key worked for some (Xioami) devices for me. Thanks for saving me hours of re-pairing!
Seems that my Hue bulbs didn't get the memo, however. Anyone else? Guess I'll have to reset those...

Thanks for the understanding everyone. Sorry to those that had to repair all of their devices. The purpose of the back up feature was to hopefully avoid this. I'm not sure why those who had a blank network key were suddenly required to enter it (or why the default network key became explicitly required), maybe a change within zigbee2mqtt config handling with the update.

I've also updated the top warning in the README with a reference to the backup. Should've done that from the start.

Hi,
can't get it to work with the standard network key.
Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79):<PHONE_NUMBER>21 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations.
Anyone see what's wrong?
Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder.

It took me 3 hours to get most of my stuff running again this morning as I had to re-connect every ducking lamp in the house. This was not cool!
@krishuang92 you have to add 16 decimal numbers within the array to get it working. Something like:
network_key:[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16]
Though I managed to use the default network key to start it, devices didn't come back. I already repair them but one Aqara Remote Switch (Single RockerRocker) just won't pair again. I'll try that later.

Anyway, thanks for the discussions and help.

Thanks for the understanding everyone. Sorry to those that had to repair all of their devices. The purpose of the back up feature was to hopefully avoid this. I'm not sure why those who had a blank network key were suddenly required to enter it (or why the default network key became explicitly required), maybe a change within zigbee2mqtt config handling with the update.

I had to pair 35+ devices again (i was already re-pairing everything when the "default network key solution" came up)but that's always a risk you have to keep in mind when u use a piece of software like this so i would say, no need to feel sorry!
After a few hours work everything works flawlessly again. And better then before, better networkmap, smoother and everything seems to be stable.

@lancelon, .configuration.yaml.bk (configuration.yaml) dosyasını bilgisayarınıza indirin, 1.5.1'e güncelleyin, güncellemenin hemen ardından durduktan sonra, doğru yapılandırmayı elde etmek için "RESET TO DEFAULT" düğmesine basın. mqtt info, port, channel gibi eski config dosyaları ve yukarıdaki anahtarı kullanın, BAŞLAT'a basın, daha önce olduğu gibi çalışacaktır.

@dzungpv  I did exactly what you said. no problem left.I've never touched a device and it works fine..thank you so much

Adding to the discussion; as I had some custom friendly names in my device config, I needed to also restore these in the new devices.yaml. Now HA is able to also find back these devices.

Hi,
can't get it to work with the standard network key.
Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79):<PHONE_NUMBER>21 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations.
Anyone see what's wrong?
Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder.
EDIT: Got it working without re-pairing.

Can you share what did you do? I have the same problem as yours and i stuck...

Hi,
can't get it to work with the standard network key.
Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2):<PHONE_NUMBER> - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79):<PHONE_NUMBER>21 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations.
Anyone see what's wrong?
Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder.
EDIT: Got it working without re-pairing.

Can you share what did you do? I have the same problem as yours and i stuck...

Same here! I have set everything back to defaults, typed of the settings from the old configuration, and added the default network key. After restarting the Add-on the devices ( Xiaomi Sensors ) where available in HA again, but i don't get any status from any device. I am really hoping for a solution to , since i don't want to get all my sensors back in front of my Raspberry PI...

@GJ2019 probably we have to create devices.yaml, but i dont have example configuration. In previous version 1.4.0 devices where automatically added to the array of devices i just changed the friendly_name and it was all good. Now i'm not sure in the new version file is called devices**.yaml** but what file structure should we use json or yaml?! And is it mandatory to have such file at all?
I tried make configuration based on this, but with no luck:
https://www.zigbee2mqtt.io/configuration/device_specific_configuration.html

I removed the port number in mqtt server settings in the add-on, and rebooted my intel nuc, then everything worked. Try that.

Believe it or not... but <IP_ADDRESS> had just been released ? Does it fix those issues ?

@zepixer: Did you removed the port number on the mqtt link ? In the config from the Zigbee2mqtt add-on?

@GJ2019 yes, that's correct.

@zepixer : Nope...no result. Still see the devices , but status doesn’t change. For example a Xiaomi door sensor tells me that a door is open which is definitely closed. Temperature on the temperature sensors doesn’t change.

@GJ2019 ok, if you also rebooted your host computer, I don't know what you can do. I have not tried v. <IP_ADDRESS> yet.

@GJ2019 ok, if you also rebooted your host computer, I don't know what you can do. I have not tried v. <IP_ADDRESS> yet.
Maybe you can post your sensored add-on config?

Sure i can !
The config :
{   "data_path": "/share/zigbee2mqtt",   "devices": "devices.yaml",   "groups": "groups.yaml",   "homeassistant": true,   "permit_join": false,   "mqtt": {     "base_topic": "zigbee2mqtt",     "server": "mqtt://<IP_ADDRESS>:1883",     "user": "myusername",     "password": "mypassword"   },   "serial": {     "port": "/dev/ttyACM0",     "disable_led": true   },   "advanced": {     "pan_id": 6754,     "channel": 11,     "network_key": [       1,       3,       5,       7,       9,       11,       13,       15,       0,       2,       4,       6,       8,       11,       12,       13     ]   } }
The latest log from /share/zigbee2mqtt/log:
7/23/2019, 8:49:25 AM - info: Logging to directory: '/share/zigbee2mqtt/log/2019-07-23.08-49-22' 7/23/2019, 8:49:25 AM - info: Starting zigbee2mqtt version 1.5.1 (commit #unknown) 7/23/2019, 8:49:25 AM - info: Starting zigbee-shepherd 7/23/2019, 8:49:27 AM - info: zigbee-shepherd started 7/23/2019, 8:49:27 AM - info: Coordinator firmware version: '20190425' 7/23/2019, 8:49:27 AM - info: Currently 9 devices are joined: 7/23/2019, 8:49:27 AM - info: unknown (0x00158d000233bdxx): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002f2ecxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00031356xx): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00033ab6xx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00033dddxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002f2ddxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002703xxx): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d000321dxxx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0003946xxx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: Zigbee: disabling joining new devices. 7/23/2019, 8:49:27 AM - info: Connecting to MQTT server at mqtt://<IP_ADDRESS>:1883 7/23/2019, 8:49:28 AM - info: zigbee-shepherd ready 7/23/2019, 8:49:28 AM - info: Connected to MQTT server 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d000233bxxx', payload '{"battery":100,"voltage":3015,"linkquality":23,"water_leak":false}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002f2exxx', payload '{"temperature":25.12,"linkquality":60,"humidity":65.42,"pressure":1019,"battery":86,"voltage":2975}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0003135xxx', payload '{"angle":7,"linkquality":0,"angle_x":-1,"angle_y":80,"angle_z":10,"angle_x_absolute":91,"angle_y_absolute":10,"battery":100,"voltage":3015}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d00033abxxx', payload '{"contact":false,"linkquality":36,"battery":100,"voltage":3045}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d00033ddxxx', payload '{"temperature":24.36,"linkquality":0,"humidity":52.54,"pressure":1020,"battery":91,"voltage":2985}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002f2dxxx', payload '{"temperature":25.64,"linkquality":44,"humidity":60.62,"pressure":1020,"battery":97,"voltage":2995}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002703xxx', payload '{"water_leak":false,"linkquality":31,"battery":100,"voltage":3025}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d000321dxxx', payload '{"contact":true,"linkquality":44,"battery":100,"voltage":3055}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0003946xxx', payload '{"battery":100,"voltage":3105,"contact":true,"linkquality":60}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190425,"log_level":"info","permit_join":false}'

I don't know whats causing this, can only ask you to try the same things I have done.
First, delete the disable led config, save and restart mqtt add on. If not, try unplugging and plug back in your coordinator, then restart add-on. Lastly try using "mqtt://homeassistant" as server name, instead of ip adress and port number.

Thanks for the support... but nope, no result. Even did a restart of the whole PI, but no updates are pushed from the sensors to HA.
Afraid i have to re-pair all of my devices :-(

Similar problems here. After updating to <IP_ADDRESS> and fixing config, the log ends with:
zigbee2mqtt:error 7/23/2019, 7:46:03 AM Failed to mount the cieApp
And nothing after that.

For me starting the addon worked again after adding availability_blacklist to the options:
{   ....   "advanced": {     ....     "availability_blacklist": []   },   .... }

For me works to change:
"disable_led": "bool?" to "disable_led": true
you could also use false instead of true.

the next thing to do is get rid of the if the network_key starts with the number 0
change - 087 to 87
after that also the "disable_led": "bool?" Change to "disable_led": false
configuration.yaml file
advanced:
network_key:

4
087
095
106
217
15
087
244
27
177
29
107
24
203
53
174

######################
config.json file
######################
{
"data_path": "/share/zigbee2mqtt",
"devices": "devices.yaml",
"groups": "groups.yaml",
"homeassistant": true,
"permit_join": false,
"mqtt": {
"base_topic": "zigbee2mqtt",
"server": "mqtt://<IP_ADDRESS>",
"user": "username",
"password": "password"
},
"serial": {
"port": "/dev/ttyACM0",
"disable_led": false
},
"advanced": {
"network_key": [
8,
24,
80,
106,
217,
15,
45,
244,
27,
188,
77,
205,
27,
35,
187,
178
],
"availability_blacklist": []
},
"ban": [],
"whitelist": [],
"queue": {}
}

I can confirm that solutions provided by @Pjanssen and @gewoonik works for me on v.<IP_ADDRESS>.
Thanks! :)

@GJ2019 I have same issues with my xiaomi sensors. I refalsh coordinator firmware, I re pair devices,  it not works.
you solve problem?

I upgraded to <IP_ADDRESS> yesterday. I can run the addon. Except that all of my Xiaomi sensors are not giving me new record updates. Also I attempt to re-pair some devices but no feedback in the logs that this is working or that the device is trying to connect. Before I had no network_key configured in my config file, so I use the default key. Also tried all of the above given options, but for now no luck.

Got it working after I reflashed CC2531 USB stick with CC2531_DEFAULT_20190608. I was running 20190223. Re-pairing was pretty simple after that. Only caused me 2 days to solve this problem.

Hello, I have a similar problem, earlier it worked without problems, now I don't want to start properly:
My specifications are RPi3+, Home Assistant 0.96.5, System HassOS 2.12, zigbee2mqtt-armhf with version <IP_ADDRESS>.

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://<IP_ADDRESS>",
    "user": "mqqt",
    "password": "PASS"
  },
  "serial": {
    "port": "/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001936DD4F-if00"
  },
  "advanced": {
    "pan_id": 6724,
    "channel": 11,
    "network_key": [
      176,
      148,
      195,
      196,
      118,
      210,
      210,
      127,
      21,
      37,
      61,
      100,
      106,
      29,
      200,
      153
    ],
    "availability_blacklist": []
  },
  "ban": [],
  "whitelist": [],
  "queue": {}
}

[Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-08-04T01:33:33: PM2 log: Launching in no daemon mode
2019-08-04T01:33:33: PM2 log: App [npm:0] starting in -fork mode-
2019-08-04T01:33:33: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 8/4/2019, 1:33:38 AM Logging to directory: '/share/zigbee2mqtt/log/2019-08-04.01-33-36'
  zigbee2mqtt:info 8/4/2019, 1:33:38 AM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 8/4/2019, 1:33:38 AM Starting zigbee-shepherd
  zigbee2mqtt:info 8/4/2019, 1:33:50 AM Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds) (Error: request timeout)
  zigbee2mqtt:info 8/4/2019, 1:34:50 AM Starting zigbee-shepherd
  zigbee2mqtt:error 8/4/2019, 1:35:02 AM Error while starting zigbee-shepherd! (Error: request timeout)
  zigbee2mqtt:error 8/4/2019, 1:35:02 AM Press the reset button on the stick (the one closest to the USB) and start again
  zigbee2mqtt:error 8/4/2019, 1:35:02 AM Failed to start
	{"message":"request timeout","stack":"Error: request timeout\n    at CcZnp.<anonymous> (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/cc-znp/index.js:208:22)\n    at Object.onceWrapper (events.js:286:20)\n    at CcZnp.emit (events.js:198:13)\n    at Timeout.<anonymous> (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/cc-znp/index.js:192:18)\n    at ontimeout (timers.js:436:11)\n    at tryOnTimeout (timers.js:300:5)\n    at listOnTimeout (timers.js:263:5)\n    at Timer.processTimers (timers.js:223:10)"}
  zigbee2mqtt:error 8/4/2019, 1:35:02 AM Exiting...
npm

ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-08-03T23_35_37_938Z-debug.log
2019-08-04T01:35:39: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-08-04T01:35:39: PM2 log: App [npm:0] starting in -fork mode-
2019-08-04T01:35:39: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.5.1
> node index.js

ls -l /dev/serial/by-id
lrwxrwxrwx    1 root     root            13 Aug  3 23:20 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001936DD4F-if00 -> ../../ttyACM0

test -w /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001936DD4F-if00 && ech
o success || echo failure
success
# test -w /dev/ttyACM0 && echo success || echo failure
success

I also pressed the reset button on the USB stick, the green LED lights up for about a minute and then goes out.

https://github.com/Koenkk/zigbee2mqtt/issues/1795#issuecomment-517994305


[bug] flickering/flashing tooltip with Inspecio mod

With Inspecio installed, hovering over a glow squid spawn egg shows a preview of the glow squid, but quickly cycling between each variant.
Tested on Jade's Parity Plus 2.0.2, plus rainglow!

MASSIVE WARNING FOR EPILEPSY OR LIGHT SENSITIVITY

this might actually not be something you can control i think it's a bug with Inspecio sorry sorry!

yeah I noticed this during testing but I couldn't figure out a fix :(

one of the devs said it probably can't be fixed on your end when I asked about it so we'll probably just have to hope they implement a way to configure itt


Working Swerve!

The only place it's used in the template code is for scaling the joystick input. I think we can change the drive command to do that if the driver wants it, but I think it's fine as-is


Execution failed for task '"framework:buildInfo'.

I am trying to build the framework but end up with the error
Process 'command 'git'' finished with non-zero exit value 128
As I understand from the gradle files, the code is uploading/deleting files from the github repository. Due to company restrictions I have very limited access to github, in that I cannot clone directories. Sinse I have downloaded the zip manually, it gives the error 'not a git repository'
commandLine 'git log -n 1 --format=%H'.split()
I am assuming this line cannot be omitted. The other git functions (upload/download) have been removed
What should I change in the buildInfo task in order to make it work without git?

yes, that can be omitted.  those lines are in there to automatically stamp the GearVRf library with the git hash of the last commit which we will output to the logcat on startup.  This allows us to help identify what was in a daily build if a problem was discovered in some random build.
you can omit any lines referencing git.

Can I omit the entire buildInfo task? because that task uses the output of 'git log -n 1 --format=%H' for creating .cpp and .java files.

i think you can.

After commenting out the buildInfo tasks in both framework.gradle and backend_oculus.gradle, and commenting out the calls made to the buildInfo task, the build gives the following error
Error:(687) Android NDK: Module gvrf-oculus depends on undefined modules: systemutils
I am not quite sure how to go about it. Can you please build once without all the git commands and let me know what all needs to be eliminated? Thank you!

@sam16222 If you download the latest master, the use of the git executable has been removed. The build now tries to read the information directly from the git metainfo and if it can't, it continues on.
I will look into what happens with the version you are using.

I get the same error when I try to build the framework with the latest version of the NDK :
Error:(686, 0) Android NDK: Module gvrf-oculus depends on undefined modules: systemutils
Downgrading the NDK version builds the framework correctly. We might have to fix the build for the latest version of the NDK.

The systemutls error was fixed by https://github.com/Samsung/GearVRf/pull/1070

@sam16222 Alternatively remove the reference to systemutils from GearVRf/GVRf/Framework/framework/src/main/jni/Android.mk if you want to keep using your snapshot.

Okay it works. Thank you!


[github assistant] can not get oauth token, currently only support Chrome

Hi there,
I use a Chromebook (Pixelbook Go) to develop my Apps Script scripts.
After installing the plugin in my Chrome session I've got this error message :
[github assistant] can not get oauth token, currently only support Chrome
Is gas-github not compliant with Chromebook ?

I am using the Github Assistant on a Pixelbook Go, although I have stuck
with 4.0.7 and using the old script editor.
On Thu, 17 Feb 2022 at 14:06, JEAN-PIERRE ASTIER @.***>
wrote:

Hi there,
I use a Chromebook (Pixelbook Go) to develop my Apps Script scripts.
After installing the plugin in my Chrome session I've got this error
message :
[github assistant] can not get oauth token, currently only support Chrome
Is gas-github not compliant with Chromebook ?
—
Reply to this email directly, view it on GitHub
https://github.com/leonhartX/gas-github/issues/157, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABD4XXIHBI7TBDS5XGPSOHLU3T6GPANCNFSM5OUZBKPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Getting the same message on MacOS with  Version 99.0.4844.51 (Official Build) (x86_64)
I think that likely something got deprecated or changed on the GitHub side of things.

Same error on macOS with version 103.0.5060.114 (Official Build) (x86_64). Makes this extension effectively useless.

I had this problem pop up suddenly after I had been using it on Windows 10 for awhile. Uninstalling Chrome (with removing Data) and reinstalling Chrome, then re-adding the extension fixed the issue for me. Although I suspect uninstalling the extension, removing all of it's data, and reinstalling it would have worked as well.

This error is likely due to a lack of secondary login to Chrome (GAS editor) again.  When installing the extension and the (green) dialog comes up and you have to log into Github, do that with your Github login, and then continue by logging into Chrome/Google to give permission to the extension to access the browser side.  Worked for me.


Linux Riscv BuildTarget

Hmmm, can't say if it actually works. I'm getting this error: java: symbol lookup error: /tmp/libgdxroot/e7dd301d/libjamepadriscv64.so: undefined symbol: SDL_SetHint

Ok, we can proceed here now?

It seem to work 🎉

But somehow, my XBOX controller doesn't get recognized. Not even the LED lights up. I think that's a different problem

Platform could be unsupported by sdl?
Anyhow, do you think we should merge this?

Merging before libgdx/libgdx#7275 is a bit pointless, I think. Otherwise, I read that someone is using this library outside of libgdx, so it could be handy without the mentioned PR


Kotlin not working: java.lang.module.FindException: Module MY_MODULE not found

Hello,
when I update from version 0.0.8 to 0.0.9, my run task aborts with Error occurred during initialization of boot layer java.lang.module.FindException: Module MY_MODULE not found where MY_MODULE is, as you might have already guessed, my module, which I defined in module-info. I'm using Gradle 6.0, and Java/JavaFX 11

Can you post your build script? Can you replicate the issue in one of our samples?

Hello,
sorry for the late reply, but I think I found the problem: Kotlin.
When I bump the javafx-gradle-plugin version to 0.0.9 and add id "org.jetbrains.kotlin.jvm" version "1.4.0" to the plugin part of the IntelliJ Modular Gradle sample, the exception above occurs.

Okay, adding kotlin before the javafxplugin fixes the issue as can be seen here

Okay, adding kotlin before the javafxplugin fixes the issue as can be seen here


does this hash table need deallocate

hello,
does this hash table need deallocate if the program run forever, how can i deal with it?
thanks

Hello,
The memory footprint, if used for a configuration file for instance, is not big. But indeed, the memory is never freed in the code here.
There are two options:

As only "allocatable" arrays are used, if you don't have a dictionary_m variable in the main program but in a subroutine it should be cleaned automatically.
Add code to deallocate all buckets(*)%entries and then buckets explicitly. I can do that if you are interested.

thansk for your reply!
In my business, it needs to be remained in memory. I just want to learn about the code. And in my mind of clang, there will be a deallocate operation. I will be appreciate if you can make it when you are available!

Hello @bryanhan1001 as I mentioned, if you keep the object in scope it will remain in memory. Could you provide a skeleton example of what you try to achieve?

sorry，I am new to fortran. so i want to know how to deallocate the hash map here


Smilies issues

Some smilies, those for which the code is between colons, are not displayed well.
See: http://i.imgur.com/EvnwfAa.png

>>> p.html
'Oui, c'est ce que je fais parfois  , mais c'est marrant de voir tous ces bugs dans les messages <img class="smiley" src="https/geekattitude.s3.amazonaws.com/static/img/smileys/geek.gif">'

http*:/*/ is interpretated as :bof: smiley

Solved 👍

Solved by: https://github.com/maur1th/naxos/commit/1fc4e2cb6229b83e85637557d72494438a3c7c31


Question: Optimum database structure?

Hi guys,
I have a database with a single collection of the following objects:
public class StateMessage
{
        public int id { get; set; }
        public string type { get; set; }
        public DateTime time { get; set; }
        public string[] states { get; set; }
}

I am logging messages every couple of minutes, with messages having a different type and different length of the states (the length of states ranging from 30 to 1000).
Storing messages into the database works great. But after storing data for some time the database grows to a couple of 100MB in size, then querying from the database becomes very slow. I am querying using the Repository Pattern, like:
using(var db = new LiteRepository(my_connection_string))
{
    var result = db.Query<StateMessage>(my_table)
        .Where(x => x.type == searched_type)
        .ToArray();
    // more code ...
}

My question is: Is it better to split the messages into separate objects for each message type and store them in separate collections, or am I doing something wrong?
Thanks

Hi @matkuki, did you create index over this type field? You must do this to avoid need read all document.
When you open your database, add:
db.EnsureIndex<StateMessage>(x => x.type)
Also, i don't know what you will use this in-memory objects, but do not use ToArray() if you using in a paging grid... it's better use Limit/Offset before ToArray().

@mbdavid Thanks, that worked!


Button mapping issue

Cannot find file to button map. C:\Program Files (x86)\Steam\config\steamvr.vrsettings has 3 lines in it and when i add the button mapping lines it just gets overwritten by the 3 lines again. So i tried C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings but when i put the button mapping lines in here it flips my display and nothing works correctly.

Hi.
The SteamVR plugin is no longer part of the PSMoveService and instead can be found here.
But, you're more likely to get an answer to this question by asking in the forum first.
https://groups.google.com/forum/#!forum/psmoveservice


fix return type annotation for gat_many and gats_many

Hello, could you relaunch the pipeline, I do not think that the failure has anything to do with the patch I wrote...


Debug plugins with a debugger

There must be a way! For some reason i don't see Rocket or any of the plugins loaded as module in the debugger...
I searched the web but majority says they should come up even when dynamically loaded, must be something weird in Mono..

Please!

rel https://github.com/angavrilov/ksp-devtools

Here it is ;) https://github.com/RocketFoundation/Rocket/wiki/Debugging-Rocket


Trying to get in touch regarding a security issue

Hey there!
I'd like to report a security issue but cannot find contact instructions on your repository.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

Hi @JamieSlome,
Thanks for reaching out. Yes, you are right: I'm opening a PR to add the SECURITY.md file and a contact method.
In the meantime, please feel free to report the security issue to<EMAIL_ADDRESS>


meeting/upcoming calendar shows cancelled sessions but doesn't label them cancelled

There's an argument for continuing to show cancelled sessions, but they should be clearly distinguished from sessions that actually intend to meet.
For a couple of days (until 6Dec), stir acts as an example.

I think this is fixed? At least I tried it in my dev instance and there is a "cancelled" pill shown.

The issue is in the calendar view, not the table list.
This is fine (I cancelled an upcoming edm meeting in my test instance):

This is not:


Update boards matrix to add AVR builds.

Summary
The checks are failing because the change is only in testing/. This updates apps/.
Impact
Testing

The error is due to https://github.com/apache/incubator-nuttx/pull/1423, let's merge this first.


ru-locale for avalon-app

Added ru and en po-files, also fixed alliases in luci-app-avalon

I have merged it, thanks.


Implement settings page

Priority: twitter integration
e.g. https://opencollective.com/opensource/connect/twitter
See also the design made by @erickrico  https://github.com/OpenCollective/OpenCollective/issues/218#issuecomment-242203492

made obsolete by v2

actually no, this hasn't been solved yet.

Hi @piamancini, do we need design for this? I'm currently organizing all tasks for design work.

I don't think we can tackle this in the short term @cuiki :(

Ok, I'll leave it in queue.

we already have a twitter integration. It seems no one is working on this so I'm closing


[WIP] fix failing coverage report upload

Is codecov supposed to be displayed on the CI of this PR?

Is codecov supposed to be displayed on the CI of this PR?

Not yet but it will once the problem is fixed :)

@Vincent-Maladiere  should be ok now


there is a white line on top menu when vscode in 4k resolution

Issue Type: Bug
there is a white line on top menu when vscode in 4k resolution( 150% Scaling)!
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:45.096Z)
OS version: Windows_NT x64 10.0.18362

@bluecc I have the same issue: I use a 4k monitor with 150% scaling (recommended by Windows) and since the update which came out yesterday, a white line appears on the top of the screen when VS Code is in fullscreen

@bluecc I've just tested VS Code in Windows Sandbox. Installed the latest version and the issue seems to NOT be present. However, since you are not allowed to change resolution in a remote windows session, I can't say for sure if the rendering resolution was indeed native 4k (with the 150% default scaling).
I also tried to see what settings might cause this issue, and so far I saw that if you change the title bar style to native instead of custom"window.titleBarStyle": "native" you will get the classic win32 type of title bar and the white line goes away. So I suspect there has to be some problems with rendering the bar which comes with the "electron" framework.

Hmm, this isn't happening with me. I've got 4K 200% and have tried 150% also.
EDIT: Ok, I See it if I resize the window and then put it in fullscreen again.

@awsumbill  I'm just curios, what's your display size? mine is 27inches and 150% scaling is perfect for me. Any reason why you went 200%?

@bluecc I've just tested VS Code in Windows Sandbox. Installed the latest version and the issue seems to NOT be present. However, since you are not allowed to change resolution in a remote windows session, I can't say for sure if the rendering resolution was indeed native 4k (with the 150% default scaling).
I also tried to see what settings might cause this issue, and so far I saw that if you change the title bar style to native instead of custom"window.titleBarStyle": "native" you will get the classic win32 type of title bar and the white line goes away. So I suspect there has to be some problems with rendering the bar which comes with the "electron" framework.

Thanks, I am using the classic win32 type of title bar now! Looking forward to the next update!

Yeah, I am about to do the same 🤣 the white line gets quite annoying and super distracting to be honest.

@bluecc  I wouldn't close this issue to be honest. Problem still needs to be solved.

@bluecc I wouldn't close this issue to be honest. Problem still needs to be solved.

@basavyr Yeah, you are right!🤣

Can reproduce this problem on a regular monitor (24" 1920x1080) if scale for this monitor is 150% or 175%
/cc @deepak1556

@awsumbill  I'm just curios, what's your display size? mine is 27inches and 150% scaling is perfect for me. Any reason why you went 200%?

I've got a pretty big screen, 43 in. so 200% is necessary.

I also have this issue, 27" 4K monitor set to 150% scaling.

I found this issue since 1.40.2 on my laptop as well, but 1.39.2 ,1.40.0 and 1.40.1 don't have this problem.
The interesting thing is that my HP ZBook laptop has a 4k screen (with recommended 250% scale) and also connects another 2 external Dell 4k screens (with recommended scale 150% scale). In this case the maximised VSCode window don't have a white stripe on the top on both Dell screens, but will have on the laptop its own screen. Now if change the scale of the laptop's screen to 150%, the white stripe disappears on the laptop's screen. Furthermore if change the scale of the Dell screen to 250%, a white stripe appears on the Dell screen.
Now, if I sign out and disconnect both external Dell screens, after signing into Windows 10 again, the scale of the laptop's screen is still 250%, but there is no white stripe on top of the maximised VSCode window! Then re-connect the two Dell screens (still with the recommended 150% scale), all of the 3 screen are fine, there is no white stripe appearing on any of them.

I also have this issue in version 1.41.0.
Device is a Microsoft Surface 3, scaling set to 175%.
The bar is not displayed on either of my 1080x1920 connected monitors.

This only has happened once to me out of the ten or so times I have opened VSCode since this issue first opened.
The line appeared after I minimized and then maximized the window.
I have not seen it since.
I have 3840 x 2160 resolution, tried on 150% and 200% scaling. When I saw the line I was at 200%.
I have a 43" monitor (TV), 42" not including borders.
I have Windows 10, version 1909, build 18363.535, VSCode version 1.41.0

Also having this issue, can persistently reproduce it since ~1.40.2 when it first appeared after updating VS Code.
Affects only maximized VS Code instances on my second 3840 x 2160 display with 175% scaling. If the maximized window is moved/resized (including switching to "half-display" layout by pressing Win+Left Arrow), the white bar goes away. If I maximize the window on my main 1080p display 125% scaling, the white bar is NOT present ¯\_(ツ)_/¯
(open a screenshot on black background to see a line on top)

Version: 1.41.0 (system setup)
Commit: 9579eda04fdb3a9bba2750f15193e5fafe16b959
Date: 2019-12-11T18:37:42.077Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

Same issue encountered. I have a 15" 1080p laptop, screen is scaled to 150%.
VSCode 1.43.0
Windows 10

I am having the same issue, I have a 49 inch ultrawide monitor which is 5k, and i have big bars appearing here and there, and also the area that is not white is dull as well. Has a solution for this been found?

I started seeing this when I changed my secondary monitor (I run VSCode on the primary monitor--and it is indeed high DPI).  Strange issue.

My issue was resolved once I turned off HDR on my monitor.

Still having this issue with HDR off, 4k resolution, and scaling set to 150%. If i set scaling to 125% it goes away, but that font size is too small for me.
I'm on the latest version of Windows as of 5/11/2020, KB4550945.

Same issue here - 4K 15 inch Laptop Monitor. 125% scaling. Annoying white line. Full screen mode fixes it. Like the new title bar too much to use the classic style :)

I found this to happen on dual monitors with different resolutions monitors. I have 2k and 4K monitors. When I set 2K monitor as the primary monitor, the white line appears.
Instead, set the 4K monitor as the primary monitor, the white line disappears!

Still having this issue with HDR off, 4k resolution, and scaling set to 150%. If i set scaling to 125% it goes away, but that font size is too small for me.
I'm on the latest version of Windows as of 5/11/2020, KB4550945.

Seeing the exact same thing here.

I am also having the same issue on a 4k monitor with 150% scaling. The same issue also a happens when I select something in Windows Terminal, so may not be a VS Code issue, it maybe issue of the windows itself!

This should be fixed with latest insiders https://code.visualstudio.com/insiders/ , please comment if its still an issue. Thanks!

This should be fixed with latest insiders https://code.visualstudio.com/insiders/ , please comment if its still an issue. Thanks!

Issue with white space on 1920x1080 laptop (100% scale)

@mpa74 it does look bad, can you open a separate issue, this issue specifically tracks the bug for 4k resolution. Thanks!

I've just installed the insiders build, the bug is still there @deepak1556

4k, 27in monitor. Bug does not occur on my second 1440p monitor.

Surface Pro X main display, 200%, white line.

Thanks for testing, that helps.

New testing request, can you check if the latest insiders https://code.visualstudio.com/insiders/ fixes the issue. Thanks!

New testing request, can you check if the latest insiders https://code.visualstudio.com/insiders/ fixes the issue. Thanks!

Yes, I can confirm that white line is gone in Insider's!


Embeddings and Ntriples

@bigerl @SimonBin @heindorf
If we want to learn embeddings on a knowledge base stored in the nt format <a> <b> <c> . Keys in the embedding csv should be a, b, c, i.e., remove all < >. Do we all agree ?

During parsing the input KG, we simply go thorough all triples and remove <>.

Sounds good. That keeps the current format and makes sure that all tools which relz on it already keep working.

However, there is a disadvantage, namely, to remove <> we need to go through all triples.

I would say that is resonable. I would suggest to do it quick&dirty now and create a new issue:
"reduce string copies during rrading input file" to look into further optimizations later.


add GitHub flavored markdown notes

closes https://github.com/storybooks/storybook/issues/2916#issuecomment-364205690

Please add a usage example to storybook-official

You probably need to run yarn install in project root to update lockfile

Live example
For some reason, it just displays raw markdown sources instead of formatted text

For some reason, it just displays raw markdown sources instead of formatted text

OK, it's because of the indentation in the example. Indent is just another way to define code block

ahh thats why. sorry I hadn't had time last week to get around to this, glad you figured it out. was definitely working in my local setup. im still in the first month of my new job, got to figure out what my ability is to work on open source :( thank you so much for being an awesome maintainer, I hope to be a better contributor over time


systemd-timsyncd failing to start on nixos-unstable

Describe the bug
When switching to nixos-unstable from nixos-19.03, I started getting this error:
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/nix/store/md7jdq475ij8cpifxb5rrh7y51qrfypq-systemd-242/example/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
  Drop-In: /nix/store/6x8wf3bc69prnahjw0bz9cp96kbzw6ki-system-units/systemd-timesyncd.service.d
           └─overrides.conf
   Active: failed (Result: exit-code) since Thu 2019-08-15 14:59:24 EDT; 24ms ago
     Docs: man:systemd-timesyncd.service(8)
  Process: 5572 ExecStart=/nix/store/md7jdq475ij8cpifxb5rrh7y51qrfypq-systemd-242/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
 Main PID: 5572 (code=exited, status=238/STATE_DIRECTORY)

Aug 15 14:59:24 dellbook systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 15 14:59:24 dellbook systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Aug 15 14:59:24 dellbook systemd[1]: Stopped Network Time Synchronization.
Aug 15 14:59:24 dellbook systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Aug 15 14:59:24 dellbook systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Aug 15 14:59:24 dellbook systemd[1]: Failed to start Network Time Synchronization.

I believe it is related to the systemd upgrade to 242. stateVersion is unset.
Metadata

system: "x86_64-linux"
host os: Linux 4.19.66, NixOS, 19.09pre188690.8746c77a383 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.09pre188690.8746c77a383"
channels(mbauer): "nixpkgs-19.09pre188239.c0e56afddbc"
nixpkgs: /home/mbauer/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module: services.timesyncd

Closing as duplicate of https://github.com/NixOS/nixpkgs/issues/64922


Recreate components on URL change

I'm finding myself doing a deep watch of router.params in all of my components used by <router-view> in order to reload the data loaded/initialized in my components' created handler. Is there a better way about this? Should this automatically happen for navigation changes in the same router component?

There is going to be a data option to route definitions, which allows you to load some data based the the route before actually initializing/updating your components.

Btw, thanks for these issues! It's really helpful to have feedback based on actual usage even before it's released :)

:+1:
How do you plan to handle async data? In my case, I'm loading from an external data source.
If I navigate to a page within the same component, causing a new set of data to be loaded, what happens between the navigation and data loading? Does the page remain unchanged until the data is loaded? Will there be an option to clear the data? I'd like to keep the UI feeling snappy, and if there's a delay between page updates after navigating without a way to clear the data, it'll feel really sluggish.

What do you mean by "clear the data"?

Currently a VM's data is not cleared or reloaded on navigation changes within the same component (e.g. navigating from /entries/1 to /entries/2 where entries is the shared component). In order to load new data, I'm watching for changes in the route params, then fetching new data based on the new route params. Before that data is fetched, I'm clearing the data set on the last fetch so I can conditionally display a "loading" indicator (so that navigation has a clear effect on the page).

There's an option called alwaysRefresh (maybe could use a better name) which basically means if the params change this component should just be reloaded.

Although I haven't really put enough thought to the async data handling part yet - maybe there could be a more elegant solution.

Alternatively - we can expose a loading flag on the route object to indicate that the async data function is still awaiting its result.

alwaysRefresh and loading are not implemented, so should I just watch the $route.params for now?

By the way how exactly should I watch vm.$route.params ?
I tried passing it to vm.$data.params
data: {
    params: vm.$route.params
}

and
vm.$watch('params', callback, {deep: true})

does not work.

The problem is that vm.$route.params was never updated when url changes from /entries/1/ to /entries/2/...

Same here. I'm trying to 'force' reload my page components when switching from route
whatever/1 to whatever/2.
How would you go about to watch the $route.params anyway ?
Thanks

+1 Also interested in refreshing component data based on a change in param.

Did you find a solution to this @rleger? I'm still trying to reload a component's data upon a param change.

Did you find a solution to this @rleger? I'm still trying to reload a component's data upon a param change.

@benwalks the best I could come up with is to watch the route params.. not elegant but for lack of a better solution it works.
ready() {
  this.$watch('$route.params', this.handleChange , { deep: true })
}

Well guys.. there has been a solution using route.data function, read about it here, just as Evan wrote when he closed the issue on 11 Jun 2015. Maybe he was too busy to explain it here..
On 1 Oct 2015 I hadn't read though the docs carefully, so I posted the problems (which weren't) here. Later I read the docs and solved the problems, and totally forgot about this issue.... So I hope this helps @benwalks @rleger

Yeah, thanks fnlctrl, I did actually figure that out in the end!  Here's some sample code for future people.
export default {
    props: ['lessonNumber'],
    data() {
      return {
        lesson: {
          title: "",
          video: "",
          description: ""
        }
      }
    },
    ready() {
      this.fetchNewLesson()
    },
    methods: {
      fetchNewLesson() {
        this.$http.get('http://localhost:4000/api/v1/lessons/' + this.lessonNumber).then(function (response) {
          this.$set('lesson', response.data.data)
        })
      }
    },
    watch: {
      lessonNumber: {
        handler: function() { this.fetchNewLesson() },
        deep: true
      }
    }
  }


add opt_clearBufferOffset for audio

In my use case i want to keep the live stream playing while switching audio tracks,
i've added this option to allow switching audio at specific time and not pause the stream for that.
Thanks,

Please read the instructions in CONTRIBUTING.md.  You need to add yourself to CONTRIBUTORS and AUTHORS.  Thanks!

Done

Thanks!


mariaDB support

HI,
Normally mariadb should work just fine with the mysql-connector, however there is another java connector written especially for mariadb (and supported by mariadb comunity): https://downloads.mariadb.org/client-java/
Here's my story. I switched from mysql to mariadb couple of days ago and after running the server for few hours, the following messages are written into traccar-server.log:
2014-04-22 04:01:22  WARN: Could not send query: Last packet not finished - java.sql.SQLNonTransientConnectionException (SQLExceptionMapper.java:136)
When this happen, nothing is written into the db and only restart of the traccar-server is fixing it. I'm not sure if this is related to the connector, but if someone have any ideas I'll appreciate the help.
Thanks.

I recently switched to MariaDB. I managed to get traccar working with MariaDB. I had to modify three things in the configuration.
In traccar.cfg you need to change the database config to:
<entry key='database.driver'>org.mariadb.jdbc.Driver</entry>
<entry key='database.dataSource'>org.mariadb.jdbc.MySQLDataSource</entry>
Additionally I had to add the MariaDB jdbc to the classpath in the wrapper.cfg file:
wrapper.java.classpath.3=/usr/share/java/mariadb-jdbc/mariadb-java-client.jar
The default autoreconnect does not work with MariaDB because it is simple not supported. One could try the tcp timeout instead. But so far this seems to work fine.

Thanks for sharing configuration parameters.


make each row a link?

Is it possible to make each row a link?

@GavMan1995 You could just have a one column table and then use custom render like so:
class Example extends React.Component {

  render() {

    const columns = [
      {
        name: "Link",
        options: {
          filter: false,
          customRender: (value, tableMeta, updateValue) => {
            return (
              {value}
            );
          }
        }
      },
    ];

    const data = [
      ["http://www.google.com"],
      ["http://www.cbs.com"],
      ["http://www.yahoo.com"],
    ];

    const options = {
      filter: true,
      filterType: 'dropdown',
      responsive: 'stacked',
      selectableRows: false
    };

    return (
      <MuiThemeProvider>
        <MUIDataTable title={"ACME Employee list"} data={data} columns={columns} options={options} />
      </MuiThemeProvider>
    );

  }
}

which would yield you a table that looks like this:

change customRender  to customBodyRender in above example

@gregnb Hello, so I'm trying to do something similar except adding two link tags in a single column.  The issue is the links should correspond to the inline data.   For example, Row 1 with data ID=1 should have an associated link of someapi/edit/1 and so forth.  RIght now I have a helper function handling other columns, but I can't figure out, even with a customBodyRender how to make this work.
My render and render helper function are below.  Thoughts?
`// render Helper to get data in array format
renderPolicies() {
return _.map(this.props.policies, policy => {
const policyLink = this.renderAdmin(policy);
return [
policy.resource.id,
policy.resource.action,
policy.resource.entity,
policyLink
];
});
}
renderAdmin = policy => {
return (

<Link to={/app/fusion/policy/edit/${policy.resource.id}}>Edit
{'   '}
<Link to={/app/fusion/policy/delete/${policy.resource.id}}>
Delete

);
};`
`render() {
const columns = [
'ID',
'Action',
'Entity',
'Edit'
];
const data = this.renderPolicies();
const options = {
  filterType: 'checkbox'
};

return (
  <MUIDataTable
    title={'Policies'}
    data={data}
    columns={columns}
    options={options}
  />
);

}`

Is this a better option than doing onRowClick and making the row go to a certain link?

Is this a better option than doing onRowClick and making the row go to a certain link?


Update PostHog API Keys

Description
Update the PostHog API Key to point to our new migrated host & Production project.
Checklist

[x] I have read the contribution guidelines

This can be done now, then all new data will drive to our new Project. The Replication on PostHog will then transfer over the historical data.


add dsa roadmap in category other under roadmaps

closes #1939
Note to reviewers
Kindly look into the PR and please let me know if any further change is needed

@psqaure11
Following the PR template is a must. It includes special words like 'fixes' or 'resolves' that connect your issue to the PR, as explained in the official docs.
If you don't link the issue correctly, even after the PR is merged, the issue might stay open, causing huge problems.

You can see here. I've done it.

I'm doing it for you this time. Please ensure it next time.
Just a heads-up to help you link issue properly next time. Have a great day!

@Anmol-Baranwal Thanks for correcting this on my part will keep this in mind from now onwards.


Allow use of GSM for superuser password secret

This is similar to #458 except we read from GSM for the superuser password secret. We use the same feature flag as before. Here is a sample CR to enable it.
kind: VerticaDB
metadata:
  name: v
  annotations:
    vertica.com/use-gcp-secret-manager: "true"
spec:
  superuserPasswordSecret: <full name of the secret in GSM>
...

The name of the GSM secret is taken from the existing spec.superuserPasswordSecret field.
Note, we no longer use the canary query for health probes as that depends on the superuser password being a k8s secret. Instead, we check if vertica is running by seeing if anyone is listening on the vertica client port.

@sivaalamp thanks for your contribution. I don't normally do this, but since we are short on time I opted to apply the code review comments myself. This will shorten the review cycle and allow us to get it in QA hands sooner.


Bump Dependencies #9065209455

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/9065209455

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


Update Scrollable.jsx

fix(#47): Added  on the children , as they can change without triggering the componentDidUpdate stage.

:tada: This PR is included in version 1.3.1-next.2 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


/run/current-system/sw/bin/wgnord: line 16: /var/lib/wgnord/credentials.json: No such file or directory jq: error: Could not open file /var/lib/wgnord/credentials.json: No such file or directory

sudo wgnord l e9*****
/run/current-system/sw/bin/wgnord: line 16: /var/lib/wgnord/credentials.json: No such file or directory
jq: error: Could not open file /var/lib/wgnord/credentials.json: No such file or directory

Running on NixOS
Thank you for your time!

Hi,
version 0.2.0 introduced a breaking change in how login works. (See https://github.com/phirecc/wgnord/commit/c04002123e4d0891e21b815b4707e130bd402e24).
Instead of user/pass wgnord now uses tokens. You can generate a token in the NordVPN dashboard and then run
wgnord l "your_token"

I should probably add a more helpful error message, since this should happen to everyone upgrading to 0.2.0.

(edit: I misread the error in my previous reply) Hi, I think the error is due to the /var/lib/wgnord directory not existing. Did you follow the installation steps in the readme? It should be created on installation.

Thank you, it worked fine after I manually created the directories it asked me to. I'd installed it through nixpkgs without doing anything else.

Oh wow, I didn't know someone made a nix package for wgnord. That's cool :)
I think the problem lies in the nix install script. I believe it would be better if the postPatch section just changed the definition of conf_dir to $out/share/ here:
https://github.com/NixOS/nixpkgs/blob/c96b386640b0c11bbb6d878d86ec39629ab92997/pkgs/applications/networking/wgnord/default.nix#L25
So something like this:
postPatch = ''
    substituteInPlace wgnord \
      --replace 'conf_dir=/var/lib/wgnord' "conf_dir=$out/share"
  '';

The linked code only changes the path of countries.txt and countries_iso31662.txt, but credentials.json, coords.json and template.conf are still attempted to be read from /var/lib/wgnord. It also appears not to install template.conf at all?
I'm not too familiar with nix though, maybe you could make an issue?
Thanks

I needed to create manually:
mkdir /etc/wireguard
mkdir /var/lib/wgnord

to make this work. This should be part of the installation process!(?) Please reopen this issue.

What distribution are you using? On arch /etc/wireguard is created by the wireguard-tools dependency.
And /var/lib/wgnord is should be created by the install commands in the manual installation instructions in the readme.

I am using Nixos. I thought I was in the nixpkgs repository and talking to the Nix package maintainer. I did not notice that i am posting upstream. Sorry.

No problem :)


Create function for populate

This popular feature table dynamically with new values.
var sheetData = [
        [1,1,1,0,1,0,1,1,1,1,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
        [0,1,0,0,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0],
        [0,1,0,0,1,0,1,0,1,0,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
        [0,1,0,0,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0],
        [0,1,0,0,1,0,1,0,1,0,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
        [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],
        [1,1,1,0,1,0,1,0,1,1,1,0,1,1,1,0,1,1,1,0,0,0,0,0],
        [1,0,0,0,1,0,1,0,1,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0],
        [1,1,1,0,1,1,1,0,1,1,1,0,1,1,1,0,0,1,0,0,0,0,0,0],
        [0,0,1,0,1,0,1,0,1,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0],
        [1,1,1,0,1,0,1,0,1,1,1,0,1,1,1,0,0,1,0,0,0,0,0,0],
        [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1]
    ];

sheet.setSheetData(sheetData);

@newerton
Sorry I don't get this one

@lbbc1117
I did a primary adaptation! :)
var CSheet = function (opt) {
...
	this.setSheetData = function (cellIndex) {
		var rowCount = cellIndex.length;
		var colCount = cellIndex[0] ? cellIndex[0].length : 0;
		var settingArea;

		for (var row = 0; row < rowCount; ++row) {
			for (var col = 0; col < colCount; ++col) {
				if (cellIndex[row][col] === 1) {
					settingArea = {
						startCell: [row, col],
						endCell: [row, col]
					};
					sheetPrivate.areaOperate(settingArea, {type: "set", state: 1});
				}
			}
		}
	};
...
}
...
var publicAPI = {
...
	setSheetData: function (cellIndex) {
		sheetModel.setSheetData(cellIndex);
		removeSelecting();
		repaintSheet();
		return;
	},
...
};

 var sheetData = [
    [1,1,1,0,1,0,1,1,1,1,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
    [0,1,0,0,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0],
    [0,1,0,0,1,0,1,0,1,0,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
    [0,1,0,0,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0],
    [0,1,0,0,1,0,1,0,1,0,1,0,1,1,1,0,0,0,0,0,0,0,0,0],
    [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],
    [1,1,1,0,1,0,1,0,1,1,1,0,1,1,1,0,1,1,1,0,0,0,0,0],
    [1,0,0,0,1,0,1,0,1,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0],
    [1,1,1,0,1,1,1,0,1,1,1,0,1,1,1,0,0,1,0,0,0,0,0,0],
    [0,0,1,0,1,0,1,0,1,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0],
    [1,1,1,0,1,0,1,0,1,1,1,0,1,1,1,0,0,1,0,0,0,0,0,0],
    [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1]
];

$('#J_timingPopulate').click(function(){
    sheet.setSheetData(sheetData);
});

@newerton
Yeah right.  A dynamic data setter for all cells.

@lbbc1117
It would be great to create a function to add 1 cell.

@newerton
Good advices amigo. As I'm busy learning deep learning recently, I may do some modification if I get time.


fix: integration tests for shield api and proxy

additionally fix authz middleware executing even for proxy routes where it was disabled

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.781%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/serve.go
0
1
0.0%

cmd/serve_proxy.go
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4687

Relevant Lines:
8715

💛  - Coveralls


Dependency package priorityqueuejs has a new version available

We have identified a dependency on priorityqueuejs (1.0.0). A new version (2.0.0) is available now.

Only cosmos
[cosmos] Update runtime dependency "priorityqueuejs" #9314
v2 claims to drop support for browsers

latest comment from #17105

The latest version of priorityqueuejs is v2.0.0
Any chance we can look into updating the version we are depending on to ensure we get any potential security fixes?
Or perhaps consider removing the dependency and inlining the implementation?

Looking at the history of , I don't see any functionality changes.
v2

Stop supporting component and browser builds.

but that's just removing the structure used to build and test the package in browser using components.


fix: increase timeout of TransactionResponse test

Close: https://github.com/FuelLabs/fuels-ts/issues/1862

This test has been timing out a lot in our workflows recently and I increased its timeout to 10s in the hopes of stopping the timeouts.

@arboleya haha, this is comedy. I change the node settings a bit and reran the workflows a couple of times and they passed each time. I'd merge it like this and we can see if it'll pop up anymore.


change getCount from Update to Query

Can you manually run prettier on your files (npx prettier --write .)? I think that's where the majority of the changes in this PR are from. I think even though the files are auto-generated by dfx generate we are still running them through prettier. So each time you run dfx generate run prettier after. We can work on getting it in a pre-commit hook. Just haven't gotten it that far yet.


SW-3140 Make spacing between table headers and search/filters consistent

Various tweaks to make spacing consistent across pages.

Species looks like there is some extra space but that's because Seed Storage Behavior is split across three lines outside of the screenshot.


Renovate/sinatra 4.x

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

Comparison is base (9e2356a) 34.97% compared to head (29274be) 34.97%.
Report is 1 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   34.97%   34.97%
=======================================
  Files          47       47
  Lines        1298     1298
=======================================
  Hits          454      454
  Misses        844      844

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


strand.md: nucleotides can't be split further

hence the patch

Thanks!  I'll probably tweak this a bit more.


p2p(peer): add support for ipv4 peers

Because the Bitcoin message protocol uses ipv6, I cut corners and only allowed peers that use ipv6
In src/network/peer.zig
    pub fn init(allocator: std.mem.Allocator, config: *const Config, address: std.net.Address) !*Peer {
        if (address.any.family != std.posix.AF.INET6) {
            return error.WeOnlySupportIPV6ForNow;
        }

Rather than doing this we should accept IPv4 Addresses too and have a function to covert all of them to ipv6 when we need to send messages
posix.AF.INET  is the flag for ipv4.

I will like to take care of this issue


Feature request : Drop down on hover

Currently, when a user wants to see the contents of the drop-down menu he/she needs to click on the dropdown.

I want to suggest a feature that when the user hovers over the dropdown then the contents of the drop-down pops out.

can i be assigned to this ?

can i be assigned to this ?

closed #422 via #419

closed #422 via #419


Added a useful resource

Have added a useful resource about exception handling in java from the scaler topics in resource section.

Hi @Vaishnaviamirayada thanks for the suggestion, could you please open this PR here 👉🏾  https://github.com/Umuzi-org/ACN-syllabus. This repo is no longer being maintained, note the info on the README

DEPRICATED!!!!
Please make your PRs here instead:
https://github.com/Umuzi-org/ACN-syllabus


Update cloud_sql.py

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).


Code cell shows "markdown" language

I can't repro this manually but I can hit it with a test reliably. Somehow we

insert a code cell
send the splice to the EH, it's handled in _spliceNotebookCells
Call this._documentsAndEditors.acceptDocumentsAndEditorsDelta with the addedDocuments
let ref = this._documents.get(resource);
There is already a cell that exists with that URI, and it is a markdown cell

So ExtHostCell#language for this new cell returns markdown, which is incorrect

I triggered it manually but I'm not sure how:

I'm done debugging for tonight but I suspect that the issue involves editing a notebook while it is closed (like outside of vscode). The test opens a notebook with the same URI but different content, and this only fails on the second run. These steps seem related:

Open a github issue notebook
Close it
Open it in vim, delete some cells
Open it in vscode, insert some cells
Save it
Sometimes those cells are saved with the wrong content

@roblourens in the smash test, can you add a validation after a document is opened in each test, and check if the document is the same as what's on disk? If it doesn't match, it means the document is obsolete and definitely a bug with our document lifecycle.

I can't repro an issue with my manual steps above, but the test still hit this reliably and I think there is a real issue that I don't fully understand. @jrieken, help my understand what's going on. I added logging to https://github.com/Microsoft/vscode/blob/roblou/notebookRandomActionTest/src/vs/workbench/api/common/extHostDocumentsAndEditors.ts#L80
and it shows that every cell gets "added" twice and "removed" twice, so the ref counting cleans it up nicely. But, in my test case, one cell only gets "removed" once so when it is added again on the second test run, an entry with that URI already exists. Why are cells ref'd twice and where should I look to figure out why one of them is not unref'd?

Why are cells ref'd twice and where should I look to figure out why one of them is not unref'd?

In the UI, when a notebook opens we don't create text models because that would be slow. However, text models drive the TextDocument api and we want each cell to appear as text document in the API as soon as a notebook is opened. Therefore, we open each cell as text document (this happens in the extension host) when a notebook opens, later the UI might also open these cell documents which ends up running the same code path and increasing the ref counting. When notebook is closed in dereferences its documents, similar things happen in the renderer - when a text model gets disposed it dereferences the extension host document. You can have a dangling reference when one of those things doesn't happen. Since references on the UI side are also ref-counted it is likely that there are dangling references, which can happen when using the openTextDocument-API which (on the UI side) creates an auto-dispose reference (will dispose after 3minutes)

So we ref each cell once from the frontend and once from ExtHostNotebooks. I think the issue is that cells are unref'd when the document closes but not when the cell is deleted. So a deleted cell can be leaked to the next time the notebook is opened. Steps

Create a cell, type in it
Delete the cell
Close the notebook
Reopen the notebook
Create a cell
The UI shows an empty cell, but the EH still has the content

Indeed. When deleting a cell $acceptDocumentAndEditorsDelta is not called 😱

Oh, I see... This is going through $acceptModelChanged


Adjusted stripe card params name

According to the documentation of Stripe (https://stripe.com/docs/tutorials/forms), the value for the data-stripe attribute of the month and year should be 'exp-month' | 'exp-year' and not 'exp_month' | 'exp_year' (dash instead of underline).

:+1: Thanks


show tables doesn't work with db2 connector

Environment
presto v0.193 provisioned by docker image shawnzhu/prestodb:0.193 from repo IBM/docker-prestodb
Steps
I configured presto to connect to a db2 instance in dashdb.
presto:whitewater> use db2.BLUADMIN;
USE
presto:bluadmin> show tables;
Query 20190320_194229_00014_druzu failed: [jcc][t4][2034][11148][4.25.13] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected.  Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009

presto:bluadmin> select count(*) from foo_users;
Query 20190320_194253_00015_druzu failed: [jcc][t4][2034][11148][4.25.13] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected.  Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009

I thought it works before when I use another dashdb to try it out.

I can confirm this feature works with shawnzhu/prestodb:0.215 with a dashdb instance.
The above errors may be caused by illegal connection-url value from the properties file under catalog folder. Notice that when using SSL in dashdb, it requires port number 50001 and parameter sslConnection=true; in connection-url.