[google-appengine] Re: Some API endpoints taking a long time to start work?

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

Hey Ben,

The cpu_ms and ms data can be found in the logs in the Developers' Console. 
Let me know how the timing code works out!

Cheers,

Nick
Cloud Platform Community Support

On Monday, August 22, 2016 at 7:36:41 AM UTC-4, Ben Rometsch wrote:
>
> Hi Nick,
>
> I'm not sure where to find the cpu_ms vs ms times? Can you point me to 
> where I would find that? 
>
> We're using cloud endpoints, so I think the logging is being managed by 
> that library as opposed to us doing any specific logging. 
>
> It's possible the AuthFilter could be waiting on FB - I'll add some 
> logging in there to see. 
>
> Thanks for your help.  
>
> On Friday, 19 August 2016 20:03:22 UTC+1, Nick (Cloud Platform Support) 
> wrote:
>>
>> Hey Ben,
>>
>> Thanks for the quick reply. Did you manage to check the "cpu_ms" vs "ms" 
>> for the request log in question? 
>>
>> As for the way to read the trace, I think the info log tags are showing 
>> up in the timeline when the method completes (with a slight logging delay) 
>> rather than when it starts, as evidenced also by the pattern of the other 
>> method calls. The rectangles show the duration of the method, while the 
>> info log tags are showing up in the timeline associated with these, but are 
>> being inserted by another process. Do you have some sort of config turned 
>> on to log all method calls? 
>>
>> Finally, does the auth filter code require some intensive CPU or a 
>> network call? 
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Friday, August 19, 2016 at 6:07:01 AM UTC-4, Ben Rometsch wrote:
>>>
>>> Thanks for the reply Nick.
>>>
>>> I dont think I was clear in my previous post, but when I think the logs 
>>> are showing is that the call into the AuthFilter is stalling for around 
>>> 1000ms before it actually starts into that method. I'm not sure what could 
>>> be causing that delay? Or maybe I'm reading this screen wrong? 
>>>
>>> On Wednesday, 17 August 2016 10:19:17 UTC+1, Ben Rometsch wrote:

 We are running a Java Cloud Endpoints API on Flexible VMs. Most of the 
 endpoints complete in a timely manner, but from time to time we see things 
 like the attached in the trace:


 


 Does anyone know why/what the platform is doing in the first 1000ms? We 
 have an AuthFilter that runs to check users are authenticated, but 
 normally 
 this runs quickly at the start of the request. We have some API urls that 
 dont go through Cloud Endpoints and they don't exhibit this issue, so are 
 suspicious that its the cloud endpoints but we are not sure? 

>>>

-- 
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/3f36917b-a97b-4f88-ac18-c426ca1ab0cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppEngine Go runtime for Mac OS X 64-bit

[Dmitry Matyukhin]

