Re: [google-appengine] Re: Multiprocessing in python

['Jungho Ahn' via Google App Engine]

On Aug 27, 2016 4:16 PM, "'Adam (Cloud Platform Support)' via Google App
Engine"  wrote:
>
> Multiple cores are not available to App Engine standard runtime
instances. If you need access to multiple cores on the same instance,
consider using the App Engine flexible runtime, which uses Compute Engine
as the underlying VM and allows you to configure the number of cores
available.
>

Yes, but i can't use multiprocess in Python flexible appengine. When I
created a process, it was a fake process which is a thread like in
appengine.

>
> On Wednesday, August 24, 2016 at 4:27:17 PM UTC-4, Jungho Ahn wrote:
>>
>> Hello,
>>
>> Is it allowed to use python multiprocessing in appengine?
>> I tried, but it looks like only one core is utilized.
>>
>> Thanks,
>
> --
> You received this message because you are subscribed to a topic in the
Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/google-appengine/D6z_WoLsBH8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/88dafadf-a328-423e-8ddc-7c4f585f88a9%40googlegroups.com
.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2B_Q-HPcD%3DcPXKryK_-ODG5Zt%3Dtq6gFJNZMK7zP4LFPOsqowZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Multiprocessing in python

['Adam (Cloud Platform Support)' via Google App Engine]

Multiple cores are not available to App Engine standard runtime instances 
.
 
If you need access to multiple cores on the same instance, consider using 
the App Engine flexible runtime 
, which uses 
Compute Engine as the underlying VM and allows you to configure the number 
of cores available 

.

On Wednesday, August 24, 2016 at 4:27:17 PM UTC-4, Jungho Ahn wrote:
>
> Hello,
>
> Is it allowed to use python multiprocessing in appengine?
> I tried, but it looks like only one core is utilized.
>
> Thanks,
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/88dafadf-a328-423e-8ddc-7c4f585f88a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How do I interpret my suddenly-upspiked usage in quotas?

['Adam (Cloud Platform Support)' via Google App Engine]

Also, if you want to PM me your project ID I can try to look into this as 
well on my end.

On Saturday, August 27, 2016 at 4:33:04 PM UTC-4, Adam (Cloud Platform 
Support) wrote:
>
> The usage graphs don't seem to correlate with the usage stated on the 
> Quotas page. I'd recommend opening a billing support case 
> , which is accessible even to 
> free accounts.
>
> On Wednesday, August 24, 2016 at 9:33:36 AM UTC-4, Jin Choi wrote:
>>
>> I am trying to reason with figures and percentage in my daily quotas. Not 
>> much of progress.
>>
>> I'm using GAE only for api for my android app, for saving user's items 
>> count, hence no static files or so.
>>
>> Just small packets coming back and forth between them.
>>
>> No crons, taskqueue, or any fancy functions at all is used. Just 
>> endpoints apis and datastore are.
>>
>>
>> So far, up until yesterday, the whole requests were about 500, more or 
>> less, 18 instance hours, one-digit percentage on read/write operations.
>>
>> All of a sudden, today in the morning (fyi, from east Asia), requests 
>> soured up by 50,000, instance hours of 83, and check attached pic for the 
>> rest of them..
>>
>> For instance hours, I guess it is possible, since I am using autoscaled 
>> option for them. Maybe GAE brought up a higher class of instance for better 
>> throughput. Just guessing.
>>
>> But, I cannot even imagine how on earth requests because 50,000 over a 
>> night. I, manually, counted how many logs for requests were handled in Logs 
>> tab over the last 24 hours. The count of requests were merely over 1000. 
>> (it's about twice as much more compared to yesterday's)
>>
>> Also, 3 miilion ops of Datastore Read Operations for today makes no sense 
>> at all to me. It's 300% of free quotas for read operations. It always has 
>> been about one-digit percent, at least until yesterday.
>>
>> So, I'd be very thankful if you can share your insight over this ... 
>> disaster. I thought I hit the jackpot when I first saw my daily quotas 
>> status today, but it seems something else just drained my quotas, for 
>> nothing...
>>
>> Thank you.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e0daea2f-3767-4a95-90cf-b1ee387abeed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How do I interpret my suddenly-upspiked usage in quotas?

