Closed marscher closed 1 year ago
It seems one Extension
contains all converters and tags, and the other does only contain tags.
Note that I released a quick fix build for conda-forge pinning asdf to <2.14
xref conda-forge/weldx-feedstock#22
@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 :hurtrealbad:
@CagtayFabry another interesting observation is that on asdf-2.13 the legacy flag of the extension is
False
, while in asdf-2.14 it isTrue
. But I cannot spot this change in upstream extension handling... Note that even asdf's extension is a legacy on 2.14Its weird :hurtrealbad:
that is indeed really weird, I suggest bringing this up in https://github.com/asdf-format/asdf/issues/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
It looks like if you have an editable install (which we also do for our Github action pipeline), we get duplicated entry points.
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.
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 🚀
@WilliamJamieson Thanks for providing this fix. It works like expected!
fixed upstream by asdf-format/asdf#1260
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.