-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined #46
Comments
Kannst du mal die Github version installieren (Experten Modus, Katze, Link einfügen) Und mir dann schreiben was er dann sagt? |
@ciddi89 mach ich |
@ciddi89
|
Ist das immer um 0 Uhr? Aber sonst läuft der Adapter oder? //Edit: frage konnte ich mir selbst beantworten. Werde versuchen es in den nächsten Tagen zu fixen. |
Ok den Fehler spuckt er nicht mehr aus, das ist erstmal beseitigt. Kannst das gerne noch mal mit der Katzen Version testen. Muss mir das aber noch mal genauer angucken, daher bitte diesen thread nicht schliessen. :) |
ja
mach ich |
@ciddi89 Log blieb heute sauber , keine Fehlermeldung |
Sollte damit oin 2.0.0 behoben sein |
- (ciddi89) Added: [#24](#24) Option to remove 'COMPACT' in log entries - (ciddi89) Added: [#21](#21) Option to remove only 'script.js' in log entries - (ciddi89) Fixed: [#46](#46) Midnight function to change today/yesterday - (ciddi89) Fixed: [#23](#23) When nothing selected in blacklist, adapter didn't work anymore - (ciddi89) Other: Small code and translation improvements
Fixed in 2.1.0 |
seit dem upgrade von v1.1.0 auf v1.2.3 bekommen ich folgende Meldung
`
2023-03-01 00:00:01.003 - error: logparser.0 (2084326) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-03-01 00:00:01.011 - error: logparser.0 (2084326) unhandled promise rejection: Cannot read properties of undefined (reading 'objArrayGetObjByVal')
2023-03-01 00:00:01.032 - error: logparser.0 (2084326) TypeError: Cannot read properties of undefined (reading 'objArrayGetObjByVal')
at updateTodayYesterday (/opt/iobroker/node_modules/iobroker.logparser/main.js:196:26)
at Timeout. (/opt/iobroker/node_modules/iobroker.logparser/main.js:179:4)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
2023-03-01 00:00:01.033 - error: logparser.0 (2084326) Cannot read properties of undefined (reading 'objArrayGetObjByVal')
2023-03-01 00:00:01.336 - info: logparser.0 (2084326) cleaned everything up...
2023-03-01 00:00:01.337 - info: logparser.0 (2084326) terminating
2023-03-01 00:00:02.843 - info: logparser.0 (2084326) terminating with timeout2023-03-01 00:00:01.339 - warn: logparser.0 (2084326) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-03-01 00:00:08.142 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-03-01 00:00:08.143 - error: host.IoBroker Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'objArrayGetObjByVal')
2023-03-01 00:00:43.863 - info: logparser.0 (2683336) starting. Version 1.2.3 in /opt/iobroker/node_modules/iobroker.logparser, node: v18.14.1, js-controller: 4.0.24`2023-03-01 00:00:08.143 - error: host.IoBroker Caught by controller[0]: at updateTodayYesterday (/opt/iobroker/node_modules/iobroker.logparser/main.js:196:26)
2023-03-01 00:00:08.144 - error: host.IoBroker Caught by controller[0]: at Timeout. (/opt/iobroker/node_modules/iobroker.logparser/main.js:179:4)
2023-03-01 00:00:08.144 - error: host.IoBroker Caught by controller[0]: at listOnTimeout (node:internal/timers:569:17)
2023-03-01 00:00:08.144 - error: host.IoBroker Caught by controller[0]: at processTimers (node:internal/timers:512:7)
2023-03-01 00:00:08.145 - error: host.IoBroker instance system.adapter.logparser.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-03-01 00:00:08.146 - info: host.IoBroker Restart adapter system.adapter.logparser.0 because enabled
The text was updated successfully, but these errors were encountered: