<frame04> tokens not detected for job attachments

[Kikkopanda]

Describe the bug

Seems to work with token but if you define any frame padding it does not work.

Expected Behaviour

Would expect the job attachments to be able to detect and evaluate <frame##> tokens as well to upload the material.

Current Behaviour

Frames with paths that used <frame##> tokens do not get detected and are not uploaded to job attachments.

Reproduction Steps

Create a node that uses a path that has <frame##> token in it

Environment

At minimum:

1. Operating system (e.g. Windows Server 2022; Amazon Linux 2023; etc.)
   Submitting from Windows 11 Pro
2. Version of Maya
   Maya 2024.2, 2025, 2026
3. Version of this package
   0.15.12
4. If this is from a version installed by the Deadline Cloud Submitter installer, then what version of the submitter installer?
   I'm using the downloaded package from this git repo and loading it via .mod files

Please share other details about your environment that you think might be relevant to reproducing the bug.
The specific issue we came across is for a vray proxy node that's loading an .abc cache for which it's been cached out for each frame of the sequence. We're using vray 7.2

[leongdl]

@Kikkopanda can you please provide an example job template? We do support wildcards like *, would * fit your use case?

[Kikkopanda]

Unfortunately * did not work with the VRayProxy nodes. I believe it's just a matter of updating or adding another re expression in assets.py to capture and expand or <frame\d*> patterns to add to the assets list and maybe update the findAllFilesForPatterns function in utils.py.

Wtih the holidays I haven't had a chance to fully test it out but in a week or so I could probably take a closer look

[leongdl]

Thank you @Kikkopanda - any additional information would be super helpful. We will also try to triage the issue and reproduce it.

[Kikkopanda]

Hello, I've been working with yuanmich2 on something else in email and he pointed me to the pull request https://github.com/aws-deadline/deadline-cloud-for-maya/pull/259/files which when I look at what was done in there it is similar to what I did to get our local deadline maya submitter code to recognize the cache paths with and tokens in thier path names however I used regex to capture cases for <frame\d+> as well which the current iteration of the code in the pull request would not catch for this scenario.