Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
x/build/app/appengine: local development server panics on pageload #34116
Running dev_appserver.py locally causes the following issue:
$ dev_appserver.py app.yaml ... panic: open app/appengine/perf_graph.html: no such file or directory goroutine 1 [running]: html/template.Must(0x0, 0xbbcd80, 0xc0002ce060, 0x1) /home/rakoczy/.goenv/versions/1.13rc1/src/html/template/template.go:372 +0x54 main.init() /home/rakoczy/development/build/app/appengine/perf_graph.go:240 +0x6c4 panic: open app/appengine/perf_graph.html: no such file or directory
This was caused by a remediation for
Ideally this is temporary until either we can easily create a nested module with AppEngine (see alternative 1 below), or until a fix for
See #34107, which discusses deployment time issues with GOPATH vs module mode.
Thanks for describing the issue in detail.
The suggested fix sounds very reasonable to me. It seems better compared to alternatives 1 and 2. Alternative 3 is also a good one.
I want to offer another alternative for us to consider (either as a solution now, or a long term direction to move in):
Another way to resolve this problem is to move away from using
In the "Migrating your App Engine app from Go 1.9 to Go 1.11" document, one of the described changes is that it's possible to write an App Engine app that's more like non-App Engine apps, meaning it has a
We already do this for some projects that need to be deployed to App Engine but also run locally. For example, the tour. See CL 165537.
Some disadvantages of this approach:
It's worth considering our longer-term goal of merging the build dashboard code into
Great point, I forgot about that option! I think that moving off