Closed mtstickney closed 7 years ago
Looks like this was an issue with our application after all, and not part of wookie. After wading through the promise-related calls, I found one of our controllers was using return-from
in a lambda improperly, which caused the error.
Apologies for the noise.
No problem, glad you found it!
I saw this in my server logs the other day, and I'm having some trouble determining whether this is actually a bug or not. The error seems to be same thing as #68, but in a different place (somewhere in
setup-parser
) -- I believe the "response already sent" error is erroneous, and only happens because I'm trying to send a status page out in response to an error that's occurred after the original response has been processed.There's a (rather large) backtrace pasted below that I'm trying to analyze to see where this could have originated from. To complicate matters, this is a clackup app, and I'm using an older version of wookie (dated 2015-09-23). I'm still working through the problem, but I figured I'd report it early in case you knew what it was. I'll update with any further progress.