Changelog¶
All notable changes to marimo-grader will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Two things release from this repository on their own tags. The service — the
backend, worker and web app, shipped as container images — releases on v*.
The notebook widget, marimo-grader-client on PyPI, releases on client-v*
and is versioned separately, because a student's notebook and the server it
submits to upgrade at different times by design. Entries below say which.
[Unreleased]¶
Added¶
- Every submission is graded from the student's own outputs. Client 0.3.0's
Submit sends marimo's session snapshot (
__marimo__/session/<notebook>.py.json, every cell's last outputs) with the notebook, waiting a couple of seconds so the newest outputs are in it. A new worker step renders it to HTML without executing anything, in about a second, by matching outputs to the submitted cells by code hash (cells with identical code are paired in order, which marimo's own matching does not do); a cell edited after it last ran shows its code without its stale output. It is the render for assignments with re-run off (the grading view used to show only code and saved files there) and the first render otherwise, until the re-run replaces it. The grading view says which it is ("The student's own outputs, saved with this attempt · all 41 cells") and the queue repeats it next to the score. Nothing changes in assignment notebooks and students do nothing. The worker pinsmarimo==0.25.2: the step uses marimo internals. -
grader attach-outputsattaches a session snapshot or an HTML render to an existing attempt (instructors only, recorded in the change log, labelled as attached). For attempts made before client 0.3.0, such as the Fall 2026 exam: re-run the notebook locally withmarimo export session, then attach the session. API:POST /api/v1/submissions/{id}/outputs. -
Grades autosave as drafts; Publish is what the student sees. In the grading queue every edit to a score, rubric item or comment saves itself as a draft a moment after you stop typing, and at once when you move to another student (
j/k, Prev/Next) or leave the page. A copy waits in the browser until the server has it, so a dropped connection, a closed tab or a crash loses nothing: the edits come back the next time the queue opens. The Save button is now Publish (still ⌘Enter, still moving on to the next student), and the "Release this grade to the student" checkbox is gone. A line under the form says where things stand: draft saved, published, or edited since publishing (the student keeps seeing the published grade until you publish the changes). Drafts update one row in place, with no audit entry or event; publishing writes both, as saving did. - Publish all drafts. Grade a whole question quietly, then publish every
draft on it at once from the queue's header, each as its grader left it, so
the class gets its grades together. Answers nobody has started stay
unpublished. API:
POST /api/v1/offerings/{id}/questions/{qid}/publish-drafts. - Drafts show in class progress. A new state, drafted, not published, hatched green on the assignments table and the assignment page's student strips. Drafts count toward "to grade" and the Grade button.
- TAs can publish grades: a course setting you can change. A toggle under
Teaching staff on the roster page (
ta_can_finalize, on by default, which until now could only be set when the course was created). Off, a TA's queue has no Publish button and their grades wait as drafts for an instructor. API:PATCH /api/v1/offerings/{id}/settings. - Resizable grading panes. Drag the bar between the notebook and the grading panel, or under the saved files, to give either more room; arrow keys nudge a focused bar, a double-click resets it, and the sizes are kept per browser.
Changed¶
- Drafts replace provisional scores. A score saved with "Release this grade" unticked was provisional: still shown to the student, feedback and all (the notebook added "Provisional score; a final grade may follow"), and counted in their overview and the Canvas export. Students and the gradebook now see published scores only; staff views show the newest, draft or not. When this deploys, any score that was saved provisional and never released becomes a draft: it leaves the student's view and is back in your queue, ready to publish. On hand-graded questions the autograder's partial points also wait for publishing.
Fixed¶
- Moving to the next student no longer discards what you typed.
j/kand Prev/Next reset the form without saving it. - Saved files thumbnails load. The web app's Content-Security-Policy
allowed images only from its own origin, so every thumbnail (a presigned
link to
<account>.r2.cloudflarestorage.com) was blocked; the links worked because opening one is a navigation.img-srcnow allowshttps://*.r2.cloudflarestorage.com; the web container needs redeploying.
Upgrade notes¶
- One migration (
submissions.snapshot_artifact_id), applied by the deploy'smigratestep. - New settings:
GRADER_MAX_SNAPSHOT_BYTES(10 MiB),GRADER_SNAPSHOT_TIMEOUT(120 s). - Students need client 0.3.0 for their snapshots to be sent; older clients still submit, and those attempts show code until outputs are attached.
[0.1.11] — 2026-10-21¶
Added¶
- Rubrics. A question graded by hand can carry a rubric: Add a rubric on the assignment page takes an outline (parts at the margin, items indented under them, 1 point each unless an item ends in "(2 points)"), pasted from a document if you like, and shows the items it makes before you save. In the grading queue each item gets its own score, grouped under its part with a subtotal, and Full marks for the blank items lets you start from full marks and take points off. The whole-notebook question is worth what its rubric adds up to. Only instructors and TAs see a rubric; scores outside an item's range, or for an item the rubric does not have, are refused.
Fixed¶
- Client 0.2.4:
put()stores figures, brain maps and more tables. A.nii.gzname is now gzipped: nibabel'sto_bytes()is uncompressed, so an image stored that way could not be read back. nltools BrainData is accepted (to_nifti())..png,.jpg,.svgand.pdfnames take a matplotlib figure or axes, a seaborn grid or a nilearn plot..csv/.tsvtake polars DataFrames, nltools DesignMatrix and numpy arrays as well as pandas, whose row labels are kept unless they are the default 0, 1, 2…. A str under a binary name (a file name passed by mistake) is refused with a pointer toupload()instead of being stored as the file.
[0.1.10] — 2026-10-19¶
Changed¶
- The assignments table shows where each assignment stands. Rows are grouped into Open now, Coming up and Closed (folded); one When column gives the date that matters next; a bar shows the class's progress (graded, waiting for you, failed, not submitted) and an Average column the mean score of students whose work is fully graded. Only the unusual gets a label: Hidden from students, Enrolled only, Not re-run. Each row has Grade (with the count waiting, straight to the queue when one question has them) or Review, Settings and More (copy student link, preview as a student, upload a corrected notebook, export to Canvas). Filters and a search sit above it. Rows are selected by clicking them (shift-click for a run); a bar at the bottom exports the selection or changes its due date.
- The assignment page is down to what is used. A sentence on where it
stands, then one row per question with a strip of marks, one per student,
colored by state; a mark opens that student's answer in the queue
(
/grade/<question>?netid=). The settings summary, student links and version history are gone from the page: Settings is a side panel, shared with the table, and the rest is under More. - Settings are grouped into When, Who and where, and Attempts and grading, with the title editable alongside.
Added¶
GET /offerings/{id}/progress[?assignment_id=]: each student's state on each question (graded, waiting, failed, running, none), counted per question and per assignment, with the answers to grade and the average; with an assignment, the per-student marks in roster order (services/progress.py).
[0.1.9] — 2026-10-19¶
Changed¶
- Publish a new version from the assignment page, with the instructor
notebook alone. The grader builds the student copy and reads the questions
as
grader publishdoes (services/student_copy.py, now shared with the CLI). A preview comes first -- the version number, the questions and how each is graded, what is new, removed or changed, the student copy to download -- and Publish version N makes it live (POST .../versions/preview,POST .../versions/from-notebook). The hand upload of two notebooks plus question JSON is gone from the page; its API remains for the CLI.
Fixed¶
- Version history times carry their UTC offset; they showed as hours in the future on servers whose database returns naive timestamps.
[0.1.8] — 2026-10-19¶
Changed¶
- Assignments is a table. One row per assignment with its access, status,
opens / due / closes, version, questions, points and grading; click a column
to sort, again to reverse (due date by default). Click rows to select them
(or Select all) and Export Canvas CSV takes the selection. The title
opens a new assignment page: key settings, a Settings button that
opens the form in place, the student notebook, Open in molab and a copyable
launch link, the questions with their grading queues, and the version history
(
GET /offerings/{id}/assignments/{aid}/versions). Uploading a version by hand moved there, under thegrader publishcommand that is the usual way.
[0.1.7] — 2026-10-19¶
Changed¶
- Needs attention groups grading failures by cause. One entry per
assignment and cause instead of one line per submission, saying what happened,
whose move it is, and whether a retry can help (
services/failures.py). Retry all re-queues a group (POST /offerings/{id}/retry), and the page follows each retried submission to its outcome -- queued, grading, graded, waiting for a hand grade, or failed again with the new reason (GET /offerings/{id}/retry-status). The awaiting-grade line no longer repeats a question id used as its title.
[0.1.6] — 2026-10-19¶
Security¶
- The safety scan excuses only findings the release also had. 0.1.5 excused a flagged line whenever its text appeared anywhere in the released copy, so a line the release merely contained (in a string, say) could cover a student's import. A finding is now excused only when the released copy was flagged for the same thing on an identical line.
[0.1.5] — 2026-10-19¶
Changed¶
- Renders show the code. The worker renders submissions with
--include-code, so the grading view (and a student's own) shows each cell's code above its output instead of only "passed". The submission view has Rendered / Code tabs, the second being the source as submitted.grader rerenderre-renders older submissions one at a time while the queue is otherwise idle.
Fixed¶
- A student is not refused for a line the course gave them. The safety
scan now runs before grading and excuses a flagged line that appears, as
written, in the released copy. A thresholding release shipped
import ioin its setup cell, and every submission from it failed before running.
[0.1.4] — 2026-10-19¶
Added¶
- Student preview. Instructors and TAs can switch their own view of an
offering to a student's (
PUT /offerings/{id}/preview, Preview as a student on the Student view page) and test an assignment the way the class will: the student list and portal,close_atand the deadline enforced, student-scoped storage credentials, staff pages refused -- in the web app and in notebooks signed in as them. Release dates do not apply, so an exam can be tried before it opens; submissions remain test attempts. A banner offers Exit preview. Newenrollments.preview_studentcolumn (migrationc4d8e1f2a903).
[0.1.3] — 2026-10-19¶
Added¶
- Private assignments and exams.
visibility: enrolledkeeps an assignment out ofassignments.jsonand serves its notebook (/a/.../student.py,/molab) only to signed-in members of the offering, by session or notebook token.release_at/due_at/close_atform one window for the notebook, its storage data and submissions; staff are exempt. A private assignment without arelease_atstays closed and is left out of students' assignment list, so an exam can be built in place.grader publishsends settings with the create, so a new private assignment is never briefly public.late_policy: rejectrefuses work after the deadline, otherwise it is accepted and markedlate. A new/a/<course>/<term>/<slug>/launchlink signs a student in and lands on their portal, which now offers Open in molab and Download .py and shows the window. Storage credentials and presigned URLs no longer outlive an assignment'sclose_at. Docs: For instructors → Exams and private assignments. - Whole-notebook submission.
notebook_submissionadds anotebookquestion that takes the entire notebook: manual whennotebook_points> 0, a graded-on-arrival receipt at 0. Turning it on lets a version publish without a_markscell;notebookis a reserved qid. autograde: falsestores and renders submissions without running checks, andrender_timeoutgives an assignment longer than the worker default.render: falseskips the re-run too: the grading view shows the submitted code and a Saved files panel of what the student wrote understorage.private()/<slug>/(GET /submissions/{id}/files, presigned links, files changed afterdue_atflagged).-
grader publishgains--private/--public,--release,--due,--close,--late-policy,--no-autograde,--notebook-pointsand--render-timeout. -
Client 0.2.0: course storage in the notebook.
marimo_grader_client.storageis the notebook side of the storage broker, moved here from dartbrains-tools so any course on the grader gets it:signin_button()/connect(),course(),private(),group(),assignment(slug), a durable@cache,local_path()for anything that wants a file. One obstore store per mount with a self-renewing credential; the token is cached where the runtime keeps things (~/.config/marimo-grader, or molab's.env, which it recognises by its sandbox).GRADER_*names throughout;storage.configure(server=...)for a course's default.assignment_card(slug)links a chapter to its assignment on the grader. dartbrains-tools 0.3 wraps this and keeps its imports working.
Fixed¶
- Client 0.1.2: a sign-in token restored from the browser's storage now
reaches the kernel as well. The widget showed "signed in" but left the
tokentrait empty, so Python code keyed off it -- the storage layer'sconnect()-- saw nobody. Only a fresh click synced it.
[0.1.2] — 2026-09-18¶
Added¶
- Storage broker (service). A signed-in notebook can ask the grader for
storage credentials:
POST /offerings/{id}/storage/sessionreturns two Cloudflare R2 temporary credentials scoped to exactly the prefixes the enrollment may reach — course data, released assignments and the shared cache read-only; the student's own area, group folders and private cache read-write; staff additionally the student areas they may grade.POST …/storage/presigngives a single presigned URL for runtimes that cannot sign requests,GET …/storage/methe mount table without minting. The grader stays in the control path only; bytes flow between the notebook and R2 directly. Student prefixes are an HMAC of the NetID, so a listing never exposes the roster. Assignments gain optionalrelease_atandclose_atsettings; outside that window the prefix is absent from every credential, so pre-release data is unreachable rather than hidden. Off untilGRADER_STORAGE_ENABLEDand the Cloudflare values are set; see the configuration reference anddocs/storage-architecture.md. - New tables
groups,group_membersand the append-onlystorage_grantsaudit (migrationb7c2e9d41f03). scripts/r2_spike.py, the isolation experiment the design rests on.
[0.1.1] — 2026-09-17¶
Security¶
- Every login-link code is now refused at the device poll, not just the
operator one.
poll()compared the code's client against the literal"operator-login-link"rather than checkingLOGIN_LINK_CLIENTS, so only half the set was excluded. Both kinds of login-link row are minted pre-approved and unconsumed, and the poll mints a notebook token from any such row — soPOST /auth/device/token, given the code out of a sign-in email, returned an eight-hour notebook token without the link ever being opened. An email code lives seven days; a device code lives ten minutes. Impact was limited — the holder of the code is the intended user, and the token grants only their own submit-and-read access — but the two paths are meant to be disjoint, andconsume_login_code()already checked the set. (#19)
Removed¶
- A roster test helper,
_netids, that nothing called and that could not have worked if anything had: the endpoint it read returns a list, so its first line would raise. (#18)
Documentation¶
- The documentation site was reworked (marimograder.org):
a live demo assignment that runs in the reader's browser alongside the
instructor notebook it was generated from, an Authentication section covering
the device handshake, SAML, email sign-in links and token lifetimes, the
deployment runbook moved out of
deploy/README.mdand onto the site as eight operator pages, and a How it works section. (#14, #15) - Corrections found by reviewing the new pages against the code: an unreleased
score is provisional rather than hidden — the student portal shows it and
the widget labels it —
grader seeddefaults--studentsto two example NetIDs,warm-cachescans the version's instructor artifact rather than the published copy, the Ed25519 key-type error is raised at first token mint rather than at startup, andGRADER_USE_BUBBLEWRAP=1enables the sandbox without requiring it. (#15) - The sidebar labels the index page "Home" instead of repeating the site name, and the header carries marimo-book's mark until the grader has one of its own. (#16, #17)
[0.1.0] — 2026-09-16¶
First tagged release: the service as deployed for the DartBrains pilot — SAML and notebook sign-in, publishing, immutable per-attempt submissions, sandboxed autograding, the grading web app, roster import and Canvas export.