Skip to content

Conversation

sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Feb 21, 2025

What kind of change does this PR introduce?

Bug fix #3071 (comment)

What is the new behavior?

Also ignore supabase_realtime_messages_publication when running db dump.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 13448819747

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.02%) to 58.221%

Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 13438662169: -0.02%
Covered Lines: 7787
Relevant Lines: 13375

💛 - Coveralls

@sweatybridge sweatybridge merged commit 3cdb5d7 into develop Feb 21, 2025
9 checks passed
@sweatybridge sweatybridge deleted the no-dump branch February 21, 2025 02:51
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.

[Bug] DB reset - ERROR: must be owner of publication realtime

2 participants