关于“Building Event-Driven Orchestration on Google Cloud”的评价

Swetnisha k. · 已于 9 months前审核

Kumar P. · 已于 9 months前审核

Was stuck on Step 9. 'delete-image' was not showing up.

Kumar P. · 已于 9 months前审核

Thomas L. · 已于 9 months前审核

Hamzah H. · 已于 9 months前审核

Salai Selva Kumari S. · 已于 9 months前审核

task10 有错

Dennis C. · 已于 9 months前审核

Cristina S. · 已于 9 months前审核

Dhibika B. · 已于 9 months前审核

Step #1: [builder] === Node.js - Runtime (google.nodejs.runtime@1.0.0) === Step #1: [builder] 2024/12/02 03:09:35 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/version.json Step #1: [builder] ***** CACHE MISS: "nodejs" Step #1: [builder] Installing Node.js v22.11.0. Step #1: [builder] 2024/12/02 03:09:36 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/nodejs-22.11.0.tar.gz Step #1: [builder] === Node.js - Npm (google.nodejs.npm@1.1.0) === Step #1: [builder] ***** CACHE MISS: "npm_modules" Step #1: [builder] Installing application dependencies. Step #1: [builder] -------------------------------------------------------------------------------- Step #1: [builder] Running "npm ci --quiet --no-fund --no-audit (NODE_ENV=production)" Step #1: [builder] npm error code EUSAGE Step #1: [builder] npm error Step #1: [builder] npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. Step #1: [builder] npm error Step #1: [builder] npm error Missing: @google-cloud/firestore@6.8.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/storage@6.12.0 from lock file Step #1: [builder] npm error Missing: @google/events@5.4.0 from lock file Step #1: [builder] npm error Missing: cloudevents@6.0.3 from lock file Step #1: [builder] npm error Missing: express@4.21.1 from lock file Step #1: [builder] npm error Missing: fast-deep-equal@3.1.3 from lock file Step #1: [builder] npm error Missing: functional-red-black-tree@1.0.1 from lock file Step #1: [builder] npm error Missing: google-gax@3.6.1 from lock file Step #1: [builder] npm error Missing: protobufjs@7.4.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/paginator@3.0.7 from lock file Step #1: [builder] npm error Missing: @google-cloud/projectify@3.0.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/promisify@3.0.1 from lock file Step #1: [builder] npm error Missing: abort-controller@3.0.0 from lock file Step #1: [builder] npm error Missing: async-retry@1.3.3 from lock file

Dennis C. · 已于 9 months前审核

Jan U. · 已于 9 months前审核

There is an error in extract-image-metadata: TypeError: Cannot read properties of undefined (reading 'text') at exports.extract_image_metadata (/workspace/index.js:39:50) at /layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src/function_wrappers.js:100:29 at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

Volodymyr K. · 已于 9 months前审核

尚也 佐. · 已于 9 months前审核

Task 10. Trigger a service to delete image files and metadata has a error during creation eventarc for delete image. I had to create it using: gcloud eventarc triggers create image-delete-trigger... The error was: "Cannot access API run.googleapis.com in project qwiklabs-gcp-04-e275cec0c415"

Szymon G. · 已于 9 months前审核

Volodymyr K. · 已于 9 months前审核

Pavithra H. · 已于 9 months前审核

Pavithra H. · 已于 9 months前审核

Wicaksono A. · 已于 9 months前审核

Wicaksono A. · 已于 9 months前审核

Enough time is not given to complete the lab. It has so many services, more time is required to review everything.

Himanshi R. · 已于 9 months前审核

Andrew-john A. · 已于 9 months前审核

problems with api run

Peter T. · 已于 9 months前审核

The lab is not showing option delete-image

Ayushi K. · 已于 9 months前审核

Mohit B. · 已于 9 months前审核

could not create the delete trigger :-(

Thomas H. · 已于 9 months前审核