Panic when memcache server is down

[Vladimir Mihailenco]

I see following panic in my code that uses memcache:

panic: appengine: API call failed: UNREACHABLE: server is not responding
runtime.panic go/src/pkg/runtime/proc.c:1442
log.Panic go/src/pkg/log/log.go:308
appengine_internal.(*context).makeAPICall go/src/pkg/appengine_internal/api_prod.go:312
appengine_internal.(*context).call go/src/pkg/appengine_internal/api_prod.go:341
appengine_internal.(*context).Call go/src/pkg/appengine_internal/api_prod.go:445
github.com/vmihailenco/appengine/context.(*context).Call github.com/vmihailenco/appengine/context/context.go:0
appengine/memcache.GetMulti go/src/pkg/appengine/memcache/memcache.go:139
appengine/memcache.Get go/src/pkg/appengine/memcache/memcache.go:116
appengine/memcache.Codec.Get go/src/pkg/appengine/memcache/memcache.go:359
github.com/vmihailenco/appengine/cache.Get github.com/vmihailenco/appengine/cache/cache.go:20

Any ideas why it panics if memcache does not respond?

[David Symonds]

That shouldn't happen, but I will make a fix to avoid the panic in that case.

[Vladimir Mihailenco]

I again see this error in the logs. Will it be fixed only with new SDK release?