Last tested: Aug 31, 2020
When attempting to save a LookML file, the save button will turn red when you click it:
There are several possible causes.
Expecting 'end_of_file', 'keyword', got '}'
There are a couple things that could trigger this error message:
We have seen this with LookML dashboards with missing or mis-aligned syntax. In this case there was no other indication in the IDE, and there is an error 400 in the console. Please reach out to Looker Support if you are seeing this behavior.
If you self-host, this could be due to permissions on the file system. Verify the permissions on the LookML folder and files in question in that users models directory using ls -lah
. They should all be owned by the user running Looker.
If you self-host OR are Looker-hosted with a custom domain, you might have Cloudflare security settings set up to block saving files with certain strings. We have seen this occur on files with comment characters #
and with particular keywords like CONCAT
, COALESCE
, and CAST
.
If this happens specifically with files in folders, this is likely due to reverse proxy settings. Check if your proxy is blocking encoded '/' (%2F) from the URL
Two things that could be going on:
Refer to: https://stackoverflow.com/questions/4390436/need-to-allow-encoded-slashes-on-apache
Final solution: Require a combination of AllowEncodedSlashes and nocanon on the Proxy statement.
Workaround while investigating: Create a blank project and manually create and edit the files outside of any folders. This will help you keep developing while you work on isolating the issue.
This content is subject to limited support.