Skip to content

fix: propagate database errors in addEntry instead of swallowing#168

Open
jakebromberg wants to merge 2 commits intomainfrom
fix/8-addentry-error-handling
Open

fix: propagate database errors in addEntry instead of swallowing#168
jakebromberg wants to merge 2 commits intomainfrom
fix/8-addentry-error-handling

Conversation

@jakebromberg
Copy link
Member

Summary

  • addEntry's catch block for getLatestShow() only logged the error without calling next(e)
  • Execution fell through and sent a misleading 400 'no active shows' instead of a 500

Test plan

  • Unit test: mock getLatestShow to throw, assert next(e) is called

Made with Cursor

The catch block for getLatestShow() only logged but didn't call next(e),
causing a misleading 400 response when the real issue was a DB error.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jakebromberg jakebromberg force-pushed the fix/8-addentry-error-handling branch from 6ab4fa9 to 39b700b Compare February 27, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant