-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting to datastore emulator doesn't work with v0.7.0+ #167
Comments
Sounds like the datastore emulator doesn't do gRPC. I don't currently have time to dig into this, but will happily take pointers if you dig into what is breaking and where. A simplified reproduction sample would be a great start. |
Thanks. will provide ASAP |
Sweet, thanks! |
Here is a gist of how to reproduce the problem. As soon as |
Any update on this? Not being able to use the datastore emulator is a big problem for us. |
@jonasfj @domesticmouse sorry to bump this again, but is there a way this could be looked at? We are unable to upgrade any library at the moment because of this, and it's becoming more and more of a problem. EDIT: Is there a way to connect to the real datastore from my local machine until this is fixed? |
@enyo, Yes, see: https://github.com/dart-lang/appengine#running-without-docker In On topic, if you're interested in debugging this please dive in. We're happy to take contributions. |
Thanks @jonasfj I think that in the long run, having a local datastore emulator is quite crucial for development, so it would be great to get this fixed I'm happy to help debugging this, but I have no idea how the communication between these two services is working. It would be great if somebody who made the breaking change could look at this. |
We have been running on
v0.6.1
for a while and just upgraded to the latest version but can't connect to our datastore emulator anymore. We checked which version broke it, and appears to bev0.7.0
:Refactored to use package:grpc to talk to Logging and Datastore backends.
which fits with the error message we get:Do you have any suggestion on how to fix this?
The text was updated successfully, but these errors were encountered: