-
Notifications
You must be signed in to change notification settings - Fork 598
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
With gcd.sh local (gcd-rpc 1.0.0) errors always #1236
Comments
cc @pcostell |
Can you share the exact output of the error messages, both on the client and on the emulator output. |
On the gcd when I make a request:
On my nodejs console all that is outputted is:
|
I have the same issue, expect i'm using the default This is the output from the datastore starting:
The admin interface can be accessed without issues, so I'm pretty sure the datastore emulator is fine. |
@zlepper I believe the gcloud emulator doesn't support gRPC, hence we can't use the gcloud emulator and must use the gcd tool.
https://github.com/GoogleCloudPlatform/gcloud-node/releases/tag/v0.30.0 Please keep in mind there is no admin console with the gcd tool . |
@susanlinsfu internally it seems to call the same cmd file as your command do? And shouldn't the node docs then be updated to reflect the proper way to use gcloud-node with the datastore emulator? |
@zlepper as the release notes say, this is a temporary workaround as the Datastore emulator from inside the gcloud SDK does not support gRPC. Do we have docs that say how to use the emulator currently? We could leave a note there about the workaround. I haven't received any time line for when the SDK emulator will support gRPC. |
There is a note about how to specify an api endpoint, which is pretty much using the datastore emulator, as far as I know. And I just (a couple of days ago) started using gcloud, so I missed the release note when I was searching around for this issue originally. |
Switching to use the gdc.cmd tool directly, as provided in the link on the release page, this happens:
And this is the output in my node terminal:
|
Yikes, those are some gnarly stack traces. Can you share your |
Just sharing a few things I realised to make it work (here on OS X):
|
@pcostell Datastore setup code: https://gist.github.com/zlepper/59c7b11d60c86bb9cd199c5162b9733d |
You need to set the apiPoint inside the datastore() instantiation.
|
@sebelga if you set the env var, you don't need to use
@pcostell should I move this issue over to google-cloud-datastore? |
@sebelga Settings the @stephenplusplus Only settings the env var and not specifying the |
This issue was moved to googleapis/google-cloud-datastore#110 |
Yeah, I don't know if that will fix the error, but it should be all you need from the standpoint of connecting to the emulator with gcloud-node. I'm going to move this issue over to that other repo, hopefully getting some more eyes on the problem. Of course, if it turns out to be an issue with this library, we will re-investigate from this end. |
I am using gcloud-node v.0.30.3 and since it doesn't support gRPC I am using gcd-rpc for my local datastore. This is only occurring on windows (gcd.cmd). I run some operation it always returns 'No connection could be made because the target machine actively refused it". The strange thing though is it completes the operation always. The error shows, but if I have some console output it always shows and if I get entities it will display the entities in the console.
The text was updated successfully, but these errors were encountered: