-
Notifications
You must be signed in to change notification settings - Fork 245
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
pacmak: go build does not build submodule directories #2618
Closed
1 of 5 tasks
eladb opened this issue
Feb 28, 2021
· 1 comment
· Fixed by #2622, cdk8s-team/cdk8s-operator#228 or awslabs/aws-delivlib-sample#83
Closed
1 of 5 tasks
pacmak: go build does not build submodule directories #2618
eladb opened this issue
Feb 28, 2021
· 1 comment
· Fixed by #2622, cdk8s-team/cdk8s-operator#228 or awslabs/aws-delivlib-sample#83
Labels
Comments
eladb
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 28, 2021
eladb
pushed a commit
that referenced
this issue
Feb 28, 2021
The `go build` command we run during pacmak did not descend into submodules. After adding `./...` to the `go build` command, a few other issues were surfaced related to static member handling. The common issue was that `GoClass` had two separate lists (for static and non-static methods/props). This caused various places in the implementation to only take into account non-static members. Added a new list called `members` which collected both static and non-static members and used it in the various dependency props. An empty module in Python (with only submodules) will result in an empty `__all__` list which yields a MyPy error. Fixes #2618 - go build does not build submodule directories Fixes #2619 - go/python module with only submodules (no direct types) fails compilation Fixes #2620 - go missing imports if class includes only static members Fixes #2621 - invalid go imports when types referenced by static members
eladb
pushed a commit
that referenced
this issue
Mar 1, 2021
The `go build` command we run during pacmak did not descend into submodules. After adding `./...` to the `go build` command, a few other issues were surfaced related to static member handling. The common issue was that `GoClass` had two separate lists (for static and non-static methods/props). This caused various places in the implementation to only take into account non-static members. Added a new list called `members` which collected both static and non-static members and used it in the various dependency props. An empty module in Python (with only submodules) will result in an empty `__all__` list which yields a MyPy error. Fixes #2618 - go build does not build submodule directories Fixes #2619 - go/python module with only submodules (no direct types) fails compilation Fixes #2620 - go missing imports if class includes only static members Fixes #2621 - invalid go imports when types referenced by static members
|
This was referenced Mar 9, 2021
This was referenced Mar 16, 2021
Closed
Closed
This was referenced Mar 17, 2021
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
🐛 Bug Report
Affected Languages
Golang
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)General Information
What is the problem?
When pacmak runs
go build
it will only build the root module and any submodules referenced by it, but if there is no reference it won't recursive into submodule directories.We need to run
go build ./...
to do that.Verbose Log
The text was updated successfully, but these errors were encountered: