-
Notifications
You must be signed in to change notification settings - Fork 77
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
[Clarification] error likely related to .env variables #74
Comments
I have the same error, did you find a solution? |
@dennysrega1ado this seems to be like a standard error given out for any kind of error. There could be couple of possibilities for this.
LOOKER_MODEL=genai_test_model
If you are still having problem, then check network tab and see which API is failing and look the response to see where exactly things are erroring out. Refer this document for any other help: https://medium.com/refined-and-refactored/how-to-set-up-genai-x-looker-extension-under-15-minutes-explore-assistant-b1f918ed9c58 |
Hi, I was running into this error for a while but managed to get it working. I noticed in your post you said you "... have the dataset explore_assistant, one model, and two empty tables (no examples)" - I think that after following these instructions you should have three tables within your explore_assistant dataset (and the one model):
All three tables are required for the extension to work (and all three should be populated with a single row after following the instructions). The issue we actually ran into was when adding our explore_id as a flag when loading the json files, we just had the explore name when it should be the format modelname:explorename. As an example this would be the samples.json loading script: In response to your first question (which I imagine why your tables are currently empty), no, the notebook can be used to finetune your model for your particular explores - but just uploading the default json files in explore-assistant-examples will give enough context model to get you started, despite the fact the table/field names in them are unlikely to match up to your own. In response to your second question, I believe having the descriptions for all your dimensions/measures will help the model. Not too sure on the third question - haven't got there yet! Hope that helps |
I think you mean finance is the model, and orders is the explore name? |
Yep, you're right - edited it to correct. Thanks! |
We are attempting to set up the Looker Explore Assistant, but we are having difficulty getting it to work.
Initially, it appears to be a parameterization issue, but it might also be related to the example tables.
Error
Error Name:
TypeError
Error Message:
Cannot read properties of undefined (reading 'examples')
Diagnosis:
The error is likely related to your Look specific .env variables.
Troubleshooting Steps
Check the LOOKML_MODEL & LOOKML_EXPLORE env variables for your extension. Are they valid (spelling) & exist in your Looker instance?
Make sure your user has access to this model and explore. At the very least with see_lookml permissions.
Check the Connection environment variables. Do valid BQ connections by those names exist in your Looker instance?
Backend
Front-End
We successfully build the bundle.js following the instructions from the explore-assistant-extension project
We are using the following values in the.env file
Looker setup
We copied the bundle.js and bundle.js.LICENSE.txt files to the /dist folder in Looker
Our manifest.lkml looks like this
Questions
If so, how many input/output examples are recommended?
The text was updated successfully, but these errors were encountered: