[Bug]: Transition causes delay on M5 Atom Matrix Listeners when using transition instead of cut

What happened?
hi there,
i use an m5 atom matrix nearly succesfully, cut is working fine, but when using a transition (eg 1sec) switching back from program to preview is weird. the atom receives a lot of commands and tries to get it right, but it takes 3sec until the light is green again. switching from preview to program also is a lot of commands, but the light is immediately red at least.
did anyone also has this problem? here the serial monitor, as you can see it takes 4sec instead of 1sec to process all information. i guess problem is in tally arbiter sending out device_states while transitioning?
i use version 2.0.16 since in 3.04 no listeners appear on the list :-(
Version
2.0.16
Distribution
Desktop
OS
MacOS
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
If applicable, What Listener Clients are You Using?
M5 Stick
TallyArbiter configuration
{
 "externalAddress": "http://<IP_ADDRESS>:4455/#/tally",
 "security": {
  "username_settings": "admin",
  "password_settings": "12345",
  "username_producer": "producer",
  "password_producer": "12345"
 },
 "sources": [
  {
   "data": {
    "ip": "<IP_ADDRESS>",
    "me_onair": [
     "1",
     "2",
     "3",
     "4",
     "5",
     "6"
    ],
    "cut_bus_mode": "off"
   },
   "name": "Atem Mini",
   "sourceTypeId": "44b8bc4f",
   "reconnect": true,
   "enabled": true,
   "id": "0f528128",
   "connected": true
  },
  {
   "data": {
    "port": 5555
   },
   "name": "atemOSC",
   "sourceTypeId": "05d6bce1",
   "reconnect": true,
   "enabled": false,
   "id": "e89e3fce",
   "connected": false
  },
  {
   "data": {
    "ip": "<IP_ADDRESS>",
    "me_onair": [
     "1",
     "2",
     "3",
     "4",
     "5",
     "6"
    ],
    "cut_bus_mode": "off"
   },
   "name": "Atem Mini EXTREME",
   "sourceTypeId": "44b8bc4f",
   "reconnect": true,
   "enabled": true,
   "id": "e461385e"
  }
 ],
 "devices": [
  {
   "name": "1",
   "description": "Cam 1",
   "tslAddress": 1,
   "enabled": true,
   "id": "54546b2b",
   "linkedPreview": false,
   "linkedProgram": false
  },
  {
   "name": "2",
   "description": "Cam 2",
   "tslAddress": 2,
   "enabled": true,
   "id": "9e1e798f",
   "linkedProgram": false,
   "linkedPreview": false
  },
  {
   "name": "3",
   "description": "Cam 3",
   "tslAddress": 3,
   "enabled": true,
   "id": "b524c3ab",
   "linkedProgram": false,
   "linkedPreview": false
  },
  {
   "name": "4",
   "description": "Cam 4",
   "tslAddress": 4,
   "enabled": true,
   "id": "440ff2a9",
   "linkedProgram": false,
   "linkedPreview": false
  },
  {
   "name": "5",
   "description": "Cam 5",
   "tslAddress": 5,
   "enabled": true,
   "id": "7cf49038",
   "linkedPreview": false,
   "linkedProgram": false
  },
  {
   "name": "6",
   "description": "Cam 6",
   "tslAddress": 6,
   "enabled": true,
   "id": "76f76a88",
   "linkedPreview": false,
   "linkedProgram": false
  },
  {
   "name": "7",
   "description": "Cam 7",
   "tslAddress": 7,
   "enabled": true,
   "id": "22703db1",
   "linkedPreview": false,
   "linkedProgram": false
  },
  {
   "name": "8",
   "description": "Cam 8",
   "tslAddress": 8,
   "enabled": true,
   "id": "9b6a3778",
   "linkedPreview": false,
   "linkedProgram": false
  }
 ],
 "device_sources": [
  {
   "deviceId": "54546b2b",
   "sourceIdx": "0",
   "address": "1",
   "sourceId": "0f528128",
   "id": "98145b89"
  },
  {
   "deviceId": "9e1e798f",
   "sourceIdx": "0",
   "address": "2",
   "sourceId": "0f528128",
   "id": "6ab7ecf8"
  },
  {
   "deviceId": "b524c3ab",
   "sourceIdx": "0",
   "address": "3",
   "sourceId": "0f528128",
   "id": "cb2c8e74"
  },
  {
   "deviceId": "440ff2a9",
   "sourceIdx": "0",
   "address": "4",
   "sourceId": "0f528128",
   "id": "740fd1dc"
  },
  {
   "deviceId": "7cf49038",
   "sourceIdx": "0",
   "address": "5",
   "sourceId": "0f528128",
   "id": "749ea434"
  },
  {
   "deviceId": "76f76a88",
   "sourceIdx": "0",
   "address": "6",
   "sourceId": "0f528128",
   "id": "b0551132"
  },
  {
   "deviceId": "22703db1",
   "sourceIdx": "0",
   "address": "7",
   "sourceId": "0f528128",
   "id": "060f82d7"
  },
  {
   "deviceId": "9b6a3778",
   "sourceIdx": "0",
   "address": "8",
   "sourceId": "0f528128",
   "id": "d27113aa"
  }
 ],
 "device_actions": [
  {
   "deviceId": "54546b2b",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/1",
    "args": "1"
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "8c55bfcc"
  },
  {
   "deviceId": "54546b2b",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/1",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "9db965ea"
  },
  {
   "deviceId": "54546b2b",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/1",
    "args": "1"
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "54762e00"
  },
  {
   "deviceId": "54546b2b",
   "data": {
    "args": "0",
    "path": "/atem/program/1",
    "port": 7777,
    "ip": "<IP_ADDRESS>"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "a0029e56"
  },
  {
   "deviceId": "9e1e798f",
   "data": {
    "path": "/atem/preview/2",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "483e0fb0"
  },
  {
   "deviceId": "9e1e798f",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/2",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "f1b05bf2"
  },
  {
   "deviceId": "9e1e798f",
   "data": {
    "path": "/atem/program/2",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "10afa484"
  },
  {
   "deviceId": "9e1e798f",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/2",
    "args": "0"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "9454ada5"
  },
  {
   "deviceId": "b524c3ab",
   "data": {
    "path": "/atem/preview/3",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "1bacd69a"
  },
  {
   "deviceId": "b524c3ab",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/3",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "abb499f1"
  },
  {
   "deviceId": "b524c3ab",
   "data": {
    "path": "/atem/program/3",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "be7b2460"
  },
  {
   "deviceId": "b524c3ab",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/3",
    "args": "0"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "ad6dab1d"
  },
  {
   "deviceId": "440ff2a9",
   "data": {
    "path": "/atem/preview/4",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "974e6334"
  },
  {
   "deviceId": "440ff2a9",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/4",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "6e5f493c"
  },
  {
   "deviceId": "440ff2a9",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/4",
    "args": "1"
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "9ac36827"
  },
  {
   "deviceId": "440ff2a9",
   "data": {
    "ip": "<IP_ADDRESS>",
    "path": "/atem/program/4",
    "args": "0",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "529f0624"
  },
  {
   "deviceId": "7cf49038",
   "data": {
    "path": "/atem/preview/5",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "74178995"
  },
  {
   "deviceId": "7cf49038",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/5",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "0b74f396"
  },
  {
   "deviceId": "7cf49038",
   "data": {
    "port": 7777,
    "ip": "<IP_ADDRESS>",
    "path": "/atem/program/5",
    "args": "1"
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "2663fcbe"
  },
  {
   "deviceId": "7cf49038",
   "data": {
    "path": "/atem/program/5",
    "args": "0",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "573b37c4"
  },
  {
   "deviceId": "76f76a88",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/6",
    "args": "1"
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "219dec80"
  },
  {
   "deviceId": "76f76a88",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/6",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "70617f71"
  },
  {
   "deviceId": "76f76a88",
   "data": {
    "ip": "<IP_ADDRESS>",
    "path": "/atem/program/6",
    "args": "1",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "f79ccc6a"
  },
  {
   "deviceId": "76f76a88",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/6",
    "args": "0"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "b46c276c"
  },
  {
   "deviceId": "22703db1",
   "data": {
    "path": "/atem/preview/7",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "9f2ca4e8"
  },
  {
   "deviceId": "22703db1",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/7",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "8747d524"
  },
  {
   "deviceId": "22703db1",
   "data": {
    "path": "/atem/program/7",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "b1ca21f5"
  },
  {
   "deviceId": "22703db1",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/7",
    "args": "0"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "c1a9f3d4"
  },
  {
   "deviceId": "9b6a3778",
   "data": {
    "path": "/atem/preview/8",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "e393251c",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "cae88439"
  },
  {
   "deviceId": "9b6a3778",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/preview/8",
    "args": "0"
   },
   "busId": "e393251c",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "dc150e66"
  },
  {
   "deviceId": "9b6a3778",
   "data": {
    "path": "/atem/program/8",
    "args": "1",
    "ip": "<IP_ADDRESS>",
    "port": 7777
   },
   "busId": "334e4eda",
   "active": true,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "d0795722"
  },
  {
   "deviceId": "9b6a3778",
   "data": {
    "ip": "<IP_ADDRESS>",
    "port": 7777,
    "path": "/atem/program/8",
    "args": "0"
   },
   "busId": "334e4eda",
   "active": false,
   "outputTypeIdx": "8",
   "outputTypeId": "58da987d",
   "id": "0988ed4d"
  }
 ],
 "tsl_clients": [],
 "tsl_clients_1secupdate": false,
 "cloud_destinations": [],
 "cloud_keys": []
}

Relevant log output
20:49:14.763 -> [SIoC] trigger event device_states
20:49:14.763 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:14.763 -> The device is in program.
20:49:14.834 -> [SIoC] trigger event device_states
20:49:14.834 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:14.834 -> The device is in program.
20:49:14.903 -> [SIoC] trigger event device_states
20:49:14.903 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:14.937 -> The device is in program.
20:49:14.973 -> [SIoC] trigger event device_states
20:49:14.973 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.011 -> The device is in program.
20:49:15.045 -> [SIoC] trigger event device_states
20:49:15.045 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.081 -> The device is in program.
20:49:15.114 -> [SIoC] trigger event device_states
20:49:15.114 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.148 -> The device is in program.
20:49:15.185 -> [SIoC] trigger event device_states
20:49:15.185 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.223 -> The device is in program.
20:49:15.262 -> [SIoC] trigger event device_states
20:49:15.262 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.295 -> The device is in program.
20:49:15.331 -> [SIoC] trigger event device_states
20:49:15.331 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.365 -> The device is in program.
20:49:15.402 -> [SIoC] trigger event device_states
20:49:15.402 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.437 -> The device is in program.
20:49:15.472 -> [SIoC] trigger event device_states
20:49:15.472 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.510 -> The device is in program.
20:49:15.547 -> [SIoC] trigger event device_states
20:49:15.547 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.585 -> The device is in program.
20:49:15.620 -> [SIoC] trigger event device_states
20:49:15.620 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.658 -> The device is in program.
20:49:15.691 -> [SIoC] trigger event device_states
20:49:15.691 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.726 -> The device is in program.
20:49:15.760 -> [SIoC] trigger event device_states
20:49:15.760 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.798 -> The device is in program.
20:49:15.836 -> [SIoC] trigger event device_states
20:49:15.836 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.874 -> The device is in program.
20:49:15.910 -> [SIoC] trigger event device_states
20:49:15.910 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:15.946 -> The device is in program.
20:49:15.984 -> [SIoC] trigger event device_states
20:49:15.984 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.018 -> The device is in program.
20:49:16.056 -> [SIoC] trigger event device_states
20:49:16.090 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.090 -> The device is in program.
20:49:16.154 -> [SIoC] trigger event device_states
20:49:16.154 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.154 -> The device is in program.
20:49:16.204 -> [SIoC] trigger event device_states
20:49:16.204 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.242 -> The device is in program.
20:49:16.280 -> [SIoC] trigger event device_states
20:49:16.280 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.318 -> The device is in program.
20:49:16.353 -> [SIoC] trigger event device_states
20:49:16.353 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.387 -> The device is in program.
20:49:16.425 -> [SIoC] trigger event device_states
20:49:16.425 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.463 -> The device is in program.
20:49:16.500 -> [SIoC] trigger event device_states
20:49:16.500 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.536 -> The device is in program.
20:49:16.573 -> [SIoC] trigger event device_states
20:49:16.573 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.607 -> The device is in program.
20:49:16.642 -> [SIoC] trigger event device_states
20:49:16.642 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.679 -> The device is in program.
20:49:16.716 -> [SIoC] trigger event device_states
20:49:16.750 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.750 -> The device is in program.
20:49:16.789 -> [SIoC] trigger event device_states
20:49:16.789 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.822 -> The device is in program.
20:49:16.894 -> [SIoC] trigger event device_states
20:49:16.894 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.894 -> The device is in program.
20:49:16.932 -> [SIoC] trigger event device_states
20:49:16.970 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:16.970 -> The device is in program.
20:49:17.004 -> [SIoC] trigger event device_states
20:49:17.042 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.042 -> The device is in program.
20:49:17.109 -> [SIoC] trigger event device_states
20:49:17.109 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.109 -> The device is in program.
20:49:17.181 -> [SIoC] trigger event device_states
20:49:17.181 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.181 -> The device is in program.
20:49:17.249 -> [SIoC] trigger event device_states
20:49:17.249 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.249 -> The device is in program.
20:49:17.323 -> [SIoC] trigger event device_states
20:49:17.323 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.359 -> The device is in program.
20:49:17.393 -> [SIoC] trigger event device_states
20:49:17.393 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.431 -> The device is in program.
20:49:17.465 -> [SIoC] trigger event device_states
20:49:17.465 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.503 -> The device is in program.
20:49:17.537 -> [SIoC] trigger event device_states
20:49:17.537 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.575 -> The device is in program.
20:49:17.612 -> [SIoC] trigger event device_states
20:49:17.612 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.646 -> The device is in program.
20:49:17.685 -> [SIoC] trigger event device_states
20:49:17.685 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.718 -> The device is in program.
20:49:17.757 -> [SIoC] trigger event device_states
20:49:17.757 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.790 -> The device is in program.
20:49:17.828 -> [SIoC] trigger event device_states
20:49:17.828 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.863 -> The device is in program.
20:49:17.901 -> [SIoC] trigger event device_states
20:49:17.901 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:17.939 -> The device is in program.
20:49:17.977 -> [SIoC] trigger event device_states
20:49:17.977 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.015 -> The device is in program.
20:49:18.049 -> [SIoC] trigger event device_states
20:49:18.049 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.083 -> The device is in program.
20:49:18.118 -> [SIoC] trigger event device_states
20:49:18.118 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.151 -> The device is in program.
20:49:18.190 -> [SIoC] trigger event device_states
20:49:18.190 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.223 -> The device is in program.
20:49:18.257 -> [SIoC] trigger event device_states
20:49:18.257 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.291 -> The device is in program.
20:49:18.325 -> [SIoC] trigger event device_states
20:49:18.325 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[],"linkedSources":[],"active":false},{"deviceId":"54546b2b","busId":"334e4eda","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true}]
20:49:18.364 -> The device is in program.
20:49:18.402 -> [SIoC] trigger event device_states
20:49:18.402 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true},{"deviceId":"54546b2b","busId":"334e4eda","sources":[],"linkedSources":[],"active":false}]
20:49:18.440 -> The device is in preview.
20:49:18.476 -> [SIoC] trigger event device_states
20:49:18.476 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true},{"deviceId":"54546b2b","busId":"334e4eda","sources":[],"linkedSources":[],"active":false}]
20:49:18.513 -> The device is in preview.
20:49:18.552 -> [SIoC] trigger event device_states
20:49:18.552 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true},{"deviceId":"54546b2b","busId":"334e4eda","sources":[],"linkedSources":[],"active":false}]
20:49:18.589 -> The device is in preview.
20:49:18.627 -> [SIoC] trigger event device_states
20:49:18.627 -> Socket Message DeviceStates: [{"deviceId":"54546b2b","busId":"e393251c","sources":[{"sourceId":"0f528128","address":"1"}],"linkedSources":[],"active":true},{"deviceId":"54546b2b","busId":"334e4eda","sources":[],"linkedSources":[],"active":false}]
20:49:18.666 -> The device is in preview.

Error stacktrace (if applicable)
No response

hi,
the tally arbiter log does not show anything weird, only that tally is switching from prv to pgm or something (can not check it right now), but really only one line in log (not 20+....)


Fixup internal documentation

There were some faults that got caught by the updated doc-nits

Merged.
4ce738d083a377e0788e5d6cf92e3756d436b2f4 Fixup internal documentation


[WFLY-14815] Fix ForwardedHandlerTestCase to comply with UNDERTOW-1837

Issue: https://issues.redhat.com/browse/WFLY-14815

Thanks; this change was pulled into the other PR and merged.


python312Packages.pyswitchbot: add pytest-asyncio

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354911

x86_64-linux

:white_check_mark: 6 packages built:

home-assistant-component-tests.shelly
home-assistant-component-tests.switchbot
python311Packages.pyswitchbot
python311Packages.pyswitchbot.dist
python312Packages.pyswitchbot
python312Packages.pyswitchbot.dist


The final model

I tested your road_mapper_final.h5 in test datasets, the output showed a blank image. Did you upload your trained parameters? or we need to train the model by ourselves?

Yes, I had uploaded the complete model and you can start testing with the model I uploaded.
Please Use the following code to load the model.
from keras.models import load_model
model = load_model("./Models/road_mapper_final.h5", custom_objects={'soft_dice_loss': soft_dice_loss, 'iou_coef': iou_coef})

You will have to define and load the custom losses to get predictions. Do let me know if this doesn't work.
Thank you.

now this is a terrible question but how do i test it with my own images?

i have defined the two functions in your code , before the load_model , but its still complaining that :
 ValueError: Unknown loss function:dice_coef_loss

I managed to run the code with the given model. You can use the below script. However, Im not 100% sure this is the right way to do.
def iou_coef(y_true, y_pred, smooth=1):
    intersection = K.sum(K.abs(y_true * y_pred), axis=[1, 2, 3])
    union = K.sum(y_true, [1, 2, 3]) + K.sum(y_pred, [1, 2, 3]) - intersection
    iou = K.mean((intersection + smooth) / (union + smooth), axis=0)

    return iou

def dice_coef_loss(y_true, y_pred, smooth=1):
    y_true_f = K.flatten(y_true)
    y_pred_f = K.flatten(y_pred)
    intersection = K.sum(y_true_f * y_pred_f)
    return (2. * intersection + smooth) / (K.sum(y_true_f) + K.sum(y_pred_f) + smooth)

def soft_dice_loss(y_true, y_pred):
    return 1 - dice_coef_loss(y_true, y_pred)

model = load_model("../Models/road_mapper_2.h5",
                   custom_objects={'soft_dice_loss': soft_dice_loss, 'iou_coef': iou_coef,
                                   "dice_coef_loss": dice_coef_loss, "dice_loss": dice_coef_loss})

Hi!
When trying to load de model I get this error:
'OSError: Unable to open file (file signature not found)' related with h5 file.
Searching around the most common source of this error is a bad or corrupt file. Anyone had the same error? Any hints?
Thanks in advance.

I tested your road_mapper_final.h5 in test datasets, the output showed a blank image. Did you upload your trained parameters? or we need to train the model by ourselves?

Hey, I am also facing the same problem, were you able to solve it. Please help me out

Sorry, I have not tried to make it work after I had placed the question.
Good luck.
El jue, 23 sept 2021 a las 23:36, AakashRana000q  (<

) escribió:

Preview: > I tested your road_mapper_final.h5 in test datasets, the ou -->
SPAM? CLICK to BLOCK
@.***/>
This email is Masked using Blur - it was sent from github.com to
@.*** (your reply stays Masked). To protect your privacy
https://www.abine.com/faq.html#caniaddcc, do not forward this message,
or add new recipients like CCs or BCCs.
Thanks for being a Blur customer! If you haven't yet, [ Try DeleteMe at a
discount.
https://joindeleteme.com/?utm_source=blur&utm_medium=email&utm_campaign=blur-offer
]
I tested your road_mapper_final.h5 in test datasets, the output showed a
blank image. Did you upload your trained parameters? or we need to train
the model by ourselves?
Hey, I am also facing the same problem, were you able to solve it. Please
help me out
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Paulymorphous/skeyenet/issues/7#issuecomment-926181271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIRIMQ5JCFH74WEMJVPJXPLUDOMTJANCNFSM4NEPGA5A
.
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.


zsh completion fails

I'm trying to generate the zsh completion in my build.rs file, using clap 2.16.2:
extern crate clap;
use clap::Shell;
include!("src/cli/mod.rs");

fn main() {
    let mut app = build();
    app.gen_completions("fcy", Shell::Fish, env!("OUT_DIR"));
    app.gen_completions("fcy", Shell::Bash, env!("OUT_DIR"));
    app.gen_completions("fcy", Shell::Zsh, env!("OUT_DIR"));
}

But the last line makes the build fail (bash and fish work fine):
➜ ~ rustc -V
rustc 1.14.0-nightly (c59cb71d9 2016-10-26)
➜ ~ cargo -V
cargo 0.13.0-nightly (806e3c3 2016-10-26)
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:
Release:        15.10
Codename:       wily

➜  ~ cargo build
error: failed to run custom build command for `fcy v0.0.4 (file:///home/nicompte/Repository/fcy2)`
process didn't exit successfully: `/home/nicompte/Repository/fcy2/target/debug/build/fcy-f49762e438fa7f28/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Fatal internal error. Please consider filing a bug report at https://github.com/kbknapp/clap-rs/issues', ../src/libcore/option.rs:705
stack backtrace:
   1:     0x55f781151248 - std::sys::backtrace::tracing::imp::write::h22f199c1dbb72ba2
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2:     0x55f78115478f - std::panicking::default_hook::{{closure}}::h9a389c462b6a22dd
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:247
   3:     0x55f7811536c6 - std::panicking::default_hook::h852b4223c1c00c59
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:263
   4:     0x55f781153cb7 - std::panicking::rust_panic_with_hook::hcd9d05f53fa0dafc
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:451
   5:     0x55f781153b44 - std::panicking::begin_panic::hf6c488cee66e7f17
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:413
   6:     0x55f781153a69 - std::panicking::begin_panic_fmt::hb0a7126ee57cdd27
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:397
   7:     0x55f7811539f7 - rust_begin_unwind
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:373
   8:     0x55f7811896bd - core::panicking::panic_fmt::h9af671b78898cdba
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/panicking.rs:69
   9:     0x55f78118972d - core::option::expect_failed::hafc66854f3459293
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/option.rs:705
  10:     0x55f7811085c3 - <core::option::Option<T>>::expect::he1fa75a7269dfe51
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/option.rs:293
  11:     0x55f7811448c7 - clap::completions::zsh::parser_of::h63d4971053837895
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:230
  12:     0x55f7811441e4 - clap::completions::zsh::get_subcommands_of::h6ccc5a8cc84ec3fe
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:202
  13:     0x55f7811442c7 - clap::completions::zsh::get_subcommands_of::h6ccc5a8cc84ec3fe
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:206
  14:     0x55f781142b22 - clap::completions::zsh::ZshGen::generate_to::hd24ded8070bf9d5e
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:28
  15:     0x55f781147081 - clap::completions::ComplGen::generate::h68568c315fd58ac4
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/mod.rs:33
  16:     0x55f7811341e9 - clap::app::parser::Parser::gen_completions_to::ha9762178a111456c
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/app/parser.rs:112
  17:     0x55f781134811 - clap::app::parser::Parser::gen_completions::hf325b7a19d4d643c
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/app/parser.rs:132
  18:     0x55f7810f2a01 - clap::app::App::gen_completions::h413df50734488193
                        at /home/nicompte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/app/mod.rs:1128
  19:     0x55f7810f9337 - build_script_build::main::h42d67b06b82522fd
                        at /home/nicompte/Repository/fcy2/build.rs:11
  20:     0x55f78115c26a - __rust_maybe_catch_panic
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libpanic_unwind/lib.rs:97
  21:     0x55f781152f1a - std::rt::lang_start::h14cbded5fe3cd915
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:332
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panic.rs:311
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/rt.rs:57
  22:     0x55f7810fc2a3 - main
  23:     0x7fb84ee5fabf - __libc_start_main
  24:     0x55f7810f0e18 - _start
  25:                0x0 - <unknown>

And with the debug feature, if that's the way to get more information:
error[E0382]: use of moved value: `s`
   --> /home/nbarbotte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:311:38
    |
310 |             ret.push(s);
    |                      - value moved here
311 |             debugln!("Wrote...{}", &*s);
    |             -------------------------^--
    |             |                        |
    |             |                        value used here after move
    |             in this macro invocation
    |
    = note: move occurs because `s` has type `std::string::String`, which does not implement the `Copy` trait

error[E0382]: use of moved value: `l`
   --> /home/nbarbotte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:322:38
    |
321 |             ret.push(l);
    |                      - value moved here
322 |             debugln!("Wrote...{}", &*l);
    |             -------------------------^--
    |             |                        |
    |             |                        value used here after move
    |             in this macro invocation
    |
    = note: move occurs because `l` has type `std::string::String`, which does not implement the `Copy` trait

error[E0382]: use of moved value: `s`
   --> /home/nbarbotte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:347:38
    |
346 |             ret.push(s);
    |                      - value moved here
347 |             debugln!("Wrote...{}", &*s);
    |             -------------------------^--
    |             |                        |
    |             |                        value used here after move
    |             in this macro invocation
    |
    = note: move occurs because `s` has type `std::string::String`, which does not implement the `Copy` trait

error[E0382]: use of moved value: `l`
   --> /home/nbarbotte/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.16.2/src/completions/zsh.rs:358:38
    |
357 |             ret.push(l);
    |                      - value moved here
358 |             debugln!("Wrote...{}", &*l);
    |             -------------------------^--
    |             |                        |
    |             |                        value used here after move
    |             in this macro invocation
    |
    = note: move occurs because `l` has type `std::string::String`, which does not implement the `Copy` trait

error: aborting due to 4 previous errors

Any idea of how I could fix it?

Thanks for posting all these details!
The debug feature appears to be having an issue of it's own :stuck_out_tongue_winking_eye: I just fixed this and pushed it to the master branch.
Could you do me a quick favor and change your Cargo.toml to:
clap = {git = "https://github.com/kbknapp/clap-rs.git", features = ["debug"]}

Then re-run it and post the debug output? This should be an easy fix!

Thank you for your answer!
Here it is, on macOs this time. It is quite long though :)
debug.txt

@nicompte Thanks!
It looks like it's failing to locate the subcommand logs for some reason. Do you have a link to the source, so I can see how you declared that subcommand?

Unfortunately this project is not open source, I can show you how it's constructed though.
The idea is that the logs subcommand is used at several places and is the subcommand of other subcommands, so you can use fcy api logs and fcy front logs. Both the api and front use the same function to get their logs subcommand.
But their is no fcy logs, it's always under a subcommand.
(probably not compiling code)
// log subcommand builder
pub fn logs_build() -> App<'static, 'static> {
    SubCommand::with_name(LOG)
        .about("log")
        .alias(LOGS)
        .alias(TAIL)
       // other options
}

// the two subcommands that use logs, like `fcy api logs`
pub fn build_api() -> App<'static, 'static> {
    SubCommand::with_name(API)
        .setting(AppSettings::SubcommandRequiredElseHelp)
        .about("api")
        .subcommand(logs_build())
       // other subcommands
}
pub fn build_front() -> App<'static, 'static> {
    SubCommand::with_name(FRONT)
        .setting(AppSettings::SubcommandRequiredElseHelp)
        .about("front")
        .subcommand(logs_build())
       // other subcommands
}

// cli creation
App::new("fcy")
        .setting(AppSettings::DeriveDisplayOrder)
        .setting(AppSettings::SubcommandRequiredElseHelp)
        .global_setting(AppSettings::ColoredHelp)
        .global_setting(AppSettings::VersionlessSubcommands)
        .version(env!("CARGO_PKG_VERSION"))
        .author(env!("CARGO_PKG_AUTHORS"))
        .about(env!("CARGO_PKG_DESCRIPTION"))
        .version_short("v")

        .subcommand(build_api())
        .subcommand(build_front())
        // other subcommands

Hope that helps, I'll try removing/adding some parts of my code to see when/where it fails.

Ok it went faster than I expected, the problem seems to be the aliases of the logs subcommand, it works when I remove them.

Oh wow, thanks for the detailed look! Ok, so then it may be aliases that's the actual bug. Let me do some testing on my local machine and see if I can either reproduce the issue, or come up with a test case to get this fixed for you.

Alright I've reproduced the issue, and it is in fact due to aliases. Once I have the fix, I'll post back here.

@kbknapp: it works fine on the latest version, thanks for your quick fix and all your work on clap 👍


[Comment to proycon-merge]

Looks nice.
I would prefer to leave the tabs for sig, pilot and pos. It is easier to read and work with in a small IGB.
Also I would like to have the Bulk import form below the sig's.
Otherwise a successful change.

Looks good and zen mode rocks.
Thoughts:

Starbase Details should be a separate page entirely. This info isn't needed as often, some systems have many POSes, page load time and page length both push this item into a separate page accessible from the
Red occupied/towers box on system details should default to max of ~10 lines and have a more link to expand if it exceeds 10 lines.
Move bulk import below sigs as suggested

Regarding the tabs versus pages, I think it's probably best to make it user-configurable, as one style simply won't suit all..

I merged the big PR in tonight with changes to make map settings configurable on a per-user and global-default basis.
@proycon Let me know when you want me to merge in your changes from this issue or make another PR for it. Thanks for contributing your hard work to the project.

Thanks for the merge! I'll do another pull request with the newest features (map overlap, rudimentary pos db view) soon

I've tested the new merge (as I could) and i'm pleased with the new look.
THX


How to mock requests to custom endpoints in integration test

Hi,
Here is the use case:
Trying to test a component that uses the google place autocomplete.
I need to mock the auth and query requests.
For some reason, in the integration test, mockJax does not seem to match any requests when a handler is created directly through the mockJax global.
We've tried using $.mockJax and Ember.$.mockJax.
Neither intercept any of the requests.
Any ideas?
Thanks

maybe simple as this:
    let widget = this.build('widget', 'withExtras').get();
    Ember.$.mockjax({ url: `/my/custom/widget`, responseText: widget, type: 'GET' });

as in ( lowercase the mockjax )

did this work for you?

Thank you. I haven't had a chance to try it yet since we skipped that test for now. Will close and keep you posted once I try it out.
Thanks again


EncryptionPropertiesFactory and DecryptionPropertiesFactory

This JIRA is an extension to Parquet Modular Encryption Jira(PARQUET-1178) that will provide the basic building blocks and APIs for the encryption support.
This JIRA provides a crypto data interface for schema activation of Parquet encryption and serves as a high-level layer on top of PARQUET-1178 to make the adoption of Parquet-1178 easier, with pluggable key access module, without a need to use the low-level encryption APIs. Also, this feature will enable seamless integration with existing clients.
No change to specifications (Parquet-format), no new Parquet APIs, and no changes in existing Parquet APIs. All current applications, tests, etc, will work.
From developer perspective, they can just implement the interface into a plugin which can be attached any Parquet application like Hive/Spark etc. This decouples the complexity of dealing with KMS and schema from Parquet applications. In large organization, they may have hundreds or even thousands of Parquet applications and pipelines. The decoupling would make Parquet encryption easier to be adopted.
From end user(for example data owner) perspective, if they think a column is sensitive, they can just set that column’s schema as sensitive and then the Parquet application just encrypt that column automatically. This makes end user easy to manage the encryptions of their columns.
Reporter: Xinli Shang / @shangxinli
Assignee: Xinli Shang / @shangxinli
Related issues:

High-level flexible and fine-grained column level access control through encryption with pluggable key access (Blocked)
Passing Field Metadata to Parquet (Blocked)
Sample of usage Parquet-1396 and Parquet-1178 for column level encryption with pluggable key access (Blocked)
High level interface to Parquet encryption (is depended upon by)

Externally tracked issue: https://issues.apache.org/jira/browse/PARQUET-1178
PRs and other links:

GitHub Pull Request #764
https://docs.google.com/document/d/17GTQAezl1ZC1pMNHjYU_bPVxMU6DIPjtXOiLclXUlyA/edit#heading=h.r9wntu3s8swd

Note: This issue was originally created as PARQUET-1396. Please see the migration documentation for further details.

Xinli Shang / @shangxinli:
Design of Parquet-1396

Xinli Shang / @shangxinli:
This is the design of Parquet-1396.

Xinli Shang / @shangxinli:
Most of the functionality of this Jira has been addressed by "PARQUET-1817: Crypto Properties Factory". Hence change the name of this Jira to 'Example of Using EncryptionPropertiesFactory/DecryptionPropertiesFactory.

Gabor Szadovszky / @gszadovszky:
As it is related to encryption which is not targeted to 1.11.0 I'm removing target from here.


[File Highlight] support adding a link in some corner of the code block for downloading

It would be nice if File Highlight can insert an additional download link for readers to download the original file that prism.js displays.

@Golmote I'm not seeing the download link on the linked page.

@mAAdhaTTah On the last example? I can see it working properly...

Yeah, looks like this in the Chrome devtools:

Toolbar doesn't have anything in it. :/

@mAAdhaTTah I've just fixed an issue in cd22499c363bcdc6a290b77d271516886dad130f, but it seems totally unrelated to the issue you're showing there.
I don't get it, I can't reproduce the issue on neither Firefox nor Chrome. Are you sure you don't have some sort of browser cache or something?

Weird... let me clone the repo locally and dig into it.

@mAAdhaTTah Did you find anything? :worried:

Haven't had a chance to dig into it–just moved into a new place. It's on my todo list tho.


perf(plugins-iterator) only loop through configured plugins

Summary
This time the plugin iteration is optimized on pre-proxy phases so that we do not loop through all the loaded plugins but only through the configured plugins.
It also uses table.clear and table.new when creating the plugins context table for post-proxy phases to avoid table resizes.

Beats the master in all tests, especially the last that this is designed to improve the most.
### Combined result for Kong git:7df13cf5a539a5ea5c6d3f5e37b623625ed5a94e:
RPS     Avg: 104563.16
Latency Avg: 1.66ms    Max: 125.91ms
### Combined result for Kong git:master:
RPS     Avg: 101330.91
Latency Avg: 1.55ms    Max: 112.74ms

### Combined result for Kong git:7df13cf5a539a5ea5c6d3f5e37b623625ed5a94e:
RPS     Avg: 97927.20
Latency Avg: 1.41ms    Max: 86.39ms
### Combined result for Kong git:master:
RPS     Avg: 96286.31
Latency Avg: 1.38ms    Max: 74.67ms

### Combined result for Kong git:7df13cf5a539a5ea5c6d3f5e37b623625ed5a94e:
RPS     Avg: 77835.94
Latency Avg: 1.48ms    Max: 74.59ms
### Combined result for Kong git:master:
RPS     Avg: 72972.76
Latency Avg: 1.72ms    Max: 131.67ms


Add advanced diff similar to SlickEdit

Issue Type: Feature Request
Visual Studio Code diff tool is not nice to use as it is annoying to have to select open files that are already open to diff. In addition to this, it does not support comparing directories. In my case when I am trying to quickly find differences between two similar checkouts of software, I would like the diff tool to denote which files are different such that I can quickly analyze differences between those files. E.g. if I have two checkouts of the same software repository on two projects, SVN is annoying to deal with so a folder diff is easier to use to differentiate which files are different. While I could look at these differences in SVN, this is not always possible if someone has something floating around that has been changed but not committed.
The below screencap from slick edit is what the diff tool should look like. It should offer the user the ability to diff a file or directory directly from a seperate window instead of forcing the user to have the files open. Sometimes, I would like to just compare two files without opening them and only open them if I find a reason to edit.

VS Code version: Code 1.40.1 (8795a9889db74563ddd43eb0a897a2384129a619, 2019-11-13T16:49:35.976Z)
OS version: Windows_NT x64 10.0.18362

it is annoying to have to select open files that are already open to diff

This is supported and you can also compare two files from the command line, pls see https://www.meziantou.net/comparing-files-using-visual-studio-code.htm

it does not support comparing directories.

Pls try https://marketplace.visualstudio.com/items?itemName=moshfeu.compare-folders

@egamma

This is supported and you can also compare two files from the command line, pls see https://www.meziantou.net/comparing-files-using-visual-studio-code.htm

I know it suppports this. However, the entry to diff files is sometimes better with a GUI window instead of from the command line. I prefer the command line, but not everyone is like this and some people prefer using a GUI window to click to the desired files to diff.

@GlenNicholls - for me the context menu on any file in the Explorer tree (even one that I haven't opened) offers 'Select for Compare' and 'Compare with Selected'. So I'm not clear what you mean when you say you have to open the files first.

@gjsjohnmurray I understand that, but it only works easily if one of the files is already open, is in the same directory, or within a few levels of the hierarchy. This gets really tedious when you have to change drives to diff files, especially if you want to diff numerous files in those directories since folder diffing is not available. The point I am trying to make is that in some situations, the current method for diffing files simply is not enough. This is the same problem as the search interface, but that is a discussion for a different issue.

@egamma

Pls try https://marketplace.visualstudio.com/items?itemName=moshfeu.compare-folders

I found this before, but a feature like this is something that really should be supported out of the box by VSC. This is something that is used all the time for software development and should be directly supported by the IDE. All the big IDEs that I've used directly support more advanced search window and diffing.

I agree with @GlenNicholls: comparing two folders is really an essential feature.
I use it everyday with other IDEs.

By the way, I find that "L13 Diff" extension is way better than "compare-folders":
https://marketplace.visualstudio.com/items?itemName=L13RARY.l13-diff

Despite 2 extensions exist with such a feature, I would love "folder comparison" feature more integrated in IDE, that is to say, using the same way than "file comparison", with "Select for Compare" and "Compare with Selected" features.


NaN on average block time

Describe the bug
I'm running Big Dipper at https://testnet-finney-blocks.nymtech.net/
Everything looks great except for one thing: Average Block Time is showing as NaN.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://testnet-finney-blocks.nymtech.net/'
View the block time

Expected behavior
I expect that the block time will show as a float
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Linux
Browser: Chromium
Version: 89

Additional context
I must have a setting wrong, but I'm not quite sure what it is. Relevant settings might be:
    "remote": {
        "rpc": "https://testnet-finney-validator.nymtech.net",
        "api": "http://testnet-finney-validator.nymtech.net:1317"
    },

The rpc endpoint is nginx proxying 26657, see e.g. https://testnet-finney-validator.nymtech.net which shows all the normal rpc methods happily. I assume those are correct.
Having taken a look through the code (checked out at tag v0.41.x-7), there aren't that many places I would expect to get NaN. One is on line 355 of methods.js
                averageBlockTime = averageBlockTime / analytics.length;

There doesn't seem to be a if(analytics.length >0) guard on that as the other ones have, but then again the method name suggests it's just doing aggregations once a day (?) so that seems like it's not the culprit.
The other instances of this kind of code mostly do have a 0 guard.
            if (analytics.length > 0){
                for (i in analytics){
                    averageBlockTime += analytics[i].timeDiff;
                    averageVotingPower += analytics[i].voting_power;
                }
                averageBlockTime = averageBlockTime / analytics.length;

I have looked through mongo and I do have analytics in my collection. Intriguingly, only the first one has a number in it:
> db.analytics.find()
{ "_id" : "q9NASbvH326GRWfM3", "height" : 1, "precommits" : 0, "averageBlockTime" : 5000, "time" : "2021-03-22T18:13:48.525181843Z", "voting_power" : NaN }
{ "_id" : "KpdLpTxFvXeYBWqCJ", "height" : 2, "precommits" : 1, "averageBlockTime" : NaN, "timeDiff" : 1613251, "time" : "2021-03-22T18:40:41.776802991Z", "voting_power" : 1000 }
{ "_id" : "vk7qZoaywS2NqGt6d", "height" : 3, "precommits" : 1, "averageBlockTime" : NaN, "timeDiff" : 5018, "time" : "2021-03-22T18:40:46.794137623Z", "voting_power" : 1000 }
{ "_id" : "HyxPQcbaTbpYeufur", "height" : 4, "precommits" : 1, "averageBlockTime" : NaN, "timeDiff" : 5020, "time" : "2021-03-22T18:40:51.814339222Z", "voting_power" : 1000 }
{ "_id" : "DLXKfA76sXqY7svBh", "height" : 5, "precommits" : 1, "averageBlockTime" : NaN, "timeDiff" : 5024, "time" : "2021-03-22T18:40:56.838838681Z", "voting_power" : 1000 }

Starting a new local copy of Big Dipper at a non-zero initial block height also results in NaN here.
I really like Big Dipper by the way! Thanks for making it.

You have to set the genesis time in the settings.json. Something like:
"public":{
...
"genesisTime": "2021-03-25T01:00:14.268797802Z",
...

Setting the genesis time doesn't have no effect. They are still NaN.

Aha! Setting the genesisTime in settings.json worked perfectly (for me). Thanks @nebkas.

@futurechimp should this be closed?

Yes please! Close it, everything is working well.


Fix new-repo-disable-projects-and-wiki

Thanks for contributing! 🍄

LINKED ISSUES: none

TEST URLS: https://github.com/new

The new-repo-disable-projects-and-wiki feature was the only one passing an empty query string to api.v3(), which caused a trailing slash to appear at the end of the URL and resulted in a 404 error.

Just pass a slash instead of an empty string

Just pass a slash instead of an empty string in the feature

This won't work. We want 'repos/' + getRepo()!.nameWithOwner, not an empty URL.

Oh your right misunderstood the issue

Thanks @cheap-glitch


Use unsigned mul instead of signed imul

closes #20

Cherry-picked to entering_longmode, setup_rust, and printing_to_screen


[TRI-1333] [TRI-1332] Upgrade all packages/* and use fetch instead of node-fetch

Problem
Our packages currently support Node 16–17. This means we can't use fetch and we can't support some modern deployment platforms like Cloudflare/Vercel edge functions.
Node v18 is now LTS and v16 has entered "end-of-life" with no official support.
Solution

Set the engines.node property in all of the packages/*/package.json files.
Upgrade all packages/* to support Node v18.
Change fetch to node-fetch
Fix any other issues
Ensure that typechecking has no errors: pnpm run --filter "./packages/**" typecheck

From SyncLinear.com | TRI-1332
TRI-1333

I would like to work on this issue. please assign to me @matt-aitken

@matt-aitken I would like to work on this. Please assign this to me. Thanks.

Hi @matt-aitken I would like to upgrade all packages. Please assign it to me.

Something to be aware of
https://github.com/nodejs/undici


FI-2429: migrate to HL7 validator wrapper

Summary
Migrate to the HL7 validator wrapper:

Get rid of suite-specific environment variables & standardize to FHIR_RESOURCE_VALIDATOR_URL
As with previous test kits, left the old validator items commented out in case somebody wants to run the UI
Bump inferno_core version
Add the IG identifier to the generator
Add new ignore message
The spec tests don't seem to even run on main so I didn't spend much time looking at them here. From searching "validator" I saw one spot where the results had to be converted to an OO

Testing Guidance
Results for running the tests against the reference server should match the results running on prod today, eg: https://inferno.healthit.gov/suites/ipa_v100/2ui786dWYhN#2.2

I noticed that this doesn't work using ./run.sh so I fixed that.

FYI @vassilpeytchev -- we have recently updated some internal Inferno infrastructure to use a different 'service wrapper' to the HL7 FHIR validator. This requires a couple of minor changes to all Test Kits that would like to stay up-to-date with Inferno, which are in this PR.  There shouldn't be any changes to test behavior, except those that occur due to using a newer version of the HL7 FHIR Validator (as it adds new checks frequently from version-to-version).
I'm not sure if this affects you or not.  But I seem to recall you had your own fork that allowed you to add a header field -- so FYI.  Let me know if you have any questions, I'm happy to walk you through anything if you are having trouble.
Also, we don't have a very thorough IPA reference implementation to test against, so its not possible for me to be very thorough in ensuring that this update has no unintended effects.  Let me know if you see anything.
Thanks!


Add various types of sentence structures

https://medium.com/countdown-education/10-sentence-structure-types-you-should-recognize-with-examples-ebb198aca784

Do we want this to work behind the scenes with gofakeit.Sentence()?
or do we need a separate method for this
because I doubt developers in general we'll know about all the different types of sentences 😅

So currently I am building a better word list together, basically a more extensive list of specific types of verbs and nouns. Then ill put together a list of various sentence structures that people can use like gofakeit.SentenceSimple() and gofakeit.SentencePeriodic(). Then I will have gofakeit.Sentence() randomly pick between one of the sentence structures.

Added sentence simple


docs: update header, nav, landing page + add examples + deleting unused files

Updated the header to link back to the Portal site
Removed sidebar blue box link to docs site homepage
Deleted unused files
Added requirements for installation to the quick start page
Updated landing page copy and organization
Adds example code snippets from @uermel

Changes can be viewed in my branch of the docs site here: https://dgmccart.github.io/cryoet-data-portal/index.html

Manasa is correct, I was still using the list wrapper for safety due to the old client version. I will fix the gist files, too.

There was a bug in an old version that required adding the list wrapper, it has been fixed. So, we can make the code more concise by removing the list wrapper.

Thank you @manasaV3! I incorporated all of your code.


[Task] If activity is claimed, it updates all activities to claimed

Please can we check if this can be closed with the latest wallet.rs update?

Checked it when approving https://github.com/iotaledger/firefly/pull/4631. Works perfectly


Adding in the Criteo JavaScript sent to us by their integration team

Verification steps

Point Waldorf to local Rizzo
Bring up any page
Verify that a request is sent to the Criteo platform (see picture below)

Seems legit...


SonOff SNZB-02 - Multiple sensor support

I bought 2 SonOff SNZB-02 (Temperature Sensor).
The first pairing works, the sensor sends its data.
I add the second one, the pairing seems to work fine. Except that after a while the following error causes the server to crash
[01/06/2022, 13:12:46] [ZigBee] Cannot read properties of undefined (reading 'error')
[01/06/2022, 13:12:46] [ZigBee] Cannot read properties of undefined (reading 'error')
[01/06/2022, 13:14:12] TypeError: Cannot read properties of undefined (reading 'error')
at Object.configure (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman-converters/devices/sonoff.js:112:24)
[01/06/2022, 13:14:12] Got SIGTERM, shutting down Homebridge...
And it's a reboot loop, until I take one out.

Log:
[01/06/2022, 13:45:32] [ZigBee] Updating service 00000049-0000-1000-8000-0026BB765291 for device Lumière WC with state { state: 'OFF', temperature: 30 }
[01/06/2022, 13:45:32] [ZigBee] Updating service 00000089-0000-1000-8000-0026BB765291 for device Lumière WC with state { state: 'OFF', temperature: 30 }
[01/06/2022, 13:45:37] [ZigBee] Zigbee message from Sensor2 {
type: 'attributeReport',
device: Device {
ID: 4,
_type: 'EndDevice',
_ieeeAddr: '0x00124b00251ca8c7',
_networkAddress: 46407,
_manufacturerID: 0,
_endpoints: [ [Endpoint] ],
_manufacturerName: 'eWeLink',
_powerSource: 'Battery',
_modelID: 'TH01',
_applicationVersion: 5,
_stackVersion: undefined,
_zclVersion: 1,
_hardwareVersion: 1,
_dateCode: '20201026',
_softwareBuildID: undefined,
_interviewCompleted: true,
_interviewing: false,
_skipDefaultResponse: false,
_skipTimeResponse: false,
meta: {},
_lastSeen:<PHONE_NUMBER>910,
_defaultSendWhenActive: undefined,
useImplicitCheckin: true,
_linkquality: 98
},
endpoint: Endpoint {
ID: 1,
profileID: 260,
deviceID: 770,
inputClusters: [ 0, 3, 1026, 1029, 1 ],
outputClusters: [ 3 ],
deviceNetworkAddress: 46407,
deviceIeeeAddress: '0x00124b00251ca8c7',
clusters: {
genBasic: [Object],
genPowerCfg: [Object],
msTemperatureMeasurement: [Object],
msRelativeHumidity: [Object]
},
_binds: [ [Object], [Object], [Object] ],
_configuredReportings: [ [Object], [Object], [Object], [Object] ],
meta: {},
pendingRequests: [],
defaultSendWhenActive: undefined
},
data: { measuredValue: 2412 },
linkquality: 98,
groupID: 0,
cluster: 'msTemperatureMeasurement',
meta: {
zclTransactionSequenceNumber: 93,
manufacturerCode: null,
frameControl: {
frameType: 0,
manufacturerSpecific: false,
direction: 1,
disableDefaultResponse: true,
reservedBits: 0
}
}
}
[01/06/2022, 13:45:37] [ZigBee] Decoded state from incoming message { temperature: 24.12 }
[01/06/2022, 13:45:37] [ZigBee] Updating state of device Sensor2 with  { temperature: 24.12 }
[01/06/2022, 13:45:37] [ZigBee] Updated state for device Sensor2 is now  { temperature: 24.12 }
[01/06/2022, 13:45:37] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor2 with state { temperature: 24.12 }
[01/06/2022, 13:45:37] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor2 with state { temperature: 24.12 }
[01/06/2022, 13:45:37] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor2 with state { temperature: 24.12 }
[01/06/2022, 13:45:42] [ZigBee] Cannot read properties of undefined (reading 'error')
{"batteryLevel":100,"charging":true,"cleaning":false,"fanSpeed":102} | Props {"state":"charging","batteryLevel":100,"cleanTime":2136,"cleanArea":38.4175,"fanSpeed":102,"in_cleaning":0,"mainBrushWorkTime":44635,"sideBrushWorkTime":44635,"filterWorkTime":44635,"sensorDirtyTime":12306,"waterBoxMode":202,"autoDustCollection":1,"dustCollectionStatus":0}
[01/06/2022, 13:46:04] TypeError: Cannot read properties of undefined (reading 'error')
at Object.configure (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman-converters/devices/sonoff.js:112:24)

I think I found the cause. I have removed all SonOff sensor and add again and no more crash but :

When I add Sensor2 everything work
When I add Sensor1, pairing work but i don't have data. And if you look the log behind, you can see it's the same "service ID" than sensor 2 "00000096-0000-1000-8000-0026BB765291"

[01/06/2022, 14:17:02] [ZigBee] Zigbee: allowing new devices to join.
[01/06/2022, 14:17:08] [ZigBee] Accepting joining whitelisted device '0x00124b00251c9510'
[01/06/2022, 14:17:08] [ZigBee] Device joined, Adding Sensor1 (eWeLink - TH01)
[01/06/2022, 14:17:08] [ZigBee] Not initializing device Sensor1: already mapped in Homebridge
[01/06/2022, 14:17:08] [ZigBee] Updating state of device Sensor1 with  {}
[01/06/2022, 14:17:08] [ZigBee] Updated state for device Sensor1 is now  { temperature: 0 }
[01/06/2022, 14:17:08] [ZigBee] No need to configure device Sensor1
[01/06/2022, 14:17:08] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:08] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:08] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:09] [ZigBee] Interview progress started for device Sensor1
[01/06/2022, 14:17:09] [ZigBee] Device announce: Sensor1 (eWeLink - TH01)
[01/06/2022, 14:17:09] [ZigBee] Not initializing device Sensor1: interview process still not completed
[01/06/2022, 14:17:10] [ZigBee] Zigbee message from Sensor1 {
type: 'readResponse',
device: Device {
ID: 5,
_type: 'EndDevice',
_ieeeAddr: '0x00124b00251c9510',
_networkAddress: 56302,
_manufacturerID: 0,
_endpoints: [ [Endpoint] ],
_manufacturerName: 'eWeLink',
_powerSource: 'Battery',
_modelID: 'TH01',
_applicationVersion: 5,
_stackVersion: undefined,
_zclVersion: 1,
_hardwareVersion: 1,
_dateCode: '20201026',
_softwareBuildID: undefined,
_interviewCompleted: false,
_interviewing: true,
_skipDefaultResponse: false,
_skipTimeResponse: false,
meta: {},
_lastSeen:<PHONE_NUMBER>324,
_defaultSendWhenActive: undefined,
useImplicitCheckin: true,
_linkquality: 69,
_deleted: false
},
endpoint: Endpoint {
ID: 1,
profileID: 260,
deviceID: 770,
inputClusters: [ 0, 3, 1026, 1029, 1 ],
outputClusters: [ 3 ],
deviceNetworkAddress: 56302,
deviceIeeeAddress: '0x00124b00251c9510',
clusters: { genBasic: [Object] },
_binds: [],
_configuredReportings: [],
meta: {},
pendingRequests: [],
defaultSendWhenActive: false
},
data: { modelId: 'TH01', manufacturerName: 'eWeLink' },
linkquality: 69,
groupID: 0,
cluster: 'genBasic',
meta: {
zclTransactionSequenceNumber: 59,
manufacturerCode: null,
frameControl: {
frameType: 0,
manufacturerSpecific: false,
direction: 1,
disableDefaultResponse: true,
reservedBits: 0
}
}
}
[01/06/2022, 14:17:10] [ZigBee] Decoded state from incoming message {}
[01/06/2022, 14:17:10] [ZigBee] Updating state of device Sensor1 with  {}
[01/06/2022, 14:17:10] [ZigBee] Updated state for device Sensor1 is now  { temperature: 0 }
[01/06/2022, 14:17:10] [ZigBee] No need to configure device Sensor1
[01/06/2022, 14:17:10] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:10] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:10] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Zigbee message from Sensor1 {
type: 'readResponse',
device: Device {
ID: 5,
_type: 'EndDevice',
_ieeeAddr: '0x00124b00251c9510',
_networkAddress: 56302,
_manufacturerID: 0,
_endpoints: [ [Endpoint] ],
_manufacturerName: 'eWeLink',
_powerSource: 'Battery',
_modelID: 'TH01',
_applicationVersion: 5,
_stackVersion: undefined,
_zclVersion: 1,
_hardwareVersion: 1,
_dateCode: '20201026',
_softwareBuildID: undefined,
_interviewCompleted: false,
_interviewing: true,
_skipDefaultResponse: false,
_skipTimeResponse: false,
meta: {},
_lastSeen:<PHONE_NUMBER>042,
_defaultSendWhenActive: undefined,
useImplicitCheckin: true,
_linkquality: 65,
_deleted: false
},
endpoint: Endpoint {
ID: 1,
profileID: 260,
deviceID: 770,
inputClusters: [ 0, 3, 1026, 1029, 1 ],
outputClusters: [ 3 ],
deviceNetworkAddress: 56302,
deviceIeeeAddress: '0x00124b00251c9510',
clusters: { genBasic: [Object] },
_binds: [],
_configuredReportings: [],
meta: {},
pendingRequests: [],
defaultSendWhenActive: false
},
data: { stackVersion: undefined },
linkquality: 65,
groupID: 0,
cluster: 'genBasic',
meta: {
zclTransactionSequenceNumber: 60,
manufacturerCode: null,
frameControl: {
frameType: 0,
manufacturerSpecific: false,
direction: 1,
disableDefaultResponse: true,
reservedBits: 0
}
}
}
[01/06/2022, 14:17:12] [ZigBee] Decoded state from incoming message {}
[01/06/2022, 14:17:12] [ZigBee] Updating state of device Sensor1 with  {}
[01/06/2022, 14:17:12] [ZigBee] Updated state for device Sensor1 is now  { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] No need to configure device Sensor1
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Zigbee message from Sensor1 {
type: 'readResponse',
device: Device {
ID: 5,
_type: 'EndDevice',
_ieeeAddr: '0x00124b00251c9510',
_networkAddress: 56302,
_manufacturerID: 0,
_endpoints: [ [Endpoint] ],
_manufacturerName: 'eWeLink',
_powerSource: 'Battery',
_modelID: 'TH01',
_applicationVersion: 5,
_stackVersion: undefined,
_zclVersion: 1,
_hardwareVersion: 1,
_dateCode: '20201026',
_softwareBuildID: undefined,
_interviewCompleted: false,
_interviewing: true,
_skipDefaultResponse: false,
_skipTimeResponse: false,
meta: {},
_lastSeen:<PHONE_NUMBER>697,
_defaultSendWhenActive: undefined,
useImplicitCheckin: true,
_linkquality: 72,
_deleted: false
},
endpoint: Endpoint {
ID: 1,
profileID: 260,
deviceID: 770,
inputClusters: [ 0, 3, 1026, 1029, 1 ],
outputClusters: [ 3 ],
deviceNetworkAddress: 56302,
deviceIeeeAddress: '0x00124b00251c9510',
clusters: { genBasic: [Object] },
_binds: [],
_configuredReportings: [],
meta: {},
pendingRequests: [],
defaultSendWhenActive: false
},
data: { swBuildId: undefined },
linkquality: 72,
groupID: 0,
cluster: 'genBasic',
meta: {
zclTransactionSequenceNumber: 61,
manufacturerCode: null,
frameControl: {
frameType: 0,
manufacturerSpecific: false,
direction: 1,
disableDefaultResponse: true,
reservedBits: 0
}
}
}
[01/06/2022, 14:17:12] [ZigBee] Decoded state from incoming message {}
[01/06/2022, 14:17:12] [ZigBee] Updating state of device Sensor1 with  {}
[01/06/2022, 14:17:12] [ZigBee] Updated state for device Sensor1 is now  { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] No need to configure device Sensor1
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Successfully interviewed device: eWeLink - TH01
[01/06/2022, 14:17:12] [ZigBee] Not initializing device Sensor1: already mapped in Homebridge
[01/06/2022, 14:17:12] [ZigBee] Updating state of device Sensor1 with  {}
[01/06/2022, 14:17:12] [ZigBee] Updated state for device Sensor1 is now  { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] No need to configure device Sensor1
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000096-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 0000008A-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:12] [ZigBee] Updating service 00000082-0000-1000-8000-0026BB765291 for device Sensor1 with state { temperature: 0 }
[01/06/2022, 14:17:16] [Doby] DEB ensureDevice | roborock.vacuum.a15 | The socket is still on. Reusing it.
[01/06/2022, 14:17:16] [Doby] DEB getState | roborock.vacuum.a15 | State {"batteryLevel":100,"charging":true,"cleaning":false,"fanSpeed":102} | Props {"state":"charging","batteryLevel":100,"cleanTime":2136,"cleanArea":38.4175,"fanSpeed":102,"in_cleaning":0,"mainBrushWorkTime":44635,"sideBrushWorkTime":44635,"filterWorkTime":44635,"sensorDirtyTime":12306,"waterBoxMode":202,"autoDustCollection":1,"dustCollectionStatus":0}
[01/06/2022, 14:17:16] [Doby] DEB changedBattery | roborock.vacuum.a15 | BatteryLevel 100%


[TextField] Using autocomplete feature in Chrome for iOS Does not Update TextField

Problem description
When filling out a form a TextField, Chrome will offer autocomplete functionality for fields which have a name that it recognises (e.g. email). On Chrome for iOS, if you select the autocomplete option Chrome offers, the underlying value of the TextField does not get updated. Not sure if this can be fixed or if there is an official supported browser list for mobile browsers?
Steps to reproduce
Fill out a TextField component that has a name property your browser will recognize (email for example) on Chrome for iOS and select the autocomplete value that Chrome offers you.
Result: The underlying of the TextField does not get updated upon selection though the text for the field does
Versions

Material-UI:
React: 0.15.2
Browser: Chrome for iOS

Looks like this is being tracked in the React Library https://github.com/facebook/react/issues/1159 so can probably mark close this as it's related to browser event implementation as i thought


Fitting Blender release cycle

With the new Blender release cycle, between bcon3 and bcon5 (just like right now), taking example of the 2.81 release:
https://wiki.blender.org/wiki/Process/Release_Cycle
https://developer.blender.org/project/view/88/
In Blender repo

master is future 2.82
beta of next release, 2.81, is on blender-v2.81-release

Here, I replicated this schema:

master is future 2.82
blender-v2.81-release is used for fixing bugs only for 2.81

My main concerns is about versionning of the addon. Because version increases in master, when I made a fix in blender-v2.81-release branch, I can't increase the addon version number, because this number is already taken in master. I find quite strange to use the next available number, because it means that this particular version does not include features from version with lower number.
Example:

Addon is in version 1.0.0
branch blender-v2.81-release is created
a new feature A is added to master, version 1.0.1
a new feature B is added to master, version 1.0.2
a fix is added to blender-v2.81-release, how to name it? I don't like 1.0.3, because it doesn't include A and B.

I think, (but it's too late for 2.81 release), that we should manage it this way:

Addon is in version 1.0.0
branch blender-v2.81-release is created
bump version to 1.1.0 is master, without any other changes
a new feature A is added to master, version 1.1.1
a new feature B is added to master, version 1.1.2
a fix is added to blender-v2.81-release, named 1.0.1

Any thoughts?

Your last points looks OK, but what if 2.81 version comes to 1.0.9? Is it suitable to use also letters, like official Blender versions? (2.79, 2.79a, 2.79b) This could allow 1.0.9a, 1.0.9b, etc if needed.

Version for addon are only numerical, so we can't use 1.0.9a
But, we can go up to 9, so next version will be 1.0.10

Yep... simply as that ^^

Let's bump master to 1.1.0 to avoid any more collisions, and continue to bump the minor (2nd) version number with each new Blender release branch we track.
If the 2.81 release branch needs another change, its version can jump to 1.0.12.

I'm OK with this, but we should note that it does break the usual versioning practice of semver, where the values are <major>.<minor>.<patch>. If we were following that strictly, all feature additions would be a minor version increase, and all bug fixes would be a patch version increase.
So just to clarify – changes on master will always be minor version increases, even if they're just bugfixes, and changes on a prior release will always be patch version increase. That seems fine to me – adding new features to old releases is probably not a priority anyway.

So just to clarify – changes on master will always be minor version increases

Sorry, no, I meant that new Blender versions (specifically, the arrival of new Blender release branches) would trigger minor version increases, and the typical bugfix would be a patch version increase within the current branch.
The idea for this came about because we have separate branches for 2.81 and 2.82 (in master), and they are both getting patch version increments, so we need them to exist at different minor versions.

Works for me!


femoral artery and femoral vein

I would like to add femoral artery and femoral vein to the Total Segmentator segment model. How can I achieve this?
I would be grateful for any advice from experts who are using Total Segmentator.

You need to manually annotate the training data (available on zenodo) and then train a nnU-Net (see nnU-Net documentation).

Thank you for your advice.
It's very difficult for me.
I need to study more.


Release 0.0.11

@pepegar can we make a release for using the new idiomatic endpoints in mu?

Sure!


Feature request: rust_decimal::Decimal TS implementation

Is your feature request related to a problem? Please describe.
My project uses rust_decimal instead of bigdecimal, which seems to be more popular. It might be helpful to provide an implementation for this as well.
Describe the solution you'd like
Provide an implementation of TS for rust_decimal::Decimal, enabled via "rust-decimal-impl" (or omit the first dash)
Describe alternatives you've considered
Downstream packages supply some manual implementation or fallback?
Additional context
I recently began using the crate, so perhaps this addition is unnecessary.

Hey! Definetely something we can add in the future!
In the meantime, you can either use

a type override (specifying the typescript type manually): #[ts(type = "number")] field: Decimal
or, if your TS equivalent of Decimal is more complicated than number, use #[ts(as = ..)]

I've opened a PR that should ideally resolve this. It uses a specific feature flag for Decimal formatting that my particular project uses (and which their documentation describes as "flexible"), however this may not be appropriate for everyone elses' projects.
Potentially we can add a feature flags for each of the available representations. e.g., rustdecimal-with-serde-str-impl, rustdecimal-serde-str-impl, rustdecimal-with-serde-float-impl, rustdecimal-serde-float-impl, serde-with-arbitrary-precision, rustdecimal-serde-arbitrary-precision-impl, etc.

As mentioned in #273, we cannot properly support this


Add REST API integration tests that verify sequence of Bridge calls executed for core REST operations

(note: offshoot of #2351)
Currently we do not have (integration) tests that verify sequences of bridge calls taken for various REST API operations. In particular, whether various authorization calls are made (or not) is not validated. Because of this, changes like #2351 are potentially risky -- and perhaps as importantly, we do not know what the current behavior actually is.
We should add such tests at least for a core set of operations (basic CRUD row access).

Depends on https://github.com/stargate/stargate/issues/2376


Support HTTP/2 requests

When clients send HTTP/2 requests (without Host headers), X-Forwarded headers will be set except X-Forwarded-Host, which causes making improper nextUris in a coordinator, resulting in connection failures from next client requests.

https://github.com/trinodb/trino-gateway/blob/fdb1aa025201bb3b2d4273a0456540bbdaca5c62/gateway-ha/src/main/java/io/trino/gateway/proxyserver/ProxyRequestHandler.java#L287
Haven't tested yet. Change from getHeader() to getServerName() should fix the problem. HTTP/2 uses authority instead of Host header.

Returns the host name of the server to which the request was sent. It may be derived from a protocol specific mechanism, such as the Host header, or the HTTP/2 authority, or RFC 7239, otherwise the resolved server name or the server IP address.

Will be part of Trino Gateway 11


vue-tsc failing on '@update:var' syntax event handlers

Hi,
Using a fresh vue-ts Vite template and adding an event handler using '@update:varName' syntax raises an error on vue-tsc command.
@update:varName="() => {}"
gives
Property 'varName' does not exist on type ...etc
Even if event update:varName and prop varName are declared in component
Sorry for duplicate issue, got a bug with github

You need to define varName in component props: props: { varName: ... }

Got it, thanks.
prop was there but not with the same casing.
I feel like this should be in the doc if it's not already.


Gradle 8.x support

I know nothing about this cancel
On Sun, Jun 23, 2024, 6:12 PM AbdelMonaam Aouini @.***>
wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/devnied/EMV-NFC-Paycard-Enrollment/issues/92, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASBCUPADYYVQXRFGQBKWOA3ZI5B4BAVCNFSM6AAAAABJYXGZEOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DQOJRGA3TAOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Doc errors

For Basic SAML configuration part (Sign-on URL, Reply URL) , while I can see the doc update here: https://github.com/MicrosoftDocs/azure-docs/pull/47293/commits/b576cc9b062866460339baae8b64e32add4723e1?short_path=b3b21f8#diff-b3b21f860547c851a4f2e027e853b176, but actually the whole doc didn't get updated.
Further more, the update said "You can retrieve settings by using the SAML Toolkit SAML Configuration page." However, the settings in Configuration page can only be displayed after registering and uploading AAD SSO config in a later section. This will make readers get confused. So can we consider to modify docs like below:
In "Configure Azure AD SSO" section, still use the default settings, but highlight the Sign-on URL and Reply URL entered are just placeholders, should be replaced later.
In "Configure Azure AD SAML Toolkit SSO", add more steps after step "e". Copy Sign-on URL and ACS URL on SAML Toolkit SSO configuration page to replace the ones we created as placeholders above.

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

ID: 0800632e-a9b3-5f96-f290-207c7ef6be88
Version Independent ID: eaa3c7a0-76d5-433f-9ac3-bc72638c0ff3
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Azure AD SAML Toolkit
Content Source: articles/active-directory/saas-apps/saml-toolkit-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@JimmyLS Thanks for the feedback. We are investigating the issue and will update you shortly.

@jeevansd Could you verify this ?

@v-nagta This is good feedback here. Can you please update the doc with the said changes?

@JimmyLS We have updated the Doc as per your comments, please review
#please-close


[Backport] ingress-nginx in Prometheus Targets of a cluster are down when port 10254 is not open monitoring v2 is enabled

https://github.com/rancher/rancher/issues/32563

On 2.5-head commit id: 0e5876

Deploy an AWS node driver cluster with rancher-nodes
SG in the instances are

Enable Monitoring v2 set rkeIngressNginx: enabled=true
ingress-nginx are up and Active


Update fly_io deployments

[ ] Integration test without automate-all fails. Complains that a fly app has not yet been created, even though one has.
[ ] Integration test with automat all fails. Complains about not recognizing a region.

[ ] Main stability issue with fly is determining which app the user just created.

Failing deployment because it wants to create 2 "app" machines:
--> Pushing image done
image: registry.fly.io/white-glade-5822:deployment-01H3ANTSW6XD3ZGHKCG3PPZ2MF
image size: 169 MB

Watch your app at https://fly.io/apps/white-glade-5822/monitoring

Provisioning ips for white-glade-5822
  Dedicated ipv6: 2a09:8280:1::5b:2f09
  Shared ipv4: <IP_ADDRESS>
  Add a dedicated ipv4 with: fly ips allocate-v4
Running white-glade-5822 release_command: python manage.py migrate
  release_command 3d8d312c215689 completed successfully
This deployment will:
 * create 2 "app" machines

No machines in group app, launching a new machine
Error: error creating a new machine: failed to launch VM: To create more than 1 machine per app please add a payment method. https://fly.io/dashboard/eric-matthes/billing
Please note that release commands run in their own ephemeral machine, and therefore count towards the machine limit.

[ ] Why is it needing multiple machines?
[ ] Does adding payment method fix this?
[ ] What does this mean for trial users?

Payment method fixed the issue.
Is this issue from a change in ie Hobby level?

Maybe I'm provisioning a resource that's no longer free?

Closing for newer, more specific issues.


[Snyk] Fix for 1 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Adding or updating a Snyk policy (.snyk) file; this file is required in order to apply Snyk vulnerability patches.
Find out more.

Vulnerabilities that will be fixed
With a Snyk patch:

Severity
Issue
Exploit Maturity

Regular Expression Denial of Service (ReDoS)  npm:semver:20150403
No Known Exploit

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


installation failure in travis-ci

1.45s$ curl https://raw.githubusercontent.com/cs01/pipx/master/get-pipx.py | python
Installing pipx
Traceback (most recent call last):
  File "<stdin>", line 231, in <module>
  File "<stdin>", line 215, in main
  File "<stdin>", line 136, in install
  File "<stdin>", line 52, in create_venv
  File "<stdin>", line 64, in upgrade_package
  File "<stdin>", line 70, in _run_pip
  File "<stdin>", line 36, in _run
  File "/opt/python/3.6.3/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/opt/python/3.6.3/lib/python3.6/subprocess.py", line 709, in __init__
    restore_signals, start_new_session)
  File "/opt/python/3.6.3/lib/python3.6/subprocess.py", line 1344, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: PosixPath('/home/travis/.local/pipx/venvs/pipx/bin/pip'): PosixPath('/home/travis/.local/pipx/venvs/pipx/bin/pip')

I suspect get-pipx.py probably needs to use https://docs.python.org/3/library/os.html#os.makedirs somewhere to ensure that the full path exists.
For reference, the WIP travis config in my PR in my project - https://github.com/guykisel/inline-plz/blob/8956751a942ce3088fbb81a563d63d8aa545073f/.travis.yml

Sorry for the inconvenience, will get this taken care of.

Thanks for taking a look! There's no hurry :)

I looked into that a bit. These problem is stated here and here but there doesn't seem to be any solution.
As stated here, the Travis file already runs inside a virtualenv. It appears that invoking venv from inside an exiting virtualenv creates a new virtual environment in which pip isn't present.
Perhaps get-pipx should not create a virtualenv of its own if get-pipx is already being run inside a virtualenv?

@r-darwish thanks for the additional info, it's very helpful!
I think the logic should be as follows:
if in_virtualenv():
    if travis():  # check for TRAVIS env var
        logging.warning("Detected travis test build. Installing pipx in non-standard way for testing")
        # use global pip and set path expectations appropriately, maybe running `pip -t` instead
    else:
        raise PipError(
            "pipx should not be installed while a virtualenv is activated. Run `deactivate` then try again."
        )

It appears that invoking venv from inside an exiting virtualenv creates a new virtual environment in which pip isn't present.

@r-darwish I tested this theory, but it does not match what's happening on my computer. No matter how I create a new virtual env, pip is always there.


feat: docs for gas-reports

Fixes https://github.com/onbjerg/foundry-book/issues/31
Motivation
Epic feature needs docs

Screenshots
Added to foundry.toml Reference

New page: Gas reports

Ah, my bad, I remember it as an index. Thanks! :smile:

No problemo, thanks for maintaining these super helpful docs