Unify handling of "IsBusy" across the SQLite provider
Open
area-adonet-sqlite
- Dominant language
- C#
- Stars
- 14.8k
- Forks
- 3.4k
- PR merge metrics
- PR metrics pending
Description
Today we have the looping around "IsBusy" on multiple places. Duplicating the logic and (more importantly) possibly not handling it in all places (i.e. #36295).
We should create an unified way of handling the "IsBusy" (or maybe reusing what is already done in `RetryWhileBusy`) and do a sweep across the code and plug it in every place where required.
The retry logic can also be bit smarter and retry right away the first time and then do maybe exponential backoff.
Contributor guide
Assessment
This issue has not been assessed yet.