Go App Engine modified APIs

69 views
Skip to first unread message

pedro mg

unread,
Jul 14, 2015, 11:13:05 AM7/14/15
to google-a...@googlegroups.com
Hi,

any idea on when appengine/runtime will be ported ? Any timeframe ? "appengine/aetest, appengine/cloudsql and appengine/runtime have not been ported yet."

https://github.com/golang/appengine#3-update-code-using-deprecated-removed-or-modified-apis

runtime.RunInBackground(...) used appengine.Context as param, but on our updated app we now use context.Context.

Also, we are getting "API error 9 (memcache:  Memcache is temporarily unavailable)" quite frequently. 

Thanks in advance, 
-- 
pedro mg

Glenn Lewis

unread,
Jul 15, 2015, 11:03:52 AM7/15/15
to google-a...@googlegroups.com, google-appengine-go
For Go on App Engine questions, please use the Google group that is specifically for that topic:

We do not have an ETA for these features yet.

Instead of runtime.RunInBackground, you can use internal.BackgroundContext.  There are other threads on the google-appengine-go mailing list about this if you want to see examples.

As for the "API error", there was a recent change that hopefully solves this problem.  Please try updating with "go get -u google.golang.org/appengine/..." and see if that fixes the problem.

-- Glenn

pedro mg

unread,
Jul 15, 2015, 2:36:29 PM7/15/15
to google-a...@googlegroups.com
Thank you Glenn 

-- 
@pedro_mg

Glenn Lewis

unread,
Jul 15, 2015, 2:44:29 PM7/15/15
to google-appengine-go
bcc: google-appengine

One clarification after re-reading what I wrote...  the recent "API error" change is to hopefully make the matching of errors easier...
It will not actually change the frequency at which you may get errors.
I have not heard of any issues with Memcache lately...
If you need higher availability of Memcache, you may wish to consider getting a Dedicated Memcache.
-- Glenn
Reply all
Reply to author
Forward
0 new messages