cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: Consistent lazy Load problems
Date Wed, 24 Jul 2013 23:42:24 GMT
Yes, it is actually filed as a separate issue:

https://issues.apache.org/jira/browse/CB-4325


I'm going to go through that code and make sure to clean (I.e. rm -rf) the
relevant folders / .tgz files if shit hits the fan

On 7/24/13 4:39 PM, "Wargo, John" <john.wargo@sap.com> wrote:

>Thanks. So you implemented the proxy fix, right?  Have you given any
>thought to how the CLI fails when this doesn't work?
>
>I suggested in my JIRA ticket that we need more information when the
>download/extraction of the www project and the platform project files
>fails. Right now you can't tell what/how it failed and the target folder
>gets created anyway which causes lazy load to think it already has its
>files when it actually doesn't.
>
>John M. Wargo
>SAP | Charlotte, NC | USA
>Office: +1 704.321.0265 | Mobile: +1 704.249.7476
>Email: john.wargo@sap.com
>Twitter: @johnwargo
>
>
>-----Original Message-----
>From: Filip Maj [mailto:fil@adobe.com]
>Sent: Wednesday, July 24, 2013 7:36 PM
>To: dev@cordova.apache.org
>Subject: Re: Consistent lazy Load problems
>
>If there are still issues feel free to reopen CB-4322, that notifies me
>directly and I can take a look
>
>On 7/24/13 4:34 PM, "Wargo, John" <john.wargo@sap.com> wrote:
>
>>Woohoo! I'll test tomorrow.
>>
>>John M. Wargo
>>SAP | Charlotte, NC | USA
>>Office: +1 704.321.0265 | Mobile: +1 704.249.7476
>>Email: john.wargo@sap.com
>>Twitter: @johnwargo
>>
>>-----Original Message-----
>>From: Filip Maj [mailto:fil@adobe.com]
>>Sent: Wednesday, July 24, 2013 6:56 PM
>>To: dev@cordova.apache.org
>>Subject: Re: Consistent lazy Load problems
>>
>>Fixed and pushed to npm as 3.0.1.
>>
>>On 7/24/13 2:19 PM, "Carlos Santana" <csantana23@gmail.com> wrote:
>>
>>>+1 on re-using already existing settings from npm and git.
>>>
>>>I would say we need to document this for folks that are behind proxy
>>>Not much just punt to git and npm docs about proxy setup.
>>>
>>>We have today:
>>>
>>>   1.
>>>
>>>   Download and install Node.js <http://nodejs.org/>. Following
>>>   installation, you should be able to invoke node or npm on your
>>>command
>>>   line.
>>>
>>>And that's it.
>>>We should add something along the lines of telling the user that both
>>>npm
>>>and git will be use as part of cordova cli functions, see the npm and
>>>git
>>>documentation for setting networking/proxy for more info.
>>>
>>>
>>>
>>>
>>>On Wed, Jul 24, 2013 at 4:41 PM, Wargo, John <john.wargo@sap.com> wrote:
>>>
>>>> Well, not my friends as much as my colleagues, but many, many of us
>>>>are
>>>> experiencing this. There was someone who wasn't a colleague of mine,
>>>>Jason
>>>> I think was his name, who complained about this a week or so ago as
>>>>well.
>>>> He logged a ticket on it as well.
>>>>
>>>> John M. Wargo
>>>> SAP | Charlotte, NC | USA
>>>> Office: +1 704.321.0265 | Mobile: +1 704.249.7476
>>>> Email: john.wargo@sap.com
>>>> Twitter: @johnwargo
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Filip Maj [mailto:fil@adobe.com]
>>>> Sent: Wednesday, July 24, 2013 4:15 PM
>>>> To: dev@cordova.apache.org
>>>> Subject: Re: Consistent lazy Load problems
>>>>
>>>> It's mind-boggling that this is only an issue for your circle of
>>>>friends,
>>>> John :)
>>>>
>>>> Anyways, the patch looks good, and I commented as much on JIRA but
>>>>will
>>>> mention it here too: I will integrate that patch as soon as I can get
>>>>a
>>>> CLA from your colleague who wrote it up.
>>>>
>>>> Appreciate your patience and help thus far!
>>>>
>>>> On 7/24/13 1:09 PM, "Wargo, John" <john.wargo@sap.com> wrote:
>>>>
>>>> >I'm not sure we need a separate environment variable when git and npm
>>>> >both already have their own proxy settings. A colleague of mine threw
>>>> >together some code for using the existing settings, seems to me that
>>>>this
>>>> >is the best way to go.  I posted his code to
>>>> >https://issues.apache.org/jira/browse/CB-4322.
>>>> >
>>>> >Still need to code the CLI to recover more gracefully when the lazy
>>>>load
>>>> >doesn't work. It also needs to identify more clearly what failed so
>>>>we
>>>> >can better troubleshoot it.
>>>> >
>>>> >Please let me know how I can help. I'm happy to test away on this
>>>>since
>>>> >this has been killing me for the last few weeks.
>>>> >
>>>> >John M. Wargo
>>>> >SAP | Charlotte, NC | USA
>>>> >Office: +1 704.321.0265 | Mobile: +1 704.249.7476
>>>> >Email: john.wargo@sap.com
>>>> >Twitter: @johnwargo
>>>> >
>>>> >-----Original Message-----
>>>> >From: Filip Maj [mailto:fil@adobe.com]
>>>> >Sent: Wednesday, July 24, 2013 2:24 PM
>>>> >To: dev@cordova.apache.org
>>>> >Subject: Re: Consistent lazy Load problems
>>>> >
>>>> >Thanks for bringing this up John.
>>>> >
>>>> >It's filed as CB-4322 and I will get to it as soon as I can.
>>>> >
>>>> >On 7/24/13 8:56 AM, "Carlos Santana" <csantana23@gmail.com> wrote:
>>>> >
>>>> >>Maybe putting proxy information some where
>>>> >> ~/.cordova/config.json
>>>> >>or npmrc
>>>> >>or enviroment variable `http_proxy`
>>>> >>
>>>> >>what about handling proxy authentication?
>>>> >>proxy = http://domain\\username:password@ip:port
>>>> >>or
>>>> >>proxy = http://username:password@ip:port
>>>> >>
>>>> >>reference:
>>>> >>
>>>> 
>>>>http://superuser.com/questions/347476/how-to-install-npm-behind-authent
>>>>i
>>>>c
>>>> >>a
>>>> >>tion-proxy-on-windows
>>>> >>
>>>> >>--Carlos
>>>> >>
>>>> >>
>>>> >>On Wed, Jul 24, 2013 at 11:16 AM, Wargo, John <john.wargo@sap.com>
>>>> wrote:
>>>> >>
>>>> >>> For weeks now I've been working with the CLI as it goes from
>>>>version to
>>>> >>> version and a few weeks back a problem arose where the lazy
load
>>>>of
>>>>the
>>>> >>> default www project fails or the lazy load of the Android or
iOS
>>>> >>>project.
>>>> >>> I've documented this repeatedly, my most recent JIRA ticket
is
>>>>here:
>>>> >>> https://issues.apache.org/jira/browse/CB-4322.
>>>> >>>
>>>> >>> What's happening is that the CLI is trying to download an archive
>>>>for
>>>> >>>some
>>>> >>> of the files it needs, but fails somehow. Using -d I can tell
a
>>>>little
>>>> >>>more
>>>> >>> about what is happening, but it is not always clear why its
>>>>failing.
>>>> >>>I'm
>>>> >>> not sure if the download is not happening or the extraction
of the
>>>> >>>download
>>>> >>> is failing, but the end result is that the CLI thinks it already
>>>>has
>>>> >>>the
>>>> >>> files it needs (when it actually doesn't) because the folder
it's
>>>> >>>looking
>>>> >>> for already exists.
>>>> >>>
>>>> >>> The CLI needs to report whether or not it is able to download
the
>>>>files
>>>> >>> and/or report that it's failing on the extraction - then act
>>>> >>>accordingly.
>>>> >>> Checking to see if the folder exists is not a valid check in
this
>>>>case
>>>> >>>as
>>>> >>> if the lazy load fails, the folder the CLI is checking for still
>>>>exists
>>>> >>>-
>>>> >>> which breaks the process and leaves the CLI in an unworkable
>>>>state.
>>>>The
>>>> >>> target folder should not be created (or it should be deleted
on
>>>>fail)
>>>> >>> unless the files have been extracted to it.
>>>> >>>
>>>> >>> This particular problem is affecting my entire team, there are
>>>>many
>>>>of
>>>> >>>us
>>>> >>> here being affected by this. I thought at first that this must
be
>>>>a
>>>> >>>proxy
>>>> >>> problem, but I've now gotten back to my home office and I'm
>>>> >>>experiencing
>>>> >>> the exact same problem on my Mac Mini which isn't using a proxy
>>>>and
>>>>has
>>>> >>>no
>>>> >>> proxy settings.  I've experienced this problem on our company
>>>>network
>>>> >>>as
>>>> >>> well as in two different hotel networks and now my home office
>>>>network.
>>>> >>> This is with three different computers on 4 different networks.
>>>> >>>
>>>> >>> On my MacBook and my windows laptop, I've configured npm and
git
>>>>with
>>>> >>>the
>>>> >>> appropriate proxy settings for my work network to no avail.
With
>>>>or
>>>> >>>without
>>>> >>> the settings, it fails.
>>>> >>>
>>>> >>> Two of my colleagues (in England and Germany) are experiencing
the
>>>>same
>>>> >>> problems; they're on different networks and have different proxy
>>>> >>>servers.
>>>> >>> They were able to get around this by manually forcing the proxy
>>>>setting
>>>> >>>in
>>>> >>> the lazyload.js file:
>>>> >>>
>>>> >>> request.get({uri:url, proxy:'http://some_proxy_server:8080'},
>>>> >>> function(err, req, body) { size = body.length; })
>>>> >>>
>>>> >>> I would prefer to not have to modify the code to make this work.
>>>> >>> Unfortunately, the end result is our developers are ready to
give
>>>>up on
>>>> >>>the
>>>> >>> CLI since we can't make it work reliably simply for creating
new
>>>> >>>projects
>>>> >>> or adding platforms to existing projects (both use lazy load).
>>>> >>>
>>>> >>> Is there a recommended fix for this? Anything I can do to help
>>>>document
>>>> >>> this better?
>>>> >>>
>>>> >>> John M. Wargo
>>>> >>> Twitter: @johnwargo
>>>> >>>
>>>> >>>
>>>> >>
>>>> >>
>>>> >>--
>>>> >>Carlos Santana
>>>> >><csantana23@gmail.com>
>>>> >
>>>>
>>>>
>>>
>>>
>>>-- 
>>>Carlos Santana
>>><csantana23@gmail.com>
>>
>


Mime
View raw message