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

Tools.go causes package conflict

Open
  • Is something wrong?
#162 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by inspecting tools.go and its package declaration, then reproduce the vendoring flow in the Bazel environment where Gazelle generates package metadata. Compare the generated package grouping with the rest of the Go files; done means the package vendors without a package-name conflict and the existing Go checks still pass.

Written by the indexing model from the issue text.

Description

When trying to vendor this package into a bazel environment, tools.go package name "tools" is conflicting with the rest of the go files. This is due to the fact that gazelle generation largely ignores build tags in it's initial phase. Is there any way that file could either get the package matched or moved into it's own directory? Happy to make a PR for that either way...

Dominant language
Go
Stars
53
Forks
67
Avg merge
21h 29m
Merged PRs (30d)
12

Getting set up

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 databricks/databricks-sql-go

All issues in databricks/databricks-sql-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.