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

fix: always close file handles to stdout/stderr logs #259

Merged
merged 2 commits into from May 17, 2023

Conversation

Junyan
Copy link
Contributor

@Junyan Junyan commented Dec 9, 2021

It should closeSync outFile and errFile when userDataDir is custom.

fixes #260

if (this.userDataDir === undefined || this.opts.userDataDir !== undefined) {
return resolve();
}

if (this.outFile) {
this.fs.closeSync(this.outFile);
delete this.outFile;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Makes sense we should always close these file handles when done. I'm curious though, what was the error you were seeing? EDIT: ah, you filed an issue #260

@connorjclark connorjclark changed the title remove custom userDataDir error fix: always close file handles to stdout/stderr logs Mar 14, 2022
@connorjclark
Copy link
Collaborator

Can you run yarn format, or allow upstream to push to your fork branches so I can run it?

@Junyan
Copy link
Contributor Author

Junyan commented Mar 29, 2022

@connorjclark done

@connorjclark connorjclark merged commit f9e4369 into GoogleChrome:main May 17, 2023
3 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error "operation not permitted, unlink chrome-err.log"
2 participants