# 🎉 Node-RED 1.0.0-beta.3 released

**URL:** <https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645>\
**Category:** News\
**Created:** [22 August 2019 12:13 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645 "2019-08-22T12:13:57Z")\
**Posts on this page:** 20\
**Page:** 7

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [14 September 2019 11:07 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/122 "2019-09-14T11:07:46Z")

</div>

My initial concern & worries, being a bit hesitant to upgrade, that something eventually could break was justified, I mean it happened to me. And it happened to you. Not that it was difficult to fix afterwards, not that I did not want to upgrade, I will for sure, also in the future.  
What I maybe was missing was some kind of warnings issued together with the release pointing me in this direction to avoid the things to break. Remember I asked for a compatibility tool. Would it really be impossible to scan a flow file for such things?

Well, anyway, my upgraded system is running perfect, no other issues whatsoever

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 September 2019 11:13 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/123 "2019-09-14T11:13:00Z")

</div>

> [@krambriw](#):
>
> Remember I asked for a compatibility tool. Would it really be impossible to scan a flow file for such things?

Well, we look forward to your example compatibility check tool 😺

I'm sure that if any of us can think of a way to do some checks we will come forward and make some suggestions. After all, a lot of people will be in the same situation. But I think we can see from the conversations in this thread, that actually this is complex enough to talk about let alone programme tests for.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [14 September 2019 11:30 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/124 "2019-09-14T11:30:56Z")

</div>

> [@scargill](#):
>
> is it safe to assume that another beta (or 1.0 official) will emerge real soon

We'll do another beta on Monday to get this fix out there.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [14 September 2019 12:01 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/125 "2019-09-14T12:01:00Z")

</div>

> [@TotallyInformation](#):
>
> Well, we look forward to your example compatibility check tool

I'm just the annoying customer putting requirements together 😉

---

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [14 September 2019 12:22 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/126 "2019-09-14T12:22:41Z")

</div>

> [@knolleary](#):
>
> a Function node that creates its own network socket connection and passes that socket down the flow for another Function node to do something with. The socket object cannot be cloned. As you imagine, this is very much an edge case scenario (in my opinion).

Ooh, I’ve similar code like this in a subflow, though not directly a socket connection it might still go wrong. Thanks for the quick reminder, it’s on my test machine. Good reason to have that go to 1.0b3 for seeing how it handles that subflow now.  
Third party library (through global context) that creates objects including circular references, with that object being passed down to a second function node...

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [14 September 2019 12:52 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/127 "2019-09-14T12:52:06Z")

</div>

Luckily we don’t think of you as customers 🙂  
More as opinionated friends down the pub

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [14 September 2019 13:03 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/128 "2019-09-14T13:03:57Z")

</div>

Wonderful

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [14 September 2019 13:05 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/129 "2019-09-14T13:05:48Z")

</div>

Yes of course, I feel the same, I was just joking a bit 😉  
Is unfortunately a bit far to a common pub where we all could meet, otherwise, a nice cold pint would be perfect right now

My best regards to all friends

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [14 September 2019 13:20 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/130 "2019-09-14T13:20:15Z")

</div>

NR has been a game-changer for me. I might even fully adopt the dashboard at some point - I must remember how to make good buttons though :-)) At one point I had haptic feedback and really good visuals then forgot all about it...

Thanks to Nick, Dave and all for the feedback on this - REALLY appreciated. As for the upgrade on Monday - well, we really could not ask for more. I'm at a pre-planned beach trip until Wednesday (last tan boost before going back to freezing blighty for the winter, though here in Southern Spain we just had the most horrendous floods) and I'll scan discussions immmediately on my return and presumably upgrade.

Sadly in our local pubs I'm the only one who can program AT ALL unless someone is sitting there very quietly and laughing.

.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 September 2019 13:22 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/131 "2019-09-14T13:22:47Z")

</div>

> [@scargill](#):
>
> Sadly in our local pubs I'm the only one who can program AT ALL unless someone is sitting there very quietly and laughing.

Not sure that you are getting much sympathy given that you are sat in sunny Spain all summer 😄

Speaking of pubs though. If anyone finds themselves in Sheffield, give me a shout, I'd be happy to share a pint or 2.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [14 September 2019 13:31 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/132 "2019-09-14T13:31:03Z")

</div>

...and I'm in Stockholm, Sweden if your path is crossing here. We do have nice beer here as well 😉

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 September 2019 16:53 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/133 "2019-09-14T16:53:48Z")

</div>

> [@krambriw](#):
>
> Stockholm, Sweden if your path is crossing here. We do have nice beer here as well

Indeed you do, I was there a couple of years ago.

I was also due to speak there - unfortunately, some nasty person released Wannacry into the NHS and I had to cancel to help take care of that.

However, it is a tad more expensive to drink there than it is in Sheffield! 😄

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [15 September 2019 10:46 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/134 "2019-09-15T10:46:16Z")

</div>

I can't help it but the following code made me unsure. Will the msg get cloned each time node.send is called?

```auto
var i = 0, howManyTimes = 5;

function f() {
    node.send(msg);
    i++;
    if( i < howManyTimes ){
        setTimeout( f, 3000 );
    }
}

f();

```

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [15 September 2019 10:53 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/135 "2019-09-15T10:53:09Z")

</div>

I'm fairly certain pre v1 the answer is no (send by ref)  
Post v1 yes - clones will be sent (as you did not specify false for the 2nd parameter)

Also, I am guessing you are meaning this code to be ran in a function block.

As I read it, the node.send() in a custom node remains unchanged and cloning is the authors responsibility.

It does mean we will have different function signature for function nodes and custom nodes - something we'll just have to get used to.

Edit... Please correct me if I am wrong.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [15 September 2019 11:16 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/136 "2019-09-15T11:16:01Z")

</div>

> [@Steve-Mcl](#):
>
> It does mean we will have different function signature for function nodes and custom nodes - something we'll just have to get used to.

I did consider this.

Custom nodes must be written to handle messages properly because they have no idea how a user may wire them in. It cannot make any assumptions about how it will be used.

Whereas a Function node is written by the user in the context of the flow it is being used.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [15 September 2019 11:17 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/137 "2019-09-15T11:17:55Z")

</div>

Once we ship the clone fix next week, then every message passed to node.send will get cloned as part of the call to node.send.  
So yes, the function you've shared will cause the msg to be cloned every time.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [15 September 2019 11:45 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/138 "2019-09-15T11:45:17Z")

</div>

> [@knolleary](#):
>
> So yes, the function you've shared will cause the msg to be cloned every time

OK, thanks, so it means that the cloned object will not be reused, instead there will be x number of cloned msg's left in memory until garbage collection runs? So just a problem with very large msg objects

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [15 September 2019 12:50 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/139 "2019-09-15T12:50:11Z")

</div>

They won't get garbage collected till whatever nodes you pass then on to have finished with them.

---

<div class="post-metadata">

**Author:** ![johanon](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johanon/32/3335_2.png) [@johanon](https://discourse.nodered.org/u/johanon)\
**Post date:** [15 September 2019 21:27 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/140 "2019-09-15T21:27:46Z")

</div>

Interesting topic to follow. ”Pass by reference” was unexpectedly emotional for a while. Also a bit heavy on the dont break my flows side. In all that I hope the main point of a major release is not blurred. To point out the direction of the future.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [6 June 2020 18:53 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645/141 "2020-06-06T18:53:06Z")

</div>

Closed on 6 June 2020 18:53 UTC



[Previous page](https://discourse.nodered.org/t/node-red-1-0-0-beta-3-released/14645.md?page=6)
