chore: back-merge main → dev (2026-08-09) - #2652
Merged
Merged
Conversation
captureConsoleIntegration listens on ['error','warn'], so the console.warn in fetchWithSentry became a SECOND Sentry event for every non-2xx in the app — grouped by that call site rather than by request. The result was a single bucket holding ~32k events across every endpoint, titling itself after whichever request happened to fail most recently. That is actively misleading, not just noisy. It read this morning as "invites/accept failed, 80 users" and was triaged as the top production issue; the real rate for that endpoint is 1 event in 7 days. The explicit captureMessage two lines below is the real report — it already fingerprints on [method, url, status] and carries headers, body and response. So this only needs to stop double-reporting: console.info, exactly as the catch block below already does for the same reason. Also skips /tokens/price 404. That means the upstream price provider declined the lookup (in practice a Mobula 429); the UI falls back to token denomination, so it is a degraded display and never a wrong number. The backend already downgraded its own log for this (PEANUT-API-75) — reporting it from the client re-created the same page-per-lookup noise as PEANUT-UI-QKY. Deliberately NOT removing the captureException in useTokenPrice: its comment says beforeSend already drops the fetch-error wrapper, so it still surfaces genuine non-fetch errors.
The bare prefix also matched /tokens/price-history and any nested path, so a 404 from one of those would have skipped its captureMessage and gone unreported. Bounded to the path end or a query/fragment.
…t-network-warn fix(sentry): stop one console.warn from swallowing every network error
…a8dd1b) Bumps src/content on production (main) from f33d67f → 8a8dd1b (peanut-content latest = mono@0488f9a). Single-file submodule pointer change. Publishes content already merged + mirrored from mono that the dev-targeted auto-PRs never promote to main.
…202608091940 content: publish latest to production (src/content → peanut-content@8a8dd1b)
…into-dev-20260809
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Contributor
Code-analysis diffPainscore total: 7158.75 → 7159.01 (+0.26) 🆕 New findings (2)
✅ Resolved (2)
|
Contributor
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Routine back-merge. Clean — zero conflicts.
Supersedes #2643, which was opened 2026-08-07 17:04Z, minutes before the badge-platform UI merge landed, and has been
mergeable=false/dirtysince. The badge platform (and the[Object]Sentry fix,3b80afb27) already reacheddevby another route, so this carries only whatmainpicked up afterwards.What comes across
fix(sentry): stop one console.warn from swallowing every network error(fix(sentry): stop one console.warn from swallowing every network error #2649) + the CodeRabbit follow-up anchoring the skip to the exact/tokens/priceroute, with its testssrc/contentpointer →peanut-content@8a8dd1b(the 2026-08-09 content publish)Verification
ort, 3 files)pnpm typecheck— cleanWorth noting the Sentry fix coming across is adjacent to the badge warning fixed in #2647: that one made the unavailable-campaign payload readable, this one stops a
console.warnfrom swallowing network errors wholesale. Both are Sentry-signal quality, and they don't overlap.