Skip to content
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

Local Development Instructions Not Working #77

Open
localjo opened this issue Jul 15, 2024 · 3 comments
Open

Local Development Instructions Not Working #77

localjo opened this issue Jul 15, 2024 · 3 comments

Comments

@localjo
Copy link

localjo commented Jul 15, 2024

I tried following the instructions for local development, but something isn't working. After running npm run db:start, when I run npx supabase status it just returns:

Stopped services: [supabase_auth_jep supabase_inbucket_jep supabase_realtime_jep supabase_storage_jep supabase_imgproxy_jep supabase_pg_meta_jep supabase_studio_jep supabase_pooler_jep]
supabase local development setup is running.

         API URL: http://127.0.0.1:54321
     GraphQL URL: http://127.0.0.1:54321/graphql/v1
          DB URL: postgresql://postgres:[email protected]:54322/postgres

I tried creating a new Supabase project online and setting SUPABASE_URL, SUPABASE_ANON_KEY, and SUPABASE_SERVICE_ROLE_KEY from that. And I tried running the npx supabase link command.

I wasn't able to get the local Supabase dashboard running. http://localhost:54323/ doesn't have anything running on it.

And after running npx run dev, and opening the app, I get JWSError JWSInvalidSignature.

So I think there are some steps missing for getting the dev environment set up.

@cmnord
Copy link
Owner

cmnord commented Jul 15, 2024

Can you inspect the logs from the Supabase Docker containers (using Docker Desktop or otherwise) and see their error logs? Are they restarting in loops?

@localjo
Copy link
Author

localjo commented Jul 16, 2024

I see some errors. In supabase_db_jep:

2024-07-16 13:53:40 172.22.0.3 2024-07-16 06:53:40.114 UTC [57] supabase_admin@postgres ERROR:  duplicate key value violates unique constraint "users_lower_email_index"
2024-07-16 13:53:40 172.22.0.3 2024-07-16 06:53:40.114 UTC [57] supabase_admin@postgres DETAIL:  Key (lower(email::text))=([email protected]) already exists.
2024-07-16 13:53:40 172.22.0.3 2024-07-16 06:53:40.114 UTC [57] supabase_admin@postgres STATEMENT:  INSERT INTO "users" ("admin","api_key","api_quota","billing_enabled","email","email_me_product","email_preferred","endpoints_beta","name","provider","provider_uid","token","inserted_at","updated_at") VALUES ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14) RETURNING "id"

In supabase_vector_jep:

2024-07-16 13:53:40 2024-07-16T06:53:40.104937Z ERROR transform{component_kind="transform" component_id=db_logs component_type=remap component_name=db_logs}: vector::internal_events::remap: Mapping failed with event. error="function call error for \"upcase\" at (476:516): expected string, got null" error_type="conversion_failed" stage="processing" internal_log_rate_limit=true
2024-07-16 13:53:40 2024-07-16T06:53:40.105093Z ERROR transform{component_kind="transform" component_id=db_logs component_type=remap component_name=db_logs}: vector::internal_events::remap: Internal log [Mapping failed with event.] is being rate limited.
2024-07-16 13:53:47 2024-07-16T06:53:47.423120Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::internal_events::docker_logs: Started watching for container logs. container_id=277d27065e98e8676fa1f04f82473994e287bd520dd90c2411c9cfbd1b1cc161
2024-07-16 13:53:47 2024-07-16T06:53:47.426663Z ERROR transform{component_kind="transform" component_id=rest_logs component_type=remap component_name=rest_logs}: vector::internal_events::remap: Mapping failed with event. error="function call error for \"to_timestamp\" at (140:166): No matching timestamp format found for \"16/Jul/2024:06:53:47 +0000: Attempting to connect to the database...16/Jul/2024:06:53:47 +0000\"" error_type="conversion_failed" stage="processing" internal_log_rate_limit=true
2024-07-16 13:53:47 2024-07-16T06:53:47.758234Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::internal_events::docker_logs: Started watching for container logs. container_id=b17fd707041de64fe7467c5e9503ca6e447ca05d4c5d551ab83ee1e15039b147

Screenshot 2024-07-16 at 1 57 40 PM

@cmnord
Copy link
Owner

cmnord commented Jul 16, 2024

I will try to reproduce with a fresh install and get back to you

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

No branches or pull requests

2 participants