4 ms·
Oh, this is an interesting lead.... I feel pretty certain the request isn't coming from our Python after stepping-thru the code. The other suggestions -- using
by encoderer 12y ago
Oh, this is an interesting lead.... I feel pretty certain the request isn't coming from our Python after stepping-thru the code.
The other suggestions -- using a SSL proxy -- has been my plan of attack.
- Someone 12y agoIf it takes several seconds to set up a test, I would give this a try: - start a test from the IDE, - wait a second or so, - manually pause all threads, - look at the stacks of the threads. Might take two or three attempts, but likely should learn you a lot. Alternatively, use a real profiler to find the call(s) that take lots of time.
- RubyPinch 12y agomocking/replacing the http/urllibs? save a traceback when a connection is made?
- ekimekim 12y agoTry an strace? strace -e trace=network ./run_my_unit_tests
- mst 12y agoAlso -f so it follows forking (I always forget that the first time, swear, and have to re-run strace with it)
- airza 12y agoWhat OS are you running? It's pretty straightforward to get going on OSX in my experience.