text:
After update to latest version 1.14.2 errors

Describe The Bug
repeating TypeError message: processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
Stopping de Hombridge Switcht plugin stops the errors in the logging.
To Reproduce
Update from 1.14.1  ->> 1.14.2
Expected behavior
no TypeError
Relevant log output
[20/08/2022, 11:45:07] [HB Supervisor] OS: Linux 5.15.56-v7+ arm
[20/08/2022, 11:45:07] [HB Supervisor] Node.js v16.17.0 /opt/homebridge/bin/node
[20/08/2022, 11:45:07] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge
[20/08/2022, 11:45:07] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[20/08/2022, 11:45:17] [Homebridge UI] Homebridge Config UI X v4.50.1 is listening on :: port 8581
[20/08/2022, 11:45:18] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[20/08/2022, 11:45:19] [HB Supervisor] Started Homebridge v1.5.0 with PID: 966
[20/08/2022, 11:45:21] Loaded config.json with 6 accessories and 9 platforms.
[20/08/2022, 11:45:22] Loaded 20 cached accessories from cachedAccessories.
[20/08/2022, 11:45:22] ---
[20/08/2022, 11:45:23] Loaded plugin: homebridge-edomoticz@2.1.38
[20/08/2022, 11:45:23] Registering platform 'homebridge-edomoticz.eDomoticz'
[20/08/2022, 11:45:23] ---
[20/08/2022, 11:45:24] Disabled plugin: homebridge-eveatmo@0.6.5
[20/08/2022, 11:45:24] ---
[20/08/2022, 11:45:24] Loaded plugin: homebridge-fritz-platform@6.0.19
[20/08/2022, 11:45:27] Registering platform 'homebridge-fritz-platform.FritzPlatform'
[20/08/2022, 11:45:27] ---
[20/08/2022, 11:45:33] Disabled plugin: homebridge-mqttthing@1.1.41
[20/08/2022, 11:45:33] ---
[20/08/2022, 11:45:34] Disabled plugin: homebridge-netcast-tv@2.0.2
[20/08/2022, 11:45:34] ---
[20/08/2022, 11:45:34] Loaded plugin: homebridge-nodemcu-roomba876@0.1.23
[20/08/2022, 11:45:34] Registering accessory 'homebridge-nodemcu-roomba876.Roomba876'
[20/08/2022, 11:45:34] ---
[20/08/2022, 11:45:34] Disabled plugin: homebridge-otgw@2.0.7
[20/08/2022, 11:45:34] ---
[20/08/2022, 11:45:34] Loaded plugin: homebridge-pihole@0.4.1
[20/08/2022, 11:45:34] Registering accessory 'homebridge-pihole.Pihole'
[20/08/2022, 11:45:34] ---
[20/08/2022, 11:45:39] Loaded plugin: homebridge-ring@11.0.7
[20/08/2022, 11:45:39] Registering platform 'homebridge-ring.Ring'
[20/08/2022, 11:45:39] ---
[20/08/2022, 11:45:39] Disabled plugin: homebridge-rpi@1.3.25
[20/08/2022, 11:45:39] ---
[20/08/2022, 11:45:39] Loaded plugin: homebridge-shelly@0.19.1
[20/08/2022, 11:45:41] Registering platform 'homebridge-shelly.Shelly'
[20/08/2022, 11:45:41] ---
[20/08/2022, 11:45:41] Loaded plugin: homebridge-tiedyegeek-hyperion-ng@0.8.4
[20/08/2022, 11:45:41] Registering accessory 'homebridge-tiedyegeek-hyperion-ng.Hyperion'
[20/08/2022, 11:45:41] ---
[20/08/2022, 11:45:48] Loaded plugin: @switchbot/homebridge-switchbot@1.14.2
[20/08/2022, 11:45:48] Registering platform '@switchbot/homebridge-switchbot.SwitchBot'
[20/08/2022, 11:45:48] ---
[20/08/2022, 11:45:48] Loading 9 platforms...
[20/08/2022, 11:45:48] Ignoring config for the platform "eveatmo" in your config.json as the plugin "homebridge-eveatmo" has been disabled.
[20/08/2022, 11:45:48] Ignoring config for the platform "OTGW" in your config.json as the plugin "homebridge-otgw" has been disabled.
[20/08/2022, 11:45:48] [Shelly] Initializing Shelly platform...
[20/08/2022, 11:45:48] Ignoring config for the platform "netcasttv" in your config.json as the plugin "homebridge-netcast-tv" has been disabled.
[20/08/2022, 11:45:48] [FritzPlatform] Initializing FritzPlatform platform...
[20/08/2022, 11:45:54] [Domoticz] Initializing eDomoticz platform...
[20/08/2022, 11:45:54] [SwitchBot] Initializing SwitchBot platform...
[20/08/2022, 11:45:54] [SwitchBot] Platform Config: {"logging":"standard"}
[20/08/2022, 11:45:54] [Ring] Initializing Ring platform...
[20/08/2022, 11:45:54] Loading 6 accessories...
[20/08/2022, 11:45:54] [Roomba] Initializing Roomba876 accessory...
[20/08/2022, 11:45:54] [Roomba] Initialised Roomba with Name: [Roomba] Hostname: [http://192.168.1.125] Model: [606]
[20/08/2022, 11:45:54] [Roomba] Services requested
[20/08/2022, 11:45:54] [Roomba] Reporting that we support AccessoryInformation, SwitchService and BatteryService
[20/08/2022, 11:45:54] [TV Backlight] Initializing Hyperion accessory...
[20/08/2022, 11:45:54] [TV Backlight] Starting Hyperion Accessory
[20/08/2022, 11:45:54] [Pihole] Initializing Pihole accessory...
[20/08/2022, 11:45:54] Ignoring config for the accessory "mqttthing" in your config.json as the plugin "homebridge-mqttthing" has been disabled.
[20/08/2022, 11:45:54] Ignoring config for the accessory "mqttthing" in your config.json as the plugin "homebridge-mqttthing" has been disabled.
[20/08/2022, 11:45:54] Ignoring config for the accessory "mqttthing" in your config.json as the plugin "homebridge-mqttthing" has been disabled.
[20/08/2022, 11:45:54] [Ring] Configuring cached accessory d583db62-f2e0-4b43-8b37-6aa1a37c0721 Voordeur
[20/08/2022, 11:45:54] [Ring] Configuring cached accessory b4b0e9e6-8277-46cb-907d-06f58f321df3 Gang
[20/08/2022, 11:45:54] [Ring] Configuring cached accessory 13ac7f2a-0f10-47d5-9c4c-43c686184559 Thuis Mode
[20/08/2022, 11:45:54] [Shelly] 1 accessory loaded from cache
[20/08/2022, 11:45:55] [Domoticz] synchronizeAccessories in progress...
Setup Payload:
X-HM://0023T6VP45BJ9
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐
    │ 205-90-328 │
    └────────────┘

[20/08/2022, 11:45:55] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge 8242) is running on port 51070.
[20/08/2022, 11:45:55] [Shelly] Admin server is running on port 8181
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590: Configuring cached accessory...
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590 Wifi 2ghz: Configuring cached accessory...
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590 Wifi 5ghz: Configuring cached accessory...
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590: Setup accessory...
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590 Wifi 2ghz: Setup accessory...
[20/08/2022, 11:45:55] [FritzPlatform]  FRITZ Box 7590 Wifi 5ghz: Setup accessory...
[20/08/2022, 11:45:55] [SwitchBot] Total SwitchBot Devices Found: 1
[20/08/2022, 11:45:55] [SwitchBot] Restoring existing accessory from cache: Curtain 90 DeviceID: E3255EA70290
[20/08/2022, 11:45:55] [SwitchBot] Curtain: Curtain 90 scanDuration is less then updateRate, overriding scanDuration with updateRate
[20/08/2022, 11:45:55] [SwitchBot] Curtain: Curtain 90 Config: {"set_minStep":20,"setOpenMode":"0","setCloseMode":"0","ble":true,"logging":"standard"}
[20/08/2022, 11:45:56] [Roomba] Power state requested for Roomba
[20/08/2022, 11:45:56] [Roomba] Battery level requested for Roomba
[20/08/2022, 11:45:56] [Roomba] Charging status requested for Roomba
[20/08/2022, 11:45:57] [Pihole] {"data":{"status":"enabled"},"status":200,"statusText":"OK","headers":{"set-cookie":["PHPSESSID=o2aig8fuqvfego4bf3isjm9b2d; path=/; HttpOnly"],"expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-store, no-cache, must-revalidate","pragma":"no-cache","content-type":"application/json","x-pi-hole":"The Pi-hole Web interface is working!","x-frame-options":"DENY","content-length":"20","connection":"close","date":"Sat, 20 Aug 2022 09:45:57 GMT","server":"lighttpd/1.4.59"},"request":{"method":"GET","url":"api.php","params":{"status":1},"baseURL":"http://192.168.1.111:80/admin/","responseType":"json"}}
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
[20/08/2022, 11:45:58] [Ring] Found the following locations:
[20/08/2022, 11:45:58] [Ring]   locationId: 3ebb8044-423c-4d30-9a97-b9ac67680962 - Thuis
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
[20/08/2022, 11:45:59] [Ring] Configuring 1 cameras and 3 devices for location "Thuis" - locationId: 3ebb8044-423c-4d30-9a97-b9ac67680962
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
[20/08/2022, 11:45:59] [homebridge-nodemcu-roomba876] This plugin slows down Homebridge. The read handler for the characteristic 'Battery Level' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[20/08/2022, 11:45:59] [homebridge-nodemcu-roomba876] This plugin slows down Homebridge. The read handler for the characteristic 'Charging State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
[20/08/2022, 11:46:00] [Roomba] Failed to get roomba battery level
[20/08/2022, 11:46:00] [Roomba] FetchError: request to http://192.168.1.125/status failed, reason: connect EHOSTUNREACH 192.168.1.125:80
    at ClientRequest.<anonymous> (/var/lib/homebridge/node_modules/homebridge-nodemcu-roomba876/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:513:28)
    at Socket.socketErrorListener (node:_http_client:481:9)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
