Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A ace
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • adapt
  • ace
  • Issues
  • #48
Closed
Open
Issue created May 08, 2018 by Michael Ritter@shakeContributor

Update CollectionCountContext when a Collection is updated

There are various situations where items might be removed/added/modified and the CollectionCountContext does not get properly updated. We should ensure that modifications to a collection will update the respective context:

  • fileCountMap
  • fileActiveMap
  • fileCorruptMap
  • fileMissingMap
  • fileMissingTokenMap
  • fileTokenMismatchMap
  • totalErrorMap
  • totalSizeMap
  • fileRemoteMissing
  • fileRemoteCorrupt

Also when working on this issue, now might be a good time to check out a different way of caching these (using caffeine or guava).

Assignee
Assign to
Time tracking