0.8.21 compiled from source on a macbook (mountain lion 10.8.2). I just tried writing a test case to reproduce and that did get the 'end' event. I then tried just pulling out the parts of my real code that were hanging without 'end' into a separate util method, and that util method *did* get the 'end' event. Maybe there was some other value in my original scope which was affecting things, though I can't pin down what it might have been.
Sorry I can't provide a better report than this. I'm willing to write it off as some likely transient error in my code though and if I can catch it in the act again I'll send along the report and test script. jonathan On Monday, March 4, 2013 9:21:12 AM UTC-8, mscdex wrote: > > On Mar 4, 11:30 am, Jonathan Gold <[email protected]> wrote: > > Did this ever get filed as a bug or otherwise addressed? I can confirm > the > > same behavior and discrepancies in the docs, and it's not clear how I'm > > supposed to correctly end my client reading of a 200 response (which > just > > hangs with no end/error/close events). > > What node version are you using? > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