Just double checked on my MacBook (12" with Intel Core M),

$goapp version
go version go1.6.2 (appengine-1.9.40) darwin/amd64

Initially `go` wasn't installed at all, but 32-bit goapp SDK worked. So I 
installed it with brew and got:
$go version
go version go1.7 darwin/amd64

It still crashes.

$ system_profiler SPHardwareDataType
Hardware:

Hardware Overview:

  Model Name: MacBook
  Model Identifier: MacBook8,1
  Processor Name: Intel Core M
  Processor Speed: 1.3 GHz
  Number of Processors: 1
  Total Number of Cores: 2
  L2 Cache (per Core): 256 KB
  L3 Cache: 4 MB
  Memory: 8 GB
  Boot ROM Version: MB81.0164.B18
  SMC Version (system): 2.25f87
  Serial Number (system): C02PM0NFGCN2
  Hardware UUID: 433DD06F-1BCF-5AA8-884C-FA7B668C0B82

According to Intel, it is a 64-bit processor.

On Tuesday, 30 August 2016 16:35:50 UTC+1, Dmitry Matyukhin wrote:
>
> Adam, thanks for clarification.
>
> I just tried to install it on another machine - MacBook Pro and I can 
> confirm that 64-bit works. The problem was happening on 12-inch MacBook 
> which is also 64-bit, but I'll double check the version of go that is 
> installed.
>
> On Monday, 29 August 2016 21:40:29 UTC+1, Adam (Cloud Platform Support) 
> wrote:
>>
>> AMD64 is actually the standard used by both Intel and AMD, and is just 
>> another name for 'x86-64' or 'x64' . 
>> It's so named because AMD first developed the architecture which Intel 
>> later adopted. Rest assured, we would not release an SDK for a 
>> 'darwin_amd64' architecture if it didn't exist! 
>>
>> As for the reason it's crashing on your system, it's likely that you just 
>> have an older 32-bit version of Go installed. As of Go 1.5, 'darwin-amd64' 
>> is the only supported architecture . You can 
>> confirm your version and architecture by typing 'go version' from the 
>> command prompt.
>>
>> Otherwise, if you have a very old 2008 or prior Mac with a 1st gen Core 
>> processor, your Mac is 32-bit only.
>>
>> On Sunday, August 28, 2016 at 11:45:39 AM UTC-4, Dmitry Matyukhin wrote:
>>>
>>> I tried to use Go Runtime for AppEngine for Mac. Since, there is a 
>>> 64-bit version, I installed that one.
>>>
>>> However, whenever I tried to run anything, it was always crashing. For 
>>> example, this happens when I did "goapp get google.golang.org/appengine"
>>>
>>> # net
>>> fatal error: unexpected signal during runtime execution
>>> [signal 0xb code=0x1 addr=0x1161be989d12 pc=0xf0eb]
>>>
>>> runtime stack:
>>> runtime.throw(0x497380, 0x2a)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/panic.go:547
>>>  
>>> +0x90
>>> runtime.sigpanic()
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/sigpanic_unix.go:12
>>>  
>>> +0x5a
>>> runtime.unlock(0x988540)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/lock_sema.go:107
>>>  
>>> +0x14b
>>> runtime.(*mheap).alloc_m(0x988540, 0x1, 0x21, 0xec2ff0)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:492
>>>  
>>> +0x314
>>> runtime.(*mheap).alloc.func1()
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:502
>>>  
>>> +0x41
>>> runtime.systemstack(0x7fff5fbfe348)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:307
>>>  
>>> +0xab
>>> runtime.(*mheap).alloc(0x988540, 0x1, 0x121, 0xed8f)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:503
>>>  
>>> +0x63
>>> runtime.(*mcentral).grow(0x98a680, 0x0)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:209
>>>  
>>> +0x93
>>> runtime.(*mcentral).cacheSpan(0x98a680, 0xec2ff0)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:89
>>>  
>>> +0x47d
>>> runtime.(*mcache).refill(0xafa000, 0x21, 0xec2ff0)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcache.go:119
>>>  
>>> +0xcc
>>> runtime.mallocgc.func2()
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:642
>>>  
>>> +0x2b
>>> runtime.systemstack(0x979d00)
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:291
>>>  
>>> +0x79
>>> runtime.mstart()
>>> 
>>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/proc.go:1051

[google-appengine] Re: AppEngine Go runtime for Mac OS X 64-bit

[Dmitry Matyukhin]

Adam, thanks for clarification.

I just tried to install it on another machine - MacBook Pro and I can 
confirm that 64-bit works. The problem was happening on 12-inch MacBook 
which is also 64-bit, but I'll double check the version of go that is 
installed.

On Monday, 29 August 2016 21:40:29 UTC+1, Adam (Cloud Platform Support) 
wrote:
>
> AMD64 is actually the standard used by both Intel and AMD, and is just 
> another name for 'x86-64' or 'x64' . 
> It's so named because AMD first developed the architecture which Intel 
> later adopted. Rest assured, we would not release an SDK for a 
> 'darwin_amd64' architecture if it didn't exist! 
>
> As for the reason it's crashing on your system, it's likely that you just 
> have an older 32-bit version of Go installed. As of Go 1.5, 'darwin-amd64' 
> is the only supported architecture . You can 
> confirm your version and architecture by typing 'go version' from the 
> command prompt.
>
> Otherwise, if you have a very old 2008 or prior Mac with a 1st gen Core 
> processor, your Mac is 32-bit only.
>
> On Sunday, August 28, 2016 at 11:45:39 AM UTC-4, Dmitry Matyukhin wrote:
>>
>> I tried to use Go Runtime for AppEngine for Mac. Since, there is a 64-bit 
>> version, I installed that one.
>>
>> However, whenever I tried to run anything, it was always crashing. For 
>> example, this happens when I did "goapp get google.golang.org/appengine"
>>
>> # net
>> fatal error: unexpected signal during runtime execution
>> [signal 0xb code=0x1 addr=0x1161be989d12 pc=0xf0eb]
>>
>> runtime stack:
>> runtime.throw(0x497380, 0x2a)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/panic.go:547
>>  
>> +0x90
>> runtime.sigpanic()
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/sigpanic_unix.go:12
>>  
>> +0x5a
>> runtime.unlock(0x988540)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/lock_sema.go:107
>>  
>> +0x14b
>> runtime.(*mheap).alloc_m(0x988540, 0x1, 0x21, 0xec2ff0)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:492
>>  
>> +0x314
>> runtime.(*mheap).alloc.func1()
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:502
>>  
>> +0x41
>> runtime.systemstack(0x7fff5fbfe348)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:307
>>  
>> +0xab
>> runtime.(*mheap).alloc(0x988540, 0x1, 0x121, 0xed8f)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:503
>>  
>> +0x63
>> runtime.(*mcentral).grow(0x98a680, 0x0)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:209
>>  
>> +0x93
>> runtime.(*mcentral).cacheSpan(0x98a680, 0xec2ff0)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:89
>>  
>> +0x47d
>> runtime.(*mcache).refill(0xafa000, 0x21, 0xec2ff0)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcache.go:119
>>  
>> +0xcc
>> runtime.mallocgc.func2()
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:642
>>  
>> +0x2b
>> runtime.systemstack(0x979d00)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:291
>>  
>> +0x79
>> runtime.mstart()
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/proc.go:1051
>>
>> goroutine 1 [running]:
>> runtime.systemstack_switch()
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:245
>>  
>> fp=0xc8241ed290 sp=0xc8241ed288
>> runtime.mallocgc(0x500, 0x0, 0x3, 0xc825f0c400)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:643
>>  
>> +0x869 fp=0xc8241ed368 sp=0xc8241ed290
>> runtime.rawmem(0x500, 0x200)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:809
>>  
>> +0x32 fp=0xc8241ed390 sp=0xc8241ed368
>> runtime.growslice(0x3b2760, 0xc825f0c400, 0x400, 0x400, 0x401, 0x0, 0x0, 
>> 0x0)
>> 
>> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/slice.go:95
>>  
>> +0x233 fp=0xc8241ed400 sp=0xc8241ed390
>> cmd/internal/obj.Symgrow(0xc8200b4000, 0xc8221d5b80, 0x401)
>> 
>> 

[google-appengine] GAE custom domain is displaying an old deleted SSL cert

[Col Wilson]

First of all I'm sorry I can;t give you my custom domain name, but when I 
go there it's displaying an expired and deleted 
(from appengine/settings/certificates) ssl key. It's not a local caching 
thing because I've tried it on several browser, laptops and networks. 

I'd really rather it displayed the new one which is associated with it.

Is there a fix for 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/725d75f6-5b2e-4111-9ba3-0442c34b379f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Multiple Cloud Endpoint API versions in the same Appengine Version.

[Francis Mwangi]

I have an android app in alpha stage that I am testing how I will be 
managing updates both in the server and client side..

 

First release to users. My android is using generated classes from this 
base cloud endpoint class and deployed to the default Appengine version.

@Api(name = *"myAPIName"*, version = *"v1*

*public class *AbstractEndpoint{

}

 

<*appengine-web-app **xmlns=**"http://appengine.google.com/ns/1.0"*>

   <*application*>myapp

   <*module*>default

   <*version*>1



 

2nd Release

I increment the Api version from V1 to V2 and use the generated classes in my 
for my 2nd app release. I deploy the backend to the same default appengine 
version 1.

 

@Api(name = *"myAPIName"*, version = *"v2*

*public class *AbstractEndpoint{

}

 

<*appengine-web-app **xmlns=**"http://appengine.google.com/ns/1.0"*>

   <*application*>myapp

   <*module*>default

   <*version*>1



 

The problem is that after the upgrade only the latter client apps using v2 can 
cases the Appengine endpoint v2 and those using V1 can no longer access the api 
v1. Either V2 overwrites V1 or  both v1 and V2 cannot run in the same Appengine 
instance or something else..

 

Have tried combing the documentation, and stack overflow for clues with no much 
success.

-- 
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/96ee2a8c-53e1-42ef-930e-988b643feda7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Matej Ramuta]

I think the issue has been fixed, I can see checkboxes again :)

On Monday, August 29, 2016 at 9:54:37 PM UTC+2, Adam (Cloud Platform 
Support) wrote:
>
> Yes, it's a known issue. For know the workaround as mentioned in the above 
> link is to manually go to 'Edit permissions' and add the User 'allUsers' 
> with Reader permission, or use the gsutil 
>  command 
> to set permissions.
>
> On Monday, August 29, 2016 at 1:52:10 PM UTC-4, Matej Ramuta wrote:
>>
>> Someone found a nice hack for this problem: 
>> https://code.google.com/p/google-cloud-sdk/issues/detail?id=1082 :)
>>
>> On Monday, August 29, 2016 at 3:06:15 PM UTC+2, Matej Ramuta wrote:
>>>
>>> Wonder if changing the html (adding in a checkbox) would help. The only 
>>> catch would be to know the name attribute of the input element :)
>>>
>>> On Aug 29, 2016 12:10, "Леонтьев Пётр" wrote:
>>>
 Tried to clear cache, refresh/change browser, create/change/delete 
 user, manage permissions - nothing seems to work.

 -- 
 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/XDEvsuem8Hw/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-appengi...@googlegroups.com .
 To post to this group, send email to google-a...@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/c6c06de1-d4be-4e1f-98cf-adab01b49892%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>

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