Skip to content

Conversation

@vietj
Copy link
Member

@vietj vietj commented May 30, 2025

Motivation:

During a server WebSocket upgrade, the HTTP connection metric is not correctly set to the WebSocket connection metric.

This leads to calling the metric implementation with a null instance of the metric instead of the the instance it was provided.

Changes:

During the server WebSocket upgrade set the HTTP connection metric onto the WebSocket connection metric.

…ction metric during the server upgrade.

Motivation:

During a server WebSocket upgrade, the HTTP connection metric is not correctly set to the WebSocket connection metric.

This leads to calling the metric implementation with a null instance of the metric instead of the the instance it was provided.

Changes:

During the server WebSocket upgrade set the HTTP connection metric onto the WebSocket connection metric.
@vietj vietj added this to the 5.0.1 milestone May 30, 2025
@vietj vietj self-assigned this May 30, 2025
@vietj vietj added the bug label May 30, 2025
@vietj vietj mentioned this pull request May 30, 2025
@vietj vietj merged commit 27e488f into 5.0 May 30, 2025
7 checks passed
@vietj vietj deleted the fix-web-socket-missing-metrics-5.0 branch May 30, 2025 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants