All issues

Tracing spans missing on the worker-pool boundary#3013

New issue
Open
AMAmara Oseicommented 2w ago

Is your feature request related to a problem?

Tracing spans missing on the worker-pool boundary — today the workflow on wavelet requires an out-of-band step that breaks the editor flow and makes the API harder to type.

Describe the solution you'd like

Migrate the affected surface to follow the same contract as the rest of the toolchain, so composed flows stay consistent and predictable.

Describe alternatives you've considered

  • Keep the current implementation and document the seam.
  • Ship a codemod that rewrites call sites at install time.

However, both would still leave the surface on a different contract from the rest of the stack, and would only delay the cleanup.

Labels: performance

NOnoor-hassanself-assigned this2w ago
AMamara-oseiadded the labelperformance2w ago
AMamara-oseiadded this to the milestonev1.4 — Stability2w ago
YUyuki-tanakaadded a commit that references this issuefix(wavelet): wire the new contract for #30135d113382w ago
NOnoor-hassanmentioned this in#30662w ago
NONoor Hassancommented 1w ago

Re-reading the spec, I think the right contract is the one in the bug report, not the one we're shipping. Going to open a small PR.

YUYuki Tanakacommented 1w ago

Closing in favor of #3114 — same root cause, same approach, and that branch is further along.

NONoor Hassancommented 1w ago

I've seen this too. I'll fix.

YUYuki Tanakacommented 1w ago

Can confirm the repro on a clean checkout — the failing case is reliable on macOS 15.2 with Node 22.

Add a comment

M↓Markdown is supported