You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run arbtt-stats on my laptop, which has been sitting idle for weeks, and get this:
arbtt-stats: Data.Binary.Get.runGetState at position 4321: Not a valid Unicode code point!
CallStack (from HasCallStack):
error, called at libraries/binary/src/Data/Binary/Get.hs:312:5 in binary-0.8.6.0:Data.Binary.Get
arbtt-stats: Data.Binary.Get.runGetState at position 4321: Not a valid Unicode code point!
CallStack (from HasCallStack):
error, called at libraries/binary/src/Data/Binary/Get.hs:312:5 in binary-0.8.6.0:Data.Binary.Get
If I run arbtt-dump, I get the same error, but it dumps records until it hits the error, so I can see the date of the record with the error, which is last month. Is there a way I can find the record, so that 1) I can post just the bad record here, without 760 MB of irrelevant data, and 2) I can fix the file so that I can get my stats again?
Arbtt version is 0.10.2, installed from the Ubuntu repo.
The text was updated successfully, but these errors were encountered:
For 2), try arbtt-recover. I expect optimistically that it will recover from this problem as well. The question will be whether it’s just a few samples that are affected, or if big parts of the file are affected, and why.
For 1), it says “at position 4321”, so maybe something like dd can be used to extract a portion of the file from that point on?
I run arbtt-stats on my laptop, which has been sitting idle for weeks, and get this:
If I run arbtt-dump, I get the same error, but it dumps records until it hits the error, so I can see the date of the record with the error, which is last month. Is there a way I can find the record, so that 1) I can post just the bad record here, without 760 MB of irrelevant data, and 2) I can fix the file so that I can get my stats again?
Arbtt version is 0.10.2, installed from the Ubuntu repo.
The text was updated successfully, but these errors were encountered: