Closed lucidhwee closed 2 months ago
Facing similar issue.
We are in the process of setting up the latest version of Explore Assistant but are encountering this issue where the UI remains stuck on the loading screen with the message, "Hello. Getting everything ready...". All network calls appear to be successful (returning 200 responses) and there are no pending network requests. Additionally, there are no errors being displayed in the console. I am attempting this setup using an admin account in Looker with full privileges.
I have managed to run it. We have to load samples data into BigQuery tables first in order for the extension to work. You can check https://github.com/looker-open-source/looker-explore-assistant/blob/main/explore-assistant-examples/README.md
@manhld0206 I load samples data into BigQuery just now following the link. It pop-up "Hello" page for awhile and turn to white with no sample data showing in UI.
@ppinyapat111222 From your description alone I couldn't guess the exact reason for the error yet.
Here are some notes which are not mentioned in the guide that helped me sucessfully deployed the extension
VERTEX_AI_ENDPOINT
, VERTEX_CF_AUTH_TOKEN
) should be None|null
. The reverse is also true I guessexplore_assistant_examples
, explore_assistant_refinement_examples
and explore_assistant_samples
explore_id
must be used in the above BigQuery tables. The format is model_name:explore_name
and should reference actual Looker explore in your Looker instanceHope it could help you
As @manhld0206 mentioned, ensure data is loaded into all 3 tables AND that all 3 tables have the same explore_id's with the format ->model_name:explore_name
. We progress pass the "Hello" page only when the data from those 3 tables are loaded. We can add improvements for handling when the required data is missing, null or undefined however.
Hi team, I'm having some trouble with the Looker Explore Assistant extension after deployment. When I access the extension, I'm getting an infinite loading "Hello" page without any error message. It happens both Looker Original and Looker Core of my testing environments.
In the past, I've been able to troubleshoot other issues by using the specific error messages that the Looker extension provides (e.g., "The error is likely related to your Look specific .env variables"). However, the current issue is more difficult to investigate because it doesn't provide any clues.
I would appreciate any suggestions you may have on how to investigate and troubleshoot this issue.