Skip to content

Add a way to introspect how many updates are currently being processed concurrently #3984

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

Closed
clot27 opened this issue Nov 25, 2023 · 2 comments · Fixed by #4626
Closed

Add a way to introspect how many updates are currently being processed concurrently #3984

clot27 opened this issue Nov 25, 2023 · 2 comments · Fixed by #4626
Milestone

Comments

@clot27
Copy link
Member

clot27 commented Nov 25, 2023

What kind of feature are you missing? Where do you notice a shortcoming of PTB?

As of now, we can't know how many updates are being processed while using BUP, it would be good to have that for debugging purposes.

Describe the solution you'd like

See #3654 (comment)

Describe alternatives you've considered

Currently, you can use app.update_processor._semaphore._value to get those (I suppose).

Additional context

Was originally suggested by harshil in dev chat IIRC :)

@Bibo-Joshi
Copy link
Member

@clot27 would you still be interested in implementing this?

@clot27
Copy link
Member Author

clot27 commented Jun 22, 2024

Yeah, I would like to implement this, not sure if I am getting time to do so anytime soon…

@Bibo-Joshi Bibo-Joshi changed the title [FEATURE] Add a way to introspect how many updates are currently being processed concurrently Add a way to introspect how many updates are currently being processed concurrently Nov 8, 2024
@Bibo-Joshi Bibo-Joshi added this to the v22.0 milestone Nov 25, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants