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

ListLeftPushAsync doesn't use AsyncTimeout? #2699

Open
lastdan opened this issue Apr 16, 2024 · 4 comments
Open

ListLeftPushAsync doesn't use AsyncTimeout? #2699

lastdan opened this issue Apr 16, 2024 · 4 comments

Comments

@lastdan
Copy link

lastdan commented Apr 16, 2024

Seems like ListLeftPushAsync doesn't use an AsyncTimeout configuration option. I have async timeout set to 1000ms. But sometimes ListLeftPushAsync calls can take more than 20 seconds to finish. Shouldn't they time out earlier?

@NickCraver
Copy link
Collaborator

Do you have an example timeout message? We'd want to se the values here because it may be an external factor like thread pool exhaustion at those values.

@lastdan
Copy link
Author

lastdan commented Apr 17, 2024

no, I have the next scenario) I've set AsyncTimeout to 1 second. I call ListLeftPushAsync, and sometimes this command takes 15+ seconds to execute (it finishes normally, but takes a lot of time). The expected behaviour is to see a timeout exception after a ~1 second of execution, am I right? I've also set SyncTimeout to 1 second, and ListLeftPush, as expected, throws a timeout exception if it runs more than a second.

@NickCraver
Copy link
Collaborator

If you have an example error message, we can help. If you don't, we can't advise further. We explicitly pack so much information into those messages just to be able to answer "why?" that you're asking. Without any specifics at all, it's just guesses.

@lastdan
Copy link
Author

lastdan commented Apr 17, 2024

ehm...what message? My question is why AsyncTimeout setting doesn't affect ListLeftPushAsync? Let's say I call ListLeftPushAsync which I know will take 15+ seconds to execute. By setting AsyncTimeout to 1 second I expect this call to end after a second with a timeout exception, but instead of this it runs for 15+ seconds. Is it by design for this method or is it a bug?

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

2 participants