-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
status/acceptedWe accept to investigate or work on it.We accept to investigate or work on it.status/needs-attentionThis issue needs more eyes on it, more investigation might be required before accepting/rejecting itThis issue needs more eyes on it, more investigation might be required before accepting/rejecting it
Description
What version of Go are you using (go version)?
$ go version
go version go1.14.1 linux/amd64What version of Badger are you using?
github.com/dgraph-io/badger v1.6.1
Does this issue reproduce with the latest master?
I did not have bandwidth to check
What are the hardware specifications of the machine (RAM, OS, Disk)?
CPU: i7-4770S
RAM: 32GB
HDD: 11T
What did you do?
While running go-ipfs 0.5.0-rc1 I noticed this message printed to my terminal:
Latest Entry Header in LSM Key: !badger!move/blocks/AFKREICVWSZ4BCVY3SJSTPHPGVEHRJR5WCNTX3MCPI2GXU4IOPC6GD25TQÿÿÿÿÿþ Meta: 0 UserMeta: 0 Offset: 104817649 len(val)=262144
Latest Entry in Log Key: !badger!move/blocks/AFKREICVWSZ4BCVY3SJSTPHPGVEHRJR5WCNTX3MCPI2GXU4IOPC6GD25TQÿÿÿÿÿþ Meta: 0 UserMeta: 0 Offset: 596118870 len(val)=262144
IPFS-specific details in ipfs/kubo#7131 (comment), but filling here as suggested by @Stebalien
Metadata
Metadata
Assignees
Labels
status/acceptedWe accept to investigate or work on it.We accept to investigate or work on it.status/needs-attentionThis issue needs more eyes on it, more investigation might be required before accepting/rejecting itThis issue needs more eyes on it, more investigation might be required before accepting/rejecting it