-
Notifications
You must be signed in to change notification settings - Fork 74
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
Ban SamLau95/nbinteract-image #624
Conversation
This is the referrer causing the build requests: https://www.nbinteract.com/examples/examples_empirical_distributions.html It isn't causing any trouble yet but rather ban it now instead of have some problems over the weekend when everyone is away. cc @SamLau95 |
For reference the output of
|
@betatim perhaps this is another user who has left open the eventloop? That's what it was before... |
The weird thing is that there were no changes to the nbinteract code. So maybe a broken browser? |
well every now and then if a user of nbinteract leaves open their browser and the eventloop stays open, it'll just keep re-sending signals to binder to build, and this continues until the person closes their window :-/ |
The behaviour you describe sounds like a bug in nbinteract. Not sure I understand why nbinteract should ever leave the event source open unless there is a bug in nbinteract or the browser wrt closing the event source. |
Heya @betatim @choldgraf , I've attempted to replicate the thebelab implementation of EventSource handling in SamLau95/nbinteract#82. Can we unban SamLau95/nbinteract-image to see whether we get lower load? |
@SamLau95 sounds good to me...I'll do this now |
This bans SamLau95/nbinteract-image as they are using up their 100 slots (and more) if we let them.