Adam Lewis
Adam Lewis
looks like merging in main, broke many tests
Failing test appears unrelated to this PR since it's a playwright test and this PR makes no changes to the UI/UX other than the command line when running `nebari init`.
> @Adam-D-Lewis can you fix the merge conflicts when you get the chance? @marcelovilla done now
I'm not sure if this is due to an unspecified dependency version constraint somewhere upstream. Or if it has something to do with a conflict or missing dependency for something...
I suspect that this occurs when the jupyterlab version in the environment (installed automatically to whatever version conda solves for in this case) doesn't match the jupyterlab version the user...
BTW, the shared directory randomly showed up me for after a while in jupyter. I had previously ssh'd into the nfs pod and manually created the directory so I'm not...
I'm also interested in this.
It seems like we could possibly do some type of conversion from keycloak roles to jupyterhub roles similar to what we do in https://www.nebari.dev/docs/tutorials/argo-workflows-walkthrough#workflow-labels though that causes some other issues...
Thanks for contributing @zealousGnu. I'm not aware of any single-stack IPv6 Nebari deployments currently. It would be a worthwhile to support this, but there aren't any resources dedicated to this...
@marcelovilla Looks like the local integration test failed too. Is there an issue already open for that flaky test. I couldn't find one by searching the error message.