04a3c4bb22
The change in 1.3 where we ensure config nodes are closed last broke this behaviour. Previously, the config node would get closed triggering the close message. With the new 1.3 behaviour, the flow nodes are stopped and as soon as the last flow node deregisters itself, the broker node would disconnect without sending the close message. The fix is to send the close message as part of the deregister flow as that will handle all cases properly
Node-RED
Low-code programming for event-driven applications.
Quick Start
Check out http://nodered.org/docs/getting-started/ for full instructions on getting started.
sudo npm install -g --unsafe-perm node-rednode-red- Open http://localhost:1880
Getting Help
More documentation can be found here.
For further help, or general discussion, please use the Node-RED Forum or slack team.
Developers
If you want to run the latest code from git, here's how to get started:
-
Clone the code:
git clone https://github.com/node-red/node-red.git cd node-red -
Install the node-red dependencies
npm install -
Build the code
npm run build -
Run
npm start
Contributing
Before raising a pull-request, please read our contributing guide.
This project adheres to the Contributor Covenant 1.4. By participating, you are expected to uphold this code. Please report unacceptable behavior to any of the project's core team at team@nodered.org.
Authors
Node-RED is a project of the OpenJS Foundation.
It was created by IBM Emerging Technology.
- Nick O'Leary @knolleary
- Dave Conway-Jones @ceejay
Copyright and license
Copyright OpenJS Foundation and other contributors, https://openjsf.org under the Apache 2.0 license.