Open Tomas-Kraus opened 1 year ago
NO_ACK-1
is lost, but we still receive NO_ACK-2, NO_ACK-3
. I don't know the details, but my first guess is that message with NO_ACK-1
is sent and there is no handler registered yet to process it.
Same problem...
+1 for me just now
Still seeing this fail pretty often on the 4.0.x maintenance release branches.
I saw this test failure several times, restarting the job usually helps.
Last time I saw it in PR #6959 https://github.com/helidon-io/helidon/actions/runs/5277095950/jobs/9544670221?pr=6959
Tested locally on the same branch (from PR) and test passed.