dceejay/nodered.snap

Node RED snappy package

nodered.snap's Issues

Auto-refresh from 590 to 600 caused a failure

My snap auto-refreshed from 590 to 600 at 2:31pm UTC - 01/07/20
It then failed to run with the following error in the log, I have reverted to 590 using snap revert node-red but the auto-refresh will push the 600 regardless :

Jul 01 15:04:14 NODE_RED_SERVER systemd[1]: Started Service for snap application node-red.node-red.
Jul 01 15:04:14 NODE_RED_SERVER node-red.node-red[4052]: NOW STARTING NODE-RED : /snap/node-red/600/bin/node-red -u /<NODE-RED_USER>/snap/node-red/600 on port 1880
Jul 01 15:04:14 NODE_RED_SERVER node-red.node-red[4076]: 1 Jul 15:04:14 - [info]
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: Welcome to Node-RED
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: ===================
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:16 - [info] Node-RED version: v1.1.0
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:16 - [info] Node.js version: v10.21.0
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:16 - [info] Linux 5.4.0-37-generic x64 LE
Jul 01 15:04:16 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:16 - [info] Loading palette nodes
Jul 01 15:04:17 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:17 - [red] Uncaught Exception:
Jul 01 15:04:17 NODE_RED_SERVER node-red.node-red[4122]: 1 Jul 15:04:17 - TypeError: Cannot read property 'forEach' of undefined
Jul 01 15:04:17 NODE_RED_SERVER node-red.node-red[4122]: at /snap/node-red/600/lib/node_modules/@node-red/registry/lib/library.js:31:19
Jul 01 15:04:17 NODE_RED_SERVER node-red.node-red[4122]: at FSReqWrap.args [as oncomplete] (fs.js:140:20)
Jul 01 15:04:17 NODE_RED_SERVER systemd[1]: snap.node-red.node-red.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 15:04:17 NODE_RED_SERVER systemd[1]: snap.node-red.node-red.service: Failed with result 'exit-code'.
Jul 01 15:04:18 NODE_RED_SERVER systemd[1]: snap.node-red.node-red.service: Scheduled restart job, restart counter is at 5.
Jul 01 15:04:18 NODE_RED_SERVER systemd[1]: Stopped Service for snap application node-red.node-red.
Jul 01 15:04:18 NODE_RED_SERVER systemd[1]: snap.node-red.node-red.service: Start request repeated too quickly.
Jul 01 15:04:18 NODE_RED_SERVER systemd[1]: snap.node-red.node-red.service: Failed with result 'exit-code'.
Jul 01 15:04:18 NODE_RED_SERVER systemd[1]: Failed to start Service for snap application node-red.node-red.

/dev/ttyUSB serial devices not supported

hot plug serial devices like USB serial ports are not currently supported by Snapd
This issue just to track that upstream

project not working

Hi,
enabling the project feature in settings.js seems not to work.
The projects features and menue options are not available after a node-red restart.

editorTheme: {
    projects: {
        // To enable the Projects feature, set this value to true
        enabled: true
    }
},

`node-red` command not found

After snap install node-red only two commands are present.

~ node-red.
node-red.desktop-launch  node-red.npm      
~ node-red 
zsh: node-red: command not found...

Unable to follow the tutorial https://nodered.org/docs/getting-started/local#installing-with-snap

core18 support

Is an update to core18 planned?

snap version 1.2.9 broken

When upgraded to 1.2.9 Node Red is giving Connection refused in the browser. As a work around I have reverted to the previous version "snap revert node-red" which restored functionality

Ability to run snap as a non-root user

currently all snaps run as root (but within containers so still isolated so should be ok).
There is a plan to add non-root user support to snapd 1Q 19.
This Issue to track that.

s390s and ppc64el architectures fail to build

The snapcraft builder currently fails to build these two architectures...
Fix is in place but not released so will close this when released

Installing modules from command line fails

Install fails with Unhandled rejection Error: EPERM: operation not permitted, chown '/root/snap/node-red/195/.npm/_cacache/content-v2/sha512/8e/ec'

Add ability to create a snap based on Node-RED snap

In a future version of snapcraft (4Q 18 ?) it will be possible to create snaps based on other snaps... so users could create custom packages based on top of default Node-RED snap.

This Issue to track upstream issue.

The settings.js file do not take effect until flows deployed

When changing settings in the /var/snap/node-red/{current}/settings.js file, running sudo snap disable node-red and then sudo snap enable node-red doesn't apply these settings on the first start.

I refreshed my browser and monitored for a while, expecting only fatal errors to show in debug window but was filling up with warning messages. Once I toggled a debug node and clicked Deploy, then the warning errors no longer showed in the Debug window.

I don't believe this is an issue with the snap specifically but more of an issue with the way snapd references the "current" directory which is the second numbered version in this instance. Deploying the flows shouldn't have changed the reference but did.

Nodes that require git repositories don't work

There are some nodes that require access to the 'git' binary to download the source.

One example when installing @arduino/node-red-contrib-arduino-iot-cloud:

2022-11-21T10:22:02.547Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @arduino/[email protected]
2022-11-21T10:22:04.462Z [err] npm
2022-11-21T10:22:04.466Z [err]  
2022-11-21T10:22:04.466Z [err] WARN
2022-11-21T10:22:04.467Z [err]  
2022-11-21T10:22:04.467Z [err] config
2022-11-21T10:22:04.468Z [err]  production Use `--omit=dev` instead.
2022-11-21T10:22:23.325Z [err] npm
2022-11-21T10:22:23.326Z [err]  
2022-11-21T10:22:23.326Z [err] ERR!
2022-11-21T10:22:23.327Z [err]  
2022-11-21T10:22:23.327Z [err] code
2022-11-21T10:22:23.328Z [err]  ENOENT
2022-11-21T10:22:23.334Z [err] npm
2022-11-21T10:22:23.334Z [err]  
2022-11-21T10:22:23.334Z [err] ERR!
2022-11-21T10:22:23.335Z [err]  
2022-11-21T10:22:23.335Z [err] syscall
2022-11-21T10:22:23.336Z [err]  spawn git
2022-11-21T10:22:23.337Z [err] npm
2022-11-21T10:22:23.337Z [err]  
2022-11-21T10:22:23.338Z [err] ERR!
2022-11-21T10:22:23.338Z [err]  
2022-11-21T10:22:23.340Z [err] path git
2022-11-21T10:22:23.345Z [err] npm
2022-11-21T10:22:23.346Z [err]  
2022-11-21T10:22:23.346Z [err] ERR!
2022-11-21T10:22:23.347Z [err]  
2022-11-21T10:22:23.347Z [err] errno
2022-11-21T10:22:23.348Z [err]  -2
2022-11-21T10:22:23.359Z [err] npm
2022-11-21T10:22:23.360Z [err]  
2022-11-21T10:22:23.360Z [err] ERR!
2022-11-21T10:22:23.361Z [err]  
2022-11-21T10:22:23.365Z [err] enoent
2022-11-21T10:22:23.365Z [err]  An unknown git error occurred
2022-11-21T10:22:23.366Z [err] npm
2022-11-21T10:22:23.366Z [err]  
2022-11-21T10:22:23.367Z [err] ERR!
2022-11-21T10:22:23.367Z [err]  
2022-11-21T10:22:23.368Z [err] enoent
2022-11-21T10:22:23.372Z [err]  This is related to npm not being able to find a file.
2022-11-21T10:22:23.372Z [err] npm ERR! enoent 
2022-11-21T10:22:23.382Z [err] 
2022-11-21T10:22:23.383Z [err] npm
2022-11-21T10:22:23.384Z [err]  
2022-11-21T10:22:23.384Z [err] ERR!
2022-11-21T10:22:23.385Z [err]  A complete log of this run can be found in:
2022-11-21T10:22:23.385Z [err] npm
2022-11-21T10:22:23.386Z [err]  
2022-11-21T10:22:23.386Z [err] ERR!
2022-11-21T10:22:23.387Z [err]      /root/snap/node-red/838/.npm/_logs/2022-11-21T10_22_04_281Z-debug-0.log
2022-11-21T10:22:23.411Z rc=254

It would be interesting either to investigate if it is possible to call 'git' if it is installed in the host system or to include 'git' in the snap.

Config path in README incorrect for version currently in stable channel

The README states that the settings and flow files are stored in /var/snap/node-red/current/ (SNAP_DATA), which appears to be true for the release currently in the edge and candidate channels. Though the snap in the stable channel is older, and has those files stored under /root/snap/node-red/current/ (SNAP_USER_DATA).

I know this was previously discussed in #21, and I assume that the intention is to promote the candidate snap to stable soon, which would make the README correct. But for the time being there's a disconnect between the docs and actual functionality that most people would experience.

snap should store configuration in /var/snap/node-red

For snaps with services it is advised to store data in $SNAP_DATA

Directory for system data of a snap.

This directory is owned and writable by root and is meant to be used by background applications (daemons, services). Unlike SNAP_COMMON this directory is backed up and restored across snap refresh and snap revert operations.