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

reset_shortcut_cache() generates error when workspace is not provided #444

Closed
NickyvVr opened this issue Feb 5, 2025 · 4 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@NickyvVr
Copy link

NickyvVr commented Feb 5, 2025

Describe the bug
TypeError: reset_shortcut_cache() missing 1 required positional argument: 'workspace'

To Reproduce
Steps to reproduce the behavior:

  1. Use labs.lakehouse.reset_shortcut_cache and don't provide a name or UUID

Expected behavior
I expected the function to run on the current workspace, because the parameter is optional

@NickyvVr NickyvVr added the bug Something isn't working label Feb 5, 2025
@m-kovalsky
Copy link
Collaborator

#443 will fix the issue regarding not having to specify the workspace parameter.

It seems there is an issue with the actual API. Contacting the product team about this. Please raise an issue with microsoft support as well regarding this API.

@NickyvVr
Copy link
Author

NickyvVr commented Feb 5, 2025

Will do, the API immediately gives the same error indeed, thanks

@m-kovalsky
Copy link
Collaborator

So there are actually 2 issues here. One is with the API itself. This is being investigated. The second issue is that semantic link retries 500 status codes (which is what this currently returns) many times - causing the failure to take 10 minutes. This is being worked on as well.

@m-kovalsky m-kovalsky self-assigned this Feb 12, 2025
@m-kovalsky
Copy link
Collaborator

Fixed in 0.9.3. The issue with the API still needs to be addressed by the product team at Microsoft. Closing this issue as that is out of my hands and not related to semantic link labs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants