HTTP Status code 503 or 429 on building large trees
There should be better options to configure a slight 10-50 ms delay to decrease throughput.
There should be more clarity as to if errors are being handled, skipped, or resulting in panics/missing people/missing details, or what retry logic is being used and whether a timeout/failure is possible where things are skipped entirely (and we give up on retrying them).
Possibly some more command-line switches or logging (have not looked into logging that deep yet).
Good idea. This fork is using rate limiter.
@artifexor This looks solid. It achieves a lot in a few changes. Do you have any plans to open a PR against this repo, by @Linekio ?
@gamesguru I have not tried yet. I just found that fork (via github insight/network) when I noticed the enormous amount of http errors and look for a solution. And indeed, it is a very elegant solution. I am not familiar with this PR thing, so I have no such plan.
@gamesguru I have not tried yet. I just found that fork (via github insight/network) when I noticed the enormous amount of http errors and look for a solution. And indeed, it is a very elegant solution. I am not familiar with this PR thing, so I have no such plan.
I added it at https://github.com/Linekio/getmyancestors/pull/74, it merged cleanly.