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.

Sign up for GitHub

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

Jump to bottom

Evaluate TaskGroup v5's destroyOnceDone #18

Open
balupton opened this issue Jun 7, 2016 · 1 comment
Open

Evaluate TaskGroup v5's destroyOnceDone #18

balupton opened this issue Jun 7, 2016 · 1 comment
Labels
enhancement Improvement or suggestion

Comments

@balupton
Copy link
Member

balupton commented Jun 7, 2016

Should the global suite have destroyOnceDone enabled or disabled? This should allow exit to correctly fire on browser environments, where no process.exit is emitted - however, it may already do so, just multiple times, which is also acceptable. This needs to be revaluated when #17 is done.
@balupton
Copy link
Member Author

balupton commented Jun 19, 2016 •
edited
Loading

Possible regression around this functionality:

@balupton balupton mentioned this issue Jun 27, 2016
Closed
@mikeumus mikeumus added enhancement Improvement or suggestion discussion labels Jan 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improvement or suggestion
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikeumus @balupton