[google-appengine] Google Appengine trying to serve me files instead of a route

[Amiran G]

Hi,

I've got a node server (express) that needs to serve files from Storage. 
The url would look something like example.com/thumbnails/filename.jpg

I have registered a route with express for /thumbnails/:id which works fine 
locally on my computer, but on appspot.com it will try to serve me a static 
file instead, which it will not find. I will get a 404 error without the 
server handler ever being invoked.

I have a running server with a debug route 
here: https://fiid-ee.ey.r.appspot.com/api/test/asdasda

The above URL works fine and the handler should just respond with whatever 
is after test/

If you add a .jpg extension, the server will give me a 
404: https://fiid-ee.ey.r.appspot.com/api/test/asdasdasd.jpg

Again, I tested this locally and it doesn't seem to be a feature of the 
server. The 404 page itself is not something implemented in Express nor 
Nuxt.js

-- 
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/8759166e-f5a3-4184-8a95-0a63a3ac1838n%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.

Re: [google-appengine] Re: Appengine Dashboard broken?

[Vitaly Bogomolov]

Same issue.

Also:

Client Errors 
This app has not received any client errors in the last 24 hours.

четверг, 8 октября 2020 г. в 21:08:56 UTC+4, linus@epspot.com: 

> Works again for me now.magic.
>
> Den tor 8 okt. 2020 10:19troberti  skrev:
>
>> We have the same issue, for all our Appengine projects.
>>
>> On Wednesday, October 7, 2020 at 11:02:47 PM UTC+2 linus@gmail.com 
>> wrote:
>>
>>> In cloud console, Appengine Dasboard for a few days it says:
>>>
>>> Current load
>>>
>>> This app has not received any requests in the last 24 hours.
>>>
>>> This is obviously wrong since I have loads of requests in the logs and I 
>>> get billed for them as well.
>>>
>>> This used to show the top 10 or 20 requested urls, is it broken?
>>>
>>> The Dashboard in Home works as expected.
>>>
>>>
>>> -- 
>> 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-appengi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/81428dd7-9003-4dd7-98de-2a52042cdd9en%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/985e1410-0ac1-47c5-8abd-2708c0bca0e5n%40googlegroups.com.

[google-appengine] Re: Cloud Tasks UI no longer accessible from python2.7 standard?

[Will Reiher]

I took the plunge and "enabled" the API on my legacy app. For anyone facing 
the same dilemma it didn't have any negative effects and my queues were all 
present and pending tasks were still queued up. I still had to use the 
button from App Engine to see them though.

On Thursday, October 8, 2020 at 10:02:56 AM UTC-7 Will Reiher wrote:

> When to check on my queues this morning only to find that I had to enable 
> the API. I've been using the Cloud Tasks UI for a while now. I'm nervous 
> that if I enable the API my existing queues will be reset or something. 
>
> My app doesn't seem to be complaining - I rely heavily on the taskqueue so 
> I'm a bit worried about what could happen.
>

-- 



How we’re addressing COVID-19
Health and safety is our top priority. We 
have made arrangements for all staff to work remotely from home to continue 
to provide uninterrupted service, expertise and advice to our authors and 
prospective customers during the unfolding COVID-19 situation. Click here 
for more information .

Connect with 
us at:
 

FriesenPress Mailing Address 
| Suite 300 - 990 Fort St, Victoria, BC, Canada, V8V 3K2
friesenpress.com 
 | friesenpress.com/blog 


You are receiving this email because 
you are a FriesenPress client or partner. This email and any documents 
attached to it may contain confidential information. If you are not the 
intended recipient, you are hereby notified that any disclosure, copying or 
distribution of the contents of this email is prohibited. If you no longer 
wish to receive promotional emails from FriesenPress, please click here 
 to change your settings.

The privacy of your information is important to us. To learn more, visit 
our privacy policy .

-- 
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/c9d963b6-9d87-408e-91ec-53cc6258aa95n%40googlegroups.com.

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

[Will Reiher]

dev_appserver.py requires python 2. You actually run it with python2 and it 
will spawn a python 3 process to handle your python3 app. This allows it to 
support app engine services that use different languages.

On Wednesday, August 12, 2020 at 3:37:14 AM UTC-7 rit...@gmail.com 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
>

-- 



How we’re addressing COVID-19
Health and safety is our top priority. We 
have made arrangements for all staff to work remotely from home to continue 
to provide uninterrupted service, expertise and advice to our authors and 
prospective customers during the unfolding COVID-19 situation. Click here 
for more information .

Connect with 
us at:
 

FriesenPress Mailing Address 
| Suite 300 - 990 Fort St, Victoria, BC, Canada, V8V 3K2
friesenpress.com 
 | friesenpress.com/blog 


You are receiving this email because 
you are a FriesenPress client or partner. This email and any documents 
attached to it may contain confidential information. If you are not the 
intended recipient, you are hereby notified that any disclosure, copying or 
distribution of the contents of this email is prohibited. If you no longer 
wish to receive promotional emails from FriesenPress, please click here 
 to change your settings.

The privacy of your information is important to us. To learn more, visit 
our privacy policy .

-- 
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/395e6328-6e62-44dc-aad3-2f391c60343en%40googlegroups.com.

Re: [google-appengine] Uploads to Legacy Blobstore are Failing with 500, nothing in the logs

[Will Reiher]

I don't remember what the error code was anymore. I just knew that 
something was f'd. It was really a hunch that that new bucket was involved 
and that if my app didn't have permission it might be the answer. I was 
prepared for a very long day but after the permission change it all just 
started working again - with the blobs showing up in that new bucket.

Most of my stuff is using Cloud Storage except for user uploads. I'm 
working to replace that with a UUID based storage name so that I can 
maintain the ability to allow for same-named files to be uploaded.

Of course today Cloud Task UI is not available and it wants me to enable 
the API (I've been using it for months now) Nervous that my queues will be 
erased if I enable it.

On Thursday, October 8, 2020 at 10:03:22 AM UTC-7 Joshua Smith wrote:

> Do you recall if you got 500 errors? I’d expect that to generate 403’s.
>
> Regardless, that does sound like the kind of thing that happened.
>
> Switching to use cloudstorage instead of blobstore wasn’t too hard, so 
> that’s the workaround I’d recommend for anyone else who hits this issue.
>
> I’m mostly just annoyed that google has switched to a support model where 
> they won’t provide timely support unless you pay them $100/month. That’s 
> greedy and stupid.
>
> -Joshua
>
> On Oct 8, 2020, at 12:58 PM, Will Reiher  
> wrote:
>
> I had an issue a few weeks back. It was due to my transition to gcloud 
> deploy. It created a new app-id.appspot.com bucket but my app engine 
> service account did not have permissions. Once I gave it permission it 
> started working again with the blobstore items showing up in the new 
> "default" bucket.
>
> On Thursday, October 8, 2020 at 3:13:28 AM UTC-7 barrado wrote:
>
>>
>> Hi,
>>
>> I have deployed this Blobstore API sample 
>> 
>>  service 
>> and it works well and allows me to successfully upload images. You could 
>> try to add further logging statements in your app to know what is causing 
>> your issue. 
>>
>> On the other hand, I recommend you to fully migrate you app to Python3 
>> since Python 2 is no longer supported by the community and use Cloud 
>> Storage instead of Blobstore.
>>
>> And also note that appcfg tooling was shuted down 
>>  on August 30th, 
>> 2020.
>>
>>
>> On Wednesday, October 7, 2020 at 4:17:44 PM UTC+2 Joshua Smith wrote:
>>
>>> Unfortunately, I used gcloud app deploy because appcfg.py stopped 
>>> working a couple weeks ago.
>>>
>>> I did use curl and it revealed nothing. Just a terse 500 with no content 
>>> from the server.
>>>
>>> On Oct 6, 2020, at 4:14 PM, Charounson Saintilus  
>>> wrote:
>>>
>>> Hey Joshua,
>>>
>>> I don’t think I’m gonna be of much help here, but wanted to mention: if 
>>> you think that running “gcloud app deploy” introduced the issue, can 
>>> you try redeploying the application using appcfg.py? 
>>>
>>> You could also use curl commands to troubleshoot the upload to 
>>> blobstore.. 
>>>
>>> Thanks,
>>>
>>> Char 
>>>
>>> On Tue, Oct 6, 2020 at 3:40 PM Joshua Smith  
>>> wrote:
>>>
 The problem persists.

 It occurs to me that last week was the first time I had to make a small 
 update to the app in a while, and I did that using “gcloud app deploy” 
  instead of appcfg.py for the first time on that project.

 Is it possible that pushing the app using gcloud introduced a problem 
 uploading to blobstore? I wouldn’t think they’d be related, but the timing 
 is suspicious.

 Downloading from blobstore still works. It’s only uploads that are 
 failing.

 My users are getting upset, and your lack of feedback or an ETA is not 
 helping.

 -Joshua

 On Oct 6, 2020, at 11:47 AM, 'Olu' via Google App Engine <
 google-a...@googlegroups.com> wrote:

 Hi, Joshua

 Thank you for reporting this issue. It seems you may be affected by an 
 internal issue reported about App Engine standard applications returning 
 elevated HTTP 500 errors. This issue is observed for App Engine  Standard 
 instances in us-central1 region. This issue is externalized on the GCP 
 Status Page as you can find more information on the Status board[1].

 I apologize for the delay or the impact this issue may be causing. For 
 swifter responses or help on issues that are urgent to you, I think it is 
 best to reach out directly to the GCP Support Engineers[2]. 

 Let us know if your application is not running in the us-central1 
 region.  

 Thank you. 

 [1]https://status.cloud.google.com/incident/appengine/20007
 [2]https://cloud.google.com/support-hub

 On Tuesday, October 6, 2020 at 10:58:39 AM UTC-4 Joshua Smith wrote:

> The silence here is deafening, but my users are howling.
>
> *Google: Please address 

Re: [google-appengine] Re: Appengine Dashboard broken?

[Linus Larsen]

Works again for me now.magic.

Den tor 8 okt. 2020 10:19troberti  skrev:

> We have the same issue, for all our Appengine projects.
>
> On Wednesday, October 7, 2020 at 11:02:47 PM UTC+2 linus@gmail.com
> wrote:
>
>> In cloud console, Appengine Dasboard for a few days it says:
>>
>> Current load
>>
>> This app has not received any requests in the last 24 hours.
>>
>> This is obviously wrong since I have loads of requests in the logs and I
>> get billed for them as well.
>>
>> This used to show the top 10 or 20 requested urls, is it broken?
>>
>> The Dashboard in Home works as expected.
>>
>>
>> --
> 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/81428dd7-9003-4dd7-98de-2a52042cdd9en%40googlegroups.com
> 
> .
>

-- 
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/CAKKTta0rKCxqiu60GBv2AbAqvT5OBCri7S2zcSm-ZN%2Bv%3DqS5WQ%40mail.gmail.com.

Re: [google-appengine] Uploads to Legacy Blobstore are Failing with 500, nothing in the logs

[Joshua Smith]

Do you recall if you got 500 errors? I’d expect that to generate 403’s.

Regardless, that does sound like the kind of thing that happened.

Switching to use cloudstorage instead of blobstore wasn’t too hard, so that’s 
the workaround I’d recommend for anyone else who hits this issue.

I’m mostly just annoyed that google has switched to a support model where they 
won’t provide timely support unless you pay them $100/month. That’s greedy and 
stupid.

-Joshua

> On Oct 8, 2020, at 12:58 PM, Will Reiher  wrote:
> 
> I had an issue a few weeks back. It was due to my transition to gcloud 
> deploy. It created a new app-id.appspot.com bucket but my app engine service 
> account did not have permissions. Once I gave it permission it started 
> working again with the blobstore items showing up in the new "default" bucket.
> 
> On Thursday, October 8, 2020 at 3:13:28 AM UTC-7 barrado wrote:
> 
> Hi,
> 
> I have deployed this Blobstore API sample 
> 
>  service and it works well and allows me to successfully upload images. You 
> could try to add further logging statements in your app to know what is 
> causing your issue. 
> 
> On the other hand, I recommend you to fully migrate you app to Python3 since 
> Python 2 is no longer supported by the community and use Cloud Storage 
> instead of Blobstore.
> 
> And also note that appcfg tooling was shuted down 
>  on August 30th, 2020.
> 
> 
> On Wednesday, October 7, 2020 at 4:17:44 PM UTC+2 Joshua Smith wrote:
> Unfortunately, I used gcloud app deploy because appcfg.py stopped working a 
> couple weeks ago.
> 
> I did use curl and it revealed nothing. Just a terse 500 with no content from 
> the server.
> 
> 
>> On Oct 6, 2020, at 4:14 PM, Charounson Saintilus > 
>> wrote:
>> 
> 
>> Hey Joshua,
>> 
>> I don’t think I’m gonna be of much help here, but wanted to mention: if you 
>> think that running “gcloud app deploy” introduced the issue, can you try 
>> redeploying the application using appcfg.py? 
>> 
>> You could also use curl commands to troubleshoot the upload to blobstore.. 
>> 
>> Thanks,
>> 
>> Char 
>> 
>> On Tue, Oct 6, 2020 at 3:40 PM Joshua Smith > wrote:
>> The problem persists.
>> 
>> It occurs to me that last week was the first time I had to make a small 
>> update to the app in a while, and I did that using “gcloud app deploy”  
>> instead of appcfg.py for the first time on that project.
>> 
>> Is it possible that pushing the app using gcloud introduced a problem 
>> uploading to blobstore? I wouldn’t think they’d be related, but the timing 
>> is suspicious.
>> 
>> Downloading from blobstore still works. It’s only uploads that are failing.
>> 
>> My users are getting upset, and your lack of feedback or an ETA is not 
>> helping.
>> 
>> -Joshua
>> 
>>> On Oct 6, 2020, at 11:47 AM, 'Olu' via Google App Engine 
>>> > wrote:
>>> 
>> 
>>> Hi, Joshua
>>> 
>>> Thank you for reporting this issue. It seems you may be affected by an 
>>> internal issue reported about App Engine standard applications returning 
>>> elevated HTTP 500 errors. This issue is observed for App Engine  Standard 
>>> instances in us-central1 region. This issue is externalized on the GCP 
>>> Status Page as you can find more information on the Status board[1].
>>> 
>>> I apologize for the delay or the impact this issue may be causing. For 
>>> swifter responses or help on issues that are urgent to you, I think it is 
>>> best to reach out directly to the GCP Support Engineers[2]. 
>>> 
>>> Let us know if your application is not running in the us-central1 region.  
>>> 
>>> Thank you. 
>>> 
>>> [1]https://status.cloud.google.com/incident/appengine/20007 
>>> 
>>> [2]https://cloud.google.com/support-hub 
>>> 
>>> 
>>> On Tuesday, October 6, 2020 at 10:58:39 AM UTC-4 Joshua Smith wrote:
>>> The silence here is deafening, but my users are howling.
>>> 
>>> Google: Please address this issue immediately! It’s been down at least 24 
>>> hours!
>>> 
>>> I created an issue in public issue tracker with the same info you see here: 
>>> 170195261 
>>> 
>>> I highly doubt I’m the only one experiencing this.
>>> 
>>> -Joshua
>>> 
>>> 
 On Oct 5, 2020, at 11:50 AM, Joshua Smith > wrote:
 
 There is a production issue in my app. (I’m happy to create a private 
 production issue ticket, but I couldn’t figure out where to do that.)
 
 My app is still on Python 2.7 and uses the legacy blobstore.
 
 I use blobstore.create_upload_url('/upload’) to populate a form. This has 
 been working fine for several years.
 
 The last successful one was: 02/Oct/2020:11:37:23 -0400
 
 As of this morning, attempts to upload to the blobstore are resulting in 
 error 

[google-appengine] Cloud Tasks UI no longer accessible from python2.7 standard?

[Will Reiher]

When to check on my queues this morning only to find that I had to enable 
the API. I've been using the Cloud Tasks UI for a while now. I'm nervous 
that if I enable the API my existing queues will be reset or something. 

My app doesn't seem to be complaining - I rely heavily on the taskqueue so 
I'm a bit worried about what could happen.

-- 



How we’re addressing COVID-19
Health and safety is our top priority. We 
have made arrangements for all staff to work remotely from home to continue 
to provide uninterrupted service, expertise and advice to our authors and 
prospective customers during the unfolding COVID-19 situation. Click here 
for more information .

Connect with 
us at:
 

FriesenPress Mailing Address 
| Suite 300 - 990 Fort St, Victoria, BC, Canada, V8V 3K2
friesenpress.com 
 | friesenpress.com/blog 


You are receiving this email because 
you are a FriesenPress client or partner. This email and any documents 
attached to it may contain confidential information. If you are not the 
intended recipient, you are hereby notified that any disclosure, copying or 
distribution of the contents of this email is prohibited. If you no longer 
wish to receive promotional emails from FriesenPress, please click here 
 to change your settings.

The privacy of your information is important to us. To learn more, visit 
our privacy policy .

-- 
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/3a55c33d-879b-48fc-8456-1a663dd34b88n%40googlegroups.com.

Re: [google-appengine] Uploads to Legacy Blobstore are Failing with 500, nothing in the logs

[Will Reiher]

I had an issue a few weeks back. It was due to my transition to gcloud 
deploy. It created a new app-id.appspot.com bucket but my app engine 
service account did not have permissions. Once I gave it permission it 
started working again with the blobstore items showing up in the new 
"default" bucket.

On Thursday, October 8, 2020 at 3:13:28 AM UTC-7 barrado wrote:

>
> Hi,
>
> I have deployed this Blobstore API sample 
> 
>  service 
> and it works well and allows me to successfully upload images. You could 
> try to add further logging statements in your app to know what is causing 
> your issue. 
>
> On the other hand, I recommend you to fully migrate you app to Python3 
> since Python 2 is no longer supported by the community and use Cloud 
> Storage instead of Blobstore.
>
> And also note that appcfg tooling was shuted down 
>  on August 30th, 
> 2020.
>
>
> On Wednesday, October 7, 2020 at 4:17:44 PM UTC+2 Joshua Smith wrote:
>
>> Unfortunately, I used gcloud app deploy because appcfg.py stopped working 
>> a couple weeks ago.
>>
>> I did use curl and it revealed nothing. Just a terse 500 with no content 
>> from the server.
>>
>> On Oct 6, 2020, at 4:14 PM, Charounson Saintilus  
>> wrote:
>>
>> Hey Joshua,
>>
>> I don’t think I’m gonna be of much help here, but wanted to mention: if 
>> you think that running “gcloud app deploy” introduced the issue, can you 
>> try redeploying the application using appcfg.py? 
>>
>> You could also use curl commands to troubleshoot the upload to 
>> blobstore.. 
>>
>> Thanks,
>>
>> Char 
>>
>> On Tue, Oct 6, 2020 at 3:40 PM Joshua Smith  wrote:
>>
>>> The problem persists.
>>>
>>> It occurs to me that last week was the first time I had to make a small 
>>> update to the app in a while, and I did that using “gcloud app deploy” 
>>>  instead of appcfg.py for the first time on that project.
>>>
>>> Is it possible that pushing the app using gcloud introduced a problem 
>>> uploading to blobstore? I wouldn’t think they’d be related, but the timing 
>>> is suspicious.
>>>
>>> Downloading from blobstore still works. It’s only uploads that are 
>>> failing.
>>>
>>> My users are getting upset, and your lack of feedback or an ETA is not 
>>> helping.
>>>
>>> -Joshua
>>>
>>> On Oct 6, 2020, at 11:47 AM, 'Olu' via Google App Engine <
>>> google-a...@googlegroups.com> wrote:
>>>
>>> Hi, Joshua
>>>
>>> Thank you for reporting this issue. It seems you may be affected by an 
>>> internal issue reported about App Engine standard applications returning 
>>> elevated HTTP 500 errors. This issue is observed for App Engine  Standard 
>>> instances in us-central1 region. This issue is externalized on the GCP 
>>> Status Page as you can find more information on the Status board[1].
>>>
>>> I apologize for the delay or the impact this issue may be causing. For 
>>> swifter responses or help on issues that are urgent to you, I think it is 
>>> best to reach out directly to the GCP Support Engineers[2]. 
>>>
>>> Let us know if your application is not running in the us-central1 
>>> region.  
>>>
>>> Thank you. 
>>>
>>> [1]https://status.cloud.google.com/incident/appengine/20007
>>> [2]https://cloud.google.com/support-hub
>>>
>>> On Tuesday, October 6, 2020 at 10:58:39 AM UTC-4 Joshua Smith wrote:
>>>
 The silence here is deafening, but my users are howling.

 *Google: Please address this issue immediately! It’s been down at least 
 24 hours!*

 I created an issue in public issue tracker with the same info you see 
 here: 170195261 

 I highly doubt I’m the only one experiencing this.

 -Joshua


 On Oct 5, 2020, at 11:50 AM, Joshua Smith  wrote:

 There is a production issue in my app. (I’m happy to create a private 
 production issue ticket, but I couldn’t figure out where to do that.)

 My app is still on Python 2.7 and uses the legacy blobstore.

 I use blobstore.create_upload_url('/upload’) to populate a form. This 
 has been working fine for several years.

 The last successful one was: 02/Oct/2020:11:37:23 -0400

 As of this morning, attempts to upload to the blobstore are resulting 
 in error 500 and I don’t see the request in my logs.

 I simulated one of these uploads using curl, but that produced no 
 insight:

 * Using HTTP2, server supports multi-use
 * Connection state changed (HTTP/2 confirmed)
 * Copying HTTP/2 data in stream buffer to connection buffer after 
 upgrade: len=0
 * Using Stream ID: 1 (easy handle 0x7fa064808200)
 > POST /_ah/upload/AMmfu6YC1hHSvQPFczp—redacted—Pt3zS4LmedW5GR/ HTTP/2
 > Host: —redacted— 
 > User-Agent: curl/7.64.1
 > Accept: */*
 > Content-Length: 12881
 > Content-Type: 

[google-appengine] App engine connection to cloud storage

[Punita Goel]

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/0be4291b-0de4-47db-bee3-4449ff11c1fdn%40googlegroups.com.

Re: [google-appengine] Uploads to Legacy Blobstore are Failing with 500, nothing in the logs

['barrado' via Google App Engine]

Hi,

I have deployed this Blobstore API sample 

 service 
and it works well and allows me to successfully upload images. You could 
try to add further logging statements in your app to know what is causing 
your issue. 

On the other hand, I recommend you to fully migrate you app to Python3 
since Python 2 is no longer supported by the community and use Cloud 
Storage instead of Blobstore.

And also note that appcfg tooling was shuted down 
 on August 30th, 2020.


On Wednesday, October 7, 2020 at 4:17:44 PM UTC+2 Joshua Smith wrote:

> Unfortunately, I used gcloud app deploy because appcfg.py stopped working 
> a couple weeks ago.
>
> I did use curl and it revealed nothing. Just a terse 500 with no content 
> from the server.
>
> On Oct 6, 2020, at 4:14 PM, Charounson Saintilus  
> wrote:
>
> Hey Joshua,
>
> I don’t think I’m gonna be of much help here, but wanted to mention: if 
> you think that running “gcloud app deploy” introduced the issue, can you 
> try redeploying the application using appcfg.py? 
>
> You could also use curl commands to troubleshoot the upload to blobstore.. 
>
> Thanks,
>
> Char 
>
> On Tue, Oct 6, 2020 at 3:40 PM Joshua Smith  wrote:
>
>> The problem persists.
>>
>> It occurs to me that last week was the first time I had to make a small 
>> update to the app in a while, and I did that using “gcloud app deploy” 
>>  instead of appcfg.py for the first time on that project.
>>
>> Is it possible that pushing the app using gcloud introduced a problem 
>> uploading to blobstore? I wouldn’t think they’d be related, but the timing 
>> is suspicious.
>>
>> Downloading from blobstore still works. It’s only uploads that are 
>> failing.
>>
>> My users are getting upset, and your lack of feedback or an ETA is not 
>> helping.
>>
>> -Joshua
>>
>> On Oct 6, 2020, at 11:47 AM, 'Olu' via Google App Engine <
>> google-a...@googlegroups.com> wrote:
>>
>> Hi, Joshua
>>
>> Thank you for reporting this issue. It seems you may be affected by an 
>> internal issue reported about App Engine standard applications returning 
>> elevated HTTP 500 errors. This issue is observed for App Engine  Standard 
>> instances in us-central1 region. This issue is externalized on the GCP 
>> Status Page as you can find more information on the Status board[1].
>>
>> I apologize for the delay or the impact this issue may be causing. For 
>> swifter responses or help on issues that are urgent to you, I think it is 
>> best to reach out directly to the GCP Support Engineers[2]. 
>>
>> Let us know if your application is not running in the us-central1 
>> region.  
>>
>> Thank you. 
>>
>> [1]https://status.cloud.google.com/incident/appengine/20007
>> [2]https://cloud.google.com/support-hub
>>
>> On Tuesday, October 6, 2020 at 10:58:39 AM UTC-4 Joshua Smith wrote:
>>
>>> The silence here is deafening, but my users are howling.
>>>
>>> *Google: Please address this issue immediately! It’s been down at least 
>>> 24 hours!*
>>>
>>> I created an issue in public issue tracker with the same info you see 
>>> here: 170195261 
>>>
>>> I highly doubt I’m the only one experiencing this.
>>>
>>> -Joshua
>>>
>>>
>>> On Oct 5, 2020, at 11:50 AM, Joshua Smith  wrote:
>>>
>>> There is a production issue in my app. (I’m happy to create a private 
>>> production issue ticket, but I couldn’t figure out where to do that.)
>>>
>>> My app is still on Python 2.7 and uses the legacy blobstore.
>>>
>>> I use blobstore.create_upload_url('/upload’) to populate a form. This 
>>> has been working fine for several years.
>>>
>>> The last successful one was: 02/Oct/2020:11:37:23 -0400
>>>
>>> As of this morning, attempts to upload to the blobstore are resulting in 
>>> error 500 and I don’t see the request in my logs.
>>>
>>> I simulated one of these uploads using curl, but that produced no 
>>> insight:
>>>
>>> * Using HTTP2, server supports multi-use
>>> * Connection state changed (HTTP/2 confirmed)
>>> * Copying HTTP/2 data in stream buffer to connection buffer after 
>>> upgrade: len=0
>>> * Using Stream ID: 1 (easy handle 0x7fa064808200)
>>> > POST /_ah/upload/AMmfu6YC1hHSvQPFczp—redacted—Pt3zS4LmedW5GR/ HTTP/2
>>> > Host: —redacted— 
>>> > User-Agent: curl/7.64.1
>>> > Accept: */*
>>> > Content-Length: 12881
>>> > Content-Type: multipart/form-data; 
>>> boundary=c1bce33de7c355c9
>>> > 
>>> * Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
>>> * We are completely uploaded and fine
>>> < HTTP/2 500 
>>> < x-guploader-uploadid: 
>>> ABg5-UyVR-AC3_kY-A3vD45EgWUWJjzynvU_S0rDjhhsIlyJsDmYRU-ZrjSLe9Pppe7eCd-S9dHAv_7dVcsvfMj5wS0
>>> < content-length: 0
>>> < date: Mon, 05 Oct 2020 15:38:41 GMT
>>> < server: UploadServer
>>> < content-type: text/html; charset=UTF-8
>>> < 
>>> * Connection #0 to host 

[google-appengine] Re: Appengine Dashboard broken?

[troberti]

We have the same issue, for all our Appengine projects.

On Wednesday, October 7, 2020 at 11:02:47 PM UTC+2 linus@gmail.com 
wrote:

> In cloud console, Appengine Dasboard for a few days it says:
>
> Current load
>
> This app has not received any requests in the last 24 hours.
>
> This is obviously wrong since I have loads of requests in the logs and I 
> get billed for them as well.
>
> This used to show the top 10 or 20 requested urls, is it broken?
>
> The Dashboard in Home works as expected.
>
>
>

-- 
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/81428dd7-9003-4dd7-98de-2a52042cdd9en%40googlegroups.com.