['Adam (Cloud Platform Support)' via Google App Engine]

The usage graphs don't seem to correlate with the usage stated on the 
Quotas page. I'd recommend opening a billing support case 
, which is accessible even to 
free accounts.

On Wednesday, August 24, 2016 at 9:33:36 AM UTC-4, Jin Choi wrote:
>
> I am trying to reason with figures and percentage in my daily quotas. Not 
> much of progress.
>
> I'm using GAE only for api for my android app, for saving user's items 
> count, hence no static files or so.
>
> Just small packets coming back and forth between them.
>
> No crons, taskqueue, or any fancy functions at all is used. Just endpoints 
> apis and datastore are.
>
>
> So far, up until yesterday, the whole requests were about 500, more or 
> less, 18 instance hours, one-digit percentage on read/write operations.
>
> All of a sudden, today in the morning (fyi, from east Asia), requests 
> soured up by 50,000, instance hours of 83, and check attached pic for the 
> rest of them..
>
> For instance hours, I guess it is possible, since I am using autoscaled 
> option for them. Maybe GAE brought up a higher class of instance for better 
> throughput. Just guessing.
>
> But, I cannot even imagine how on earth requests because 50,000 over a 
> night. I, manually, counted how many logs for requests were handled in Logs 
> tab over the last 24 hours. The count of requests were merely over 1000. 
> (it's about twice as much more compared to yesterday's)
>
> Also, 3 miilion ops of Datastore Read Operations for today makes no sense 
> at all to me. It's 300% of free quotas for read operations. It always has 
> been about one-digit percent, at least until yesterday.
>
> So, I'd be very thankful if you can share your insight over this ... 
> disaster. I thought I hit the jackpot when I first saw my daily quotas 
> status today, but it seems something else just drained my quotas, for 
> nothing...
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a7a2e161-db27-490c-bfa6-ad17ef983c8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Task Queue - Authentication Token

['Adam (Cloud Platform Support)' via Google App Engine]

In your particular case no, there's no way to make the App Engine task 
queue retry a task with a different header if it fails.

I would recommend against using Spring Security framework to secure App 
Engine task handlers for this very reason, since App Engine already uses 
OAuth2.0 to secure the handler and using 'login: admin' will prevent anyone 
but App Engine and application administrators from accessing it.

On Saturday, August 27, 2016 at 10:11:58 AM UTC-4, Apurva Nandan wrote:
>
> Hello everyone, 
>
> Thanks for your insights and suggestions. However, I will explain my setup 
> again as 
> I am using a push queue and app engine api to submit tasks to the default 
> queue.
>
> Queue queue = QueueFactory.getDefaultQueue();
> 
> queue.add(TaskOptions.Builder.withUrl("/api/tasks/indexLine").header("Authorization",
>  
> token).param("linejson", linejson));
>   
>
> The task handler url is secured by using spring security framework by 
> Oauth 2.0 tokens. Hence I pass an additional authorization header to the 
> task for authentication. Now in case this oauth2.0 authorization token 
> expires while sitting in the queue then whenever the task actually runs, 
> the handler will return a 401 unauthorized error.
>
> Is there anyway by which the task queue would check that the task got a 
> 401 error and then it could ask for a refresh token and then call the 
> handler with that token.
>
> - Apurva 
>
> On Wed, Aug 24, 2016 at 1:53 AM, 'Adam (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> To clarify the above, your task handler only gets called when it's time 
>> for the task to actually run, not when the task gets first placed in the 
>> queue, so there isn't a chance that you'll need to deal with an expired 
>> auth token.
>>
>> If you're using push queues, it's sufficient to protect your task handler 
>> URL with 'login: admin' since push queues handlers live on and are issued 
>> by App Engine, which will always be able to authenticate. See 'Securing 
>> Task Handlers 
>> 
>> '.
>>
>> If you have a pull queue, your task handler is either calling the Task 
>> Queue REST API every time it needs to lease a task which requires OAuth 
>> authentication, or you're doing it from within App Engine as well which 
>> uses the application credentials. See 'Using Pull Queues 
>> 
>> '.
>>
>> On Tuesday, August 23, 2016 at 6:19:44 PM UTC-4, Nick wrote:
>>>
>>> The task queue can invoke admin secured urls when you use push, which 
>>> would normally require IAM access. If you set it up like that (assuming you 
>>> can trust your admins) all invocations can be trusted, regardless of 
>>> headers etc.
>>>
>>> Presumably in this case you'll still need to send a user identifier for 
>>> context, but you can assume the operation was authorized by the call that 
>>> queued the task.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/FTbKR62589o/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/77248dbc-840b-419e-b68f-d96f6ba62d16%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b2a69296-b54c-45ce-8b19-8b8f29df998a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Authentication with Google Apps domain account

