search

project-chip / zap

ZAP stands for ZCL Advanced Platform. It is used to configure clusters, attributes and other entities for Matter and ZigbeePro applications.
Apache License 2.0
139 stars 83 forks source link

UnhandledPromiseRejectionWarning: TypeError: Cannot convert null to a BigInt #1459

Open Jardaliao opened 1 week ago

Jardaliao commented 1 week ago

log

⇝ (node:263808) UnhandledPromiseRejectionWarning: TypeError: Cannot convert null to a BigInt at BigInt () at extractBigIntegerValue (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:176:16) at getIntegerFromAttribute (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:214:11) at getBoundsInteger (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:184:20) at checkAttributeBoundsInteger (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:252:30) at validateSpecificAttribute (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:95:15) at /home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/rest/user-data.js:261:30 (Use electron --trace-warnings ... to show where the warning was created) (node:263808) UnhandledPromiseRejectionWarning: 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:263808) UnhandledPromiseRejectionWarning: TypeError: Cannot convert null to a BigInt at BigInt () at extractBigIntegerValue (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:176:16) at getIntegerFromAttribute (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:214:11) at getBoundsInteger (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:184:20) at checkAttributeBoundsInteger (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:252:30) at validateSpecificAttribute (/home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/validation/validation.js:95:15) at /home/jay/projects/xxx/.zap/zap-v2024.03.14-nightly-src/dist/src-electron/rest/user-data.js:261:30 (node:263808) UnhandledPromiseRejectionWarning: 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

how to reproduce:

dhchandw commented 2 hours ago

EventList and AttributeList are externally managed attributes and should not be visible in the ZAP GUI. If you pull the latest ZAP version you will not see them. These attributes are managed in the application code.