forked from supabase/supabase
-
Notifications
You must be signed in to change notification settings - Fork 0
[pull] master from supabase:master #631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
## Context There's some changes for Vector Buckets with the wrappers extension on version 0.5.7 and above The "Query from Postgres" CTA (which runs an import foreign schema command) no longer accepts the bucket name as part of the schema options (ref [changelog](https://github.com/supabase/wrappers/releases/tag/v0.5.7)), and instead takes the bucket name as the remote schema name. So changes here are to update the SQL for importing foreign schema for vector buckets if wrappers extension is above 0.5.7 Also - the `::embd` type no longer seems to exist in 0.5.7 as well, so updated the example code too ## To test Can probably test on a new US East 1 project on the preview - [ ] Verify creating a vector bucket table + can query from postgres (via the Insert vectors CTA after creating a table) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Fixed breadcrumb navigation links for vector bucket pages. * **Improvements** * Unified loading state for schema workflows and disabled actions while loading. * Enhanced version compatibility checks for foreign schema imports to support newer extension syntax. * Adjusted generated SQL for vector data to use the appropriate embedding syntax based on extension version. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- 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? LLM configuration ## What is the current behavior? No skills for E2E tests ## What is the new behavior? Claude skill for E2E tests <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added comprehensive end-to-end testing guidelines for Studio Playwright tests, covering test execution, environment setup, robust selector patterns, common pitfalls, debugging workflows, and CI troubleshooting. * **Chores** * Updated repository ignore settings so skills-related documentation files are tracked and can be committed. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Observability Dashboard: unified overview for service health and database infrastructure with interactive charts and metric cards (CPU, memory, disk I/O, connections, error rate, slow queries). * Service Health Monitoring: per-service health cards and a multi-service table with error/warning counts and drill-down links to reports/logs. * Interval Selector: new chart-interval dropdown with plan-aware retention messaging. * Menu & Reports: updated Observability menu with Overview entry and Custom Reports management. * **Documentation** * Added a footer link to troubleshooting guides. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- 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? This pull request adds documentation and support for the Dropzone (File Upload) and Realtime Cursor components for both Vue and Nuxt.js frameworks in the UI library. It updates the sidebar navigation, introduces new documentation pages, and ensures these components are referenced in the project overview and component listings. TODO: install new dependencies and resolve conflicts in lock.json ## Additional context Initiative by Terry :) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added Dropzone and Realtime Cursor components for Vue and Nuxt.js (file upload with previews/validation; collaborative cursor tracking). * **Documentation** * Added comprehensive Vue and Nuxt.js docs and registry entries for Dropzone and Realtime Cursor with usage examples and API guidance. * **Bug Fixes** * Fixed text escaping in several authentication and UI components for consistent rendering. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Terry Sutton <saltcod@gmail.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com> Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
…ce (#42227) **Logic changes** - Adds function in `helpers.ts` to extract URLs from text via regex - I also considering using a library like [linkify-it](https://www.npmjs.com/package/linkify-it) for this but figured it's not worth the extra dep - Adds associated tests in `helpers.test.ts` - Adds "URL Validity" scorer which performs a HEAD request for links in Assistant response text and determins what portion of links have `.ok` responses - Adds eval case to check correctness of support ticket URL answers **Prompt changes** - Informs Assistant of https://supabase.com/dashboard/support/new being the URL to create support tickets - Encourages Assistant to "self-debug" issues before directing users to create support tickets See [Eval Report](#42227 (comment)) and [Correctness](https://www.braintrust.dev/app/supabase.io/p/Assistant/trace?object_type=experiment&object_id=1ad0f9b0-5adb-436c-9812-a87aac62c036&r=1ef13459-a98c-4904-925e-6d81276cebb2&s=dbe5c607-a560-462b-8745-41d430744431) analysis for new support ticket test case. Resolves AI-384 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added URL validity scoring to evaluations and helper utilities for extracting/cleaning URLs. * Added evaluation cases for support-ticket URL handling and OAuth callback guidance. * **Documentation** * Updated assistant guidance to prefer self-resolution, include support-ticket direction, clarified data-recovery search steps, and added template-URL notation. * **Tests** * Expanded URL extraction and related utility tests to cover many formats and edge cases. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 : )