Lorenzo Angeli

Hi @John Su, please have a look in here, by the end you'll find instructions on how to access the logs. Cheers. L.

Hi @guiramalho , this seems to be a file from the nuke studio integration . The code for the thumbnail in there is quite simple and pick the mid frame, please feel free to drop an email to support with suggestions on how it should behave and we'll be looking into it. Cheers. L.

No python api session in browser, the information between the desktop (path) and the server will be transmitted through the event system.

Hi @John Su, I'll check this asap. Would you mind sending the logs to support@ftrack.com ? They might contain some sensible information. Cheers. L.

The environment variable will tell the session object where to pick up its plugins (the resolve in this case). The resolve will then submit to the server the information on how to represent the component path through the event I've been linking you previously. Hope it makes more sense this way. L.

Hi @John Su, sounds strange should work, but I'll double check. out of curiosity what size were these files ? Cheers. L.

Hi @John Su, you can find some more information about the plugin ftrack environment paths here. Overall though the env does not have to be known by the server as is up to the session object to discover it and put it to the use. The resolve scripts uses the ftrack events to notify the server about the resolved path of the component . ftrack event system is quite powerful and I'd suggest digging deeper looking in here. You can also find more examples on how to use events in our recipes repository. Hope it helps. L.

HI @Jakub Trllo, >> I hope this issue is not caused because we don't have newest ftrack_api version I've been checking this with the one of latest api (1.8.0), but I would expect the same behaviour from previous versions too. If you suspect is an api version issue please let me know what version are you using so I can try to replicate. >> Api do not return `None` if default value is set  Setting the default value on the custom attribute indeed override the None if the value is not set, that's what is for. >> If value is not set, `None` should be returned If you want it to return None, you simply have to leave the default value empty, tested now and seems to be working as expected. >> [....] if all parents don't have set that custom attribute's value then default should be returned like values in web app. On checking the previous hierarchy item, that's something I'd leave to the coder to implement as custom logic , rather than providing it by default (as it might cause confusion) Hope it helps! L.

Hi @Jakub Trllo the only thing which might be happening is a bit of slowdown, but this won't impact the robustness of the overall system. If there's any doubt let us know. Cheers. L.

Hi @Jakub Trllo, look like you hit a genuine bug there ! Thanks for reporting, we will soon start looking into it. For now though you can use this workaround (see the session.reset() before the last commit) task = session.query('Task').first() user = session.query('User').first() # This will work as expected task.create_note('Note 1', user) session.commit() task.create_note('Note 2', user) session.commit() note3 = task.create_note('Note 3', user) session.commit() note3.create_reply('Reply 1', user) session.commit() task.create_note('Note 4', user) # here is the fix session.reset() # reset the session session.commit() # On this line Hope it helps! L.

@John Su if you want this to be working for everyone, $FTRACK_EVENT_PLUGIN_PATH should be set on each machine , and should be pointing to a shared folder on the network path. If on the other hand you just want to test it by yourself you can drop it in the local plugin folders under a hook folder (please note this applies also on the shared one). If you are still having issues please let us know and we'll try to further help you out. Cheers. L. ps. Best of course is to extend the environment and not to replace it , so something like: FTRACK_EVENT_PLUGIN_PATH=$FTRACK_EVENT_PLUGIN_PATH:/your/central/path

Hi @AlexOddbratt, overall your approach seems right. For general actions though, I'd suggest having a looking into our helper class in there you can find a helper function that might help you out narrowing down the entity type you are after. For what concerns custom attributes I'd suggest having a look a the query projections as might be a good way to speed it up. Hope it helps. L.

Hi @John Su, you don't need to have ftrack connect running to have actions and events. You can run them as simple python scripts (as long as they can access the ftrack-python-api). 1) no it should jut work 2) In here you can find many examples on how to run events and actions as standalone. Hope it helps. L.

Thanks @Michael Habenicht I'll check if there's anything we can do to ease these issues . Cheers. L.

Hi @John Su, sure you can ! just extract the given script (or download it directly from here ) and drop it in a folder mapped in a FTRACK_EVENT_PLUGIN_PATH environment variable. When the session start will look into that variable to see if there's any plugin to be discovered and run. I'd suggest having one folder on a shared server folder mapped so you can simply drop events in there. Hope it helps. If you need any further help just let us know ! L.

Installing and testing the api in Blender Go to the blender's python folder (blender <version>/<version>/python/bin/) Ensure pip is installed with: ./Python3.7m -m ensurepip Install the api using pip: ./pip3 install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 as alternative is possible to run the pip module directly from python with: ./python -m pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 If you want/need to have this included in your requirements.txt you can use the the pip editable syntax as such : (in your requirements.txt) [...] someothermodule >= 0.2 -e git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3#egg=ftrack-python-api [...] Launch Blender and open Python Console to test the api

Hi @TTT there's no need to install it locally to each machine. This event can be easily hosted on a central network folder and mapped into the FTRACK_CONNECT_PLUGIN_PATH Hope it helps. L.

Hi @John Su, the path is resolved through an event available in ftrack_connect itself and called resolve.py If the path is red is possible that your structure cannot be properly initialised and hence not be resolved. You can try adding more logs into the resolve.py and see if anything is off. Please send us , either here or through support (depending on how sensible the information are) and we'll look further into it. Hope it helps. Cheers. L.

I'd like to report here , for other users which might find similar issues, the root cause which has been resolved through the internal ticketing system. Here the full reply from our developer: we are looking now on how to properly fix this for an upcoming api release.

Hi @tweak-wtf sadly there's no easy way for us to replicate this issue. We'll be looking though, to improve the error logging in the api to present a more complete report. Let us know if you have any progress on this. Cheers. L.

Hi @instinct-vfx, glad to hear! Please feel free to report any issue or notes about your experience with them. Cheers. L.

Hi @tweak-wtf , thanks for reporting back , and good idea to raise the overall logging level ! Sadly though, I cannot see anything in the errors that would help pin point the root cause. As the error seems to be happening from within the plugin only, and not from a plain shell or plain maya, I'd suggest have the pyblishs developers involved. If you get any further information coming out from them, please feel free to report here so we can cross examine the results. As last thing , could you please check what interpreter pyblish is using adding at the beginning of your script: import sys print sys.executable In the meanwhile we'll keep looking on potential causes on our side. L.

@tweak-wtf could you please try with a simple standalone python script rather than from within maya to see if you can replicate ? Thanks !

Hi @tweak-wtf sorry to see you are having problems. The error seems to be coming from a wrong deserialization of the server response (json) relative to the storage scenario. This could be caused by a variety of things related to the network itself (proxy, firewall etc....) Could you please check if any of these changes have been put in place before this error have started happening ? I've trying to replicate it with you same version of the ftrack-python-api without success so far. Looking forward to hear more from you ! In the meanwhile we'll keep looking for other potential reasons. L.

@sconlogue@czarnowski.com it might well be to be fair. Deadline integration is not something we maintain, and I fear might still be using old api under the hood. If you do have any update from Thinkbox let us know, might be handy for other users facing the same issue. Cheers. L.