Skip to content

Delete preprocess data #1042

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

Merged
merged 6 commits into from
Apr 8, 2015

Conversation

antgonza
Copy link
Member

@antgonza antgonza commented Apr 7, 2015

No description provided.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 79.07% when pulling f9c0ca1 on antgonza:delete-preprocess-data into 2199bdd on biocore:master.

preprocessed data EBI and VAMPS submission is not in a valid state
['not submitted', 'failed']
QiitaDBError
If the preprocessed data has (meta)analyses
Copy link
Contributor

Choose a reason for hiding this comment

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

This is not accurate: If the preprocessed data has been processed

@josenavas
Copy link
Contributor

Just a documentation comment. Once it is fixed, 👍

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 79.07% when pulling 1bb2c91 on antgonza:delete-preprocess-data into 2199bdd on biocore:master.

@ElDeveloper
Copy link
Contributor

I tried deleting a Preprocessed data object that had already generated a processed data object and I got the following error:

Couldn't remove preprocessed data 111: Illegal operation due to EBI submission status ('false') or VAMPS submission status ('not submitted')

And I honestly don't understand what that means.

ppd = cls(ppd_id)
if ppd.status != 'sandbox':
raise QiitaDBStatusError(
"Illegal operation on non sandbox preprocessed data")
Copy link
Contributor

Choose a reason for hiding this comment

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

Since these messages (832 and 836) are likely to be seen by users on the GUI, do you think you could rephrase them?

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the changes. I think it should be "sandboxed" not "sandbox".

@squirrelo
Copy link
Contributor

Couple of comments.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.06%) to 79.06% when pulling 3974fb7 on antgonza:delete-preprocess-data into 2199bdd on biocore:master.

@squirrelo squirrelo added this to the Alpha 0.1 milestone Apr 7, 2015
with self.assertRaises(QiitaDBStatusError):
PreprocessedData.delete(1)

def test_delete_advance(self):
Copy link
Contributor

Choose a reason for hiding this comment

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

advance -> advanced

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 79.04% when pulling a74fd0f on antgonza:delete-preprocess-data into 2199bdd on biocore:master.

@ElDeveloper
Copy link
Contributor

Testing on my system.

@ElDeveloper
Copy link
Contributor

Looks good from my testing the only outstanding thing is that, it gave me the following message even though I never submitted to EBI:

screen shot 2015-04-08 at 10 38 19 am

I attach the whole screenshot, because it may be that the EBI status it has is messing with the check? Not sure why is this the case though.

@ElDeveloper
Copy link
Contributor

To the rest of the qiita devs, the reason why this is failing for some studies is because 'false' is not a valid status for the EBI submission. The load_preprocessed command is the culprit of this inconsistency as it sets the value to true or false. AFAIK, false and true are not accepted statuses, but if I'm wrong, then this PR should accept true/false as a valid status, can someone else confirm?

ElDeveloper added a commit that referenced this pull request Apr 8, 2015
@ElDeveloper ElDeveloper merged commit f605fd4 into qiita-spots:master Apr 8, 2015
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.

5 participants