It seems that an update broke nbproject on Google Vertex AI

[falexwolf]

[falexwolf]

It worked in #170

It runs:

[falexwolf]

I tested nbproject 0.3.1 on the current Google Vertex and it shows similar problems as the current nbproject.

Hence, it seems to be due to an update on GCP.

[Koncopd]

Hm, the error is pretty strange, i will check.

[Koncopd]

Very strange behavior indeed. The problem above is caused by ipylab not working, the notebook wasn't saved by the command and this is why nbproject read the unsaved empty notebook and threw the error. So we probably need to check at the beginning if ipylab works and treat the environment like classic notebooks if it doesn't.

So this is an ipylab bug. And now it starts to be really strange. When i have only one notebook at the start of GCP environments for notebooks (or how these things are called?), then for the first notebook ipylab indeed didn't work. For all following notebooks ipylab and thus nbproject worked just fine with all interactive features. Then i deleted all created notebooks, and created a notebook again and again ipylab didn't work. But then again for all notebooks which i created after it started working again. So it seems that in some cases JupyterFrontEnd just didn't load. I haven't faced the problem locally though.

https://github.com/jtpio/ipylab/blob/main/examples/commands.ipynb
It seems that JupyterFrontEnd might not initialize immediately, maybe this happens in GCP from time to time.

[Koncopd]

0.5.1 should work for both user-managed and managed notebooks.
https://github.com/laminlabs/nbproject/blob/main/docs/index.md has the installation instructions.

[Koncopd]

managed notebooks

We had also a problem before with identifying filename, on managed notebooks servers are not queryable. Now in these cases ipylab is used.

[falexwolf]

This is great, Sergei!