Joshua Fox

OK, switched to ``` $ node -v v8.9.4 ``` (`yarn global add google-cloud-gui` had failed earlier, but this Node version let me run that.) However, I still get that gRPC...

I succeeded! I saw my Kinds -- wonderful tool! Among the tricks I tried was the `--unsafe-perm` parameter. That may have made the difference

In case this helps others who come after me -- the tool is installed for me at `~/.nvm/versions/node/v8.9.4/lib/node_modules/google-cloud-gui/`

+1 This occurs even when type hints seem to give all necessary type info. [See my question in StackOverflow](https://stackoverflow.com/questions/72631325)

For those using the Generally Available Flex Env, [note that](https://github.com/GoogleCloudPlatform/jetty-runtime#providing-loggingproperties-via-the-web-application) `JETTY_ARGS `is the param for passing in logging.properties

ClusterCloner clones clusters, not the K8s objects inside them. So, it does not take into account services and entrypoints.

Thank you for the report. Now investigating.

What do you think of an implementation that stores emulator state in pickle files? The memory-based implementation would still be availble. Advantages - State stored across code-reload and across process...

Flask uses Werkzeug which does not reload code. It **completely restarts** the process when it detects a code change. ([Source code](https://github.com/pallets/werkzeug/blob/ef545f0d0bf28cbad02066b4cb7471bea50a93ee/src/werkzeug/_reloader.py)). I could save queue state at exit, and reload...

@anoteboom I implemented the "hibernate" approach. It can be turned off with `hibernation=False` in the constructor. Please let me know what you think.