Update problem-builder dependency.

[itsjeyd]

This PR pulls in changes from the following constituent PRs (newest first):

• Remove migration that extends course_id column open-craft/problem-builder#133 (Remove migration that extends course_id column)
• Implement Completion XBlock open-craft/problem-builder#132 (Implement Completion XBlock)
• Extend course_id field to 255 characters. open-craft/problem-builder#130 (Extend course_id field to 255 characters)
• 2.6.2 Instructor Tool uses the Course Blocks REST API open-craft/problem-builder#129 (Instructor Tool uses the Course Blocks REST API)
• Uses the same import path for instructor_task.models as edxapp open-craft/problem-builder#128 (Uses the same import path for instructor_task.models as edxapp)
• Bump version to 2.6.0 open-craft/problem-builder#127 (Bump version to 2.6.0)
• Accessibility updates open-craft/problem-builder#125 (Accessibility updates)
• Handle unresolvable anonymous ids gracefully. open-craft/problem-builder#124 (Handle unresolvable anonymous ids gracefully)
• Remove "Message (Assessment Review)" from Problem Builder in Studio open-craft/problem-builder#122 (Remove "Message (Assessment Review)" from Problem Builder in Studio)
• Update master with changes from edx-release open-craft/problem-builder#123 (Update master with changes from edx-release)
• Update xblock-utils to v1.0.3. open-craft/problem-builder#120 (Update xblock-utils to v1.0.3)

cf. OC-2086

Reviewers

• @mtyaka
• @bradenmacdonald

[mtyaka]

@itsjeyd I think we will have to skip the changes from open-craft/problem-builder#130. It includes a migration that is going to be removed (not reverted!) in open-craft/problem-builder#131.

Since I am not sure when open-craft/problem-builder#131 is getting merged, I think we should open a separate PR that only removes the migration file, and merge it to master before bumping the version number here. I'll prepare that PR now.

[itsjeyd]

@mtyaka I see, thanks for the info. Ping me when that PR is ready, I can review it.

The build for this just failed with "Action failed: bundle install", which seems unrelated to the changes introduced here. Do you know what might be causing that failure by any chance?

[mtyaka]

@itsjeyd PR is here: open-craft/problem-builder#133

The build error indicates that bundler was not found on the VM, which is strange. Maybe it was just a random/temporary CircleCI problem. I restarted the build to see.

[itsjeyd]

@mtyaka I had a look, open-craft/problem-builder#133 looks good to me. Let me know if there's anything I should do to test that PR manually?

[mtyaka]

@itsjeyd The Problem Builder PR is merged.

It looks like bundler is no longer installed by default on CircleCI: https://discuss.circleci.com/t/bundle-command-not-found/3783

It looks like everybody's simply been merging broken builds since August 😕 https://github.com/edx-solutions/edx-platform/pulls?q=is%3Apr+is%3Aclosed

[itsjeyd]

Rebased from de5813f15e41fb4633d2b2e1c852174fe74a8ff7 (to pull in changes from open-craft/problem-builder#133).

[itsjeyd]

@mtyaka I updated the commit hash to point to updated master, and updated the PR description to include open-craft/problem-builder#133.

And thanks for looking into the bundler issue. Fixing it is out of scope here, then.

[itsjeyd]

@mtyaka If you're happy with the updates, can I get a thumbs-up from you please? :)

[mtyaka]

👍

If you have some extra time, it would be interesting to see if adding - gem install bunder right above the bundle install line fixes the build issues.

• I tested this: Completion block from Implement Completion XBlock open-craft/problem-builder#132
• I read through the code
• I checked for accessibility issues
• Includes documentation

[bradenmacdonald]

@mtyaka Yep, see #754 . Unfortunately there are several other build issues which are still unresolved. I'm not sure who's responsible for maintaining CI builds on this fork at the moment; we might also only care about the Eucalyptus builds.

[bradenmacdonald]

👍

• I don't have a dogwood solutions devstack set up at the moment, so will rely on your existing testing.
• I read through the code
• I checked for accessibility issues
• Includes documentation

Normally we wouldn't merge a red build, but we can do so now until we've determined how the current problem will be resolved. I have asked edX.

[itsjeyd]

Thanks @mtyaka and @bradenmacdonald, merging now.