Noticed this in flaky tests and just when playing around with different connections using main.rs, simply awaiting getting a ping / reply over heartbeat channel doesn't guarantee we'll see the expected messages coming over iopub, namely kernel status messages.
Waiting about 50ms after receiving a heartbeat seems to be a fine workaround for now, but would prefer a more elegant solution.
Noticed this in flaky tests and just when playing around with different connections using
main.rs, simply awaiting getting a ping / reply over heartbeat channel doesn't guarantee we'll see the expected messages coming over iopub, namely kernel status messages.Waiting about 50ms after receiving a heartbeat seems to be a fine workaround for now, but would prefer a more elegant solution.