Remus Avram

Members
  • Content count

    383
  • Joined

  • Last visited

  • Days Won

    11

Remus Avram last won the day on September 21

Remus Avram had the most liked content!

About Remus Avram

  • Rank
    ftrack ninja

Profile Information

  • Gender
    Male
  • Location
    Munich

Recent Profile Visitors

797 profile views
  1. Thanks @Mattias Lagergren for the quick answer. Right! Related issue. Different entity. Nice to hear that you are working on a fix
  2. index Ftrack database

    Hi @Mattias Lagergren, thanks for the advise. This means the database is already indexed by you as you think it's the best for the studios, right?
  3. job_updated action type

    Thanks @Mattias Lagergren for the explanation. What do you mean by job?
  4. job_updated action type

    Hi Ftrack Team, I see that there are 5 types of action: add, update, remove, move and job_updated. I am wandering for what job_updated is used for? Best, Remus
  5. automatically re-subscribe users to the actions

    Thanks @Mattias Lagergren for you answer. But is it possible to manually re-register all the plugins from a folder? For example i am updating the code of a plugin. In this way the plugin will not be registered again and the new code will not be in use. On the Ftrack server side we are checking every X minutes if there is new code pushed, and if it is, then it is re-launching the actions. Is it possible to do something similar for the Ftrack-Connect?
  6. index Ftrack database

    Hi Ftrack Team, I was checking the Ftrack documentation regarding the database and I didn't find anything about indexing it. Is the database already indexed by you as you think is the best, or do we need to re-index it based on the query logs? Best, Remus
  7. Create version 0 in Ftrack

    Thanks @Lucas Correia! In this way it works. I didn't think in this way
  8. If I create a new version and then I query the asset again, then the new version is not included in the asset['versions']. Example: asset = session.query("Asset where versions.task.id is '{0}'".format(task['id'])).one() print len(asset['version']) session.create('AssetVersion', {'asset': asset, 'task': task, 'version': 13, 'status': status, } ) session.commit() asset = session.query("Asset where versions.task.id is '{0}'".format(task['id'])).one() print len(asset['version']) ------- Returns 2 2
  9. Create version 0 in Ftrack

    Hi @Mattias Lagergren can you please give us an example? I tried like this: session.create('AssetVersion', {'asset': asset, 'task': task, 'version': 0, 'status': status } ) self._session.commit() Using version 0 will just create a new version, not version 0.
  10. Manage Roles

    Thanks @Mattias Lagergren!
  11. Manage Roles

    Hi @Mattias Lagergren any updates regarding this issue?
  12. reverting entities, and event loops

    Hi @keyframe we have this already implemented in our system. Let me know if you need any help with it.
  13. Thanks @Eric Hermelin for taking a look! Cleaning the session or re-populating the data works as a workaround. But for long term I hope it will fetch the right data once we query the shot again. There are too many places where we need to patch it, and for users which don't have experience in programming (artists), it's difficult to explain.
  14. Hi all, I have a shot queried from DB via ftrack_api. I update a custom attribute of the respective shot. Then, in the same session, I query the shot again. The custom attribute of the respective shot is not updated even after I queried the shot again. Please find below an example: def test_query_custom_attributes(self): def update_custom_attribute(test_asset): new_session = ftrack_api.Session() same_test_asset = new_session.query("AssetBuild where id is '{0}'".format(test_asset["id"])).one() same_test_asset['custom_attributes']['delivery_name'] = "unittest" new_session.commit() test_asset = self._session.query("AssetBuild").first() delivery_name = test_asset['custom_attributes']['delivery_name'] update_custom_attribute(test_asset) test_asset = self._session.query("AssetBuild where id is '{0}'".format(test_asset["id"])).one() new_delivery_name = test_asset['custom_attributes']['delivery_name'] self.assertNotEqual(delivery_name, new_delivery_name) self._session.cache.clear() test_asset = self._session.query("AssetBuild where id is '{0}'".format(test_asset["id"])).one() new_delivery_name = test_asset['custom_attributes']['delivery_name'] self.assertNotEqual(delivery_name, new_delivery_name) Clearing the cache and fetching the shot again from the database works.
  15. We were able to reproduce the issue `int() argument must be a string or a number, not 'Symbol'` and I can confirm that this is fixed. Tested in Ftrack version `3.5.6` with ftrack_api version `1.3.2`. Thanks for this fix