stackql / stackql/stackql-devel
[BUG] Get rid of pseudo-clobbering error messaging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Rubbish Error message pseudo-clobbering. Some of the real error generally persists (as per screen capture). Only a meaningful error message should be displayed, no rubbish boilerplate.
To Reproduce
See screen capture.
This one is easy to reproduce using a select operation; just misspell the select keyword, eg: slct sizeGb from google.compute.disks where project = 'stackql-demo' and zone = 'australia-southeast1-a';.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the misspelled slct query against google.compute.disks, then trace how the select operation formats parser errors. Done means the output contains only a clear, concise, meaningful error message without the irrelevant boilerplate shown in the screenshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100