-
Notifications
You must be signed in to change notification settings - Fork 103
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
"flag redefined: cpuprofile" with sha1cd v0.3.1, avo v0.6.0 #893
Comments
somewhat related: #756 |
Thanks for the very detailed report! I'll tackle this now. Doing a reasonably large refactor due to a misbehaving transitive dependency I'm not so keen on, especially since this is the first time I have run into this in this project. If it happens again I'll happily do that. For now I'll just rename the flag to cpu_profile to be consistent with most of our commands. |
Following up here, the maintainer of avo sent a PR to sha1cd to remove the dependency on avo on the root go module and that just landed. So now the extra flags being registered is gone since #898 :) |
Hi, you are using
github.com/pjbgf/sha1cd
currently in verion 0.3.0. If upgraded to version 0.3.1 it also updatesgithub.com/mmcloughlin/avo
to v0.6.0, which defines the flag "cpuprofile" here also defined here:zoekt/cmd/zoekt-git-index/main.go
Line 49 in 27f6d0b
Its probably a good idea to create some own FlagSet (NewFlagSet) or do some workaround to keep zoekt updatable in the future.
Maybe it would even be possible to remove the old workaround "cpu_profile" by doing it right this time and consolidate the cpuprofile argument.
zoekt/cmd/zoekt-index/main.go
Line 62 in 27f6d0b
Steps to reproduce
go get -u ./... && go run ./cmd/zoekt-git-index/
Output:
The text was updated successfully, but these errors were encountered: