[BUG]: Corrupt and lost data about badger HOT 1 CLOSED

Ohhh wow i found the error... this is some forgotten semicolon level stuff:

if forgot to copy the chunk variables for the goroutines and their pointer got assigned a new value while the goroutines where running.
This took me way to long to catch.

And also i tested all modes with up to 10000 concurrencies and it seams to work!

Maybe not so obvious but one needs to do this in a for loop with wb.Set too, i guess because wb.Set is only executed when wb.Flush() is called.

func (k *KeyValStore) BatchWriteChunk(chunks []buzhashChunker.ChunkData) error {

	wb := k.badgerDB.NewWriteBatch()
	defer wb.Cancel()

	for _, chunk := range chunks {
		chunk := chunk // important

		atomic.AddUint64(&k.writeCounter, 1)
		err := wb.Set(chunk.Hash[:], chunk.Data)
		if err != nil {
			log.Fatal("Error writing chunk: ", err)
			return err
		}
	}

	return wb.Flush()
}

This is even defined in the documentation

https://pkg.go.dev/github.com/dgraph-io/badger#Txn.Set

from badger.