Skip to content

fix: API hardening, WS recovery, search, and TUI error handling#18

Merged
xsmyile merged 2 commits intomasterfrom
fix/api-hardening
Apr 16, 2026
Merged

fix: API hardening, WS recovery, search, and TUI error handling#18
xsmyile merged 2 commits intomasterfrom
fix/api-hardening

Conversation

@xsmyile
Copy link
Copy Markdown
Member

@xsmyile xsmyile commented Apr 16, 2026

Summary

  • Replace CORS mirror_request() with explicit Any (static * rather than reflecting request origin)
  • Handle broadcast::RecvError::Lagged by logging + continuing instead of disconnecting the WS client
  • Add semaphore (10 concurrent) around webhook HTTP tasks to bound fan-out
  • Allow + and _ in FTS5 search queries (addresses like user+tag@example.com)
  • Add error_for_status() to all TUI API client methods

Test plan

  • All 67 tests pass
  • Zero clippy warnings

Closes #15

xsmyile added 2 commits April 16, 2026 11:35
- Replace CORS mirror_request() with explicit Any (static Access-Control-
  Allow-Origin: * rather than reflecting request origin) (H-3)
- Handle broadcast::RecvError::Lagged by logging and continuing instead
  of disconnecting the WebSocket client (M-2)
- Add semaphore (max 10 concurrent) around webhook HTTP tasks to prevent
  unbounded fan-out under email bursts (M-3)
- Allow + and _ characters in FTS5 search queries so addresses like
  user+tag@example.com are searchable (M-4)
- Add error_for_status() to all TUI API client methods so HTTP errors
  are surfaced immediately instead of causing deserialization failures (M-5)

Closes #15
@xsmyile xsmyile merged commit 22adfe6 into master Apr 16, 2026
2 checks passed
@xsmyile xsmyile deleted the fix/api-hardening branch April 16, 2026 09:42
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.

API hardening and search fixes

1 participant