[20/08/2022, 11:46:00] [Roomba] Failed to get roomba charging status
[20/08/2022, 11:46:00] [Roomba] FetchError: request to http://192.168.1.125/status failed, reason: connect EHOSTUNREACH 192.168.1.125:80
    at ClientRequest.<anonymous> (/var/lib/homebridge/node_modu

Config for homebridge-switchbot
{
    "name": "SwitchBot",
    "credentials": {
        "openToken": "8668c1cd56faef6d66e6226497b815c36ea08c41c1a47b8a715a548c83d4258c0ff370ad65f65fffe050e1d84a811ba0",
        "notice": "Keep your token a secret!"
    },
    "options": {
        "devices": [
            {
                "deviceId": "E3:25:5E:A7:02:90",
                "configDeviceName": "Curtain 90",
                "configDeviceType": "Curtain",
                "ble": true,
                "curtain": {
                    "set_minStep": 20,
                    "setOpenMode": "0",
                    "setCloseMode": "0"
                },
                "logging": "standard"
            }
        ],
        "logging": "standard"
    },
    "platform": "SwitchBot"
}

Screenshots
No response
Device & Model
Curtain 90
Node.js Version
v16.17.0
NPM Version
8.15.0
Homebridge Version
v1.5.0
Homebridge Switchbot Plugin Version
v1.14.2
Homebridge Config UI X Plugin Version
v4.50.1
Operating System
Raspian

I have this error too and it persists when returning to 1.14.0

None of those errors look like they are coming from SwitchBot

Hello Donavan,
That is a little fast concluded. After upgrading to the latest plugin it started with this error.
And when you dis-enable the Switcht plugin, the error disappears. so how can you tell "None of those errors look like they are coming from SwitchBot.
Thanks!
greet Pieter

Op 21 aug. 2022, om 14:04 heeft Donavan Becker @.***> het volgende geschreven:
Closed #444 https://github.com/OpenWonderLabs/homebridge-switchbot/issues/444 as not planned.
—
Reply to this email directly, view it on GitHub https://github.com/OpenWonderLabs/homebridge-switchbot/issues/444#event-7227616129, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH4FISU7URGICCSCGYAFVLV2ILLNANCNFSM57C7CYSA.
You are receiving this because you authored the thread.

Can confirm as well, got the same after updating to 1.14.2, but it seems to persist even if rolling back to the older version.
Disabling the plugin stops the log from spamming.

Heel Donavan,
Please reopen this issue, there are more people having this issue.
Thanks
vriendelijke groet,
Pieter
Op 21 aug. 2022 om 14:27 heeft Zaki @.***> het volgende geschreven:

Can confirm as well, got the same after updating to 1.14.2, but it seems to persist even if rolling back to the older version.
Disabling the plugin stops the log from spamming.
[image]https://user-images.githubusercontent.com/31648832/185790829-6fb10de3-dc53-423c-a2bd-a1364b21044c.png
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenWonderLabs/homebridge-switchbot/issues/444#issuecomment-1221536082, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH4FIQKF2E3OM5BXTL2H7DV2IOEPANCNFSM57C7CYSA.
You are receiving this because you authored the thread.Message ID: @.***>

SwitchBot are the only BLE devices I’m running from Homebridge

Same with @grunkyb  here.

Same as @zaki and @grunkyb only Switchbot is my ble device in Homebridge....

@PvdGulik I am not experiencing this and that is why it is closed as cannot reproduce.

@PvdGulik I am not experiencing this and that is why it is closed as cannot reproduce.

I am also experiencing this as well after update, seems it might be an API you use as even rolling back, or switching to the other Switchbot API that is Bluetooth only has this. Only disabling the plug-in the issue goes away.

same issue here.
rollback to 1.14.1 makes the error disappear for me.

Here's how it looks with my debug logs turned on for SwitchBot
[22/08/2022, 17:55:35] [SwitchBot] 01:23:45:67:89:ab
[22/08/2022, 17:55:35] [SwitchBot] 01:23:45:67:89:ab
[22/08/2022, 17:55:35] [SwitchBot] Humidifier: Humidifier BLE Address Found: 01:23:45:67:89:ab
[22/08/2022, 17:55:35] [SwitchBot] Humidifier: Humidifier Config BLE Address: 01:23:45:67:89:ab
[22/08/2022, 17:55:35] [SwitchBot] [DEBUG] Humidifier: Humidifier serviceData: {"model":"e","modelName":"WoHumi","onState":true,"autoMode":false,"percentage":27}
[22/08/2022, 17:55:35] [SwitchBot] [DEBUG] Humidifier: Humidifier model: e, modelName: WoHumi,autoMode: false, onState: true, percentage: 27
[22/08/2022, 17:55:35] [SwitchBot] [DEBUG] Humidifier: Humidifier connected: true
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')

Show more of the log
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')

This repeats itself a few times with varying numbers of repeats of the TypeError then this
[22/08/2022, 17:55:43] [SwitchBot] 01:23:45:67:89:ab
[22/08/2022, 17:55:43] [SwitchBot] 01:23:45:67:89:ab
[22/08/2022, 17:55:43] [SwitchBot] Humidifier: Humidifier BLE Address Found: 01:23:45:67:89:ab
[22/08/2022, 17:55:43] [SwitchBot] Humidifier: Humidifier Config BLE Address: 01:23:45:67:89:ab
[22/08/2022, 17:55:43] [SwitchBot] [DEBUG] Humidifier: Humidifier serviceData: {"model":"e","modelName":"WoHumi","onState":true,"autoMode":false,"percentage":27}
[22/08/2022, 17:55:43] [SwitchBot] [DEBUG] Humidifier: Humidifier model: e, modelName: WoHumi,autoMode: false, onState: true, percentage: 27
[22/08/2022, 17:55:43] [SwitchBot] [DEBUG] Humidifier: Humidifier connected: true
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')

Show more of the log

processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
processLeAdvertisingReport: Caught illegal packet (buffer overflow): TypeError: Cannot read properties of undefined (reading 'slice')
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier BLE parseStatus
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier CurrentRelativeHumidity: 27
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier Active: 1
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier updateCharacteristic CurrentRelativeHumidity: 27
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier updateCharacteristic CurrentHumidifierDehumidifierState: 0
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier updateCharacteristic TargetHumidifierDehumidifierState: 1
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier updateCharacteristic Active: 1
[22/08/2022, 17:55:44] [SwitchBot] [DEBUG] Humidifier: Humidifier updateCharacteristic RelativeHumidityHumidifierThreshold: 0

Hello Donavan, Please reopen this issue, as you can SER there are more and more people having this issue. Thanks

I'm able to connect to the device through the OpenAPI, e.g., curl -X GET -k -H 'Authorization: xxxx' -i 'https://api.switch-bot.com/v1.0/devices/0123456789AB/status'
What's everyone using here? I'm on a Raspberry Pi 4B running 64-bit Bullseye.
I'm wondering if it's a Pi + BLE thing but need others to confirm.

For me at least, you can still activate the Switchbot, but there is a lot of spam in the log.
I have pi 3B and using BLE
I also noticed there were some build errors In the post upgrade process with a 404 error for abandonware, but that might be a red herring

Like @TommyGKiwi  mentioned, I can also still use my Switchbot and the existing automations all work fine, it's just the issue with the errors that are spamming the homebridge logs.

Thanks for reopening.
For me the SwitchBot works, just the spam in the log. I’m using a Raspberry Pi 3B+
Thanks
Pieter

I'm having the same issue in version 1.14.2

same issue here.
rollback to 1.14.1 makes the error disappear for me.

I reported the error in my lab env, a pi zero 2, with raspbian homebridge and nothing else.
However, I did the installation of the plugin in my prod env, pi4, with many other plugins, and I don't have the error.

Seems to only be a raspberryPi noisily log issue.

I found that during the installation I get the following error:
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v93-linux-arm.tar.gz
When I browse following that link, there's nothing in https://github.com/abandonware/node-bluetooth-hci-socket/releases/.
Is this related to the Issue #444?
Thanks

This is a node-SwitchBot/noble issue. It will have to resolve at those repos before it can be resolved here.

Can anyone spot anything in this function in noble? You can see that this could be throwing it.
Hci.prototype.processLeAdvertisingReport = function (numReports, data) {
  try {
    for (let i = 0; i < numReports; i++) {
      const type = data.readUInt8(0);
      const addressType = data.readUInt8(1) === 0x01 ? 'random' : 'public';
      const address = data
        .slice(2, 8)
        .toString('hex')
        .match(/.{1,2}/g)
        .reverse()
        .join(':');
      const eirLength = data.readUInt8(8);
      const eir = data.slice(9, eirLength + 9);
      const rssi = data.readInt8(eirLength + 9);

      debug(`\t\t\ttype = ${type}`);
      debug(`\t\t\taddress = ${address}`);
      debug(`\t\t\taddress type = ${addressType}`);
      debug(`\t\t\teir = ${eir.toString('hex')}`);
      debug(`\t\t\trssi = ${rssi}`);

      this.emit(
        'leAdvertisingReport',
        0,
        type,
        address,
        addressType,
        eir,
        rssi
      );

      data = data.slice(eirLength + 10);
    }
  } catch (e) {
    console.warn(
      `processLeAdvertisingReport: Caught illegal packet (buffer overflow): ${e}`
    );
  }
};

I have the same error too.

Has anyone tried this: https://github.com/OpenWonderLabs/homebridge-switchbot/issues/425#issuecomment-1190864279

Yes, but did not resolve the issue..
Still continues errors in the logging

I have the same issue. It switches from local BLE to mini hub, therefore, no operation problem, but log are full of this error.

Not sure why there seems to be two bug reports for the same issue, but I'll chime in. I have the same issue (Raspberry Pi). I suspected SwitchBot since it started after I upgraded to 1.14.2 but when I rolled back the issue persisted. So I wasn't sure. Then I was away on vacation for two weeks. Came back to the issue still happening and I see others have reported the issue here.

I've done an error stack trace on this and found a workaround.
I changed lines 78–80 in OpenWonderLabs/node-switchbot/blob/latest/lib/switchbot-advertising.js from
    if (bufIsInvalid && manufacturerDataIsInvalid) {
      return null;
    }

to
    if (bufIsInvalid || manufacturerDataIsInvalid) {
      return null;
    }

If you look at the blame for the code, you can see that the && manufacturerDataIsInvalid was added on 18 August, right about when this problem started showing up.
On my RPi, the path to the file to change is /var/lib/homebridge/node_modules/@switchbot/homebridge-switchbot/node_modules/node-switchbot/lib.
Can anyone else check this is the right solution?

@grunkyb, I will make this change and then push it out to a beta. can you test it then? it will be part of Issue #476 & Pull Request #474

@grunkyb latest be there has these changes.

Installed v1.15.1-beta.11  early this morning and no more error logs. API 1.1 working well too.

Same here, 1.5.1-beta.11 has resolved the noisy logs for me. Everything works accordingly as well.

Perfect! I will get 2.0.0 all packaged up and publish it soon.

I don't know how to test, but I see it is solved in 2.0.0. When will 2.0.0 be released?

Oke, I installed 2.0.0 but found I only can select Bot, no Curtain. Is that supposed to be so?
Thanks!

Oke, I installed 2.0.0 but found I only can select Bot, no Curtain. Is that supposed to be so?
Thanks!

Do you have a screenshot?

that isn't this plugin.

Fixed with v2.0.0, Once released.

authors: CyberMrProper Niklas31 PvdGulik TommyGKiwi csyee donavanbecker galaxydpw grunkyb nyjklein zaki-hanafiah

repo: OpenWonderLabs/homebridge-switchbot

license: ISC


text:
Support Request: I can't update Swtichbot plugin

Describe Your Problem
I can't update Swtichbot plugin
Relevant log output
USER: pi
DIR: /usr/local
CMD: sudo -E -n npm install -g @switchbot/homebridge-switchbot@2.6.2

(##################) ⠋ reify:googleapis: timing reifyNode:node_modules/@switchbot/home
> @abandonware/bluetooth-hci-socket@0.5.3-10 install
> node-pre-gyp install --fallback-to-build --update-binary

node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-10/bluetooth_hci_socket-0.5.3-10-node-v108-linux-arm.tar.gz
make: Entering directory '/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/build'
  CXX(target) Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o
make: g++: No such file or directorypis: timing reifyNode:node_modules/@switchbot/home
make: *** [bluetooth_hci_socket.target.mk:111: Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o] Error 127
make: Leaving directory '/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Linux 5.10.103-v7l+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--update-binary" "--module=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node" "--module_name=bluetooth_hci_socket" "--module_path=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v108"
gyp ERR! cwd /usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket
gyp ERR! node -v v18.16.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! not ok
node-pre-gyp ERR! build error(##################) ⠼ reify:googleapis: timing reifyNode: ode_modules/@switchbot/home
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --update-binary --module=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node --module_name=bluetooth_hci_socket --module_path=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)
node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1091:16)
node-pre-gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:302:5)
node-pre-gyp ERR! System Linux 5.10.103-v7l+
node-pre-gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--update-binary"
node-pre-gyp ERR! cwd /usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket
node-pre-gyp ERR! node -v v18.16.0
node-pre-gyp ERR! node-pre-gyp -v v1.0.10
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --update-binary --module=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node --module_name=bluetooth_hci_socket --module_path=/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/bluetooth-hci-socket/lib/binding --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)

> @abandonware/noble@1.9.2-20 install
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/noble/build'
  SOLINK_MODULE(target) Release/obj.target/noble.nodeNode:node_modules/@switchbot/home
make: g++: No such file or directory
make: *** [noble.target.mk:20: Release/obj.target/noble.node] Error 127
make: Leaving directory '/usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/noble/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Linux 5.10.103-v7l+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/noble
gyp ERR! node -v v18.16.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! not ok
npm ERR! code 1
npm ERR! path /usr/local/lib/node_modules/@switchbot/homebridge-switchbot/node_modules/@abandonware/noble
npm ERR! command failed
npm ERR! command sh -c node-gyp-build

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2023-04-18T00_21_25_992Z-debug-0.log

Operation failed. Please review log for details.

Config for homebridge-switchbot
No response
Screenshots
No response
Device & Model
Pi
Node.js Version
v18.16.0
NPM Version
v9.5.1
Homebridge Version
v1.6.0
Homebridge SwitchBot Plugin Version
v2.6.2
Homebridge Config UI X Plugin Version
No response
Operating System
Raspian

check #713

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Migrate zos contracts to solidity v0.5.x

I tried to find if the issue is already exists or not, but it seems that there is no duplicates.
Currently, I see that zos-lib contracts almost use solidity v0.4.24. It would be great if the solidity version can be migrated to v0.5.x breaking changes.

Implemented in https://github.com/OpenZeppelin/openzeppelin-sdk/commit/ef03e13516855757b9bcfda6f0a8aab5534240db#diff-4c2060ba83bbf88924e4d2f83222f514. We may want to migrate to 0.6 now though!

repo: OpenZeppelin/openzeppelin-sdk

license: MIT


text:
expectEvent/inLogs could be improved

No support for BigNumbers
The current equality test fails for BigNumber objects (which have an equal method). chai-bignumber supports these assertions with the chain number.should.be.bignumber.equal(otherNumber).

Unnecessary async
There are no awaits in inLogs (and rightly so), but due to it being async, it forces callers to await on the returned promise.

Superceded by #1169 and #1189

Reopening because we have no issue to track supporting BigNumber equality in expectEvent.

authors: frangio nventuro

repo: OpenZeppelin/openzeppelin-solidity


text:
Update ERC721 to match spec

Now that the ERC721 NFT Standard has been merged (https://github.com/ethereum/EIPs/pull/841) and is now a draft standard, the ERC721 implementation at https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/contracts/token/ERC721/ERC721Token.sol should be updated

See #803

authors: gakonst spalladino

repo: OpenZeppelin/zeppelin-solidity

license: mit

license_source: bigquery


text:
Juggernaut "Unyielding" not calculating?

Tried it with multiple skills and no change

Obvious question, do you have Endurance Charges enabled in the Configuration tab?

Yes sir.

Disregard... it's working for me now.  I'm 100% certain I had End Charges enabled and it wasn't showing for any skills, neither with "show node power" color or any change in numbers when allocated.
Sorry.

authors: Kobelayton Openarl

repo: Openarl/PathOfBuilding


text:
fix(app): fix jump to current step when outside current window

Overview
run log jump to current step was not working when the viewport was outside of the current command
window. this reuses the component logic on mount to jump to the current command window.
closes #10898
Changelog

Fixes run log jump to current step when outside current command window

Review requests
for long protocols, confirm that scrolling outside the current command window displays the 'jump to current step' button, and that clicking the button scrolls as expected.
Risk assessment
low

@y3rsh this PR may affect start/end time issues in https://github.com/Opentrons/opentrons/issues/11047

source: gharchive/pull-request

repo: Opentrons/opentrons


text:
Chore Release 7.4.0

This is the working branch for the 7.4.0 release
This release is for HEPA/UV firmware update and a new gripper model version

[!NOTE]
This branch is based on chore_release-7.3.1
chore_release-7.3.1  is not yet merged to release
The diff will be inflated until 7.3.1 is released and chore_release-7.3.1  is merged into release

TODO

[ ] @ahiuchingau  is there more work to do?
[ ] @ahiuchingau once ready, merge to edge then cherry pick gripper version PR into this branch chore_release-7.4.0
[x] @vegano1 cherry pick this PR into this branch chore_release-7.4.0
[ ] @y3rsh create a tag when ready to build for https://github.com/Opentrons/ot3-firmware/pull/782

@y3rsh
PR has been cherry picked
https://github.com/Opentrons/opentrons/pull/15311


text:
refactor(api): mypy: typecheck untyped defs

By default, mypy doesn't check function definitions that do not have
type annotations. This is seen as a sane default to aid introducing
typing to a codebase that doesn't have it previously, and ours was
covered spottily at best. However, it's also very easy to forget to
annotate functions, especially if they don't take arguments -
properties, magic/special dunder methods like iter, that sort of
thing; and that leads to missed opportunities for typechecking, as the
changes in this commit reflect.
Tell mypy to check functions that are not annotated (with carveouts for
older sections of the codebase that we know are soon to be deleted) and
fix up all the errors that notes.
There are few places that actually required code changes, with the most
major being the tools submodule, which needed some changes anyway to
work properly in certain call situations so arguments passed to the
interpreter wouldn't conflict with arguments passed to the scripts.
Risk Assessment
This touches a lot of iles, but most of it is annotation only changes. Key things to test are

opentrons_simulate with some of the more rarely used args like log capture
The scripts in opentrons.tools

Just one question and one request.
Can we put all the changes to the factory tests in a separate PR?

yeah that's a good idea


text:
fix(api): fix APIv1 GPIO ctl for cmdline and jupyter protocol execution

Overview
When the robot server is running, protocols executed in Jupyter or using opentrons_execute would not have control over the GPIOs. Currently, a warning with a workaround is shown if the protocol is in APIv2. However, there is no indication given to the user of why GPIO controls are not working when they are running a v1 protocol.
This PR fixes the issue by surfacing the same warning as v2 and actually implementing the workaround for v1 protocols.
closes #6045

Changelog

adds a new info message right before GPIO chardev is being built in APIv1
allowed GPIO chip access during robot.connect

this automatically surfaces the following warning when a v1 protocol is executed in Jupyter or via opentrons_execute:
Failed to initialize character device, will not be able to control gpios (lights, button, smoothie kill, smoothie reset). If you need to control gpios, first stop the robot server with systemctl stop  opentrons-robot-server. Until you restart the server with systemctl start opentrons-robot-server, you will be unable to control the robot using the Opentrons app.

if the GPIOs are not held by the robot server, the resulting GPIOCharDev (not the simulator) will be set as the robot._driver.gpio_chardev

added setup_v1 function in gpio.py so robot can setup GPIO pins without being async

Review requests
Not sure if adding GPIOCharDev.setup_v1 is the best way to tackle the problem, any suggestions?
Test this PR by executing robot.turn_on_rail_lights() in Jupyter and using opentrons_execute:

before killing the robot server, a warning should be shown that the GPIO char dev has failed to initialized
after killing the server, no warning and the robot lights should turn on

Risk assessment
Low - this PR only affects APIv1 protocols when the robot server is stopped

Can we hold off on merging this, for a sec? I'll start a discussion in Slack.

authors: SyntaxColoring ahiuchingau


text:
Design: Partners Landing

Please use one of the following templates to create new issues:
For a new feature:
As a [VISITOR, ADMIN, ETC],
When I [CONTEXT/LOCATION FOR FEATURE],
It should [DESCRIBE FEATURE]
For a bug:
As a [VISITOR, ADMIN, ETC],
When I [CONTEXT OF BUG]
It [DESCRIBE BUG]
It should [EXPECTED OUTCOME]
See #361 for additional information.

as visitor
in partners landing page
do we have to  make animation for when landing on partners page?

repo: OperationCode/operationcode


text:
Fix menu typography

The current menu text is hard to read and a bit too small.
It should also be horizontally aligned with the logo.

Fixed in #37


text:
Before Insert trigger still violates not-null constraint

Hello, I'm using pg-trigger to update a column in Table 2 (Workspace) before I insert a row in Table 1 (Task):
@pgtrigger.register(
    pgtrigger.Trigger(
        name="increment_workspace_highest_task_number",
        when=pgtrigger.Before,
        operation=pgtrigger.Insert,
        func="""
        DECLARE
        highest_number  INTEGER;
        BEGIN
            SELECT workspace_workspace.highest_task_number INTO highest_number
            FROM workspace_workspace
            WHERE workspace_workspace.id = NEW.workspace_id;
            UPDATE "workspace_workspace" AS workspace
            SET "highest_task_number" = highest_number + 1
            FROM workspace_workspace
            WHERE workspace.id = NEW.workspace_id;
            NEW.number = highest_number + 1;
            RETURN NEW;
        END;""",
    )
)

I'm doing this operation on a Task table (model) that has a number field (column). I get the following error:
psycopg2.errors.NotNullViolation: null value in column "number" violates not-null constraint

Is there a way to bypass that error other than making the column nullable?

A few things to note here.

It seems like your trigger definition may not be compatible with django-pgtrigger. The func attribute is automatically inserted between a BEGIN and END, and the declare attribute of the trigger can be used to declare variables like your declaration. See the anatomy of a trigger in the docs
I assume what's happening is that highest_number has a null value inserted into it instead of a 0. I don't know the exact syntax, but you're probably going to want to do a COALESCE somewhere to return a 0 instead of a null

I believe I've addressed the issue, but feel free to re-open if I haven't

authors: apkallum wesleykendall


text:
How to insert blob?

/*CREATE TABLE images (
    id int PRIMARY KEY,
    image blob
);*/

$stmt = $db->prepare("INSERT INTO images (id, image) VALUES (?, ?);");

$stmt->bindValue(1, 5, PDO::PARAM_INT);

$f = file_get_contents('test.png'); // very small image 1x1px
$stmt->bindValue(2, $f, PDO::PARAM_LOB);

$stmt->execute();

var_dump($stmt->errorInfo());

array(3) {
  [0]=>
  string(5) "00000"
  [1]=>
  int(2)
  [2]=>
  string(16) "Input length = 1"
}

Can someone post a working example, or blob insertion is not working at the moment?

[Info] It seems that inserting blob as strings will not work anymore. I get in system.log this message:
WARN [Thrift:12] 2015-01-14 06:59:32,994 Constants.java (line 181)
Inputing CLQ3 blobs as strings (like ... )
is now deprecated and will be removed in a future version.
You should convert client code to use a blob constant ( ... )
instead (see http://cassandra.apache.org/doc/cql3/CQL.html changelog section for more info).

Now I changed all my code from this
$fileContent = file_get_contents($_FILES['my_file']['tmp_name']);
...
$stmt->bindValue(':file', bin2hex($fileContent));

to this
$stmt->bindValue(':file', "0x". bin2hex($fileContent), PDO::CASSANDRA_BLOB);

Cassandra 1.2.x

Indeed, this is a new CQL constraint

authors: mathieu-lornac moldcraft

repo: Orange-OpenSource/YACassandraPDO


text:
Arguments are being passed as an array

The complete array of arguments are being passed instead of each position as an argument.
instead of  fn.apply(this, [arg1, arg2, arg3])
it was sending fn.apply(this, [[arg1, arg2, arg3]])

Sorry! Wrong fix


text:
InternalsVisibleTo doesn't seem to work

One would use this attribute to e.g. give test projects access to the internal members of another project under test.
In AssemblyInfo.cs under Orchard.Azure.MediaServices we have (line 16):
[assembly: InternalsVisibleTo("Orchard.Azure.MediaServices.Tests")] // Not working. :( Someone please fix.

And I can verify that it's not working with my own module/test project.
Any ideas?

I had the same problem some time ago. Make sure that the AssemblyInfo.cs file is included in the compilation. In the csproj file it should be:
<Compile Include="Properties\AssemblyInfo.cs" />

The codegen utility used to add this file to the project as None or Content. In that case the code is not compiled at all and your attribute is not added to the assembly.

Thanks @MpDzik! Setting Build Action to Compile on the AssemblyInfo.cs file works.

authors: MpDzik thekaveman

repo: OrchardCMS/Orchard


text:
(4/6) Start to initialize Kubernetes master... 安装失败

如题master节点在初始化kubernetes master时失败，install.log也未能打印出错误信息。
个人猜测：
./kubekit s 启动文件服务后，手动kubeadm init验证，发现有错误信息如下：
unable to get URL "https://dl.k8s.io/release/stable-1.8.txt":
Get https://storage.googleapis.com/kubernetes-release/release/stable-1.8.txt: dial tcp 172.217.27.144:443: i/o timeout

kubeadm会去https://storage.googleapis.com/kubernetes-release/release/stable-1.8.txt下载一个文件，需要有外网网络环境，且需要科学上网姿势。
该文件内容为v.1.8.3,建议加入到文件服务中。
另外: 建议把kubeadm执行过程的打印信息也输出至install.log中，方便调试排错，辛苦

遇到了同样的问题， 不过关键的gcr镜像已经有了，后面就手动安装。。

感谢你们的反馈，我会近期重现一下

This issue is resolved
ref:kubeadm init --kubernetes-version=v1.8.2

@Graham-Aker
已经发现作者已经更新了master.sh脚本，添加了--kubernetes-version=v1.8.2
但是似乎还没有更新到package下载包中，下载下来的master.sh脚本中没有--kubernetes-version=v1.8.2

@dengqingpei1990
@Graham-Aker
安装包已经更新

authors: Graham-Aker TimothyYe dengqingpei1990

repo: Orientsoft/kubekit


text:
Automatic Refresh does not work

We use the custom connector to get data from the Clockify API. Everything works fine on PowerBI desktop, but when we turn on the automatic refresh on the PowerBI service the dataset fails to refresh. The error is the following:
Data source error: Column 'Project ID' in Table 'Projects' contains blank values and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.
Cluster URI: WABI-NORTH-EUROPE-L-PRIMARY-redirect.analysis.windows.net
Activity ID: 5ab5cd08-66ba-46d0-822b-3b44b97a0a93
Request ID: 22beef8f-e799-493b-b9b1-d7d5564a79d5
Time: 2022-12-14 07:18:37Z
We have tried everything that could:

Re-installed the custom connector on the getaway
Updated the getaway
Removed all the blank and duplicate values from every table with PowerQuery
Removed the mentioned table, but then we got the same error message for another table.

Also, some times when we upload the dataset with no relationships it refreshes the data, but it returns blank tables.

Please confirm this is related to the MEZ file.

The problem was due to a bug in PowerBI service, all the datasets that had a gateway connection could not refresh. I did not have to do with the MEZ file.

OK then, I will close this issue. Thanks.

authors: OscarValerock vikitsich

repo: OscarValerock/Clockify-PowerBI


text:
Add new student

hi there.
This is my first pr on this course. Please add me to organization.

Здравствуйте!)
Репозитории созданы, приглашение должно быть у вас в почте
Постарайтесь принять их как можно быстрее

Здравствуйте!)
Репозитории созданы, приглашение должно быть у вас в почте
Постарайтесь принять их как можно быстрее


