Skip to content
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

[BUG] Submitted task never got executed when actor reaching max_concurrency #37

Closed
zhanglei1949 opened this issue Oct 21, 2023 · 1 comment

Comments

@zhanglei1949
Copy link
Contributor

When max_concurrency is set to 1, and two tasks are send to a same actor, the actor will only execute the first submitted taks, while the second one got stuck and will never be executed.

@zhanglei1949
Copy link
Contributor Author

Close since fixed by #39

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

No branches or pull requests

1 participant