Open ischurov opened 3 weeks ago
Hey @ischurov π
Thank you for the detailed issue, and I am sorry you are facing this.
This issue is caused because Neptune tries to automatically log a few details when a run is initialized, like hardware monitoring, console logs, source file, git details, etc.
To prevent the NeptuneFieldCountLimitExceedException
error on initializing a run that has already reached the field-count limit, you will need to turn off all such logging, as shown below:
run = neptune.init_run(
with_id=run_id,
capture_hardware_metrics=False,
capture_stderr=False,
capture_stdout=False,
capture_traceback=False,
git_ref=False,
source_files=[],
)
This will prevent Neptune from trying to create new fields, and you'll be able to initialize the run to delete existing fields.
Please let me know if this works for you π
Describe the bug
I created a run with large number of fields, and now cannot do anything with it due to
NeptuneFieldCountLimitExceedException
preventing loading the run. Particularly, I cannot delete any fields to recover from this state.Reproduction
Create a run with more than 9000 fields. Then try to load this run:
Expected behavior
I expected the run to be loaded. If there is a limit on the number of the fields, I expected that I would be able to delete some fields and than save the run to the server. In fact, I cannot delete any fields, as I cannot load the run. Thus I do not see any ways to deal with that run at all.
Traceback
Environment
The output of
pip list
:The operating system you're using: MacOS Sonoma 14.4.1 (23E224) The output of
python --version
: Python 3.11.9