-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If tick is called in futureTickQueue we got exception #60
Comments
I'm not sure I follow what you're doing, can you provide a gist to reproduce this? In case you're calling |
@clue Please check this library: Here tick() is called if on read there is no data. If I understand correctly, this is for loop not to block. I use futureTick to queue read/write pipeline, eg:
Is this a correct way to implement PSR7->PSR7 pipeline? |
Another example: What if we make a call inside a loop? |
Let's ping @WyriHaximus and let's see what he has to add 👍 |
@nick4fake it's a horrible hack that I would not recomend 😞 , heck I strongly discourage of doing it when there are alternatives. It 'works' but only in most circumstances. That one in particular was made to provide a fully working |
@WyriHaximus thanks for giving some insight! What do you suggest we should do here? Is this something worth fixing or should we look into avoiding this altogether (is this even reasonable?)? |
I believe this has been superseded now that #72 is in and the I'm closing this for now, please feel free to come back with more details if this problem persists and we can reopen this 👍 |
Hi,
On our project we call futureTick() in case in stream handler we need to wait for new data to populate. It has internal call to tick() that eventually clears current futureTick queue. In FutureTickQueue in tick() we simply call dequeue() exact amount of times equal to queue length at the tick() beginning. The problem is that we don't check if queue is already empty.
The text was updated successfully, but these errors were encountered: