Jump to content
  1. Company news

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

    1. 1.2k
      posts
    2. 1.3k
      posts
    3. API

      1.7k
      posts
    4. 631
      posts
    5. Actions and Widgets

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

      280
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      28
      posts
  3. ftrack Review

    1. 98
      posts
    2. 113
      posts
    3. 30
      posts
  4. Connect and plugins

    1. 402
      posts
    2. Connect package releases

      Notes on the latest Connect releases.

      7
      posts
    3. 156
      posts
    4. 328
      posts
    5. 49
      posts
  5. Tech preview

    1. API

      18
      posts
    2. Connect 2.0 beta

      Forum to discuss bugs related to Connect 2.0 beta. 

      1
      post
    3. New integrations

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

      31
      posts
  • Recent posts

    • caching the session as weve been having some crashing issues that seem to be keeping the session open, so current thought process was to cache the session which will allow me to exit it later if need be. Unless theres a kill all session kinda command i dont know of 
    • @Jason Porath  I found quite fine running running unit and functional tests on test projects right on production server. It is quite easy to construct any context with ftrack_api and release it after tests finished. In worst case you will got a bunch of test entities on test project that no one cares. so feel free to: @pytest.fixture def session():     return ftrack_api.Session()   @pytest.fixture def context(request, session😞     context = session.create('Folder', {'parent_id': ..., 'project_id': ..., 'name': ...})     def finalizer():         session.rollback()         session.delete(context)         session.commit()     request.addfinalizer(finalizer)     return context The better approach is to running tests on staging ftrack server that should have relative fresh database snapshot from production, that is much more complex. 
    • Hi Peter, what's your use case? Just caching objects (or some other server state) locally or something else?
    • @Toby Angwin @kristin you should be in now. Sorry for the delay ! 
  • Popular Contributors

×
×
  • Create New...