1. Company news

    1. 19
      posts
  2. ftrack Studio (main app)

    1. 1,210
      posts
    2. 1,237
      posts
    3. API

      1,728
      posts
    4. 627
      posts
    5. Actions and Widgets

      Extending the functionality in ftrack with custom Actions and Widgets - read more at ftrack.com/actions

      279
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      28
      posts
  3. ftrack Review

    1. 98
      posts
    2. 112
      posts
    3. 26
      posts
  4. Connect and plugins

    1. 400
      posts
    2. Connect package releases

      Notes on the latest Connect releases.

      7
      posts
    3. 146
      posts
    4. 324
      posts
    5. 49
      posts
  5. Tech preview

    1. API

      18
      posts
    2. New integrations

      Discussions of the new tools that will replace current Connect integrations into Nuke, Maya, 3DS Max and other applications.

      31
      posts
    3. 31
      posts
    4. 3
      posts
  • Popular Contributors

    Nobody has received reputation this week.

  • Status

  • Who's Online (See full list)

    There are no registered users currently online

  • Recent posts

    • I recently came across the news that CentOS 8 is effectively being killed, so the last production release of CentOS will be CentOS 7. The end-of-life for CentOS 7 is 2024. I know that future versions of Ftrack will be distributed as Kubernetes Helm files. As a consequence of these changes to CentOS it's very likely that our studio will run Kubernetes on Ubuntu instead of CentOS. Will there be Ftrack documentation to support other OSes besides CentOS 7? Reference: https://blog.centos.org/2020/12/future-is-centos-stream/
    • How is the progress on this? 
    • The docs for on-prem installation recommend using Sentry for error handling, so we've set that up for our studio. I've noticed that Sentry collects at least 3 or 4 errors every day but they are all related to internals of the Ftrack server so there's nothing here that we can really fix. Is there some system for sending these errors to Ftrack devs periodically?
    • Hey Peter, What you're running in to is the fact that populate() constructs a query using that attribute string, and we don't support typecasting in a projection. see https://bitbucket.org/ftrack/ftrack-python-api/src/23f582cd146e71f871ba8a17da30c0ad831de836/source/ftrack_api/session.py#lines-1070 We do support passing a list, tuple or QueryResult, so my workaround would be something like the populate line in this snippet. The rest is just included to set up my example / test. shot = session.query('select children from Shot where children is_not None').first() session.populate(shot['children'][:], 'status') with session.auto_populating(False): print(shot['children'][0]['name']) print(shot['children'][0]['status']) I suppose the root cause of all this is that children maps to Contexts, which can include Projects, which themselves do not have statuses.