-
```
Currently, it is necessary to manually specify all dependencies when running
mockgen on a file. For example, running `mockgen --source=temp.go` on the
attached file produces the following error:…
-
```
gomock will fail on the following interface:
type Bad interface {
DoSomething(func() string)
}
with the error: "2011/10/09 17:05:54 Can't deduce package for a *ast.FuncType"
It seems like "…
-
```
Currently, it is necessary to manually specify all dependencies when running
mockgen on a file. For example, running `mockgen --source=temp.go` on the
attached file produces the following error:…
-
```
What steps will reproduce the problem?
run mockgen --source=temp.go --aux_files=flag=/invalid/path/here
--destination=mock_temp.go
What is the expected output? What do you see instead?
Expected …
-
```
What steps will reproduce the problem?
run mockgen --source=temp.go --aux_files=flag=/invalid/path/here
--destination=mock_temp.go
What is the expected output? What do you see instead?
Expected …
-
```
What steps will reproduce the problem?
1. Check out my clone with explanation, example interface and test file here:
https://code.google.com/r/nickmab-callsetpatch
2. Running go test in the calls…
-
```
What steps will reproduce the problem?
1. run mockgen
2. run golint
3. get errors
What is the expected output? What do you see instead?
I see the error listed below, I assumed gomock would at l…
-
```
What steps will reproduce the problem?
1. run mockgen
2. run golint
3. get errors
What is the expected output? What do you see instead?
I see the error listed below, I assumed gomock would at l…
-
```
Scenario is : caller pass mock to---->Method_0(mock),but Method_0(..) didn't
call mock's method,and passed mock to------> Method_1(mock)
,finally,mock.ToVerify() gets called in Method_1().Becaus…
-
Hi,
More of a question than an issue. The spec (packaging/amazon-linux-ami/ecs-init.spec) file contains:
Requires: docker >= 1.6.0, docker = 1.6.0
should be sufficient.
Thoughts?