Bigquery connection failing

[Navrooz]

I have been trying to connect VulcanSQL with BigQuery but receive an error 'Not found'.

Also, not getting any endpoints in /localhost/doc

The credentials file is working fine as I tested the connection with DBeaver.

• profiles, vulcan, sql and yaml files are at the below link.

Files: https://drive.google.com/drive/folders/1g1lyEG32x63hAzrIo2JK8vFAk5GpNC1U?usp=sharing

[wwwy3y3]

hi @Navrooz , thanks for your issue report. We'll check out your attached files and see what's going on.

[JSYOU]

Hi @Navrooz, based on your configuration in vulcan.yaml, the files user.sql and user.yaml need to be placed in the sqls folder in order for it to run correctly.

Please create a sqls folder and move user.sql and user.yaml into it, then try again. Thank you.

[Navrooz]

@JSYOU -Hi, Thank you for your reply !
Both the user.sql and user.yaml files are already in sqls folder.

[JSYOU]

Hi @Navrooz ,
Have you successfully executed your project?

[Navrooz]

I tried but as I shared in the screenshots, I get an error 'Not Found' and blank 'localhost:3000/doc' page. It seems like Vulcan is not parsing the endpoint.

[JSYOU]

Hi @Navrooz ,
Are you using the vulcan start command in the vulcanTest-1 directory?

We recommend that the working directory be in the same location as the vulcan.yaml.

If you want to use the vulcan start --config ./vulcanTest-1/vulcan.yaml command from the upper directory, you need to add ./vulcanTest-1/ to the path of folderPath, 'profiles', keyFilename in vulcan.yaml and profiles.yaml.

for example:
Directory Structure

vulcan.yaml

profiles.yaml

[Navrooz]

Hi @JSYOU ,

Thank you for your valuable suggestion.

I am executing the vulcan start command from the vulcanTest-1 directory which has vulcan.yaml, profiles and creds file in it.The result is still the same (Blank home page with no endpoints and 'Not Found' error on API endpoint). Please let me know if you need any files from my end for investigation.

[wwwy3y3]

hi @Navrooz
Can you also provide following information ?

• Version:
  Use command vulcan version to get your packages' version

  cli version: 0.1.0-alpha.1
  core version: 0.1.0-alpha.1
  build version: 0.1.0-alpha.1
  serve version: 0.1.0-alpha.1
  

• OS: macOS, windows 11 ...

[Navrooz]

Yes sure. Here's the extract:
OS: Windows 11

[oscar60310]

It looks like a file listing issue on Windows, we handled it when initializing projects but not for searching sql files.
https://github.com/Canner/vulcan-sql/blob/develop/packages/cli/src/commands/init.ts#L131
https://github.com/Canner/vulcan-sql/blob/develop/packages/build/src/lib/schema-parser/schema-reader/fileSchemaReader.ts#L59

[Navrooz]

So, is there any workaround for sqls in Windows ?

[Navrooz]

You are right, the problem is with listing issue .I tried to reproduce the issue and below are my findings.

1.The demo project https://vulcansql.com/docs/quickstart runs fine. However, if I modify the sql path in vulcan.yaml then I am encountering the same issue as with my project i.e. no endpoints appearing in localhost:3000/doc

2. I changed code as described in your above comment and tried executing the project but no luck.

3.Tried running the project in Linux environment on Windows using WSL. It's not able to install dependencies and fails at building project stage.

[wwwy3y3]

@Navrooz We're fixing this windows issue in #145.

Please give us some time to do a proper PR review.

We'll release a new version after this PR get merged.

[wwwy3y3]

hi @Navrooz thanks for your patience. This windows path issues has been fixed at release v0.3.2.

Please upgrade your version and let us know if it resolves your issues. We'll close this issue in a few days if it's resolved or other issues come up unrelated to this windows path parsing issue.

If there are other windows development issues, please do share with us at our discussion thread: #148

[Navrooz]

@wwwy3y3 Thank you for the update!

I am able to establish the connection and receive response now.

[wwwy3y3]

@Navrooz Glad to hear that!

If there are other windows development issues come up, please do let us know at our discussion thread: #148

Closing this issue.