Version 11.3.0 of nyc was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency zeromq was updated from 5.1.0 to 5.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

zeromq is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

If I understand it correctly your API allows us only to send String messages.

Is it also possible to whisper raw buffers to other zyre peers?

The devDependency mocha was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When

• I try to monitor 'join' events on a network with a zyre.js node (1) and
• I create another node (2) that joins a group (A) right after I start node (2)
• (node (2) starts after node (1) is started)

then

• node (1) does not emit a 'join' to indicate that node (2) joined group (A).

I think this is a bug because when I ask node (1) information about group (A) some time later, it says node (1) did join the group (even though it did not emit the 'join' event).

I can replicate this using the following code on my macbook:

const Zyre = require('zyre.js')
const testGroup = 'testGroup'

const node1 = Zyre.new({name: 'Node 1'})
const node2 = Zyre.new({name: 'Node 2'})

node1.on('join', (id, name, group)=> {
	console.log(name, 'joined', group)
})

node1.start(() => {
	node1.join(testGroup) // this line is not necessary to reproduce the bug

	node2.start(() => {
		node2.join(testGroup)
	})
})

setTimeout(function () {
	console.log(node1.getGroup(testGroup))
}, 2000)

Hi, From the look at it , reconnecting into a group isn't working properly. DGRAM and resuse UDP socket seems to have unexpected behavior althought the whole pair connect/on connect is working, as well as join/on join.

However, whisper isn't working while responding to a onshout , we need a huge workaround to not loose any message ...
Issue as been encounterd on Windows Server , Linux Centos and Cloud Azure Linux Centos.
I followed the pattern Sender A (Shout) -> Recv B (On Shoot) -> Recv (B) Whisper -> Sender A (OnWhisper )

The dependency debug was updated from 4.1.0 to 4.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

I've noticed the behaviour of iface is, to me, surprising.

From the Zyre reference implementation in C :

//  Set network interface for UDP beacons. If you do not set this, CZMQ will
//  choose an interface for you. On boxes with several interfaces you should
//  specify which one you want to use, or strange things can happen.
//  The interface may by specified by either the interface name e.g. "eth0" or
//  an IP address associalted with the interface e.g. "192.168.0.1"
ZYRE_EXPORT void
    zyre_set_interface (zyre_t *self, const char *value);

Note that we can specify IP address.

However, looking at the algorithm used in zyre.js, it only accepts the interface name.

My desire is, on Windows, to supply 127.0.0.1 to denote the loopback adapter 'pseudo interface'.
I'm willing to make the change & PR but wanted to clarify this.

Additionally, even if I do supply the adapter name, I run into the situation where the code fails to accept it because it is marked as 'internal'

Note the adapter is marked as private.
The code has the logic of declining to use nay with .internal being truthy.
This makes sense to me if the user did not explicitly supply an adapter (select the first public iface). But if they specify an adapter, what does it matter if it's public/private?

I'd appreciate any thoughts!