Club: let a member edit their report, and send one already decided back for review by widgetii · Pull Request #412 · OpenIPC/website

widgetii · 2026-10-08T17:48:55Z

Requested in the OpenIPC chat: let a member edit a report while no maintainer has reviewed it, and require a new acceptance when one already reviewed is changed.

What a member can do

On /club, an Edit link sits beside each of their reports (not withdrawn ones). They can change:
- the note;
- the camera they proposed: maker, marking and SoC;
- files: take any out, add photos, a boot log or a U-Boot console.
ipctool's output and a backup are what the camera said and stay as sent.
The endpoint is POST /api/v1/club/reports/{id}/edit. It works only on the member's own reports; anyone else gets 404.
A report about a new camera has to keep at least one photo. The limit of 24 files still applies, and an edit that changes nothing is refused.

Review

Pending: the edit is simply made, with no review row.
Published or rejected: the form says so before saving ("goes back to them… off the catalogue until they accept it again"). Saving adds a review row with decision edit, so the report is pending again:
- it leaves the public page and its board;
- it returns to the queue, marked "Edited by the sender".
The next decision settles the stars the way any decision does. Re-publishing takes back a removed file's star and pays for added ones; rejecting takes everything back. Stars already earned stay until then.

How it's built

Reports can still change only through internal/reports. Store.Edit stands the guard down for its own transaction, as Takedown does, and every edit is logged in the append-only, guarded report_edits table (migration 031). The migration also adds edit to the allowed report_reviews.decision values.
A file position is never reused, not even one whose file earned stars and was removed, so ledger rows keep their meaning. An edit and a review never interleave, because both hold the report's lock.
Added text files and an edited note are redacted with the report's own ipctool facts, and any MAC is caught regardless.
Fixed along the way: List read every decision other than publish and reject as "withdrawn". It now reads edit as pending.

Tests

club/edit_test.go, all in one test:
- editing while pending: the note, the camera and a photo, with no review row;
- refused edits: another member's, one that changes nothing, removing the last photo, a position that doesn't exist, editing the YAML;
- publishing, then editing: the report is pending, hidden publicly and taken off the board, back in the queue as edited, and its stars are unchanged so far;
- re-publishing: the removed photo's star is revoked and the boot log is paid, positions are 1, 3, 4, the unit is back, two edits are logged, and the edit history refuses changes.
EditReport.test.tsx: only what changed is sent, and the re-review warning appears.
service/run.sh test: all 23 packages pass, and gofmt is clean. Frontend lint, typecheck, tests (709) and build pass, and the bundle check passes.

Not yet done

Validation on dev.openipc.org.

…ck for review Asked for in the OpenIPC chat: change a report while no maintainer has looked at it, and have one changed after review accepted again. - /club has Edit beside each of the member's reports: the note, the camera they proposed (maker, marking, SoC), files taken out, photos and text added. ipctool's output and a backup are what the camera said and stay as sent. POST /api/v1/club/reports/{id}/edit, the member's own only. - While it waits for review an edit is simply made. Once a maintainer has published or rejected it, saving says so first, then adds a review row 'edit' (migration 031): the report is pending again, off the board and the public pages, and back in the queue marked as edited. The next decision settles its stars as any does: a file taken out is taken back, one added is paid. - Reports stay changed only through internal/reports: Store.Edit stands the guard down for its own transaction as Takedown does, and every edit is logged in append-only report_edits. A file's position is never used twice, so the ledger's rows keep meaning what they meant. One edit and one review never interleave (the report's lock). - List read any decision but publish and reject as withdrawn; it reads 'edit' as pending now.

qodo-free-for-open-source-projects · 2026-10-08T17:52:18Z

PR Summary by Qodo

Let members edit reports and resubmit decided reports for review

✨ Enhancement 🐞 Bug fix 🧪 Tests 🕐 40+ Minutes

AI Description

• Members can edit their reports’ notes, proposed cameras, and files without changing original
 ipctool evidence.
• Decided reports return to review and leave public listings; stars reconcile after the next
 decision.
• Guarded transactions, append-only edit history, localized UI, and tests support the new workflow.

Diagram

graph TD
  UI["Member edit form"] --> API["Club edit API"] --> STORE["Reports Store.Edit"] --> DECIDED{"Previously decided?"}
  DECIDED -- "No" --> KEEP["Keep pending"] --> QUEUE["Pending queue"] --> REVIEW["Review and stars"]
  DECIDED -- "Yes" --> ROW["Append edit review"] --> QUEUE

High-Level Assessment

Keep the edit in the existing reports store and represent a return to pending with an append-only review row. Directly changing a prior decision or maintaining a separate status field would conflict with the existing history-derived review state; reusing the report lock also keeps edits and decisions from interleaving.

Files changed (23) +872 / -45

Enhancement (8) +510 / -8

Club.tsxExpose editing in the member report ledger +18/-5

Expose editing in the member report ledger
• Shows edit timestamps and an Edit control for non-withdrawn reports. Reloads reports and member data after a save.
frontend/apps/site/src/components/club/Club.tsx

EditReport.tsxAdd the member report-edit form +102/-0

Add the member report-edit form
• Lets members change notes and proposed-camera details, remove files, and add photos or text files. Warns when saving will trigger re-review.
frontend/apps/site/src/components/club/EditReport.tsx

Review.tsxIdentify sender edits in the review queue +2/-0

Identify sender edits in the review queue
• Displays the latest member-edit timestamp on queued reports so maintainers can recognize resubmissions.
frontend/apps/site/src/components/club/Review.tsx

club.tsAdd edit metadata and client request helper +12/-0

Add edit metadata and client request helper
• Extends member and queued report types with edit timestamps and adds the authenticated multipart edit request.
frontend/apps/site/src/lib/club.ts

api.goConnect authenticated members to report editing +15/-0

Connect authenticated members to report editing
• Registers the endpoint, requires sign-in, passes member identity to the reports API, and invokes the post-review callback after a successful edit.
service/internal/club/api.go

club.goExpose last-edited times to members and reviewers +8/-1

Expose last-edited times to members and reviewers
• Reads the latest edit timestamp from 'report_edits' and includes it in member reports and review-queue entries.
service/internal/reports/club.go

edit.goImplement guarded, owner-only report edits +349/-0

Implement guarded, owner-only report edits

• Validates changes and applies them under the report lock, preserving file-position history and logging every edit. Decided reports receive an 'edit' review row; removed file bytes are cleaned up when unreferenced.

service/internal/reports/edit.go

store.goTreat edit decisions as pending +4/-2

Treat edit decisions as pending
• Maps 'edit' review rows to pending status while preventing the ordinary review method from issuing that decision.
service/internal/reports/store.go

Bug fix (1) +1 / -1

view.goKeep edited reports in the pending list +1/-1

Keep edited reports in the pending list
• Fixes list-state decoding so an 'edit' decision is pending rather than withdrawn.
service/internal/reports/view.go

Refactor (1) +57 / -33

handler.goReuse upload handling for edit requests +57/-33

Reuse upload handling for edit requests
• Extracts shared file preparation and adds edit-aware multipart parsing. Edits can specify file positions to remove but cannot replace YAML or backups.
service/internal/reports/handler.go

Tests (3) +211 / -2

EditReport.test.tsxTest changed-field submission and re-review warning +60/-0

Test changed-field submission and re-review warning
• Checks that the form sends only changed fields and selected file operations, and warns before saving a decided report.
frontend/apps/site/src/components/club/EditReport.test.tsx

reports_test.goProtect ownership of the new edits table +2/-2

Protect ownership of the new edits table
• Extends the reports-package boundary test to catch access to 'report_edits' outside the permitted area.
service/deploytest/reports_test.go

edit_test.goExercise editing and the full re-review lifecycle +149/-0

Exercise editing and the full re-review lifecycle
• Covers pending edits, ownership and validation failures, public and board visibility, queue return, star reconciliation, non-reused positions, and append-only history.
service/internal/club/edit_test.go

Documentation (1) +7 / -1

CLAUDE.mdDocument the member-edit lifecycle +7/-1

Document the member-edit lifecycle

• Explains editable fields, immutable ipctool evidence, guarded edit history, and re-review after a decided report changes.

CLAUDE.md

Other (9) +86 / -0

boards.en.ymlAdd English report-edit copy +9/-0

Add English report-edit copy
• Adds form actions, the re-review warning, an edit timestamp, and the review-queue marker.
data/locales/boards.en.yml

boards.ru.ymlAdd Russian report-edit copy +9/-0

Add Russian report-edit copy
• Translates the edit controls, re-review warning, timestamp, and queue marker.
data/locales/boards.ru.yml

boards.zh.ymlAdd Chinese report-edit copy +9/-0

Add Chinese report-edit copy
• Translates the edit controls, re-review warning, timestamp, and queue marker.
data/locales/boards.zh.yml

boards.en.jsonAdd English site translations for editing +9/-0

Add English site translations for editing
• Adds site translation keys for edit actions, re-review messaging, timestamps, and the queue marker.
frontend/apps/site/src/i18n/boards.en.json

boards.ru.jsonAdd Russian site translations for editing +9/-0

Add Russian site translations for editing
• Adds the Russian site strings for the edit form and review-queue indicator.
frontend/apps/site/src/i18n/boards.ru.json

boards.zh.jsonAdd Chinese site translations for editing +9/-0

Add Chinese site translations for editing
• Adds the Chinese site strings for the edit form and review-queue indicator.
frontend/apps/site/src/i18n/boards.zh.json

main.goRegister the member-edit route +1/-0

Register the member-edit route
• Adds the POST edit endpoint to the service's route declarations.
service/cmd/openipc/main.go

031_report_edits.sqlAdd guarded edit history and an edit decision +26/-0

Add guarded edit history and an edit decision
• Allows 'edit' in review history and creates indexed 'report_edits' records. Guard triggers prevent changes to recorded edits.
service/internal/db/migrations/031_report_edits.sql

routes.jsonDeclare the web edit endpoint +5/-0

Declare the web edit endpoint
• Adds the POST member-report edit path to the web route manifest.
service/routes.json

qodo-free-for-open-source-projects · 2026-10-08T17:54:23Z

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. ~~Edited cameras stay on the old board~~ ✓ Resolved

Description

Store.Edit replaces a published report's camera proposal without clearing its existing
report_models links. If a maintainer accepts the changed proposal as a new board, Decide adds
that link alongside the old one, and the published report contributes to both boards.

Code

service/internal/reports/edit.go[R95-99]

+			if _, err := tx.Exec(ctx, `DELETE FROM report_proposals WHERE report_id = $1`, id); err != nil {
+				return err
+			}
+			if _, err := tx.Exec(ctx, `INSERT INTO report_proposals (report_id, maker, board, soc) VALUES ($1, $2, $3, $4)`,
+				id, c.Proposal.Maker, c.Proposal.Board, c.Proposal.SoC); err != nil {

Evidence
The edit changes only report_proposals; publication inserts links with ON CONFLICT DO NOTHING
and does not replace prior links. PublishedTexts emits content for every board linked to a
published report.
service/internal/reports/edit.go[85-103]
service/internal/reports/club.go[397-410]
service/internal/reports/club.go[514-523]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Changing a published camera proposal leaves its previous catalogue-board link attached, so accepting the new camera can publish the report on both boards.
## Fix Focus Areas
- service/internal/reports/edit.go[91-103]
- service/internal/reports/club.go[397-405]
## Recommended Fix
Ensure rereview resolves the report's existing board links when a changed proposal is accepted. Remove links that the new decision supersedes while preserving links the maintainer explicitly retains.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. ~~Failed edits leave uploaded files behind~~ ✓ Resolved

Description

Store.Edit calls place() inside its database transaction but does not remove files already
placed if a later placement or database operation fails. When an edit fails after a successful
Files.Keep, the deferred incoming-file discard cannot remove that permanent copy, leaving bytes
with no report-file row.

Code

service/internal/reports/edit.go[R179-180]
+			if err := place(); err != nil {
+				return err

Evidence
The edit places uploads before later inserts and transaction work can fail. Keep clears the
incoming file handle after linking the permanent file, so the handler's deferred in.discard() does
not undo a successful placement when the transaction rolls back.
service/internal/reports/edit.go[168-205]
service/internal/reports/edit.go[259-262]
service/internal/reports/handler.go[367-386]
service/internal/reports/files.go[88-115]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
An edit can permanently place uploaded files and then roll back its database transaction, leaving unreferenced bytes in storage.
## Fix Focus Areas
- service/internal/reports/edit.go[168-205]
- service/internal/reports/edit.go[319-345]
- service/internal/reports/files.go[88-115]
## Recommended Fix
Track files placed during the edit and, on placement or transaction failure, remove only those confirmed unreferenced. Preserve files already referenced by other reports.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. ~~Members can delete the backup that should stay as sent~~ ✓ Resolved

Description

Store.Edit checks only that each remove position exists in report_files. It never checks the
file's kind, so a backup row (kind backup) can be removed, and EditReport.tsx shows a 'Take out'
checkbox for every file, backup included. That goes against the stated rule that ipctool's output
and a backup stay as sent. The deleted bytes are then queued as orphans and removed from the store.

Code

service/internal/reports/edit.go[R126-131]

+		for _, pos := range c.Remove {
+			if _, ok := files[pos]; !ok {
+				return refusal{fmt.Errorf("remove: the report has no file %d", pos)}
+			}
+			removed[pos] = true
+		}

Evidence
Backups are stored as report_files rows of kind backup (memberReport reads f.Kind == "backup",
and prepare handles the kind backup). The remove loop in Edit only checks files[pos] exists.
The frontend renders report.files.map checkboxes with no kind filter, and read(edit) refuses
only a new backup part, not removing an existing one.
service/internal/reports/edit.go[125-131]
service/internal/reports/club.go[175-189]
frontend/apps/site/src/components/club/EditReport.tsx[74-84]
service/internal/reports/handler.go[367-374]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Store.Edit lets a member remove any file position, including the report's backup. That contradicts the rule that the backup stays as sent.
## Fix Focus Areas
- service/internal/reports/edit.go[125-131]
- frontend/apps/site/src/components/club/EditReport.tsx[74-84]
## Recommended Fix
In the remove loop, return `refusal{...}` when `files[pos].kind == "backup"`. In EditReport.tsx, filter out files with `kind === 'backup'` from the 'Take out' list. Add a test case for it.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

View medium (3)

4. ~~A review racing an edit pays stars on stale files~~ ✓ Resolved

Description

Store.Decide calculates each file’s potential stars before opening its transaction and taking the
report-stars: lock, while Store.Edit changes the file rows under that lock. If an edit commits
between the calculation and the review’s lock acquisition, the review uses the old file set for its
ledger writes, potentially awarding a star for a removed position and none for a newly added file.

Code

service/internal/reports/edit.go[R47-54]

+// Edit applies a member's change to their report, in one transaction under
+// the report's lock (the one Decide holds, so a review and an edit do not
+// interleave). place puts the added files in the store.
+func (s *Store) Edit(ctx context.Context, id, member, by string, c Change, notePublic func(string) string, place func() error) (Edited, error) {
+	var out Edited
+	var what []string
+	err := Unguarded(ctx, s.DB, func(tx pgx.Tx) error {
+		if _, err := tx.Exec(ctx, `SELECT pg_advisory_xact_lock(hashtextextended('report-stars:' || $1, 0))`, id); err != nil {

Evidence
Decide calls s.potential(ctx, id, yaml != "") on s.DB before pgx.BeginFunc, then acquires
pg_advisory_xact_lock inside the transaction and uses the earlier result for ledger deltas. Edit
holds the same lock while deleting and inserting report_files, so the lock does not protect
Decide’s read from an intervening edit.
service/internal/reports/club.go[366-379]
service/internal/reports/club.go[391-394]
service/internal/reports/club.go[436-466]
service/internal/reports/edit.go[53-56]
service/internal/reports/club.go[377-395]
service/internal/reports/club.go[449-461]
service/internal/reports/edit.go[125-146]
service/internal/reports/edit.go[152-205]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`Decide` reads file-star potential before taking the per-report advisory lock held by `Edit`, allowing an intervening edit to make the amounts used for the decision and ledger writes stale.
## Fix Focus Areas
- service/internal/reports/club.go[366-395]
- service/internal/reports/edit.go[53-54]
## Recommended Fix
Move the `yaml` read and potential calculation into the `pgx.BeginFunc` callback, after acquiring `pg_advisory_xact_lock`. Make `potential` accept a querier so it reads the current files through the transaction; keep the decision and ledger writes under the same lock, and preserve the rule excluding the report’s own backup.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

5. ~~A takedown racing an edit can restore the wiped note~~ ✓ Resolved

Description

Edit reads the status, then runs UPDATE reports SET note..., and Takedown does not take the
report-stars: lock. When a takedown commits after Edit's status check, the edit's UPDATE waits on
the row lock and then overwrites the blanked note. Its INSERTs also add new report_files to a
report that is now withdrawn.

Code

service/internal/reports/edit.go[R65-80]

+		st, err := s.status(ctx, tx, id)
+		if err != nil {
+			return err
+		}
+		if st.State == "withdrawn" {
+			return ErrNotEditable
+		}
+
+		var note string
+		if err := tx.QueryRow(ctx, `SELECT note FROM reports WHERE id = $1`, id).Scan(&note); err != nil {
+			return err
+		}
+		if c.Note != nil && *c.Note != note {
+			if _, err := tx.Exec(ctx, `UPDATE reports SET note = $2, note_public = $3 WHERE id = $1`,
+				id, *c.Note, notePublic(*c.Note)); err != nil {
+				return err

Evidence
Takedown runs Unguarded and blanks note/note_public, deletes files, and inserts a 'withdraw'
review, all without the advisory lock. Edit's withdrawn check and its writes are separate statements
under READ COMMITTED, so they do not serialize with Takedown.
service/internal/reports/store.go[349-399]
service/internal/reports/edit.go[65-83]
service/internal/reports/edit.go[194-207]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Edit and Takedown can interleave: Edit passes the withdrawn check, Takedown commits, then Edit writes the note and files back into a withdrawn report.
## Fix Focus Areas
- service/internal/reports/store.go[349-360]
- service/internal/reports/edit.go[53-71]
## Recommended Fix
Have Takedown take the same `pg_advisory_xact_lock(hashtextextended('report-stars:' || id, 0))` at the start of its transaction. Alternatively, have Edit lock the report row first with `SELECT ... FROM reports WHERE id=$1 FOR UPDATE` and only then read the status.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

6. ~~Maintainers can publish content they never saw~~ ✓ Resolved

Description

An edit to a pending report adds no review row and no version marker, and Decide has no way to
tell that the report changed after the maintainer opened the queue. A member can swap photos or text
while a maintainer has the queue item open, and publishing then puts the unseen files and note on
the public board.

Code

service/internal/reports/edit.go[R222-229]

+		out.Status = st.State
+		if st.State == "published" || st.State == "rejected" {
+			if _, err := tx.Exec(ctx, `INSERT INTO report_reviews (report_id, decision, by, note) VALUES ($1, 'edit', $2, $3)`,
+				id, by, strings.Join(what, ", ")); err != nil {
+				return err
+			}
+			out.Status, out.Rereview = "pending", true
+		}

Evidence
Edit inserts a review row only when the state is published or rejected. Decide takes only
id/decision/models and publishes whatever report_files/note_public hold at commit time.
PublishedTexts then serves the current files of any report whose latest decision is 'publish'.
service/internal/reports/edit.go[222-229]
service/internal/reports/club.go[348-366]
service/internal/reports/club.go[501-512]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A pending report can be changed by its member between a maintainer loading the queue and clicking publish, so content nobody reviewed gets published.
## Fix Focus Areas
- service/internal/reports/club.go[348-394]
- service/internal/club/api.go[645-690]
- frontend/apps/site/src/components/club/Review.tsx[80-92]
## Recommended Fix
Send the `edited_at` the reviewer saw (or the latest report_edits id) with the decision. Inside Decide's locked transaction, compare it with `max(at)` from report_edits and refuse with 409 if they differ, so the reviewer reloads.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

7. ~~Changing the file kind silently drops picked files~~ ✓ Resolved

Description

The kind ` handler calls setAdd([]) but does not clear the uncontrolled file `. After a member
switches kind, the input still shows the chosen files while none of them are sent. Only files
re-picked after the switch are submitted, and the form gives no sign that the earlier selection was
discarded.

Code

frontend/apps/site/src/components/club/EditReport.tsx[R88-92]

+          <select value={kind} onChange={(e) => { setKind((e.target as HTMLSelectElement).value as AddKind); setAdd([]); }} class={field}>
+            {ADD_KINDS.map((k) => <option key={k} value={k}>{t(`club.kind_${k}`)}</option>)}
+          </select>
+          <input type="file" multiple aria-label={t('club.edit_add')} accept={kind === 'photo' ? 'image/jpeg,image/png,image/webp' : '.txt,.log,text/plain'}
+            onChange={(e) => setAdd([...((e.target as HTMLInputElement).files ?? [])])} class="text-sm text-body" />

Evidence
onChange on the select resets the add state, but the file input has no value/key binding.
Its displayed FileList keeps the old selection, while save appends only add.
frontend/apps/site/src/components/club/EditReport.tsx[44-45]
frontend/apps/site/src/components/club/EditReport.tsx[88-92]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Switching the add-kind select empties the files to send, but the file input still shows the previous selection.
## Fix Focus Areas
- frontend/apps/site/src/components/club/EditReport.tsx[88-92]
## Recommended Fix
Give the file input `key={kind}` so it remounts empty when the kind changes, or clear `input.value` through a ref in the select's onChange handler.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Tip of the day

💡 Did you know, you can keep summaries lean with Findings visible per group, which tucks the rest behind a View link

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

… racing a review or a takedown - The queue carries each report's revision (its sender's edit count), and a decision sent with it is refused with 409 when the report changed since: a maintainer never publishes what they did not see. - Decide reads what each file would earn under the report's lock, the one an edit holds, so a review never pays for the files as they were. - Takedown takes the same lock: an edit cannot write into a report being withdrawn, and re-checks withdrawn under it. - Changing the proposed camera unlinks the board the old one was published on; the next review decides the board afresh. - A backup stays as sent: an edit cannot take it out, and the form does not offer it. - An edit that fails after placing its files takes them back out of the store. - The edit form clears its file picker when the kind changes, so what it shows is what it sends.

qodo-free-for-open-source-projects Bot reviewed Oct 8, 2026

View reviewed changes

openipc-ai added 2 commits October 8, 2026 17:57

Merge remote-tracking branch 'origin/master' into club-report-edit

aa3bb1e

widgetii merged commit f07f2a0 into master Oct 8, 2026
2 checks passed

widgetii deleted the club-report-edit branch October 8, 2026 18:24

Navigation Menu

Repository navigation

Club: let a member edit their report, and send one already decided back for review - #412

Club: let a member edit their report, and send one already decided back for review#412
widgetii merged 3 commits into
masterfrom
club-report-edit

widgetii commented Oct 8, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 8, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 8, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

widgetii commented Oct 8, 2026

What a member can do

Review

How it's built

Tests

Not yet done

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 8, 2026

PR Summary by Qodo

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

qodo-free-for-open-source-projects Bot commented Oct 8, 2026 •

edited

Loading