Request timed out - Application loads but non-responsive canvas

Aperta
  • Qualcosa non va?
#2,171 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
docker-compose, next.js, postgresql, typescript
Ambito
databases, full-stack

Direzione di ricerca

Start by reproducing the non-responsive canvas with the supplied Docker Compose setup and inspect the browser and container logs around the reported request timeout. The report does not identify a relevant source file or test, so trace the failing request from the canvas interactions; done means users can add and remove workflow nodes and execute a workflow.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Describe the bug
Application does not respond to any interactions, and I cannot add any nodes or remove the initial trigger node.

To Reproduce
Steps to reproduce the behavior:

  1. git clone project
  2. copy .env.sample file to parent directory of sim project
  3. replace postgres at the end of Database variable with "simstudio"
  4. add the 4 keys requested
  5. docker compose -f docker-compose.prod.yml up -d
  6. access the application
  7. Sign-up for new account
  8. login
  9. interface loads but non-responsive when trying to add or remove any items to canvas area

Expected behavior
Ability to add new nodes to workflow and then execute.

Screenshots
If applicable, add screenshots to help explain your problem.
the migrations container does read exited everytime I try to run.

Additional context
Docker Logs:tacit@ubuntu:/media/storage/sim$ docker compose -f docker-compose.prod.yml logs -f
WARN[0000] The "COPILOT_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "SIM_AGENT_API_URL" variable is not set. Defaulting to a blank string.
migrations-1 | $ bunx drizzle-kit migrate --config=./drizzle.config.ts
migrations-1 | Reading config file '/app/packages/db/drizzle.config.ts'
migrations-1 | Using 'postgres' driver for database querying
realtime-1 | 2025-12-03T16:34:57.024Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
realtime-1 | 2025-12-03T16:34:57.024Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
migrations-1 | [⣷] applying migrations...{
migrations-1 | severity_local: "NOTICE",
migrations-1 | severity: "NOTICE",
migrations-1 | code: "42P06",
migrations-1 | message: "schema "drizzle" already exists, skipping",
migrations-1 | file: "schemacmds.c",
migrations-1 | line: "132",
migrations-1 | routine: "CreateSchemaCommand",
migrations-1 | }
migrations-1 | {
migrations-1 | severity_local: "NOTICE",
migrations-1 | severity: "NOTICE",
migrations-1 | code: "42P07",
migrations-1 | message: "relation "_drizzle_migrations" already exists, skipping",
migrations-1 | file: "parse_utilcmd.c",
migrations-1 | line: "207",
migrations-1 | routine: "transformCreateStmt",
migrations-1 | }
db-1 |
db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
db-1 |
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: starting PostgreSQL 16.11 (Debian 16.11-1.pgdg12+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: listening on IPv6 address "::", port 5432
db-1 | 2025-12-03 16:34:48.748 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db-1 | 2025-12-03 16:34:48.758 UTC [29] LOG: database system was shut down at 2025-12-03 16:19:16 UTC
db-1 | 2025-12-03 16:34:48.773 UTC [1] LOG: database system is ready to accept connections
simstudio-1 | ▲ Next.js 15.4.1
simstudio-1 | - Local: http://localhost:3000
simstudio-1 | - Network: http://0.0.0.0:3000
simstudio-1 |
simstudio-1 | ✓ Starting...
simstudio-1 | ✓ Ready in 262ms
simstudio-1 | Accessing resource attributes before async attributes settled
simstudio-1 | Accessing resource attributes before async attributes settled
simstudio-1 | 2025-12-03T16:35:03.154Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:03.154Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:12.083Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:12.083Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
simstudio-1 | {"message":"Request timed out","stack":"Error: Request timed out\n at (file:///app/apps/sim/.next/server/chunks/node_modules@opentelemetry_5e131325._.js:1:3170)\n at emit (node:events:92:22)\n at emitCloseNTAndComplete (internal:http:82:58)\n at processTicksAndRejections (native)","name":"Error"}

Lingua principale
TypeScript
Stelle
29.8k
Fork
3.9k
Merge medio
1h 44m
PR unite (30g)
841

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di simstudioai/sim

Tutte le issue di simstudioai/sim

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.