# Interesting even with LINK nodes
**URL:** https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318
**Category:** General
**Created:** [17 June 2019 10:46 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318 "2019-06-17T10:46:17Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 10:46 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/1 "2019-06-17T10:46:17Z")
I was messing around and using some `LINK` nodes.
I noticed a _problem_ in **how** you can connect them.
Seems you aren't limited to connecting the _virtual out_ to the _virtual in_.
Seems you can connect the _virtual out_ to the _REAL IN_.
See attached.
Oh, and the two bottom `link` nodes are connected, horizontally only.
**Be warned!**
It really messes up the flow.
Pressing either A or B, there is the initial display in the respective A or B `debug` node.
But then it _screams_ which ever button you pressed down the debug list on the right until you get this:
`"RangeError: Maximum call stack size exceeded"`
If you press A or B
See next picture.
Anyway, that aside there is also a _problem_ with how NR deals with the link.
When I select it and delete it, the `DEPLOY` button doesn't activate.
See next two pictures.
Just mentioning.
Is this a bug?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [17 June 2019 11:14 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/2 "2019-06-17T11:14:56Z")
Looks like a fun bug 🙂
You might want to say what version of Node-RED though.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 11:17 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/3 "2019-06-17T11:17:16Z")
(Sorry, I am typing it so often these days I forget where/when I typed it.)
NR: 0.20.3
Dashboard: 2.15.4
```auto
me@me-desktop:~/.node-red$ node -v
v8.16.0
me@me-desktop:~/.node-red$
```
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [17 June 2019 11:18 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/4 "2019-06-17T11:18:07Z")
Have you tested it with the latest version to see if it has already been fixed?
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 11:24 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/5 "2019-06-17T11:24:46Z")
Um,
I don't know how to reply to that.
To the best of my knowledge it is the latest.
If it isn't, well.... Sorry.
I would love to be able to recall all the update commands for all the programs, but I can't.
Could you help me with how to update it if it isn't?
(Other than a link)
And....
For anyone who is running the same version as I am and have the problem, they know it isn't them going mad.
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [17 June 2019 11:37 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/6 "2019-06-17T11:37:01Z")
The current version number can be found here: [https://www.npmjs.com/package/node-red](https://www.npmjs.com/package/node-red)
Rather than repeat the upgrade instructions that are contained in the docs, you can read them there
I'm sure you've upgraded node-red before.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 11:39 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/7 "2019-06-17T11:39:31Z")
Well, I dug around and found this:
`bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)`
But that starts asking me about RasPi stuff..... Granted it kind of has raspbian-deb-packages in the name.
I am updating one of my RPIs just now.
But this is going to take a while on a RPZ.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 11:45 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/8 "2019-06-17T11:45:49Z")
Version now 0.20.5
(On the RPZ(W) not the Ubuntu one)
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [17 June 2019 11:52 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/9 "2019-06-17T11:52:58Z")
Hmm, makes me think that it would be useful to have something - a script maybe - that outputs the installed and latest versions of Node.js, npm, node-red and packages listed in `~/.node-red/package.json` (or more accurately `/package.json`).
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 11:56 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/10 "2019-06-17T11:56:41Z")
Something I "noticed"....
When updating the RPZ(W) NR was 0.20.3
node -v was v8.16.0
After the update it is:
```auto
pi@TelePi:~/.node-red $ node -v
v8.12.0
pi@TelePi:~/.node-red $
```
That is backwards.
Not really game to update the Ubuntu one just yet.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 12:25 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/11 "2019-06-17T12:25:31Z")
Right: Update with `Link` nodes.
See pictures for version.
Interesting thing I noticed too:
In the previous version when I connected the top `link` output to the bottom `link` input, it did it only that way.
Now, with the latest version it _automagically_ does it both ways.
See pictures.
And:
It still crashes and stack overflow error.
The problem remains as far as I can see.
 
And P.S.
When I delete the link between the `link` nodes, the `DEPLOY` button isn't activated (still).
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 June 2019 12:32 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/12 "2019-06-17T12:32:31Z")
This was fixed in 0.20.4 - or are you saying otherwise ?
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 12:33 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/13 "2019-06-17T12:33:10Z")
DCJ,
I can only say what I see.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 June 2019 12:37 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/14 "2019-06-17T12:37:17Z")
> [@Trying\_to\_learn](#):
>
> But that starts asking me about RasPi stuff.
The pi upgrade script should work ok on Ubuntu, it is how I do it.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 June 2019 12:38 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/15 "2019-06-17T12:38:34Z")
Odd - thought we handleded that properly, but I can see in the latest code it is indeed broken. Thanks for reporting.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 12:40 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/16 "2019-06-17T12:40:13Z")
That is on Ubuntu.
I just went through the motions on a RPI.
Same.
I guess you don't want/need the piccies?
If you do, let me know.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 June 2019 12:41 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/17 "2019-06-17T12:41:22Z")
> [@Trying\_to\_learn](#):
>
> I can only say what I see.
Did you remember to force a full browser refresh (usually Ctrl+F5).
What version of NR have you got now? Look in NR startup log.
What does
`apt-cache policy nodejs`
say?
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 June 2019 12:42 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/18 "2019-06-17T12:42:49Z")
@colin - no need - we can see the issue
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 12:42 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/19 "2019-06-17T12:42:54Z")
Thanks Colin.
I have since found a later command which I had documented.
(Yeah, my filing system needs an overhaul)
I now use:
`sudo npm install -g --unsafe-perm node-red`
Though I am .... a bit weary of it as I have been through the motions of `sudo....` before.
And it kind of doesn't say if it needs to be run from the _home_ or _node-red_ directory.
I have been caught out many times on that and was told it has to be the .node-red directory.
(shrug)
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 June 2019 12:44 UTC](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318/20 "2019-06-17T12:44:07Z")
> [@Colin](#):
>
> Did you remember to force a full browser refresh (usually Ctrl+F5).
> What version of NR have you got now? Look in NR startup log.
You see the pictures with the new version in the red circle/elipse. 0.20.5
[Next page](https://discourse.nodered.org/t/interesting-even-with-link-nodes/12318.md?page=2)