You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New ASE version 3.23 was released couple weeks ago and represents a big jump since the last version that was released at the end of 2021. One of our unit tests started failing since it hardcodes a binary output from _StructureDataBaseViewer._prepare_payload which in turn relies on ase.Atoms.write.
In #611 I pinned the ase version to unblock CI. We need to verify that the differences are insignificant, and generally verify that the new ASE version did not break anything else that is not covered by tests.
The text was updated successfully, but these errors were encountered:
Recently released version ase 3.23 broke one of our tests that hardcodes
a binary output from ase.Atoms.write. I opened aiidalab#612 with more details.
New ASE version 3.23 was released couple weeks ago and represents a big jump since the last version that was released at the end of 2021. One of our unit tests started failing since it hardcodes a binary output from
_StructureDataBaseViewer._prepare_payload
which in turn relies onase.Atoms.write
.aiidalab-widgets-base/tests/test_viewers.py
Line 79 in df106c5
aiidalab-widgets-base/aiidalab_widgets_base/viewers.py
Line 1093 in df106c5
In #611 I pinned the ase version to unblock CI. We need to verify that the differences are insignificant, and generally verify that the new ASE version did not break anything else that is not covered by tests.
The text was updated successfully, but these errors were encountered: