You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[DEPR]: MATLAB-specific handling in edx-platform #192
Our system currently has special handling for MATLAB problems via an old integration through xqueue that isn't really supported any longer, and appears to be broken today. Since this integration should now be done via LTI, we can remove:
Associated JavaScript, CSS, template, and text fixture code.
It may be that removing this would adversely affect grades, in which case it may be better to leave behind a bare shell that does nothing but acting as a dumb placeholder for legacy content scoring purposes. More investigation needed.
Scattered special-case hanlding for MATLAB in coderesponse and xqueue.
This would eliminate the "MATLAB API Key" advanced course setting UI in Studio:
And the equivalent one at the ProblemBlock level:
Effect on old course content:
Student scores must be preserved.
It is not necessary to be able to render the original student submission or detailed response information.
Proposal Date
10 May 2023
Target Ticket Acceptance Date
24 May 2023
Earliest Open edX Named Release Without This Functionality
Quince.
Since it is not currently in a working state, there's no need to offer an extra release for migration.
Rationale
The current endpoint does not hook up to a working external service, and is not useful.
LTI is already the accepted way to integrate MATLAB content.
It will slightly simplify ProblemBlock and the LMS's XBlock runtime to remove this.
Just to be clear @ormsbee , would this DEPR also cover the Matlab API Key field in the problem editor, thus clearing up 2U's T&L team to remove it from the new React-based problem editor? (cc @jristau1984)
@kdmccormick: Yes, but to be clear: I don't think that work needs to wait for this DEPR to be accepted, since it's more of a bookkeeping DEPR–i.e. I'm pretty sure that it's been broken for years, so immediately removing the view of the broken thing doesn't negatively impact users. I'm leaving it open for a couple of weeks of comment Just In Case, and if people want to add any more information.
@dianakhuang: No, its not. I removed it from the settings interface so that people wouldn't see it anymore, but I didn't remove the underlying code because a lot of capa's xqueue interface code uses MATLAB for its tests. So if I removed MATLAB, I'd have to re-implement those tests for xqueue, which didn't seem worthwhile since xqueue itself was on the chopping block. I'm now thinking that this DEPR will be executed when the xqueue code in edx-platform finally dies as part of #286
Given that the old implementation doesn't work, this can be considered unblocked for removal. We don't need to work on it separately if the removal of all the xqueue related code is close to landing but this can be picked up for removal sooner if that's gonna be a while.
This is safe to be removed at any time, but it's less work to remove it after XQueue compatibility is removed. So, we're marking this as blocked on #286
Activity
[-][DEPR]: Matlab API Key[/-][+][DEPR]: Matlab-specific handling in edx-platform[/+][-][DEPR]: Matlab-specific handling in edx-platform[/-][+][DEPR]: MATLAB-specific handling in edx-platform[/+]ormsbee commentedon May 10, 2023
There was a slack thread about this as well.
kdmccormick commentedon May 11, 2023
Just to be clear @ormsbee , would this DEPR also cover the Matlab API Key field in the problem editor, thus clearing up 2U's T&L team to remove it from the new React-based problem editor? (cc @jristau1984)
ormsbee commentedon May 11, 2023
@kdmccormick: Yes, but to be clear: I don't think that work needs to wait for this DEPR to be accepted, since it's more of a bookkeeping DEPR–i.e. I'm pretty sure that it's been broken for years, so immediately removing the view of the broken thing doesn't negatively impact users. I'm leaving it open for a couple of weeks of comment Just In Case, and if people want to add any more information.
ormsbee commentedon May 24, 2023
This DEPR was announced here: https://discuss.openedx.org/t/deprecation-removal-matlab-specific-handling-in-edx-platform/10069/5
feat!: remove MATLAB support
feat!: remove Matlab key from Studio Problem settings
feat!: remove Matlab key from Studio Problem settings
2 remaining items
ormsbee commentedon Jan 25, 2025
@dianakhuang: No, its not. I removed it from the settings interface so that people wouldn't see it anymore, but I didn't remove the underlying code because a lot of capa's xqueue interface code uses MATLAB for its tests. So if I removed MATLAB, I'd have to re-implement those tests for xqueue, which didn't seem worthwhile since xqueue itself was on the chopping block. I'm now thinking that this DEPR will be executed when the xqueue code in edx-platform finally dies as part of #286
dianakhuang commentedon Jun 26, 2025
Blocked on the XQueue ticket: #286
feanil commentedon Sep 4, 2025
Given that the old implementation doesn't work, this can be considered unblocked for removal. We don't need to work on it separately if the removal of all the xqueue related code is close to landing but this can be picked up for removal sooner if that's gonna be a while.
ormsbee commentedon Sep 8, 2025
@feanil: The FC work for xqueue removal was restarted this morning, so I'd ask that this still wait behind that work.
feanil commentedon Sep 15, 2025
Ok, I'll move this back to
Plan Acceptedfor now then since the XQueue work is still in progress.dianakhuang commentedon Jun 25, 2026
The XQueue work is actively in progress. Will move review date to match review date of XQueue.
kdmccormick commentedon Nov 12, 2026
This is safe to be removed at any time, but it's less work to remove it after XQueue compatibility is removed. So, we're marking this as blocked on #286