Josh Campbell

> @ThingEngineer I started with analytics.enabled = false then did `supabase db reset` and that worked for me to create the missing database and schemas. Obviously this removes all your...

> Another possibility to keep your local data would be to manually connect to the database container and manually run the migration: > > ``` > CREATE DATABASE _supabase WITH...

@t1mmen Curious. I think the initial issue is obviously upgrading the CLI without first stopping supabase with the no back up flag (verified on other projects). And it seems whether...

> it'd be nice if ["Backup and stop running containers" step](https://supabase.com/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=macos) was baked into upgrade process in a nicer way (so as to not clutter up `seed.sql` which might be...

> Is this possibly an bug on Docker's end or on Supabase's end? How will we know it's possible to update Docker Desktop again? Version: 4.41.2 (191736) still does not...

Welcoming PR's for this.

## Feature Request - onChecked RecursiveTreeView event - Only fires when a node checkbox is checked or unchecked - Returns (at a minimum) the `id` of the node and the...

This is happening again in v1.226.3 No issues, just the warning message after linking and a diff between the local and remote supabase/config.toml.

Thank you @sweatybridge, since this does not cause an actual problem with anything I don't feel it warrants it's own issue. However, just as an fyi there may be one...