I’m currently investigating the cause of the ftrack api spamming me with debug logging, and it specifically appears whilst publishing. Its generating so many log outputs that I believe its slowing the process down quite a bit.
Now this might be completely unrelated to Pyblish, but so far I’m struggling to find what could be causing the logging for ftrack to be set to debug. As far as I can tell, the output only happens during Pyblish publishing. For example I’ve just taken a section of code from an integration plugin and run it from within nukes script editor, and no output was generated at all while creating entities through ftrack. Interestingly I’m not getting the same result in 3dsmax, running the same code. However I seem to recall the debug messages appearing about the time I started using Pyblish, however that could be completely coincidental.
So I guess my questions are:
- Is there any chance\seems reasonable that Pyblish could be related to my problem.
- Is there a way to turn Pyblish’s logging off, (purely for testing purposes.) I’ve tried
logging.getLogger("pyblish").setLevel(logging.WARNING)in order to reduce them, however it still seems to generate the pyblish Info logs as well as the pesky ftrack ones.
I appreciate this is a long shot, but thought it might be worth asking here. In truth I suspect the answer must be buired somewhere in our own internal code, but I’ve been performing text searches across the whole lot for likely suspects.