-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: set up sandbox for script execution [INS-3378] #6991
Conversation
We should document the intended lifetime of the hidden browser window, eg. app start->app close or per function call, or whatever. |
@jackkav It sounds reasonable, I've updated its design and workflow in the doc, please have a look. |
Will create a naive version for this. |
hiddenBrowserWindow.loadURL(hiddenBrowserWindowUrl); | ||
|
||
console.log( | ||
`[main][init hidden win step 1/6]: starting hidden browser window(id=${hiddenBrowserWindow.id}): `, |
Check notice
Code scanning / Semgrep OSS
Semgrep Finding: javascript.lang.security.audit.unsafe-formatstring.unsafe-formatstring Note
…re are multiple windows now
chore: refactor table driven tests into the normal style
1358986
to
2ad8d17
Compare
Changes:
This change basically sets up a sandbox which is an isolated environment for executing scripts, it contains following changes: