Re: [google-appengine] Re: App Engine - Enable Cloud Debugging for PHP

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

Hi Bilal,

That is correct. The instructions for Cloud Debugger allows the link 
between your code and the graphical user interface of Google Cloud 
Platform, so that you can see information with the StackDriver/Debugging 
tool in our Dashboards. An example on how to view that is shown here 
https://cloud.google.com/debugger/docs/quickstart#view_deployed_source_code

Sincerely,

Alexis
Google Cloud Platform Support

On Thursday, April 15, 2021 at 3:27:54 AM UTC-4 bha...@gmail.com wrote:

> Hello Alex,
> Thanks again for the help.
>
> I understand from you that if I follow the instructions on how to enable 
> Cloud Debugger with the StackDriver on my PHP Larave app, including the 
> php.ini file, Is should be viewing my PHP Laravel app logs inside the Stack 
> Driver somewhere on GCP Dashboard. Correct?
>
> Regards
> Bilal 
>
> On Tue, Apr 13, 2021 at 9:46 PM 'Alexis (Google Cloud Platform Support)' 
> via Google App Engine  wrote:
>
>> Hi Bilal,
>>
>> I suppose you are asking why use App Engine? 
>>
>> The article you provided says that you can use App Engine, Compute 
>> Engine, Kubernetes Engine, etc... Your question was about App Engine, so I 
>> linked the App Engine documentation.
>>
>> In general, the Operational Suite (formerly "Stack Driver") requires some 
>> sort of VM to operate the logs. These VMs are hidden from you when you use 
>> a Google Service and it's included inside of it, along with the rest of the 
>> code. However, in this case I suspect you use your own service/framework 
>> for your code and the logs are not embedded as part of the Google 
>> infrastructure. So, you need a VM of some sort to merge the logs with GCP's 
>> infrastructure tools. Any of the selections above will do.
>>
>> Hope this answers your question.
>>
>> Sincerely,
>>
>> Alexis
>> Google cloud Platform Support
>>
>> On Tuesday, April 13, 2021 at 1:11:32 PM UTC-4 bha...@gmail.com wrote:
>>
>>> Hi Alex,
>>> Thanks a lot for assisting here. I will surely check it and try it out.
>>>
>>> I have one question though. Basically, I am enabling stack driver so 
>>> that my app, Laravel, would send its log to stack driver which is read by 
>>> GCP Cloud Debugger? Do I get the idea here? Maybe I miss the point, I am 
>>> just asking to get more info.
>>>
>>> Thanks
>>>
>>> On Tue, Apr 13, 2021 at 7:52 PM 'Alexis (Google Cloud Platform Support)' 
>>> via Google App Engine  wrote:
>>>
>>>> Hi,
>>>>
>>>> It will be a pleasure to help.
>>>>
>>>> App Engine works by uploading/deploying your local configuration and 
>>>> code. This means you would start locally first. Therefore, if your php.ini 
>>>> is in the root folder of your local code, it should work. In the document 
>>>> you provided, some details are omitted for the entire App Engine process 
>>>> of 
>>>> configuration since it's mostly about Cloud Debugger. However, the rest of 
>>>> the details on how the configuration works for App Engine can be found 
>>>> here[1]. 
>>>>
>>>> In your case, the php.ini is fairly standard to the runtime and not 
>>>> proprietary to App Engine's YAML, but more part of your codebase and the 
>>>> root folder structure. The explicit answer is located here[2] (where it 
>>>> says "If you need any of the above functions, add a php.ini file in the 
>>>> root of your application"). Also, please note the section below that, that 
>>>> also talks about describing the root folder in the YAML. You may find all 
>>>> the details on that page.
>>>>
>>>> Let us know if that solves your issue. Thank you.
>>>>
>>>> Sincerely,
>>>>
>>>> Alexis
>>>> Google Cloud Platform Support
>>>>
>>>> [1] 
>>>> https://cloud.google.com/appengine/docs/flexible/php/configuration-files
>>>> [2] 
>>>> https://cloud.google.com/appengine/docs/flexible/php/runtime#disabled_functions
>>>>
>>>> On Monday, April 12, 2021 at 5:37:03 PM UTC-4 bha...@gmail.com wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>> I followed the instructions on the page 
>>>>> https://cloud.google.com/debugger/docs/setup/php?authuser=1
>>>>>
>>>>> I am using App Engine Flex. At once the docs asks to do the following:
>>>>>
>>>>>
>>>>> App Eng

Re: [google-appengine] Re: App Engine - Enable Cloud Debugging for PHP

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

Hi Bilal,

I suppose you are asking why use App Engine? 

The article you provided says that you can use App Engine, Compute Engine, 
Kubernetes Engine, etc... Your question was about App Engine, so I linked 
the App Engine documentation.

In general, the Operational Suite (formerly "Stack Driver") requires some 
sort of VM to operate the logs. These VMs are hidden from you when you use 
a Google Service and it's included inside of it, along with the rest of the 
code. However, in this case I suspect you use your own service/framework 
for your code and the logs are not embedded as part of the Google 
infrastructure. So, you need a VM of some sort to merge the logs with GCP's 
infrastructure tools. Any of the selections above will do.

Hope this answers your question.

Sincerely,

Alexis
Google cloud Platform Support

On Tuesday, April 13, 2021 at 1:11:32 PM UTC-4 bha...@gmail.com wrote:

> Hi Alex,
> Thanks a lot for assisting here. I will surely check it and try it out.
>
> I have one question though. Basically, I am enabling stack driver so that 
> my app, Laravel, would send its log to stack driver which is read by GCP 
> Cloud Debugger? Do I get the idea here? Maybe I miss the point, I am just 
> asking to get more info.
>
> Thanks
>
> On Tue, Apr 13, 2021 at 7:52 PM 'Alexis (Google Cloud Platform Support)' 
> via Google App Engine  wrote:
>
>> Hi,
>>
>> It will be a pleasure to help.
>>
>> App Engine works by uploading/deploying your local configuration and 
>> code. This means you would start locally first. Therefore, if your php.ini 
>> is in the root folder of your local code, it should work. In the document 
>> you provided, some details are omitted for the entire App Engine process of 
>> configuration since it's mostly about Cloud Debugger. However, the rest of 
>> the details on how the configuration works for App Engine can be found 
>> here[1]. 
>>
>> In your case, the php.ini is fairly standard to the runtime and not 
>> proprietary to App Engine's YAML, but more part of your codebase and the 
>> root folder structure. The explicit answer is located here[2] (where it 
>> says "If you need any of the above functions, add a php.ini file in the 
>> root of your application"). Also, please note the section below that, that 
>> also talks about describing the root folder in the YAML. You may find all 
>> the details on that page.
>>
>> Let us know if that solves your issue. Thank you.
>>
>> Sincerely,
>>
>> Alexis
>> Google Cloud Platform Support
>>
>> [1] 
>> https://cloud.google.com/appengine/docs/flexible/php/configuration-files
>> [2] 
>> https://cloud.google.com/appengine/docs/flexible/php/runtime#disabled_functions
>>
>> On Monday, April 12, 2021 at 5:37:03 PM UTC-4 bha...@gmail.com wrote:
>>
>>>
>>> Hi,
>>> I followed the instructions on the page 
>>> https://cloud.google.com/debugger/docs/setup/php?authuser=1
>>>
>>> I am using App Engine Flex. At once the docs asks to do the following:
>>>
>>>
>>> App Engine flexible environment pecl install stackdriver_debugger-alpha
>>>
>>> If your php.ini file does not include extension=stackdriver_debugger.so 
>>> after running this step, add it manually.
>>>
>>>
>>> On App Engine Flex, how can I access the php.ini to include that 
>>> extension?
>>>
>>> I did the rest of steps, however, when running cloud_build on App 
>>> Engine, I get error something like "install google/cloud or 
>>> google/error-reporting packages". I already have Google/cloud installed.
>>>
>>> Most probably, the extension is missing from php.ini and that's why it's 
>>> not working.
>>>
>>>
>>> I appreciate your help.
>>>
>>> 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/3zU3bF8O8sw/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/dc1a4854-de71-4729-9e6c-f8b1193c25a1n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/dc1a4854-de71-4729-9e6c-f8b1193c25a1n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/de6b2e4b-e192-48a7-92b6-c0ff58da9119n%40googlegroups.com.

[google-appengine] Re: App Engine - Enable Cloud Debugging for PHP

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

Hi,

It will be a pleasure to help.

App Engine works by uploading/deploying your local configuration and code. 
This means you would start locally first. Therefore, if your php.ini is in 
the root folder of your local code, it should work. In the document you 
provided, some details are omitted for the entire App Engine process of 
configuration since it's mostly about Cloud Debugger. However, the rest of 
the details on how the configuration works for App Engine can be found 
here[1]. 

In your case, the php.ini is fairly standard to the runtime and not 
proprietary to App Engine's YAML, but more part of your codebase and the 
root folder structure. The explicit answer is located here[2] (where it 
says "If you need any of the above functions, add a php.ini file in the 
root of your application"). Also, please note the section below that, that 
also talks about describing the root folder in the YAML. You may find all 
the details on that page.

Let us know if that solves your issue. Thank you.

Sincerely,

Alexis
Google Cloud Platform Support

[1] https://cloud.google.com/appengine/docs/flexible/php/configuration-files
[2] 
https://cloud.google.com/appengine/docs/flexible/php/runtime#disabled_functions

On Monday, April 12, 2021 at 5:37:03 PM UTC-4 bha...@gmail.com wrote:

>
> Hi,
> I followed the instructions on the page 
> https://cloud.google.com/debugger/docs/setup/php?authuser=1
>
> I am using App Engine Flex. At once the docs asks to do the following:
>
>
> App Engine flexible environment pecl install stackdriver_debugger-alpha
>
> If your php.ini file does not include extension=stackdriver_debugger.so 
> after running this step, add it manually.
>
>
> On App Engine Flex, how can I access the php.ini to include that extension?
>
> I did the rest of steps, however, when running cloud_build on App Engine, 
> I get error something like "install google/cloud or google/error-reporting 
> packages". I already have Google/cloud installed.
>
> Most probably, the extension is missing from php.ini and that's why it's 
> not working.
>
>
> I appreciate your help.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dc1a4854-de71-4729-9e6c-f8b1193c25a1n%40googlegroups.com.

[google-appengine] Re: How to install a fresh wordpress

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

Hi,

With your picture, I can't tell if you are using an ephemeral IP. If you 
are, the first thing to do would be to promote your ephemeral external IP 
to a static external IP. There's more information about this here[1]

Also, for resetting the data on your VM... Your Wordpress is just software 
you installed on our virtual machine (GCE instance). So, if you wipe the VM 
clean and use the same method to install as before, it should be fine. 
Unless you utilized a method that automatically installed WP along with the 
VM bundled with it? You will have to specify if you did it differently. In 
short, this[2] procedure allows you to delete the instance. You can 
experiment with stopping/restarting/delete instances and be free to do as 
you wish without loosing your IP *as long as it's depicted as a static IP 
in our systems*. Updating to a static IP (*and not choosing to deleted it 
in your configurations*) is your safest bet to do this properly. Once it's 
static, you can delete and recreate, this can sometimes be as fast as a 
manual format. If a manual format is what you want, you can log in using 
SSH into your VM and do a normal wipe like on any other machine. A search 
for you OS command line on how to wipe could help. However, most people 
prefer to completely delete the instance (once they have a static IP) since 
it's as fast and especially if you have a bundle of configuring the VM + 
Wordpress.

[1] 
https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address#reserve_new_static
[2] https://cloud.google.com/compute/docs/instances/deleting-instance

On Monday, October 19, 2020 at 11:35:46 AM UTC-4 31th...@gmail.com wrote:

> Hello there,
> I would like to know how can I install a fresh wordpress on my VM instance 
> without changing the external IP address.
>
> https://prnt.sc/v1wtpx
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f37933e8-415e-42d0-a8dc-c292e4157894n%40googlegroups.com.

[google-appengine] Re: App engine connection to cloud storage

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

Hi,

I'll try to assist the best I can.

The main issue here is that what you are doing is an http request and not 
local to the machine. For example "gs://" is essentially the gsutil tool 
wrapping-up an HTTP request and emulating locally, but it's not part of the 
local file system. Whereas the library you are using thinks it's 
manipulating the file system. Hence the problem you are having.

The workaround would be this[1], which consists of "mounting" GCS to the 
filesystem using Cloud Storage FUSE. But the problem is that it's an 
anti-pattern on App Engine. App Engine is ephemeral and could have many 
instances with these mounts. You are bypassing a library with concurrency 
for when many instances would talk to the same database. This means it may 
work if you only max one instance, but you could have problems after more 
than one instance is talking to the same files. It just doesn't make sense 
architecturally, but it may work. Use at your own risk. 

Let me know if there's something I'm not seeing or why you can't use the 
library provided.


[1] https://cloud.google.com/compute/docs/disks/gcs-buckets#mount_bucket

On Thursday, October 8, 2020 at 10:57:10 AM UTC-4 punit...@gmail.com wrote:

> In my Springboot based JAVA app, how can I specify the address of cloud 
> storage to access it directly without using "Storage" GCP Java classes. 
> With windows local app, I am using application.properties file to specify 
> the same, and access it directly. 
>
> If I try to replace the same "E:/folder1/folder2" with 
> "gs://bucket1/folder1/folder2"
> it gives me error: 
> Constructor threw exception; nested exception is 
> java.nio.file.FileSystemException: /workspace/gs:: Read-only file system. 
> Meaning it is trying to find the path in the same workspace as where the 
> jar/war file is placed.
>
> Any help?
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/26498f75-4686-4a9d-91f6-9af94ac3aa5en%40googlegroups.com.

[google-appengine] Re: My app verification is still pending

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

Hello,

I will try to assist the best I can.

There is an internal escalation process for this request. However, it 
requires a project ID, to which I strongly suggest you do NOT post this in 
this public forum. As George mentioned above, you may create a private 
request using the Public Issue Tracker link. The private request will not 
show your post publicly, but only with Google.

Hope this helps.

Sincerely,

Alexis
Google Cloud Platform Support

On Wednesday, September 16, 2020 at 10:02:14 AM UTC-4 edav...@gmail.com 
wrote:

> I have this same issue. Can you provide the correct link to create a 
> support ticket for this particular issue?
>
> On Wednesday, October 16, 2019 at 11:19:50 AM UTC-4 George (Cloud Platform 
> Support) wrote:
>
>> Has your app verification progressed meanwhile? You should keep in 
>> contact with the consent screen verification team, who is expected to 
>> verify and eventually approve your consent screen. You might be well 
>> entitled to support, so opening a support ticket in place of Groups 
>> postings should allow for direct and personalized help in this matter. You 
>> may also consider opening an issue in the Public Issue Tracker 
>> , if you need guidance in checking 
>> with the verification team. 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e3c43641-3e05-457e-81ae-1ea646ff9a4en%40googlegroups.com.

[google-appengine] Re: Spending LImits Going Away :(

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

Hello everyone,

To summarize this conversation, it is possible to set proactive limits by:
- Maximum number of instance[1] in an app
- Disable your app programmatically[2] for any resource consumption, etc..
- Cap API limits to prevent too many requests[3]

If I understood properly, Joshua's situation is about caching. So in that 
case, we are talking about resource limits related to CPU cycles, or maybe 
amount of requests... I suspect that whatever resource spiked by this 
situation, can probably make use of the second option above or even the 
third if it's API consumption. But it all depends on how fast this happened 
and I would agree that having a hard cap feature would prevent the delay.

In terms of instantaneous hard caps (with no delays), a feature request[4] 
can be done. However, I think it would be advantageous to clarify how such 
a cap can be helpful without impacting scalability. Please see below.

When submitting a feature request:
- Try to clarify how the limit should differentiate a CPU cycle that is 
legit and versus one that isn't legit. Would you want that on all your 
instances? Would you mind if it stopped all your services as a false alarm? 
(The current solution for that is max instances in my first point above 
because scaling is a horizontal concept and it doesn't completely stop 
things since it's a delta quantity. If some of the other issues mentioned 
were due to excessive instances or API requests ,  then please refer to the 
above).

I hope this message consolidates the research and saves time for any new 
person reading this post. Thank you in advance.

[1] 
https://cloud.google.com/appengine/docs/managing-costs#specify_the_maximum_number_of_instances
[2] 
https://cloud.google.com/appengine/docs/managing-costs#disable_your_app_programmatically
[3] https://cloud.google.com/apis/docs/capping-api-usage
[4] https://cloud.google.com/support/docs/issue-trackers?hl=id#trackers-list

On Wednesday, September 2, 2020 at 11:18:59 AM UTC-4 vit@gmail.com 
wrote:

> Canceling a simple and straightforward option "daily spending limit" is a 
> very cruel action for beginners just starting to learn the platform. A 
> separate warning should be given in the starter guide:
>
> In order not to go bankrupt when using GCP, you first need to carefully 
> study the documentation section https://cloud.google.com/cost-management.
>
> My story.
>
> Ndb model with a lot of indexed fields (since the field property indexed = 
> True by default). The cost of writing one entry to such a model was very 
> high.
>
> The main program sent a message to the queue when a fairly rare event 
> occurred. The handler of such a message from the queue updated the 
> corresponding record in the model, and then an exception occurred due to an 
> error in the code, and the handler exited with an error code.
>
> The platform initiated several processing retries, which also failed. In 
> each attempt, there was a write to the model.
>
> The main program, not finding the results of processing, added a new 
> message to the queue, which caused a new series of attempts described 
> above. And so on.
>
> The daily budget was depleted within a few minutes and the program was 
> stopped by a fuse "daily spending limit".
>
> In the current reality, I would have received a bill for several thousand 
> dollars if I had reacted to this situation within 24 hours.
>
> Yes, then I changed the model, leaving indexed=True only for a couple of 
> fields where it was really necessary and changed the logic of both the main 
> program and the message handler from the queue.
>
> But all this happened later.
>
> вторник, 25 августа 2020 г. в 20:03:33 UTC+4, Joshua Smith: 
>
>> Once again last night, my wallet was saved when a runaway bot chewed up 
>> my site’s whole daily spending limit. I got an email from a user, set up a 
>> firewall rule, and goosed my budget to get things going again.
>>
>> I’m *very* concerned about Google’s decision to remove this feature. 
>> Offering a cloud service that bills by usage without having a way to limit 
>> the spend shifts an unreasonable amount of risk onto the subscriber.
>>
>> I’ve set up budget alerts, as suggested, but I’m concerned that:
>>
>> - What if my bill shoots up really fast? How quickly is this alert going 
>> to go out?
>>
>> - What if I am away from the computer (remember when we used to be able 
>> to leave our houses? good times… good times…)?
>>
>> I run this particular site as a not-for-profit social good. (It’s a site 
>> that small town governments use to post their meetings.) I make *no* money 
>> on it.
>>
>> I’d be perfectly happy to handle this with self-set quotas on something 
>> other than dollars. For example, in my case the budget-buster is always 
>> “Cloud Datastore Read Operations.” If I could set a cap on that one thing, 
>> it’d give me the protection I need.
>>
>> -Joshua
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 

[google-appengine] Re: Deploying to App Engine Standard Env + Laravel Project + Read-only file system error

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

Hi Hadil,

The error says: "Failed to open stream: Read-only file system". I think 
this means that it's finding a file there already (under 
"/workspace/storage/framework/views/") where it shouldn't be. This could be 
a caching issue with Laravel where the files are upload by certain machines 
only. However, if it isn't a caching issue, then something is different 
about those local machines and what it uploads since one dev doesn't have 
this problem 100% of the time. It could also be a config issue in Laravel.

Scenario 1: If all the devs are pulling from the same repo:
- What if you try one of these[1] commands to clear view cache on 
non-working machines?
- What if you try clearing the general[2] cache on non-working machines?
- Check the gitignore file if it's the same across stations that work and 
don't work

Scenario 2: If the devs are not pulling from same repo:
- Where is the part of the code that should have VIEW_COMPILED_PATH? Is 
that code different across repos?
- Check the gitignore file if it's the same across stations that work and 
don't work

There's a lot of possibilities, but I suspect it might be caching being 
uploaded into the wrong path somehow. Probably due to local testing.

[1] https://laravel.com/docs/7.x/views#optimizing-views
[2] https://laravel.com/docs/7.x/configuration#configuration-caching

On Wednesday, August 26, 2020 at 4:16:05 AM UTC-4 hadil.cha...@mmpww.com 
wrote:

> Hello Mary,
>
> Thank you for your reply.
>
> The app.yaml file already includes "/*tmp*" for both "*VIEW_COMPILED_PATH*" 
> and "*APP_STORAGE*". For more permanent files, we're already using Cloud 
> Buckets. What Laravel is trying to do is store compiled views (which are 
> *temporary* files) onto "/*workspace*/storage/framework/views/". However, 
> from app.yaml we already set "VIEW_COMPILED_PATH" as *tmp*, why is the 
> code still trying to save onto the "*workspace*" directory? I need to 
> emphasize again that this project has been working fine for more than a 
> year on app engine and it started breaking only 2 weeks ago. I appreciate 
> the links you shared but if you read the problem carefully you'll see that 
> the links do not address our issue.
>
> With the above in mind, can you please direct us towards a solution?
>
> On Wednesday, August 26, 2020 at 12:13:31 AM UTC+3 Mary (Google Cloud 
> Support) wrote:
>
>> Hello Hadil,
>>
>> Yes that is correct. Since App Engine Standard the disk is read-only[1] 
>> with the exception of the /tmp directory, the app.yaml file will be need 
>> modified for the APP_STORAGE to reflect /tmp  as you have mentioned. If 
>> these are static files that Laravel needs to retrieve you can use a Cloud 
>> Storage bucket to store them. There is an open source Laravel Google Cloud 
>> Storage Package[2] which can help you with this. More information can be 
>> found on how to configure Laravel with the above package[3]. Please be 
>> aware since this package is open source, it is not supported or endorsed by 
>> GCP.
>>
>> [1] 
>> https://cloud.google.com/appengine/docs/the-appengine-environments#comparing_high-level_features
>> [2] https://github.com/Superbalist/laravel-google-cloud-storage
>> [3] 
>> https://stackoverflow.com/questions/57177524/laravel-how-to-access-stored-image-from-google-cloud-storage-using-php-laravel
>>
>> On Tuesday, August 25, 2020 at 8:02:02 AM UTC-4 hadil.cha...@mmpww.com 
>> wrote:
>>
>>> Also, something else worth noting is that we're not sure why Laravel is 
>>> trying to the write to the folder "/*workspace*/storage/framework/views/" 
>>> instead of "/*tmp*/storage/framework/views/". Also, in case it's 
>>> helpful to someone, below is a copy of our app.yaml (it's been configured 
>>> the same way for over a year):
>>>
>>> APP_KEY: XXX
>>> APP_URL: 'X'
>>> APP_NAME: XXX
>>> APP_STORAGE: /tmp
>>> APP_ENV: production
>>> APP_DEBUG: true
>>> VIEW_COMPILED_PATH: /tmp
>>>
>>> On Monday, August 24, 2020 at 7:02:51 PM UTC+3 Hadil Charafeddine wrote:
>>>
 Hello,

 Our team has been using App Engine Standard for this project (PHP and 
 Laravel 5.8.38) for over a year now without any issues with deployment. 
 However, a couple of weeks ago we started getting a 500 HTTP error every 
 time we deploy (with and without --no-promote option).

 When we check our logs, we find that the error is caused by:
 *2020/08/18 06:15:15 [error] 25#25: *2 FastCGI sent in stderr: "PHP 
 message: PHP Fatal error:  Uncaught ErrorException: 
 file_put_contents(/workspace/storage/framework/views/c1b305dfa33e081e1fc836f46439e09f829e8770.php):
  
 failed to open stream: Read-only file system*

 It's very weird that we're receiving this message now even though the 
 project has been working fine for more than a year and we've made 
 countless 
 deployments to date without this issue. Furthermore, we did not update the 
 configuration of the project nor did we update the Laravel version.

[google-appengine] Re: Spending LImits Going Away :(

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

Hello Joshua,

I'll try to help the best I can. I've added a question below, along with 
some answers too.

Questions:
- Which feature did Google remove? What was this feature called and where 
was it shown in the GUI? I'm asking so that we can try to maybe do a 
feature request or see why it was removed.

To answer your question, the alerts should be prompt unless there is an 
outage or some other exceptional circumstance. However, keep in mind that 
we do not have control over public communication channel delays such as 
SMS, email, etc... Double-checking in the GUI could tell you if it was 
already sent out or not. Delays can also happen if alerts have multiple 
conditions and one of them hasn't been met yet. See full article here[1] 
for more details about latency possibilities.

If you're away from the computer, you have notification options here[2], 
called "channels".

[1] 
https://cloud.google.com/monitoring/alerts/concepts-indepth#notification-latency
[2] 
https://cloud.google.com/monitoring/support/notification-options#creating_channels

On Tuesday, August 25, 2020 at 12:03:33 PM UTC-4 Joshua Smith wrote:

> Once again last night, my wallet was saved when a runaway bot chewed up my 
> site’s whole daily spending limit. I got an email from a user, set up a 
> firewall rule, and goosed my budget to get things going again.
>
> I’m *very* concerned about Google’s decision to remove this feature. 
> Offering a cloud service that bills by usage without having a way to limit 
> the spend shifts an unreasonable amount of risk onto the subscriber.
>
> I’ve set up budget alerts, as suggested, but I’m concerned that:
>
> - What if my bill shoots up really fast? How quickly is this alert going 
> to go out?
>
> - What if I am away from the computer (remember when we used to be able to 
> leave our houses? good times… good times…)?
>
> I run this particular site as a not-for-profit social good. (It’s a site 
> that small town governments use to post their meetings.) I make *no* money 
> on it.
>
> I’d be perfectly happy to handle this with self-set quotas on something 
> other than dollars. For example, in my case the budget-buster is always 
> “Cloud Datastore Read Operations.” If I could set a cap on that one thing, 
> it’d give me the protection I need.
>
> -Joshua
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f77ae31b-61bd-4251-bb5d-4809076b70fan%40googlegroups.com.

Re: [google-appengine] Re: Transactional tasks delayed

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

Hello Okku,

I looked into your case and even though I cannot divulge private 
information in a public post, there is this[1] article that states that the 
max is five transactional tasks into the task queues during a single 
transaction. It also says that the tasks are enqueued, rather than acting 
in parallel. Obviously, if they happen fast, they may appear as parallel. 
But in this case, they are slow from your perspective. And I think what you 
are asking is why they are throttled every second when they take ms to 
complete (as shown in the picture above), rather than what the ceiling 
should be.

For example, in the picture, the 33rd second of 23:26 has 5 tasks and you 
should aim to reach that consistently if you want it to be faster (but it 
will never fully be parallel since they are enqueued). If you have them all 
in the same run_in_transaction() function, that could be the cause of it. 
It's hard to say what should and shouldn't be the best pattern due to the 
semantics of your application, but I think it might be best to look at it 
in reverse and try to figure why certain tasks can happen 5 times a second 
and then duplicate that as an appropriate pattern in your application.

The bug that was confirmed previously was more of an outage. Engineers can 
relate those delays to outages. However if you are experiencing this three 
times with months apart, a secondary problem could be the root cause.

I understand that your initial question was if others are having this issue 
and I will let others answer, but I did some research for that too and 
didn't find it to be common. If you need further specific assistance, it 
might best best to do a support ticket. Otherwise, try to isolate why 
certain tasks are faster than others in comparison with your business logic.

[1] 
https://cloud.google.com/appengine/docs/standard/python/datastore/transactions#transactional_task_enqueuing

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/60e8b3d8-7129-4eb1-a098-74887cdcdcc4o%40googlegroups.com.

[google-appengine] Re: Not able to run dev_appserver with Python 3 only environment

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

Hello Ritesh,

I looked in our internal issues and I did not find this error posted. It 
could be a new one. However, a quick Google search shows that someone 
here[1] downgraded to an older version of the SDK and it worked. Older 
versions of the SDK can be found here[2].

If it does work with an older version, it could mean that there is an 
issue. And we would need to report that in the issue tracker here[3], under 
"Cloud SDK issues". However, there are many other possibilities (too many 
not visible) and it would be good to isolate further without brew, etc.. 
Just for testing under which environment/config this happens.

If you could, please let us know if it works with an older version of Cloud 
SDK and under which specific environment. Otherwise, this may need to be a 
support ticket. Thank you in advance.

[1] 
https://www.reddit.com/r/googlecloud/comments/gdndx4/gcloud_sdk_update_from_28900_to_29000_on_mac/
[2] https://cloud.google.com/sdk/docs/downloads-versioned-archives#archive
[3] https://cloud.google.com/support/docs/issue-trackers

On Wednesday, August 12, 2020 at 6:37:14 AM UTC-4, Ritesh Nadhani wrote:
>
> Hello
>
> I am getting back to GAE after many years. Things have definitely changed. 
> As a new project, I got started with Python 37 runtime. My virtualenv is 
> created using: python3 -m venv ENV and thus does not have python2.
>
> When I try to run my app in local mode using dev_appserver.py (i am just 
> trying to play around with the sample app from the documentation), I get:
>
> dev_appserver.py app.yaml
> ERROR: (dev_appserver) python2: command not found
>
> I installed google-cloud-sdk using brew with: brew cask install 
> google-cloud-sdk.
>
> As of now, my only requirement for my app is GAE and datastore and I am 
> hoping to be able to use the datastore emulator with the above.
>
> Ritesh
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3c414bee-38e8-49fb-bc30-3d6b2796f5dbo%40googlegroups.com.

Re: [google-appengine] Re: Spring Boot + JSP + WAR + Java 11 + GAE Standard Environment = sad

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

Hello Todd,

You are correct for the support of App Engine Standard with JAR and if you 
prefer WAR it's understandable. There is a possible workaround here[1] but 
that's for old Java 7 and I think now 8. There is an old discussion about 
that here[2]. Deploying it in Flex is the better option. However, there is 
an explanation here[3], under "What are the changes between the Java 8 and 
Java 11 standard runtimes?", as to why it's not compatible. It's due to the 
API. To be future-proof, it might be best to stay with the Flex engine. I 
understand Standard engine is cheaper, but the API is older.

[1] 
https://cloud.google.com/appengine/docs/standard/java/configuration-files#an_example
[2] https://github.com/GoogleCloudPlatform/cloud-code-intellij/issues/1912
[3] https://ludoch.github.io/java11.html

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/badd3a69-b476-43ae-8929-144bf7018bdco%40googlegroups.com.

[google-appengine] Re: Currently getting hundreds of 503 errors calling service from task queue

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

Hello Rob,

Without taking other factors into consideration, you may be affected by 
this[1] issue. It shows that App Engine is affected. It might be best to 
engage GCP support for a better answer. However, you can also follow the 
status of the issue here[2]. 

Hope this helps.

[1] https://status.cloud.google.com/incident/zall/20006
[2] https://b.corp.google.com/issues/161347350

On Thursday, July 23, 2020 at 9:17:25 AM UTC-4, Rob Curtis wrote:
>
> Hi, I'm suddenly getting hundreds of 503 errors when call task handler in 
> service.
>
> Is anyone else experiencing this outage?
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/14a1ef47-7834-4bcb-9ab5-e1200d9aa01bo%40googlegroups.com.

[google-appengine] Re: cloudsearch.googleapi is returning drastically wrong result count for a particular

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

Hello Sudeshna,

Thank you for reporting this potential issue.

Since you are mentioning that the API call is returning the wrong result 
count, it might be better to engage our engineers through another system. 
This[1] issue tracker system will allow you log a ticket with them. Then, 
we could follow-up with it.

Thank you.

[1] https://cloud.google.com/support/docs/issue-trackers

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a62a0557-963c-44e6-8345-9a89f94402aao%40googlegroups.com.

[google-appengine] Re: How to protect for Host Header Injection in Endpoints on AppEngine

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

Hello Alexandru,

Thank you for reporting this potential issue.

It would be preferable to post this type of issue directly with our 
engineering team. You mentioned "As far as I understood from the Endpoints 
Team"... And I'm wondering if you already did post that with them? I 
searched and couldn't find such a post in our system. The process on how to 
do it is listed here[1] and it shows you how to access that ticketing 
system to submit your issue.

Could you let me know if you've already created such an issue please? I 
don't want to create a duplicate. Then, we could follow-up with it.

Thank you.

[1] https://cloud.google.com/support/docs/issue-trackers

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0302f2ac-c9db-4c6a-9e1f-c9f37793e95fo%40googlegroups.com.