erigontech / erigontech/erigon
Build info can have misleading git_tag
Open
UX
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.5k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 465
Description
```
[INFO] [03-07|13:24:04.610] Build info git_branch=main git_tag=v3.0.0-beta1-290-g760e725 git_commit=760e7252d0a1a45d294e511e34286d87bec59453
```
has git_tag=v3.0.0-beta1-290-g760e725 despite being built from a different commit.
Contributor guide
Research direction
Start by locating the code that assembles and logs the build-info fields, then reproduce the reported case using the shown git_branch, git_tag, and git_commit values. Done means git_tag no longer reports a misleading tag when the build comes from a different commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100