asdf-2.14.1 leads to a condition where weldx extension is found twice.

[marscher]

This makes get_weldx_extension() fail, as the weldx extension is meant to be found only once. Eventually we register our extension in a legacy manner.
Downgrading to asdf-2.13 circumvents this problem.

[marscher]

It seems one Extension contains all converters and tags, and the other does only contain tags.

[marscher]

Note that I released a quick fix build for conda-forge pinning asdf to <2.14

[marscher]

xref conda-forge/weldx-feedstock#22

[marscher]

@CagtayFabry another interesting observation is that on asdf-2.13 the legacy flag of the extension is False, while in asdf-2.14 it is True. But I cannot spot this change in upstream extension handling... Note that even asdf's extension is a legacy on 2.14

Its weird

[CagtayFabry]

@CagtayFabry another interesting observation is that on asdf-2.13 the legacy flag of the extension is False, while in asdf-2.14 it is True. But I cannot spot this change in upstream extension handling... Note that even asdf's extension is a legacy on 2.14

Its weird

that is indeed really weird, I suggest bringing this up in asdf-format/asdf#1254 too and looking for clarification with the asdf devs on what is happening here

I have not followed the 2.14 release in depth so far

[marscher]

It looks like if you have an editable install (which we also do for our Github action pipeline), we get duplicated entry points.

[WilliamJamieson]

I think ASDF (thanks @braingram) may have fixed this bug in asdf-format/asdf#1260. Can you confirm that this resolves your bug? If so we will do a bugfix release ASAP for you.

[CagtayFabry]

I think ASDF (thanks @braingram) may have fixed this bug in asdf-format/asdf#1260. Can you confirm that this resolves your bug? If so we will do a bugfix release ASAP for you.

We will look into it, thank you for the heads up! @WilliamJamieson 🚀

[marscher]

@WilliamJamieson Thanks for providing this fix. It works like expected!

[marscher]

fixed upstream by asdf-format/asdf#1260