8.3.2.29. v4.3.8ΒΆ

commit a694d1716d533796927710d773e8f3a07f83c9fc
Author: Greg Althaus <galthaus@austin.rr.com>
Date:   Fri Oct 2 09:43:51 2020 -0500

    build: update to v4.3.8

M   go.mod
M   go.sum

commit 8e8a790770d6174345d67106b23b19f82980b5b9
Author: Greg Althaus <galthaus@austin.rr.com>
Date:   Thu Sep 24 13:30:45 2020 -0500

    fix(static,api): clean paths for general files

M   backend/fs.go
A   clitest/static_test.go
M   frontend/frontend.go

commit 6f87c14ebbdb651cf102826e615d3f1eb24bbf85
Author: Greg Althaus <galthaus@austin.rr.com>
Date:   Thu Aug 6 12:33:38 2020 -0500

    build: Fix build break from back port - nOfThese

M   datastack/index/index_test.go

commit 5fb2f22920b6f9e8ff740c3c042c1cc12b84a9ad
Author: Victor Lowther <victor.lowther@gmail.com>
Date:   Wed Aug 5 12:31:23 2020 -0500

    fix(indexCorruption): Indexes were being corrupted by duplicate adds/removes

    The index.Add and index.Remove code was not properly accounting for having duplicate items passed to Add and Remove,
    respectively.  That caused Remove to remove extra unrelated items in the case of being called with duplicates,
    potentially leading to a panic dues to slices being out of bounds.  Add was potentially allowing multiple items in the
    Index to have the same Key(), which violates our deeply held beliefs that all keys must be unique for sanity's sake.

    This fixes both of those issues by refactoring the Add and Remove codepaths to be aware of duplicates and handle them --
     in the case of the Remove codepath, duplicates are ignored, and in the case of the Add codepath, the last of the
     objects with identical Key() values will be the one that winds up in the index.

    Signed-off-by: Victor Lowther <victor.lowther@gmail.com>

M   datastack/index/index.go
M   datastack/index/index_test.go

End of Note