1. 07 Nov, 2017 2 commits
  2. 27 Oct, 2017 1 commit
  3. 29 Sep, 2017 3 commits
  4. 11 Sep, 2017 1 commit
  5. 05 Sep, 2017 1 commit
  6. 28 Aug, 2017 1 commit
  7. 11 Jul, 2017 1 commit
  8. 04 Jul, 2017 2 commits
  9. 30 Jun, 2017 1 commit
  10. 29 Jun, 2017 1 commit
  11. 16 Jun, 2017 1 commit
  12. 15 Jun, 2017 2 commits
  13. 14 Jun, 2017 1 commit
  14. 13 Jun, 2017 1 commit
  15. 12 Jun, 2017 7 commits
  16. 12 May, 2017 5 commits
  17. 11 May, 2017 1 commit
  18. 10 May, 2017 2 commits
  19. 04 May, 2017 1 commit
  20. 02 May, 2017 1 commit
    • Julien Muchembled's avatar
      master: fix identification of unknown masters · fbcf9c50
      Julien Muchembled authored
      This fixes the following crash:
      
        Traceback (most recent call last):
          ...
          File "neo/master/handlers/identification.py", line 94, in requestIdentification
            uuid = app.getNewUUID(uuid, address, node_type)
          File "neo/master/app.py", line 449, in getNewUUID
            assert uuid != self.uuid
        AssertionError
      fbcf9c50
  21. 28 Apr, 2017 3 commits
    • Julien Muchembled's avatar
      Better logging of connector errors · 29e8323c
      Julien Muchembled authored
      29e8323c
    • Julien Muchembled's avatar
    • Julien Muchembled's avatar
      client: fix possible data corruption after conflict resolutions with replicas · 46c36465
      Julien Muchembled authored
      This really fixes the bug described in
      commit 40bac312,
      which could probably be reverted. It only reduced the probability of failure.
      
      What happened is that the second conflict on 'a' for t3 what first reported by
      an answer to first store with:
      - a base serial at which a=0
      - a conflict serial at which a=7
      However, the cached data is not 8 anymore but 12, since a second store already
      occurred after the first conflict (reported by the other storage node).
      
      When this conflict was resolved before receiving the conflict for second store,
      it gave:
      
        resolve(old=0, saved=7, new=12) -> 19
      
      instead of:
      
        resolve(old=4, saved=7, new=12) -> 15
      
      (if we still had the data of the first store, we could also do
        resolve(old=0, saved=7, new=8)
       but that would be inefficient from a memory point of view)
      
      The bug was difficult to reproduce. testNotifyReplicated had to be run many
      many times before that race conditions trigger it. The test was changed to
      enforce some of them, and the above scenario now happens almost always.
      46c36465
  22. 27 Apr, 2017 1 commit