Merge branch 'main' into main

Author: bmcutler

Gemfile.lock

@@ -39,6 +39,7 @@ GEM
       logger
     faraday-net_http (3.1.1)
       net-http
+    ffi (1.17.2-aarch64-linux-gnu)
     ffi (1.17.2-arm64-darwin)
     ffi (1.17.2-x64-mingw-ucrt)
     ffi (1.17.2-x86_64-linux-gnu)
@@ -220,7 +221,7 @@ GEM
       gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
-    json (2.18.1)
+    json (2.19.3)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -239,6 +240,8 @@ GEM
     mutex_m (0.2.0)
     net-http (0.4.1)
       uri
+    nokogiri (1.18.9-aarch64-linux-gnu)
+      racc (~> 1.4)
     nokogiri (1.18.9-arm64-darwin)
       racc (~> 1.4)
     nokogiri (1.18.9-x64-mingw-ucrt)
@@ -285,6 +288,7 @@ GEM
     yell (2.2.2)
 
 PLATFORMS
+  aarch64-linux-gnu
   arm64-darwin-22
   arm64-darwin-23
   arm64-darwin-24

_docs/developer/getting_started/vm_install_using_vagrant.md

@@ -15,8 +15,7 @@ Machine (VM) on your computer and the VM will use the Ubuntu GNU/Linux
 operating system.
 
 ***NOTE:** We only officially support and test development using
-VirtualBox for AMD and Intel machines and QEMU for
-M-Series ARM MacOS machines.*
+VirtualBox.*
 
 ---
 
@@ -51,14 +50,7 @@ M-Series ARM MacOS machines.*
    platform and prevent VirtualBox from working correctly. It is recommended to not install
    or use WSL2 alongside VirtualBox for now.*
 
-5. If you're on an M-series ARM MacOS (e.g., M1, M2, M3),
-   you will be using QEMU with SMB file sharing.
-   To enable this, open **System Settings** and navigate to **General > Sharing**.
-   Press the (i) button next to **File Sharing**, and in the popup window
-   click "Options...". Then turn on "Share files and folders using SMB" and
-   check the box next to your name in the list below.
-
-6. The complete installation process could take an hour or more and 
+5. The complete installation process could take an hour or more and 
    will probably fail if paused or interrupted.  Make
    sure your internet connection is strong and consistent.  You'll
    probably want to plug in your laptop power cord.  Check your
@@ -122,24 +114,14 @@ M-Series ARM MacOS machines.*
       * [Ruby](https://www.ruby-lang.org/en/downloads)  
       * [Git](https://git-scm.com/downloads)  
       * [Vagrant](https://developer.hashicorp.com/vagrant/install)
-      * *M-SERIES ARM MacOS:* [QEMU](https://www.qemu.org)  
-      * *EVERYONE ELSE:* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+      * [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
           * Ensure VirtualBox version is compatible with Vagrant.
 
 
    * **MacOS**  
       You can either go to respective sites and download the necessary binaries or
       install [Homebrew](http://brew.sh/), if you don't have it, and then:
 
-      If you have an M-series ARM Mac, run:
-      ```
-      brew install --cask vagrant
-      brew install qemu
-      vagrant plugin install vagrant-qemu
-      ```
-  
-      Or if you have an older Intel-based Mac, run:
-
       ```
       brew install --cask vagrant
       brew install --cask virtualbox
@@ -243,9 +225,6 @@ M-Series ARM MacOS machines.*
 
 
    * **Build pre-packaged VM**
-
-     *NOTE: The pre-packaged Submitty VM is not (yet)
-     available for QEMU / M-Series ARM Mac machines.*
  
      If you are using VirtualBox as your provider, you will by default
      use a pre-packaged Submitty VM.  This will have all of Submitty
@@ -285,13 +264,8 @@ M-Series ARM MacOS machines.*
 
 
    * **Build from scratch**
-
-      * Using QEMU on an M-Series Arm MacOS, type:
-        ```
-        vagrant up --provider=qemu
-        ```
  
-      * On Linux or Intel-based Mac, type:
+      * On Linux or Mac, type:
         ```
         FROM_SCRATCH=1 vagrant up --provider=virtualbox
         ```
@@ -326,12 +300,7 @@ M-Series ARM MacOS machines.*
      creation of these sample submissions and their autograding and
      decrease the time to complete installation.
 
-     * On M-series ARM Mac:
-       ```
-       NO_SUBMISSIONS=1 vagrant up --provider=qemu
-       ```
-
-     * On Linux or Intel-based Mac:  
+     * On Linux or Mac:  
        ```
        NO_SUBMISSIONS=1 FROM_SCRATCH=1 vagrant up --provider=virtualbox
        ```

_docs/developer/getting_started/worker_vm.md

@@ -31,22 +31,7 @@ machines* in addition to your primary vagrant virtual machine.
 
    _NOTE: This will create the vagrant configuration file: `.vagrant/workers.json`._
 
-
-4. If you are on MacOS running QEMU, restart the network socket in public mode:
-   ```
-   vagrant workers socket restart --public
-   ```
-   _NOTE: Using the `--public` flag will make your worker VMs accessible to anyone
-   on your local network, which may be a modest security concern.
-   We suggest this to minimize possibility of errors while creating the
-   worker machines and will revert this in a later step._
-
-   _NOTE: Running a socket command while a worker machine is running can detach the
-   process, making the VM inaccessible to vagrant. If this happens and you are unable
-   to `vagrant workers halt`, then you may run `pkill -15 -f qemu-system-` to kill
-   all virtual machines running on your computer (including the main Submitty VM)._
-
-6. Now you can create the worker machine(s) with:
+4. Now you can create the worker machine(s) with:
    ```
    vagrant workers up
    ```
@@ -55,26 +40,23 @@ machines* in addition to your primary vagrant virtual machine.
 
    When this is finished, you should see the Submitty duck ASCII art for each new worker machine.
 
-7. You can verify that all the worker machines are running with:
+5. You can verify that all the worker machines are running with:
    ```
    vagrant workers status
    ```
 
-8. `vagrant ssh` into the main virtual machine and run:
+6. `vagrant ssh` into the main virtual machine and run:
    ```
    refresh_vagrant_workers   # (runs python3 /usr/local/submitty/GIT_CHECKOUT/Submitty/.setup/bin/refresh_vagrant_workers.py)
    submitty_install
    ```
 
-9. To stop the worker machines, you can run:
+7. To stop the worker machines, you can run:
    ```
    vagrant workers halt
    vagrant workers socket stop
    ```
 
-   _For MacOS QEMU users: Once the virtual machine(s) are halted, if you would like to restart under
-   private networking, you may do so by omitting the `--public` flag from the `vagrant workers socket start` command._
-
 
 ---
 

_docs/developer/troubleshooting/installation_troubleshooting.md

@@ -190,7 +190,7 @@ References and useful links: [https://gist.github.com/pjdietz/5768124](https://g
 
 ## SSH connection was unexpectedly closed
 
-* If you see an error similar to on ARM64 Machine (Apple Silicon):
+* If you see an error similar to:
 
   ```
   The SSH connection was unexpectedly closed by the remote end. This
@@ -219,19 +219,10 @@ References and useful links: [https://gist.github.com/pjdietz/5768124](https://g
   vagrant box update
   ```
 
-* Verify qemu is install correctly
-
-  * Firstly, use this command will display the installed version of QEMU for ARM64. 
-    ```
-    qemu-system-aarch64 --version
-    ```
-      
-  * Secondly, Verify that the QEMU binary for ARM64 is accessible in your system's PATH by running:
-    ```
-    which qemu-system-aarch64
-    ```
-
-    *Note: This command will display the path to the QEMU ARM64 binary (e.g., /opt/homebrew/bin/qemu-system-aarch64)
+* Verify Virtualbox is install correctly
+  ```
+  VirtualBox -h
+  ```
 
 * Verify Vagrant Installation
   ```
@@ -262,9 +253,9 @@ References and useful links: [https://gist.github.com/pjdietz/5768124](https://g
   vagrant destroy
   ```
 
-* Boots up a new Vagrant environment using the QEMU provider
+* Boots up a new Vagrant environment
   ```
-  vagrant up --provider=qemu
+  vagrant up --provider=virtualbox
   ```
 
 ---

_docs/instructor/assignment_preparation/no_file_rubric_grading.md

@@ -0,0 +1,48 @@
+---
+category: Instructor > Assignment Preparation
+title: No File Rubric Grading
+redirect_from:
+  - /instructor/no_file_rubric_grading
+---
+
+The **No File Rubric Grading** feature is a utility within the Bulk Upload instructor submission interface. It allows instructors to automatically submit an empty "placeholder" pdf submission for **every** active student on a specific gradeable. 
+
+An example of when this would be useful is for an assignment (like a presentation) where students do not have anything to submit to Submitty, but the instructor still wishes to grade them through Submitty.
+
+In this case, an instructor can use the **No File Rubric Grading** feature to enable rubric grading for all students. 
+
+---
+
+## How to Use this Feature
+
+1. **Create the Gradeable:** Ensure your gradeable is set to the 
+   type: *"TA/Instructor will (bulk) upload scanned .pdf"*.
+   
+2. **Access the Submission Page:** Navigate to the gradeables page and click the 
+   **Bulk Upload** tab.
+
+3. **Click "No File Rubric Grading":** This button is located 
+   near the top of the Bulk Upload section alongside the other submission modes.
+
+4. **Click "Submit Placeholder for Every Student":** This will actually submit the pdf
+   placeholders for every student on the gradeable. After confirming, a message will appear at the top of the screen displaying the successful number of submissions made.  
+   ![](/images/instructor/assignment_preparation/no_file_rubric_grading.png){:width="800px"}
+
+**Important:** This action **will** create 
+a new submission for all students on the gradeable. It will appear as the student's
+active version within the grading view and on the database. It will not erase any 
+previous submissions.
+
+---
+
+## Grading
+
+Once the submissions have been processed, they can be graded like any other student submission. They will be listed as a new version under the student's version status. Further uses of the function (while uneccessary) will simply increment the version number.
+
+---
+
+## Troubleshooting
+
+Ensure you are logged in as an Instructor level user.  
+Full grading access is required to use this feature. 
+There is currently no Team gradeable functionality for this feature. 

_docs/instructor/assignment_preparation/personalized_exams.md

@@ -7,7 +7,7 @@ redirect_from:
 
 
 We provide scripts to prepare personalized exams for each student,
-facilitating randomized assigned seating, QR codes, and notes/crib sheets:
+facilitating randomized seating assignments, QR codes, and notes/crib sheets:
 
 
 * (Optional) Collect student left or right handedness.  
@@ -32,7 +32,7 @@ facilitating randomized assigned seating, QR codes, and notes/crib sheets:
     ```
 
 
-* Prepare a "blank" test as a .pdf file.  Be sure to empty space on
+* Prepare a "blank" test as a .pdf file.  Be sure to leave empty space on
   the first page to allow placment of the large box with student
   information and the QR code.
 
@@ -46,12 +46,12 @@ facilitating randomized assigned seating, QR codes, and notes/crib sheets:
   instructions to prepare personalized exams.
 
   Note that in addition to the QR code on the first page, the
-  student's name and email address is placed in the upper right corner
+  student's name and email address are placed in the upper right corner
   of all following pages.
 
   ![](/images/instructor/personalized_exam/personalized_page_1.png){:width="380px"}
   ![](/images/instructor/personalized_exam/personalized_page_2.png){:width="380px"}
 
 
 * _TODO: Write instructions for printing a large set of personalized exams
-  with our specific copier._
+  with our specific copier._

_docs/instructor/course_management/course_materials.md

@@ -30,9 +30,11 @@ Materials" label in the navigation bar.
     ![](/images/course_materials_option_subdir.png)  
 
 * Note: The total size of all files uploaded at one time must be less
-  than or equal to 10 mb or the value of the
+  than or equal to 100 mb or the value of the
   [upload file size limit](/sysadmin/installation/system_customization#allowing-large-student-file-upload-submissions)
-  for your server.
+  for your server, and the total size of all files stored in course materials must 
+  be less than 1 GB.
+
 
 
 

_docs/student/student_errors.md

@@ -8,11 +8,11 @@ title: Debugging Submitty Output
 
 Your code is not tested locally first, Submitty should be used as the
 final submission server, not as a debugger. Before submitting anything
-make sure that you are able to run your code locally without error.
+make sure that you are able to run your code locally without errors.
 In addition the instructor may decide to use hidden tests which still
 reveal the grade. Often these tests check corner cases and exactly what those
 could vary by your program but common cases to consider are positive, 
-negative, zero, and floating point values and how your code performs give
+negative, zero, and floating point values and how your code performs given
 unexpected but valid input.
 
 Often times there may be a missing punctuation or small typo in the output
@@ -45,21 +45,21 @@ perform operations slower than hashmaps or trees-like structures. If your code
 gets a kill signal and you are using specific data structures be sure you are
 using them correctly
 
-If you are using python, ineffeicant use of dictionaries, and sets can cause this error to occur.
+If you are using python, inefficient use of dictionaries, and sets can cause this error to occur.
 
 ![](/images/killSignal.png)
 
 ### Segmentation Fault
 
 For anyone who has ever programmed in a language with explicit memory management such as C/C++
-you are probably familiar with the infamous and seemingly unhelpful error know as Segmentation Fault.
+you are probably familiar with the infamous and seemingly unhelpful error known as Segmentation Fault.
 In short however a SegFault is the result of a memory access violation.
 
 This can occur for a number of reasons, first case we will look at is going out of bounds. 
 If while iterating over a list your index is out of the range of the list this can 
 result in a memory SegFault.
 
-Another possibly is when using pointers, if a pointer on the stack is initialzied to NULL
+Another possibility is when using pointers, if a pointer on the stack is initialzied to NULL
 or never initialized in the first place but you try to dereference it this is the same thing 
 as a NUllPointerException in Java and is a very common issue when dealing with pointers 
 which are commonly found when dealing with Tree structures and and linked lists.
@@ -70,6 +70,6 @@ but since submitty is a teaching tool lets assume the problems given are
 not so large that you run out of memory trying to solve it.  A common example 
 of this is infinite recursion. Make sure the base case is eventually called.
 
-There are other reasosn for SegFaults but these are very common examples.
+There are other reasons for SegFaults but these are very common examples.
 However what ever the reason DrMemory/Valgrind and gdb are excellent tools to 
 help with more advanced errors if print debugging isn't cutting it. 

_docs/student/testing_networks.md

@@ -9,7 +9,7 @@ title: Testing Networked Applications Locally
 We are currently hosting the docker images that will be used for grading on the
 [Docker Hub](https://hub.docker.com/u/submitty/).  
 
-You can can "pull" the most recent submitty images using the commands:  
+You can "pull" the most recent submitty images using the commands:  
 ```
 docker pull submitty/python:2.7
 docker pull submitty/python:3.6
@@ -34,7 +34,7 @@ docker create -i -t -v SOURCE_CODE_DIRECTORY:SOURCE_CODE_DIRECTORY -w SOURCE_COD
 ``-i`` boots the container in interactive mode, allowing submitty to pipe standard
 input to the containers.  
 
-``-t`` Allocates a pseudo-TTY so that you can interact with your container.  
+``-t`` allocates a pseudo-TTY so that you can interact with your container.  
 
 ``-v`` mounts a directory on the host machine so that output persists after the
 docker exits. ``SOURCE_CODE_DIRECTORY:SOURCE_CODE_DIRECTORY`` specifies first
@@ -61,7 +61,7 @@ Once you have created a few containers, you can create a network with this comma
 ```
 docker network create --driver bridge NETWORK_NAME
 ```
-Where you can specify your own network_name.
+You can specify your own network_name.
 
 Then, you can connect your containers to the network as follows:
 ```