Ryan Bliss
Ryan Bliss
@stevenic that is probably fine. Only problem is that having it hardcoded into the SDK means it is difficult to change without sdk upgrades, so it is harder to resolve...
Now obsolete with #516
Should be fixed with #562...at least mostly. Might still be improvements we can make long term, but I think the new `AzureLiveShareHost` and `LiveShareRuntime` implementations together make this easier.
Any update on this? It's been down for a while now.
Makes sense. In the description of the `@isomophic-git/cors-proxy` npm package, it said the service was "generously sponsored by Clever Cloud". Perhaps assume that generosity has new memory limits 😆
@JessieLiroff also note that we do plan to support Live Share in GCC soon. Azure Fluid Relay is a relatively new Azure service, and the final certification it needs for...
@JessieLiroff Live Share should be supported in Live Share in GCC, please let me know if there are any other issues on your end. Closing for now :)
+1. Any update here would be greatly appreciated. P.S. I found this thread, not sure how relevant it is: https://groups.google.com/g/discuss-webrtc/c/pdJrg24joGA?pli=1
@pheidler yeah good catch, this is something we have fixed in our latest version of `2.0.0-internal.10`, probably should patch it into the current v1 as well. Good issue, will look...
@pheidler feel free to update to 1.4.1 / 1.4.1-preview.0 (for live-share-react and live-share-turbo). Fix should be up. Will close this issue once I've merged the PR.