Determining downloader shard_size isn't robust
braydonf opened this issue · 1 comments
There is an issue where the state->shard_size could be set to too small of a value if the first pointer added is the last, tail shard. The shard size should be based on the pointer at index 0, this info is necessary before requesting any shards.
👋 Hey! Thanks for this contribution. Apologies for the delay in responding!
We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.
As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!