-
Notifications
You must be signed in to change notification settings - Fork 79
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
Failed to fetch semantic model #89
Comments
hey @LukaFontanilla - do you know what can be a reason for that ? thnx! |
@antfido was this issue fixed, i am also running into similar issue. @LukaFontanilla how can we fix the above issue. |
Nope, still stucked here @vijayram0690 |
@vijayram0690 did you solve it ? |
I assume this error is returned when the extension first starts up and not after a NL request is submitted? It would be helpful to understand what requests are failing. Can you please check the browser dev tools and both the "Console" and "Network" tabs and share any Looker specific errors you find there? Given the error message I would assume there is a failing Looker API call. It would be helpful to see what that is. As for the newer Explore Assistant deployment, there are 3 BigQuery tables that are provisioned -> explore_assistant_examples, explore_assistant_refinement_examples, & explore_assistant_samples. Each of these tables should have a row for the given model and explore you want to use with the Explore Assistant (we are no longer reliant on a single set of environment variables for this). Additionally each explore_id value should be in the format you listed, where the model name and explore name are separated by a single ":". |
Hey, so here are the screenshots from console: Thanks a lot for your help @LukaFontanilla . |
hey @LukaFontanilla - would you be able to look into that one ? Thnx a lot ! :) |
I'm having a similar issue. I think its related to my exploreKey having '::' in it instead of the expected ':' the code is looking for. |
@dassowmd it's just generic output of the error (defined wrongly) so I wouldnt bother about it. is it working for you know ? |
@antfido I think the issue is that the EXPLORE_ID in the .env file has a single colon, but Looker delimits with a double colon. I didn't catch it, which sent me down a rabbit hole. Once I figured that out it seems to be working fine. Would it be possible to validate that the EXPLORE_ID set in that file is properly formatted to only have a single colon? |
@antfido I tried pushing the feature, but can't on this repo. But I was thinking something like this in
Full file:
|
Hey,
I redeployed the extension (I couldn't find a bug in my former deploy), and now I'm getting an error as on the screen below:
Did anyone experience a similar error ? How did you handle it ?
I ran out what to change, my .env file looks good. Maybe I wrongly define example_id in examples ? I defines it as
<my_Looker_model_name>:<my_Looker_explore_name> . I don't add .model and .explore .
Thanks !
The text was updated successfully, but these errors were encountered: