Can't get past compiling error in query preview window.

[LandonPerkins]

Ambitious project and I love the effort. I've been following it for a few months now and had time to install it today.
After installation of all of the components I hit a roadblock with the Compiled Query Preview. I run into the following error on all sqlx files.

No amount of vscode restarts and file name changes has helped.

">dataform compile" runs without issue and the file is listed in the output.

Any thoughts?

[ashish10alex]

Hi @LandonPerkins ,
Thanks for creating the discussion. interesting error. I tied to recreate the error with a similar setup to what you have. But I was unable to recreate the error. Could you please clone this minimal dataform repo that I have created here and try to re-create the issue. In the screenshot below you will notice that I have used a similar filename to what you have and used the name attribute in the config to get a different name for the table. If the issue does not occur when you try this repo, I would appreciate it if you could try to add that edge case which causes the error and share it here.

[LandonPerkins]

Thanks for the response.
Fails locally with the same error.

Fails in the codespace because it doesn't detect google-cloud-cli.
What's noteworthy here is that the "Query" section in the preview panel did populate with the query while on my local machine it did not appear.

[ashish10alex]

thanks @LandonPerkins . Thanks for testing both options. So the dev container option is working. Once you run the 3 gcloud comments it will work as expected. I have published a video on YouTube to how to use Dataform tools with dev containers.

--

Regarding the football_dataform repository not working on your system with the same error as you reported before. My intuition is that it is some kind of path issue. To be able to investigate It further I have added a debug log option to the extension which you can enable in the settings. If you could share the debug logs with me that would help me narrow down on what the issue could be. NOTE: you will need to to reload the window to be able to select Dataform tools as an option in output channel once you enable it. Please let me know if the screenshots below are sufficient.

0. Update to the latest version of Dataform tools extension v0.9.3

1. Got to vscode setting and enable logging
   

2. Reload vscode window using ctrl + shift + p followed by Developer reload window

3. Open the panel at the bottom select Dataform tools from the dropdown and compile the file. You can optionally open the logs in the editor
   

[LandonPerkins]

Sorry for the delay. I have the logs of compiling football_dataform and saving the output into the Compiled Query Preview panel.
extension-output-ashishalex.dataform-lsp-vscode-#1-Dataform Tools.dataform-lsp-vscode-#1-Dataform Tools.log
I will try the dev container on my repo when the opportunity arises.

[ashish10alex]

Hi @LandonPerkins , thanks for sending the logs. I have spotted the issue. You seem to be using multi-root workspace . If you notice the logs, the full path of the file being compiled does not look like a subset of the workspace folder path. I was able to re-create this scenario by opening a different folder and adding a Dataform folder to the workspace.

Your logs

[2025-02-24T20:20:42.300Z] DEBUG: Workspace folder: c:\Users\<user>\Code\Dataform
[2025-02-24T20:20:43.423Z] DEBUG: Getting current file metadata for document: c:\Users\<user>\Code\football-dataform\football_dataform\definitions\0100_GAMES_META.sqlx

How to fix

Open a new vscode window and open the Dataform project in it.

Your logs after doing this will look something like this

[2025-02-24T20:20:42.300Z] DEBUG: Workspace folder: c:\Users\<user>\Code\football-dataform
[2025-02-24T20:20:43.423Z] DEBUG: Getting current file metadata for document: c:\Users\<user>\Code\football-dataform\football_dataform\definitions\0100_GAMES_META.sqlx

--

Please let me know if this works for you and thanks for the persistence so far, appreciate it 🙂

[LandonPerkins]

This did correct the issue. Will the multi-root workspace be taken into consideration in future releases?
Thanks for your help troubleshooting.

[ashish10alex]

Yh, definitely. Something that can be looked at. If you are keen try the CONTRIBUTING.md , contributions are always welcome 🙂

[ashish10alex]

I have created an issue for this feature request as well #110