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

Error running aah cli 'build' on certain projects after upgrading go1.11 to 1.12 #253

Open
joelsdc opened this issue Mar 28, 2019 · 3 comments
Assignees
Labels

Comments

@joelsdc
Copy link
Contributor

joelsdc commented Mar 28, 2019

What version of aah are you using (aah --version)?

$ aah --version
aah v0.12.3
cli v0.13.4
go  v1.12.1

Does this issue reproduce with the latest release?

Yes

What operating system are you using (such as macOS, Linux and Windows)?

macOS Mojave

What did you do?

Build a static binary of my project

What did you expect to see?

The single binary built ;)

What did you see instead?

A build error

Additional context

When building a single image binary (also happens with regular build) I get the following error:

FATAL
# git.xxx.com/zzz/app/generated
app/generated/add_controllers.go:45:42: undefined: models

exit status 2

Extra info

Some extra info to hopefully help you troubleshoot:

  1. This started happening after upgrading from go1.11.X to go1.12.1
  2. I was able to have a scenario were certain projects would build, and others would give the above error.

Workaround:

Reinstall aah cli:

curl https://aahframework.org/install-cli | bash

and then rebuild the project:

$ aah b -s
...
Build successful for 'zzz' [git.xxx.com/zzz]
Application artifact is here: /Users/joel/git/zzz/build/zzz-ff3c0e5-dirty-darwin-amd64.zip

Thanks!
Joel.

@joelsdc
Copy link
Contributor Author

joelsdc commented Mar 28, 2019

Steps to reproduce:

AFAIR:

  1. Have go1.11.latest installed.
  2. Install aah
  3. Builds you project
  4. Update to go1.12.1
  5. Build your project again <-- here it failed.
  6. Reinstall aah
  7. Build again <-- this one works.

@jeevatkm jeevatkm self-assigned this Mar 30, 2019
@jeevatkm
Copy link
Member

@joelsdc Thanks for reporting an issue.

@joelsdc
Copy link
Contributor Author

joelsdc commented May 9, 2019

Hi @jeevatkm, I think we can summarize that you have to rebuild the cli after every go version upgrade.

Is there any way around this?

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

No branches or pull requests

2 participants