Jonathan Manning

e.g. here's how I've set up some human assets: ``` > refgenie list -g homo_sapiens--GRCh38 Local refgenie assets Server subscriptions: http://refgenomes.databio.org ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ genome ┃ asset (seek_keys) ┃ tags ┃...

Okay, thanks for the response @stolarczyk

@stolarczyk I notice the 'likely solved' tag- could you expand? e.g. how would I modify the above hack to get the information more cleanly? I notice that there's not been...

+1 for more flexibility and to subscribe.

Thanks for the help @stolarczyk - and fair enough. I'll do that for now.

@stolarczyk is this now solved by https://github.com/refgenie/refgenie/commit/3bcb4ff07a7e9239889569ee33bbe481fcdbed13, so I can [re-tag as the docs say](http://refgenie.databio.org/en/latest/tag/)?

Okay, thank for the info @nsheff . We would definitely like this as per the OP, right now we're using excess storage building the same asset twice just so that...

Thank you, but no, that doesn't really cover it. For one thing it's not very explicit ('default' behaviours doing quite specific things always worry me a bit). For another we...

Note: as a workaround I've added a back-off to the retries which _seems_ to be helping.

Here are some high-verbosity logs from an example. [stdout.txt](https://github.com/refgenie/refgenie/files/6598863/stdout.txt) [stderr.txt](https://github.com/refgenie/refgenie/files/6598864/stderr.txt)