Firebase-tools: penyiapan: kode status INVALID_ARGUMENT web 400

Dibuat pada 15 Nov 2018  ·  41Komentar  ·  Sumber: firebase/firebase-tools

Info versi: 6.1.0
Informasi Platform: OSX

Langkah-langkah untuk mereproduksi

cd dir
firebase init (khusus hosting)
pilih proyek yang ada
firebase serve --only hosting --debug

Ini menjalankan situs secara lokal.

[2018-11-15T17:12:15.331Z] <<< HTTP RESPON 400 bervariasi=X-Origin, Referer, Origin, Accept-Encoding, content-type=application/json; charset=UTF-8, tanggal=Kamis, 15 Nov 2018 17:12:15 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMAASAL, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", rentang-terima=tidak ada, koneksi=dekat
[2018-11-15T17:12:15.331Z] <<< HTTP RESPONSE BODY code=400, message=Permintaan berisi argumen yang tidak valid., status=INVALID_ARGUMENT

Kesalahan: Kesalahan HTTP: 400, Permintaan berisi argumen yang tidak valid.
[2018-11-15T17:12:15.532Z] Konteks Kesalahan: {
"tubuh": {
"kesalahan": {
"kode": 400,
"message": "Permintaan berisi argumen yang tidak valid.",
"status": "INVALID_ARGUMENT"
}
},
"tanggapan": {
"Kode status": 400,
"tubuh": {
"kesalahan": {
"kode": 400,
"message": "Permintaan berisi argumen yang tidak valid.",
"status": "INVALID_ARGUMENT"
}
},
"tajuk": {
"bervariasi": "X-Origin, Referer, Origin, Accept-Encoding",
"tipe konten": "aplikasi/json; charset=UTF-8",
"tanggal": "Kamis, 15 Nov 2018 17:12:15 GMT",
"server": "ESF",
"kontrol-cache": "pribadi",
"x-xss-protection": "1; mode=block",
"x-frame-options": "ASAL SAMA",
"x-content-type-options": "nosniff",
"alt-svc": "quic=\":443\"; ma=2592000; v=\"44,43,39,35\"",
"rentang-terima": "tidak ada",
"koneksi": "tutup"
},
"meminta": {
"uri": {
"protokol": "https:",
"garis miring": benar,
"auth": nol,
"host": "mobilesdk-pa.googleapis.com",
"pelabuhan": 443,
"nama host": "mobilesdk-pa.googleapis.com",
"hash": nol,
"pencarian": nol,
"permintaan": nol,
"pathname": "/v1/projects/540833485883/clients/_:getWebAppConfig",
"path": "/v1/projects/540833485883/clients/_:getWebAppConfig",
"href": " https://mobilesdk-pa.googleapis.com/v1/projects/540833485883/clients/_ :getWebAppConfig"
},
"metode": "DAPATKAN"
}
}
}

p1

Komentar yang paling membantu

Terima kasih semua telah membawa ini menjadi perhatian kami. Kami secara aktif menyelidiki masalah ini sekarang.

(Nomor pelacakan internal: 119615185)

Semua 41 komentar

Sama disini:

Info versi: 6.1.0 (juga diuji dengan 6.0.0, 5.0.0)
Informasi Platform: OSX 10.14 macOS Mojave 18A391

$ firebase serve --only hosting,functions --debug

Diuji dengan proyek yang ada dan yang baru. Kesalahan yang sama.

Error: HTTP Error: 400, Request contains an invalid argument.
[2018-11-15T17:40:46.943Z] Error Context: {
  "body": {
    "error": {
      "code": 400,
      "message": "Request contains an invalid argument.",
      "status": "INVALID_ARGUMENT"
    }
  },
  "response": {
    "statusCode": 400,
    "body": {
      "error": {
        "code": 400,
        "message": "Request contains an invalid argument.",
        "status": "INVALID_ARGUMENT"
      }
    },
    "headers": {
      "vary": "X-Origin, Referer, Origin,Accept-Encoding",
      "content-type": "application/json; charset=UTF-8",
      "date": "Thu, 15 Nov 2018 17:40:46 GMT",
      "server": "ESF",
      "cache-control": "private",
      "x-xss-protection": "1; mode=block",
      "x-frame-options": "SAMEORIGIN",
      "x-content-type-options": "nosniff",
      "alt-svc": "quic=\":443\"; ma=2592000; v=\"44,43,39,35\"",
      "accept-ranges": "none",
      "connection": "close"
    },
    "request": {
      "uri": {
        "protocol": "https:",
        "slashes": true,
        "auth": null,
        "host": "mobilesdk-pa.googleapis.com",
        "port": 443,
        "hostname": "mobilesdk-pa.googleapis.com",
        "hash": null,
        "search": null,
        "query": null,
        "pathname": "/v1/projects/128559963708/clients/_:getWebAppConfig",
        "path": "/v1/projects/128559963708/clients/_:getWebAppConfig",
        "href": "https://mobilesdk-pa.googleapis.com/v1/projects/128559963708/clients/_:getWebAppConfig"
      },
      "method": "GET"
    }
  }
}

Saya mengalami masalah yang sama persis. Saya baru saja menguji proyek yang sama tanpa perubahan apa pun di komputer lain, dan bahkan proyek lain yang berjalan dengan baik sekitar 3 bulan, dan masalahnya sama. Menyebarkannya normal, tetapi localhost (_firebase serve --only functions,hosting --debug_) berhenti bekerja dengan kesalahan annoing ini...
Saya tidak berpikir masalahnya adalah aplikasinya (milik saya atau milik Anda).
Semuanya bekerja dengan baik sekitar 2 jam yang lalu!

+1 untuk saya

masalah yang sama. kemarin semuanya bekerja dengan baik

[2018-11-15T17:22:20.885Z] >>> HTTP REQUEST GET https://mobilesdk-pa.googleapis.com/v1/projects/xxx/clients/_:getWebAppConfig

[2018-11-15T17:22:21.179Z] <<< HTTP RESPONSE BODY code=400, message=Request contains an invalid argument., status=INVALID_ARGUMENT

+1 untuk saya, dan untuk seorang teman juga, berhenti bekerja pagi ini ketika berfungsi dengan baik kemarin. Saya tidak melihat apa-apa tentang itu di https://status.firebase.google.com , apakah ada orang dari Firebase yang bisa berkomentar?

+1 untuk saya - semuanya berhenti bekerja tiba-tiba. Mencoba memutakhirkan ke 6.1.0 dari 6.0.1 dan sekarang firebase serve juga memberi saya pesan ini:

 functions: Preparing to emulate functions.
⚠  Setup required, please run: firebase setup:emulators:firestore

Saya berhasil menjalankan perintah itu dan ketika saya mencoba menjalankan firebase serve lagi saya mendapatkan:

i  functions: Preparing to emulate functions.
✔  firestore: started on http://localhost:8080
⚠  firestore: Error: Invalid or corrupt jarfile /home/alex/.cache/firebase/emulators/cloud-firestore-emulator-v1.2.1.jar

Mencari perintah yang baru saja saya jalankan, saya menemukan halaman ini: https://firebase.google.com/docs/firestore/security/test-rules-emulator

Saya mencoba menjalankan firebase --open-sesame emulators berpikir itu adalah masalah dengan 6.1.0 dan mendapatkan kesalahan ini:

Error: Did not recognize preview feature

+1 Masalah yang sama, dimulai pagi ini

+1. Dapat memverifikasi masalah yang terjadi saat menggunakan firebase serve tanpa params dalam proyek yang ada, dengan firebase-tools versi v6.0.1 dan v6.1.0. Selain itu, perintah firebase serve keluar tanpa menutup proses simpul dengan benar yang membuka port penyajian, yang memerlukan penghentian manual proses tersebut.

Hanya ingin menambahkan bahwa saya juga mengalami masalah ini. firebase serve berfungsi dengan baik kemarin. Ini ada di firebase 6.0.1 dan 6.1.0

Saya memiliki masalah yang sama persis.

Sama!

sama. Saya tidak bisa menyebarkan sekarang

Gerakan mengungkap kekerasan seksual demi menghapuskannya:

image

Terima kasih semua telah membawa ini menjadi perhatian kami. Kami secara aktif menyelidiki masalah ini sekarang.

