data not going out for send

I assume this is newbie issue.

My node-nanomsg class is receiving messages (Google Flatbufers (FB) ) just fine. When I connect to send, my client sees the connection and the tcp socket is bound. However, the does not seem to be starting.

What observe is that in this section: the this_pollSend is called only once on the first invokation of socket.send() but on subsequent calls it is not being triggered. To me it feels like something is getting stuck in the out-quue

Socket.prototype._startPollSend = function () {
    if (!this._pollSend) {
        this._pollSend = nn.PollSocket(this.binding, true, function (events) {
            if (events) this.flush();
        }.bind(this));
    }
}

Below is how I have structured my class wrapper for NanoMSG:

const nano = require('nanomsg')
const flatbuffers = require('flatbuffers/js/flatbuffers').flatbuffers
const {Telemetry} = require('./Payloads/Telemetry')
const {Topics} = require('./messages/Packet')

class LMB {
    constructor(config) {
        this.sock
        this.config = config
        this.nodeName = config.nodeName
        this.topicList = config.topicList
        this.topics = Topics
        this.topicMap = new Map([
            [this.topics.simActorStateTest, new Telemetry()],
            [this.topics.navActorStateTest, new Telemetry()] ])
    }

    connect() {
        this.sock = nano.socket('bus')
        this.sock.bind(this.config.urlList[0])
        this.sock.connect(this.config.urlList[1])
        this.sock.on('data', this.receive.bind(this))
        this.sock.self = this;
    }

//payload is a FB uint8 byte array, this method is being called in a loop every second. everything looks fine here, 
    send(topic, payload) {
        let size = payload.length + 8
        let packet = new ArrayBuffer(size)
        let buffer = new Uint8Array(packet)
        let view = new DataView(packet)
        view.setUint32(0, topic)
        view.setUint32(4, size)
        buffer.set(payload, 8)
        this.sock.send(buffer)
    }

    receive(packet) {
        let view = new DataView(packet.buffer)
        let topic = view.getUint32(0, true)
        let size = view.getUint32(4, true)
        let jPacket = {"topic": topic, "size": size}
        let payload = packet.slice(8, packet.length-8)
        this.topicMap.get(topic).parse(payload, jPacket)
        console.log(JSON.stringify(jPacket, null, 4))
    }
}

module.exports = { LMB }

The config file (where the connections are described looks like this (but as I said, my client is reporting that the nanoMSG JS sender is connecting fine, it is just the messages are not going over the “wire”

{
  "nodeName": "YSG4206-Orchestrator",
  "urlList": [ "tcp://10.4.30.239:2018", "tcp://10.4.30.239:2019" ],
  "topicList": [ "sim.Actor.State.Test" ]
}

[DrYSG]

Bus is not the issue. I was missing an await. Now I have a different issue. The data I am putting into the header of the packet (before the payload) is with the wrong endian depending on whether it is from the C++ or Javascript side. That is not your issue. It is mine!

    send(topic, payload) {
        let size = payload.length + 8
        let packet = new ArrayBuffer(size)
        let buffer = new Uint8Array(packet)
        let view = new DataView(packet)
        view.setUint32(0, topic)
        view.setUint32(4, size)
        buffer.set(payload, 8)
        this.sock.send(buffer)
    }

    receive(packet) {
        let view = new DataView(packet.buffer)
        let topic = view.getUint32(0, true)
        let size = view.getUint32(4, true)
        let jPacket = {"topic": topic, "size": size}
        let payload = packet.slice(8, packet.length-8)
        this.topicMap.get(topic).parse(payload, jPacket)
        console.log(JSON.stringify(jPacket, null, 4))
    }

[reqshark]

lol sure, if you’re doing C++ strings with std::string then you can relax and don’t worry about it

Bjarne Stroustrup appends the terminating zero for you

🌴