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

Debugging facilities? #38

Open
ale-dd opened this issue Sep 24, 2021 · 0 comments
Open

Debugging facilities? #38

ale-dd opened this issue Sep 24, 2021 · 0 comments

Comments

@ale-dd
Copy link

ale-dd commented Sep 24, 2021

I am well aware that not even asyncio provides good debugging facilities for anything related to concurrency. But aioprocessing being often adopted as a drop-in replacement at a late stage in the development cycle, it has the opportunity to surface race conditions that were introduced by code written much before the adoption of aioprocessing by a given project. This makes chasing root causes much harder than for software that has grown organically around aioprocessing from the get-go. Is there any advice as to what would be the best practices, or any good hint as to where to best instrument the aioprocessing code to support ease of debugging?

thank you!

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