text:
Bias correct notebook

Overview
This PR adds a bias-correction notebook that uses xclim to bias-correct climate model variables and feeds the corrected value into a hydrological model to produce a hydrograph.

I suggest to remove the first part with the vector handling and focus on the bias correction. I think it's easier to follow when tutorials are short and focused, rather than trying to do everything.

@huard Just to be clear - There are 2 notebooks here, one is the Full-process notebook and the other is the bias-correction notebook. Your comment concerns the bias-correction notebook, right?
So what I can do is remove the auto-extraction of area/latitude/etc. and just keep the shapefile geometry part, and provide numerical values as we do at other times, is that good?

Correct.
Yes!

authors: huard richardarsenault

repo: Ouranosinc/raven


text:
Fix Mobile Navigation

Fix mobile navigation

Mobile navfixed

repo: OvoOno-Studio/vue-dapp


text:
Pagination functionality.

Check this out. (Haven't tested, maybe needs a fix)
My recommendations its to remove all $perPage, references. clean all that and just just the new function to read directly from request this 2 vars: limit + page.
What I have seen in other libraries its people gives options to set this vars names, I don't think its necessary, you can always overwrite them.
Its up to you, my suggestions:

Clean, remove all $paginate & $perPage
move functions specs to the contract and just use the,  {@inheritdoc}
show the contract in the readme for people references.

Simple the better.

You need to limit the database query too. So your $query->get() approach is wrong. Also I think people can pass in the item limit from controller easily. No need to overkill a simple thing.
    public function index(Request $request) {
        $this->repo->paginate($request->limit);
    }

You approach also restricts a users ability to use limit as a request parameter while using pagination.

Humm...
$this->repo->paginate() its Laravel defaults.
This pagination implementation needs to know how many records are.
People can do $request->limit = 'xXX'
There is a simplePagination that does not require to know that.
Works well on Lumen, where defaults pagination was not giving right links.
By reading request, we don't need to pass by this vars, but you are the boss here!😋

We can work this out for lumen for sure, it just needs to be cleaned up and go the correct place. We might make a class for lumen or a trait for lumen methods.

Laravels magic resolves the page parameter from the $request, same we doing with limit.
The trick we adding here its to be able to turn pagination on-off by sending the limit in the request.
What this function does its the same than Laravel, but also returns others parameters in the query for the next_page_url and so..
make a test, for example with simple url , check what happens with rest of parameters when you do the paginate using laravel defaults.
Also, have a look at this:: https://github.com/rlacerda83/lumen-api-query-parser/wiki/Usage
its very interesting how parses urls and returns a query build.
with a url like this:
http://musicboxx.dev/v1/role?page=1&order=33&limit=3
Laravel returns:
    "first_page_url": "http://musicboxx.dev/v1/role?page=1",
    "from": 1,
    "last_page": 2,
    "last_page_url": "http://musicboxx.dev/v1/role?page=2",
    "next_page_url": "http://musicboxx.dev/v1/role?page=2",
    "path": "http://musicboxx.dev/v1/role",
    "per_page": 15,
    "prev_page_url": null,
    "to": 15,
    "total": 22

but I think this is more convenient:
    "first_page_url": "http://musicboxx.dev/v1/role?page=1&order=33&limit=3",
    "from": 1,
    "last_page": 8,
    "last_page_url": "http://musicboxx.dev/v1/role?page=8&order=33&limit=3",
    "next_page_url": "http://musicboxx.dev/v1/role?page=2&order=33&limit=3",
    "path": "http://musicboxx.dev/v1/role",
    "per_page": "3",
    "prev_page_url": null,
    "to": 3,
    "total": 22

i would suggest to not "bind" this to specific request parameter (e.g., ?limit=xxx or ?page=xxx) as this would result in not being able to use this package with specific standards (e.g., json:api) that define other parameters..
I think, these query parameters should be customizable in the config file!

authors: OzanKurt johannesschobel kikoseijo

repo: OzanKurt/Repoist


text:
Add dl.setBackend() and remove usage of ENV.math

Fixes #615

This change is

Reviewed 32 of 32 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

src/environment.ts, line 225 at r1 (raw file):

    }
    // tslint:disable-next-line:no-unused-expression
    new NDArrayMath(backendType, safeMode);

this is weird, can you explain this in a comment?

src/math/decorators.ts, line 40 at r1 (raw file):

  'Training': 'Gradients';
  'Performance': 'Memory'|'Timing';
  'Environment': '';

can you put a TODO here to allow a null subheading?

src/math/math.ts, line 240 at r1 (raw file):

    this.disposeData = ENV.engine.disposeData.bind(ENV.engine);
    this.registerVariable = ENV.engine.registerVariable.bind(ENV.engine);
    this.startScope = ENV.engine.startScope.bind(ENV.engine);

this is the only one I'm a little worried about, can you keep this here?

Comments from Reviewable

Review status: 30 of 33 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

src/environment.ts, line 225 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
this is weird, can you explain this in a comment?

made it more explicit (with code). only new NDArrayMath() is truly needed, since the c-tor of NDArrayMath() calls Env.setMath() which does all the setup, but this way is more explicit.

src/math/decorators.ts, line 40 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
can you put a TODO here to allow a null subheading?

Done.

src/math/math.ts, line 240 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
this is the only one I'm a little worried about, can you keep this here?

Done.

Comments from Reviewable

authors: dsmilkov nsthorat

repo: PAIR-code/deeplearnjs


text:
PFS: keyword filter is kept in the box when I switch taxon

I am in borrelia PFS -> applied keyword filter.
Then I went to bartonella -> PF tab. They previous keyword is still displayed in the box, which
should be cleared when I change context.

I have a fix locally. will deploy soon.

fixed, verified on alpha.


text:
Metagenome binning is ready to go

Ross and Bruce have declared binning ready to go, so please add the link to the production site.

hooray!

authors: hyoo olsonanl


text:
Dmvm 92(feature) 프로젝트 세팅

🎫 92

✨ 새로운 기능 추가

변경 사항에 대한 설명
DB 스키마와 swagger api 문서 추가에 대한 PR 입니다.
PostgreSQL 기반으로 nest js 서버에 엔티티 파일을 추가했습니다.
테스트 방법
DB ddl을 통해 DB를 세팅한 후, 서버를 실행시켜 TypeOrmCoreModule이 성공적으로 돌아가는지 확인해야 합니다.

성공 예시
실패 예시

변경된 환경
.env 파일에 다음과 같은 내용을 채워주세요.
DATABASE_HOST=
DATABASE_PORT=
DATABASE_USERNAME=
DATABASE_PASSWORD=
DATABASE_NAME=

참고 사항
제 로컬 PostgreSQL 환경에서는 TypeOrmCoreModule이 잘 실행되었습니다. AWS RDS에서도 잘 연결 되는지 확인이 필요합니다.
추후 message_type, appointment_status, auth_provider, geometry 타입이 정해지면 타입 추가가 필요합니다.

typeorm에서 관계 설정하는 코드 보실 때 아래 글 참고하면 좋을 것 같습니다!
https://marklee1117.tistory.com/m/45

repo: PBTP/mongle-server


text:
Unsuccessful connection

Hello,
I run the client and the server as instructed, but it seems like the connection finished before the first rate request even takes place. I get the following output:
connect
NO RESPONSE!!
finished connect
Rate (Mbps)	RTT (ms)	Sent		Lost
Getting rate
TypeError: must be real number, not NoneType
ERROR: Output from python get_rate() is not a float
( I added the NO RESPONSE!! and Getting rate prints).
Do you know why this might occur?
Thank you!

Any solution to this?

authors: KatyaTubs anilsh

repo: PCCproject/PCC-Uspace


text:
Memory leak

I have spent the last two days trying to figure out a memory leak I had in my code when using this library. Since the project I was working on has a pretty large code base, it took me a looooong time to find out that the memory leak was actually being caused by this library.
To prove it, I have written a small c++ file with a main function and an auxiliary one. The code is the following:
void readCIF(const std::string &fnCIF, cif::datablock &dataBlock)
{
    cif::file cifFile;
    cifFile.load(fnCIF);
    dataBlock = cifFile.front();
}

int main() {
    std::filesystem::path filePath = "/home/msalinas/Documents/standalone-installations/cifParser/libcifpp/examples/1cbs.cif.gz";
    cif::datablock dataBlock;
    readCIF(filePath, dataBlock);
    return 0;
}

This, returns the following in valgrind:
LEAK SUMMARY:
==207784==    definitely lost: 2,544 bytes in 53 blocks
==207784==    indirectly lost: 61,624 bytes in 1,888 blocks
==207784==      possibly lost: 0 bytes in 0 blocks
==207784==    still reachable: 0 bytes in 0 blocks
==207784==         suppressed: 0 bytes in 0 blocks
==207784==
==207784== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

If I remove the dataBlock = cifFile.front();, the leak is gone.
If I create a new empty datablock object and assign it like that:
void readCIF(const std::string &fnCIF, cif::datablock &dataBlock)
{
    cif::file cifFile;
    cifFile.load(fnCIF);
    cif::datablock db;
    dataBlock = db;
}

the leak is also gone (but then I'm not reading anything from the file, so that is pointless).
If I write the .front() return into db but not assign it back to dataBlock, also no leak (but then I'm losing the contents of the file as the readCIF() function exits):
void readCIF(const std::string &fnCIF, cif::datablock &dataBlock)
{
    cif::file cifFile;
    cifFile.load(fnCIF);
    cif::datablock &db = cifFile.front();
    //dataBlock = db;
}

But if I uncomment the last line an store the file contents into dataBlock, then I'm losing memory.
The leak only shows up when the contents of the cif file are stored inside a pointer received by argument, that's why I didn't do it all in the main() function and used another one instead.
My guess is that there has to be a problem with memory management in the cif::datablock class. I'm not fluent enough in c++ to try fixing it myself, but at least I was able to identify this issue so it could (hopefully) get fixed @mhekkel :)

Found it, thanks for reporting.
Fix is in trunk.

repo: PDB-REDO/libcifpp


text:
No de-duping of copies and near-copies

In a private discussion on Discord, someone pointed out that there’s no de-duping of decks. Each copy of a deck (whether on the same source site or not) will count towards a commander’s popularity. This overweights format staples, explosive new builds, and possibly decks built by popular content creators

Near-dupes are especially interesting/irksome. If I swap a couple of mana rocks, is it a different deck? Knock out a basic for another rock? What if I swap a single basic for a snow-covered basic?

This is probably a solved problem in the search world. At worst, I’m guessing that we can treat each deck as a document, each card as a token, and compute similarity with traditional techniques.

repo: PDHdata/SmallFormats


text:
Negate Perms

So Stormbow fixed my Permissions.yml file and everything works.
However, I'm wondering, is the proper way to negate a permission this;
- -maxbans.immune
or this;
- - maxbans.immune
Basically, Is it with a space after the second - or not.
Thanks,
Sunboyz
(PS, Stormbow yes I did put the negations in front of the global wildcards this time :p)

Super Stormbow to the rescue!  :D
- -maxbans.immune is correct.

Thanks!

repo: PEXPlugins/PermissionsEx


text:
PostgreSQL Unable to connect to SQL database

========== UNABLE TO LOAD PERMISSIONS BACKEND =========
Your configuration must be fixed before PEX will enable
Details: Unable to connect to SQL database
=======================================================
ru.tehkode.permissions.exceptions.PermissionBackendException: Unable to connect to SQL database
        at ru.tehkode.permissions.backends.sql.SQLBackend.<init>(SQLBackend.java:118) ~[PermissionsEx-1.23.4.jar:?]
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_211]
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) ~[?:1.8.0_211]
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ~[?:1.8.0_211]
        at java.lang.reflect.Constructor.newInstance(Unknown Source) ~[?:1.8.0_211]
        at ru.tehkode.permissions.backends.PermissionBackend.getBackend(PermissionBackend.java:392) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.backends.PermissionBackend.getBackend(PermissionBackend.java:367) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.PermissionManager.createBackend(PermissionManager.java:624) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.PermissionManager.setBackend(PermissionManager.java:606) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.PermissionManager.initBackend(PermissionManager.java:693) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.PermissionManager.<init>(PermissionManager.java:67) ~[PermissionsEx-1.23.4.jar:?]
        at ru.tehkode.permissions.bukkit.PermissionsEx.onEnable(PermissionsEx.java:175) [PermissionsEx-1.23.4.jar:?]
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:263) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:352) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:417) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at org.bukkit.craftbukkit.v1_15_R1.CraftServer.enablePlugin(CraftServer.java:462) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at org.bukkit.craftbukkit.v1_15_R1.CraftServer.enablePlugins(CraftServer.java:376) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at net.minecraft.server.v1_15_R1.MinecraftServer.a(MinecraftServer.java:456) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at net.minecraft.server.v1_15_R1.DedicatedServer.init(DedicatedServer.java:266) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at net.minecraft.server.v1_15_R1.MinecraftServer.run(MinecraftServer.java:783) [core.jar:git-Spigot-2ee05fe-d31f05f]
        at java.lang.Thread.run(Unknown Source) [?:1.8.0_211]
Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver
        at java.net.URLClassLoader.findClass(Unknown Source) ~[?:1.8.0_211]
        at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_211]
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) ~[?:1.8.0_211]
        at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_211]
        at ru.tehkode.libs.org.apache.commons.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1420) ~[?:?]
        at ru.tehkode.libs.org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1371) ~[?:?]
        at ru.tehkode.libs.org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[?:?]
        at ru.tehkode.permissions.backends.sql.SQLBackend.getSQL(SQLBackend.java:245) ~[?:?]
        at ru.tehkode.permissions.backends.sql.SQLBackend.<init>(SQLBackend.java:112) ~[?:?]
        ... 20 more

multiserver:
  use-netevents: true
permissions:
  debug: false
  allowOps: false
  user-add-groups-last: false
  log-players: false
  createUserRecords: false
  backend: sql
  informplayers:
    changes: false
  basedir: plugins/PermissionsEx
  backends:
    file:
      type: file
      file: permissions.yml
    sql:
      type: sql
      uri: postgresql://localhost/postgresql?user=postgres&password=*************
      file: permissions.yml
updater: true
alwaysUpdate: false

I'm using postgres database. I have tried 127.0.0.1, 0.0.0.0 instead localhost, use username, password fields, but it still dont work.

bump

PEX 1.x isn't supported here.
Your server environment doesn't include the PostgreSQL JDBC driver, so you can't connect to your database without that present.
I'm not sure if PEX 2.0 supports PostgreSQL yet - it seems like currently only MariaDB/MySQL and H2 are supported SQL databases.

as md said :) also please don't spam everywhere when you don't get answered in 30 seconds.


text:
Document spawn outdoors attribute

https://github.com/search?q=repo%3APGMDev%2FPGM outdoors&type=code
This attribute will make a player spawn at the highest point of a spawn region. For example, this could be used to stop players from getting stuck in a hollowed out map with a large, generalized spawn.

Not the highest point of a region, the highest point of the world (ie: the highest block in the world at that x,z).
In other words: it won't allow spawning in a position unless such position is above the highest block in the world in that x,z position.

repo: PGMDev/Website


text:
Modularization of sidebar items

Group sidebar items within methods inside its own file;
Build sidebar object with these methods;
Custom sidebar for Scenes (as a generic sidebar including scenes subfolder would break site layout);
Add "previous/return/back to *" button to sidebar when inside folders with too many items.

I'm working on this feature

Most parts were accomplish with this pr
Custom sidebar for Scenes (as a generic sidebar including scenes subfolder would break site layout);
It is currently under development, nothing much to say as there are no content here yet
Add "previous/return/back to *" button to sidebar when inside folders with too many items.
It proved unnecessary


text:
Fix PHP Notice in Squiz.PHP.NonExecutableCode

Description
(After applying the changes in #160 locally...)
While looking into https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/152, I ran the following command:
phpcbf -p . --standard=Squiz --ignore="*/build/*,*/vendor/*" --basepath=. --extensions=inc --suffix=.conflictcheck
Instead of a useful report, I got a PHP Fatal error:
EFFFFFFEFEEEEFFEFFEFFEFEEFFEEEFFEFFFFFFFFEFFFFFFFFPHP Fatal error:  Uncaught PHP_CodeSniffer\Exceptions\RuntimeException: Undefined array key "scope_condition" in .../src/Standards/Squiz/Sniffs/PHP/NonExecutableCodeSniff.php on line 116 in .../src/Runner.php:608
Stack trace:
#0 .../src/Standards/Squiz/Sniffs/PHP/NonExecutableCodeSniff.php(116): PHP_CodeSniffer\Runner->handleErrors()
#1 .../src/Files/File.php(518): PHP_CodeSniffer\Standards\Squiz\Sniffs\PHP\NonExecutableCodeSniff->process()
#2 .../src/Files/LocalFile.php(92): PHP_CodeSniffer\Files\File->process()
#3 .../src/Fixer.php(174): PHP_CodeSniffer\Files\LocalFile->process()
#4 .../src/Reports/Cbf.php(52): PHP_CodeSniffer\Fixer->fixFile()
#5 .../src/Reporter.php(285): PHP_CodeSniffer\Reports\Cbf->generateFileReport()
#6 .../src/Runner.php(691): PHP_CodeSniffer\Reporter->cacheFileReport()
#7 .../src/Runner.php(438): PHP_CodeSniffer\Runner->processFile()
#8 .../src/Runner.php(204): PHP_CodeSniffer\Runner->run()
#9 .../bin/phpcbf(18): PHP_CodeSniffer\Runner->runPHPCBF()
#10 {main}
  thrown in .../src/Runner.php on line 608

This pull request fixes this error, allowing the suggested command to produce a report.
I'm not adding any specific tests for this, as the integration test that will eventually be added as part of #152 will cover this case.
Suggested changelog entry

Related issues/external references
Related to https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/152
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

[ ] This change is only breaking for integrators, not for external standards or end-users.

[ ] Documentation improvement

PR checklist

[x] I have checked there is no other PR open for the same change.
[x] I have read the Contribution Guidelines.
[x] I grant the project the right to include and distribute the code under the BSD-3-Clause license (and I have the right to grant these rights).
[ ] I have added tests to cover my changes.
[x] I have verified that the code complies with the projects coding standards.
[ ] [Required for new sniffs] I have added XML documentation for the sniff.

Closing as not the correct fix - see #149 which I'd opened about this already.

Thanks. I did look through the open pull requests, but didn't realise the connection / overlap with #149.

Thanks. I did look through the open pull requests, but didn't realise the connection / overlap with #149.

I've now realised that #149 is an issue, not a pull request. Closing this pull request as a duplicate of an issue makes less sense to me. Can we get this merged in (as it blocks #152) while we wait for a fix for #149 (which seems more broadly scoped than this)?

Merging this would hide the problem, instead fixing it, so that is not a solution, but a problem multiplying.
IMO this issue is not a blocker for #152 when checking individual conflicts. You would only run into it when trying to run the complete check, which is not the ask.
All the same, if you want to do that, you can have this as a commit locally in a WIP branch (like I have as well), but I do not consider it a valid fix as this is a situation which should never be able to happen and adding defensive coding for a situation which shouldn't be able to exist is not the way to go.

Merging this would hide the problem, instead fixing it, so that is not a solution, but a problem multiplying.

I agree that #149 is a valid bug. I agree that this pull request hides one of the symptoms of that bug. I agree that this pull request does not fix (and does not attempt to fix) #149. It seems that we disagree on whether or not this pull request adds value to the project in its current form. I'll close this off now to reduce the noise / respect your decision.

authors: fredden jrfnl


text:
Login with GitHub is not configured to support 2FA

Currently, only traditional GitHub accounts not secured with 2-factor authentication are able to log in with GitHub.

Yep. This is because i´m using the Laravel Socialite Package that don´t support 2FA atm.. :/

authors: cbales fwartner

repo: PHPMap/PHPMap


text:
Is PHPixie Dead?

Is PHPixie Dead?
There are no commits on the repo.
Ready to help in development.

Unfortunately, that's what it looks like. I would also be interested in information.

Its sad. Looks like its has a good code base.

Sad... Would git it a try.

authors: eltonmorais iaminstanceof mveer08 trixal

repo: PHPixie/Project


text:
killed after the model is saved

Hi @qqingzheng,
Thanks for your awesome work!
One issue: The program seems to be unexpectedly stopped/killed after the model is saved. See the below pic for the place where the stop happens. Can you please give some hints on this?

@LinB203 help

This appears to be just a warning or output message and it should not affect the model training process.

authors: ArlenCHEN LinB203 qqingzheng

repo: PKU-YuanGroup/Open-Sora-Plan


text:
Growatt exception: Error: {"result":2}

Hi zusammen,
ich versuche gerade das Plugin zu konfigurieren und habe nun mehrmals den User und das Passwort geprüft und auch über einen freigegebenen Link getestet, bekommen aber immer den Fehler Growatt exception: Error: {"result":2}, was auch immer das im Detail heißt?
Version 3.2.4 in /opt/iobroker/node_modules/iobroker.growatt,
node: v16.17.0,
js-controller: 4.0.23
DEBUG-Log ioBroker.
growatt.0 | 2024-08-05 14:01:17.773 | debug | Leave growattLogout :247ms
-- | -- | -- | --
growatt.0 | 2024-08-05 14:01:17.537 | debug | Leave growattData :1003ms
growatt.0 | 2024-08-05 14:01:17.526 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:17.525 | debug | Enter growattLogout
growatt.0 | 2024-08-05 14:01:17.524 | error | Growatt exception: Error: {"result":2}
growatt.0 | 2024-08-05 14:01:17.389 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:17.300 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:17.168 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:17.039 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:16.902 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:16.902 | debug | Growatt time for login : 368ms
growatt.0 | 2024-08-05 14:01:16.901 | debug | Growatt isConnected() : true
growatt.0 | 2024-08-05 14:01:16.540 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:16.538 | debug | Growatt login with user and password
growatt.0 | 2024-08-05 14:01:16.537 | debug | Growatt isConnected() : false
growatt.0 | 2024-08-05 14:01:16.535 | debug | Growatt new API
growatt.0 | 2024-08-05 14:01:16.534 | debug | Enter lifeSignCallback 600000ms
growatt.0 | 2024-08-05 14:01:16.534 | debug | Enter growattData, Param: sessionHold:true
growatt.0 | 2024-08-05 14:01:16.477 | info | starting. Version 3.2.4 in /opt/iobroker/node_modules/iobroker.growatt, node: v16.17.0, js-controller: 4.0.23

I did enable checkboxes after another and now it works. Seems like the missing 'data logger' when only using a battery like NOAH 2000 makes problems..
Still not able to retrieve valuable power data from the NOAH 2000, like SOC, current production, etc.


text:
"The application to execute does not exist"

When attempting to create a new project in Visual Studio using a PLCnext template, an error message appears similar to the following:
The application to execute does not exist: 'C:\Users\...\AppData\Local\.net\plcncli\...\plcnli.dll'

or
The application to execute does not exist: 'C:\Users\...\AppData\Local\Temp\.net\EngineeringLibraryBuilder\...\EngineeringLibraryBuilder.dll'.

I am aware of the cause (a caching issue with .NET Core 3.x) and the work-around (delete the plcncli or the EngineeringLibraryBuilder directory in the .NET directory).
This issue is a hint for others who experience a similar problem. The issue can be closed when this problem is resolved.
(internal reference: #208771)

The following symptom is also related to this issue.
When trying to create a new project in Visual Studio, an error like the following may appear:

In all cases the solution is to delete the offending directory from the local .NET cache - for example, delete this directory and its contents:
C:\Users\...\AppData\Local\.net\plcncli

Link to the original issue:
https://github.com/dotnet/runtime/issues/3830
With the next version our CLI will switch to .NET 5.x. In the mean time you could set the DOTNET_BUNDLE_EXTRACT_BASE_DIR to a different, non temporary location as a workaround.

Fixed with Version 2021.6

authors: martinboers mluhmann


text:
🛑 MUSA is down

In 3b28bc1, MUSA (https://storemusa.com/) was down:

HTTP code: 403
Response time: 448 ms

Resolved: MUSA is back up in 53758ee after 22 minutes.

repo: POCLANOS/status


text:
🛑 MUSA is down

In d79689f, MUSA (https://storemusa.com/) was down:

HTTP code: 403
Response time: 303 ms

Resolved: MUSA is back up in 1de681e after 20 minutes.


text:
XML Load Error: An XML Loading error occurred

Hi everyone, I'm facing with a problem that I cannot open the Page XML files with "JPageViewer 1.4 (Windows, 64 bit)".  I can only open XML file in the example folder.
Page XML files are the output of OCR-D workflow:
ocrd process    "sbb-binarize -I OCR-D-IMG -O OCR-D-BIN -P model default"    "anybaseocr-crop -I OCR-D-BIN -O OCR-D-CROP"    "tesserocr-segment -I OCR-D-CROP -O OCR-D-SEG -P shrink_polygons true -P padding 4"    "segment-extract-glyphs -I OCR-D-SEG -O OCR-D-GLYPHS -P transparency true"
I'm using WSL1 and Ubuntu 18.04 LTS on Windows 10. Here is my workplace folder, I can't open these XML files.

Can you please post the PAGE-XML or even better the whole OCR-D workspace, so we can debug this?

Firstly I created a workplace with such line:
ocrd-import --nonnum-ids --ignore --render 300 /mnt/d/workplace/OCR-D-IMG
Then I run the OCR-D workflow above and get XML files for the 4 images. And here is one PAGE-XML file from folder "OCR-D-CROP"
`
-<pc:PcGts pcGtsId="OCR-D-CROP_OCR-D-CROP_0001" xsi:schemaLocation="http://schema.primaresearch.org/PAGE/gts/pagecontent/2019-07-15 http://schema.primaresearch.org/PAGE/gts/pagecontent/2019-07-15/pagecontent.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:pc="http://schema.primaresearch.org/PAGE/gts/pagecontent/2019-07-15">
-pc:Metadata
pc:CreatorOCR-D/core 2.23.3</pc:Creator>
pc:Created2021-05-17T15:27:56.431326</pc:Created>
pc:LastChange2021-05-17T15:27:56.431326</pc:LastChange>
-<pc:MetadataItem value="ocrd-sbb-binarize" name="preprocessing/optimization/binarization" type="processingStep">
-<pc:Labels externalId="parameters" externalModel="ocrd-tool">
<pc:Label value="default" type="model"/>
<pc:Label value="page" type="operation_level"/>
</pc:Labels>
-<pc:Labels externalId="version" externalModel="ocrd-tool">
<pc:Label value="0.0.7" type="ocrd-sbb-binarize"/>
<pc:Label value="2.23.3" type="ocrd/core"/>
</pc:Labels>
</pc:MetadataItem>
-<pc:MetadataItem value="ocrd-anybaseocr-crop" name="preprocessing/optimization/cropping" type="processingStep">
-<pc:Labels externalId="parameters" externalModel="ocrd-tool">
<pc:Label value="0.04" type="colSeparator"/>
<pc:Label value="0.3" type="maxRularArea"/>
<pc:Label value="0.05" type="minArea"/>
<pc:Label value="0.01" type="minRularArea"/>
<pc:Label value="0.75" type="positionBelow"/>
<pc:Label value="0.4" type="positionLeft"/>
<pc:Label value="0.6" type="positionRight"/>
<pc:Label value="10.0" type="rularRatioMax"/>
<pc:Label value="3.0" type="rularRatioMin"/>
<pc:Label value="0.95" type="rularWidth"/>
<pc:Label value="10" type="padding"/>
</pc:Labels>
-<pc:Labels externalId="version" externalModel="ocrd-tool">
<pc:Label value="1.3.0" type="ocrd-anybaseocr-crop"/>
<pc:Label value="2.23.3" type="ocrd/core"/>
</pc:Labels>
</pc:MetadataItem>
</pc:Metadata>
-<pc:Page imageHeight="3263" imageWidth="1995" imageFilename="OCR-D-IMG_0001.jpg">
<pc:AlternativeImage comments=",binarized" filename="OCR-D-BIN/OCR-D-BIN_OCR-D-BIN_0001.IMG-BIN.png"/>
<pc:AlternativeImage comments=",binarized,cropped" filename="OCR-D-CROP/OCR-D-CROP_OCR-D-CROP_0001-IMG.png"/>
-pc:Border
<pc:Coords points="424,564 1376,564 1376,2955 424,2955"/>
</pc:Border>
</pc:Page>
</pc:PcGts>`

I know where my problem is. After I open the PAGE XML file, I need to open the corresponding image to show the layout. I missed the information in Gitter so I stuck there a little bit. I think it would be better if there is a Message box that can give a feedback when successfully loading the XML file and tell the user what to do next.

authors: YHDASHEN kba

repo: PRImA-Research-Lab/prima-page-viewer


text:
Published date

Timeliness matters for podcasts, sometimes having the date for an episode helps.
Display the pubdate for an episode. Like many things, this can be a general date for theplayer, and the builder can prefill with the feed item pubDate

You're suggesting adding a third text field somewhere in the UI? I think if date is important to someone they could stick it one of the two fields we provide. Adding a third field that we know probably is used less frequently than it's not used is going to be hard to optimize a responsive for.

authors: farski kookster


text:
[TECS] Pitch down when engaging alt ctrl for first time

During flight test, when altitude position control has been engaged airplane started to pitch down. The pitch integral reached high negative value at that time. We flew with master 3724947 and we used TECS fix https://github.com/PX4/Firmware/pull/2783

Logging: http://logs.uaventure.com/view/Mz4PbA4F32q9ekaH85xudP

@mswingtra Are you sure you are using the right version? We are logging the pitch and the thrust integrator for TECS but I can't see it in LogMuncher?

It seems that there has changed something in logging upstream, and since we update roughly once a month we did not have that change this time. We will have it by the next flight, so then we can provide more data. For now, either this issue can be kept open and we'll update it ASAP, or we'll reopen it in two-three weeks.

@tumbili we noticed a TECS init issue today, with latest master. We did 2 flights, when POSCTL was engaged the first time we had a huge pitch integrator:

Log: http://logs.uaventure.com/view/oFMJ6Etfx2XsZA6zdLkypc

@AndreasAntener Thanks for reporting! Seems like this issue is still present after all.

This here might be another instance of it:
http://logs.uaventure.com/view/CRzMpDoUvSshcFPY8wNXUA

So we should really have fixed this now. Patch is on master.

authors: AndreasAntener LorenzMeier mswingtra tumbili


text:
Missing PWM_MAIN_REV* params in v1.8.0

I'm not longer able to see the PWM_MAIN_REV* params in the latest v1.8.0 release; neither in QGC v3.3.2 or in the nsh console.  The ailerons of my Wing Wing Z-841 are moving in the opposite of the correct stabilization direction. If these params have been removed in  v1.8.0, then which param should I now use to revert the roll correction in stabilized mode?  Notice that everything works properly in Manual mode so I don't need to change or reset the RC inputs.  The issue is within the latest firmware release.

Which flight controller are you using?

mRo PixRacer R14

With a current Pixhawk 4 it all looks good. I'm closing this for now.

Ok, but I'm not using the Pixhawk 4.  Did you test it with the Pixracer?

@hamishwillee Can we document this in the user guide? We should change the comment string so it discusses the autopilot component MAIN / AUX are each connected to.
The naming is unfortunate:

MAIN: IO
AUX: FMU

Pixracer has only FMU, so it has only AUX. I need to figure out why the *_DIS parameters show up at all - there should be none there.

Fix in code is here:
https://github.com/PX4/Firmware/pull/9917
@hamishwillee Please close the issue once documentation is updated.

authors: IeiuniumLux LorenzMeier


text:
Is there a way to find the external magnetometers supported by PX4 ver 1.8.0?

I'm working on integrating here+ gnss with intel aero drone with px4 ver 1.8.0 running.
I was looking for magnetometers already supported by ver 1.8.0 but haven't been able to find this information. Is the PX4/Firmware/ROMFS/px4fmu_common/init.d/rc.sensors corresponding to the latest PX4 version? This seems to only list one option for external compass for intel aero.
if anyone can point to magnetometers/compass currently supported in ver 1.8.0 that will be great.
Thanks!

Docs say:

PX4 can be used with the following compass parts (magnetometers): Bosch BMM 150 MEMS (via I2C bus), HMC5883 / HMC5983 (I2C or SPI), IST8310 (I2C) and LIS3MDL (I2C or SPI).

This is based on the drivers in Firmware here: https://github.com/PX4/Firmware/tree/master/src/drivers/magnetometer
What is actually supported by each board may change due to space considerations etc.

authors: ambikaverma hamishwillee


text:
[WIP]: PX4 platform layer

Highlevel PX4 layers

PX4 Modules (src/modules)

uORB pub/sub and parameters
controllers, estimators, state machines, mavlink, etc

PX4 Drivers (src/drivers)

modules that access hardware
sensors, outputs, etc
platform agnostic drivers

PX4 Libraries (src/lib)

used by modules and drivers
have access to uORB, parameters, etc
non-px4 libraries also exist that aren't allowed to use anything in the px4 platform (px4_add_library vs add_library)

PX4 platform layer (src/platform)

uORB, parameters, hrt, work queue, task creation, px4 logging
defines everything in the PX4 platform layer, and implements all generic code. Depends on a significant amount of OS specific code (does it make sense for that to live under the top level os/)?

PX4 OS support layer (os/)

nuttx, posix (probably linux separately), qurt
contains non-px4 drivers
should not use anything in the PX4 platform layer (parameters, logging, hrt, etc).

This is now obsolete with @bkueng's refactoring work, but we may want to firmly define some of these layers later.