sahusury
sahusury
Hi Team, Do you have any update on this issue.
I have tried many below tests for my instance and the code if they can cause this error, **but I still see the same issue/error in every below case**. 1....
We intentionally introduced an error in the LookML dimension named id by pointing it to a non-existent column test in the database table. In this scenario, we expect Spectacles to...
@DylanBaker I tried with Spectacles 2.4.14 but I am still facing the same issue. Approach 1: Tried in looker IDE with pull request Approach 2: Tried in Google cloud shell...
Hi @DylanBaker I tried with verbose mode and below is the error which I am facing: The API was able to capture the error but not able to show it...
Hi @DylanBaker I tried with the latest version and there are 2 observations: 1. SQL validation is taking very long time around 27mins to complete the validation for just 4...
Hi @DylanBaker With verbose mode enabled I received below error:
Hi @DylanBaker , I tested with 2.4.18 version the error messages are now a bit sorted but it is consuming around 25 mins for do the SQL validation with --incremental...
Hi @DylanBaker, apologies for the delay as we were busy in some important developments. To answer your questions: Ans a) We are using BQ as DB hence we do not...