I'm trying to work out if a change between ver 1.5 and 2.0 is deliberate.
The case is a node sending a message that requires signing, but signing failed (e.g. nonce timeout).
In previous versions (1.5) , this would result in the send function returning false.
In the current dev branch, this results in signerSignMsg returning false, but the message itself can be sent and return "st=ok", e.g.:
send: 4-4-97-0 s=4,c=3,t=16,pt=0,l=0,sg=0,st=ok: Nonce requested from 0. Waiting... Message to send could not be signed! sign fail send: 4-4-97-0 s=4,c=2,t=36,pt=0,l=0,sg=0,st=ok:
So the send function returns true, even though the gateway will discard the message (presumably).
I seem to have lots of radio issues, so I want my nodes to repeat status updates until the send is confirmed.
I guess my question is this: should the send function (transportSendWrite) be changed so that if signing fails, the send fails, or should I go about this differently (e.g. using ack's, or testing with mGetSigned)?
p.s. I'm fairly new to the forum, and github, so I'm not sure where the best place to post this is - let me know if it's not appropriate here.