You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing issues with multiple PRs, all facing the same issue:
5m 31s
Run spectacles lookml --config-file spectacles_config.yml --client-id $looker_client_id --client-secret $looker_client_secret --branch $GITHUB_HEAD_REF --remote-reset
Connected to Looker version 24.0.39 using Looker API 4.0
Warning: ====== Validating LookML in project data_mesh [warning] ===============
Completed validation in 5 minutes and 30 seconds.
Encountered unexpected ReadError: ""
Full error traceback logged to file.
@piatrnove1995 could you please run in verbose mode (-v or --verbose) so we can see the full traceback? Alternatively, you can check the spectacles.log file for previous runs.
This is likely a transient issue with your Looker instance's API, but the traceback will help me confirm.
Best I can tell, this is a timeout on an API call, and Spectacles just returns a very generic message.
We are currently hitting the same problem. Are you using a freshly created Looker user to run Spectacles? We are, and I think there's some kind of race condition happening in Looker regarding creating a user, then using it.
Hi!
We are facing issues with multiple PRs, all facing the same issue:
5m 31s
Run spectacles lookml --config-file spectacles_config.yml --client-id $looker_client_id --client-secret $looker_client_secret --branch $GITHUB_HEAD_REF --remote-reset
Connected to Looker version 24.0.39 using Looker API 4.0
Warning: ====== Validating LookML in project data_mesh [warning] ===============
Completed validation in 5 minutes and 30 seconds.
Encountered unexpected ReadError: ""
Full error traceback logged to file.
For support, please create an issue at https://github.com/spectacles-ci/spectacles/issues
Error: Process completed with exit code 1.
Please let us know how to proceed.
The text was updated successfully, but these errors were encountered: