If we rely on the server side to do the recursion, we don't have fine grained control on the client side on what a reasonable timeout for the cooking is, because the storage has to return all the tree at once, instead of doing one request per level.
Description
Description
Revisions and Commits
Revisions and Commits
Related Objects
Related Objects
- Mentioned In
- rDVAU9f673806699a: cookers.revision_*: Fix storage timeouts when fetching a large revision log
D1778: Fix revision cooking errors with the vault for large revision log
T1934: vault timeout on cooking revision_gitfast for repositories with numerous number of revisions
rDSTO2eced78da85d: algos.dir_iterators: Implement iterator protocol in DirectoryIterator
D445: vault.to_disk: Perform directory recursive iteration client-side
D444: storage.algos.dir_iterators: Fixes and improvements - Mentioned Here
- rDSTO329d0f920895: storage: set timeout to 20s for directory_ls