🎉 Node-RED 2.1.4 released

News
41

Hi ... found a nasty bug ...

difficult to reproduce, but I give it a try.

  • edited the subflow enviroment Variables like this

image

  • pressed done
  • testing the "action" disappears and the dialog crashed

image
image807×204 8.63 KB

  • not able to edit anything later ...
  • exported the subflow
  • analysed the problem:
                    "opts": {
                        "opts": [
                            {
                                "l": {
                                    "en-US": "Auto"
                                },
                                "v": "auto"
                            },
                            {
                                "l": {
                                    "en-US": "Add"
                                },
                                "v": "add"
                            },
                            {
                                "l": {
                                    "en-US": "Toggle"
                                },
                                "v": "toggle"
                            },
                            {
                                "v": "loop"
                            }
                        ]

... something missing

No a real problem because I could fix it during import and replace the old version
Little note ... I was in the German version of the editor at this time. (promise that I will never do that again :wink:

42

If you've found a reproducable bug in the current release, please raise an issue on github with details. That will ensure it doesn't get overlooked/forgotten about.

43

If I manage to really reproduce this I will.

44

Hi,
I've been running node-red in my home automation dockerized stack for quite a while now and I always upgraded without any issue. This time, upgrading from:

image: nodered/node-red:2.1.3

to

image: nodered/node-red:2.1.4

the container doesn't start anymore throwing this error:

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea2a16c

My stack is defined in a docker-compose.yaml running on a raspberry pi 4. The image I pull should be this one:
https://hub.docker.com/layers/nodered/node-red/2.1.4/images/sha256-379a162f0d4614357e9204c7dfe5d0c214516c5850867dab5c4c7139d4cf00c0?context=explore

does anyone have the same issue?

Thank you,
Gab

45

regarding my previous answer. I just noticed that a fixed tag 2.1.4-1 has been created and should be used.
So for anyone upgrading on docker, please use

image: nodered/node-red:2.1.4-1
46

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.