[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

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

Hello Matt, 


As the issue is related to user’s deployment failure sometimes which is an 
indicator that this issue shouldn't be reported on Google Groups as this 
forum is meant for general discussion of the platform, not specific 
technical issues. 


What's needed for anybody who would want to report a technical issue, is to 
use the issue tracker  
rather than google groups so that we can properly involve the engineering 
team and further investigate this deployment issue in the public issue 
tracker. If it is required to share any private or project specific 
information please choose the “Private” component so that the information 
are not visible to the public. 


I wish you the best of luck in proceeding to either open a proper issue 
report in the public issue tracker. 


I would also encourage you to share the public issue tracker link in this 
thread if you keep that public so that other users can go to the link for 
resolution or they can see the updates on the issue. 



On Friday, January 18, 2019 at 3:25:29 PM UTC-5, Matt Haff wrote:
>
> I'm having the same issue, I posted a separate question here per Nick's 
> request - 
> https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/google-appengine/NJMzqz5JqZQ
>

-- 
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/7e695132-6a2a-4202-b8db-bccea1ca86bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Can't make a new NodeJS App Deploy

[Jason Collins]

This should be fixed as of yesterday afternoon (Pacific Time). Please let 
us know if you are still seeing this issue.


On Tuesday, 22 January 2019 15:58:38 UTC-8, Paulo Freitas wrote:
>
> Hello guys,
>
> I have a nodejs service running in the AppEngine for a while. But today, 
> now, I tried to do a new deploy, `gcloud app deploy` and get a constant 
> *build 
> error* with a link to the log bellow, in itallic.
> Anyone with the same issue? Does anyone has any clue on how to solve it?
>
> att, 
>
> Paulo Freitas
>
>
> Log here
>
> *starting build "3f82f9df-292c-4956-9558-43dcbc1400fa" FETCHSOURCE BUILD 
> Starting Step #0 - "fetcher" Step #0 - "fetcher": Already have image (with 
> digest): gcr.io/cloud-builders/gcs-fetcher 
>  Step #0 - "fetcher": Fetching 
> manifest 
> gs://staging.small-talk-3972f.appspot.com/ae/1081fb4b-8d15-4cda-a21c-e7a42a8a0e3d/manifest.json
>  
> .
>  
> Step #0 - "fetcher": Processing 1785 files. Step #0 - "fetcher": 
> ** Step #0 - "fetcher": 
> Status: SUCCESS Step #0 - "fetcher": Started: 2019-01-22T18:35:38Z Step #0 
> - "fetcher": Completed: 2019-01-22T18:35:41Z Step #0 - "fetcher": Requested 
> workers: 200 Step #0 - "fetcher": Actual workers: 200 Step #0 - "fetcher": 
> Total files: 1785 Step #0 - "fetcher": Total retries: 0 Step #0 - 
> "fetcher": GCS timeouts: 0 Step #0 - "fetcher": MiB downloaded: 5.93 MiB 
> Step #0 - "fetcher": MiB/s throughput: 2.57 MiB/s Step #0 - "fetcher": Time 
> for manifest: 322.05 ms Step #0 - "fetcher": Total time: 2.65 s Step #0 - 
> "fetcher": ** Finished 
> Step #0 - "fetcher" Starting Step #1 - "builder" Step #1 - "builder": 
> Pulling image: 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found Step #1 - "builder": Error response from daemon: manifest for 
> gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
>  
> not found ERROR: failed to pull because we ran out of retries. ERROR ERROR: 
> build step 1 
> "gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
> "
>  
> failed: error pulling build step 1 
> "gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 
> ":
>  
> exit 

[google-appengine] Re: Can't make a new NodeJS App Deploy

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

Hello Paulo, 

More information is needed to start our investigation properly. What steps 
have you undertaken prior to running this command? Have you modified 
anything in your application's code or app.yaml configuration file? 

As a first step, you may consider running 'gcloud components update', and 
then trying to run gcloud init again. 

After doing so, what is the output from the following commands? 

gcloud info 

gcloud app deploy --verbosity=debug 

All sensitive information should be deleted or overwritten from replies, to 
safeguard your privacy. 

A copy of your app.yaml file, sensitive information redacted out, is also 
needed, enabling us to recreate your environment in view of eventual error 
reproduction.

-- 
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/c950582e-8e3c-4be4-9f75-f29fd3ef04bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How do I setup routing for react in GAE? Directly routing to react-router-dom routes via URL fails in GAE on basic create-react-app?

[dangelot via Google App Engine]

Hello, 

It seems that you got a great answer on Stack overflow already[1]

Should you have any concern regarding this issue please do not hesitate to 
contact us.

[1] 
https://stackoverflow.com/questions/54247953/how-do-i-setup-routing-for-react-in-gae-directly-routing-to-react-router-dom-ro


On Friday, January 18, 2019 at 3:17:45 PM UTC-5, Nathan Grubb wrote:
>
>
> *Setting GAE app.yaml for react-router routes produces "Unexpected token 
> <" errors.*
> -
>
> In the development environment, all routes work when called directly.  
> localhost:5000 and localhost:5000/test produce expected results.
>
> In GAE standard app.yaml functions for the root directory when the URL 
> www.test-app.com is called directly.  ***www.test-app.com/test 
>  produces a 404 error.***
>
> app.yaml #1
> runtime: nodejs8
> instance_class: F1
> automatic_scaling:
>   max_instances: 1
>
>
> handlers:
>   - url: /
> static_files: build/index.html
> upload: build/index.html
>   - url: /
> static_dir: build
>
>
> Configuring app.yaml to accept wildcard routes fails for all paths.  
> www.test-app.com/ and www.test-app.com/test produce an error *"Unexpected 
> token <"*.  It appears that it is serving .js files as index.html.
>
> app.yaml #2
> runtime: nodejs8
> instance_class: F1
> automatic_scaling:
>   max_instances: 1
>
>
> handlers:
>   - url: /.*
> static_files: build/index.html
> upload: build/index.html
>   - url: /
> static_dir: build
>
>
> *Steps to reproduce this issue:*
> ==
>
> Node: 10.15.0
> npm: 6.4.1
>
> gcloud init via Google Cloud SDK
>
> npm init react-app test-app
>
>
> npm install react-router-dom
>
>
> Add router to index.js:
>
> index.js
> import {BrowserRouter as Router, Route} from 'react-router-dom';
> import React from 'react';
> import ReactDOM from 'react-dom';
> import './index.css';
> import App from './App';
> import * as serviceWorker from './serviceWorker';
>
>
>
>
> ReactDOM.render(
>   
> 
>   ,
>   document.getElementById('root'));
> serviceWorker.unregister();
>
>
>
> Add routing to app.js:
>
> app.js
> import {Route} from 'react-router-dom'
> import React, { Component } from 'react';
> import logo from './logo.svg';
> import './App.css';
>
>
> class App extends Component {
>   render() {
> return (
>   
>render={() =>  
> 
>   
>   
> Edit src/App.js and save to reload.
>   
>className="App-link"
> href="https://reactjs.org;
> target="_blank"
> rel="noopener noreferrer"
>   >
> Learn React
>   
> 
>   } />
>render={() =>  
> Hello, World!
>   } />
>   
> );
>   }
> }
>
>
> export default App;
>
>
> No changes to package.json:
>
> package.json
> {
>   "name": "test-app",
>   "version": "0.1.0",
>   "private": true,
>   "dependencies": {
> "react": "^16.7.0",
> "react-dom": "^16.7.0",
> "react-router-dom": "^4.3.1",
> "react-scripts": "2.1.3"
>   },
>   "scripts": {
> "start": "react-scripts start",
> "build": "react-scripts build",
> "test": "react-scripts test",
> "eject": "react-scripts eject"
>   },
>   "eslintConfig": {
> "extends": "react-app"
>   },
>   "browserslist": [
> ">0.2%",
> "not dead",
> "not ie <= 11",
> "not op_mini all"
>   ]
> }
>
>
> npm run build 
>
>
> gcloud app deploy
>
>
>
> How do we convince app engine to allow a react SPA to process routes 
> directly?
> -
>

-- 
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/9ed158a0-d120-46c6-ae59-dbf89be96675%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: What is the expected output for app_identity.get_default_version_hostname()

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

Hello,

Please look into this document 
,
 
which describes using the app_identity.get_default_version_hostname() 
method you can retrieve the entire hostname component if an app is served 
from a custom domain where the app ID is part of the hostname (i.e. 
http://.appspot.com). So as George mentioned earlier you are 
getting expected behavior from the 
app_identity.get_default_version_hostname() method.

Regarding your second question, if your domain is mapped to your App Engine 
app you can use the apps.domainMappings.list 

 
method to list your resource records. You can also achieve this using 
Console or gcloud command "gcloud app domain-mappings list" 
. 
 You can get more details on this at number four point of this document 

 
and on gcloud command “gcloud app domain-mappings” here 
. If 
your domain is not mapped, to programmatically map your domain to your App 
Engine app you can use the app.domainMappings.create 

 
method. You can find more about the methods available with REST Resource: 
apps.domainMappings here 
.
 



On Wednesday, January 16, 2019 at 7:21:00 PM UTC-5, NP wrote:
>
> Thanks for the response.
>
> With regards to question 2, if the project is being deployed by different 
> users (hence different domains), you wouldn't know the custom domain URL 
> upfront. A work around is to have user enter the value, which then gets 
> stored and then you read it. I just wanted to know if there was an API that 
> provided this value directly so that I wouldn't be reinventing the wheel.
>
>
> On Wednesday, January 16, 2019 at 1:44:38 PM UTC-8, George (Cloud Platform 
> Support) wrote:
>>
>> In reply to your first question, you are right: 
>> google.appengine.api.app_identity.app_identity.get_default_version_hostname()
>>  
>> gets the standard host name of the default version of the app. For example, 
>> if your application_id is my-app, then the result might be 
>> my-app.appspot.com. You may check this on the 
>> "google.appengine.api.app_identity.app_identity module" page 
>> 
>> . 
>>
>> In what concerns question 2), there does not seem to be a compelling need 
>> to programmatically obtain the custom name instead, as the standard host 
>> name and the custom one point to the same site, and can be used 
>> interchangeably. Mapping between custom ID has been performed by project 
>> owners, and the information should be readily available, even if not by 
>> means of an API call from your code. In other words, you are supposed to 
>> know your custom domain URL already. 
>>
>

-- 
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/d33d10db-1c0e-4399-8b6f-fa639c9a9cb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: app.yaml not being recognized by my app

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

Hi David,

Dev app server was previously used to test your application on local 
environment replicating the App Engine First Generation’s behavior 
 
however as GO 1.11 is now running on the Second Generation there is no need 
to use Dev app server anymore.

The Second Generation of App Engine will run your code exactly how it would 
run on your local machine.

That being said, the command to run your Go 1.11 application on your local 
environment is “go run 
”.
 
Please note that Go 1.11 is in Beta release meaning that this feature could 
change and is not subject to any SLA.



On Thursday, January 17, 2019 at 11:33:07 AM UTC-5, David Manz wrote:
>
> I didn't have 'api_version' in the app.yaml.  I don't think the app.yaml 
> was being read at all.
>
> With Go 1.11, what is the correct way to start the app locally?  Is it 'go 
> run .', or is it 'goapp serve'?  'goapp serve' isn't working for me on 
> Windows, because I have a space in my path:
>
> > "\Users\David\AppData\Local\Google\Cloud 
> SDK\google-cloud-sdk\platform\google_appengine\goapp" serve
> python: can't open file 'C:\Users\David\AppData\Local\Google\Cloud': 
> [Errno 2] No such file or directory
>
> David
>
>
> On Thursday, January 17, 2019 at 9:02:41 AM UTC-6, Omair (Cloud Platform 
> Support) wrote:
>>
>> Hi David,
>>
>> The reason it does not work for runtime go111 is because 'api_version' is 
>> not a supported element for Go 1.11. For full list of supported elements 
>> for Go 1.11 click here 
>> .
>>  
>> The supported elements for Go 1.9 can be seen here 
>> 
>> .
>>
>> I hope this helps. 
>>
>> On Wednesday, January 16, 2019 at 11:31:50 PM UTC-5, David Manz wrote:
>>>
>>> If I modify the app.yaml like this:
>>>
>>> #runtime: go111
>>> runtime: go
>>> api_version: go1
>>>
>>>
>>> then I can run "dev_appserver.py ./app.yaml", and I can see my static 
>>> content.
>>>
>>> I don't know why runtime:go111 doesn't work, but I suppose this works 
>>> for now.
>>>
>>> Thanks again!
>>>
>>> David
>>>
>>>
>>> On Wednesday, January 16, 2019 at 9:54:34 PM UTC-6, David Manz wrote:

 Hi George,

 Thanks for the help.

 I did find the documentation on serving static content, but I think 
 there's something more basic that I'm missing.  If I delete app.yaml from 
 the directory entirely, then I don't see any errors--just the same 
 behavior.

 My directory looks like this:

 src/myapp/app.yaml
 src/myapp/myappscript.go
 src/myapp/myapptemplate.html
 src/myapp/static/x.png

 and I'm doing 'go run .' in the Google Cloud SDK Shell from inside 
 src/myapp/

 >dev_appserver.py ./app.yaml

 INFO 2019-01-15 20:06:17,151 devappserver2.py:120] Skipping SDK 
 update check.
 INFO 2019-01-15 20:06:17,960 api_server.py:274] Starting API server 
 at: http://localhost:4291
 INFO 2019-01-15 20:06:17,960 stub_util.py:357] Applying all pending 
 transactions and saving the datastore
 INFO 2019-01-15 20:06:17,960 stub_util.py:360] Saving search indexes
 Traceback (most recent call last):
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\dev_appserver.py", line 96, 
 in 
 _run_file(__file__, globals())
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\dev_appserver.py", line 90, 
 in _run_file
 execfile(_PATHS.script_file(script_name), globals_)
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\devappserver2.py",
  
 line 454, in 
 main()
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\devappserver2.py",
  
 line 442, in main
 dev_server.start(options)
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\devappserver2.py",
  
 line 202, in start
 options.api_host, apiserver.port, wsgi_request_info_)
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\dispatcher.py",
  
 line 262, in start
 ssl_port)
   File "C:\Users\David\AppData\Local\Google\Cloud 
 SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\dispatcher.py",
  
 line 403, in _create_module
 ssl_port=ssl_port)

[google-appengine] Upgraded my account by mistake

[Yatin Arora]

I am using free credit provided by Google for GCP services, but I upgraded 
my account by mistake and now I can see more than 8 cores there available,
what does this mean can I degrade my account back to normal, will they 
charge me after credit over.
how upgrading effects me monetarily 
Please help me regarding this 

-- 
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/40880c84-f10f-498d-a134-00a2ff72d5e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.