roshan
roshan
Hey! I fixed the bug on my local branch but I am unable to push the branch to upstream to make a PR. I require permissions!
Yikes, that's my bad. Just added a PR.
Facing something similar, did you manage to fix it?
Are there any updates on this issue? Our use case is running heavy inference/scientific workflows inside nested containers on a Kubernetes pod.
Thanks for the prompt reply - appreciate it! Would love to know to find out when you guys start work on this, happy to help test it out.
Not sure, to be honest. I was able to reproduce it with: 1. React renders component -> first websocket connection is established 2. React re-renders component -> second websocket connection...
Closing didn't seem to work, unfortunately. I moved some stuff around so the component actually removes and creates new websocket connection on re-render, but still running into a similar issue....
Closing this issue, managed to fix it with improvements to session handling outside of the Websockets library
follow up issues after more experimentation, not sure if related: - uvm doesn't work when computing pca for a large dataset (64736, 24929) in our case, - crashes with `CUSOLVER_STATUS_EXECUTION_FAILED`...
thanks for the detailed reply! do you know if there is a workaround for forcing the creation of a new context/garbage collection at the api-level - maybe something akin to...