Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKrexVLvD_pkgn+37GGmU=7ojiPVPfMLm3w4o_OH7n_Kj=hY6A@mail.gmail.com>
References: 
 <CACrj35HTshwCppj7dpQMWjYx=eM_vrzeOhSrxGcjQKLsuUkhAw@mail.gmail.com>
 <CACrj35GSgdaGE8ZZJg+qwD-eG_9JyxhhF3Gr5r0ALLnxFcLL=Q@mail.gmail.com>
 <CAKrexVL6xNyP9uZ87XovOT6DZdurT9TC6yM6ANeH0CL9i5FeUg@mail.gmail.com>
 <CACrj35FpY8if5b=S5r_etbComajU3KHydrrRqgO3vkerORUa8Q@mail.gmail.com>
 <CAKrexVLvD_pkgn+37GGmU=7ojiPVPfMLm3w4o_OH7n_Kj=hY6A@mail.gmail.com>
From: Mark Hahn <mark@hahnca.com>
Date: Tue, 31 Jan 2012 14:57:27 -0800
Message-ID: 
 <CACrj35F_TfOWMwapw-DtJDV0n6S9usrhU4n-TGEb27DhG35gEQ@mail.gmail.com>
Subject: Re: new ReferenceError(options is not defined)
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=bcaec531420f42547c04b7dae484

--bcaec531420f42547c04b7dae484
Content-Type: text/plain; charset=ISO-8859-1

How did the couch error message know the word "options"?  My use of the
word options is for the specific node call http.request.

BTW: thanks for the help.  I'm sure I'm doing something stupid.

On Tue, Jan 31, 2012 at 2:48 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?
> > > > >
> > > > >
> > > >
> > >
> >
>

--bcaec531420f42547c04b7dae484--