Closed BbrSofiane closed 3 years ago
Acknowledging this one as well. Will check if somebody on our team can take a look.
@BbrSofiane, Thanks for reporting the issue. Similar to #42, this xblock is only known to work till Ginkgo
. We are yet to find out its compatibility with Juniper
and later releases.
@shimulch fair enough. Are there any plans to make it compatible with Juniper and/or Koa?
Just some context here, based on what I'm seeing in the exception:
18000 is the default LMS port. Is the LMS running? If it is and you're getting this error, this might be due to the differences between the docker devstack and the vagrant box devstack of Ginkgo yore. On the vagrant devstack, all of the services ran from one VM. With the docker devstack, the containers have their own network and communicate with each other via DNS-style names. localhost
might not work there since the studio container is a different one and I'm not sure they share ports via localhost, too.
However my biggest suspicion is that the LMS isn't running since the tracebacks don't mention any code within the XBlock itself, only internal platform code. If that's not the case then it must be that this XBlock is accessing studio code that is rarely used within other XBlocks and so hasn't been made aware within the devstack of the new arrangements. Or that the traceback is missing something important.
Either way, I hope that helps you diagnose the issue. Unfortunately we don't have any active plans to port this XBlock forward. We'd be happy to accept pull requests for it, and in the future we upgrade it if one of our clients decides to use it with an upgraded version.
@Kelketek thanks for the update.
The LMS was running when I tried on devstack. Could it be that the edx-rest-api-client needs to be updated to 5.2.1? I'll dig into it and I'll post here if I get anywhere.
@BbrSofiane This block should work on Juniper, however it is designed for the solutions fork of the edx-platform and will not work without modification on the regular version. It should be possible to disable the features that depend on the solutions fork, or find alternative APIs that work on the standard edX version.
We'd be happy to accept PRs for the same.
Closing this issue since we don't have any plans to upgrade compatibility at this time. As mentioned, we'd be happy to review a PR if one comes in. Thanks, all!
Following my issues with issue#42, I tried the Xblock on a devstack instance of Koa and I got a different error.
Are the two issues related?