All issues

Tracing spans missing on the worker-pool boundary#3016

New issue
Open
LELeon Fischercommented 4w ago

Is your feature request related to a problem?

Tracing spans missing on the worker-pool boundary — today the workflow on apothem 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: refactor

LEleon-fischerself-assigned this4w ago
LEleon-fischeradded the labelrefactor4w ago
LEleon-fischeradded a commit that references this issuefix(apothem): wire the new contract for #30165df2e7a4w ago
LEleon-fischermentioned this in#30704w ago
LELeon Fischercommented 2w ago

Pulled this locally, the workaround in the description is solid. Happy to land it as a follow-up.

LELeon Fischercommented 2w ago

Could we add a regression test before the patch lands? Otherwise this will resurface as soon as the surrounding cleanup happens.

LELeon Fischercommented 2w ago

Bumping priority — three customers hit this last week, two of them on the enterprise tier.

LELeon Fischercommented 2w 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.

Add a comment

M↓Markdown is supported