Editor stuck at "Adding Flows to workspace"

After upgrade to 1.2, the editor stops at "Adding Flows to workspace". It appears to be the same issue experienced here:



I'm afraid I cannot follow the debugging steps used before. Is there an easier way to find and remove the offending node? If that is the likely problem?

Hi @taisau

How do you run Node-RED?

If you can set the NODE_ENV environment variable to development before running Node-RED, then you'll get the non-minified version of the editor code - so the stack traces will be easier to follow.

Thanks, @knolleary.
Running on a raspberry pi, installed with the script.
It would appear that it is brads-i2c-nodes causing it.
I'll try reinstalling or rebuilding the node.

Starting as a systemd service.
15 Oct 09:40:48 - [info]
Welcome to Node-RED
===================
15 Oct 09:40:48 - [info] Node-RED version: v1.2.0
15 Oct 09:40:48 - [info] Node.js  version: v14.13.1
15 Oct 09:40:48 - [info] Linux 4.19.97-v7l+ arm LE
15 Oct 09:40:48 - [info] Loading palette nodes
15 Oct 09:40:51 - [info] Dashboard version 2.23.4 started at /ui
15 Oct 09:40:51 - [warn] ------------------------------------------------------
15 Oct 09:40:51 - [warn] [node-red-contrib-brads-i2c-nodes/bmp180] Error: The module '/home/pi/.node-red/node_modules/i2c-bus/build/Release/i2c.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 83. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).

I am getting the same problem with a variation in that if I uninstall and reinstall Node-RED.

It works for about six hours and then starts exhibiting the problem.

Starting as a systemd service.
28 Oct 17:00:04 - [info]
Welcome to Node-RED
===================
28 Oct 17:00:04 - [info] Node-RED version: v1.2.2
28 Oct 17:00:04 - [info] Node.js  version: v14.15.0
28 Oct 17:00:04 - [info] Linux 5.4.72-v7l+ arm LE
28 Oct 17:00:04 - [info] Loading palette nodes
28 Oct 17:00:06 - [info] Dashboard version 2.23.4 started at /ui
28 Oct 17:00:07 - [info] Settings file  : /home/pi/.node-red/settings.js
28 Oct 17:00:07 - [info] Context store  : 'default' [module=memory]
28 Oct 17:00:07 - [info] User directory : /home/pi/.node-red
28 Oct 17:00:07 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Oct 17:00:07 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
28 Oct 17:00:07 - [info] Creating new flow file
28 Oct 17:00:07 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
28 Oct 17:00:07 - [info] Server now running at http://127.0.0.1:1880/
28 Oct 17:00:07 - [info] Starting flows
28 Oct 17:00:07 - [info] Started flows

After installing Node-RED I use the pallet manger to also install:

node-red-dashboard
node-red-contrib-ds18b20-sensor
node-red-contrib-unit-converter
node-red-contrib-alexa-remote2
@victronenergy/node-red-contrib-victron