GitLab

Wire flatfs sync argument into Datastore creation

add option to disable syncing

allow put to try again if it fails due to too many open files

add log statement for retry

vendor

add threadsafe mount datastore and small fixups on keytransform

Fix interface issues and implement more things on sub-datastores

thanks to btc

Batching

implement batch ops for different datastore types

rename Transaction to Batch

Revert "add in support for batched writes"

add in benchmarks for put and batchput

move batching into separate interface

address concerns from PR

regrab old code

Revert "add in support for batched writes"

add in support for batched writes

switch uuid implementation

motivation: code.google.com is going away and satori's seemd sufficient and not overly complex

measure: Unregister at Close time

This allows open-close-open cycles with the same prefix.

measure: Datastore wrapper that records metrics

Backport from go-ipfs, fix tests, hopefully fix Windows

For background, see https://github.com/golang/go/issues/3366

Here's the failure seen:

    --- FAIL: TestPutOverwrite (0.03s)
    	flatfs_test.go:118: Put fail: rename C:\Users\gates\AppData\Local\Temp\test-datastore-flatfs-679014441\7175\put- 717454915 C:\Users\gates\AppData\Local\Temp\test-datastore-flatfs-679014441/7175/71757578.data: Cannot create a file when that file already exists.

Used to error out with

    flatfs_test.go:66: Put fail: failed to open dir: fsync: The handle is invalid

It seems Windows does not want syscall.Fsync to be called on directory
handles.