I considered suggesting showing a dot as the junction is now but with a slightly larger circle or horizontal oval revealed on mouse-over.
Click on the dot to drag and move, on the outer circle to start a wire.
But I decided the suggestion would be stomped on, or worse, I'd be invited to write the code!
Awesome new change, but... how can we reset the counter?
Unfortunately, that was not added - please add a feature request thread to Feature Requests
I am a rookie in this forum, but I hope I have done it well:
The instance I changed yesterday to the beta failed early this morning 
FYI this has never happened before so either a big coincidence or something up
That's an uncaught exception coming from inside the contrib-better-sftp node - hard to see how the beta would be responsible.
I think you may be right -just a big coincidence.
I'm suspecting that a Cheerlights flame war was in progress and that my remote server couldn't cope with the traffic maybe???
I was already filtering one of the wassocks out so I'll add the other one to my filter list 
My first new use of the junction node to manually re-direct a wire path - very nice
Its been found and fixed Julian ...
Just experienced a glitch in the matrix
I'd added in a junction node in a link call flow and then noticed I was getting "timeout" error messages in the debug sidebar when it was being called
All looked fine visually, added debugging nodes - found that it wasn't getting out of the 1s delay node but couldn't work out why
Restarted NR - no diff- refreshed browser and the wire was missing from the junction node to the delay node
Re-added it and it is fine again
You wired backwards from 1s timer to the junction.
This is a known issue in beta 1 - fixed in master (beta 2 next week)
I thought - well that's strange since I've been doing this in other flows and not noticed
And then when I've gone back to the other flows - I've noticed none of my unused debug nodes are attached!
To wire from a junction, currently you have to hold CTRL when clicking the junction. Its a bit odd since normally holding ctrl means add a node & you dont have to hold control when wiring a from a regular node output - thats just how it is for now.
I've been playing with some SVG and CSS and think it might be worth asking Nick about the feasibility of a grab handle appearing upon hover OR the junction expands out to reveal its hidden ports (so to speak) as I dont have much experience in the d3 side of things (so would need his help).
something like below perhaps?...
<svg viewBox="-50 -50 380 380" class="svg-3">
<path d=" M27,19 h6 a12,12 0 0 1 12,12 v6 a12,12 0 0 1 -12,12 h-6 a12,12 0 0 1 -12,-12 v-6 a12,12 0 0 1 12,-12 z M27,19 h6 a12,12 0 0 1 12,12 v6 a12,12 0 0 1 -12,12 h-6 a12,12 0 0 1 -12,-12 v-6 a12,12 0 0 1 12,-12 z M27,19 h6 a12,12 0 0 1 12,12 v6 a12,12 0 0 1 -12,12 h-6 a12,12 0 0 1 -12,-12 v-6 a12,12 0 0 1 12,-12 z" style="fill:grey;fill-opacity:1;" />
</svg>
.svg-3:hover path:hover {
d: path(" M9,24 h6 a1,1 0 0 1 1,1 v18 a1,1 0 0 1 -1,1 h-6 a4,4 0 0 1 -4,-4 v-12 a4,4 0 0 1 4,-4 z M45,24 h6 a4,4 0 0 1 4,4 v12 a4,4 0 0 1 -4,4 h-6 a1,1 0 0 1 -1,-1 v-18 a1,1 0 0 1 1,-1 z M20,20 h20 a4,4 0 0 1 4,4 v20 a4,4 0 0 1 -4,4 h-20 a4,4 0 0 1 -4,-4 v-20 a4,4 0 0 1 4,-4 z");
}
body {
display: flex;
flex-wrap: wrap;
justify-content: space-between;
}
svg {
width: 30%;
height: 30%;
background: #eee;
margin-bottom: 5%;
}
svg polyline,
svg line,
svg path {
fill: grey;
stroke: #000;
stroke-linecap: round;
stroke-linejoin: round;
transition: 0.2s;
}
<edit>
I feel it is only fair to fill in a few details here: The SVG/CSS was the easy part (and thats saying something). It may not be sensible/feasible/easily achievable under the d3 hood (so no promises)
</edit>
Crashy Crash- Crash...!
@knolleary,
Upgraded to 3.0.0 beta 1 last night.
I have some test nodes, TCP connected to localhost port 2001 in one flow and another TCP listening on localhost 2001. This works fine and passes data between the flows fine.
until I
do a FULL DEPLOY. Node-RED crashes
9 May 21:56:55 - [info] Stopping flows
9 May 21:56:55 - [info] [tcp in:da552e190d95fb24] stopped listening on port
9 May 21:56:55 - [red] Uncaught Exception:
9 May 21:56:55 - [error] Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
any node deployment still works fine even when I move that node and deploy it.
This was never the case on recent prior versions. The last one was 2.2.2.
Start up info
9 May 21:55:31 - [info]
9 May 21:55:31 - [info] Node-RED version: v3.0.0-beta.1
9 May 21:55:31 - [info] Node.js version: v18.1.0
9 May 21:55:31 - [info] Linux 5.4.0-109-generic x64 LE
9 May 21:55:32 - [info] Loading palette nodes
9 May 21:55:32 - [info] Dashboard version 3.1.6 started at /ui
9 May 21:55:32 - [info] Settings file : /home/myname/.node-red/settings.js
9 May 21:55:32 - [info] Context store : 'default' [module=memory]
9 May 21:55:32 - [info] User directory : /home/myname/.node-red
9 May 21:55:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 May 21:55:32 - [warn] Flows file name not set. Generating name using hostname.
9 May 21:55:32 - [info] Flows file : /home/myname/.node-red/flows_ThinkPad-T420s.json
9 May 21:55:33 - [info] Server now running at http://127.0.0.1:1880/
If this repeatable every time?
Can you share a minimal flow that demonstrates this & I'll fix it for beta 2
@Steve-Mcl ,
Yes it repeats. As a matter of fact when putting this flow together, I made a new flow with new entries and not copies of the nodes I tested. I disabled them. I had to change to "Modified Nodes" for deployment. That deployed, but I had to re-start flows for the connection to work. Once I switched back to "Full Deploy", it crashes, stops all flows and returns the command prompt on the terminal. Here is my exported "flow 4".
[{"id":"d5aee383de79fdc8","type":"tab","label":"Flow 4","disabled":false,"info":"","env":[]},{"id":"96c42434017055f0","type":"tcp in","z":"d5aee383de79fdc8","name":"","server":"server","host":"","port":"2001","datamode":"stream","datatype":"utf8","newline":"","topic":"","trim":false,"base64":false,"tls":"","x":160,"y":220,"wires":[["a439bdc8358ac1d7"]]},{"id":"66f6cfd609c1335c","type":"tcp out","z":"d5aee383de79fdc8","name":"","host":"localhost","port":"2001","beserver":"client","base64":false,"end":false,"tls":"","x":450,"y":140,"wires":[]},{"id":"ed70a85bb0db6d9f","type":"inject","z":"d5aee383de79fdc8","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":160,"y":140,"wires":[["66f6cfd609c1335c"]]},{"id":"a439bdc8358ac1d7","type":"debug","z":"d5aee383de79fdc8","name":"debug 1","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":420,"y":220,"wires":[]}]
I do not know what I'm doing wrong.
New Junction Nodes. I cannot seem to get this to work on my system at all. I'm not sure what I'm doing wrong. Shift key + click-drag and the connections do not highlight at all.
Right-Click and I get a mouse menu.
Could it be Node-related? I have spotted a v18.1.0 in your log output, maybe there have been some underlying changes there.
Have you tried the current v16 LTS release?
Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy
