Leo Gallucci
Leo Gallucci
+1 also can't reproduce it, non-deterministic so far 
I don't follow why it uses the IP to connect, in K8s the Hub's pod can die every now and then and the new Hub pod will have a different...
That log was for the same user
So could be pointing to an old IP, should point to the service domain name instead https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
Please don't worry about my fork, I'm doing some Jinja magic in the meantime (not using my fork anymore).
There is already a concept of `groups` in the API, this could be leveraged 
### Problem trying to be solved https://github.com/ideonate/cdsdashboards allows users to share interactive Jupyter Dashboards however when a person leaves the company his/her dashboard may no longer be available as his/her...
Maybe @danlester also has some ideas
+1 for JSDocs support for inline documentation, e.g. on how it looks in IntelliJ: 
Thanks @kokorin ! what about final file size, CPU usage and browser compatibility in comparison with the current setup?