escape char interpretation issue - ql.io

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion escape char interpretation issue
Received-SPF: pass (google.com: domain of su...@subbu.org designates 209.85.212.170 as permitted sender) client-ip=209.85.212.170;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: escape char interpretation issue
From: Subbu Allamaraju <su...@subbu.org>
In-Reply-To: <a13ad5ac-c9c9-4b3c-9a5f-895e74738...@m13g2000yqc.googlegroups.com>
Date: Thu, 12 Apr 2012 13:34:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8A4FCDE-DF0D-4B1B-AC13-5123D4F65...@subbu.org>
References: <ea653cb1-d150-4568-a0f9-99c84dfb6...@p6g2000yqi.googlegroups.com> <E4D3AE7A-B598-44A3-8A49-1831DAAD4...@subbu.org> <a6137cd1-10f3-454f-9ec2-e88c2e7fa...@oo9g2000pbc.googlegroups.com> <41D13038-0A1D-41C4-9C98-16AC17BF6...@subbu.org> <502b67d2-6c30-45d4-8031-c6c467278...@2g2000yqp.googlegroups.com> <1638868f-14d9-4c7c-9213-8ca7fa2a0...@w17g2000yqe.googlegroups.com> <2EF8C68B-CBFE-449B-84BC-15B9B4CCA...@subbu.org> <4bc98f73-d960-4551-b665-32d28b2bc...@2g2000yqk.googlegroups.com> <661CB75E-960D-464C-8838-19A682C9A...@subbu.org> <da6fef61-6d30-4afb-bdd7-7d6533bfb...@m13g2000yqi.googlegroups.com> <21DBE194-BA81-4B62-B594-E19B6B5BF...@subbu.org> <f2d554a7-0542-4648-a84d-a71f47417...@2g2000yqk.googlegroups.com> <4D46B151-574F-41D8-9BF3-10A03E0D8...@subbu.org> <a13ad5ac-c9c9-4b3c-9a5f-895e74738...@m13g2000yqc.googlegroups.com>
To: qlio@googlegroups.com

Got it.

ql.io uses a xml2json which in turn uses node-expat. node-expat is built =
on expat which is a native lib on most operating systems. Since such =
modules are not binary portable, npm uses node-waf to build them =
locally. That step is failing in your case. As I mentioned below, I'm =
able to run ql.io on a fresh CentOS 6.0 VM last night without any =
issues.

However, this issue has bugged us enough that I would like to get to the =
bottom of this.

Let me setup a new CentOS instance on EC2 and share it with you to =
compare.

Subbu=20

On Apr 12, 2012, at 12:40 PM, anandva wrote:

> yes the dir structures are same, file perm are also same.
>=20
> I also did not follow the comment "error without symblink to Release
> from default".
>>> i have created a symblink following this thread, =
http://groups.google.com/group/qlio/browse_thread/thread/d5efdd5dcdbe2cf7/=
ef13c1043abf0ce8?lnk=3Dgst&q=3Dexpat#ef13c1043abf0ce8
> then the error was "unable to load ..." rather than Cannot find the
> file.
>=20
> Could it be that ql.io is unable to load node.js dependent
> functionality (javascript, C++ code)..?
>=20
> -Vivek.
>=20
> On Apr 12, 11:35 am, Subbu Allamaraju <su...@subbu.org> wrote:
>> On Mac, do you see the same dir structure? I also did not follow the =
comment "error without symblink to Release from default".
>>=20
>> Subbu
>>=20
>> On Apr 11, 2012, at 11:00 PM, anandva wrote:
>>=20
>>=20
>>=20
>>> here's env details, soln in the link didn;t help much,
>>=20
>>> node -v >> v0.6.15
>>> npm -v >> 1.1.16
>>> centOS >> CentOS (Final) 5.5 x86_64
>>=20
>>> here is the error without symblink to Release from default,
>>=20
>>> Error: Cannot find module '../build/default/node-expat'
>>>    at Function._resolveFilename (module.js:332:11)
>>>    at Function._load (module.js:279:25)
>>>    at Module.require (module.js:354:17)
>>>    at require (module.js:370:17)
>>>    at Object.<anonymous> =
(/home/vapuri/mhwork/qlio/node_modules/ql.io-
>>> =
app/node_modules/ql.io-console/node_modules/xml2json/node_modules/node-
>>> expat/lib/node-expat.js:6:14)
>>>    at Module._compile (module.js:441:26)
>>>    at Object..js (module.js:459:10)
>>>    at Module.load (module.js:348:31)
>>>    at Function._load (module.js:308:12)
>>>    at Module.require (module.js:354:17)
>>=20
>>> -Vivek.
>>=20
>>> On Apr 11, 9:34 pm, Subbu Allamaraju <su...@subbu.org> wrote:
>>>> Which version of node/npm are you running?
>>=20
>>>> I just built a CentOS 6.0 x86 VM using VirtualBox. I installed gcc, =
openssl, expat, expat-devel, and then node-0.6.14. After that I created =
a new ql.io app and it started fine.
>>=20
>>>> On some distros, some folks ran into this issue. Could you try the =
fix in the link below?
>>=20
>>>>        http://archive.cnblogs.com/a/2178519
>>=20
>>>> Subbu
>>=20
>>>> On Apr 11, 2012, at 5:39 PM, anandva wrote:
>>=20
>>>>> Subbu,
>>=20
>>>>> i managed to install expat and expat-devel packages, after npm =
clean
>>>>> and reinstall went successfully but got into below  error on =
startup
>>>>> --Error: Cannot find module '../build/default/node-expat' >> tried =
ln -
>>>>> s Release default now am getting below error
>>>>> -bash-3.2$ bin/start.sh
>>>>> Error: Unable to load shared library /home/vapuri/mhwork/qlio/
>>>>> node_modules/ql.io-app/node_modules/ql.io-console/node_modules/
>>>>> xml2json/node_modules/node-expat/build/Release/node-expat.node
>>>>>    at Object..node (module.js:472:11)
>>>>>    at Module.load (module.js:348:31)
>>>>>    at Function._load (module.js:308:12)
>>>>>    at Module.require (module.js:354:17)
>>>>>    at require (module.js:370:17)
>>>>>    at Object.<anonymous> =
(/home/vapuri/mhwork/qlio/node_modules/ql.io-
>>>>> =
app/node_modules/ql.io-console/node_modules/xml2json/node_modules/node-
>>>>> expat/lib/node-expat.js:6:14)
>>>>>    at Module._compile (module.js:441:26)
>>>>>    at Object..js (module.js:459:10)
>>>>>    at Module.load (module.js:348:31)
>>>>>    at Function._load (module.js:308:12)
>>=20
>>>>> As suggested in another thread tried deleting combinations of npm =
or
>>>>> sudo or perm, none of them is helping...
>>=20
>>>>> -Vivek.
>>=20
>>>>> On Apr 11, 3:51 pm, Subbu Allamaraju <su...@subbu.org> wrote:
>>>>>> I'm not sure what native libs are needed for expat on CentOS - =
but here is a quick way to figure out.
>>=20
>>>>>> Try "npm install expat" in some temp dir. If that goes through =
you've the right dependencies installed. If not, expat and expat-devel =
are the libs to look for.
>>=20
>>>>>> On Apr 11, 2012, at 11:37 AM, anandva wrote:
>>=20
>>>>>>> That fixed issue on my mac able to proceed,
>>=20
>>>>>>> While trying to setup on CentOS5.5 do we need "expat =
libexpat1-dev"
>>>>>>> modules and tried without those
>>>>>>> getting different errors deleting and not deleting npm folder, =
here
>>>>>>> are the details,
>>>>>>> https://github.com/isaacs/npm/issues/2359
>>=20
>>>>>>> Appreciate your help Subbu.
>>=20
>>>>>>> -Vivek.
>>=20
>>>>>>> On Apr 11, 11:07 am, Subbu Allamaraju <su...@subbu.org> wrote:
>>>>>>>> Looks like an npm issue. Could you try deleting ~/.npm dir and =
redo make clean install?
>>=20
>>>>>>>> On Apr 11, 2012, at 12:58 AM, anandva wrote:
>>=20
>>>>>>>>> I should have refreshed only ql.io-compiler module instead i =
did make
>>>>>>>>> clean install on myapp dir , getting following error, any =
idea?
>>=20
>>>>>>>>> 1. ENOENT, lstat =
'/..../node_modules/ql.io-app/node_modules/ql.io-
>>>>>>>>> console/node_modules/validator/index.js'
>>>>>>>>> 2.
>>>>>>>>> npm ERR! EEXIST, mkdir =
'/.../node_modules/ql.io-app/node_modules/ql.io-
>>>>>>>>> console/node_modules/connect/lib'
>>>>>>>>> npm ERR! File exists: =
/..../node_modules/ql.io-app/node_modules/ql.io-
>>>>>>>>> console/node_modules/connect/lib
>>>>>>>>> npm ERR! Move it away, and try again.
>>=20
>>>>>>>>> tried deleting the folders but those are not existing.
>>=20
>>>>>>>>> On Apr 10, 6:44 pm, anandva <apurivi...@gmail.com> wrote:
>>>>>>>>>> Thanks Suddu, i will give it a try after the update later =
today. Thx.
>>=20
>>>>>>>>>> On Apr 10, 6:22 pm, Subbu Allamaraju <su...@subbu.org> wrote:
>>=20
>>>>>>>>>>> ql.io-compi...@0.5.3 has the fix for nulls. For the escaped =
quote issue, I'm still waiting for a resolution/work-around from PEG.js.
>>=20
>>>>>>>>>>> Subbu
>>=20
>>>>>>>>>>> On Apr 9, 2012, at 10:43 AM, anandva wrote:
>>=20
>>>>>>>>>>>> Thanks for the response Subbu.
>>=20
>>>>>>>>>>>> i did bit more reading on features, i think for both issues =
i could
>>>>>>>>>>>> handle through MonkeyPatching, where i could write a local =
script to
>>>>>>>>>>>> transform values for the keys which has escape chars or =
null's.
>>=20
>>>>>>>>>>>> -Vivek.
>>=20
>>>>>>>>>>>> On Apr 9, 8:55 am, Subbu Allamaraju <su...@subbu.org> =
wrote:
>>>>>>>>>>>>> Both are due to some limitations/bugs in the underlying =
PEG.js parser generator. For the first case, the work-around is to use =
single quotes as
>>=20
>>>>>>>>>>>>> data =3D { "fname" : "fname","lname":'\"lname\"'};
>>=20
>>>>>>>>>>>>> For the second issue of null, I'll check in a work around =
today.
>>=20
>>>>>>>>>>>>> Subbu
>>=20
>>>>>>>>>>>>> On Apr 7, 2012, at 11:51 PM, anandva wrote:
>>=20
>>>>>>>>>>>>>> Hi,
>>=20
>>>>>>>>>>>>>> Hope this is normal behavior question and answered =
already.I got below
>>>>>>>>>>>>>> data from api as valid JSON, but getting error as missing =
encoding
>>>>>>>>>>>>>> while returning data.
>>>>>>>>>>>>>> 1. Is there any way i could encode data on api fetch?
>>=20
>>>>>>>>>>>>>> data =3D { "fname" : "fname","lname":"\"lname\""};
>>=20
>>>>>>>>>>>>>> return data;
>>=20
>>>>>>>>>>>>>> 2. if the returned data has null value for one of the =
data elements
>>>>>>>>>>>>>> that is also causing issue?
>>=20
>>>>>>>>>>>>>> data =3D { "fname" : "fname","lname":null};
>>=20
>>>>>>>>>>>>>> return data;
>>=20
>>>>>>>>>>>>>> data returned is a json representation of java object, i =
am exploring
>>>>>>>>>>>>>> to see we could transform based on needs for clients.
>>=20
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Vivek.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
