fix: skip block indexing if it raises an error while loading - #35139
Conversation
|
Thanks for the pull request, @rpenido! What's next?Please work through the following steps to get your changes ready for engineering review: 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. 🔘 Let us know that your PR is ready for review:Who will review my changes?This repository is currently maintained by Where can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:
When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
6f0680e to
e41db7f
Compare
pomegranited
left a comment
There was a problem hiding this comment.
@rpenido Thank you for finding this issue and fixing it!
I've proposed a slightly different implementation -- please let me know what do you think.
Could you also add a brief test to openedx/core/djangoapps/content/search/tests/test_api.py which demonstrates the issue, so we're sure it stays fixed?
Co-authored-by: Jillian <jill@opencraft.com>
Tests here: a5fa737 |
pomegranited
left a comment
There was a problem hiding this comment.
👍 Thanks @rpenido !
- I tested this by running
./manage.py cms reindex_studio --experimentalon a course containing an ORA problem. Noted indexing the ORA was skipped, but the rest of the library was indexed as expected. - I read through the code
-
I checked for accessibility issuesN/A -
Includes documentationN/A -
User-facing strings are extracted for translationN/A
|
@rpenido 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
|
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
|
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
This PR handles errors while updating the document for a library component, so if we get an error with one component, it does not prevent other components from the library from being indexed.
More info
While indexing a library with an
openassessmentblock, the following error is thrown:Every assessment must contain a "title" element.This prevented the whole library with anopenassessmentblock from being indexed.