Kyle Meyer
Kyle Meyer
> At reproman/interface/retrace.py:211, we iterate over a tracer to get distributions and files, using the distribution every iteration but the files only from the last: > [...] > We should...
> No, I didn't find a problem case All right, thanks for confirming. > In fact, I'd rather if we made the tracer.identify_distributions() functions so we don't have to iterate...
I tried to trigger the issue with the script below but didn't have any luck. script ```sh #!/bin/sh set -eux cd $(mktemp -dt rman-XXXXXXX) git init virtualenv --python=python3 ./venv #...
Yeah, I see that too with `python -m pytest -s -v reproman/tests/test_api.py` That call seems to read quite a few files under `.git/`, mostly refs. ``` $ reprozip trace python...
It's worse than not having the ability to rerun from the local machine. reproman run records for concurrent jobs are not compatible with datalad rerun. See the run record bullet...
Odd. Do you see that with every docker image you retrace? I've tried a few images, from within and outside a git repo, and can't convince retrace to assign it...
> @kyleam - do you some easy wrapper around docker to given a docker hub "repository" (such as https://hub.docker.com/_/neurodebian) to mint all needed calls to `datalad containers-add`? Hmm, does this...
I've pushed a rough prototype, which may or may not be viable start, to kyleam/datalad-container-dhub-tags (obviously not its final home if it ends up being useful). `python containers_add_dhub_tags.py --help` will...
> * since there is only one version for a tag at a given point in time when we run it, and otherwise information about the tag would be lost,...
> do you know if there is some associated with manifest date (I do not see anything in `manifest`)? I'm not sure I understand your question, but either way I'm...