Frederick

> What are we using for `__hash__` now? currently we use `_EdgeGeneric_HashWithBase()`

Is this still an issue? I don't get this behavior now.

Is this still an issue now that the client is a pool?

added this to the docs in https://github.com/edgedb/edgedb-go/commit/7315ffdbf20cbff04b02f9a19db845e8cd42a4fe

Closing due to inactivity.

I understand the friction. There may be room for improvement here. I'll have to think about this. It seems like there should be an interface for decoding too.

There is no API yet. The issue for it is here https://github.com/edgedb/nebula/issues/459

I can't reproduce any more using `EdgeDB CLI 3.0.0+8b024db`.

I think cloud instances should be able to stop and start. @elprans do I have that right?

I opened an issue for that functionality in nebula https://github.com/edgedb/nebula/issues/459