go-diff

I'm a beginner on golang. Every time I remove the go 1.13, it suddenly goes back again. I'm not sure why. It has something to do with GoLand?

How can I cache my modules in codebuild using AWS provided image (Go 1.12)?

I'm trying to cache go modules in codebuild using the go image (1.12) from AWS.

After digging deeper, I found that there is no /go/pkg folder in that image. Hence, when I tried to cache /go/pkg it would throw an error.

Error mounting /go/pkg/mod: symlink /codebuild/local-cache/custom//go/pkg/mod /go/pkg/mod: no such file or directory

Even after I run go mod download (which will create the /go/pkg/mod, it won't cache the folder because codebuild cannot mounted it earlier).

This is my codebuild.yml

I've almost completed migrating based on google's instructions.

It's very nice to not have to call into the app-engine libraries whatsoever.

However, now I must replace my calls to app-engine-standard memcached.

Here's what the guide says: "To use a memcache service on App Engine, use Redis Labs Memcached Cloud instead of App Engine Memcache."

So is this my only option; a third party? They don't even list pricing on their page if GCE is selected.

I also see in the standard environment how-to guides there is a guide on Connecting to internal resources in a VPC network.

From that link it mentions Cloud Memorystore. I can't find any examples if this is advisable or possible to do on GAE standard. Of course it wasn't previously possible but now that GAE standard has become much more "standard", I think it should be possible?

Thanks for any advice on the best way forward.

The Go package, google.golang.org/appengine, provides IsDevAppServer which reports whether an App Engine app is running in the development App Server (e.g. localhost:8080). However, this does not work unless the (deprecated) standalone SDK is used. See appengine.go#L57 for the implementation.

New GAE apps written in Go are basically a regular web server that can be compiled and started locally like any go program;

• old; dev_appserver.py
• new; go run main.go

Detecting a development server can be useful for to prevent CORS issues when running locally:

I'd have a Go module, say github.com/myorg/mymodule, of which I'd like to update the version in another module. However, if I try to go get -u it, I get an unexpected module path error:

I am trying to run a go script for SLACK bot that downloaded from git. https://github.com/nlopes/slack/blob/master/examples/websocket/websocket.go#L34

I replaced the auth code of my bot in the websocket.go

I've recently been migrating an App Engine (Go) app from Go 1.9 to 1.11. I've followed the steps in the Migrating your App Engine app from Go 1.9 to Go 1.11 document, excluding the optional ones. I plan on doing the optional tasks later once I get this working.

I get the app to build and I can deploy it just fine. Most of everything works fine, with the exception of one API that is used to look up some info on a Google Play IAP. When I do that, I get the following error:

Error 403: Insufficient Permission: Request had insufficient authentication scopes., insufficientPermissions

I've checked, and the scope that I'm using is https://www.googleapis.com/auth/androidpublisher, which is still the scope listed in the Google Play Developer API documentation.

I'm using the App Engine default service account for the client by calling DefaultClient from the golang.org/x/oauth2/google library, which returns a client without an error

When I test the same code with Go 1.9, there are no authentication issues at all, and the API works. I'm guessing that these is something in the authentication setup which has changed but I can't find any documentation on it, nor on what I should do differently.

I have to imagine that a lot of people have had to do this migration, and I can't find any posts with this problem, so I'm lost as to why I'm getting it.

I am trying to migrate from Go 1.9 to Go 1.11. I copied the main function from the migration document

This is my app.yaml

At $DAYJOB we are using a Go 1.9-based AppEngine application. Now that Google is deprecating version 1.9, I am trying to move to 1.11, using the migration guide. It says that I should set runtime: go111 and remove the api_version: go1.9 value from app.yaml, but when doing so, I get an error message deploying: