1. 08 Sep, 2021 1 commit
  2. 20 Jul, 2021 2 commits
  3. 11 Jul, 2021 1 commit
  4. 02 Jul, 2021 1 commit
  5. 24 May, 2021 20 commits
    • Kirill Smelkov's avatar
      Merge branch 'master' into t · d02d6555
      Kirill Smelkov authored
      * master:
        go/zodb: Prevent newly-created not-yet committed objects to go to ghost on deactivate
        go/zodb: Fix PActivate not to panic after an error
        go/zodb/fs1tools: Verify
        go/zodb/fs1tools: Dumper += DumpEndOK
        go/zodb: tests: Add a couple of missed t.Helper()
        go/zodb: tests: Teach tDB.Commit to return committed TID
      d02d6555
    • Kirill Smelkov's avatar
      . · 85475968
      Kirill Smelkov authored
      85475968
    • Kirill Smelkov's avatar
      go/zodb: Prevent newly-created not-yet committed objects to go to ghost on deactivate · bb618ce1
      Kirill Smelkov authored
      When object is just created, it is not yet assigned an OID, but can be
      reachable from other objects. The code that processes transaction can
      reach to that new object and try to PActivate/PDeactivate it. And
      currently PDeactivate will drop the object state completely.
      
      Another example of object without an OID is Bucket embedded into a Tree
      object. There, the code that scans the tree can reach to that bucket and
      try to activate/deactivate it, leading, again, to dropping state of that bucket.
      
      -> Fix it.
      bb618ce1
    • Kirill Smelkov's avatar
      . · 15f12104
      Kirill Smelkov authored
      15f12104
    • Kirill Smelkov's avatar
      . · 9de09953
      Kirill Smelkov authored
      9de09953
    • Kirill Smelkov's avatar
      go/zodb: Fix PActivate not to panic after an error · 67f0d2cd
      Kirill Smelkov authored
      Persistent.PActivate used to panic when called the second time, if the
      first time it hit an error. WCFS hit this in practice via object, that was
      previously accessed and pinned into the cache, but later deleted in the
      storage.
      
      -> Fix PActivate to reset .loading on an error, so that next time PActivate is
      called, it tries to trigger load again instead of panicking. Change doload
      criteria from
      
      	state==GHOST && refcnt==1
      
      to
      
      	state==GHOST && loading==nil
      
      because now, after failed PActivate, refcnt can be != 0, if there are several
      other PActivate calls that were waiting for the failed PActivate but did not
      yet woke up.
      
      Here is how added test fails without the fix:
      
          --- FAIL: TestActivateAfterDelete (1.65s)
          panic: t.zodb.MyObject(0000000000000065): activate: need to load, but .loading != nil [recovered]
                  panic: t.zodb.MyObject(0000000000000065): activate: need to load, but .loading != nil
      
          goroutine 10085 [running]:
          testing.tRunner.func1.2(0x649020, 0xc000520660)
                  /home/kirr/src/tools/go/go/src/testing/testing.go:1143 +0x332
          testing.tRunner.func1(0xc0001cb080)
                  /home/kirr/src/tools/go/go/src/testing/testing.go:1146 +0x4b6
          panic(0x649020, 0xc000520660)
                  /home/kirr/src/tools/go/go/src/runtime/panic.go:965 +0x1b9
          lab.nexedi.com/kirr/neo/go/zodb.(*Persistent).PActivate(0xc0001184d0, 0x6e8360, 0xc00019ac90, 0x0, 0x0)
                  /home/kirr/src/neo/src/lab.nexedi.com/kirr/neo/go/zodb/persistent.go:191 +0xce5
          lab.nexedi.com/kirr/neo/go/zodb.TestActivateAfterDelete(0xc0001cb080)
                  /home/kirr/src/neo/src/lab.nexedi.com/kirr/neo/go/zodb/persistent_test.go:786 +0x72c
      67f0d2cd
    • Kirill Smelkov's avatar
      go/zodb/fs1tools: Verify · 5a26fb31
      Kirill Smelkov authored
      Add utility to verify FileStorage data for consistency.
      To verify we just need to iterate through all records, because
      FileStorage driver performs all consistency checks by itself.
      
      Mimic normal output to be the same as in fstest from ZODB/py.
      Example runs of fstest.py and `fs1 verify` on a broken file:
      
          $ python ~/src/wendelin/z/ZODB/src/ZODB/scripts/fstest.py -v 1.fs
                   4: transaction tid 0x03e044f6448c8022 #0
                 213: transaction tid 0x03e044f646e044bb #1
          1.fs has data records that extend beyond the transaction record; end at 466
      
          $ fs1 verify -v 1.fs
                   4: transaction tid 0x03e044f6448c8022 #0
                 213: transaction tid 0x03e044f646e044bb #1
          2021/05/24 12:43:37 fsverify: 1.fs: 1.fs: transaction record @355: -> (iter data): 1.fs: data record @416: check: data record [..., 466) overlaps txn boundary [..., 458)
      
      As can be seen, in fs1 case, the error contains more details: [start, end) of
      both mismatching transaction and data records.
      
      In addition to fstest-like verbosity, add progress-mode, where % of total
      completion is printed in a style similar to one used by `fs1 verify-index`.
      
      The Go-based implementation is also faster even when data is on HDD. For
      example on a 73GB database provided by @jerome[1] fsrefs.py takes ~15 minutes
      to run and occupy ~70-100% of CPU. On the other hand `fs1 verify` takes ~7
      minutes to run and occupy ~ 20-30% of CPU.
      
      Tests pending.
      
      [1] nexedi/zodbtools!19 (comment 129480)
      5a26fb31
    • Kirill Smelkov's avatar
      go/zodb/fs1tools: Dumper += DumpEndOK · c66dc12d
      Kirill Smelkov authored
      Some dumpers might want to print something at the end of their dump.
      We will need this functionality for Verify (see next patch).
      c66dc12d
    • Kirill Smelkov's avatar
      . · 86db839d
      Kirill Smelkov authored
      86db839d
    • Kirill Smelkov's avatar
      . · bf50c7a7
      Kirill Smelkov authored
      bf50c7a7
    • Kirill Smelkov's avatar
      . · b80071ce
      Kirill Smelkov authored
      b80071ce
    • Kirill Smelkov's avatar
      . · c864ec80
      Kirill Smelkov authored
      c864ec80
    • Kirill Smelkov's avatar
      . · 24ab091c
      Kirill Smelkov authored
      24ab091c
    • Kirill Smelkov's avatar
      . · 48b8fcaf
      Kirill Smelkov authored
      48b8fcaf
    • Kirill Smelkov's avatar
      . · ab729680
      Kirill Smelkov authored
      ab729680
    • Kirill Smelkov's avatar
      . · ed46529d
      Kirill Smelkov authored
      ed46529d
    • Kirill Smelkov's avatar
      . · 9160424c
      Kirill Smelkov authored
      9160424c
    • Kirill Smelkov's avatar
      7d896243
    • Kirill Smelkov's avatar
      go/zodb: tests: Teach tDB.Commit to return committed TID · c68c0994
      Kirill Smelkov authored
      And use that in the callers.
      c68c0994
    • Kirill Smelkov's avatar
      . · aa4b6f46
      Kirill Smelkov authored
      aa4b6f46
  6. 23 May, 2021 1 commit
  7. 19 May, 2021 3 commits
  8. 10 May, 2021 2 commits
  9. 03 May, 2021 1 commit
  10. 26 Mar, 2021 8 commits