Skip to content
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

Detect when isolate reload is barred and inform the user #5582

Merged
merged 1 commit into from
Aug 24, 2016
Merged

Detect when isolate reload is barred and inform the user #5582

merged 1 commit into from
Aug 24, 2016

Conversation

johnmccutchan
Copy link
Contributor

  • React to the signal from the VM that an isolate is barred from performing a hot reload and must be restarted.
  • Roll the engine forward

@johnmccutchan
Copy link
Contributor Author

@devoncarew @Hixie

@devoncarew
Copy link
Member

I think some of the engine artifacts aren't yet available on google storage.

@@ -445,9 +445,18 @@ class HotRunner extends ResidentRunner {
} else {
flutterUsage.sendEvent('hot', 'reload');
}
} catch (errorMessage, st) {
} catch (error, st) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we ensure that we're only catching a Map here (on Map)?

@devoncarew
Copy link
Member

lgtm, but you probably want to wait to land this until all the engine artifacts build through.

@johnmccutchan johnmccutchan merged commit 09e68c3 into flutter:master Aug 24, 2016
@yjbanov
Copy link
Contributor

yjbanov commented Aug 24, 2016

A lot of breakages caused by this PR (dashboard, sample log file)

@yjbanov
Copy link
Contributor

yjbanov commented Aug 24, 2016

Rolling it back in #5590

@johnmccutchan
Copy link
Contributor Author

Thanks Yegor!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants