Skip to content

Update export schema version and temporarily disable export#2341

Merged
sphuber merged 1 commit into
aiidateam:provenance_redesignfrom
sphuber:fix_2340_disable_export_and_up_schema_version
Dec 12, 2018
Merged

Update export schema version and temporarily disable export#2341
sphuber merged 1 commit into
aiidateam:provenance_redesignfrom
sphuber:fix_2340_disable_export_and_up_schema_version

Conversation

@sphuber
Copy link
Copy Markdown
Contributor

@sphuber sphuber commented Dec 11, 2018

Fixes #2340

The migration after the provenance redesign has been merged into
provenance_redesign. To avoid people from importing "dirty" export
files into a cleanly migrated database, the export schema version is
upped. Additionally, creating new export archives with the latest
version is disabled, until the export procedure has been verified to
abide by the new rules in place after the provenance redesign.

Comment thread aiida/cmdline/commands/cmd_export.py Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ehm... won't issue #2340 be closed when merging this PR?
I am confused...

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By the way: fine to be so explicit about it but I was under the impression that provenance_redesign was anyhow not meant to be used for any kind of production runs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are absolutely right, it should reference #2342
Regarding the disabling of the export. It is true that provenance_design is not expected to work, however, we want to merge it soon and it is not clear if #2342 will then have already been addressed. To prevent incorrect archives from being accidentally created, I think it is better to disable it. Still we should fix it as soon as possible of course

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have corrected the issue number reference. But I noticed that I forgot to skip tests that either rely on verdi export create or on fixture archives that are still v0.3. Not ideal, but I think it is still better than people accidentally creating broken archives

The migration after the provenance redesign has been merged into
`provenance_redesign`. To avoid people from importing "dirty" export
files into a cleanly migrated database, the export schema version is
upped. Additionally, creating new export archives with the latest
version is disabled, until the export procedure has been verified to
abide by the new rules in place after the provenance redesign.
@sphuber sphuber force-pushed the fix_2340_disable_export_and_up_schema_version branch from fae638c to 17a96c3 Compare December 11, 2018 18:28
@coveralls
Copy link
Copy Markdown

coveralls commented Dec 11, 2018

Coverage Status

Coverage decreased (-1.0%) to 68.008% when pulling 17a96c3 on sphuber:fix_2340_disable_export_and_up_schema_version into 42bc788 on aiidateam:provenance_redesign.

@ltalirz
Copy link
Copy Markdown
Member

ltalirz commented Dec 11, 2018

@giovannipizzi Can you please check and approve?
I don't feel qualified to make this decision about disabling exports in develop...

@sphuber sphuber merged commit 1673ec2 into aiidateam:provenance_redesign Dec 12, 2018
@sphuber sphuber deleted the fix_2340_disable_export_and_up_schema_version branch December 12, 2018 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants