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

Would like a way to have an isolate which does not provide dart:io #20281

Open
eseidelGoogle opened this issue Aug 6, 2018 · 3 comments
Open

Would like a way to have an isolate which does not provide dart:io #20281

eseidelGoogle opened this issue Aug 6, 2018 · 3 comments
Labels
c: new feature Nothing broken; request for a new capability customer: dream (g3) dependency: dart Dart team may need to help us engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team

Comments

@eseidelGoogle
Copy link
Contributor

customer:dream has asked for the ability to launch an isolate without providing it access to dart:io.

Similarly @sbaranov mentions that if we ever implement #14330 for iOS, that may also require such a boundary to comply with store guidelines.
@zanderso
Copy link
Member

zanderso commented Aug 7, 2018

I think this should probably be part of a more general mechanism for passing capabilities to child isolates. I'll do some thinking about this.

@eseidelGoogle eseidelGoogle changed the title Would like a spawnIsolate which allows removing dart:io Would like a way to have an isolate which does not provide dart:io Aug 8, 2018
@zoechi zoechi added engine flutter/engine repository. See also e: labels. dependency: dart Dart team may need to help us labels Aug 23, 2018
@zoechi zoechi added this to the Goals milestone Jan 31, 2019
@zoechi zoechi added the c: new feature Nothing broken; request for a new capability label Jan 31, 2019
@ened
Copy link
Contributor

ened commented May 31, 2019

@zanderso did you have a conclusion? The general mechanism would probably also allow isolates to only contain a selected set of plugins each, right?

@zanderso
Copy link
Member

zanderso commented Jun 4, 2019

Sorry for dropping the ball on this. It would be nice to be able to do this with a new capabilities mechanism, but this is probably more readily implemented with a bigger hammer in the VM by filtering libraries by Uri at child isolate startup. @a-siva @rmacnak-google

@kf6gpe kf6gpe added the P2 Important issues not at the top of the work list label May 29, 2020
@Hixie Hixie removed this from the None. milestone Aug 17, 2020
@flutter-triage-bot flutter-triage-bot bot added team-engine Owned by Engine team triaged-engine Triaged by Engine team labels Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: new feature Nothing broken; request for a new capability customer: dream (g3) dependency: dart Dart team may need to help us engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ened @zoechi @Hixie @kf6gpe @zanderso @eseidelGoogle @pedromassangocode