['Adam (Cloud Platform Support)' via Google App Engine]

The 'Organization' option on project creation is actually related to 
enterprise billing and not Google Apps, so you should be ok. You only need 
to specify your Google Apps domain under App Engine -> Settings. I've 
confirmed this works on a regular project without any organization 
specified.

On Wednesday, August 24, 2016 at 12:55:42 AM UTC-4, sugumar.p sugu wrote:
>
> I don't think com.google.appengine.api.users.User is not working. But I am 
> thinking that I didn't properly created project for Google apps domain 
> authentication. Because, There is no option like Google Apps organization 
> on the project creation page in my cloud console
>
>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/52d0555f-e29b-42d7-80f4-d49ee823b4b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: ImportError: No module named django.core.handlers.wsgi

['Adam (Cloud Platform Support)' via Google App Engine]

It's not necessary to add any of the App Engine SDK paths to PYTHONPATH for 
the development server to work. There's also a syntax error (the leading 
':'). I'd advise just not setting it at all in your shell's config file.

If that doesn't resolve the issue, you can try making a small handler from 
the development server that just prints sys.path and share the output of 
that. It will also help to confirm if *all* external imports don't work and 
not just the Django import.

On Tuesday, August 23, 2016 at 10:25:38 PM UTC-4, Mak Ahmad wrote:
>
> here it is Adam
>
> USERNAME-macbookpro:Documents USERNAME$ which python
>
> /usr/bin/python 
>
> USERNAME-macbookpro:Documents USERNAME$ python --version 
>
> Python 2.7.10 
>
> USERNAME-macbookpro:Documents USERNAME$ export|grep PYTHON 
>
> declare -x PYTHONPATH=
> ":/Users/USERNAME/Documents/google_appengine:/Users/USERNAME/Documents/google_appengine/lib/django-1.5"
>
>
> hope that helps
>
>
>
> On Tuesday, August 23, 2016 at 3:15:44 PM UTC-7, Adam (Cloud Platform 
> Support) wrote:
>>
>> I'm glad you were able to get it to work with the launcher. If you get 
>> ImportErrors only when starting from the terminal it's possible your Python 
>> interpreter is misconfigured. You might want to share the output of the 
>> following:
>>
>> Check which Python interpreter you're using
>> $ which python
>>
>> Check your python version
>> $ python --version
>>
>> Check any Python environment variables eg. PYTHON_PATH
>> $ export | grep PYTHON
>>
>>
>> On Monday, August 22, 2016 at 8:09:45 PM UTC-4, Mak Ahmad wrote:
>>>
>>> I tried a few things and also tried
>>>
>>> http://howto.pui.ch/post/39245389801/tutorial-django-on-appengine-using-google-cloud
>>>
>>> with no luck.
>>>
>>> So then I used the "Google App Engine Launcher" and added the existing 
>>> application there and hit start and it worked. For some reason starting the 
>>> application in a terminal using  "dev_appserver.py " doesn't work but 
>>> with the GUI it does
>>>
>>> On Friday, August 19, 2016 at 3:22:43 PM UTC-7, Adam (Cloud Platform 
>>> Support) wrote:

 If you are having issues setting up Django on App Engine I'd advise 
 following the officially documented method, as per 'Running Django on 
 App Engine standard environment 
 ', which uses a 
 pre-configured 'appengine-django-skeleton' project. This method uses 'pip 
 -t' to vendor the latest Django version into the project.

 On Wednesday, August 17, 2016 at 12:44:56 PM UTC-4, Mak Ahmad wrote:
