...
When navigating to http://localhost:18000/ and encountering OSError
...
Potential Fix:
Making sure docker state is completely fresh
make dev.stop
make dev.remove-containers
docker system prune -a
picked Ydocker images -a
(to see if they're all gone)docker ps -a
(to see if all containers are gone)docker volume rm $(docker volume ls)
(to remove all volumes)docker volume ls
(to see if all volumes are gone)
At this point docker should be in a completely fresh state!
...
Code Block |
---|
note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. make: * [requirements] Error 1 |
To fix:
Pull up the workspace in your code editor and search for PyYAML. From there, change the version to 5.3.1 and save all files.
...
Code Block |
---|
Request Method: GET Request URL: http://localhost:18000/ Django Version: 3.2.20 Exception Type: OSError Exception Value: Error reading /edx/var/edxapp/staticfiles/webpack-stats.json. Are you sure webpack has generated the file and the path is correct? |
Potential fix:
Rerun all of the following commands
make requirements
SHALLOW_CLONE=1 make dev.clone.https
make dev.pull.large-and-slow
make dev.provision
makedev.up.large-and-slow
...
Error when navigating to the login or registration pages:
registration: http://localhost:18000/register?next=%2F
...
Code Block |
---|
VM2013:384 Uncaught ReferenceError: showRegisterLinks is not defined
at eval (eval at _.template (underscore.js:1454:20), <anonymous>:384:2)
at template (underscore.js:1461:21)
at html-utils.js:169:55
at child.buildForm (FormView.js:94:59)
at child.initialize (FormView.js:43:22)
at Backbone.View (backbone.js:1310:21)
at child [as constructor] (backbone.js:2070:41)
at new child (backbone.js:2070:41)
at child.login (AccessView.js:153:42)
at child.loadForm (AccessView.js:141:17) |
We believe an old JavaScript file was being stored/pulled from and that causes this error
Fix:
While on the login page, do a hard refresh (cmd + shift + r)
This clears cache
...