Hi Richmond
This URL returns '403 Forbidden' for me:
https://code.google.com/p/googleappengine/issues/detail?id=10134
Is that intentional? I can't find any discussion in this group about ID
allocation collisions.
Thanks
Stephen
On Saturday, 11 January 2014 00:26:59 UTC, Richmond Manzana
And when you have, please post a link here so other interested Gophers can
star it.
Stephen
On Monday, 28 January 2013 17:18:30 UTC, schuppe wrote:
File a ticket you should:
https://code.google.com/p/googleappengine/issues/entry?template=Feature%20request
On Fri, Jan 25, 2013 at 6:59 PM,
You haven't made it clear exactly which API you're trying to use, but if
you're trying to create a blobstore key in Python, you might use the
following:
blobstore.create_gs_key('/gs/bucket/path/to/object')
and if you're using the Files API, you might use
In the 'Caveats on Using Data Admin Features' in
https://developers.google.com/appengine/docs/adminconsole/datastoreadmin
it's mentioned that 'All Datastore Admin operations occur within your
applications, and thus counts against your quota'. (Incidentally, if any
Googlers are reading:
If I remember correctly, Pagespeed is intelligent about considering the
number of concurrent HTTP connections a browser will allow to a particular
host. In our case, it didn't start combining Javascript files until we were
requesting enough CSS/JS assets to require more than (I think) 6
It seems that you can't do this via the API Console, but you can achieve
the same effect by settings appropriate ACLs to grant permissions to your
service account using gsutil:
https://developers.google.com/storage/docs/gsutil_reference_guide#setorgetacls
We've done this with an API project
I'm not the best person to provide a comparison between services because
we've only tried Sendgrid. That said, they've been excellent for our needs
- we've sent just shy of 2 million mails via them so far.
Stephen
On Thursday, 19 July 2012 05:32:11 UTC+1, Vivek Kumar wrote:
hie can some one
No need to apologise - I hope you're now able to query as you originally
intended.
Stephen
On Thursday, 5 July 2012 05:58:31 UTC+1, saintthor wrote:
i am sorry. it seems i misunderstanded the word That has nothing to do
with ndb;.
在 2012年7月5日星期四UTC+8上午1时46分20秒，Stephen Lewis写道
The datastore itself draws no distinction between 'ndb entities' and 'db
entities' - the syntax Guido suggested will should work for entities
created via either the ndb or the db API.
Are you unable to query your entities created using the ndb API in the
admin console? It works for me...
increasing.
On the upside, https has started to work for us on a custom domain,
although with a certificate error.
On Saturday, 23 June 2012 05:23:02 UTC+12, Stephen Lewis wrote:
Curiosity got the better of me, and I've just tried this - unfortunately,
it doesn't work. When serving from
When you serve up a Cloud Storage object directly from Cloud Storage, you
can certainly pre-gzip the content and make sure it's served with the
correct 'Content-Encoding'. The reference to this is at:
https://developers.google.com/storage/docs/reference-headers#contentencoding
I'd be
affect signed URLs.
Stephen
On Friday, 22 June 2012 12:42:27 UTC+1, Emanuele Ziglioli wrote:
Thanks for the tip! I will certainly try next week. Storing two versions
would be nice and easy to do!
On Friday, 22 June 2012 23:38:40 UTC+12, Stephen Lewis wrote:
When you serve up a Cloud Storage
For what it's worth, I'm seeing what looks like the same problem with a
Python app. I've reported it as issue
7536http://code.google.com/p/googleappengine/issues/detail?id=7536
.
Stephen
On Friday, 18 May 2012 17:38:37 UTC+1, Yin Liu wrote:
I found I am unable to deploy to GAE with the
Hi Marzia
It's not in the release notes, but it looks like you've fixed issue
7448http://code.google.com/p/googleappengine/issues/detail?id=7448 (a
bug in the TimeBasedHRConsistencyPolicy that caused some transactions never
to be applied). Please pass on my thanks to whoever did this - I'm
Hi
The 405 status code means 'Method Not Allowed' [0]. It looks like someone
(or something) is making a HEAD request to '/', and your app isn't set up
to handle HEAD requests.
To answer your second question: you can get rid of the errors by adding a
handler for these requests.
Stephen
[0]
Under the heading Isolation and Consistency in
http://code.google.com/appengine/docs/python/datastore/transactions.html
it says Unlike with most databases, queries and gets inside a datastore
transaction do not see the results of previous writes inside that
transaction.. Unless I've
16 matches
Mail list logo
