Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Get rid of pseudo-clobbering error messaging

Open
#44 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

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.

Description

bug v0.3

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.

Screen Shot 2023-01-28 at 8 44 05 pm

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.

Dominant language
Go
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.