Test import with 8.MReV and 8.MechCx about lore HOT 13 CLOSED

@ShawnMilo FYI

After some preliminary examination, it appears that a "AB Experiment" or "Content Cohort" is applied through a combination of a user_partitions section in the policy.json and corresponding group_access attributes on the xblock tags (leaf only). So it shouldn't affect import at all.

However, I'm not sure if the 8.MReV course with "irregularities" mentioned above conforms to this.

from lore.

@amir-qayyum-khan has started to look into this from the xbundle end of things.

See mitodl/xbundle#33 and mitodl/xbundle#34

from lore.

@pdpinch @ShawnMilo @carsongee

On uploading both course on Lore i get exception
https://gist.github.com/amir-qayyum-khan/a3e01160b35392450ff0

**On going back I see course

from lore.

I have not been able to duplicate the error at all. If you delete your database again and undo any changes you did with makemigrations, does it still happen?

I don't see the constraint being created in the migration file.

from lore.

This is caused by #80. Decision needed.

from lore.

@ShawnMilo
I am still getting this issue. FYI What I did

1. Rebase Lore
2. Reset project using git reset --hard mit_origin/master
3. Stop docker docker stop lore_db_1
4. Reset database docker rm lore_db_1
5. docker-compose up

Still getting same issue,

from lore.

Amir, try the following:

git clean -xdf
boot2docker destroy
boot2docker init --memory=4096
boot2docker up
eval $(boot2docker shellinit)
docker-compose up

The boot2docker destroy may be the key step for the clean up you need.

On Jun 4, 2015, at 3:39 AM, Amir Qayyum Khan [email protected] wrote:

@ShawnMilo
I am still getting this issue. FYI What I did

1. Rebase Lore
2. Reset project using git reset --hard mit_origin/master
3. Stop docker docker stop lore_db_1
4. Reset database docker rm lore_db_1
5. docker-compose up

Still getting same issue,

—
Reply to this email directly or view it on GitHub.

from lore.

ok Peter, let me do it

Thanks

from lore.

@pdpinch @ShawnMilo fixed exception by running these command.

git clean -xdf
boot2docker destroy
boot2docker init --memory=4096
boot2docker up
eval $(boot2docker shellinit)
docker stop lore_db_1
docker rm lore_db_1
docker-compose up

By the way now it is showing me imported course (edX-Archive-8.MReVx-2T2014) with 163 pages? Is this behaviour OK?

from lore.

@amir-qayyum-khan, yeah, that result looks good. It was breaking due to the extra makemigrations step you ran. You shouldn't have to do that unless you change the content of a models.py yourself.

from lore.

thanks @ShawnMilo ,

from lore.

Is this issue ready to be closed?

from lore.

@ShawnMilo there's still an open issue in xbundle, mitodl/xbundle#34 -- but on a 2nd look I realize it's in the xml -> course conversion, which isn't a blocker (as yet) for LORE.

We'll take another look at this later when we're working on export.

from lore.