-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.9 archives with group extras not importable on aiida v1.4.2 #4560
Comments
As discussed with @chrisjsewell , this will be fixed by bumping the export file format to v0.10 (with a migration that does nothing). |
Just as a final clarification: As long as the groups exported do not contain extras, import on aiida v1.4.2 works fine. 7c7,9
< "extras" : {},
---
> "extras" : {
> "t" : 0
> }, |
To clarify even further, it is due to the lack of these lines in 1.4.2: aiida-core/aiida/tools/importexport/dbimport/utils.py Lines 192 to 194 in def9a03
|
Just for my understanding, the export file is importable on |
yes.
No. We will bump the export file format instead, i.e. export files with groups that contained extras, created from the aiida-core |
Describe the bug
subset.aiida
is an export file created with the currentdevelop
branch (and includes group extras).Steps to reproduce
aiida-core
1.4.2https://www.dropbox.com/s/0hm1y89d9go3533/subset_1.aiida?dl=1 -O subset.aiida
verdi import subset.aiida
Note: The export file was created with a group containing extras.
I've created another export file that contains all the nodes of the group but not the group itself.
This export file imports fine on aiida 1.4.2.
The text was updated successfully, but these errors were encountered: