vercel: Alias immediately after a deploy now fails

We are investigating the issue. We recently started to enforce that an alias can’t be pointed to a deployment that can’t handle traffic. Unfortunately it seems these changes had some side effects.

In fact sometime the deploy is failing.

$ now --public deploy build/
> Deploying C:\projects\aim-web-app\client\build under stevelee
> Using Node.js 8.9.4 (default)
> Ready! https://alwaysinmind-qntfvyiiaa.now.sh [2s]
> Initializing…

and no more status outputs to console

Should be fixed by now! It was a tricky (but simple) issue that was only affecting requests being served by bru.now.sh. I’m in Brazil, so I’m being served by sfo.now.sh – that’s why I had a hard time reproducing it.

@SteveALee could you confirm it doesn’t happen anymore? 🙂

I just started getting this issue. It used to exit after deploying, now after running now it sits for about 60s then says:

> Deployment complete!
> Running in sfo1

@matheuss I can confirm it’s working again for me. Thanks for the fix. 👍

@SteveALee crap that’s my bad! alias is the correct name, my apologies. Thanks for the pickup @matheuss .

@matheuss yes it seemed a strange use of ‘files’ 😃

Glad you got some useful intell!

@matheuss sure, will try ASAP 😃

Sleep got removed from windows and replaced with timeout ages ago.

I find in git for windows bash that timeout always runs the bash version of timeout which is no use. Hence the one line portable node script I posted above.

A hacky package.json script to give a portable delay till this command becomes synchronous again

    "pause": "node -e \"((time) => new Promise((resolve) => setTimeout(resolve, time)))(process.argv[1]).then(() => process.exit(0))\" 3000"

The CLI exits successfully after initializing - This started happening to me after updating to 0.9.3