Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
🐛 BUG: Unable to distinguish tail message type from the websocket message payload
See original GitHub issueWhat version of Wrangler are you using?
0.0.0
What operating system are you using?
Mac
Describe the Bug
(sent here from the #do-alarms Discord channel by Matt @ cloudflare)
Please add a new field to every tail websocket wire protocol message to distinguish the various contexts now present in workers. Right now it is impossible to always tell the difference between eyeball requests, DO requests, cron requests, and now DO alarm requests [*].
Could be a type code number if necessary to keep the payload small.
Would be immediately useful, thanks! I don’t use wrangler, but use the WS directly.
* strictly speaking cron requests can be identified by the payload properties, but the others are often ambiguous
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Let me check. I’ll respond here tomorrow with more.
Yes they use the same tracing infrastructure.