Chris Combs
Chris Combs
@dolce can you please publish 1.6.0 to npm
I believe this may have been caused by 89dc9015bda754b37cc12c06c9af7919690a2fe6. I'll try to get my environment set up to file a PR for the GUI.
OK, #578 ought to patch this up.
I see the same with the Ubuntu package, it barfs as follows: ``` rmlint --no-with-color -T duplicates --see-symlinks --partial-hidden -c sh:handler=symlink --hardlinked --crossdev --size 1-18446744073709551615 --max-depth 512 -o json -c...
same as #84? —me, a rando
Same problem here. I think this is because of the progress output which "rewrites itself" but is still adding to the output bytes of data. you can see it replay...
it looks like the output is provided by `tqdm` in logger.py: ``` def def_tqdm(x): return tqdm(x, leave=True, file=sys.stdout, bar_format="{n_fmt}/{total_fmt} [{elapsed}
ok, I forked the repo and changed it from 0.1 second update interval to 10 seconds. I'm running it now in colab pro and am seeing many fewer status updates....
yes--they say it requires a graphics card (GPU) with 16gb of ram (usd $8000). Or you can play with it in Google CoLab for $0 and a lot of patience
thank you, that's good to know!