Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43966 - [nodejs] dynamically linking against libuv causes stdout truncation bug

Attached to Project: Community Packages
Opened by Jason Papakostas (vith) - Thursday, 26 February 2015, 19:40 GMT
Last edited by Felix Yan (felixonmars) - Friday, 27 February 2015, 16:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When a PHP script shells out to a nodejs script and reads the stdout from it in a certain way, the stdout can be get truncated.
If I rebuild the nodejs package from ABS but remove the --shared-libuv flag from ./configure in the PKGBUILD, the bug will go away.

Arch package versions:
nodejs 0.12.0-2
libuv 1.4.1-2

Note that nodejs v0.12.0 source includes libuv v1.0.2

Steps to reproduce:
This repo contains a test to demonstrate the bug: https://github.com/vith/process-bug
My test failed on both of my Arch Linux installs and passed on other Ubuntu/Fedora systems.
This task depends upon

Closed by  Felix Yan (felixonmars)
Friday, 27 February 2015, 16:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.12.0-3 built with shipped libuv.
Comment by Doug Newgard (Scimmia) - Friday, 27 February 2015, 02:19 GMT
So is this a libuv bug, a change in behavior, or a nodejs bug?
Comment by Jason Papakostas (vith) - Friday, 27 February 2015, 06:12 GMT
All I know is upstream nodejs doesn't seem ready to be linked against this libuv version yet: https://github.com/joyent/node/pull/9179

Loading...