(Nomor pelacakan internal: 119615185)

@Neilpoulin Anda tidak dapat menerapkan? Versi CLI apa yang Anda gunakan dan kesalahan apa yang Anda dapatkan?

Maaf- ini tidak terkait langsung dengan perintah penyebaran basis api. bangunan saya
proses termasuk langkah yang mengambil konfigurasi ini, dan karena gagal saya
tidak dapat menyebarkan.
Pada Thu, Nov 15, 2018 at 12:10 Michael Bleigh [email protected]
menulis:

@Neilpoulin https://github.com/Neilpoulin Anda tidak dapat menerapkan? Apa
versi CLI yang Anda gunakan dan kesalahan apa yang Anda dapatkan?


Anda menerima ini karena Anda disebutkan.

Balas email ini secara langsung, lihat di GitHub
https://github.com/firebase/firebase-tools/issues/1015#issuecomment-439155616 ,
atau matikan utasnya
https://github.com/notifications/unsubscribe-auth/AAw-atNnP6wSmeHQke6z4EKIsx1D6r7Yks5uvbw_gaJpZM4Ygu-y
.

Jika ini membantu seseorang, Anda bisa menjalankan fungsi Anda dengan memaksa port sementara itu. Ini tidak akan membantu menyebarkan atau hosting. Contoh:
sudo firebase serve --only functions --port=9000

Masalah yang sama ... pengembangan kami terhenti karena masalah ini. Kami memiliki aplikasi sudut yang dihosting dengan fungsi firebase yang menyajikan konten. Saya kira ini ada hubungannya dengan layanan firebase tetapi dasbor statusnya menunjukkan semuanya hijau. Semuanya bekerja dengan baik sampai kemarin.

Ini berfungsi sekarang, tetapi dengan peringatan ...

⚠  database: WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/Users/rodrigodutra/.cache/firebase/emulators/firebase-database-emulator-v3.5.0.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
⚠  database:
...

Saya tidak lagi mendapatkan kesalahan 400 argumen ilegal tetapi yang lain di tempatnya sekarang dan masih tidak berjalan:

2018-11-15T20:01:14.098Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Thu, 15 Nov 2018 20:01:22 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
[2018-11-15T20:01:14.098Z] Starting @google-cloud/functions-emulator
[2018-11-15T20:01:14.115Z] Parsing function triggers
Warning: You're using Node.js v10.13.0 but Google Cloud Functions only supports v6.11.5.
[2018-11-15T20:01:14.238Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Thu, 15 Nov 2018 20:01:22 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
i  hosting: Serving hosting files from: public
✔  hosting: Local server: http://localhost:5000
⚠  database: WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/home/qkay/.cache/firebase/emulators/firebase-database-emulator-v3.5.0.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
⚠  database: 

error: SUPERVISOR error Error: listen EADDRINUSE 127.0.0.1:5001
    at Server.setupListenHandle [as _listen2] (net.js:1286:14)
    at listenInCluster (net.js:1334:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1460:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:62:10)
error: supervisorPort (5001) is already in use
error: restPort (5002) is already in use
12:01:15.254 [NamespaceSystem-akka.actor.default-dispatcher-3] INFO akka.event.slf4j.Slf4jLogger - Slf4jLogger started

12:01:15.408 [main] INFO com.firebase.server.forge.App$ - Listening on port 9000

12:01:15.438 [main] ERROR com.firebase.server.forge.App$ - Error initializing Netty Listener
java.net.BindException: Address already in use
    at java.base/sun.nio.ch.Net.bind0(Native Method)
    at java.base/sun.nio.ch.Net.bind(Net.java:461)
    at java.base/sun.nio.ch.Net.bind(Net.java:453)
    at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
    at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:128)
    at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:500)
    at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1226)
    at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:495)
    at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:480)
    at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973)
    at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:209)
    at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:355)
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:399)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:464)
    at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
    at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
    at java.base/java.lang.Thread.run(Thread.java:834)

12:01:15.440 [Thread-1] INFO com.firebase.server.forge.App$ - Attempting graceful shutdown.

12:01:15.444 [NamespaceSystem-akka.actor.default-dispatcher-4] INFO akka.actor.CoordinatedShutdown - Starting coordinated shutdown from JVM shutdown hook

12:01:15.448 [Thread-1] INFO com.firebase.server.forge.App$ - Graceful shutdown complete.


Error: database: emulator has exited with code: 1

Saya tidak lagi mendapatkan kesalahan 400 argumen ilegal tetapi yang lain di tempatnya sekarang dan masih tidak berjalan:

2018-11-15T20:01:14.098Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Thu, 15 Nov 2018 20:01:22 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
[2018-11-15T20:01:14.098Z] Starting @google-cloud/functions-emulator
[2018-11-15T20:01:14.115Z] Parsing function triggers
Warning: You're using Node.js v10.13.0 but Google Cloud Functions only supports v6.11.5.
[2018-11-15T20:01:14.238Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Thu, 15 Nov 2018 20:01:22 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
i  hosting: Serving hosting files from: public
✔  hosting: Local server: http://localhost:5000
⚠  database: WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/home/qkay/.cache/firebase/emulators/firebase-database-emulator-v3.5.0.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
⚠  database: 

error: SUPERVISOR error Error: listen EADDRINUSE 127.0.0.1:5001
    at Server.setupListenHandle [as _listen2] (net.js:1286:14)
    at listenInCluster (net.js:1334:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1460:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:62:10)
error: supervisorPort (5001) is already in use
error: restPort (5002) is already in use
12:01:15.254 [NamespaceSystem-akka.actor.default-dispatcher-3] INFO akka.event.slf4j.Slf4jLogger - Slf4jLogger started

12:01:15.408 [main] INFO com.firebase.server.forge.App$ - Listening on port 9000

12:01:15.438 [main] ERROR com.firebase.server.forge.App$ - Error initializing Netty Listener
java.net.BindException: Address already in use
  at java.base/sun.nio.ch.Net.bind0(Native Method)
  at java.base/sun.nio.ch.Net.bind(Net.java:461)
  at java.base/sun.nio.ch.Net.bind(Net.java:453)
  at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
  at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:128)
  at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:500)
  at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1226)
  at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:495)
  at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:480)
  at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973)
  at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:209)
  at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:355)
  at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:399)
  at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:464)
  at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
  at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
  at java.base/java.lang.Thread.run(Thread.java:834)

12:01:15.440 [Thread-1] INFO com.firebase.server.forge.App$ - Attempting graceful shutdown.

12:01:15.444 [NamespaceSystem-akka.actor.default-dispatcher-4] INFO akka.actor.CoordinatedShutdown - Starting coordinated shutdown from JVM shutdown hook

12:01:15.448 [Thread-1] INFO com.firebase.server.forge.App$ - Graceful shutdown complete.


Error: database: emulator has exited with code: 1

Nyalakan ulang Mac Anda...

Coba firebase serve --only hosting atau firebase serve --only functions untuk mengatasi masalah ini. Mencari perbaikan untuk itu sekarang.

Saya juga punya masalah; baru saja reboot komputer saya dan berfungsi lagi.

@Neilpoulin Anda tidak dapat menerapkan? Versi CLI apa yang Anda gunakan dan kesalahan apa yang Anda dapatkan?

@mbleigh Ingin memberi Anda lebih banyak detail sekarang setelah saya kembali ke komputer saya:

Secara khusus, saya menjalankan firebase-tools di node.js. Perintah yang gagal adalah ini:

Ketika saya pertama kali menemukan kesalahan ini, firbase-tools berada di versi 6.0.1 . Saya kemudian memutakhirkannya ke 6.1.0 tetapi kesalahannya sama.

const fbcli = require("firebase-tools");
const opts = {"project": "stage"}; //this is an active alias for my firebase setup
return fbcli.setup
    .web(opts)
    .then(firebaseConfig => { 
        // some config setup stuff for webpack
    }.catch(error => {
        //This gets called rigt away, see error object below
        console.error(error);
    })

di mana kesalahan yang tertangkap terlihat seperti:

{
  "name": "FirebaseError",
  "message": "HTTP Error: 400, Request contains an invalid argument.",
  "children": [],
  "status": 500,
  "exit": 1,
  "stack": "Error\n    at new FirebaseError (/Users/myrepo/node_modules/firebase-tools/src/error.js:11:16)\n    at module.exports (/Users/myrepo/node_modules/firebase-tools/src/responseToError.js:46:10)\n    at Request._callback (/Users/myrepo/node_modules/firebase-tools/src/api.js:50:25)\n    at Request.self.callback (/Users/myrepo/node_modules/request/request.js:185:22)\n    at emitTwo (events.js:126:13)\n    at Request.emit (events.js:214:7)\n    at Request.<anonymous> (/Users/myrepo/node_modules/request/request.js:1161:10)\n    at emitOne (events.js:116:13)\n    at Request.emit (events.js:211:7)\n    at IncomingMessage.<anonymous> (/Users/myrepo/node_modules/request/request.js:1083:12)",
  "context": {
    "body": {
      "error": {
        "code": 400,
        "message": "Request contains an invalid argument.",
        "status": "INVALID_ARGUMENT"
      }
    },
    "response": {
      "statusCode": 400,
      "body": {
        "error": {
          "code": 400,
          "message": "Request contains an invalid argument.",
          "status": "INVALID_ARGUMENT"
        }
      },
      "headers": {
        "vary": "X-Origin, Referer, Origin,Accept-Encoding",
        "content-type": "application/json; charset=UTF-8",
        "date": "Thu, 15 Nov 2018 18:33:41 GMT",
        "server": "ESF",
        "cache-control": "private",
        "x-xss-protection": "1; mode=block",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "alt-svc": "quic=\":443\"; ma=2592000; v=\"44,43,39,35\"",
        "accept-ranges": "none",
        "connection": "close"
      },
      "request": {
        "uri": {
          "protocol": "https:",
          "slashes": true,
          "auth": null,
          "host": "mobilesdk-pa.googleapis.com",
          "port": 443,
          "hostname": "mobilesdk-pa.googleapis.com",
          "hash": null,
          "search": null,
          "query": null,
          "pathname": "/v1/projects/465836249868/clients/_:getWebAppConfig",
          "path": "/v1/projects/465836249868/clients/_:getWebAppConfig",
          "href": "https://mobilesdk-pa.googleapis.com/v1/projects/465836249868/clients/_:getWebAppConfig"
        },
        "method": "GET"
      }
    }
  }
}

EDIT pada 13:16 MT, saya tidak lagi melihat kesalahan ini

Kami telah mengembalikan build backend yang menyebabkan masalah ini. Bisakah Anda mencobanya sekarang dan melihat apakah masih rusak?

Bekerja untuk saya

+1 bekerja sekarang. Terima kasih

+1 dikonfirmasi bekerja untuk saya juga.

+1 kembali dalam bisnis

@ryanpbrewster ya itu berfungsi lagi. Terima kasih! kalian harus memiliki semacam pengujian e2e untuk itu

ps: ini bekerja tanpa reboot, tetapi saya telah menemukan beberapa proses simpul yang menggantung dan mematikannya sebelum firebase serve

bahkan setelah reboot, saya masih menjalankan proses dari upaya penerapan sebelumnya. Saya baru saja pergi ke atas dan membunuhnya secara manual dan sekarang alat firebase berfungsi dengan baik untuk saya.

+1 siap! Tks banyak.

Terimakasih untuk kesabarannya. Kesalahan argumen yang tidak valid telah diselesaikan.

mencoba memecahkan masalah selama 5 jam sekarang, di 'firebase deploy'.

fungsinya adalah:

exports.makeUppercase = functions.database.ref('/userfollowers/{pushId}/followers')
    .onWrite((change, context) => {
      // Only edit data when it is first created.
      if (change.before.exists()) {
        return null;
      }
      // Exit when the data is deleted.
      if (!change.after.exists()) {
        return null;
      }
      // Grab the current value of what was written to the Realtime Database.
      const original = change.after.val();
      console.log('Uppercasing', context.params.pushId, original);
      const uppercase = original.toUpperCase();
      // You must return a Promise when performing asynchronous tasks inside a Functions such as
      // writing to the Firebase Realtime Database.
      // Setting an "uppercase" sibling in the Realtime Database returns a Promise.
      return change.after.ref.parent.child('uppercase').set(uppercase);
    });

yang langsung dari dokumentasi.

terminal menunjukkan:

⚠  functions: failed to create function makeUppercase
HTTP Error: 400, The request has errors

log fungsi cloud menunjukkan:
{"@type":"type.googleapis.com/google.cloud.audit.AuditLog","status":{"code":3,"message":"INVALID_ARGUMENT"},"authenticationInfo":{"principalEmail":"[email protected]"},"requestMetadata":{"callerIp":"86.120.235.246","callerSuppliedUserAgent":"FirebaseCLI/3.19.0,gzip(gfe),gzip(gfe)","requestAttributes":{"time":"2019-05-14T08:34:18.563Z","auth":{}},"destinationAttributes":{}},"serviceName":"cloudfunctions.googleapis.com","methodName":"google.cloud.functions.v1.CloudFunctionsService.CreateFunction","authorizationInfo":[{"resource":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}},{"permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}}],"resourceName":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","request":{"location":"projects/parkour-9136c/locations/us-central1","@type":"type.googleapis.com/google.cloud.functions.v1.CreateFunctionRequest","function":{"labels":{"deployment-tool":"cli-firebase"},"entryPoint":"makeUppercase","eventTrigger":{"eventType":"providers/google.firebase.database/eventTypes/ref.write","resource":"projects/_/instances/parkour-9136c/refs/userfollowers/{pushId}/followers","service":"firebaseio.com"},"sourceUploadUrl":"https://storage.googleapis.com/gcf-upload-us-central1-f5adb7fe-7321-4f3c-8fe0-2b2307d26138/5b099ea8-161b-44a7-a3bd-18ce75c64859.zip?GoogleAccessId=service-807137615499@gcf-admin-robot.iam.gserviceaccount.com&Expires=1557824657&Signature=PJKzJsZtHWO1kIkmrSojpdgvb0jRzV91eNC9rZc4j%2FMcoHjILGm36FKCt6qQ2fxeAUu1%2FbrxpagdI7fHmUUUrDdTmnTNISr7FiN61sifUI%2B%2FGnUwo8SguzvrA7kADFqu8nD05FAo7BvG7biUrHmLgISlwo5dTKqcTSmExnaICA1tHYxjz%2Fk0RbmdGkcQ5HdeCKBnW0R7wQPsxswQyvR4cAU4WD2m3PPM9lncVr7pB%2Fh77FboGLi3sq%2FGHyEwUtjfUmyN9d%2FYUpKs48TMsGPknAGIvaFFUWQR23YCDUcrPipq1nW2W1JUdf5nGylYmVEeyF3jLrm%2BsOIcXiZ6LCRhpg%3D%3D","name":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase"}}}

apa solusinya?
Terima kasih

@nicoara tolong buka edisi baru dengan informasi yang diperlukan. Terima kasih.

mencoba memecahkan masalah selama 5 jam sekarang, di 'firebase deploy'.

fungsinya adalah:

exports.makeUppercase = functions.database.ref('/userfollowers/{pushId}/followers')
    .onWrite((change, context) => {
      // Only edit data when it is first created.
      if (change.before.exists()) {
        return null;
      }
      // Exit when the data is deleted.
      if (!change.after.exists()) {
        return null;
      }
      // Grab the current value of what was written to the Realtime Database.
      const original = change.after.val();
      console.log('Uppercasing', context.params.pushId, original);
      const uppercase = original.toUpperCase();
      // You must return a Promise when performing asynchronous tasks inside a Functions such as
      // writing to the Firebase Realtime Database.
      // Setting an "uppercase" sibling in the Realtime Database returns a Promise.
      return change.after.ref.parent.child('uppercase').set(uppercase);
    });

yang langsung dari dokumentasi.

terminal menunjukkan:

⚠  functions: failed to create function makeUppercase
HTTP Error: 400, The request has errors

log fungsi cloud menunjukkan:
{"@type":"type.googleapis.com/google.cloud.audit.AuditLog","status":{"code":3,"message":"INVALID_ARGUMENT"},"authenticationInfo":{"principalEmail":"[email protected]"},"requestMetadata":{"callerIp":"86.120.235.246","callerSuppliedUserAgent":"FirebaseCLI/3.19.0,gzip(gfe),gzip(gfe)","requestAttributes":{"time":"2019-05-14T08:34:18.563Z","auth":{}},"destinationAttributes":{}},"serviceName":"cloudfunctions.googleapis.com","methodName":"google.cloud.functions.v1.CloudFunctionsService.CreateFunction","authorizationInfo":[{"resource":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}},{"permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}}],"resourceName":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","request":{"location":"projects/parkour-9136c/locations/us-central1","@type":"type.googleapis.com/google.cloud.functions.v1.CreateFunctionRequest","function":{"labels":{"deployment-tool":"cli-firebase"},"entryPoint":"makeUppercase","eventTrigger":{"eventType":"providers/google.firebase.database/eventTypes/ref.write","resource":"projects/_/instances/parkour-9136c/refs/userfollowers/{pushId}/followers","service":"firebaseio.com"},"sourceUploadUrl":"https://storage.googleapis.com/gcf-upload-us-central1-f5adb7fe-7321-4f3c-8fe0-2b2307d26138/5b099ea8-161b-44a7-a3bd-18ce75c64859.zip?GoogleAccessId=service-807137615499@gcf-admin-robot.iam.gserviceaccount.com&Expires=1557824657&Signature=PJKzJsZtHWO1kIkmrSojpdgvb0jRzV91eNC9rZc4j%2FMcoHjILGm36FKCt6qQ2fxeAUu1%2FbrxpagdI7fHmUUUrDdTmnTNISr7FiN61sifUI%2B%2FGnUwo8SguzvrA7kADFqu8nD05FAo7BvG7biUrHmLgISlwo5dTKqcTSmExnaICA1tHYxjz%2Fk0RbmdGkcQ5HdeCKBnW0R7wQPsxswQyvR4cAU4WD2m3PPM9lncVr7pB%2Fh77FboGLi3sq%2FGHyEwUtjfUmyN9d%2FYUpKs48TMsGPknAGIvaFFUWQR23YCDUcrPipq1nW2W1JUdf5nGylYmVEeyF3jLrm%2BsOIcXiZ6LCRhpg%3D%3D","name":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase"}}}

apa solusinya?
Terima kasih

mencoba memecahkan masalah selama 5 jam sekarang, di 'firebase deploy'.

fungsinya adalah:

exports.makeUppercase = functions.database.ref('/userfollowers/{pushId}/followers')
    .onWrite((change, context) => {
      // Only edit data when it is first created.
      if (change.before.exists()) {
        return null;
      }
      // Exit when the data is deleted.
      if (!change.after.exists()) {
        return null;
      }
      // Grab the current value of what was written to the Realtime Database.
      const original = change.after.val();
      console.log('Uppercasing', context.params.pushId, original);
      const uppercase = original.toUpperCase();
      // You must return a Promise when performing asynchronous tasks inside a Functions such as
      // writing to the Firebase Realtime Database.
      // Setting an "uppercase" sibling in the Realtime Database returns a Promise.
      return change.after.ref.parent.child('uppercase').set(uppercase);
    });

yang langsung dari dokumentasi.

terminal menunjukkan:

⚠  functions: failed to create function makeUppercase
HTTP Error: 400, The request has errors

log fungsi cloud menunjukkan:
{"@type":"type.googleapis.com/google.cloud.audit.AuditLog","status":{"code":3,"message":"INVALID_ARGUMENT"},"authenticationInfo":{"principalEmail":"[email protected]"},"requestMetadata":{"callerIp":"86.120.235.246","callerSuppliedUserAgent":"FirebaseCLI/3.19.0,gzip(gfe),gzip(gfe)","requestAttributes":{"time":"2019-05-14T08:34:18.563Z","auth":{}},"destinationAttributes":{}},"serviceName":"cloudfunctions.googleapis.com","methodName":"google.cloud.functions.v1.CloudFunctionsService.CreateFunction","authorizationInfo":[{"resource":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}},{"permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}}],"resourceName":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase","request":{"location":"projects/parkour-9136c/locations/us-central1","@type":"type.googleapis.com/google.cloud.functions.v1.CreateFunctionRequest","function":{"labels":{"deployment-tool":"cli-firebase"},"entryPoint":"makeUppercase","eventTrigger":{"eventType":"providers/google.firebase.database/eventTypes/ref.write","resource":"projects/_/instances/parkour-9136c/refs/userfollowers/{pushId}/followers","service":"firebaseio.com"},"sourceUploadUrl":"https://storage.googleapis.com/gcf-upload-us-central1-f5adb7fe-7321-4f3c-8fe0-2b2307d26138/5b099ea8-161b-44a7-a3bd-18ce75c64859.zip?GoogleAccessId=service-807137615499@gcf-admin-robot.iam.gserviceaccount.com&Expires=1557824657&Signature=PJKzJsZtHWO1kIkmrSojpdgvb0jRzV91eNC9rZc4j%2FMcoHjILGm36FKCt6qQ2fxeAUu1%2FbrxpagdI7fHmUUUrDdTmnTNISr7FiN61sifUI%2B%2FGnUwo8SguzvrA7kADFqu8nD05FAo7BvG7biUrHmLgISlwo5dTKqcTSmExnaICA1tHYxjz%2Fk0RbmdGkcQ5HdeCKBnW0R7wQPsxswQyvR4cAU4WD2m3PPM9lncVr7pB%2Fh77FboGLi3sq%2FGHyEwUtjfUmyN9d%2FYUpKs48TMsGPknAGIvaFFUWQR23YCDUcrPipq1nW2W1JUdf5nGylYmVEeyF3jLrm%2BsOIcXiZ6LCRhpg%3D%3D","name":"projects/parkour-9136c/locations/us-central1/functions/makeUppercase"}}}

apa solusinya?
Terima kasih

coba tambahkan dokumen di akhir jalur ref db. misalnya /userfollowers/{pushId}/followers/{follower}

@bkendall saya memulai utas baru: https://github.com/firebase/firebase-tools/issues/1317

Saya menjalankan 'firebase deploy --debug' dan menemukan pesan baru.

[2019-05-20T14:43:23.863Z] <<< HTTP RESPONSE 400 vary=X-Origin, Referer, Origin,Accept-Encoding, content-type=application/json; charset=UTF-8, date=Mon, 20 May 2019 14:43:23 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="46,44,43,39", accept-ranges=none, connection=close
[2019-05-20T14:43:23.863Z] <<< HTTP RESPONSE BODY code=400, message=The request has errors, status=INVALID_ARGUMENT, details=[@type=type.googleapis.com/google.rpc.BadRequest, fieldViolations=[field=runtime, description=Runtime field cannot be empty.]]
⚠  functions: failed to create function makeUppercase
HTTP Error: 400, The request has errors

@soclbz perubahan tidak membuat perbedaan.

Terima kasih

Mendapatkan kesalahan _"Runtime field tidak boleh kosong"_ yang sama:

[06-06T18:51:31.127Z] <<< HTTP RESPON 400 bervariasi=X-Origin, Referer, Origin,Accept-Encoding, content-type=application/json; charset=UTF-8, tanggal=Kamis, 06 Jun 2019 18:51:30 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMAORIGIN, x-content- Tipe-
pilihan=nosniff, alt-svc=quic=":443"; ma=2592000; v="46,44,43,39", rentang-terima=tidak ada, koneksi=dekat
[06-06T18:51:31.128Z] <<< HTTP RESPONSE BODY code=400, message=Permintaan memiliki kesalahan, status=INVALID_ARGUMENT, details=[@type=type.googleapis.com/google.rpc.BadRequest , fieldViolations=[field=runtime, description=bidang Runtime tidak boleh kosong.]]

Ini juga terjadi untuk proyek yang baru dibuat menggunakan npx firebase init ketika mencoba menerapkan fungsi contoh hello world.

@stpch apakah Anda menggunakan CLI versi lama? Silakan lihat di #1317

@stpch apakah Anda menggunakan CLI versi lama? Silakan lihat di #1317

Saya menggunakan versi terbaru:

Sayangnya, ada firebase-tools versi lama yang diinstal melalui yarn yang lebih diutamakan daripada npx . Ini berfungsi sekarang dengan versi terbaru.

Apakah halaman ini membantu?
0 / 5 - 0 peringkat