Skip to content

🔄 Sync with upstream changes#17

Open
h0lybyte wants to merge 271 commits intomainfrom
upstream-main
Open

🔄 Sync with upstream changes#17
h0lybyte wants to merge 271 commits intomainfrom
upstream-main

Conversation

@h0lybyte
Copy link
Copy Markdown
Member

Upstream Sync

This PR contains the latest changes from the upstream repository.

Changes included:

  • Synced from upstream/main
  • Auto-generated by upstream sync workflow

Review checklist:

  • Review the changes for any breaking changes
  • Check for conflicts with local modifications
  • Verify tests pass (if applicable)

This PR was automatically created by the upstream sync workflow

edgurgel and others added 30 commits October 1, 2025 11:53
* fix: reduce max_frame_size to 5MB
* fix: fullsweep_after=100 on gen rpc pub sub workers

---------

Co-authored-by: Eduardo Gurgel Pinho <eduardo.gurgel@supabase.io>
* Also tweak buckets to account all the way to 3000KB
* Start tagging the payload size metrics with message_type. message_type can be presence, broadcast or postgres_changes
It uses a fork of Phoenix for time being

* fix: count presence_diff events on MessageDispatcher
* fix: remove traces from console during development
* fix: use LiveView stream for status page

* fix: need full node name on localhost for tests

* fix: cleanup

* fix: add tests

* fix: bump version

* fix: cleanup syntax

* fix: format
---------

Co-authored-by: blacksmith-sh[bot] <157653362+blacksmith-sh[bot]@users.noreply.github.com>
Co-authored-by: Eduardo Gurgel Pinho <eduardo.gurgel@supabase.io>
Selective broadcast for Postgres Changes. We use the fact that we know where each subscription subscribed from and do a direct broadcast for each node instead of spamming the whole cluster.

If the subscription node is not readily available (for whatever reason) we fallback to sending to the whole cluster.
…ransport (supabase#1563)

Also set fullsweep_after for RealtimeChannel processes
* Use GenRpc on SubscriptionsChecker
* Use GenRpc on PostgresCdcRls
Tweaked a few tests and increase max cases to 4
Validates the size of the track message sent and fails if exceeds the value set by `tenant.max_payload_size_in_kb`
When regional_broadcasting is true GenRpcPubSub uses a single node in each region to broadcast to the rest of the region. Nodes communicating inside the same region have a much lower latency.
supabase-libs-pr-manager bot and others added 30 commits March 24, 2026 08:40
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
This way we can truly have Watchdog and ReplicationConnection linked
Also use Tasks to ensure that they drop the used memory after
aggregating such metrics
Comma-separated list of `key=value` pairs appended as `extra_label` query parameters
on each metrics push (e.g., `region=us-east-1,env=prod`). Useful for label injection
supported by systems like VictoriaMetrics. If not set, no extra labels are added.
…1770)

Include db_host_resolved to tenant info

Also minor things like renaming the module to use RealtimeWeb and use external_id instead of project_ref
* ci: update supabase-js for e2e tests in workflow

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
* Application.fetch_env! does an ETS lock on every single read and we do it across several high volume areas of the service
* Map.drop removed as Jason already tackles this and this will prevent map copy
* Always use gen_rpc as the communication method between cluster
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.

10 participants