TypeError: 'NoneType' object is not callable

🐛 Bug

(compiler_gym) zeyi@server121:~/scripts$ python main.py 
Exception in thread Thread-1:
Traceback (most recent call last):
  File ".../lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File ".../lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File ".../lib/python3.8/site-packages/aim/ext/resource/tracker.py", line 102, in _stat_collector
    self._track(stat)
  File ".../lib/python3.8/site-packages/aim/ext/resource/tracker.py", line 78, in _track
    self._track_func()(
TypeError: 'NoneType' object is not callable

To reproduce

Minimum example:

from aim import Run


def main():
    run = Run()
    for i in range(1000):
        run.track(i, name="loss")


if __name__ == "__main__":
    main()

This problem happens occasionally. In my case it happens one out of four times. However, if I change the script slightly, the problem above never appears.

from aim import Run

run = Run()

def main():
    for i in range(1000):
        run.track(i, name="loss")


if __name__ == "__main__":
    main()

Notice that I moved the variable run into global scope. I think the problem is due to some objects are de-referenced too quickly (e.g., the thread used to track? I’m not sure).

Expected behavior

The script should run without problem.

Environment

aim==3.4.1
aimrecords==0.0.7
aimrocks==0.0.10

Python 3.8.12

Linux server121 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[uduse]

@alberttorosyan Yeah I can’t reproduce this problem with the new version of aim 👍 nice fix

[uduse]

No I don’t call those functions explicitly. Could it be a concurrency problem? I’m having multiple async functions and each one of them has their own aim.Run object.