diff --git a/.bundle/config b/.bundle/config index 23692288..ee5bb423 100644 --- a/.bundle/config +++ b/.bundle/config @@ -1,2 +1,3 @@ --- BUNDLE_PATH: "vendor/bundle" +BUNDLE_FROZEN: "false" diff --git a/Gemfile.lock b/Gemfile.lock index 6b068262..ad1ad4af 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,36 +1,46 @@ GEM remote: https://rubygems.org/ specs: - activesupport (7.0.7) + activesupport (7.1.2) + base64 + bigdecimal concurrent-ruby (~> 1.0, >= 1.0.2) + connection_pool (>= 2.2.5) + drb i18n (>= 1.6, < 2) minitest (>= 5.1) + mutex_m tzinfo (~> 2.0) - addressable (2.8.1) + addressable (2.8.6) public_suffix (>= 2.0.2, < 6.0) + base64 (0.2.0) + bigdecimal (3.1.4) coffee-script (2.4.1) coffee-script-source execjs coffee-script-source (1.11.1) colorator (1.1.0) - commonmarker (0.23.8) + commonmarker (0.23.10) concurrent-ruby (1.2.2) - dnsruby (1.61.9) - simpleidn (~> 0.1) + connection_pool (2.4.1) + dnsruby (1.70.0) + simpleidn (~> 0.2.1) + drb (2.2.0) + ruby2_keywords em-websocket (0.5.3) eventmachine (>= 0.12.9) http_parser.rb (~> 0) ethon (0.16.0) ffi (>= 1.15.0) eventmachine (1.2.7) - eventmachine (1.2.7-x64-mingw32) - execjs (2.8.1) - faraday (2.7.4) + execjs (2.9.1) + faraday (2.7.12) + base64 faraday-net_http (>= 2.0, < 3.1) ruby2_keywords (>= 0.0.4) faraday-net_http (3.0.2) - ffi (1.15.5) - ffi (1.15.5-x64-mingw32) + ffi (1.16.3) + ffi (1.16.3-x64-mingw-ucrt) forwardable-extended (2.6.0) gemoji (3.0.1) github-pages (228) @@ -215,30 +225,31 @@ GEM rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.3.6) - mini_portile2 (2.8.1) minima (2.5.1) jekyll (>= 3.5, < 5.0) jekyll-feed (~> 0.9) jekyll-seo-tag (~> 2.1) - minitest (5.19.0) - nokogiri (1.14.1) - mini_portile2 (~> 2.8.0) + minitest (5.20.0) + mutex_m (0.2.0) + nokogiri (1.15.5-arm64-darwin) racc (~> 1.4) - nokogiri (1.14.1-x64-mingw32) + nokogiri (1.15.5-x64-mingw-ucrt) + racc (~> 1.4) + nokogiri (1.15.5-x86_64-linux) racc (~> 1.4) octokit (4.25.1) faraday (>= 1, < 3) sawyer (~> 0.9) - parallel (1.22.1) + parallel (1.23.0) pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (4.0.7) - racc (1.6.2) + racc (1.7.3) rainbow (3.1.1) rb-fsevent (0.11.2) rb-inotify (0.10.1) ffi (~> 1.0) - rexml (3.2.5) + rexml (3.2.6) rouge (3.26.0) ruby2_keywords (0.0.5) rubyzip (2.3.2) @@ -255,21 +266,22 @@ GEM unf (~> 0.1.4) terminal-table (1.8.0) unicode-display_width (~> 1.1, >= 1.1.1) - typhoeus (1.4.0) + typhoeus (1.4.1) ethon (>= 0.9.0) tzinfo (2.0.6) concurrent-ruby (~> 1.0) unf (0.1.4) unf_ext - unf_ext (0.0.8.2) - unf_ext (0.0.8.2-x64-mingw32) + unf_ext (0.0.9.1) + unf_ext (0.0.9.1-x64-mingw-ucrt) unicode-display_width (1.8.0) webrick (1.8.1) yell (2.2.2) PLATFORMS - ruby - x64-mingw32 + arm64-darwin-20 + x64-mingw-ucrt + x86_64-linux DEPENDENCIES github-pages (= 228) @@ -277,4 +289,4 @@ DEPENDENCIES webrick (~> 1.8) BUNDLED WITH - 2.2.24 + 2.4.21 diff --git a/_docs/developer/development_instructions/index.md b/_docs/developer/development_instructions/index.md index aad612c5..648356f7 100644 --- a/_docs/developer/development_instructions/index.md +++ b/_docs/developer/development_instructions/index.md @@ -28,7 +28,6 @@ complicated and expensive steps at the bottom of the page._ Please also see [Installation Version Notes](/sysadmin/installation/version_notes) - --- ## Submitty Help - List of Shortcuts @@ -202,41 +201,6 @@ autograding configuration, you'll probably need to: * [Batch Regrade Homeworks](/instructor/batch_regrade_submissions) already submitted to those gradeables. ---- - -## System Clock Testing & Troubleshooting - -* If the VM has a clock skew (incorrect time) - - ``` - sudo service ntp stop - sudo ntpd -gq - sudo service ntp start - ``` - - -* If you need to test time and/or date dependent elements, you can - change it in the vagrant machine so you don't have to wait. To - remove the syncing and set your own time: - - ``` - sudo systemctl disable ntp - timedatectl set-ntp 0 - sudo date -s "-- :: - ``` - - To check the date, helpful to make sure the date and time you set has stuck: - - ``` - date - ``` - - To sync back with the current time: - - ``` - sudo systemctl enable ntp - timedatectl set-ntp 1 - ``` --- @@ -259,12 +223,10 @@ these changes. ``` sudo python3 /usr/local/submitty/GIT_CHECKOUT/Submitty/.setup/update_database.py ``` - - + --- ## Re-Creating All Sample Course Data - * If you've changed the script to create a new course (`create_course.sh`), or the schema for the master database (`submitty_db.sql`), or the schema for the course databases @@ -331,6 +293,8 @@ these changes. work that has been done._ --- +--- + ## Virtual Machine Recovery using Snapshots diff --git a/_docs/developer/development_instructions/sample_data.md b/_docs/developer/development_instructions/sample_data.md index 5615d6aa..7c678926 100644 --- a/_docs/developer/development_instructions/sample_data.md +++ b/_docs/developer/development_instructions/sample_data.md @@ -73,4 +73,3 @@ You may also need to edit test cases in Cypress, Selenium, etc. --- See also: [Re-Creating All Sample Course Data](/developer/development_instructions/index#re-creating-all-sample-course-data) - diff --git a/_docs/developer/development_instructions/troubleshooting.md b/_docs/developer/development_instructions/troubleshooting.md deleted file mode 100644 index 8b2c5e56..00000000 --- a/_docs/developer/development_instructions/troubleshooting.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Troubleshooting -category: Developer > Development Instructions ---- - - ---- - - -## Forwarded Port Already in Use - -* If you see an error similar to: - - ``` - Vagrant cannot forward the specified ports on this VM, since they - would collide with some other application that is already listening - on these ports. The forwarded port to #### is already in use - on the host machine. - ``` - - This means that one or more of the ports requested by vagrant is already in - use by another application running on your computer. - - -* This may happen if you attempt to create multiple Submitty VMs -- - perhaps unintentionally! E.g., if you have multiple directories on - your computer each with a clone/copy of the Submitty repo. It is - necessary to run `vagrant destroy` in each of these - directories/repositories to clean up unwanted VMs. - - The following command can help locate misplaced repositories/VMs: - - ``` - vagrant global-status - ``` - -* If you might have old, forgotten VMs from previous OS versions - hanging around it can be helpful to completely delete the `.vagrant` - folder in your repository. Also check to see if you have multiple - clones or backups of the repository and thus multiple `.vagrant` - folders on your machine. - - -* You can scan to see what processes on your machine are using the - conflicting ports. Depending on your operating system, try these - commands: - - ``` - netstat -anvp tcp | awk 'NR<3 || /LISTEN/' - ``` - - ``` - lsof -i | grep LISTEN - ``` - - Then you can type `kill ` with the `` of the process (if - you confirm you don't need that process). If you don't recognize - the process using the port in question, search to figure out if you - can or should disable it. For example, on MacOS, the AirPlay - Receiver in Control Center is using port 7000, so you may choose to - turn that off. - - -* You can choose to override the default ports and use an alternate - port through an environment variable. The current variables are - `VM_PORT_SITE`, `VM_PORT_WS`, `VM_PORT_DB`, `VM_PORT_SAML`, and - `VM_PORT_SSH`. - - For example, if the conflicting port is the default site port (1511), - and you want to use port 1512 instead: - ``` - VM_PORT_SITE=1512 vagrant up - ``` - - You can alternatively create a `.env` file in the root of your project - with the text `VM_PORT_SITE=1512` (and any other variables separated by - newlines). Note that you will need to install the env plugin beforehand: - ``` - vagrant plugin install vagrant-env - ``` - ---- - - -## Host-Only / Static Networking - -If you are having trouble being able to view the Submitty webpage after a ```vagrant up``` you might need to -modify the interfaces in your VM. To fix this: - -As root modify ```/etc/network/interfaces``` and add: - -``` -# The host-only network interface -auto eth1 -iface eth1 inet static -address 192.168.56.101 -netmask 255.255.255.0 -network 192.168.56.0 -broadcast 192.168.56.255 -``` - -References and useful links: [https://gist.github.com/pjdietz/5768124](https://gist.github.com/pjdietz/5768124) and [http://christophermaier.name/2010/09/01/host-only-networking-with-virtualbox/](http://christophermaier.name/2010/09/01/host-only-networking-with-virtualbox/) diff --git a/_docs/developer/getting_started/vm_install_using_vagrant.md b/_docs/developer/getting_started/vm_install_using_vagrant.md index 3ada54c5..19a0bd54 100644 --- a/_docs/developer/getting_started/vm_install_using_vagrant.md +++ b/_docs/developer/getting_started/vm_install_using_vagrant.md @@ -258,9 +258,7 @@ Below are quick steps to get everything installed and running. If you do not see this message due to an error or the installation has frozen, check out: - * [Installation Troubleshooting](#installation-troubleshooting) - - * [Development Instructions Troubleshooting](/developer/development_instructions/troubleshooting) + * [Installation Troubleshooting](/developer/troubleshooting/installation_troubleshooting) --- @@ -402,84 +400,6 @@ Below are quick steps to get everything installed and running. ``` vagrant up ``` - ---- - -## Installation Troubleshooting - -* If your install becomes stuck on ``SSH auth method: private key`` for more than three minutes, - then what you can do is open Virtual Box, navigate to your VM, and click the green "Show" button. - Having the VM's terminal GUI open can seem to keep it awake for communication. While developing on Submitty, - this "Show" terminal option can sometimes lead to the VM being faster with loads, so it may be worth having the GUI - open even after your vagrant up. - -* If your install seems to randomly freeze during `vagrant up` -with no explanation, then there are a couple of things that may be going wrong: - - *Note: If this happens, it may be worth running a simple `vagrant destroy` before you try to `vagrant up` again. It is possible to repair, but it is usually more effort than it is worth.* - - * First, check to make sure you have a solid internet connection. - Even if the connection is fast, it may experience drop-outs every - once in a while, so it is highly recommended to install it with a wired - connection to the internet. - - * Secondly, check to make sure your computer is not going to - sleep, this can be changed in settings for some systems, or you - can install a program to keep it awake (for example, amphetamine on Mac). - -* If an error is thrown during `vagrant up`, you may need to - uninstall Virtual Box and all virtual machines by typing the - following commands: - - _CAUTION: This should only be done if you do not have any other virtual machines._ - - To remove Virtual Box type: - - ``` - sudo apt-get remove --purge virtualbox - ``` - To remove all virtual machines and configuration files type: - - ``` - sudo rm ~/"VirtualBox VMs" -Rf - sudo rm ~/.config/VirtualBox/ -Rf - ``` - This will delete all virtual machine settings. Then install - the latest version of Virtual Box and vagrant from the links given in step 3 (using Ubuntu Software). - -* If it has been a while since your last `vagrant destroy` and - `vagrant up` you may need to update/upgrade/reinstall the virtual - box, vagrant, and the installed boxes on your - system: - - For example, on Mac: - - ``` - brew reinstall --cask virtualbox - brew reinstall --cask vagrant - vagrant plugin update - vagrant box update - ``` - - If you continue to have errors on Mac with `vagrant up` after - reinstalling virtualbox and vagrant, check "System Preferences" -> - "Security & Privacy". You may need to approve/reapprove - "Allow apps download from". You may also need to restart your computer. - - Similar instructions for other OS. - -* If this error is thrown during `vagrant up` command: - ``` - ubuntu-26.84: E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/gcc-9gcc-9_9.4.0-1ubuntu1-20.84.1_amd64.deb Connection fail [IP: 189.211.241.193] - ``` - then you should use VPN to connect to the internet and then try `vagrant up`.This error usually occurs when you are outside the United States and the connection to the Ubuntu package repository is being blocked or restricted. - - __Note:__ The IP address provided in the error message may vary. - ProtonVPN, which provides free VPN service can be used. You can download from their official website at (https://protonvpn.com). You can also use other VPN services. - - -* See also [Development Instructions Troubleshooting](/developer/development_instructions/troubleshooting) - --- ## Testing with a remote device diff --git a/_docs/developer/getting_started/vm_install_using_vagrant_apple_silicon.md b/_docs/developer/getting_started/vm_install_using_vagrant_apple_silicon.md index 0c13d8e4..8aade5da 100644 --- a/_docs/developer/getting_started/vm_install_using_vagrant_apple_silicon.md +++ b/_docs/developer/getting_started/vm_install_using_vagrant_apple_silicon.md @@ -171,9 +171,7 @@ the installation process. If you do not see this message due to an error or the installation has frozen, check out: - * [Installation Troubleshooting](/developer/getting_started/vm_install_using_vagrant#installation-troubleshooting) - - * [Development Instructions Troubleshooting](/developer/development_instructions/troubleshooting) + * [Installation Troubleshooting](/developer/troubleshooting/installation_troubleshooting) --- diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md new file mode 100644 index 00000000..226de852 --- /dev/null +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -0,0 +1,171 @@ +--- +title: Installation Troubleshooting +category: Developer > Development Troubleshooting +--- + + +* If your install becomes stuck on ``SSH auth method: private key`` for more than three minutes, + then what you can do is open Virtual Box, navigate to your VM, and click the green "Show" button. + Having the VM's terminal GUI open can seem to keep it awake for communication. While developing on Submitty, + this "Show" terminal option can sometimes lead to the VM being faster with loads, so it may be worth having the GUI + open even after your vagrant up. + +* If your install seems to randomly freeze during `vagrant up` +with no explanation, then there are a couple of things that may be going wrong: + + *Note: If this happens, it may be worth running a simple `vagrant destroy` before you try to `vagrant up` again. It is possible to repair, but it is usually more effort than it is worth.* + + * First, check to make sure you have a solid internet connection. + Even if the connection is fast, it may experience drop-outs every + once in a while, so it is highly recommended to install it with a wired + connection to the internet. + + * Secondly, check to make sure your computer is not going to + sleep, this can be changed in settings for some systems, or you + can install a program to keep it awake (for example, amphetamine on Mac). + +* If an error is thrown during `vagrant up`, you may need to + uninstall Virtual Box and all virtual machines by typing the + following commands: + + _CAUTION: This should only be done if you do not have any other virtual machines._ + + To remove Virtual Box type: + + ``` + sudo apt-get remove --purge virtualbox + ``` + To remove all virtual machines and configuration files type: + + ``` + sudo rm ~/"VirtualBox VMs" -Rf + sudo rm ~/.config/VirtualBox/ -Rf + ``` + This will delete all virtual machine settings. Then install + the latest version of Virtual Box and vagrant from the links given in step 3 (using Ubuntu Software). + +* If it has been a while since your last `vagrant destroy` and + `vagrant up` you may need to update/upgrade/reinstall the virtual + box, vagrant, and the installed boxes on your + system: + + For example, on Mac: + + ``` + brew reinstall --cask virtualbox + brew reinstall --cask vagrant + vagrant plugin update + vagrant box update + ``` + + If you continue to have errors on Mac with `vagrant up` after + reinstalling virtualbox and vagrant, check "System Preferences" -> + "Security & Privacy". You may need to approve/reapprove + "Allow apps download from". You may also need to restart your computer. + + Similar instructions for other OS. + +* If this error is thrown during `vagrant up` command: + ``` + ubuntu-26.84: E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/gcc-9gcc-9_9.4.0-1ubuntu1-20.84.1_amd64.deb Connection fail [IP: 189.211.241.193] + ``` + then you should use VPN to connect to the internet and then try `vagrant up`.This error usually occurs when you are outside the United States and the connection to the Ubuntu package repository is being blocked or restricted. + + __Note:__ The IP address provided in the error message may vary. + ProtonVPN, which provides free VPN service can be used. You can download from their official website at (https://protonvpn.com). You can also use other VPN services. + +--- + +## Forwarded Port Already in Use + +* If you see an error similar to: + + ``` + Vagrant cannot forward the specified ports on this VM, since they + would collide with some other application that is already listening + on these ports. The forwarded port to #### is already in use + on the host machine. + ``` + + This means that one or more of the ports requested by vagrant is already in + use by another application running on your computer. + + +* This may happen if you attempt to create multiple Submitty VMs -- + perhaps unintentionally! E.g., if you have multiple directories on + your computer each with a clone/copy of the Submitty repo. It is + necessary to run `vagrant destroy` in each of these + directories/repositories to clean up unwanted VMs. + + The following command can help locate misplaced repositories/VMs: + + ``` + vagrant global-status + ``` + +* If you might have old, forgotten VMs from previous OS versions + hanging around it can be helpful to completely delete the `.vagrant` + folder in your repository. Also check to see if you have multiple + clones or backups of the repository and thus multiple `.vagrant` + folders on your machine. + + +* You can scan to see what processes on your machine are using the + conflicting ports. Depending on your operating system, try these + commands: + + ``` + netstat -anvp tcp | awk 'NR<3 || /LISTEN/' + ``` + + ``` + lsof -i | grep LISTEN + ``` + + Then you can type `kill ` with the `` of the process (if + you confirm you don't need that process). If you don't recognize + the process using the port in question, search to figure out if you + can or should disable it. For example, on MacOS, the AirPlay + Receiver in Control Center is using port 7000, so you may choose to + turn that off. + + +* You can choose to override the default ports and use an alternate + port through an environment variable. The current variables are + `VM_PORT_SITE`, `VM_PORT_WS`, `VM_PORT_DB`, `VM_PORT_SAML`, and + `VM_PORT_SSH`. + + For example, if the conflicting port is the default site port (1511), + and you want to use port 1512 instead: + ``` + VM_PORT_SITE=1512 vagrant up + ``` + + You can alternatively create a `.env` file in the root of your project + with the text `VM_PORT_SITE=1512` (and any other variables separated by + newlines). Note that you will need to install the env plugin beforehand: + ``` + vagrant plugin install vagrant-env + ``` + +--- + + +## Host-Only / Static Networking + +If you are having trouble being able to view the Submitty webpage after a ```vagrant up``` you might need to +modify the interfaces in your VM. To fix this: + +As root modify ```/etc/network/interfaces``` and add: + +``` +# The host-only network interface +auto eth1 +iface eth1 inet static +address 192.168.56.101 +netmask 255.255.255.0 +network 192.168.56.0 +broadcast 192.168.56.255 +``` + +References and useful links: [https://gist.github.com/pjdietz/5768124](https://gist.github.com/pjdietz/5768124) and [http://christophermaier.name/2010/09/01/host-only-networking-with-virtualbox/](http://christophermaier.name/2010/09/01/host-only-networking-with-virtualbox/) diff --git a/_docs/developer/troubleshooting/system_clock_testing_troubleshooting.md b/_docs/developer/troubleshooting/system_clock_testing_troubleshooting.md new file mode 100644 index 00000000..dc956101 --- /dev/null +++ b/_docs/developer/troubleshooting/system_clock_testing_troubleshooting.md @@ -0,0 +1,39 @@ +--- +title: System Clock Testing & Troubleshooting +category: Developer > Development Troubleshooting +--- + + +* If the VM has a clock skew (incorrect time) + + ``` + sudo service ntp stop + sudo ntpd -gq + sudo service ntp start + ``` + + +* If you need to test time and/or date dependent elements, you can + change it in the vagrant machine so you don't have to wait. To + remove the syncing and set your own time: + + ``` + sudo systemctl disable ntp + timedatectl set-ntp 0 + sudo date -s "-- :: + ``` + + To check the date, helpful to make sure the date and time you set has stuck: + + ``` + date + ``` + + To sync back with the current time: + + ``` + sudo systemctl enable ntp + timedatectl set-ntp 1 + ``` + +--- \ No newline at end of file diff --git a/_docs/sysadmin/troubleshooting/database_overview.md b/_docs/sysadmin/troubleshooting/database_overview.md index d503febd..5fc50e3e 100644 --- a/_docs/sysadmin/troubleshooting/database_overview.md +++ b/_docs/sysadmin/troubleshooting/database_overview.md @@ -1,6 +1,6 @@ --- title: Database Overview -category: System Administrator > Troubleshooting & Other Information +category: System Administrator > SysAdmin Troubleshooting, etc. redirect_from: - /sysadmin/database_overview --- diff --git a/_docs/sysadmin/troubleshooting/log_files.md b/_docs/sysadmin/troubleshooting/log_files.md index 248b63aa..7ea5ff61 100644 --- a/_docs/sysadmin/troubleshooting/log_files.md +++ b/_docs/sysadmin/troubleshooting/log_files.md @@ -1,6 +1,6 @@ --- title: Log Files -category: System Administrator > Troubleshooting & Other Information +category: System Administrator > SysAdmin Troubleshooting, etc. redirect_from: - /instructor/log_files - /sysadmin/log_files diff --git a/_docs/sysadmin/troubleshooting/system_debugging.md b/_docs/sysadmin/troubleshooting/system_debugging.md index be6dfb3d..7a09ba28 100644 --- a/_docs/sysadmin/troubleshooting/system_debugging.md +++ b/_docs/sysadmin/troubleshooting/system_debugging.md @@ -1,6 +1,6 @@ --- title: Websockets / System & Debugging -category: System Administrator > Troubleshooting & Other Information +category: System Administrator > SysAdmin Troubleshooting, etc. redirect_from: - /sysadmin/system_debugging --- diff --git a/_docs/sysadmin/troubleshooting/user_access_level.md b/_docs/sysadmin/troubleshooting/user_access_level.md index a8df8301..35b0f2d8 100644 --- a/_docs/sysadmin/troubleshooting/user_access_level.md +++ b/_docs/sysadmin/troubleshooting/user_access_level.md @@ -1,6 +1,6 @@ --- title: User Access Level -category: System Administrator > Troubleshooting & Other Information +category: System Administrator > SysAdmin Troubleshooting, etc. redirect_from: - /sysadmin/user_access_level --- diff --git a/navtreedata.js b/navtreedata.js index abd40508..65345c19 100644 --- a/navtreedata.js +++ b/navtreedata.js @@ -172,7 +172,7 @@ var NAVTREE = [ "Rainbow Grades", "/sysadmin/configuration/rainbow_grades", null ], [ "Student Photos", "/sysadmin/configuration/student_photos", null ] ] ], - [ "Troubleshooting & Other Information", "/sysadmin/troubleshooting/database_overview", [ + [ "SysAdmin Troubleshooting, etc.", "/sysadmin/troubleshooting/database_overview", [ [ "Database Overview", "/sysadmin/troubleshooting/database_overview", null ], [ "User Access Level", "/sysadmin/troubleshooting/user_access_level", null ], [ "Log Files", "/sysadmin/troubleshooting/log_files", null ], @@ -215,7 +215,6 @@ var NAVTREE = [ "GitHub Actions", "/developer/testing/github_actions", null ] ] ], [ "Vagrant Email Configuration", "/developer/development_instructions/vagrant_email_configuration", null ], - [ "Troubleshooting", "/developer/development_instructions/troubleshooting", null ], [ "Miscellaneous", "/developer/development_instructions/miscellaneous", null ], [ "Advanced Development", "/developer/development_instructions/automated_grading", [ [ "Automated Grading", "/developer/development_instructions/automated_grading", null ], @@ -234,6 +233,10 @@ var NAVTREE = [ "Frontend JavaScript", "/developer/developing_the_php_site/javascript", null] ] ], ] ], + [ "Development Troubleshooting", "/developer/troubleshooting/installation_troubleshooting", [ + [ "Installation Troubleshooting", "/developer/troubleshooting/installation_troubleshooting", null ], + [ "System Clock Troubleshooting", "/developer/troubleshooting/system_clock_testing_troubleshooting", null ], + ] ], [ "Software and System Design", "/developer/software_and_system_design/interface_design_style_guide", [ [ "Interface Design", "/developer/software_and_system_design/interface_design_style_guide", null ], [ "Web Accessibility", "/developer/software_and_system_design/web_accessibility", null ],