Uploaded image for project: 'Ivy'
  1. Ivy
  2. IVY-1145

metadata lock files not always deleted from cache

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.0-RC1
    • Fix Version/s: 2.2.0-RC1
    • Component/s: Core
    • Labels:
      None

      Description

      DefaultRepositoryCacheManager.cacheModuleDescriptor() sometimes leaves metadata*.lck files in the cache directory after a successful resolve. the problem seems to only occur when the searched artifact is actually found in the cache.

      The problem starts on DefaultRepositoryCacheManager:880, where the lock is created. It looks like lock / unlock should always happen in a try/finally, which doesn't happen here. In my case, the method returns on line 920 without ever unlocking the file.

      The issue started at revision 805346 (the most recent revision to this file).

      happy coding
      jt

        Activity

        Hide
        maartenc Maarten Coene added a comment -

        Thanks for reporting!
        It should be ok now in trunk, could you give it a try?

        Maarten

        Show
        maartenc Maarten Coene added a comment - Thanks for reporting! It should be ok now in trunk, could you give it a try? Maarten
        Hide
        tormp Jason Trump added a comment -

        yep, trunk build resolves issue, thanks.
        jt

        Show
        tormp Jason Trump added a comment - yep, trunk build resolves issue, thanks. jt

          People

          • Assignee:
            maartenc Maarten Coene
            Reporter:
            tormp Jason Trump
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development