Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not find resolver timestamp on LakeFs server for application: maya/2025 #60

Closed
2 tasks done
Jeremyball opened this issue Oct 2, 2024 · 2 comments
Closed
2 tasks done
Assignees

Comments

@Jeremyball
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

Running maya2025 via launcher

ayon_usd gets stuck on this:

ValueError: Could not find resolver timestamp on LakeFs server for application: maya/2025

Expected Behavior:

Maya 2025 opens

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

  1. run launcher
  2. navigate to asset
  3. run maya2025

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

>>> [ Will add environments for apps and tools: maya/2025 ] 
>>> [ Opening of last workfile was disabled by user ] 
>>> [ It is set to not start last workfile on start. ] 
>>> [ Using resolver from LakeFS: lakefs://ayon-usd/v0.1.0/AyonUsdResolverBin/MayaWin/Maya2025_Py311_Win_Windows_AMD64.zip ] 
*** WRN: >>> { ActionsModel }: [ Action trigger failed. ] 
==============================
Could not find resolver timestamp on LakeFs server for application: maya/2025
==============================
Traceback (most recent call last):
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\core_0.4.4\ayon_core\tools\launcher\models\actions.py", line 405, in trigger_action
    action.process(selection)
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\action.py", line 116, in process
    self.application.launch(
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\defs.py", line 306, in launch
    return self.manager.launch(self.full_name, *args, **kwargs)
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\manager.py", line 173, in launch
    return self.launch_with_context(context)
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\manager.py", line 149, in launch_with_context
    return launch_context.launch()
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\manager.py", line 597, in launch
    self.run_prelaunch_hooks()
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\applications_1.0.1\ayon_applications\manager.py", line 581, in run_prelaunch_hooks
    prelaunch_hook.execute()
  File "C:\Users\$USER\AppData\Local\Ynput\AYON\addons\usd_0.1.0\ayon_usd\hooks\pre_resolver_init.py", line 48, in execute
    raise ValueError(
ValueError: Could not find resolver timestamp on LakeFs server for application: maya/2025

Additional context:

No response

@BigRoy BigRoy self-assigned this Oct 2, 2024
@BigRoy
Copy link
Collaborator

BigRoy commented Oct 2, 2024

@Jeremyball thanks for trying this out.

Did you have the (still private) LakeFS keys configured?

ayon+settings://usd/lakefs/access_key_id
ayon+settings://usd/lakefs/secret_access_key

It's likely that those are not configured in this case because it would currently throw the same error message.
(Since #61 that would log a warning, but it still would just report it couldn't find a timestamp or any items instead of saying "couldn't connect" - I'll make a separate issue to track that -> that's here now: #62.)

You'll need to request the private keys via Ynput Community discord currently as per the initial release announcement.

@Jeremyball
Copy link
Author

Sorry didn't see that. Yep no keys configured. I will head over to discord and flip you a message. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants