incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keith Gable <zi...@ignition-project.com>
Subject Re: new ReferenceError(options is not defined)
Date Wed, 01 Feb 2012 17:25:12 GMT
Not knowing anything about node, but is CouchDB trying to execute the
CoffeeScript or the compiled JavaScript?
On Feb 1, 2012 10:58 AM, "Mark Hahn" <mark@hahnca.com> wrote:

> That's a feature of coffeescript.  A var by itself is expanded to
> {headers:headers}.  It makes for very readable code if you name your local
> variables to match.
>
> hash = {var1, var2, var3}   and    {var1, var2, var3}  = hash
>
> It makes it very easy to use hashes for function arguments.
>
> Sorry if this was off-topic.  I love coffeescript.
>
>
> On Wed, Feb 1, 2012 at 8:17 AM, Keith Gable <ziggy@ignition-project.com
> >wrote:
>
> > That's invalid JavaScript. "headers" is inserted in this hash/map
> without a
> > value.
> > On Jan 31, 2012 4:49 PM, "CGS" <cgsmcmlxxv@gmail.com> wrote:
> >
> > > At line 6 from your node code snippet you defined variable "options":
> > >
> > > options = {host: 'localhost', port: mh.dbPort, method: 'PUT', headers,
> > > path: dbPath}
> > >
> > > My toss of dices would go in the definition of the headers, but that's
> > just
> > > a wild guess.
> > >
> > > CGS
> > >
> > >
> > >
> > > On Tue, Jan 31, 2012 at 11:30 PM, Mark Hahn <mark@hahnca.com> wrote:
> > >
> > > > I'm not familiar with the options you are talking about.  Are these
> > some
> > > > kind of http options or couchdb options in the json body?
> > > >
> > > > On Tue, Jan 31, 2012 at 2:16 PM, CGS <cgsmcmlxxv@gmail.com> wrote:
> > > >
> > > > > Hi Mark,
> > > > >
> > > > > It looks very much like an JS engine error and it seems there is
a
> > > > problem
> > > > > in setting up the "options" parameter. From the error, either
> > "options"
> > > > > parameter doesn't exist, or it is not well formatted (no idea about
> > > > > node.js). Another option is an incompatibility with JS engine
> version
> > > > which
> > > > > doesn't accept your "options" in that format.
> > > > >
> > > > > I would suggest to ask about what's wrong with your "options" setup
> > > (and
> > > > JS
> > > > > engine compatibility if nothing is wrong) in node.js mailing
> > list/forum
> > > > or
> > > > > wait here for someone who knows node.js enough to see where you
> went
> > > > wrong
> > > > > there. Definitely the error is there, but I cannot tell you what
> as I
> > > > have
> > > > > no idea about node.js (as I said it before).
> > > > >
> > > > > I hope this post will help you at least as a starting point in
> > > debugging.
> > > > >
> > > > > CGS
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jan 31, 2012 at 10:00 PM, Mark Hahn <mark@hahnca.com>
> wrote:
> > > > >
> > > > > > I'm bumping this because it is killing me.  I can't get past
this
> > > > > problem.
> > > > > >  It is happening several places in my code.
> > > > > >
> > > > > > What can cause an "OS Process Error"?
> > > > > >
> > > > > > On Mon, Jan 30, 2012 at 2:29 PM, Mark Hahn <mark@hahnca.com>
> > wrote:
> > > > > >
> > > > > > > I'm getting this error on a put request for an attachment.
> > > > > > >
> > > > > > >     [error] [<0.7533.1>] OS Process Error <0.7546.1>
::
> > > > > > > {<<"unnamed_error">>,
> > > > > > >     <<"(new ReferenceError(\"options is not defined\",
> \"\"))">>}
> > > > > > >
> > > > > > > This is my node code ...
> > > > > > >
> > > > > > > headers = {}
> > > > > > > headers.Authorization     = mh.dbAuthHdr
> > > > > > >  headers['content-type']   = contentType
> > > > > > > headers['content-length'] = contentLength
> > > > > > >  dbPath = '/ri/' + compDoc._id + '/' + attachmentName +
> '?rev=' +
> > > > > > > compDoc._rev
> > > > > > > options = {host: 'localhost', port: mh.dbPort, method:
'PUT',
> > > > headers,
> > > > > > > path: dbPath}
> > > > > > >
> > > > > > > respStr = ''
> > > > > > > resp = null
> > > > > > > readStream = fs.createReadStream filePath
> > > > > > >  readStream.on 'error', (e) ->
> > > > > > > vh.err req, res, 'um: uploadAttachment read error ' +
> compDoc._id
> > > + '
> > > > > ' +
> > > > > > > e.message, 500
> > > > > > >  readStream.pipe http.request options, (resProx) ->
> > > > > > > if +resProx.statusCode isnt 201
> > > > > > >  vh.err req, res,
> > > > > > > 'um: uploadAttachment db request err ' + compDoc._id +
' ' +
> > > > > > > resProx.statusCode, 500
> > > > > > >  return
> > > > > > > resProx.on 'data', (chunk) -> respStr += chunk.toString()
> > > > > > >  resProx.on 'end', (chunk) ->
> > > > > > > if chunk then respStr += chunk.toString()
> > > > > > >  resp = JSON.parse respStr
> > > > > > > docUpdate = procThumbnails: compDoc.procThumbnails
> > > > > > >  if lastUpdate then docUpdate.needsNotification = yes
> > > > > > > db.updateDoc compDoc._id, docUpdate, (err, doc) ->
> > > > > > >  if err
> > > > > > > log 'dba: uploadAttachment compDoc update err ' + compDoc._id
> > > > > > >  cb false
> > > > > > > return
> > > > > > > compDoc = doc
> > > > > > >  callback true
> > > > > > >
> > > > > > > This is the value of my options ...
> > > > > > >
> > > > > > >          host: <string> localhost
> > > > > > >          path: <string>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /ri/04b7c4eb50d1d01dbb1a0f097bb80/thumbnail-72x48c.jpg?rev=27-3d44ae708d6fe9c835577d71f5e70359
> > > > > > >          method: <string> PUT
> > > > > > >          headers:
> > > > > > >             content-length: <number> 3511
> > > > > > >             content-type: <string> image/jpeg
> > > > > > >             Authorization: <string> Basic ... snipped
...
> > > > > > >          port: <number> 5984
> > > > > > >
> > > > > > > Does anyone have an idea of what I'm doing wrong?
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message