Pedro B. Arruda
Pedro B. Arruda
I think that we could close this because it seems quite old and nobody else has commented on it.
Let's reopen this later, if somebody else sees an issue.
Whoa! This is a tough one. I have been digging into your issue and will have to give it a thought during the weekend, now that Dobby is finally free.
So, as a better workaround than spinning a `try_recv`, you could try a [`recv_timeout`](https://docs.rs/yaque/latest/yaque/queue/struct.Receiver.html#method.recv_timeout) to reduce CPU load substantially. That is still a hack, but it's all I can do...
Question, what OS and what version of yaque are you using? It can be that the reason your app is getting stuck is the code not handling some specific event...
I can't believe it's that simple! Do you have any resources on this funky behavior? EDIT: Sorry! I saw the link in your comment.
So, I will merge and create a new minor version tomorrow, when I have some time to look into this closely.
> I've investigated this a little bit, and I'm _guessing_ that this is likely to be caused by the test harness running so fast, thrashing inotify subscriptions very fast. If...
> Sorry for the delay, it's over at #22 No problem. I myself am having little time during these weeks to code at all.
That looks like a reasonable request. I think that I did not include this at first because of the `RecvGuard` type (I remember some borrow check complaints back then). Let...