zacwbond commented on issue #781: Make connection update process timeout
@rymanluk Your a) makes sense to me. If I get a timeout, I'd tend to assume
that the event that timed out is never going to happen, so it would be odd to
send a timeout event if the procedure is eventually going to succeed.
Another problem I've noticed is that I frequently see a call to my reset_cb
with error code 19 when the gap connection parameter update procedure is
initiated. I think it must be associated with the function
`ble_hs_hci_wait_for_ack()`. That makes it sound like an HCI problem and not a
Nimble problem, but it only ever happens with the parameter update procedure,
and only intermittently.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
Apache Git Services