Skip to content
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

fix: create CEA object when enrolling using a license flow #18

Open
wants to merge 5 commits into
base: 0x29a/bb8626/enroll-enterprise-learners-in-invite-only-courses
Choose a base branch
from

Conversation

0x29a
Copy link
Member

@0x29a 0x29a commented Apr 19, 2024

This is a port of #19.

@@ -2419,7 +2420,4 @@ def ensure_course_enrollment_is_allowed(course_id, email, enrollment_api_client)

course_details = enrollment_api_client.get_course_details(course_id)
if course_details["invite_only"]:
CourseEnrollmentAllowed.objects.update_or_create(
Copy link
Member Author

@0x29a 0x29a Apr 19, 2024

Choose a reason for hiding this comment

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

I tried to re-use this helper as is, but it was locking a DB row causing enrollment to fail here, because the LMS was trying to modify the locked row. That's why I had to use this API to create CEA in a separate transaction. If this approach is viable, we'll have to backport this endpoint to Palm.

Copy link
Member

Choose a reason for hiding this comment

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

@0x29a It's surprising that we haven't run into this race condition before. Any idea why it might be occuring now?

Irrespective of the reasons, I think using the API is a fine approach to take, given that we get the course details in the previous statement using the API and not an import. It looks like the enrollment_allowed is a recent API addition (added 6/7 months ago). We would have probably used it if it existed earlier, as this allows creating CEA objects from other services like an admin MFE as well.

Copy link
Member Author

@0x29a 0x29a Apr 22, 2024

Choose a reason for hiding this comment

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

Thanks for checking this, @tecoholic.

Any idea why it might be occuring now?

This was bothering me as well, but I was unable to figure this out back then. It turns out that the view modified in openedx#1813 is not atomic. And the view modified in #14 doesn't send any internal HTTP requests in fact, so CEA objects are manipulated within a single transaction. In this PR we modify a view that is both atomic and sends a request to another atomic view, and they both try to modify CEA.

We can also change View with NonAtomicView here, and this will simplify things a bit, but I'm not sure how risky this is.

@0x29a 0x29a force-pushed the 0x29a/bb8808/cea-license-flow branch from 5927941 to 2381ecf Compare April 22, 2024 15:18
@0x29a 0x29a force-pushed the 0x29a/bb8808/cea-license-flow branch from 2381ecf to 7d010cb Compare April 23, 2024 08:46
@0x29a 0x29a marked this pull request as ready for review April 23, 2024 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants