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

Error on content import when creating destination folder #149

Open
drstrangelooker opened this issue Mar 12, 2024 · 4 comments
Open

Error on content import when creating destination folder #149

drstrangelooker opened this issue Mar 12, 2024 · 4 comments
Assignees

Comments

@drstrangelooker
Copy link
Contributor

drstrangelooker commented Mar 12, 2024

Hi @drstrangelooker @AdamMinton ,

I'm getting the same issue as @jtorreio.

However, it is happening when I run ldeploy content import. I get a generic looker_sdk error. As suggested, I tried gem update gazer and this did not resolve the issue.

Here is a screenshot of the error:

image

I've updated looker_deployer and looker_sdk and it hasn't done the trick either.

This is a high priority issue as we are blocked from deploying any Looker content to our instances. Can you please investigate?

Please let me know if you need anything from me. Thank you!

Originally posted by @jacobakh in #148 (comment)

@drstrangelooker drstrangelooker changed the title Hi @drstrangelooker @AdamMinton , Error on content import when creating destination folder Mar 12, 2024
@jacobakh
Copy link

Looker suggests in the API query_id update message that setting the Legacy Feature "Disallow Numeric Query IDs" to OFF should put the Looker instance back to its original state. Doing this has no affect on the issue I mentioned.

In addition, we are making no calls to the looker-sdk package, just the ldeploy content import.

Cheers

@drstrangelooker
Copy link
Contributor Author

Yes this is a different issue. ldeploy uses looker-sdk. Can you try updating to the latest version of looker-sdk with the command pip install --upgrade looker-sdk and try again. I would expect to get a more informative error message from the newest version of the sdk.

@jacobakh
Copy link

Hi @drstrangelooker ,

As mentioned above, I've already upgraded it. I did it again for safe measure, and I'm getting the same error when I run the ldeploy import command.

@jacobakh
Copy link

Hi @drstrangelooker @AdamMinton

Hope all is well. Following up on the above issue- Is there a timeline for the fix? Please let me know if you need anything from me. Cheers

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

No branches or pull requests

3 participants