ransomw1c

slight scope shift here as the plan is to use a `--concurrency-factor` flag for both `bundle upload` and `download` that can be set between `1` and the upper bound on...

skimmed over some of `git` to understand what needs to be done here, although i'm erring toward a semi-naive implementation: list labels will get label data and bundle data, put...

@galvare2 what to do in the case of multiple labels referring to the same bundle? although we're not using the exact same format, git ``` commit 72c11afbbbb0ea7ec8edaf8601d203977e5ea7f6 (tag: 0.5, d20190625-storageputparamtype--wip)...

> The choice to include labels when listing bundles should be optional. There is a performance implication for it. i agree > other features I have been thinking of that...

it'd be good to have a proposal for user feedback (that is, to gauge intent of the changes) for large files. cafs parallelization is already done.

there's been an ask from Zhuo for a clearer way to indicate progress on uploads

it's worth mentioning that > no explicit `panic()` should be allowed to cross a package boundary. https://github.com/golang/go/wiki/PanicAndRecover#usage-in-a-package in other words, we don't need to defend panics in the same way...

here are [more](https://about.sourcegraph.com/blog/go-when-is-it-ok-to-recover) [opinions](https://github.com/grpc/grpc-go/issues/441#issuecomment-155588816) on the proper use of `recover()`. i'm inclined to agree that > catching a panic might leave [datamon] in an inconsistent or incorrect state, so while...

here are a few ideas to describe the sort of feature requests this issue might track. ### multiple downloads from the same bundle to the same destination the current use-case...

there are some conventions over configuration scattered throughout the application. another constant that exists, where changing it could break source-data compatability, is the blob size. needless to say, pack and...