kallithea Changeset - 496df7eb2bc2

Changeset - 496df7eb2bc2

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Mads Kiilerich - 6 years ago 2019-10-20 21:55:40
mads@kiilerich.com

Grafted from: 06c9f46eb700

model: use repo.set_invalidate() instead of accesssing CacheInvalidation directly

Trying to contain the use of CacheInvalidation ...

1 file changed with 2 insertions and 2 deletions:

kallithea/model/scm.py

0 comments (0 inline, 0 general)

kallithea/model/scm.py

➞

Show inline comments

@@ @@ -48,7 +48,7 @@ from kallithea.lib.vcs.backends.base imp @@
 from kallithea.lib.vcs.exceptions import RepositoryError
 from kallithea.lib.vcs.nodes import FileNode
 from kallithea.lib.vcs.utils.lazy import LazyProperty
-from kallithea.model.db import CacheInvalidation, PullRequest, RepoGroup, Repository, Session, Ui, User, UserFollowing, UserLog
 from kallithea.model.db import PullRequest, RepoGroup, Repository, Session, Ui, User, UserFollowing, UserLog
 log = logging.getLogger(__name__)
@@ @@ -217,9 +217,9 @@ class ScmModel(object): @@
         :param repo_name: the repo for which caches should be marked invalid
         """
         log.debug("Marking %s as invalidated and update cache", repo_name)
         CacheInvalidation.set_invalidate(repo_name)
         repo = Repository.get_by_repo_name(repo_name)
         if repo is not None:
             repo.set_invalidate()
             repo.update_changeset_cache()
     def toggle_following_repo(self, follow_repo_id, user_id):

0 comments (0 inline, 0 general)