Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

Race condition on ZAP connect #44

Open
jean-airoldie opened this issue May 28, 2019 · 3 comments
Open

Race condition on ZAP connect #44

jean-airoldie opened this issue May 28, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@jean-airoldie
Copy link
Owner

jean-airoldie commented May 28, 2019

zeromq/libzmq#3523

@jean-airoldie jean-airoldie added the bug Something isn't working label May 28, 2019
@jean-airoldie
Copy link
Owner Author

jean-airoldie commented May 28, 2019

We should block until the handler is ready by sending and empty message to its client.

@jean-airoldie
Copy link
Owner Author

See zeromq/libzmq#3524. This causes the CI to randomly fail.

@jean-airoldie jean-airoldie changed the title CI auth::client::test::test_plain_denied blocks forever Race condition on ZAP connect May 28, 2019
@jean-airoldie jean-airoldie added the critical A critical issue label May 28, 2019
@jean-airoldie jean-airoldie pinned this issue May 28, 2019
@jean-airoldie jean-airoldie unpinned this issue May 29, 2019
@jean-airoldie jean-airoldie pinned this issue May 29, 2019
@jean-airoldie jean-airoldie removed the critical A critical issue label Jun 14, 2019
@jean-airoldie
Copy link
Owner Author

Basically this makes the inproc transport not 100% reliable when tons of sockets are trying to authenticate at the same time. When this error occur, the authentication attempt fails so the socket stays in mute state, meaning the next recv / send call will fail with WouldBlock.

This is not a critical bug, but I it can bite you. However, I haven't encountered a used case where this could occur, other than in the unit tests for this library.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant