Local Project Link Request says update config.toml but no differences cited

[sosensible]

Describe the bug Attempting to run > supabase link generated this exception.

Connecting to remote database...
Finished supabase link.
WARNING: Local config differs from linked project. Try updating supabase\config.toml
[api]
enabled = true
port = 54321
schemas = ["public", "graphql_public"]
extra_search_path = ["public", "extensions"]
max_rows = 1000
[api.tls]
enabled = false

To Reproduce Steps to reproduce the behavior:

1. run > supabase link
2. enter the db password when requested
3. read the error message
4. check for differences there are none
5. look for docs to say what settings are in linked project, no known path to resolve
6. tried updating to current db version on prod site and repeating but same results

Expected behavior Local dev to link with remote without a WARNING: that has not path to resolution.

Screenshots n/a

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: ... would not create ticket ...
• Version of OS: Windows 11
• Version of CLI: 1.183.5
• Version of Docker: 27.0.3
• Versions of services:

      SERVICE IMAGE      │      LOCAL       │  LINKED
  ─────────────────────────┼──────────────────┼────────────
  supabase/postgres      │ 15.1.1.78        │ 15.1.1.78
  supabase/gotrue        │ v2.155.3         │ v2.155.3
  postgrest/postgrest    │ v12.2.2          │ v12.2.2
  supabase/realtime      │ v2.29.15         │ -
  supabase/storage-api   │ v1.6.8           │ v1.6.8
  supabase/edge-runtime  │ v1.54.10         │ -
  supabase/studio        │ 20240701-05dfbec │ -
  supabase/postgres-meta │ v0.83.2          │ -
  supabase/logflare      │ 1.4.0            │ -
  supabase/supavisor     │ 1.1.56           │ -
  darthsim/imgproxy      │ v3.8.0           │ -

  Additional context n/a

[hamzaakramdropslab]

@sosensible did you find the solution to this problem

[sosensible]

We got it running but blocking some of the service containers from starting, but that is not functional as we expect to use some of those services.

[evris99]

Same for me with supabase-cli version 1.187.2

[empz]

Also experiencing this issue. Supabase CLI 1.187.3

[plainpaul]

Same issue using: Supabase CLI 1.187.3

[plainpaul]

I'm somewhat new to supabase and even newer to supabase cli so pardon my ignorance. I didn't realize I could have a local dev instance when I started, so I built everything through the remote dashboard/SQL editor. To get it locally, is this where Project Link comes into play? Are there any workarounds to get this work bug fixed? Is there any way to output the toml file from Supabase's dashboard and update it that way?

[sweatybridge]

I can confirm this is a bug with detecting differences in remote and local config, which results in the printed message. However, seeing this message does not mean linking project failed. You can continue using supabase locally with cli despite config differences.

@plainpaul hope this clarifies.

[sweatybridge]

The config diff bug as been resolved in latest cli release.