multipleResolves log message

[air1one]

We get a log message right after forging that looks like this :

0|core  |  ℹ  multipleResolves (a promise was resolved multiple times) 
0|core  | Initially resolved with: [
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined, undefined, undefined,
0|core  |   undefined, undefined
0|core  | ]
0|core  | Then resolved again with: undefined

We need to investigate and fix the issue.

[sebastijankuzner]

The message is caused by Promise.race in:

core/packages/core-p2p/src/network-monitor.ts

Lines 158 to 182 in 56b4671

	// we use Promise.race to cut loose in case some communicator.ping() does not resolve within the delay
	// in that case we want to keep on with our program execution while ping promises can finish in the background
	await Promise.race([
	Promise.all(
	peers.map(async peer => {
	try {
	await this.communicator.ping(peer, pingDelay, forcePing);
	} catch (error) {
	unresponsivePeers++;
	if (peerErrors[error]) {
	peerErrors[error].push(peer);
	} else {
	peerErrors[error] = [peer];
	}
	this.emitter.emit("internal.p2p.disconnectPeer", { peer });
	this.emitter.emit(ApplicationEvents.PeerRemoved, peer);
	return undefined;
	}
	}),
	),
	delay(pingDelay),
	]);

Nothing unusual is happening, because race method is causing "multipleResolves" events as described in nodejs docs. We are also logging all process errors with log-process-errors package.