Bob Ippolito

It appears that the code to handle creating and sending the response is entirely separate between mochiweb and webmachine, so a workaround in one wouldn't do anything for the other.

Doesn't repro with the larger body here, regardless of tracing setting.

I don't know why tracing should make a difference, but it could be some sort of timing issue or race condition in httpc. Adding a non-zero amount of sleep between...

The connection is being dropped because the response to the request is sent without the body of the request being read. The server does not bother reading the body because...

http://dl.dropbox.com/u/13940/swfmill/button-gh17.zip That SWF file does not round-trip correctly when pumped through swf2xml then xml2swf. The Makefile builds it and the .flm files for comparison. This is what the output looks...

As far as I can tell this looks like a bug in next.js, the minifier is doing an incorrect rename Here's a segment of the production code that's broken: minified...

This is what lexical's prod build looks like, which would be what next.js's minifier is using as input and explains why next.js got this wrong in this specific way. ```js...

If anyone else is seeing this: I've heard reports that the swc minifier does not have this bug, and it's the default minifier in the latest version of next.js.

This can happen if you have imported multiple versions of Lexical, unfortunately the callstack isn't enough information to help you with this issue. Can you reproduce this error and post...

Make sure you are only using import or only using require. Mixing both could cause problems. Are you using any third party packages that depend on lexical? Can you post...