透過 Google Cloud 監控應用程式 Reviews

Gitimaya P. · Reviewed over 4 years ago

Fabian Oswaldo V. · Reviewed over 4 years ago

Pandya, D. · Reviewed over 4 years ago

Dawud R. · Reviewed over 4 years ago

Rogerio D. · Reviewed over 4 years ago

Madhan K. · Reviewed over 4 years ago

the app.yaml file needs to be updated to runtime: python39 as per the changes here https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates - otherwise the app keeps failing with 502 errors

Antonio O. · Reviewed over 4 years ago

Wildson l. · Reviewed over 4 years ago

amazing

David A. · Reviewed over 4 years ago

After app deploy command, the profiler wasn't starting because of compatibility error with protobuf. I had to add to requirements file the following line: protobuf==3.20.1 It took me some time to figure it out. After the fix, the profiler page had no data.

Andrei S. · Reviewed over 4 years ago

Satrio H. · Reviewed over 4 years ago

Logs request is not working correctly

Aaron D. · Reviewed over 4 years ago

Task 3 is not working at all

Jonathan R. · Reviewed over 4 years ago

David S. · Reviewed over 4 years ago

Task 3 is not working at all

Jonathan R. · Reviewed over 4 years ago

WESLEY F. · Reviewed over 4 years ago

I need technical assistance, this lab is broken

Manjunath N. · Reviewed over 4 years ago

The lab did not worked

Vincent T. · Reviewed over 4 years ago

lab broke near the start. import statement for profiler threw an error and would never work. after that, the rest of the lab was pretty boring

WILLIAM^Bill W. · Reviewed over 4 years ago

can't cun app engine app -- Bad Gateway Error. https://github.com/protocolbuffers/protobuf/issues/10051

Hiroyuki K. · Reviewed over 4 years ago

Alex E. · Reviewed over 4 years ago

I need technical assistance, this lab is broken

Manjunath N. · Reviewed over 4 years ago

Manjunath H. · Reviewed over 4 years ago

Issue with the Lab, Not able to complete...

Sudhakar K. · Reviewed over 4 years ago

Can't finish Task 2, after deploying app there is an error: 502 Bad Gateway

Kamil H. · Reviewed over 4 years ago