sqlx's close method on a Pool is meant to only return when all connections have been closed and freed, but there have been bugs introduced in this area before, and it seems like removal can occasionally fail on Github's CI at the moment. I think the best solution might be to just retry removing the file a fixed number of times with delays, up to 1s total maybe.
sqlx's
closemethod on a Pool is meant to only return when all connections have been closed and freed, but there have been bugs introduced in this area before, and it seems like removal can occasionally fail on Github's CI at the moment. I think the best solution might be to just retry removing the file a fixed number of times with delays, up to 1s total maybe.