-
Notifications
You must be signed in to change notification settings - Fork 60
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
"deploy_semantic_model" function #335
Comments
Thanks for raising the issue. Somehow this bug came back. Made a PR to fix it. |
Hi, just wanted to know if this issue is fixed. |
Hi, thank you for checking in. I am unfortunately still experiencing the issue. The function worked fine when I tested it the first time today, but then when I re-ran it on a different deployment case it threw the same exact error. My syntax:
Note: '###' in the code above is just an abstraction for the real variable values I am using. |
A PR has been made. The fix will go in the next release. Also, always do %pip install, not !pip install. |
Fixed in 0.8.10. |
Thank you so much! |
Hello,
I started experiencing issues while using the "deploy_semantic_model" function in the "semantic-link-labs" library.
I used this function to deploy semantic models across different workspaces, and it used to work perfectly until a couple of days ago.
What I now get when I use the function is the following error:
" create_semantic_model_from_bim() got an unexpected keyword argument 'overwrite' "
I checked the syntax multiple times, it is correct and as per documentation:
sempy_labs.deploy_semantic_model(source_dataset: str, source_workspace: str | None = None, target_dataset: str | None = None, target_workspace: str | None = None, refresh_target_dataset: bool = True, overwrite: bool = False)
I have tried removing the "overwrite" value from the function arguments - it is the one that seems to create problems - but didn't help.
As I said, this used to work until very recently - could it be related to any ongoing upgrades of the "semantic-link-labs" library?
Thanks so much in advance!
The text was updated successfully, but these errors were encountered: