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
@thekthuser I don't think start-offset stuff will help you here. I'm rather strapped for time, so I won't be able to help sort this in the short term; however, if someone comes along and is open to submitting a patch, I'm happy to review it.
There are two things to look at
(Easy) Remove the log message Unable to scan target for gzips; this is expected, it means it found something that looked like a gzip file, but the file was so broken it couldn't read it. Flooding the log with those messages is unhelpful
(Hard) Find source of the race condition bug you've bumped into where close happens before the system is finished. It could be that it'd be better to rewrite the scanner to just be single-threaded; I don't think much performance is gained from the goroutines in the code since the I/O of Go is so far from exhausting read performance of a modern disk
When I run this after scanning 90+% or possibly 100% I get an uncountable (past my terminal's scrollback limit) number of lines with variations of:
followed by:
Is there an argument I can add to get around this? Are the found (maybe just possible) wallets being saved somewhere I can find?
The text was updated successfully, but these errors were encountered: