Repository navigation
GAE + GCE support #210
Description
Activity
@stephenplusplus did you enable the Google Cloud Datastore API for your project?
stephenplusplus commented
on Sep 15, 2014 ContributorAuthorMore actionsYes, and I should mention I've been getting this error for the last couple days, but at first I was able to access without any errors. It also works if I specify the credentials manually:
new gcloud.datastore.Dataset({ credentials: { /* contents of json key file */ } });
@stephenplusplus I now have a GCE instance running sillycloud, and I cannot reproduce your issue. I'll keep it around and monitor it for some days.
stephenplusplus commented
on Sep 16, 2014 ContributorAuthorMore actionsHmm. Well, that's good to hear, since that means our GCE support wasn't compromised, but disappointing that I don't know how to fix.
I wonder if you tried making a change to see if you can surpass the limit that I'm exceeding. If you want to run an experiment, pasting the below as the
getUsersfunction (https://github.com/stephenplusplus/sillycloud/blob/master/actions.js#L10) should run the query once every 100 ms until it reaches 20 attempts (as written, feel free to changetimesToRunandintervalMs).function getUsers(req, res) { var ran = 0; var timesToRun = 20; var intervalMs = 100; var query = dataset.createQuery(['Users']); var interval = setInterval(function() { if (++ran <= timesToRun) { dataset.runQuery(query, function(err, results) { if (ran === timesToRun) { _handleResponse(res)(err, results); } } } else { clearInterval(interval); } }, intervalMs); }
Just an idea. I'm desperate to find a fix to this. Thanks for testing!
// edit: if you know of a less abusive way to get to the same ends, that's probably better :)
stephenplusplus commented
on Sep 21, 2014 ContributorAuthorMore actionsGCE resolved 👍
GAE still being worked on in #233.
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
on Feb 2, 2015 - addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 6, 2020 58 remaining items
- added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 5, 2026 - added 2 commits that reference this issue
on Mar 9, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 17, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
GAE
GAE support is still underway so I'll leave this part out for now.
GCE
I created an instance:
And initiate gcloud like this:
When accessing a file from my bucket, everything goes smoothly. However, when trying to run a query on my dataset, I get a 403:
I'm able to retrieve a token without an issue, but still receive that error after making the request. Any idea if this is a problem with my project/account, or a problem with gcloud?
After reading Authenticating from Google Compute Engine, I saw a line:
Any chance our need for the userinfo.email scope could qualify for "user data"?