-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I tested presence in production and I want to give some feedback #12
Comments
Is it possible this happened right after a hot code reload? |
No. It was a live coding session during 1 hour aprox. And it was a cycle for all that long. |
No ideas ? :( |
A live coding session? What do you mean by this? |
Oh lol. It's just my product. CodersTV is made for live programming broadcasts 👍 |
Riight so the actual source of the running app wasn't what was being coded on? If not then I have no ideas, but the source code of presence is pretty trivial if you want to debug through it. |
Ok, I will put a lot of debugs in the source code to know what is exactly Gabriel Pugliese On Fri, Oct 11, 2013 at 12:03 AM, Tom Coleman notifications@github.comwrote:
|
Hardest thing ever to debug! 😢 |
Hey guys,
I've used your package on production on http://coderstv.com yesterday and I've noticed some strange behaviour in my use case.
I'm using the count of users in determined location of the page. For simplicity, suppose I'm publishing presences for everyone that are on
/
First, the code:
And the html that prints it:
I had a constant number of watchers of 20. But, sometimes it had shown 30-40 watchers for like 5 seconds and then go back to 20 and stays there for 1-2minutes. And it was a cycle.
I just want to know why would that happen and where of the code is probably doing that behaviour, so I can debug it.
The text was updated successfully, but these errors were encountered: