All issues

TLS renegotiation fails against the new gateway#3010

New issue
Open
LNLNcommented 1w ago

Is your feature request related to a problem?

TLS renegotiation fails against the new gateway — today the workflow on millcreek 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: documentation

LNln-dev7self-assigned this1w ago
LNln-dev7added the labeldocumentation1w ago
LNln-dev7added a commit that references this issuefix(millcreek): wire the new contract for #30105b4e4361w ago
LNln-dev7mentioned this in#30591w ago
LNLNcommented 1w ago

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

LNLNcommented 1w ago

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

LNLNcommented 1w ago

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

LNLNcommented 6d 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