Stuck on an issue?
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.
Collaborators count sometimes off by one
See original GitHub issueCan’t repro, but often enough when I start a session the collaboratorsCount is set to 2, while no one else is connected.
I’ve checked the codebase, and the remote server, but can’t find any glaring mistake.
So keep an eye out.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Your Complete Guide to Using the Instagram Collab Feature
The original creator (with a public account) can tag another account (public or private) as a collaborator. The collaborating account can ...
Read more >Everything You Need to Know about Instagram Collabs
The Instagram Collab feature is accessible for all users regardless of their follower count. Can you add more than one collaborator on Instagram ......
Read more >The 6 keys to effective collaboration in the workplace
Collaboration in the workplace used to be limited to in-person brainstorms and project coordination. But the way we work is changing.
Read more >Collaboration tips - YouTube Help - Google Support
Access to intriguing shooting locations or interesting people. Choose compatible collaborators. Think beyond subscriber count. While a large subscriber count is ...
Read more >How to count total lines changed by a specific author in a Git ...
This is a nice tool to get the count for all authors at once, including commit and modified files count: sudo apt-get install...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think that’s already happening (when we close the tab, the sockets get killed off in a while). It seems the tab somehow keeps the sockets open across refreshes. But if that’s the case, it may be a bug in the browser, and we won’t be able to do anything about it. In fact, this is likely the case: I can’t repro in Firefox, only Chrome. So maybe investigate further and open a crbug.
Let’s reopen if someone will mention it again.