-
Notifications
You must be signed in to change notification settings - Fork 115
Progress bar for deploying functions? #76
Comments
Can you provide details with which I can debug your issue? Version of Node.js, version of the emulator, sample code that you're trying to deploy, command with which you're deploying the function, etc. |
apologies, should have included it at the top: node@v7.6.0 Deployed the basic 'helloWorld' function, which ran fine initially after install ( Trying to deploy a real function on the emulator that has a few dependencies takes awhile, and it seems to be hanging without any sort of feedback. Would be nice if there was some sort of progress bar or [error] feedback if the emulator is running into issues. |
I recommend using Node.js v6.9.1, as that's the version of Node.js used by the production Cloud Functions service. I'll still need more information in order to reproduce the problem you're seeing. Can you post here the code for a function that I can deploy in order to reproduce your issue? Can you post what your |
running the command
I am noticing a mismatch in ports for my functions code, and where the emulator is running, but not sure if that's the issue |
@donjae Are you still encountering issues with deployment? Deploying to the Emulator should be really fast, no more than a couple seconds. |
Yeah, still encountering issues. But like you mentioned earlier, I'm using a non-supported node version. I wish I could be more specific in what's causing the issue, but don't really have much info besides that it's stuck on loading without any response. I'll see if I can pull up some logs later when I try again |
I'll be publishing another version soon that will hopefully solve your issue. |
thanks fam, I'll keep an eye out and test it out when it's released and lyk |
I released 1.0.0-alpha.16, can you see if it works better for you? |
Description
Feature request to have some sort of progress bar for deploying functions. Can't tell if functions is running into issues or just hanging
The text was updated successfully, but these errors were encountered: