Bug: GET /items/:id returns 500 when item is missing

[ascerra]

Bug

GET /items/99999 (non-existent id) returns HTTP 500 instead of 404.

Steps to reproduce

1. Start the app (python app.py or equivalent).
2. curl -i http://127.0.0.1:5000/items/99999

Expected

HTTP 404 with a JSON body like {"error": "item not found"}.

Actual

HTTP 500 Internal Server Error. Stack trace mentions a missing key / unhandled lookup in the items handler.

Environment

Python 3.12, Linux, current main.

Notes

This is an API correctness bug on the items endpoint. Please triage with normal labeling for this repo.

[fullsend-ai-triage]

🤖 Triage · ⚠️ Cancelled · Started 3:07 PM UTC · Ended 3:09 PM UTC

Commit: 38f5096 · View workflow run →

[ascerra]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 3:09 PM UTC · Completed 3:13 PM UTC

Commit: adf32fd · View workflow run →

[fullsend-ai-triage]

This issue describes the same underlying problem as #8 — the GET /items/:id endpoint does not exist in app.py. The current codebase only defines PATCH and DELETE handlers for /items/<int:item_id>, so a GET request to that path produces an error rather than a proper 404 response.

Issue #8 tracks adding this endpoint with the exact behavior you're expecting (200 with item JSON when found, 404 with {"error": "item not found"} when not). It has already been triaged and is ready for implementation.

Closing this as a duplicate — progress can be tracked in #8.

---

Labels: API endpoint issue matching the area/api label used on related issues #8 and #19.

[ascerra]

/fs-triage

[fullsend-ai-triage]

🤖 Triage · ⚠️ Cancelled · Started 3:14 PM UTC · Ended 3:15 PM UTC

Commit: 0f1a4a3 · View workflow run →

[ascerra]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 3:16 PM UTC · Completed 3:20 PM UTC

Commit: e606da1 · View workflow run →