Possible bug with user sandboxes in Houdini

Hi, we use user sandboxes for keeping work files separated per user.
In Houdini for some time now we have been getting an error when trying to show others’ sandboxes:

_task_resolve_sandbox_users - failed: _task_resolve_sandbox_users() takes exactly 2 arguments (1 given)
Traceback (most recent call last):
  File "e:\bottleship\code\btltest3\install\app_store\tk-framework-shotgunutils\v5.7.6\python\task_manager\worker_thread.py", line 83, in run
    result = task_to_process.run()
  File "e:\bottleship\code\btltest3\install\app_store\tk-framework-shotgunutils\v5.7.6\python\task_manager\background_task.py", line 139, in run
    return self._cbl(*self._args, **self._kwargs)
TypeError: _task_resolve_sandbox_users() takes exactly 2 arguments (1 given)

The result is that sandboxes are not shown.

At first I suspected some version incompatibility, but now upgraded everything and it still breaks.

Any ideas?

tk-multi-workfiles: v0.12.3
tk-framework-shotgunutils_v4.x.x: v4.4.15
tk-framework-shotgunutils_v5.x.x: v5.7.6
tk-houdini: v1.7.2
3 Likes

Hey @mmoshev,

Just taking a blind guess before someone smarter chimes in, but could it be related to permissions? Does this happen for an admin user as well as an artist?

-David

2 Likes

@DavidMason thank you for the response.

Yes, I am an admin user, but happens to me as well. Rather it seems like the call pattern in shotgunutils is wrong - the callback takes 2 arguments, but shotgunutils passes one… something along those lines.

2 Likes

Now we are getting the same with Nuke, and there seems to be a problem with filesystem location registration.
Have not explicitly linked the two, but that would make sense.
It happens rarely, I wonder if it is caused by wrong registrations or something.

Still getting this in several DCCs, any ideas? Perhaps there was a non-compatible change in tk-framework-shotgunutils that the engines have not caught up with?

I’ve started seeing this issue since performing an app/core update 1 week ago.