Corrupted Telemetry file uncaught exception

[Hugobox]

Current Behavior

Hi!
When the telemetry file gets corrupted (in my case hard disk was full), Node-Red is prevented from starting with error: [error] Error: Could not read or parse telemetry file '/data/uibuilder/.config/telemetry.json'. Unexpected end of JSON input [uiblib:parseTelemetryFile]
at Object.parseTelemetryFile (/usr/src/node-red/node_modules/node-red-contrib-uibuilder/nodes/libs/uiblib.cjs:769:23)
at async EventEmitter. (/usr/src/node-red/node_modules/node-red-contrib-uibuilder/nodes/uib-runtime-plugin.js:365:9)

Expected Behavior

A corrupted telemetry json file should not prevent Node-Red from starting up, it should replace the corrupted file with a new one.

Steps To Reproduce

Modify the telemetry dile so it doesnt parse as clean json
Try to start Node-Red

Example Node-RED flow

paste your flow here

Environment

• UIBUILDER version: 7.7.3
• Node-RED version: 5.0.2
• Node.js version:
• npm version:
• Platform/OS: windows
• Browser: chrome

How is Node-RED installed? (globally/locally? admin/user?):

How/where is UIBUILDER installed (palette-manager/globally/locally? Which folder?)

Have you changed any of the uibuilder settings in your settings.js file?

[TotallyInformation]

Hi, many thanks for reporting this. I will make sure it is fixed in the next release.

As a note for others who might stumble on this: The telemetry file can always be deleted before starting Node-RED, you will simply get a new telemetry ID on next start. Of course, this is not ideal for me as it bloats the data but the telemetry is only ever meant to be an estimate of usage.