-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(start): wait for emulated android to really be ready before signaling #161
Conversation
4590b30
to
f3bda88
Compare
Blocked on #163 |
9846f02
to
4bbae01
Compare
Unblocked! |
error.message + ')'); | ||
}) | ||
.then<string>(() => { | ||
logger.info('Waiting on for ' + avdName + ' to be ready to launch chrome'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'Waiting for '
@@ -422,6 +438,7 @@ function sendStartedSignal(signal: string, viaIPC: boolean) { | |||
logger.warn('No IPC channel, sending signal via stdout'); | |||
} | |||
} | |||
console.log(signal); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to be here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The signal goes to stdout if it isn't send by and IPC channel. This functionality was accidentally removed in 1f9713a, and I fixed it while debugging this PR. I could make a issue to document the bug/fix if you'd like
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see. Yeah, it'd be nice to have a short comment explaining that.
lgtm, minor nits |
…ling Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be booted up and ready to instance chrome. While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of `lib/cmds/start.ts` was being devoted to this one feature. Also closes angular#166
…ling (angular#161) Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be booted up and ready to instance chrome. While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of `lib/cmds/start.ts` was being devoted to this one feature. Also closes angular#166
…ling (angular#161) Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be booted up and ready to instance chrome. While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of `lib/cmds/start.ts` was being devoted to this one feature. Also closes angular#166
…ling (angular#161) Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be booted up and ready to instance chrome. While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of `lib/cmds/start.ts` was being devoted to this one feature. Also closes angular#166
Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.
While I was doing that I moved some stuff into
lib/utils.ts
since I felt like too much oflib/cmds/start.ts
was being devoted to this one feature.Additionally,
--started-signifier
wasn't sending anything to the console, so I fixed that too (see #166)