Closed haristotle closed 4 years ago
Yes, the order of super is very important! If you've fixed the issue, would you care to open a PR with the change? Also be sure to add a note to the changelog and bump the version in sregistry/version.py. There were a bunch of changes to the super class since this module was developed, so I'm not surprised that you hit the issue.
Yes, I have opened a PR. Let me know if I did anything wrong or need to do anything else.
Hi,
I'm new to this, so if I should put this somewhere else, please let me know.
Error Anyways, I am getting the following error when trying to pull a container:
To Reproduce Steps to reproduce the behavior:
sregistry pull 122059246,singularityhub/gitlab-ci
Expected behavior I expected sregistry to pull the container down as in the example here: https://singularityhub.github.io/sregistry-cli/client-gitlab
Workaround I found that if I reordered this block from sregistry/main/gitlab/_init_.py:
to be this:
Then everything works as expected.
I'm not sure if this is the best solution or if there's a good reason to put
super()
in any particular place. Also, I don't know whysuper()
is erasing the data inself.base
, so I feel like this may be a symptom of a bigger issue.Version of Singularity and Singularity Registry Client My Singularity version is 3.5.2+380-gc2452e48d My Singularity Registry Client version is 0.2.34
Let me know if you need anything else.
Thanks!