Caching files always in `use_file`
What does this MR do?
This MR solves the conflicts by
- The artifacts browser
I think the solution is
use_fileshould not be in the exclusive lease. It always reads the existing file regardless of the file store (i.e.
- Once we fire
use_file, we always make a clone (cache) of the original file and remove the cache after the READ operation is done. This prevents the process of
migrate!removes the original file and disturbs READing.
Does this MR meet the acceptance criteria?
- Changelog entry added, if necessary
- Tests added for this feature/bug
- Conform by the code review guidelines
- Has been reviewed by a Backend maintainer
End-to-end tests pass (
package-and-qamanual pipeline job)
What are the relevant issue numbers?