In a recent thread @TotallyInformation pointed out that a node having two output wires results in Node-red cloning the entire message object. [image] If this is the case, how much extra processing / memory does this consume? Would it be more economical if the debug node had an output and could o…

To be honest, I'd settle for an intermediate where the debug node gets an extra flag. If set, it looses the switch and gains an output. I think this would cover the vast majority of cases since you can already effectively turn off output by not selecting the option in the settings. That would surel…

[image] TotallyInformation: looses the switch and gains an output Mostly I agree as it's visually much better... (hate the button plus link on top... uurgh) - but then it would be always on sending to the log with no way to turn off apart from unwiring. I also like the idea of a new type of …

Regardless of any performance gains, I would always use this "test point" in preference to normal debug nodes just for the sake of visual declutter. Only output while hovered though, seems like a gimmick. But while on the topic of scope creep, how about a built-in link out node in the config, all…

[image] jbudd: , seems like a gimmick but a useful one - I usually run with most of my debug nodes turned off - and only turn them on to see when I need to.

Ok but how do you hover over one node and click to inject at the same time?

[image] dceejay: then it would be always on sending to the log with no way to turn off apart from unwiring. Not the case I think Dave. Simply de-select the option. Requires a re-deploy of course. [image] PS: Actually, it would be perfectly possible to make those flags immediately tell the …

This topic has come up many times. I do agree an improved debug node - of some sort - would be beneficial. Being able to 'attach' a debug probe at any point in the flow. I think it may be some new UX capability, rather than the "normal" node UX. The current model of debug node doesn't avoid the clo…

More clicks but still a major improvement with minimal change to the debug node. Sometimes something is better than nothing. :slight_smile:

Should debug nodes be capable of passing the message forwards?

Core Development

dceejay 1 February 2025 13:48 9

I'm not saying hover should be the only mode of operation - click on and click off also a totally valid configuration. But yeah - most of the work I do does not require many inject nodes - lots of streams of live data instead.

Also click on/off would require saving of state - so would trigger the deploy button (may not need to deploy but) - whereas hover would be stateless and not flag a deploy.

Topic		Replies	Views
A flashing node for the edit screen - requeset Feature Requests	23	491	20 May 2023
Debug node - on/off causing deploy button to get triggered Feature Requests	7	1190	13 August 2018
Debugging ... little tweaks that perhaps can be useful Feature Requests	19	2940	14 January 2020
Function Node switch with a Click tab like Enable on Debug to assist in Troubleshooting Feature Requests	17	456	17 June 2023
Feature request: Attach debug node to the IN connector on a node Feature Requests	25	2303	25 August 2019

Should debug nodes be capable of passing the message forwards?

Related topics