Possibly unhandled Error: 1; Deploy build without mongo url #66
Comments
|
Try deploying with -d flag. There is a bug where deploying on free accounts without it hangs. It's due to the prompt now asks during deploys on free account.
-
MJ
… On Sep 3, 2017, at 7:27 AM, janat08 ***@***.***> wrote:
Using meteor-now gets stuck on deploy build step after logging this.
dled Error: 1
at Promise$_rejecter (C:\Users\ALERATOR\AppData\Roaming\npm\node_modules\me
teor-now\node_modules\promise-spawner\node_modules\bluebird\js\main\promise.js:
590:44)
at C:\Users\ALERATOR\AppData\Roaming\npm\node_modules\meteor-now\node_modul
es\promise-spawner\index.js:85:13
at tryCatch1 (C:\Users\ALERATOR\AppData\Roaming\npm\node_modules\meteor-now
\node_modules\promise-spawner\node_modules\bluebird\js\main\util.js:63:19)
at Promise$_callHandler [as _callHandler] (C:\Users\ALERATOR\AppData\Roamin
g\npm\node_modules\meteor-now\node_modules\promise-spawner\node_modules\bluebir
d\js\main\promise.js:695:13)
at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (C:\Use
rs\ALERATOR\AppData\Roaming\npm\node_modules\meteor-now\node_modules\promise-sp
awner\node_modules\bluebird\js\main\promise.js:711:18)
at Promise$_settlePromiseAt [as _settlePromiseAt] (C:\Users\ALERATOR\AppDat
a\Roaming\npm\node_modules\meteor-now\node_modules\promise-spawner\node_modules
\bluebird\js\main\promise.js:868:14)
at Promise$_settlePromises [as _settlePromises] (C:\Users\ALERATOR\AppData\
Roaming\npm\node_modules\meteor-now\node_modules\promise-spawner\node_modules\b
luebird\js\main\promise.js:1006:14)
at Promise$_rejectPromises [as _rejectPromises] (C:\Users\ALERATOR\AppData\
Roaming\npm\node_modules\meteor-now\node_modules\promise-spawner\node_modules\b
luebird\js\main\promise.js:999:10)
at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (C:\Users\ALERA
TOR\AppData\Roaming\npm\node_modules\meteor-now\node_modules\promise-spawner\no
de_modules\bluebird\js\main\async.js:74:12)
at Async$consumeFunctionBuffer (C:\Users\ALERATOR\AppData\Roaming\npm\node_
modules\meteor-now\node_modules\promise-spawner\node_modules\bluebird\js\main\a
sync.js:37:14)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)
⢃⠨
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
that worked.
On Sun, Sep 3, 2017 at 7:56 PM, Mirza Joldic <[email protected]>
wrote:
… Try deploying with -d flag. There is a bug where deploying on free
accounts without it hangs. It's due to the prompt now asks during deploys
on free account.
-
MJ
> On Sep 3, 2017, at 7:27 AM, janat08 ***@***.***> wrote:
>
> Using meteor-now gets stuck on deploy build step after logging this.
>
> dled Error: 1
> at Promise$_rejecter (C:\Users\ALERATOR\AppData\
Roaming\npm\node_modules\me
> teor-now\node_modules\promise-spawner\node_modules\bluebird\
js\main\promise.js:
> 590:44)
> at C:\Users\ALERATOR\AppData\Roaming\npm\node_modules\
meteor-now\node_modul
> es\promise-spawner\index.js:85:13
> at tryCatch1 (C:\Users\ALERATOR\AppData\Roaming\npm\node_modules\
meteor-now
> \node_modules\promise-spawner\node_modules\bluebird\js\main\
util.js:63:19)
> at Promise$_callHandler [as _callHandler] (C:\Users\ALERATOR\AppData\
Roamin
> g\npm\node_modules\meteor-now\node_modules\promise-spawner\
node_modules\bluebir
> d\js\main\promise.js:695:13)
> at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler]
(C:\Use
> rs\ALERATOR\AppData\Roaming\npm\node_modules\meteor-now\
node_modules\promise-sp
> awner\node_modules\bluebird\js\main\promise.js:711:18)
> at Promise$_settlePromiseAt [as _settlePromiseAt]
(C:\Users\ALERATOR\AppDat
> a\Roaming\npm\node_modules\meteor-now\node_modules\
promise-spawner\node_modules
> \bluebird\js\main\promise.js:868:14)
> at Promise$_settlePromises [as _settlePromises]
(C:\Users\ALERATOR\AppData\
> Roaming\npm\node_modules\meteor-now\node_modules\
promise-spawner\node_modules\b
> luebird\js\main\promise.js:1006:14)
> at Promise$_rejectPromises [as _rejectPromises]
(C:\Users\ALERATOR\AppData\
> Roaming\npm\node_modules\meteor-now\node_modules\
promise-spawner\node_modules\b
> luebird\js\main\promise.js:999:10)
> at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer]
(C:\Users\ALERA
> TOR\AppData\Roaming\npm\node_modules\meteor-now\node_
modules\promise-spawner\no
> de_modules\bluebird\js\main\async.js:74:12)
> at Async$consumeFunctionBuffer (C:\Users\ALERATOR\AppData\
Roaming\npm\node_
> modules\meteor-now\node_modules\promise-spawner\node_
modules\bluebird\js\main\a
> sync.js:37:14)
> at _combinedTickCallback (internal/process/next_tick.js:73:7)
> at process._tickCallback (internal/process/next_tick.js:104:9)
> ⢃⠨
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKz-gXGjGaeEVFB56ShdofiUoJJ0Ojebks5seq_2gaJpZM4PLKL9>
.
|
|
Perhaps this option should be enabled if free account is detected? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using meteor-now gets stuck on deploy build step after logging this.
The text was updated successfully, but these errors were encountered: