Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Peer can deadlock on task completion #18

Closed
MichaelDrogalis opened this issue Sep 29, 2014 · 2 comments
Closed

Peer can deadlock on task completion #18

MichaelDrogalis opened this issue Sep 29, 2014 · 2 comments

Comments

@MichaelDrogalis
Copy link
Contributor

Reproduced in core.async plugin tests with a high number of virtual peers. Sometimes, closing a peer will block as it tries to flush its pipeline. The pipeline will block on reading from an ingress queue. This queue should always provide the sentinel value. Something is hanging on to the sentinel as a consumer and never committing it back to the queue, hence the hang.

@MichaelDrogalis
Copy link
Contributor Author

Tentative fix on 33ff91e.

@MichaelDrogalis
Copy link
Contributor Author

Fixed in release 0.3.3.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant