# Node-RED 0.20.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-0-20-0-beta-4-released/7339>\
**Category:** News\
**Created:** [28 January 2019 16:03 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-4-released/7339 "2019-01-28T16:03:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [29 January 2019 13:19 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-4-released/7339/2 "2019-01-29T13:19:46Z")

</div>

I'm currently testing the beta in a docker container running on a raspberry pi 3.  
The docker image was built using `"node-red": "0.20.0-beta.4",` in the provided `package.json` that comes with the `node-red-docker` github repository.

these are the logs when starting the container:

```auto
29 Jan 12:54:23 - [info] Node-RED version: v0.20.0-beta.4
29 Jan 12:54:23 - [info] Node.js version: v8.1.3
29 Jan 12:54:23 - [info] Linux 4.14.27-v7+ arm LE
29 Jan 12:54:25 - [info] Loading palette nodes
29 Jan 12:54:48 - [info] Dashboard version 2.13.0 started at /ui
29 Jan 12:55:03 - [info] Settings file : /data/settings.js
29 Jan 12:55:03 - [info] Context store : 'default' [module=memory]
29 Jan 12:55:03 - [info] User directory : /data
29 Jan 12:55:03 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
29 Jan 12:55:03 - [info] Flows file : /data/flows.json

```

so far so good, after that I get these errors:

```auto

29 Jan 12:55:09 - [error] [ui_text:98fc9db.54eaf6] RangeError: Maximum call stack size exceeded
    at Flow.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:287:12)
    at Object.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:214:40)
    at Flow.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:301:28)
    at Object.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:214:40)
    at Flow.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:301:28)
    at Object.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:214:40)
    at Flow.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:301:28)
    at Object.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:214:40)
    at Flow.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:301:28)
    at Object.getNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:214:40)

```

So this is the first thing that I've seen that didn't occur with beta-3. Node-red started and everything was fine, the dashboard was served but I didn't test further.

At first I tried to update via the palette manager the relevant node (I thought that was the dasbhoard since all the errors pointed to some ui\_nodes). after succesfully updating the dashboard to `2.13.1` i restarted the container but some nodes disappeared from the mapped `/data` directory. upon further inspection the `/data/package.json` only refers to some of the nodes (which I think are the ones that I installed via the palette manager itself) the other "contrib" nodes were missing from the file system and so, they were unregistered:

```auto
29 Jan 12:59:40 - [info] Dashboard version 2.13.1 started at /ui
29 Jan 12:59:56 - [warn] Missing node modules:
29 Jan 12:59:56 - [warn] - node-red-contrib-amazondash (0.0.1): ButtonPressed
29 Jan 12:59:56 - [warn] - node-red-node-discovery (0.0.18): discovery, announce
29 Jan 12:59:56 - [warn] - node-red-contrib-advanced-ping (1.2.0): adv ping
29 Jan 12:59:56 - [warn] - node-red-contrib-freeboard (0.0.7): freeboard
29 Jan 12:59:56 - [warn] - node-red-contrib-later (0.0.5): later
29 Jan 12:59:56 - [warn] - node-red-contrib-mopidy (2.0.2): mopidy-out, mopidy-in, mopidy-config
29 Jan 12:59:56 - [warn] - node-red-contrib-node-hue (0.9.1): node-hue-out, node-hue-in, node-hue-bridge
29 Jan 12:59:56 - [warn] - node-red-node-mongodb (0.0.13): mongodb, mongodb out, mongodb in
29 Jan 12:59:56 - [warn] - node-red-contrib-mongodb2 (0.5.5): mongodb2, mongodb2 in

```

copied those back from yesterday backup, the instance now is running as expected. but with updated dashboard and those nodes back on the fs, I'm still seeing those `Maximum call stack size exceeded` errors on start.

tl;dr

two problems, maximum call size exceeded, and nodes missing form fs when updating a node via the palette

---

_[View the full topic](https://discourse.nodered.org/t/node-red-0-20-0-beta-4-released/7339)._