You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wasted like 3 hours in spaghetti code trying to debug this and finally found the problem to be that my route handler ends the response with res.end(200). Changing that to res.send(200) seems to have fixed the problem and now I can reach the end(callback) method of supertest.
The text was updated successfully, but these errors were encountered:
I must apologize for this. I tried to reproduce the issue in a new project, I couldn't. I went back to the original project where I encountered this but it's changed since, and I couldn't reproduce the bug there either. Apologize for wasting your time.
It's all good. Perhaps at the time, the project was using domains in some strange way, that might have effected this since in node core, http.OutgoingMessage will throw if you attempt to write a non-string or buffer as you showed in your example.
Wasted like 3 hours in spaghetti code trying to debug this and finally found the problem to be that my route handler ends the response with
res.end(200)
. Changing that tores.send(200)
seems to have fixed the problem and now I can reach theend(callback)
method of supertest.The text was updated successfully, but these errors were encountered: