Azure / Azure/azure-webpubsub

Live trace issues

Open
#65 1 comment 0 reactions 1 assignee Claimed by @wanlwanl View on GitHub
bug-bash-round-1 livetrace
Dominant language
TypeScript
Stars
147
Forks
96
Avg merge
19h 28m
Merged PRs (30d)
87

Description

https://github.com/Azure/azure-webpubsub/issues/26
- [x] No live trace Client connection failed with bad request
Try connect client with an invalid hub name, client connect failed with 400 but live trace shows no logs.
fixed here https://msazure.visualstudio.com/One/_git/OSSServices-SignalR-PortalExtension/pullrequest/4367501

https://github.com/Azure/azure-webpubsub/issues/28
- [x] Live trace tool still has "Azure SignalR" in it
Repro steps
1. Create a Web PubSub resource
2. Go to diagnostic settings, click open live trace tool
3. Hover over to "supported services"
4. In the drop it says "Azure SignalR"
5. The docs and sdks are also pointing to SignalR docs
- [x] Live trace tool doesn't auto reconnect
Repro steps
1. Open live trace
2. Wait for some time until the websocket connection is closed
3. There will be a disconnected state showing on the top right corner of the page
4. There should be a better way to handle disconnect (either have some automatic reconnect or a better way to let user know client is disconnected) since disconnect here will cause logs to be lost.
- [ ] Live trace doesn't work all the time
Cannot consistently repro this, but some observations:
1. Unauthorized request (401) doesn't show in live trace (for most of the time, with a "Cannot read property 'hub' of null" error in console). There is a small chance that following message will be printed out:
> Sending message during operation {hub}=chat,{event}=connect,{category}=connections got unexpected response with status code 401. Detail:
2. Seems after the connection is closed and reconnected, it will stop receiving logs.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.