-
-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to get it working with restify's clients #79
Comments
The intereceptors are removed once they are "used". |
I setup the nock interceptor before each test so don't think it's that. It's something to do with how restify modifies the node http request object, it's probably out of the scope of nock to try and fix it. |
Yeah, you're right, sorry my coffeescript reading is bad. Reopening this one just to make sure if it's not a nock bug. You can add a |
No feedback, so I'm closing this one. |
I'm having the same problem. Nock is not working for the restify json client. I tried adding .log(console.log) but nothing was logged. It just hangs. You should be able to repro this quite easily. |
You can inspect what nock is trying to do by putting a callback using .log() If that doesn't get you an insight, I'll need a failing test case (a gist is fine). Pedro On Tuesday, 19 de February de 2013 at 07:40, Jason Avinger wrote:
|
Nock can't be used with Restify now. var moduleCallback; Nock knows when req.end is called. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
Can't seem to get it working with restify's various clients, but mainly the json client. Below test shows the nock stub working fine with a plain http.request call, but in the second attempt -- using the same url/port and method -- the test hangs when making the request..
console output:
The text was updated successfully, but these errors were encountered: