Sling
  1. Sling
  2. SLING-2402

The file data store is not synchronized

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: Installer Core 3.3.2, Installer Core 3.3.4
    • Fix Version/s: None
    • Component/s: Installer
    • Labels:
      None

      Description

      The current file data store is only partially synchronized. As sometimes can be seen in the BundleInstallUpgradeDowngradeTest#testRemoveAndReadd test:
      1. a resource is added, copied into the file data store
      2. this gets removed again
      3. before it is finally removed, the same resource is added again
      4. the file data store still has the pointer to the old file as it is unchanged and uses that
      5. The file gets removed from the data store due to 2.
      6. The resource from 3. is tried to be transformed, file is not available anymore -> failure

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        1h 1m 1 Carsten Ziegeler 03/Feb/12 14:13
        Gavin made changes -
        Workflow re-open possible,doc-test-required [ 12787861 ] no-reopen-closed,doc-test-required [ 12790677 ]
        Gavin made changes -
        Workflow no-reopen-closed,doc-test-required [ 12766278 ] re-open possible,doc-test-required [ 12787861 ]
        Gavin made changes -
        Workflow Copy of no-reopen-closed,doc-test-required [ 12762651 ] no-reopen-closed,doc-test-required [ 12766278 ]
        Gavin made changes -
        Workflow no-reopen-closed,doc-test-required [ 12651784 ] Copy of no-reopen-closed,doc-test-required [ 12762651 ]
        Carsten Ziegeler made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s Installer Core 3.3.6 [ 12319558 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Carsten Ziegeler added a comment -

        Rethinking this, the data store is synced in general and this is really an edge use
        cases. The exact same artifact has to be provided directly again after it has been
        removed. The time window is very small as well.
        As I want to avoid rewriting the data store i'll close this as wont fix and fix the
        test instead.

        Show
        Carsten Ziegeler added a comment - Rethinking this, the data store is synced in general and this is really an edge use cases. The exact same artifact has to be provided directly again after it has been removed. The time window is very small as well. As I want to avoid rewriting the data store i'll close this as wont fix and fix the test instead.
        Carsten Ziegeler created issue -

          People

          • Assignee:
            Carsten Ziegeler
            Reporter:
            Carsten Ziegeler
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development