git: reuse most recent backend when possible #51

pmrowla · 2022-03-28T06:07:11Z

When selecting a backend to use for a given git call, we will now try the most recently used backend first, before trying the remaining backends
If we are switching backends, close the previously used backend before making the git call w/new backend

pmrowla · 2022-03-28T06:14:36Z

scmrepo/git/__init__.py

@@ -71,6 +77,10 @@ def reset_all(self) -> None:
        for backend in self.initialized.values():
            backend._reset()  # pylint: disable=protected-access

+    def move_to_end(self, key: str, last: bool = True):


We could just make this move_to_head() and get rid of the last option (since that's all we will ever use), but I went with this for now to stay consistent with the OrderedDict call

pmrowla self-assigned this Mar 28, 2022

pmrowla commented Mar 28, 2022

View reviewed changes

git: reuse most recent backend when possible

313a06b

pmrowla force-pushed the pygit-merge-nfs branch from d4759f2 to 313a06b Compare March 30, 2022 04:44

pmrowla marked this pull request as ready for review March 30, 2022 04:44

pmrowla merged commit 49024b9 into iterative:main Mar 30, 2022

pmrowla deleted the pygit-merge-nfs branch March 30, 2022 04:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

git: reuse most recent backend when possible #51

git: reuse most recent backend when possible #51

pmrowla commented Mar 28, 2022

pmrowla Mar 28, 2022 •

edited

Loading

git: reuse most recent backend when possible #51

git: reuse most recent backend when possible #51

Conversation

pmrowla commented Mar 28, 2022

pmrowla Mar 28, 2022 • edited Loading

Choose a reason for hiding this comment

pmrowla Mar 28, 2022 •

edited

Loading