Open rgbkrk opened 6 years ago
I think we just got burned by this with the nbinteract repository. @rgbkrk did you figure out a way to work around this from your side of things?
Yeah, we .close()
the event source after we get a freshly baked container. It wasn't an issue at the time, it just smelled like a likely operational problem waiting to happen.
it just smelled like a likely operational problem waiting to happen.
Is this still a problem?
If you leave the eventsource open after "ready" it continues launching more
Reproduction steps:
Not a crazy deal for me, I just happened to notice while hitting the event source API directly. My current code does a
.close
appropriately. Figured this should probably be cleaned up though.