We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes the facet server wasn't starting and I tracked it down to an error on this line:
let percent_cpu = Number(stdout.split('\n')[1].trim());
While debugging, I found stdout to be an empty string. Should probably guard against this.
stdout
I got around it by just setting the percent_cpu variable to a phony constant string.
percent_cpu
Encountered this on Windows 10 and Max 8.2.2.
The text was updated successfully, but these errors were encountered:
Great catch, thanks! I don't have a Windows machine to test, but this should safeguard against ever running .trim() on a non-string.
Sorry, something went wrong.
Commit: 216ddb3
No branches or pull requests
Sometimes the facet server wasn't starting and I tracked it down to an error on this line:
While debugging, I found
stdout
to be an empty string. Should probably guard against this.I got around it by just setting the
percent_cpu
variable to a phony constant string.Encountered this on Windows 10 and Max 8.2.2.
The text was updated successfully, but these errors were encountered: