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
@captn3m0 This isn't quite enough information to debug the problem. The word "Killed" is never outputted by any of our code. One possibility is that your system may be running out of memory to process the entire list.
You could try out https://github.com/18F/domain-scan as an alternative parallelizer for pshtt, that makes use of Python 3 concurrency primitives to manage a rolling pool of threads over a given CSV. If you don't use the --sort flag, I believe it never holds the entire dataset in memory, and should be time- and memory-efficient.
If you see the same problems, then I would also look at running the tool on a vanilla EC2 server or something like that, to eliminate the possibility of novel interference from something in your local environment.
I'm running pshtt against a file with ~13k domains. These are the final lines of the debug output:
The invocation was:
pshtt domains.csv --markdown --debug --cache --output output.md
The
output.md
file is empty. I've tried running on shorter domain lists and it works fine (NoKilled
in output, and the file is generated correctly).The text was updated successfully, but these errors were encountered: