Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error message is confusing and misleading #247

Open
cyyeh opened this issue Jul 22, 2023 · 1 comment
Open

Error message is confusing and misleading #247

cyyeh opened this issue Jul 22, 2023 · 1 comment
Labels
needs-triage type/bug Something went wrong

Comments

@cyyeh
Copy link
Member

cyyeh commented Jul 22, 2023

Environment

  • Version:

    cli version: 0.6.0
    core version: 0.6.0
    build version: 0.6.0
    serve version: 0.6.0
    
  • OS: macOS

What's wrong?

There is an error message shown by VulcanSQL as following:

ERROR: {"code":"ERR_BAD_REQUEST","requestUrl":"http://host.docker.internal:3000/auth/available-types","method":"get","status":404,"data":"Not Found"}
actualUrl:  http://host.docker.internal:3000/api/agg_revenue_per_platform

However, it turns out I only need to add csv in the response-format field in vulcan.yaml

What's the correct behavior?

The error message should be clear enough to tell me what's wrong.

Notes: This issue is raised by our user armaan in Discord.

Reproducing steps

@cyyeh cyyeh added type/bug Something went wrong needs-triage labels Jul 22, 2023
@armaandhull
Copy link

To reproduce this issue:

  • update the vulcan.yaml to
response-format:
  enabled: true
  options:
    default: json
    formats:
      - json
  • run the catalog server
  • Try to connect to an api endpoint via the UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage type/bug Something went wrong
Projects
None yet
Development

No branches or pull requests

2 participants