Hi FunnyTurkey96
what's the clearml server you are using ?
Hi FunnyTurkey96
Any chance you can try to run with the latest form GitHub (i just tested your code and it seemed to work on my machine).pip install git+
I cannot reproduce, tested with the same matplotlib version and python against the community server
Well taking the file out of my git repo folder it seems to work perfectly. May it have something to do with the git integration and the uncommitted changes?
It seems to be stuck in the following step:
` $ python eraseme.py
ClearML Task: created new task id=fa3db29498f241a19de81b75f787887e
ClearML results page:
======> WARNING! Git diff to large to store (1327kb), skipping uncommitted changes <======
2021-07-11 19:17:31,351 - clearml.Task - INFO - Waiting for repository detection and full package requirement analysis
ClearML Monitor: GPU monitoring failed getting GPU reading, switching off GPU monitoring
2021-07-11 19:17:32,821 - clearml.Task - INFO - Finished repository detection and package analysis
2021-07-11 19:17:32,822 - clearml.Task - INFO - Waiting to finish uploads `
2021-07-11 19:17:32,822 - clearml.Task - INFO - Waiting to finish uploads
I'm assuming a very large uncommitted changes 🙂
seems like. I’m working with git only locally, with remote machine where the code actually runs (you know this pycharm pro remote). So for git integration I had to reproduce the git on the remote machine. and since it’s not updated regularly, the git diffs are large…
Do you have a better solution for the git integration for the way I work?
And anyway, the git diffs are logged long before, and still the reporting doesn’t upload, and I don’t see why it should.
with remote machine where the code actually runs (you know this pycharm pro remote).
Are you using the pycharm plugin ? (to sync the local git changes with clearml)
https://github.com/allegroai/clearml-pycharm-plugin
BTW:
======> WARNING! Git diff to large to store (1327kb), skipping uncommitted changes <======
This means all your git changes are stored as an artifact, which is consistent with the "wait for upload" message.
Thx! fixing the too-big-diff (due to a jupyter notebook) solved the issues.