You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #428 was released to use inform instead of send_resp as part of the websocket upgrade request, the conn is no longer updated with status = 101, so when it is passed to telemetry handlers at the end of the span, we no longer have a status to report.
Is there a way we could still update the status field in the conn without interfering with subsequent behavior?
The text was updated successfully, but these errors were encountered:
Since #428 was released to use
inform
instead ofsend_resp
as part of the websocket upgrade request, theconn
is no longer updated withstatus = 101
, so when it is passed to telemetry handlers at the end of the span, we no longer have a status to report.Is there a way we could still update the status field in the conn without interfering with subsequent behavior?
The text was updated successfully, but these errors were encountered: