Request timed out - Application loads but non-responsive canvas

Offen
  • Stimmt etwas nicht?
#2,171 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
docker-compose, next.js, postgresql, typescript
Bereich
databases, full-stack

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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"}

Vorherrschende Sprache
TypeScript
Sterne
29.8k
Forks
3.9k
Ø Merge
1 Std. 44 Min.
Gemergte PRs (30 T.)
841

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus simstudioai/sim

Alle Issues in simstudioai/sim

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.