Skip to content

Conversation

srujzs
Copy link
Contributor

@srujzs srujzs commented Oct 9, 2025

We can't actually pause during execution so we shouldn't signal that we did.

We can't actually pause during execution so we shouldn't
signal that we did.
@srujzs srujzs requested review from bkonyi and jyameo October 9, 2025 23:05
@srujzs
Copy link
Contributor Author

srujzs commented Oct 9, 2025

I tried removing _currentPauseEvent entirely, but it looks like Flutter tools' testing is relying on a pause event at start, specifically from here when the isolate is created and pauseIsolatesOnStart is true. For now, I left that, modifications to that flag which also results in a new pause event being sent, and resume, where a resume event is sent.

It's not clear to me whether PauseStart and Resume should still be sent even though we don't pause. I suppose it signals on start that the isolate has started but we haven't run main yet?

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

Successfully merging this pull request may close these issues.

1 participant