>
> Sorry there's nothing else I'm doing with the sys path. I just deleted 
> my working directory and did pip uninstall django so it uninstalled it 
> from 
> the Python library. I then recloned the working directory with all the 
> sys 
> path code commented and ran the server and still get the same error.
>
> Does Django need to be installed within google python SDK? I know it's 
> built in but is there an additional step needed? 
>
> I am using a Mac by the way 
>
> On Tuesday, August 16, 2016 at 3:46:45 PM UTC-7, Adam (Cloud Platform 
> Support) wrote:
>>
>> Are you doing anything else with sys.path anywhere in your code? I'm 
>> testing again with only the builtin version of django in app.yaml, and I 
>> do 
>> not get any ImportErrors.
>>
>> You should not need to modify sys.path in any way unless you're 
>> using an installed version of django somewhere other than the 
>> application 
>> root. You should use either the built-in django or vendor your own with 
>> pip, but not both at the same time.
>>
>> On Sunday, August 14, 2016 at 2:33:09 PM UTC-4, Mak Ahmad wrote:
>>>
>>> Thank you Adam. I should have shared that I already do have django 
>>> in my app.yaml
>>>
>>> application: xx-
>>> version: 1
>>> runtime: python27
>>> api_version: 1
>>> threadsafe: yes
>>>
>>> # Handlers match in order, put above the default handler.
>>> handlers:
>>> - url: /static
>>>   static_dir: static
>>> - url: /.*
>>>   script: main.application
>>>
>>> libraries:
>>> - name: django
>>>   version: "1.5"
>>> - name: jinja2
>>>   version: "2.6"
>>> - name: markupsafe
>>>   version: "0.15"
>>> - name: ssl
>>>   version: latest
>>>
>>> builtins:
>>> - django_wsgi: on
>>>
>>>
>>> Any thoughts on how I can get the build in django in my sys.path?
>>>
>>>
>>> On Sunday, August 14, 2016 at 10:35:32 AM UTC-7, Adam (Cloud 
>>> Platform Support) wrote:

 You're getting the ImportError because django is not in your 
 sys.path.

 If you want to use one of the built-in django versions 
 
  
 from the 

[google-appengine] Re: My daily quotas' gone weird all of a sudden. How do I interpret this?

[Anssi Hannula]

I'm also seeing it again right now, with instance hours again being shown 
as ~83.4 h (along with other inflated stats). "Estimated cost for the last 
6 hours" shows $0.00 as expected though. (App ID is "intoa-design")

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/086b7213-41fd-4d1c-8a64-fbc15ed91623%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] [Newbie] How to create a REST based API backend in Python?

[pratibha s]

Hi,

I'm GAE newbie. I'm trying to implement a RESTful API for a python based 
backend. I'm reading the docs and here is what I learnt. 
1. GAE recommends using cloud endpoints which originally uses protoRPC to 
expose models via APIs. 
2. This means models need to be converted to RPC messages for communicating 
with the API. 
3. Use a REST based API which will enable directly manipulating the model 
entities via API.

Here is my question, without using external third party libraries, how do 
you create a REST based APIs? 

Regards,
Pratibha

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/033731e0-ff6a-48c0-8329-732e88251d81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Task Queue - Authentication Token

[Apurva Nandan]

Hello everyone,

Thanks for your insights and suggestions. However, I will explain my setup
again as
I am using a push queue and app engine api to submit tasks to the default
queue.

Queue queue = QueueFactory.getDefaultQueue();

queue.add(TaskOptions.Builder.withUrl("/api/tasks/indexLine").header("Authorization",
token).param("linejson", linejson));


The task handler url is secured by using spring security framework by Oauth
2.0 tokens. Hence I pass an additional authorization header to the task for
authentication. Now in case this oauth2.0 authorization token expires while
sitting in the queue then whenever the task actually runs, the handler will
return a 401 unauthorized error.

Is there anyway by which the task queue would check that the task got a 401
error and then it could ask for a refresh token and then call the handler
with that token.

- Apurva

On Wed, Aug 24, 2016 at 1:53 AM, 'Adam (Cloud Platform Support)' via Google
App Engine  wrote:

