Skip to content
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

go-fuzz-build cannot determine dependency alias. #358

Open
aiburegit opened this issue Oct 11, 2024 · 2 comments
Open

go-fuzz-build cannot determine dependency alias. #358

aiburegit opened this issue Oct 11, 2024 · 2 comments

Comments

@aiburegit
Copy link

Hello!
When I try to collect the target I get the following message:
[user@8548b56971da server]$ ~/go/bin/go-fuzz-build -preserve crypto/internal/bigmod -work .           
workdir: /tmp/go-fuzz-build12999488
failed to execute go build: exit status 1
k8s.io/apiserver/pkg/util/flowcontrol/fairqueuing/queueset
/home/user/kubernetes/staging/src/k8s.io/apiserver/pkg/util/flowcontrol/fairqueuing/queueset/queueset.go:480: request.SeatSeconds undefined (type request has no field or method SeatSeconds)

In workdir:

//line /home/user/kubernetes/staging/src/k8s.io/apiserver/pkg/util/flowcontrol/fairqueuing/queueset/queueset.go:480
               go_fuzz_dep.Sonar(__gofuzz_v1, request.SeatSeconds(highR), 24878469)

In queueset.go:480:

 case qs.currentR >= highR:
               qs.advanceEpoch(ctx, realNow, incrR)
       }
 The thing is that in this module the package name is redefined:
import (
...
 fqrequest "k8s.io/apiserver/pkg/util/flowcontrol/request"
...
)
(it so happens that the project has a structure of the same name)

highRit matters precisely from  fqrequest.
As I understand it, the error is as follows: go-fuzz-build, when getting dependencies, found the required package, but did not take into account that its name was overridden, and tries to use the original name of the package, which coincides with the structure of the same name.
Expected result:  go_fuzz_dep.Sonar(__gofuzz_v1,  fqrequest.SeatSeconds(highR), 24878469)

@wulie
Copy link

wulie commented Oct 11, 2024 via email

@josharian
Copy link
Collaborator

Thanks for the bug report. There is nobody actively working on go-fuzz, but PRs do get reviewed, albeit not always quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants