Matthias Dellweg

Do we need a versioned dependency on dynaconf here?

> @mdellweg the feature used here is added on dynaconf 3.2.5 https://github.com/dynaconf/dynaconf/releases/tag/3.2.5 which is not available on pulpcore 3.49 https://github.com/pulp/pulpcore/blob/3.49/requirements.txt#L19 (the lower bound for pulp_ansible) > > We would need...

FWIW, I believe failing to download the avatar (by the power of firewall) should not impact the correctness and success of the sync. And for the security concerns, the validity...

Can you confirm that your version runs with this DeclarativeFailsafeArtifact statement? https://github.com/pulp/pulp_ansible/blob/main/pulp_ansible/app/tasks/collections.py#L713

Oh, the skipping seems to work. But there's another bug appearing: "'NoneType' object is not iterable" Can you confirm, this happens on the newest version too?

> So you say that the namespace avatar was never the problem? I'm saying the skipping of downloads works as advertised. But I don't yet understand the "real" cause of...

If you want to do some debugging, It would be interesting to know which stage throws the error. Also can you spot a place, where d_artifacts is set to None?

Thanks for looking into this. If you get to see it again, we should have bugreport issue for it. Let's keep this issue as a wishlist item. The original ask...

`is_highest` was the actual name of the bad field. It's use has been removed. This issue can conclude with the removal of the field from the database.

We need to remove them. In general, as long as we allow content to be shared, the content itself cannot tell you where it came from.