> To clarify the above, your task handler only gets called when it's time
> for the task to actually run, not when the task gets first placed in the
> queue, so there isn't a chance that you'll need to deal with an expired
> auth token.
>
> If you're using push queues, it's sufficient to protect your task handler
> URL with 'login: admin' since push queues handlers live on and are issued
> by App Engine, which will always be able to authenticate. See 'Securing
> Task Handlers
> 
> '.
>
> If you have a pull queue, your task handler is either calling the Task
> Queue REST API every time it needs to lease a task which requires OAuth
> authentication, or you're doing it from within App Engine as well which
> uses the application credentials. See 'Using Pull Queues
> '.
>
> On Tuesday, August 23, 2016 at 6:19:44 PM UTC-4, Nick wrote:
>>
>> The task queue can invoke admin secured urls when you use push, which
>> would normally require IAM access. If you set it up like that (assuming you
>> can trust your admins) all invocations can be trusted, regardless of
>> headers etc.
>>
>> Presumably in this case you'll still need to send a user identifier for
>> context, but you can assume the operation was authorized by the call that
>> queued the task.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-appengine/FTbKR62589o/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/77248dbc-840b-419e-b68f-
> d96f6ba62d16%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFk2cV4d-WOhZBDMbXWEmoQNKsQTLEJuymj0PTtDTcGELfPQvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: My daily quotas' gone weird all of a sudden. How do I interpret this?

[OferR]

I'm seeing the same issue with similar numbers.
I guess it is a Google issue.

Google???


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a2959d9d-22fe-43ef-87f3-bfe71790bb56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: My daily quotas' gone weird all of a sudden. How do I interpret this?

[OferR]

I'm seeing the same issue with similar numbers.
I guess it is a Google issue.

Google???







On Wednesday, August 24, 2016 at 4:32:58 PM UTC+3, Jin Choi wrote:
>
>
> I am trying to reason with figures and percentage in my daily quotas. Not 
> much of progress.
>
> I'm using GAE only for api for my android app, for saving user's items 
> count, hence no static files or so.
>
> Just small packets coming back and forth between them.
>
> No crons, taskqueue, or any fancy functions at all is used. Just endpoints 
> apis and datastore are.
>
>
> So far, up until yesterday, the whole requests were about 500, more or 
> less, 18 instance hours, one-digit percentage on read/write operations.
>
> All of a sudden, today in the morning (fyi, from east Asia), requests 
> soured up by 50,000, instance hours of 83, and check attached pic for the 
> rest of them..
>
> For instance hours, I guess it is possible, since I am using autoscaled 
> option for them. Maybe GAE brought up a higher class of instance for better 
> throughput. Just guessing.
>
> But, I cannot even imagine how on earth requests because 50,000 over a 
> night. I, manually, counted how many logs for requests were handled in Logs 
> tab over the last 24 hours. The count of requests were merely over 1000. 
> (it's about twice as much more compared to yesterday's)
>
> Also, 3 miilion ops of Datastore Read Operations for today makes no sense 
> at all to me. It's 300% of free quotas for read operations. It always has 
> been about one-digit percent, at least until yesterday.
>
> So, I'd be very thankful if you can share your insight over this ... 
> disaster. I thought I hit the jackpot when I first saw my daily quotas 
> status today, but it seems something else just drained my quotas, for 
> nothing...
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e5ba82ab-433f-4f71-9178-c22063db1274%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google Cloud Storage browser - can't share files publicly

[Matej Ramuta]

Since yesterday I'm experiencing a bug on Google Cloud Storage browser. I 
wanted to add some new images to it and make them public, but can't do that 
anymore (see the image below or attachment). 

   - There's *no checkboxes* in the "Share publicly" column anymore.
   - I also tried *selecting an image* (Name column) and then *clicking on 
   "Share publicly"* button - but *nothing happens*.

The *old images*, which were made public before the bug all *work ok*. *New 
images* show *"Access denied"* XML when clicking on the *public* link.

Does anyone know where the problem is? It's very weird...



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/15dc9092-e0d3-4e4a-a344-5f431dd88b43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.