1. 01 Dec, 2020 8 commits
  2. 08 Oct, 2020 1 commit
    • Tim Burke's avatar
      Release 1.6.2 · 9dccbc9f
      Tim Burke authored
      Change-Id: I733c4bcf28d845aa0413ef4af06cdab6bc25cc7b
      9dccbc9f
  3. 02 Oct, 2020 1 commit
    • Kota Tsuyuzaki's avatar
      Add a few coverage for legacy crc code · 15a257e5
      Kota Tsuyuzaki authored
      it actually doesn't assert the value
      becase we now use same if statement
      for the assertion but hope it to be
      even a little better than no covarage.
      
      Change-Id: I8860a2a8227e43e02afddcbad1e108157c0872f6
      15a257e5
  4. 30 Sep, 2020 1 commit
    • Tim Burke's avatar
      Be willing to write fragments with legacy crc · 5626cd57
      Tim Burke authored
      ...if users *really* want to. They opt-in at run time by setting
      
          LIBERASURECODE_WRITE_LEGACY_CRC=1
      
      in the environment; leaving it unset, set to an empty string, or set to
      the string "0" continues to write zlib crcs.
      
      UpgradeImpact
      =============
      This option is intended to allow a smooth upgrade from liberasurecode
      1.5.0 and earlier in a system with multiple readers and writers:
      
        * Before upgrade, ensure the environment variable is set on all nodes.
          This will be ignored by earlier versions.
        * Upgrade liberasurecode on each node in the system, restarting any
          services that use it. Every node continues writing CRCs that are
          still usable by nodes that have not yet upgraded.
        * Now that every node is capable of reading zlib CRCs, remove the
          environment variable from each node to start writing new CRCs.
      
      If you are already using 1.6.0 or later, just upgrade normally.
      
      Closes-Bug: #1886088
      Closes-Bug: #1867937
      Related-Bug: #1666320
      Needed-By: https://review.opendev.org/#/c/739164/
      Change-Id: I9adfbe631a2dddc592fd08f8a325f3e8331b92f1
      5626cd57
  5. 04 Apr, 2020 1 commit
  6. 13 Mar, 2020 1 commit
  7. 11 Mar, 2020 1 commit
    • Tim Burke's avatar
      Reformat license file · b24c23da
      Tim Burke authored
      *Hopefully*, this will make it "standard" enough that GitHub will
      call it out as the BSD-2-Clause that it is.
      
      Change-Id: If097a3d86e1bd22cebbcbc160c6ae238663843c5
      b24c23da
  8. 11 Feb, 2020 1 commit
  9. 06 Feb, 2020 2 commits
    • Pete Zaitcev's avatar
      Do not discard a technical return value in tests · 4568188d
      Pete Zaitcev authored
      Compilers are getting smarter, and we started getting this:
      
      libec_slap.c: In function 'test_hd_code':
      libec_slap.c:285:14: error: 'frags.array' may be used uninitialized
       in this function [-Werror=maybe-uninitialized]
      
      The fix is to consume the error code in such a way that the
      test proceeds further only when frags are indeed initialized.
      
      Change-Id: I54db0172a36419206d00b22608523a08818f41f6
      4568188d
    • Thiago da Silva's avatar
      Build and test on centos-8 node · 4e4995cc
      Thiago da Silva authored
      Change-Id: I6c7a1725ba00981d45511fc3c18795737b1967cb
      4e4995cc
  10. 30 Jan, 2020 1 commit
  11. 29 Jan, 2020 1 commit
  12. 14 Jan, 2020 3 commits
  13. 21 Oct, 2019 1 commit
  14. 20 Oct, 2019 1 commit
  15. 18 Oct, 2019 1 commit
  16. 18 Jul, 2019 1 commit
  17. 16 Jul, 2019 3 commits
  18. 08 Jul, 2019 9 commits
  19. 02 Jul, 2019 1 commit
  20. 12 Jun, 2019 1 commit