Except ref.delete() doesn't allow the node process to exit. Ever.
I've had to hack around it with a process.exit() callback for a while now. But now I'm 11 messages into a firebase-functions support issue because using the firebase module in an isomorphic way (functions & cli) causes delays of 20 -> 40 seconds if you return early (even on a hot start). I'd love to narrow down the cause, and to see if this crazy hangup issue that Version 3.4.1 says was fixed is the culprit.
And, just to check, I removed the nice function wrappers and ref passing, and firebase still wouldn't exit on a firebase.app().delete(). nor does .goOffline()
Environment:
Issue:
calling
.delete()
not sufficient for node process to disconnect.Steps to reproduce:
What I've thought all along was a pretty standard use for a small cli module:
Except ref.delete() doesn't allow the node process to exit. Ever.
I've had to hack around it with a
process.exit()
callback for a while now. But now I'm 11 messages into afirebase-functions
support issue because using thefirebase
module in an isomorphic way (functions & cli) causes delays of 20 -> 40 seconds if you return early (even on a hot start). I'd love to narrow down the cause, and to see if this crazy hangup issue that Version 3.4.1 says was fixed is the culprit.And, just to check, I removed the nice function wrappers and
ref
passing, andfirebase
still wouldn't exit on afirebase.app().delete()
. nor does.goOffline()
Relevant Code:
https://github.com/one19/im-doin (isomorphic firebase interaction module)
https://github.com/one19/im-doin-slack (function environment where it's not invoked via command line)
firebase web sandbox doesn't provide an adequate location for realizing use case of a node environment.
The text was updated successfully, but these errors were encountered: