"nocanc mqtt" broken pipe

[mjbmikeb2]

2021/02/12 21:01:22 WARNING Failed to send 23 byte message for NoCAN channel 'everything': Failed to write 50 bytes for value of encoded event 9, write tcp 127.0.0.1:41380->127.0.0.1:4242: write: broken pipe

The message repeats many times.

Possibly related to #5
Multiple topics are matched to a single channel.

The canzero is sending about 20 messages per second and receiving 1 per second from a Windows box.

I can trigger it by sending the following message 2 times in a row from the Rasp Pi.
mosquitto_pub -t 'node20/c_enable_light' -m "node20/c_enable_light=1" -h 127.0.0.1

(The payload looks strange because it contains a copy of the topic.)

[mjbmikeb2]

I tried using a dedicated channel instead of a shared channel but inbound message handling seems to be very unreliable.
Using two sources of MQTT messages at the same time makes it fail faster. nocanc just goes into a state where it prints messages about a broken pipe.

[omzlo]

This is not really a bug. When nocanc finishes a job (for example uploading a firmware) it closes connection with nocand. But nocand doesn't know that yet and may try to send a message to the client, causing a broken pipe error.