WAI
Status Update
No update yet.
Comments
mi...@gmail.com
I'm having the same problem and unfortunately there's no trace of the error (I can't find it on logs at least).
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
cp...@squeeze.biz
I also have this error. Any idea?
th...@google.com
kr...@gmail.com
I'm seeing the same problem. I believe this is the only way to use the Blobstore with Google Cloud Storage, correct? I'd be happy to create a different storage account but it doesn't seem possible to use the Blobstore/GS integration...
ma...@gmail.com
I too am having this problem with the application parrot-pairing, although the otherwise-identical app parrot-pairing-dev worked fine the first time.
ak...@gmail.com
It occurred to me that I have a separate Cloud Services project that I think was previously also named "parrot-pairing" but which I renamed to "parrot-pairing-db" when I discovered the names would clash. Could this renaming process have left some detritus around that poisoned the "parrot-pairing" name for cloud services projects?
he...@gmail.com
Thank you for the report. There are some errors which are not resolved by simply retrying. In the case of parrot-pairing I have found the bug which we will fix in a future release. When the fix rolls out, the retry should succeed.
The error information is not visible to application developers as it's an error in the implementation. However, given a particular app id we on the App Engine team can investigate further.
This is not the only way to use Google Cloud Storage and App Engine, although it is one of the ways we intend to accomplish our goal of simplifying the configuration of your application. There is more information on how to configure this here:https://developers.google.com/appengine/docs/python/googlestorage/
The error information is not visible to application developers as it's an error in the implementation. However, given a particular app id we on the App Engine team can investigate further.
This is not the only way to use Google Cloud Storage and App Engine, although it is one of the ways we intend to accomplish our goal of simplifying the configuration of your application. There is more information on how to configure this here:
cs...@gmail.com
Could you look into my app? The ID is whamcitylights
It would save me a lot of time to be able to use the Blobstore API integration with GS. I plan to slowly migrate to GS completely but I really can't afford to make the full transition right now. Thus enabling this integration would be huge benefit. Thanks
It would save me a lot of time to be able to use the Blobstore API integration with GS. I plan to slowly migrate to GS completely but I really can't afford to make the full transition right now. Thus enabling this integration would be huge benefit. Thanks
[Deleted User] <[Deleted User]>
The issue with whamcitylights appears to be the same one--in fact I expect most cases are that same issue.
an...@google.com
an...@google.com
be...@google.com
as...@google.com
ch...@google.com
Thanks! When do you expect the fix to roll out? Days? Weeks? Months?
Description
Here I am using Pegman & trying to drag the pegman on the map. Before I release the pegman, it automatically update the street view panorama associated with this map with new position & fires position_changed events of street view panorama.
Now I don't want to fire position_changed events when I drag the pegman over the map till I release the pegman.
Do Maps API-v3 has events like pegmandrag, pegmandragstart & pegmandragend?
If not, what it the alternate solution to not to update street view panorama till I release the pegman on the map.