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

Cannot read output from another node process installed with snap #2713

Closed
angryziber opened this issue May 18, 2020 · 5 comments
Closed

Cannot read output from another node process installed with snap #2713

angryziber opened this issue May 18, 2020 · 5 comments

Comments

@angryziber
Copy link

When node is installed via snap (14/stable channel).

execSync('node something').toString() always returns an empty string with no errors.
This is a problem as many transforming packages use this trick to deasync processing.

execSync('node something', {stdio: 'inherit'}).toString()
would correctly display the output in parent process's stdout, but there is no way of capturring it.

If node is installed via deb package, there is no such problem.

Makes jest/etc unusable in many cases.

@mscdex mscdex transferred this issue from nodejs/node May 18, 2020
@bnoordhuis
Copy link
Member

That's almost certainly caused by snap's security sandbox. Try getting in touch with the maintainer of the node snap, he or she can probably provide more details.

@angryziber
Copy link
Author

The problem is only when node reads output of another node.
No problems with reading output of other apps, nor other apps reading output of node...

@angryziber
Copy link
Author

Added issue here: nodesource/distributions#1053

@gireeshpunathil
Copy link
Member

@angryziber - is this resolved?

@gireeshpunathil
Copy link
Member

inactive, closing. feel free to re-open if it is outstanding

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

No branches or pull requests

3 participants