Log wird geflutet nacg Update auf 1.90

Habe gerade ein Update gemacht auf die V1.90 gemacht. Danach bekam ich jede Menge Meldungen im log.
Alle anderen wesentlichen Adapter sind stable. Genauso wie js-controller

Zeitdebugsillyinfowarnerror
|   |   |
-- | -- | -- | --
info.0 | 2021-07-20 20:56:04.062 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.061 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.060 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.059 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.058 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.055 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.054 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.053 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.051 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.051 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.048 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.047 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.046 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.045 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.044 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.041 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.040 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.038 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.038 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.033 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.029 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.028 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.027 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.026 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.025 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.023 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.021 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.018 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.018 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:04.017 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.933 | warn | (12202) State "info.0.sysinfo.disks.diskLayout.dev2.temperature" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.931 | warn | (12202) State "info.0.sysinfo.disks.diskLayout.dev1.temperature" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.912 | warn | (12202) State "info.0.sysinfo.disks.diskLayout.dev0.temperature" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.911 | warn | (12202) State "info.0.sysinfo.cpu.info.virtualization" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.910 | warn | (12202) State "info.0.sysinfo.cpu.info.flags" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.909 | warn | (12202) State "info.0.sysinfo.cpu.info.speedMax" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.908 | warn | (12202) State "info.0.sysinfo.cpu.info.speedMin" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.542 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.542 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.541 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.540 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.540 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.539 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_bytes" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.538 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.537 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.537 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_bytes" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.536 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.operstate" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.536 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.iface" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.535 | warn | (12202) State "info.0.sysinfo.system.hardware.sku" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.534 | warn | (12202) State "info.0.sysinfo.system.uuid.macs-1" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.533 | warn | (12202) State "info.0.sysinfo.system.uuid.macs-0" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.532 | warn | (12202) State "info.0.sysinfo.system.uuid.os" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.529 | warn | (12202) State "info.0.sysinfo.system.baseboard.memSlots" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.529 | warn | (12202) State "info.0.sysinfo.system.baseboard.memMax" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.526 | warn | (12202) State "info.0.sysinfo.cpu.temperature.chipset" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.526 | warn | (12202) State "info.0.sysinfo.cpu.temperature.cores-3" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.524 | warn | (12202) State "info.0.sysinfo.cpu.temperature.cores-2" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.523 | warn | (12202) State "info.0.sysinfo.cpu.temperature.cores-1" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.522 | warn | (12202) State "info.0.sysinfo.cpu.temperature.cores-0" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.520 | warn | (12202) State "info.0.sysinfo.memory.memLayout.ram0.ecc" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.411 | warn | (12202) State "info.0.sysinfo.disks.fsSize.fs0.available" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.407 | warn | (12202) State "info.0.sysinfo.network.info.defaultGateway" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.407 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.406 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.383 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.382 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.381 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.267 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.tx_bytes" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.267 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_errors" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.266 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_dropped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.266 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.rx_bytes" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.265 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.operstate" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.264 | warn | (12202) State "info.0.sysinfo.network.stats.iface0.iface" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.148 | warn | (12202) State "info.0.sysinfo.docker.info.productLicense" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.148 | warn | (12202) State "info.0.sysinfo.docker.info.initBinary" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.147 | warn | (12202) State "info.0.sysinfo.docker.info.isolation" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.147 | warn | (12202) State "info.0.sysinfo.docker.info.liveRestoreEnabled" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.146 | warn | (12202) State "info.0.sysinfo.docker.info.defaultRuntime" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.146 | warn | (12202) State "info.0.sysinfo.docker.info.clusterAdvertise" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.146 | warn | (12202) State "info.0.sysinfo.docker.info.clusterStore" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.145 | warn | (12202) State "info.0.sysinfo.docker.info.serverVersion" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.145 | warn | (12202) State "info.0.sysinfo.docker.info.experimentalBuild" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.144 | warn | (12202) State "info.0.sysinfo.docker.info.labels" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.144 | warn | (12202) State "info.0.sysinfo.docker.info.name" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.143 | warn | (12202) State "info.0.sysinfo.docker.info.noProxy" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.143 | warn | (12202) State "info.0.sysinfo.docker.info.httpsProxy" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.142 | warn | (12202) State "info.0.sysinfo.docker.info.httpProxy" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.142 | warn | (12202) State "info.0.sysinfo.docker.info.dockerRootDir" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.141 | warn | (12202) State "info.0.sysinfo.docker.info.memTotal" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.141 | warn | (12202) State "info.0.sysinfo.docker.info.ncpu" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.140 | warn | (12202) State "info.0.sysinfo.docker.info.architecture" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.140 | warn | (12202) State "info.0.sysinfo.docker.info.osType" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.139 | warn | (12202) State "info.0.sysinfo.docker.info.operatingSystem" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.139 | warn | (12202) State "info.0.sysinfo.docker.info.kernelVersion" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.139 | warn | (12202) State "info.0.sysinfo.docker.info.nEventsListener" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.138 | warn | (12202) State "info.0.sysinfo.docker.info.cgroupDriver" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.138 | warn | (12202) State "info.0.sysinfo.docker.info.loggingDriver" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.137 | warn | (12202) State "info.0.sysinfo.docker.info.systemTime" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.137 | warn | (12202) State "info.0.sysinfo.docker.info.ngoroutines" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.136 | warn | (12202) State "info.0.sysinfo.docker.info.oomKillDisable" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.136 | warn | (12202) State "info.0.sysinfo.docker.info.nfd" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.135 | warn | (12202) State "info.0.sysinfo.docker.info.debug" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.135 | warn | (12202) State "info.0.sysinfo.docker.info.bridgeNfIp6tables" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.134 | warn | (12202) State "info.0.sysinfo.docker.info.bridgeNfIptables" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.133 | warn | (12202) State "info.0.sysinfo.docker.info.ipv4Forwarding" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.132 | warn | (12202) State "info.0.sysinfo.docker.info.cpuSet" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.132 | warn | (12202) State "info.0.sysinfo.docker.info.cpuShares" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.131 | warn | (12202) State "info.0.sysinfo.docker.info.cpuCfsQuota" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.131 | warn | (12202) State "info.0.sysinfo.docker.info.cpuCfsPeriod" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.130 | warn | (12202) State "info.0.sysinfo.docker.info.kernelMemory" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.130 | warn | (12202) State "info.0.sysinfo.docker.info.swapLimit" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.129 | warn | (12202) State "info.0.sysinfo.docker.info.memoryLimit" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.126 | warn | (12202) State "info.0.sysinfo.docker.info.driver" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.125 | warn | (12202) State "info.0.sysinfo.docker.info.images" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.124 | warn | (12202) State "info.0.sysinfo.docker.info.containersStopped" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.124 | warn | (12202) State "info.0.sysinfo.docker.info.containersPaused" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.123 | warn | (12202) State "info.0.sysinfo.docker.info.containersRunning" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.123 | warn | (12202) State "info.0.sysinfo.docker.info.containers" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.122 | warn | (12202) State "info.0.sysinfo.docker.info.id" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.121 | warn | (12202) State "info.0.sysinfo.cpu.currentLoad.cpus-3" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.121 | warn | (12202) State "info.0.sysinfo.cpu.currentLoad.cpus-2" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.120 | warn | (12202) State "info.0.sysinfo.cpu.currentLoad.cpus-1" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.119 | warn | (12202) State "info.0.sysinfo.cpu.currentLoad.cpus-0" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.118 | warn | (12202) State "info.0.sysinfo.network.info.defaultInterface" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.114 | warn | (12202) State "info.0.sysinfo.cpu.currentSpeed.cores-3" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.113 | warn | (12202) State "info.0.sysinfo.cpu.currentSpeed.cores-2" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.112 | warn | (12202) State "info.0.sysinfo.cpu.currentSpeed.cores-1" has no existing object, this might lead to an error in future versions
info.0 | 2021-07-20 20:56:03.109 | warn | (12202) State "info.0.sysinfo.cpu.currentSpeed.cores-0" has no existing object, this might lead to an error in future versions

Bei mir tauchen noch ein paar Datenpunkte auf, welche oben noch nicht genannt sind:
js-controller 3.3.14
info 1.9.0
Nach dem Update wurden alle Objekte unter info.* gelöscht und dann die Instanz neu gestartet.
20 Jul 2021 22:10:14.477
info.0 (18135) State "info.0.sysinfo.battery.virtual" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.476
info.0 (18135) State "info.0.sysinfo.battery.sku" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.474
info.0 (18135) State "info.0.sysinfo.system.hardware.virtual" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.471
info.0 (18135) State "info.0.sysinfo.system.hardware.sku" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.342
info.0 (18135) State "info.0.sysinfo.memory.info.swaptotal" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.340
info.0 (18135) State "info.0.sysinfo.memory.info.slab" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.338
info.0 (18135) State "info.0.sysinfo.memory.info.cached" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.336
info.0 (18135) State "info.0.sysinfo.memory.info.buffers" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.334
info.0 (18135) State "info.0.sysinfo.memory.info.total" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.332
info.0 (18135) State "info.0.sysinfo.cpu.info.cache-l3" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.331
info.0 (18135) State "info.0.sysinfo.cpu.info.cache-l2" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.329
info.0 (18135) State "info.0.sysinfo.cpu.info.cache-l1i" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.327
info.0 (18135) State "info.0.sysinfo.cpu.info.cache-l1d" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.325
info.0 (18135) State "info.0.sysinfo.cpu.info.virtualization" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.323
info.0 (18135) State "info.0.sysinfo.cpu.info.flags" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.321
info.0 (18135) State "info.0.sysinfo.cpu.info.processors" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.320
info.0 (18135) State "info.0.sysinfo.cpu.info.physicalCores" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.318
info.0 (18135) State "info.0.sysinfo.cpu.info.cores" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.316
info.0 (18135) State "info.0.sysinfo.cpu.info.governor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.315
info.0 (18135) State "info.0.sysinfo.cpu.info.speedMax" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.313
info.0 (18135) State "info.0.sysinfo.cpu.info.speedMin" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.311
info.0 (18135) State "info.0.sysinfo.cpu.info.speed" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.310
info.0 (18135) State "info.0.sysinfo.cpu.info.stepping" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.308
info.0 (18135) State "info.0.sysinfo.cpu.info.model" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.306
info.0 (18135) State "info.0.sysinfo.cpu.info.family" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.305
info.0 (18135) State "info.0.sysinfo.cpu.info.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.303
info.0 (18135) State "info.0.sysinfo.cpu.info.brand" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.302
info.0 (18135) State "info.0.sysinfo.cpu.info.manufacturer" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.273
info.0 (18135) State "info.0.sysinfo.os.info.uefi" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.272
info.0 (18135) State "info.0.sysinfo.os.info.serial" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.270
info.0 (18135) State "info.0.sysinfo.os.info.logofile" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.269
info.0 (18135) State "info.0.sysinfo.os.info.codepage" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.267
info.0 (18135) State "info.0.sysinfo.os.info.fqdn" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.266
info.0 (18135) State "info.0.sysinfo.os.info.hostname" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.264
info.0 (18135) State "info.0.sysinfo.os.info.arch" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.262
info.0 (18135) State "info.0.sysinfo.os.info.kernel" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.261
info.0 (18135) State "info.0.sysinfo.os.info.codename" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.259
info.0 (18135) State "info.0.sysinfo.os.info.release" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.257
info.0 (18135) State "info.0.sysinfo.os.info.distro" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.256
info.0 (18135) State "info.0.sysinfo.os.info.platform" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.254
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.temperature" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.252
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.smartStatus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.251
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.interfaceType" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.249
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.firmwareRevision" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.247
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.sectorsPerTrack" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.246
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.tracksPerCylinder" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.244
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.totalTracks" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.242
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.totalSectors" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.241
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.totalHeads" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.239
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.totalCylinders" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.237
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.bytesPerSector" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.236
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.234
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.232
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.231
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.229
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev1.device" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.227
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.temperature" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.226
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.smartStatus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.225
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.interfaceType" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.223
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.firmwareRevision" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.222
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.sectorsPerTrack" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.220
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.tracksPerCylinder" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.219
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.totalTracks" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.218
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.totalSectors" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.216
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.totalHeads" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.215
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.totalCylinders" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.214
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.bytesPerSector" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.212
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.211
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.209
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.208
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.206
info.0 (18135) State "info.0.sysinfo.disks.diskLayout.dev0.device" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.150
info.0 (18135) State "info.0.sysinfo.os.versions.bash" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.148
info.0 (18135) State "info.0.sysinfo.os.versions.gcc" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.147
info.0 (18135) State "info.0.sysinfo.os.versions.python3" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.145
info.0 (18135) State "info.0.sysinfo.os.versions.python" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.144
info.0 (18135) State "info.0.sysinfo.os.versions.perl" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.142
info.0 (18135) State "info.0.sysinfo.os.versions.postfix" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.141
info.0 (18135) State "info.0.sysinfo.os.versions.git" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.139
info.0 (18135) State "info.0.sysinfo.os.versions.npm" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.138
info.0 (18135) State "info.0.sysinfo.os.versions.v8" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.137
info.0 (18135) State "info.0.sysinfo.os.versions.node" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.135
info.0 (18135) State "info.0.sysinfo.os.versions.systemOpensslLib" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.134
info.0 (18135) State "info.0.sysinfo.os.versions.systemOpenssl" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.132
info.0 (18135) State "info.0.sysinfo.os.versions.openssl" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:14.130
info.0 (18135) State "info.0.sysinfo.os.versions.kernel" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.923
info.0 (18135) State "info.0.sysinfo.system.uuid.macs-0" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.921
info.0 (18135) State "info.0.sysinfo.system.uuid.os" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.919
info.0 (18135) State "info.0.sysinfo.system.bios.releaseDate" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.918
info.0 (18135) State "info.0.sysinfo.system.bios.version" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.916
info.0 (18135) State "info.0.sysinfo.system.bios.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.914
info.0 (18135) State "info.0.sysinfo.system.baseboard.memSlots" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.913
info.0 (18135) State "info.0.sysinfo.system.baseboard.memMax" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.911
info.0 (18135) State "info.0.sysinfo.system.baseboard.model" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.909
info.0 (18135) State "info.0.sysinfo.system.baseboard.manufacturer" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.907
info.0 (18135) State "info.0.sysinfo.system.chassis.assetTag" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.905
info.0 (18135) State "info.0.sysinfo.system.chassis.version" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.904
info.0 (18135) State "info.0.sysinfo.system.chassis.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.902
info.0 (18135) State "info.0.sysinfo.system.chassis.manufacturer" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.900
info.0 (18135) State "info.0.sysinfo.cpu.temperature.chipset" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.898
info.0 (18135) State "info.0.sysinfo.cpu.temperature.cores-3" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.897
info.0 (18135) State "info.0.sysinfo.cpu.temperature.cores-2" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.895
info.0 (18135) State "info.0.sysinfo.cpu.temperature.cores-1" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.893
info.0 (18135) State "info.0.sysinfo.cpu.temperature.cores-0" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.891
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.voltageMax" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.890
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.voltageMin" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.888
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.voltageConfigured" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.886
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.clockSpeed" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.885
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.ecc" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.882
info.0 (18135) State "info.0.sysinfo.memory.memLayout.ram0.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.881
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev4.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.879
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev4.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.877
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev4.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.876
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev4.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.874
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev3.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.872
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev3.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.870
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev3.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.869
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev3.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.867
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev2.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.865
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev2.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.863
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev2.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.862
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev2.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.860
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.protocol" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.858
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.857
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.model" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.855
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.physical" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.853
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.851
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.849
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev1.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.847
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.protocol" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.846
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.844
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.model" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.842
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.physical" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.840
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.838
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.837
info.0 (18135) State "info.0.sysinfo.disks.blockDevices.dev0.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.835
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.mount" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.833
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.use" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.831
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.available" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.829
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.used_hist" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.828
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.used" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.826
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.size" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.824
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.823
info.0 (18135) State "info.0.sysinfo.disks.fsSize.fs0.fs" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.821
info.0 (18135) State "info.0.sysinfo.usb.dev4.serialNumber" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.819
info.0 (18135) State "info.0.sysinfo.usb.dev4.maxPower" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.818
info.0 (18135) State "info.0.sysinfo.usb.dev4.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.817
info.0 (18135) State "info.0.sysinfo.usb.dev4.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.815
info.0 (18135) State "info.0.sysinfo.usb.dev4.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.813
info.0 (18135) State "info.0.sysinfo.usb.dev4.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.812
info.0 (18135) State "info.0.sysinfo.usb.dev4.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.810
info.0 (18135) State "info.0.sysinfo.usb.dev4.deviceId" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.808
info.0 (18135) State "info.0.sysinfo.usb.dev4.bus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.806
info.0 (18135) State "info.0.sysinfo.usb.dev3.serialNumber" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.805
info.0 (18135) State "info.0.sysinfo.usb.dev3.maxPower" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.803
info.0 (18135) State "info.0.sysinfo.usb.dev3.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.802
info.0 (18135) State "info.0.sysinfo.usb.dev3.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.800
info.0 (18135) State "info.0.sysinfo.usb.dev3.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.798
info.0 (18135) State "info.0.sysinfo.usb.dev3.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.797
info.0 (18135) State "info.0.sysinfo.usb.dev3.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.795
info.0 (18135) State "info.0.sysinfo.usb.dev3.deviceId" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.793
info.0 (18135) State "info.0.sysinfo.usb.dev3.bus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.788
info.0 (18135) State "info.0.sysinfo.usb.dev2.serialNumber" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.781
info.0 (18135) State "info.0.sysinfo.usb.dev2.maxPower" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.774
info.0 (18135) State "info.0.sysinfo.usb.dev2.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.759
info.0 (18135) State "info.0.sysinfo.usb.dev2.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.757
info.0 (18135) State "info.0.sysinfo.usb.dev2.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.754
info.0 (18135) State "info.0.sysinfo.usb.dev2.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.752
info.0 (18135) State "info.0.sysinfo.usb.dev2.deviceId" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.750
info.0 (18135) State "info.0.sysinfo.usb.dev2.bus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.748
info.0 (18135) State "info.0.sysinfo.usb.dev1.serialNumber" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.745
info.0 (18135) State "info.0.sysinfo.usb.dev1.maxPower" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.743
info.0 (18135) State "info.0.sysinfo.usb.dev1.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.740
info.0 (18135) State "info.0.sysinfo.usb.dev1.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.739
info.0 (18135) State "info.0.sysinfo.usb.dev1.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.737
info.0 (18135) State "info.0.sysinfo.usb.dev1.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.735
info.0 (18135) State "info.0.sysinfo.usb.dev1.deviceId" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.732
info.0 (18135) State "info.0.sysinfo.usb.dev1.bus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.730
info.0 (18135) State "info.0.sysinfo.usb.dev0.serialNumber" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.728
info.0 (18135) State "info.0.sysinfo.usb.dev0.maxPower" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.726
info.0 (18135) State "info.0.sysinfo.usb.dev0.vendor" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.724
info.0 (18135) State "info.0.sysinfo.usb.dev0.removable" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.723
info.0 (18135) State "info.0.sysinfo.usb.dev0.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.721
info.0 (18135) State "info.0.sysinfo.usb.dev0.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.719
info.0 (18135) State "info.0.sysinfo.usb.dev0.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.717
info.0 (18135) State "info.0.sysinfo.usb.dev0.deviceId" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.715
info.0 (18135) State "info.0.sysinfo.usb.dev0.bus" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.713
info.0 (18135) State "info.0.sysinfo.audio.dev0.status" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.711
info.0 (18135) State "info.0.sysinfo.audio.dev0.out" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.709
info.0 (18135) State "info.0.sysinfo.audio.dev0.in" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.707
info.0 (18135) State "info.0.sysinfo.audio.dev0.channel" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.705
info.0 (18135) State "info.0.sysinfo.audio.dev0.default" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.703
info.0 (18135) State "info.0.sysinfo.audio.dev0.driver" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.701
info.0 (18135) State "info.0.sysinfo.audio.dev0.revision" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.699
info.0 (18135) State "info.0.sysinfo.audio.dev0.manufacturer" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.697
info.0 (18135) State "info.0.sysinfo.audio.dev0.name" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.695
info.0 (18135) State "info.0.sysinfo.audio.dev0.id" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.693
info.0 (18135) State "info.0.sysinfo.network.info.defaultGateway" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.691
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.ms" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.689
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.tx_sec" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.678
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.rx_sec" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.676
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.tx_errors" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.671
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.tx_dropped" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.670
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.tx_bytes" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.660
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.rx_errors" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.658
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.rx_dropped" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.656
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.rx_bytes" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.655
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.operstate" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.653
info.0 (18135) State "info.0.sysinfo.network.stats.iface0.iface" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.464
info.0 (18135) State "info.0.sysinfo.cpu.currentLoad.cpus-3" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.462
info.0 (18135) State "info.0.sysinfo.cpu.currentLoad.cpus-2" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.461
info.0 (18135) State "info.0.sysinfo.cpu.currentLoad.cpus-1" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.459
info.0 (18135) State "info.0.sysinfo.cpu.currentLoad.cpus-0" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.455
info.0 (18135) State "info.0.sysinfo.network.info.defaultInterface" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.453
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.carrierChanges" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.452
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ieee8021xState" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.450
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ieee8021xAuth" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.448
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.dnsSuffix" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.447
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.dhcp" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.445
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.speed" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.443
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.mtu" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.442
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.duplex" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.440
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.438
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.operstate" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.437
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.virtual" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.435
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.internal" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.434
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.mac" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.432
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ip6subnet" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.430
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ip6" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.428
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ip4subnet" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.426
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ip4" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.425
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.ifaceName" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.423
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface1.iface" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.421
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.carrierChanges" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.419
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ieee8021xState" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.417
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ieee8021xAuth" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.415
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.dnsSuffix" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.412
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.dhcp" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.409
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.speed" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.407
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.mtu" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.405
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.type" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.403
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.operstate" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.401
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.virtual" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.399
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.internal" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.397
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.mac" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.394
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ip6subnet" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.392
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ip6" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.390
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ip4subnet" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.388
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ip4" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.386
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.ifaceName" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.383
info.0 (18135) State "info.0.sysinfo.network.interfaces.iface0.iface" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.381
info.0 (18135) State "info.0.sysinfo.cpu.currentSpeed.cores-3" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.379
info.0 (18135) State "info.0.sysinfo.cpu.currentSpeed.cores-2" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.377
info.0 (18135) State "info.0.sysinfo.cpu.currentSpeed.cores-1" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:13.375
info.0 (18135) State "info.0.sysinfo.cpu.currentSpeed.cores-0" has no existing object, this might lead to an error in future versions
20 Jul 2021 22:10:10.822
info.0 (18135) Reading/updating systemdata.
20 Jul 2021 22:10:10.742
info.0 (18135) starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.info, node: v12.22.2, js-controller: 3.3.14
20 Jul 2021 22:10:06.352
host.ioBrokerTestsystem instance system.adapter.info.0 started with pid 18135
20 Jul 2021 22:10:06.059
host.ioBrokerTestsystem "system.adapter.info.0" enabled
20 Jul 2021 22:07:28.488
host.ioBrokerTestsystem instance system.adapter.info.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
20 Jul 2021 22:07:27.727
host.ioBrokerTestsystem stopInstance system.adapter.info.0 send kill signal
20 Jul 2021 22:07:27.585
host.ioBrokerTestsystem stopInstance system.adapter.info.0 (force=false, process=true)
20 Jul 2021 22:07:27.582
host.ioBrokerTestsystem "system.adapter.info.0" disabled

Nach Update auf 1.9.0 System auf Raspberry nur noch lauffähig bei angehaltenem info adapter

Bitte mal Objekte vom Ibfo Adapter löschen und GitHub Version installieren und Debug log posten

Nach Update auf 1.9.0 System auf Raspberry nur noch lauffähig bei angehaltenem info adapter

uahc bei hochgesetztem Loglevel auf warn?

Ok, guy s... ich habe soeben GitHub nochmal aktualisiert. jetzt??

Ok, guy s... ich habe soeben GitHub nochmal aktualisiert. jetzt??

Ich denke unverändert oder noch schlechter... musste das gleich wieder abschalten, das kocht mir den armen kleinen ARM :)  ... Frist ein Loch in den Speicher.... nach 1 Minute braucht der Adapter >700MB

auf was hast Du denn die Abfrageintervalle von den Daten stehen? 1s? mach da mal überall 0 rein, dann ist das aus. Dann am besten mit 60 oder 120s mal weiter versuchen.

@Apollon77 Mit der aktuellen Github Version sind alle Warnungen weg :-)

Intervalle von 3-120s ..... jetzt nur noch 4 Stk auf 120s. Dadurch kann ich den Adapter wieder per GUI ausschalten... CPU Last trotzdem >65% statt 2-4% ohne.... Da muss noch mehr im Hintergrund passieren.

Loglevel auf WARN bringt keinen Unterschied in der CPU Last

@hombach Hast du die neue github version schon installiert, welche @Apollon77 oben erwähnt hat?
Ich hab gerade mal meinen Info Adapter wie folgt eingestellt. Mal sehen was mein System sagt. Bisher hatte ich das auslesen der Systemdaten deaktiviert.

ja, hab die neuste direkt von GIT. Hat ja auch was gebracht.... keine warnings, nur info.... aber die CPU-Last ist so nicht zu vertreten.  (eigentlich fast OT in diesem "Thread" ;) )

@hombach Dann mach doch hier weiter https://github.com/iobroker-community-adapters/ioBroker.info/issues/312 ;-)

@hombach Die Infos sollten an sich auch weg sein wenn du einmalig alle Objekte löschst.
ich habe gerade eine 1.9.1 released.

 IMHO ist der issue erledigt.


Explicit API to allow user to register existing tables

For example, if you want to register a sample of records to use find_matches_to_new_records
In duckdb linker, at the moment have to do:
df_sample = df.sample(1)
linker._con.register("__splink__df_new_records", df_sample)

matches = linker.find_matches_to_new_records(None, blocking_rules=["1=1"], match_weight_threshold=-10000)

and also edit linker.py
        if isinstance(records, list):
            self._records_to_table(records, "__splink__df_new_records")

At the moment, if you have some labels in a csv, how do you ‘tell’ Splink about them?
I reckon each linker needs a linker.register_data(data, tablename), which can take data in a variety of formats.
e.g. with duckdb, data couuld be a arrow/pandas table or a list of dicts
whereas with Spark, it would usually be a Spark dataframe, but could be a pandas or arrow dataframe
Another area this crops up is in some of the real time linking code - where you have a model and want to give Splink just two records, to generate a pairwise comparison and score
At the moment, you provide data as a dict, but that’s not ideal due to data typing issues.  Using linker.register_data() under the hood should help there too


vmm-task is built explicitly with x86_64-unknown-linux-musl in Makefile

What happened?
Failed to build with arm64 machine. However, I noticed that arm will be supported in 2024, but explicitly specify the x86 target in the Makefile is not a good manner
What did you expect to happen?
Built in arm64
How can we reproduce it (as minimally and precisely as possible)?
Build with arm machine
Anything else we need to know?
No response
Dev environment
No response

Yes, we are not support on aarch64 platform at present, while it is on our Roadmap.
Let's keep this open.

already fixed by https://github.com/kuasar-io/kuasar/pull/11

already fixed by https://github.com/kuasar-io/kuasar/pull/11


[$250] Distance - Page is not scrollable after adding multiple stops

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.75-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4572868
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Click on FAB > Submit expense > Distance tab
Add a start waypoint, a finish waypoint, and multiple stops
Try to Scroll the page
Do step 1 - 3 on mWeb

Expected Result:
Page becomes scrollable to view the whole content after adding multiple waypoints (Same behavior as in mWeb)
Actual Result:
Page is not scrollable to view the whole content after adding multiple waypoints which is a different behavior compared to mWeb.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/de96b11b-7ef9-48a3-8e63-50690e0f4ea8

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014d91998739178ee2
Upwork Job ID:<PHONE_NUMBER>596056064
Last Price Increase: 2024-06-05
Automatic offers:

Krishna2323 | Contributor | 102695130

Issue OwnerCurrent Issue Owner: @stitesExpensify

We think this issue might be related to the #collect project.

Hey @mollfpr, a few proposals here to review when you get a chance!

Wrap the content in a ScrollView and remove the View.

@Krishna2323 What's the difference between your main and the alternative solution? Also, I tried the above step but it did not work. In the alternative solution, wrapping the DraggableList with <ScrollView style={styles.flex1}> seems to fix the issue, so I don't understand the purpose of the second step.
@GandalfGwaihir As mentioned before in the @Krishna2323 proposal, we can't use the ListFooterComponent to avoid the issue https://github.com/Expensify/App/issues/40211 arising again.

@Krishna2323 The result looks good, but I think the expected result is similar to what we have in iOS where the scroll can be used above the waypoint list instead of just space beside the add stop button.
https://github.com/Expensify/App/assets/25520267/114974c0-98b2-495e-a974-679e68f42348

@allgandalf I can do it for you. We still don't have selected proposal yet, and I still don't know the reason we can't pass the component to footer props.

@allgandalf It seems the issue occurs again.
https://github.com/Expensify/App/assets/25520267/2b1e100c-b4a1-4fb2-91bd-fc00fa609eb5
@Krishna2323 I'm not sure if using NestableScrollContainer  and NestableDraggableFlatList is the correct way, because NestableScrollContainer is used to wrap multiple NestableDraggableFlatList. Meanwhile, we only have one draggable flat list component.

@Krishna2323 Okay, I'll try to play around and see if there's a regression from using the NestableScrollContainer.

PR is being worked on

Not overdue Melvin

Little bump @mollfpr, can you review the PR when you get a chance?

PR is under active review

Applying the New Feature label to get another BZ member on this while I am OOO til July 10. To catch you up on where we are @lschurr, we have a PR and it's being actively reviewed: https://github.com/Expensify/App/pull/43810
Thanks for watching over this, I'll grab it back from you when I return!

This is held on an upstream fix https://github.com/Expensify/App/pull/43810#issuecomment-2215401234

Upstream issue we are blocked on is here: https://github.com/computerjazz/react-native-draggable-flatlist/issues/543

Summarizing payment on this issue:

Contributor: @Krishna2323 $250 - PAID via Upwork
Contributor+: @mollfpr $250 - please request via ND

Upwork job is here: https://www.upwork.com/jobs/~1737876297360310272

@mollfpr can you please complete the BZ checklist for this issue?

[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

I couldn't find the offending PR.

[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

The regression step should be good.

[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Click on FAB > Submit expense > Distance tab
Add a start waypoint, a finish waypoint, and multiple stops
Verify page is scrollable after the content overflows
👍 or 👎

$250 approved for @mollfpr

Test case issue created: https://github.com/Expensify/Expensify/issues/420216
All done here, thanks!


/var/log filled sd card after using remote gpio library

I wrote this script (I may be using it wrong)

But it has seemed to fill my sd card with massive logs in /var/log
daemon.log and syslog and syslog.1 are huge and contain the following line:
python3[1793]: ALSA lib pcm.c:7843:(snd_pcm_recover) overrun occurred

Why was this closed? ;)
What version of GpioZero are you using? What version of Raspbian are you using?

This was the only thing I had done on the raspberry pi recently so thought it was the issue.
I also have google aiy on the raspberry pi and I think it may be the issue as it just randomly stopped working and I cant get it to work again.
Gpiozero 1.4.0 and Jessie

I don't know, that's not a combination I've tried myself. If you can recreate this problem on a freshly-written SD card then please re-open this issue.

I just got this again with a freshly written SD card, daemon.log and syslog got filled agin.
This time it uses the newer version of google aiy which is different than the old version.
This is everything that is installed.
MySQL
sudo apt-get install mysql-server --fix-missing
sudo apt-get install mysql-client php5-mysql
Connect to MySQL from python
sudo apt-get install python-dev libmysqlclient-dev
sudo apt-get install python-mysqldb
pip install mysqlclient
Vim
sudo apt-get install vim
Apache
sudo apt-get install apache2
PHP
sudo apt-get install php5cd /var
The remote daemon is also on

Hmmm, then perhaps there's some kind of conflict with google AIY and pigpiod? (pigpiod is the underlying library that GpioZero uses for remote gpio)
Might be worth chasing up this bug on each of those projects' websites.
https://aiyprojects.withgoogle.com/
http://abyz.me.uk/rpi/pigpio/pigpiod.html
(ping @joan2937 )

Yeah this isn't a bug in gpiozero, it's something going on with pigpio.

The logs are apparently being created by the ALSA library.  By default pigpio uses the PCM peripheral to time the GPIO sampling.  Presumably Google AIY is also using the PCM peripheral via the ALSA library.
One way to test would be to start the pigpio daemon with the -t0 option (see http://abyz.me.uk/rpi/pigpio/pigpiod.html).  pigpiod will then use the PWM peripheral instead of the PCM peripheral.
E.g. try something like the following.
sudo killall pigpiod
sudo pigpiod -t0

@joan2937 Oooh, interesting. As somebody who knows very little about all this, does using PCM over PWM (or vice versa) allow more precision in pigpiod, or are they both equally capable?
Would there be a possibility to also have an additional -t 2 clock option, to then have pigpiod use No clock peripheral? (with errors then thrown as appropriate if the user tries to use a function which requires a clock peripheral)   Or perhaps that's a stupid question? ;-)

@lurch
PWM and PCM are equal as far as the timing is concerned.
They are actually used to pace the DMA transfers (an idea of Gerts, first implemented by Richard Hirst and used in his servoblaster).  The GPIO are sampled by a DMA transfer from the GPIO register to memory.
High speed sampling and accurate time-stamping are central to pigpio.  They are the reason it exists.  This would be impossible without using DMA transfers.  As a byproduct you also get pretty accurate PWM generation on all the GPIO for free.

Thanks guys for all your help, (sorry for posting the issue in the wrong place, I was confused at first when it happened)
I have tried joan's suggestion and it seems to work so far.
It throws this error:
/home/pi/AIY-voice-kit-python/src/aiy/_drivers/_led.py:51: RuntimeWarning: This channel is already in use, continuing anyway.  Use GPIO.setwarnings(False) to disable warnings.
This is the led for the button but the led seems to work

@joan2937 As far as GpioZero is concerned, the remote-connection feature is pigpio's killer feature ;-)
I don't think GpioZero actually makes use of High speed sampling and accurate time-stamping (although I'm sure other people must find them useful) - GpioZero kinda adopts a lowest-common-denominator approach, so that different GPIO libraries can be swapped in and out.
@av4625 Glad to hear that things are working now :-)

@lurch
One thing I would do, time permitting, is copy the source base and make a new project.  I'd then strip out all the DMA sampling, waves, PWM.  That would leave generic code which should work on any Linux platform.  There would still be a lot of functionality left.  Sampling and PWM could be added back in albeit in a degraded pure software form.


🐛 BUG: When the environment variable is empty, bindings from another environment are loaded.

Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
3.61.0
What version of Node are you using?
v22.1.0
What operating system and version are you using?
Sonoma 14.4.1
Describe the Bug
Observed behavior
I want to use different D1 for the validation environment and the production environment. To do so, I set up wrangler.toml as follows:
[env.stg]
d1_databases = [
  { binding = "DB", database_name = "db-stg", database_id = <stg-db-id> },
]

[env]
d1_databases = [
  { binding = "DB", database_name = "db", database_id = <prd-db-id> },
]

[[d1_databases]]
binding = "DB"
database_name = "db-stg"
database_id = <stg-db-id>

[[d1_databases]]
binding = "DB"
database_name = "db"
database_id = <prd-db-id>

Then deploy to Cloudflare Workers it with the wrangler deploy command.
However, this configuration will cause the deployment to fail with the following error:
Your worker has access to the following bindings:
- D1 Databases:
  - DB: db-stg (<stg-db-id>)
  - DB: db (<prd-db-id>)

✘ [ERROR] A request to the Cloudflare API (/accounts/<accountId>/workers/scripts/<productName>) failed.

  the binding name 'DB' cannot be used more than once [code: 10053]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

Expected behavior
This is probably due to the fact that the value of env.stg is being read even though the environment variable has not been set.
If I set the environment variable to stg, this works fine.
However, I don't want the production app name to have -prd attached to it, so I want to deploy it with empty environment variables.
Thanks for reading.
Please provide a link to a minimal reproduction
https://github.com/ogadra/empty-variable-in-wrangler
Please provide any relevant error logs
No response

This is because your wrangler.toml is not valid. If you converted it to JSON it would look like this:
{
  "compatibility_date": "2024-06-20",
  "compatibility_flags": [
    "nodejs_compat"
  ],
  "main": "src/index.ts",
  "name": "empty-variable-in-wrangler",
  "d1_databases": [
    {
      "binding": "DB",
      "database_id": "<stg-db-id>",
      "database_name": "db-stg"
    },
    {
      "binding": "DB",
      "database_id": "<prd-db-id>",
      "database_name": "db"
    }
  ],
  "env": {
    "d1_databases": [
      {
        "binding": "DB",
        "database_id": "<prd-db-id>",
        "database_name": "db"
      }
    ],
    "stg": {
      "d1_databases": [
        {
          "binding": "DB",
          "database_id": "<stg-db-id>",
          "database_name": "db-stg"
        }
      ]
    }
  }
}

You can see that you have added two DB bindings to the top-level - amongst other issues.
We have a PR to provide better errors in this case: https://github.com/cloudflare/workers-sdk/pull/5737

@petebacondarwin So, I can't switch the database binding with the stage name, can I?  Thanks.

I'm not quite sure what you mean but I think what you want in your wrangler.toml is something like:

@petebacondarwin I did it!! Thanks for your advice!


Executor failed to await responses

System Info

CPU architecture: x86_64
GPU name: NVIDIA A100
TensorRT-LLM tag: v0.10.0

Who can help?
@byshiue
Information

[ ] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
tle::IdType request_id = executor_->enqueueRequest(std::move(request));
std::vector<tle::Response> responses = executor_->awaitResponses(request_id);
tle::Response& response = responses.at(0);
if (response.hasError()) {
  LOG(ERROR) << "Failed to predict: " << response.getErrorMsg();
}

Expected behavior
No error.
actual behavior
Failed to predict: Encountered an error in forwardAsync function: [TensorRT-LLM][ERROR] Assertion failed: Unable to get batch slot for reqId (/home/jenkins/agent/workspace/LLM/release-0.10/L0_PostMerge/llm/cpp/tensorrt_llm/batch_manager/trtGptModelInflightBatching.cpp:679)
1       0x7f5528ff196e tensorrt_llm::common::throwRuntimeError(char const*, int, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) + 78
2       0x7f552900ef23 /usr/lib64/libtensorrt_llm.so(+0x422f23) [0x7f552900ef23]
3       0x7f5529c99ac4 tensorrt_llm::batch_manager::TrtGptModelInflightBatching::forwardAsync(std::__cxx11::list<std::shared_ptr<tensorrt_llm::batch_manager::LlmRequest>, std::allocator<std::shared_ptr<tensorrt_llm::batch_manager::LlmRequest> > > const&) + 1828
4       0x7f5529cbdc57 tensorrt_llm::executor::Executor::Impl::forwardAsync(std::__cxx11::list<std::shared_ptr<tensorrt_llm::batch_manager::LlmRequest>, std::allocator<std::shared_ptr<tensorrt_llm::batch_manager::LlmRequest> > >&) + 71
5       0x7f5529cc149c tensorrt_llm::executor::Executor::Impl::executionLoop() + 396
6       0x7f55110f15a0 /usr/lib64/libstdc++.so.6(+0xce5a0) [0x7f55110f15a0]
7       0x7f5510b0cea5 /usr/lib64/libpthread.so.0(+0x7ea5) [0x7f5510b0cea5]
8       0x7f550f9a3b0d clone + 109
additional notes
The issue is easier to reproduce when the QPS is lower.

Hi @xingdiyou could u please try the latest code base to see if the issue still exists on your side?


Implement dynamic language/locale switching

[ ] Can switch between languages on the fly
[ ] Can switch between locale on the fly

This is not longer possible because of subdomains. All we would do it put in links to subdomains.
New issue can be created when Angular 7 comes out.


feat(selectors): Adding selectors inside the chaosengine

Signed-off-by: Shubham Chaudhary<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Checklist:

[ ] Fixes #
[ ] PR messages has document related information
[ ] Labelled this PR & related issue with breaking-changes tag
[ ] PR messages has breaking changes related information
[ ] Labelled this PR & related issue with requires-upgrade tag
[ ] PR messages has upgrade related information
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] E2E run Required for the changes

Can we resolve the conflicts?


Listen to custom port

This PR introduces a new configuration field api.port, so users can run the Vulnerability DB API in a port different than :8080
The default value will be 8080, so existing toml files are kept valid.

Hi @jesusfcr, thanks for having a look into this! :smile:
I have added the port to the config.toml, README.md and local.env files.
There was no need to add to run.toml, since it's auto generate based on the contents of config.toml plus local.env, the port will be added to file after we run envsubst on it. Let me know if it does not work like that.

Hi @jesusfcr, thanks for having a look into this! 😄
I have added the port to the config.toml, README.md and local.env files.
There was no need to add to run.toml, since it's auto generate based on the contents of config.toml plus local.env, the port will be added to file after we run envsubst on it. Let me know if it does not work like that.

Hi, is in config.toml where you have to use the variable.

@jesusfcr done!


devices: remove duplicated disks after the readlink resolve

If a disk has a symlink it will be re-added to the devices lists one with resolved path and the other with a defined path. We can rebuild the list from the readlink output cause readlink always return the correct path for all disks.
Signed-off-by: Seena Fallah<EMAIL_ADDRESS>

jenkins test centos-container-all_in_one

@guits Can you take a look? Seems something is wrong with jenkins.

@clwluvw Hi! There was an issue with the latest versions of podman which required a fix. Could you rebase and push your PR(s) again? Thx


feat(weave): Add a new deployment and service for gorilla parquet

This PR is included in version 1.9.0 :tada:


Support SASL/Bearer for the Kafka Bindings

Describe the bug
When service binding provides type as SASL/OAUTH Bearer Kafka connection doesn't work.
This is due to the missing authorization server URL provided by binding.
This is up to discussion if that type should be supported.
I'm logging issue in quarkus and RHOAS operator

See: https://github.com/quarkusio/quarkus/issues/17005


Understanding pass through columns

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
In staging model for Companies, we have a field property_annualrevenue.
Today I used hubspot__company_pass_through_columns to only bring columns I need to the intermediate models. I added the following:
hubspot__company_pass_through_columns:
  - name: "property_annualrevenue"
    alias: "annualrevenue"

But even with the above code, the resulting column in hubspot__companies is company_annual_revenue. I don't understand few things:

Is the word "property" automatically stripped out?
Why isn't alias I chose used?
Why is the word "company" added to that field?

Relevant error log or model output
No response
Expected behavior
The column name is exactly as in alias
dbt Project configurations
  hubspot__company_pass_through_columns:
    - name: "property_annual_revenue"
      alias: "annual_revenue"

Package versions
packages:
  - package: dbt-labs/audit_helper
    version: 0.9.0
  - package: fivetran/hubspot
    version: [">=0.9.0", "<0.10.0"]

What database are you using dbt with?
snowflake
dbt Version
$ dbt --version
Core:
  - installed: 1.5.0
  - latest:    1.5.0 - Up to date!

Plugins:
  - bigquery:  1.5.1 - Up to date!
  - postgres:  1.5.0 - Up to date!
  - redshift:  1.5.1 - Up to date!
  - snowflake: 1.5.0 - Up to date!

Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @moseleyi thanks for opening this issue, I just wanted to confirm that you intended to close the issue. Were you able to get your passthrough columns to succeed within the package?

@fivetran-joemarkiewicz yes I managed to get it working, can't remember what it was but I think it was my yaml indentation that was at fault


Bind to other node signals cause crash when hotreload

Connecting to signals in the same node has no problems. But I'm using nodes in the editor for configuring procedural generation. When I make changes the nodes they emit a "changed" signal. A parent node has connected to these signals to detect changes and regenerate the level.
However, as soon the editor reloads the extension after compilation it crashes with SIGSEGV: Illegal storage access.. If I remove the line in the parent node that connects to the child signals then it doesn't crash. Might be solved by having all signals get disconnected when the extension is unloaded.

@xix-xeaon
The test code reproduced based on your report is in testproject/editor.
Please let me know if there are any errors or additions.

Did your test project fail before this fix? In either case, this fix does not fix the problem in my project. I tried creating a reproduction test project but was unable. I may have misunderstood the problem, I'll have to do some more debugging.

Yes. There was a bug that caused hot reloading to fail if a user-defined class was requested as an argument.
Does Nim output a stack trace before or after the SIGSEGV error? Or, is it possible that a previous version of the library remains and is being referenced?

Well, I was wrong about the cause of this bug. The parent node has a gdexport property for choosing the MeshInstance3D which contains the hightmap to be manipulated, and guarding access to this property with a isNil check solved the problem.
It seems that when the extension is reloaded, all the properties on the child are set first which triggers the change signal which is still connected to the parent, causing the generation function on the parent to run. However, at this point in time, the properties on the parent have not yet been set, and the reference to the heightmap is nil.
It is only after all the properties on the children have been set (and their setters have been called, as well as the functions connected to the signals that they emit) that the parent properties are finally set.
Essentially, during the reload all properties momentarily become unset, so you can't depend on properties on other nodes having been set yet, even though they're supposed to have a value. I would assume this is simply how Godot works and not a fault of gdext-nim.


a minor mistake

In the Spike Detection part
"Use the IidSpikeEstimator to train the model for spike detection. Add it to the DetectChangepoint() method with the following code:" --> DetectChangepoint() must be DetectSpike()

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

ID: 0953823a-7d2a-a323-5365-d9a349385552
Version Independent ID: 54ec317c-cfb9-0c2c-ccc2-4b90a5746e99
Content: Tutorial: Detect anomalies in product sales - ML.NET
Content Source: docs/machine-learning/tutorials/sales-anomaly-detection.md
Product: dotnet-ml
GitHub Login: @JRAlexander
Microsoft Alias: johalex

Thanks, @LanderVe! We'll get that fixed and I'll reference this in the PR to keep you in the loop. Thanks again for your help. Good catch


unreadable output on pwsh 6 on windows 10

Thank you for reporting this. I haven't tried it on Windows at all. Could you try to build from this branch (https://github.com/sharkdp/hexyl/pull/3) and see if this solves the problem?


Feature Request - Loot Capacitor functionality

Is there an existing proposal for this?

[x] I did not find any existing requests.

Explain your idea
I would like to ask that loot capacitors which increase the operation speed of a machine also increase the push/pull rate of moving items.
Why do you thing this feature belongs in Ender IO.
The SAG mill output gets backed up and the machine speed is severely limited by the speed it moves items, which kind of nullifies the point of the fancy loot capacitor
Are there any alternatives?
The only one I can think of would be to increase the transfer speed without regard for the capacitor, but that seems too strong.
Any Additional Information?
No response

I assume this is using push/pull I/O to adjacent inventories? Generally I’d expect people to be using conduits for high throughput but this can be something we can consider :)


build: dereference a variable when checking (NFC)

Some versions of CMake dereference the variable here and others do not.
Explicitly dereference to ensure that the library name is properly set.
Failure to do so will fail to load the library as the output path
becomes the name.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test and merge

CC: @vgorloff


build_with_nuitka breaks Jinja2

build_with_nuitka uses "--nofollow-import-to=*.tests" which breaks Jinja2 which has a jinja2.tests for the tests used in the Jinja2 templating language.
(I have a temporary workaround, so no rush on how to solve this)

You can specify --follow-import-to=jinja2.tests for this I believe. Let me know if that is not the case. Maybe it should be documented though.


Autocomplete onBlur clears the selected value

Bug report 🐞
Version & Environment

Version of browser:

Chrome v92.0.4515.159
Brave v1.29.77

Version of geist-ui/react: v2.2.0

Expected Behaviour
The behavior I expect is to have the value of the Autocomplete remain in place in the event that a user clicks away from the Autocomplete without selecting a new item.
Actual results (or Errors)
I got an error:
There are no errors thrown in this case. The autocomplete simply is not persisting the previously selected value, when you click away without selecting a new option.
<AutoComplete
      initialValue={value}
      value={value}
      width={width || '100%'}
      placeholder="Search by zone name"
      disableFreeSolo
      clearable
      options={listOptions}
      onSearch={handleSearch}
      onSelect={handleSelect}
      scale={1}>
  <AutoComplete.Empty>
    No Options...
  </AutoComplete.Empty>
</AutoComplete>

I've posted a video of this issue in the next comment 👍
Additional Notes:
We are not controlling the onBlur event, and we did notice that when we add a onBlur handler to the AutoComplete component it no longer closes the menu upon clicking away from the Autocomplete.

https://user-images.githubusercontent.com/9354827/132398894-3ca76a50-ff66-48fb-b7ed-b5d4fcaeb5b0.mov

Hi @stormy251, is the Test option the initial value? Do you have a value string for each option?

Hey @ofekashery,
Thank you for your response, I have double checked, that each item in the options array contains a non empty string value. In this case the Test option is the initial value correct 👍 .
If I had to guess where this problem/potential bug exists, I would say there is some sort of onBlur internal to the AutoComplete, that when I provide disableFreeSolo &  clearable  properties, it complicates the onBlur, and results in clearing the currently set value.

This is a feature of AutoComplete. When you turn on the disableFreeSolo, you can only enter values from the list.
The reason for this problem is that the value or initialValue of component AutoComplete is not exactly equal to the one provided in options.value.

I tested this again manually and if value / initialValue and option.value are equal, then onBlur does not remove the value of the input box in disableFreeSole & clearable mode.

This issue was closed because it was not active for a long time, please reopen when there are updates.


feat: Frame Processors for Android

🤫
resolves #164
resolves #212

I'm blocked by https://github.com/facebookincubator/fbjni/issues/61. If there's any (fb)JNI experts reading this, please let me know if you can help me. cc @G0retZ

All checks have passed

Lets gooooo


Bugfixes

Description
changed form UI
Affected Dependencies
None
How has this been tested?
Locally
Gif:

Checklist

[x] I have followed the Contribution Guidelines.
[x] My changes do not edit/add any unrequired files.
[x] My changes are covered by tests.

previous commits coming will make a new!


version aware backup

our backup should be version aware. etcd 3.1 could only recover from 3.1 backup not 3.0.

Closed by #396


chore: fix some log error about pr622

Signed-off-by: Daniel Hu<EMAIL_ADDRESS>Description
chore: fix some log error about pr622

I forgot to push this commit to pr #662


New version: PencilArrays v0.12.2

Registering package: PencilArrays
Repository: https://github.com/jipolanco/PencilArrays.jl
Created by: @jipolanco
Version: v0.12.2
Commit: eeda3ef4b65c2f75882ee7186f592ffeee20a333
Reviewed by: @jipolanco
Reference: https://github.com/jipolanco/PencilArrays.jl/commit/eeda3ef4b65c2f75882ee7186f592ffeee20a333#commitcomment-63532000
Description: Distributed Julia arrays using the MPI protocol

@jipolanco did you skip version on purpose?  What do you want us to do?
[noblock]

Sorry about that, it was an accident.
Please feel free to close this PR and I'll soon tag the right version.


Drawing binary search trees in StackEdit

Hi, just asking, is it possible to draw diagrams like these:
https://en.wikipedia.org/wiki/Binary_search_tree
I'm more used to graphviz-style syntax whereas it seems flowchart.js and the other UML sequence-style diagram syntax are kind of limiting in what kind of graphs can actually be output. Perhaps some thought could be given to perhaps implementing the syntax the way like Haroopad does?
http://pad.haroopress.com/page.html?f=how-to-draw-diagram
It's a lot easier to work with and far more human-readable, imho.
Thanks!

That would be useful.


feat: support params for lw monitors with push

fix #725
Add support for pushing params for Lightweight monitors when used in

Synthetics config file
CLI flags --params {"foo": "bar"}

Update: Waiting for Kibana to accept the params support before making progress on the agent side.

Kibana side is done https://github.com/elastic/kibana/pull/157226, ready for review and E2E.


error while executing at wasm backtrace:

Is there any sample code for accessing the file system?

@w01fb0ss - this worked for me.. would you be able to try my reproduced version of your code and see if it fails similarly on your machine?
https://github.com/nilslice/debug-501

@w01fb0ss - this worked for me.. would you be able to try my reproduced version of your code and see if it fails similarly on your machine?
https://github.com/nilslice/debug-501

The code runs successfully, sorry, this is my problem, I will close this issue


Spin ebs_raid into its own cookbook

This is a very opinionated resource that isn't part of the core AWS offerings.  We should continue to support it as a company, but we should make this cookbook focus on management of the core AWS resources.

I think it actually makes the most sense here for now.  It needs some refactoring though.


When to add support for windows 7 asa target platform ?

The "flutter-desktop-embedding" still can not run on windows 7 system,i can not fix this problem,hope this problem have a official fix.

@biij5698 Please, continue the discussion in the #40855, no need to create a new issue as it was already mentioned that there is no specific plan to support it.