Michal Stolarczyk

I think it this further indicates that that's a concurrency issue. The config is in a corrupted state when it is read by the process that produced these logs --...

are you worried about misusage of this functionality? I think it's pretty useful

so this would go even beyond a single genome? Yes, I'm still on board, this use case warrants implementation

I think this will be relatively easy: 1. implement "force _no_ overwrite" functionality in `RefGenConf.pull` 2. API call to this endpoint: http://refgenomes.databio.org/v2/assets 3. call `RefGenConf.pull(..., no_overwrite=True)` for each result

hi @AndrewSkelton, thanks for reaching out. Which assets are you exactly referring to? These ones? - [hg38/salmon_partial_sa_index](http://refgenomes.databio.org/v3/assets/splash/2230c535660fb4774114bfa966a62f823fdb6d21acf138d4/salmon_partial_sa_index?tag=default) - [hg38/tgMap](http://refgenomes.databio.org/v3/assets/splash/2230c535660fb4774114bfa966a62f823fdb6d21acf138d4/tgMap?tag=default) We definitely didn't remove any sequences/transcripts on purpose. The assets are...

I think you should be able to do that like this: 1. build a new `fasta` asset based on a cDNA sequence and tag it as `cdna` ``` refgenie build...

Hi! yes, that's a valid point, which we have recognized some time ago. We successfully run I'd say ~100 builds in parallel and this is accommodated by config file locking...

> Maybe we never tried it and we may not be checking that correctly -- or maybe it is allowable, @stolarczyk correct me if I'm wrong here. It's not allowable,...

there's a command specifically designed for this: ``` ~ refgenie alias get -a hg38 58de7f33a36ccd9d6e3b1b3afe6b9f37cd5b2867bbfb929a ```

``` usage: refgenie alias get [-h] [-c C] [--skip-read-lock] [-a A [A ...]] Get aliases. optional arguments: -h, --help show this help message and exit -c C, --genome-config C Path...