sashaouellet / helix Goto Github PK

Describe the bug
When creating a new "set," the new set does not show up in the set dropdown for assigning new props.
Also, when clicking "Set Membership" on a right click of an asset, no options appear.

To Reproduce
Steps to reproduce the behavior:

1. File>New>Set

2. Named "Kitchen" and "CharacterProp"

3. Ctrl+E for new asset

4. In set dropdown, no new set appears.

5. Right-click on any asset in the Asset List

6. Select "Set Membership"

7. No options appear

Expected behavior
Expected to create a new set with a specified name and then have that new set appear in the set list dropdown for a new asset/prop.
Expected to right click on "Set Membership" and have options to change the set container.

OS (please complete the following information):
Windows 10

Additional context
cmd.exe reads:
File "I:\Savannah\CollaborativeSpace\helix\python\helix\manager\viewer.py", line 407 in handleSetMembership
if s.id in el.setList:
AttributeError: 'Element' object has no attribute 'setList'

Can't use console "help" command without help.txt and the proper env set

The legacy asset viewer only shows assets from the specific container context a user is selecting, however the Global Asset Viewer is more robust and has nice sorting and filtering options.

The proposition is to merge the context-dependent filtering into the newer Global Asset Viewer and remove the redundancy of having 2 viewers.

the ability to rename assets in the asset list.

In order to increase clarity of what shot is what, the proposition is to add a new property to the shot object to keep track of a "name." The name will be a short (~10-15 character) text field that serves to add further clarification to a shot's number.

This avoids having to maintain an external mapping spreadsheet of shot number to shot "name".

The character and effects folder are too vague. We need dedicated filters that can separate rigs from character models. For the effects filter, add sub-filters for cloth, hair and destruction.

If you close out of a tab, say for example "asset list". The "window" (drop down menu at the top) does not recognize it as closed. To reopen the window you need to click on the name of whatever tab was closed twice in the "window" drop down to reopen.

Some investigation needs to occur to properly ensure that permissions are being obeyed by the task view UI. Notably, users should not be able to edit existing tasks if they don't have the permission node to do that.

Hey, per your request. but i also had a thought, could you add in the taskbar icon to help differentiate software thanks :)

Describe the bug
Publishing files makes the necessary files in the release directory however it cannot be inserted into the DB since it is expecting a "TEXT" field to not be null.

To Reproduce
Steps to reproduce the behavior:

1. Pick any asset
2. Right click > Publish...
3. Choose a file and hit publish
4. See error

Expected behavior
Should complete the publish and insert the PublishedFile object into the DB

The set asset is a little vague and is supposed to act as a container for other assets anyway. The proposal is to abstract its concept in a way that detaches it from being an asset, but rather is assigned to newly created assets. Sequences can then be marked with what "set" they belong to, and all child shots of the sequence inherit this attribute.

This makes it easier for us down the line to group assets together in a more sensible way for users in the DCC packages.

If we have info about what shot a user is working on, we can quickly grab all assets that are within that shot's set and present their latest published version in a sort of "shot manifest" view.

This requires an update to the sequence and asset DB tables with a new "set" column - this contains foreign keys to a new "sets" table.

A UI must be provided to the users to allow them to create "snapshots." Up front, we'd expect to want this for shots, but should be general enough to be repurposed for assets as well.

The idea is that users would create a snapshot of a shot by inputting a playblast, render, etc. and this would be stored as the latest snapshot of the particular shot. We can then aggregate all the latest versions and string them together for a dailies review.

Describe the bug
File path translation error occurs when importing any files for a new asset

To Reproduce
Steps to reproduce the behavior:

1. Go to File > Import asset...
2. Choose a folder, set a name for the asset, click import
3. See error

Expected behavior
Should import the files and translate paths properly to achieve that

Stacktrace
Traceback (most recent call last): File "/home/souell20/mount/stuhome/Helix/Helix-dev/python/helix/api/commands.py", line 750, in handleInput return main(cmd, argv[1:]) File "/home/souell20/mount/stuhome/Helix/Helix-dev/python/helix/api/commands.py", line 614, in main return importEl(**args) File "/home/souell20/mount/stuhome/Helix/Helix-dev/python/helix/environment/permissions.py", line 194, in wrapper return function(*args, **kwargs) File "/home/souell20/mount/stuhome/Helix/Helix-dev/python/helix/api/commands.py", line 235, in importEl el = Element(name, elType, show=env.getEnvironment('show'), sequence=sequence, shot=shot, clipName=clipName, makeDirs=True) File "/home/souell20/mount/stuhome/Helix/Helix-dev/python/helix/database/element.py", line 202, in __init__ os.makedirs(self.work_path) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib64/python2.7/os.py", line 157, in makedirs mkdir(name, mode) OSError: [Errno 13] Permission denied: '/i-drive/Savannah'

I am trying to make a camera asset for a shot. I am in the shot level and do file > new > asset. When I say create, I get this a window saying: "List index out of range."

Show the details says:
Traceback (most recent call last):
File "I:\Savannah\CollaborativeSpace\helix\python\helix\api\commands.py", line 930, in handleInput
return main(cmd, argv[1:])
File "I:\Savannah\CollaborativeSpace\helix\python\helix\api\commands.py", line 630, in main
return mke(**args)
File "I:\Savannah\CollaborativeSpace\helix\python\helix\environment\permissions.py", line 200, in wrapper
return function(*args, **kwargs)
File "I:\Savannah\CollaborativeSpace\helix\python\helix\api\commands.py", line 219, in mke
el = Element(name, elType, sequence=sequence, shot=shot, clipName=clipName, setName=setName, makeDirs=True)
File "I:\Savannah\CollaborativeSpace\helix\python\helix\database\element.py", line 205, in init
parentSet = parent.getSet()
File "I:\Savannah\CollaborativeSpace\helix\python\helix\database\shot.py", line 149, in getSet
return Set.fromPk(self.setId)
File "I:\Savannah\CollaborativeSpace\helix\python\helix\database\shot.py", line 196, in setId
return sq.getSet().id
File "I:\Savannah\CollaborativeSpace\helix\python\helix\database\sequence.py", line 116, in getSet
return Set.fromPk(self.setList[0])
IndexError: list index out of range

when creating a new asset instead of allowing each individual to create whatever name they want under whatever name. Force the 'set' to go in front of the asset name when the asset is finished being created.
When imputed the asset name would be something like: 'set'_'name'.mb
This would prevent there being a bunch of naming conventions in the asset list making it easier to navigate.

I misunderstood the use of "import asset" option as (import your new file to the database). It appears to be (update preexisting asset) or (upload new asset version).
Id recommend removing the "new" section under "file" and creating the "file" menu something like this:
File
Create Show
Create sequence
Create shot

   Create new asset
   Update asset version

   Export Assets (plural)

   Connect to database

Can you add the option to upload a file at the same time as creating the directory with the "file:new:asset".

Currently, we can only see the creation day and what version number were on. Seeing what day the last asset was published would be nice for files that are more constantly updated.