Siddhant Sadangi

Hey @NiklasKappel 👋 This is a known issue and is already in the engineering backlog to fix ✅ Usage-wise, this should not have any impact, as the error is basically...

Hey @rkinas, This issue is currently in the engineering backlog. However, as mentioned earlier, this _error_ typically does not have any negative impact on logging, so it is not considered...

If this is crowding your console output, you can silence Neptune messages using Python `logger`: ```py import logging logging.getLogger("neptune").setLevel(logging.CRITICAL) ``` Note that this will silence **ALL** Neptune messages, including Run...

Hello @GuangShuaiWang 👋 Thank you for reporting this issue! Could you please provide us with more details: **1. Describe the bug** A clear and concise description of what is the...

Thanks for sharing the details 🙏 Can you also share the version of `neptune` or `neptune-client` that you are using?

I was able to reproduce the issue with `jupyterlab==4.0.2`. Looks like the widget does not support `jupyterlab>=4.0`. I've forwarded this issue to the relevant teams. While we work on it...

That's great to hear 🎉 I will keep this issue open till we do not add support for `jupyterlab>=4.0`. If you have any questions/suggestions about `neptune-notebooks`, feel free to put...

I'm closing this as our Jupyter integration has been deprecated, and we don't intend to update the widget to support newer versions of JupyterLab in the foreseeable future.

You can follow updates to this issue here: https://github.com/neptune-ai/neptune-client/issues/1702 Be assured, though, that this "error" does not lead to data loss. It is merely caused by the training and validation...

Hey @raethlein Thanks for the quick response! Yes, it does work if imported as stated in the docs. However, it'd be great if this change can be highlighted in the...