[pull] master from supabase:master#1000
Merged
Merged
Conversation
As part of hibernation (suspend and wake), wakes via PostgREST happen automatically. However, if a user goes straight to the dashboard, we want to ensure the project wakes up from it's slumber. I've decided to add this logic at a very central point that will prevent most project-ref related pages to load (purposely). The project ref details endpoint returns whether the project is hibernating or not - so for any regularly running project, none of the added logic will be invoked and there is no extra network calls, so no negative perf impact for these checks. Eventually with v3 architecture none of this is needed as wakes are done at the proxy/network layer, but this is a necessary change for v2 for more graceful wakes. Adjusted network restrictions as it would query before the project loads and potentially time out while still loading <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **New Features** * Automatic wake-up for hibernating projects restores functionality without manual intervention. * **Platform API Enhancements** * New conversation management endpoints for escalation, synchronization, and resolution. * New project wake endpoint for managing dormant project states. * Updated read-replica operation response codes for improved API consistency. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Problem The Disk Size section in the database report used raw HTML headings and unstyled spans without semantic Tailwind tokens, resulting in inconsistent typography and spacing compared to the rest of the report. ## Fix - Replace bare `<h5>` labels with `<p className="text-sm text-foreground-light">` for consistent muted label styling - Add `font-semibold text-foreground` to stat values so they stand out clearly - Simplify the stat row layout from a brittle `inline-grid grid-cols-12 gap-12` to `flex flex-wrap items-center gap-8` with `ml-auto` on the action button - Replace `<h3 className="mt-8 text-sm">` with a properly styled `<p>` label for the Large Objects sub-section - Style the empty-state "No large objects found" message with `text-sm text-foreground-light` ## How to test - Go to `/project/<ref>/observability/database` - Scroll to the Database Size section - Confirm the Space used and Provisioned disk size labels are muted and values are bold/prominent - Confirm the layout is clean and the Increase disk size button sits to the right - Confirm the Large Objects sub-section label and empty state are consistently styled <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Updated the visual layout and styling of the Database Size widget's summary area, improving the presentation of disk space metrics. * Enhanced the styling of the Large Objects section header and empty-state messaging for better visual consistency. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
## Problem Deleting a custom report waited for the API round trip before updating the UI. The confirmation modal showed a loading spinner, the report stayed visible in the sidebar until the request resolved, and the interaction felt sluggish. ## Fix The delete now applies optimistically. On confirm, the report is removed from the sidebar immediately and the user is navigated away. The actual delete runs in the background. If it fails, the cached list is rolled back to its previous state and an error toast is shown. The optimistic behavior lives inside `useContentDeleteMutation` (via `onMutate` snapshot + `onError` rollback), so any current or future caller of that hook gets it for free, no per-call wiring required. ## How to test - Open a project with at least one custom report - Click the kebab menu on a report and choose Delete report, then confirm - Expected result: the report disappears from the sidebar instantly and a success toast appears - To test rollback: throttle/offline the network or force the delete endpoint to fail, then delete again - Expected result: the report reappears in the sidebar and an error toast is shown <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Improvements** * Deletion flows now provide explicit loading, success and error feedback; UI updates immediately on delete and will restore if the action fails. * **Removals** * Removed the reports menu and individual report menu item UI components (affects report-level rename/delete dropdowns and related menu navigation). * **Tests** * Added tests covering content deletion behavior, multiple-deletion cases, and data integrity after removals. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…46874) ## Problem The Memory usage chart now includes a Swap series, but the telemetry reports docs do not mention it. Swap is shown alongside Used, Cache + buffers, and Free in the same chart, not as a standalone chart. ## Fix - Add **Swap** to the Memory usage component table - Add a short note that the Swap series only appears when the system is swapping, with a brief explanation of what swap means for performance - Add a swap-activity row to the Memory usage "How it helps debug issues" table No standalone Swap section and no separate entry in the charts summary table, since swap is part of the Memory usage chart. ## How to test - Run the docs site and open the Reports guide (`/docs/guides/telemetry/reports`) - Confirm the Memory usage section lists Swap as a component and the tables render correctly <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated Advanced Telemetry (Database) to include "Swap" in the memory-usage breakdown, explain what swap is, and note its impact when RAM is exhausted. * Added "Swap activity monitoring" to troubleshooting guidance as a signal of sustained paging to disk and its effect on database performance, plus recommended mitigation actions. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated React Router packages to v7.17.0 for improved routing stability. * Adjusted workspace dependency governance and overrides for more consistent installs. * Removed an obsolete PostCSS re-export. * **New Features** * Integrated Tailwind into the build pipeline to enable utility-first styling. * **Style** * Added global base styles to standardize border color across UI elements. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update (stale internal links). ## What is the current behavior? The Logs guide moved from `/docs/guides/platform/logs` to `/docs/guides/telemetry/logs`, but five internal links still use the old path. They only resolve through a two-hop permanent redirect (`platform/logs` → `monitoring-troubleshooting/logs` → `telemetry/logs`, in `apps/www/lib/redirects.js`). Affected: - `guides/database/extensions/pgaudit.mdx` - `guides/platform/read-replicas.mdx` - `guides/storage/cdn/metrics.mdx` (`#logs-explorer`) - `troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx` - `troubleshooting/http-status-codes.mdx` (`#logs-explorer`) ## What is the new behavior? Links now point directly at `/docs/guides/telemetry/logs` (relative links use `../telemetry/logs`), avoiding the redirect chain. The `#logs-explorer` anchor is preserved and still resolves (`## Logs Explorer` in `guides/telemetry/logs.mdx`). 5 files changed, links only — no content changes. ## Additional context Pure documentation link cleanup, analogous to the Metrics-guide link fixes.
…46816) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update (stale internal links / dead anchors). ## What is the current behavior? The Metrics guide moved from `/docs/guides/platform/metrics` to `/docs/guides/telemetry/metrics` and was split into sub-pages, but 15 internal links across the docs still use the old path: 1. **Redirect chain** — non-anchored links to `/docs/guides/platform/metrics` only resolve via a two-hop permanent redirect (`platform/metrics` → `monitoring-troubleshooting/metrics` → `telemetry/metrics`, in `apps/www/lib/redirects.js`). 2. **Dead anchors** — `#accessing-the-metrics-endpoint` and `#deploying-supabase-grafana` no longer exist on the restructured page, so those links currently land at the top of the page instead of the intended section. ## What is the new behavior? - Non-anchored links now point directly at the canonical `/docs/guides/telemetry/metrics` (relative links use `../telemetry/metrics`), avoiding the redirect chain. - `#accessing-the-metrics-endpoint` links → `/docs/guides/telemetry/metrics` (the Metrics API endpoint access content lives on that page). - `#deploying-supabase-grafana` links → `/docs/guides/telemetry/metrics/grafana-self-hosted`, the page that now holds the Prometheus/Grafana installation instructions those links referenced. 15 files changed, links only — no content changes. ## Additional context Pure documentation link cleanup. Affected files include several guides (`database/connection-management`, `database/inspect`, `platform/performance`, `platform/read-replicas`) and troubleshooting entries that reference the Metrics/Grafana setup guide.
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * 404 handling now returns path-aware not-found pages for missing docs and guides, improving accurate user-facing 404 responses. * Improved file-missing errors for guides so missing content cases surface clearer diagnostic info. * **Chores** * Enhanced 404 telemetry so missing-path information is recorded for better monitoring and quicker troubleshooting. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Towards FUNC-308 ## What kind of change does this PR introduce? Docs update ## What is the current behavior? Missing error codes definitions for Edge Functions ## What is the new behavior? This PR adds maps the possible error codes that Edge Functions can return <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added a new “Error Codes” guide for Edge Functions, explaining how to use the `sb-error-code` response header and covering error categories (bad implementation, authentication, request, server) with causes and solutions. * **New Features** * Updated site navigation to include a direct “Error Codes” link under the functions menu for quicker access. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>
github-actions
Bot
added
the
documentation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )