Skip to content

Vanilla example fails #10

Closed
weskinner opened this Issue Jan 17, 2012 · 5 comments

4 participants

@weskinner

npm version 0.7.0
couchdb 1.1.0

changes_stream.log.setLevel(self.log.level.levelStr)
                                          ^

TypeError: Cannot read property 'levelStr' of undefined
at Request.on_feed_response as onResponse
at ClientRequest. (/home/william/projects/tmp/node_modules/follow/node_modules/request/main.js:430:16)
at ClientRequest.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1225:11)
at HTTPParser.onHeadersComplete (http.js:102:31)
at Socket.ondata (http.js:1124:24)
at TCP.onread (net.js:336:27)

@zemirco
zemirco commented Jan 21, 2012

jep same problem here

node version 0.6.7
npm version 1.1.0-beta-10

/node_modules/follow/lib/feed.js:238
changes_stream.log.setLevel(self.log.level.levelStr)
TypeError: Cannot read property 'levelStr' of undefined
at Request.on_feed_response as onResponse
at ClientRequest. (/node_modules/follow/node_modules/request/main.js:430:16)
at ClientRequest.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1238:11)
at HTTPParser.onHeadersComplete (http.js:102:31)
at Socket.ondata (http.js:1137:24)
at TCP.onread (net.js:354:27)

@jameseisenhauer

any thoughts on this issue. I am having same problem.

windows 7
node v0.6.8
npm 1.1.0-2
couchdb "version": "1.0.2"

F:\Se-WorkSpace\Gavel\src\com>node followTest.js

F:\Se-WorkSpace\Gavel\src\com\node_modules\follow\lib\feed.js:238
changes_stream.log.setLevel(self.log.level.levelStr)
^
TypeError: Cannot read property 'levelStr' of undefined
at Request.on_feed_response as onResponse
at ClientRequest. (F:\Se-WorkSpace\Gavel\src\com\node_modules\follow\node_modules\request\main.js:430:16)
at ClientRequest.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1238:11)
at HTTPParser.onHeadersComplete (http.js:102:31)
at Socket.ondata (http.js:1137:24)
at TCP.onread (net.js:354:27)

F:\Se-WorkSpace\Gavel\src\com>node -v
v0.6.8

F:\Se-WorkSpace\Gavel\src\com>npm -v
1.1.0-2

@weskinner

"follow" : "<=0.3.1" is my temporary solution

@jameseisenhauer

thanks wes your work around worked for me as well.

@jhs jhs closed this in 417edee Feb 3, 2012
@jhs
Iris Couch member
jhs commented Feb 3, 2012

Thanks for the bug report, and sorry for my careless error. This is fixed and pushed to NPM in version 0.7.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.