fix: surface real network cause on Gitea issue creation failure (v0.51.4)
A thrown fetch error (DNS failure, connection refused, timeout) never reached the res.ok branch, so its actual cause was lost — err.message alone is often just "fetch failed" with the real reason nested in err.cause. Now logs the full cause server-side and folds it into the error returned to the admin support view's tooltip. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -2,6 +2,11 @@
|
||||
|
||||
All notable changes to Epicure are documented here. This file is mirrored in-app at `/changelog` (and in the admin dashboard) via `apps/web/lib/changelog.ts` — update both together.
|
||||
|
||||
## 0.51.4 — 2026-07-19 12:50
|
||||
|
||||
### Fixed
|
||||
- Gitea issue creation failures now log the real network-level cause server-side (DNS/connection/timeout, not just "fetch failed") and surface a more specific message in the admin support view's tooltip.
|
||||
|
||||
## 0.51.3 — 2026-07-19 12:35
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user