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

[SE-4235] Add missing parameter processors code #150

Conversation

pkulkark
Copy link
Contributor

@pkulkark pkulkark commented Mar 24, 2021

Somewhere between versions 2.0.0 and 2.1.0, the code to handle external parameter processors was dropped. This PR adds it back. Without this, external processors that are specified in the parameter processors settings is not called.

Jira Tickets: OSPR-5686

Sandbox URL: TBD

Testing Instructions:

  1. Install this branch on your xblock runtime environment (for example xblock-sdk).
  2. Test the parameter processors from tahoe-lti as per the test instructions provided
  3. Verify that the external parameter processors are being called correctly.

Reviewers

@openedx-webhooks openedx-webhooks added needs triage open-source-contribution PR author is not from Axim or 2U labels Mar 24, 2021
@openedx-webhooks
Copy link

Thanks for the pull request, @pkulkark! I've created OSPR-5686 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket:

  • supporting documentation
  • Open edX discussion forum threads
  • timeline information ("this must be merged by XX date", and why that is)
  • partner information ("this is a course on edx.org")
  • any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

@coveralls
Copy link

coveralls commented Mar 24, 2021

Coverage Status

Coverage remained the same at 0.0% when pulling 1926299 on open-craft:pooja/fix-parameter-processor-logic into a5ca2cd on edx:master.

@pkulkark pkulkark force-pushed the pooja/fix-parameter-processor-logic branch from db253da to 3c1a549 Compare March 24, 2021 11:24
@natabene
Copy link
Contributor

@pkulkark Thank you for your contribution. Please let me know once it is ready for our review.

@openedx-webhooks openedx-webhooks added waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. and removed needs triage labels Mar 24, 2021
@pkulkark
Copy link
Contributor Author

@natabene This is ready for edX's review.

@openedx-webhooks openedx-webhooks added engineering review awaiting prioritization and removed waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. engineering review labels Mar 26, 2021
Copy link
Contributor

@giovannicimolin giovannicimolin left a comment

Choose a reason for hiding this comment

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

@pkulkark @gabor-boros I left some comments in the code :)

lti_consumer/lti_1p1/consumer.py Outdated Show resolved Hide resolved
lti_consumer/lti_1p1/consumer.py Outdated Show resolved Hide resolved
@pkulkark
Copy link
Contributor Author

Thanks @giovannicimolin. I've made the changes as per your suggestions. Could you take a look and let me know if it looks good?

@giovannicimolin
Copy link
Contributor

@pkulkark Code changes look good, were you able to test these changes and make sure they work as expected?

@pkulkark
Copy link
Contributor Author

@giovannicimolin Yup, I tested it on this sandbox. Everything works as expected.

Copy link
Contributor

@giovannicimolin giovannicimolin left a comment

Choose a reason for hiding this comment

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

👍

  • I tested this:
  1. I checked the sandbox instance using the staff user.
  2. Checked data from additional parameter processors were passed to the LTI tool.
  • I read through the code
  • I checked for accessibility issues NA
  • Includes documentation NA (bugfix)

@pkulkark Thanks for the fix, this was missed when implementing LTI 1.1 support outside XBlocks for the Discussions epic.

@nedbat
Copy link
Contributor

nedbat commented Jun 11, 2021

@pkulkark Is this ready for a final review?

@pkulkark
Copy link
Contributor Author

@nedbat Yes, this is good for a final review.

lti_consumer/lti_xblock.py Outdated Show resolved Hide resolved
lti_consumer/lti_1p1/consumer.py Outdated Show resolved Hide resolved
@giovannicimolin
Copy link
Contributor

@pkulkark I just realized that squash & merge is not enabled for this repo. Can you squash your commits down to a single one following OEP-51?

I can merge after that.

This Adds back the parameter processors code logic
that was missed in a recent refactor.
@pkulkark pkulkark force-pushed the pooja/fix-parameter-processor-logic branch from ed0b23f to 1926299 Compare August 6, 2021 13:11
@giovannicimolin
Copy link
Contributor

@sarina @nedbat Merging this as all comments have been addressed.

@giovannicimolin giovannicimolin merged commit 41d9dd8 into openedx:master Aug 6, 2021
@giovannicimolin giovannicimolin deleted the pooja/fix-parameter-processor-logic branch August 6, 2021 13:16
@shimulch shimulch restored the pooja/fix-parameter-processor-logic branch August 7, 2021 12:41
@shimulch shimulch deleted the pooja/fix-parameter-processor-logic branch August 7, 2021 13:01
pkulkark added a commit to open-craft/edx-platform that referenced this pull request Aug 9, 2021
This PR updates the lti-consumer-xblock version
to a new commit that contains the backported fix
from openedx/xblock-lti-consumer#150
pkulkark added a commit to open-craft/edx-platform that referenced this pull request Aug 9, 2021
This PR updates the lti-consumer-xblock version
to a new commit that contains the backported fix
from openedx/xblock-lti-consumer#150
@louis-s-29
Copy link

@pkulkark @giovannicimolin - Hi, currently testing out the new xblock-lti-consumer 3.0.3 and tahoe-lti.

Per the "how to test" instructions of tahoe-lti, I was wondering if this PR + Tahoe-lti will work only for Lti1.1 or also Lti1.3?

@pkulkark
Copy link
Contributor Author

@louis-s-29 Tahoe-lti only supports LTI 1.1 as far as I know.

@giovannicimolin
Copy link
Contributor

@louis-s-29 Parameter processors are currently not implemented in LTI 1.3, but they can be plugged in the LTI 1.3 launch handler along with the custom parameter support.

Upon a quick check, the parameter processor code seems to be generic enough so that it isn't too complex to add support for on LTI 1.3. If you are going to work on adding support, let me know, I can help/guide you through the implementation process.

nizarmah added a commit to open-craft/edx-platform that referenced this pull request Sep 16, 2021
The previous lti-consumer-xblock commit hash was pointing to a code drift branch which was backporting openedx/xblock-lti-consumer#150 to tag `2.4.0`

Unfortunately, `config_id` duplicate errors started showing for one of the clients. Accordingly, we had to update the xblock to the latest version which inculded that fix and still supported koa (`2.10.1`).

However, openedx/xblock-lti-consumer#150 was not merged until tag `3.0.3`. Thefore, we created a custom tag, `2.10.1-opencraft` which includes the backported change on top of tag `2.10.1`
nizarmah added a commit to open-craft/edx-platform that referenced this pull request Sep 16, 2021
The previous lti-consumer-xblock commit hash was pointing to a code drift branch which was backporting openedx/xblock-lti-consumer#150 to tag `2.4.0`

Unfortunately, `config_id` duplicate errors started showing for one of the clients. Accordingly, we had to update the xblock to the latest version which inculded that fix and still supported koa (`2.10.1`).

However, openedx/xblock-lti-consumer#150 was not merged until tag `3.0.3`. Thefore, we created a custom tag, `2.10.1-opencraft` which includes the backported change on top of tag `2.10.1`
nizarmah added a commit to open-craft/edx-platform that referenced this pull request Sep 16, 2021
The previous lti-consumer-xblock commit hash was pointing to a code drift branch which was backporting openedx/xblock-lti-consumer#150 to tag `2.4.0`

Unfortunately, `config_id` duplicate errors started showing for one of the clients. Accordingly, we had to update the xblock to the latest version which inculded that fix and still supported koa (`2.10.1`).

However, openedx/xblock-lti-consumer#150 was not merged until tag `3.0.3`. Thefore, we created a custom tag, `2.10.1-opencraft` which includes the backported change on top of tag `2.10.1`

(cherry picked from commit 85884f3)
xitij2000 pushed a commit to open-craft/edx-platform that referenced this pull request Nov 22, 2021
This PR updates the lti-consumer-xblock version
to a new commit that contains the backported fix
from openedx/xblock-lti-consumer#150

(cherry picked from commit 9612bad)
xitij2000 pushed a commit to open-craft/edx-platform that referenced this pull request Nov 22, 2021
The previous lti-consumer-xblock commit hash was pointing to a code drift branch which was backporting openedx/xblock-lti-consumer#150 to tag `2.4.0`

Unfortunately, `config_id` duplicate errors started showing for one of the clients. Accordingly, we had to update the xblock to the latest version which inculded that fix and still supported koa (`2.10.1`).

However, openedx/xblock-lti-consumer#150 was not merged until tag `3.0.3`. Thefore, we created a custom tag, `2.10.1-opencraft` which includes the backported change on top of tag `2.10.1`

(cherry picked from commit 85884f3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants