You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: