bytedance/deer-flow

[Stability][BUG-010] Workspace negative performance timestamp runtime error

Geschlossen

#3.121 geöffnet am 21.05.2026

 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Python (9.005 Forks)batch import
help wanted

Repository-Metriken

Stars
 (67.767 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 2T 5h) (229 gemergte PRs in 30 T)

Beschreibung

Parent stability dashboard: #3107

This issue tracks BUG-010 from #3107.

Problem

Opening the workspace can trigger a full-screen Next.js runtime error overlay:

Runtime TypeError
Failed to execute 'measure' on 'Performance': 'WorkspacePage' cannot have a negative time stamp.

Representative frontend log:

Source: frontend browser console log captured by the local frontend service.

[browser] Uncaught TypeError: Failed to execute 'measure' on 'Performance': 'WorkspacePage' cannot have a negative time stamp.

Impact

  • A tester/user can see a framework error instead of the workspace.
  • It disrupts the core entry flow even if persisted thread data is not corrupted.

Open question

This needs confirmation outside the local dev/Turbopack-style environment. If it only happens in development, it may be lower priority; if it can happen in the Docker/release path, it should be fixed before stable tagging.

Contributor Guide