overwhelming memcache errors when tilt config is in a bad state

[nicks]

Steps to Reproduce

1. Run tilt up
2. In another terminal, run cp ~/.tilt-dev/config ~/.tilt-dev/config.backup
3. Ctrl-c tilt to exit
4. Restore the config cp ~/.tilt-dev/config.backup ~/.tilt-dev/config
5. Run tilt get session

Expected Behavior

A reasonable error message

Current Behavior

tilt get session
E1018 16:56:41.640903  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.640903  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.640903  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.641165  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.641165  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.641165  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.642379  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.642379  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.642379  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.643578  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.643578  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.643578  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.644771  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.644771  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
E1018 16:56:41.644771  109060 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:36983/api?timeout=32s": dial tcp 127.0.0.1:36983: connect: connection refused
The connection to the server 127.0.0.1:36983 was refused - did you specify the right host or port?

About Your Use Case

I'm pretty sure this is a kubectl regression; i see similar behavior with

KUBECONFIG=$HOME/missing-config kubectl get pods