Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[OmPrakash Muppirala]

On Tue, May 1, 2018 at 11:16 PM, Alex Harui 
wrote:

> I think that's a bug in releasecandidate.xml.  When you run the release
> target, it calls the update.versions target before reminding you to run the
> release.npm target.  It did not occur to me that the publishing grabbed
> files other than the tar.gz (which should have the right version in its
> files).


It appears that the npm library needs this package.json file to be passed
during an installation.  I will try to remove it and try to publish.


>   So I suppose you could try running release.npm before update.versions.
>

If my above fix does not work, I will switch the order and see if that
fixes it.

Thanks,
Om


>
> HTH,
> -Alex
>
> On 5/1/18, 11:10 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"  wrote:
>
>  As per git history, this file was updated from 0.9.2 to 0.9.3 on
> 3/16/2018
> at around 10:40AM :
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%
> 2F2e6923440655c2c2314a9f3e2e1d91fa745cd6e2%23diff-
> 6515d4243f4018bb4527c9184823da7f=02%7C01%7Caharui%40adobe.com%
> 7Ca1f8ef5c36e84b2ce18508d5aff364ab%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636608382274076486=xcQE%
> 2BsDRTUvsyE8t3eUTPHRg9ojfQleqCVx7aP9vFCs%3D=0
>
> According to https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.npmjs.com%2Forg%2Fapache-royale=02%
> 7C01%7Caharui%40adobe.com%7Ca1f8ef5c36e84b2ce18508d5aff364ab%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608382274076486=%
> 2FCSPJkc%2B6CctGw4btT%2BoX5rUSS2CAq7aE36SNop0e0g%3D=0, the 0.9.3
> release was
> made on at around 11:00 AM on the same day.
>
> I am guessing that the npm publish script was run accidentally that
> caused
> a 0.9.3 release to be pushed.
>
> Is it possible that this can happen again? i.e. are some scripts
> getting
> called when they should not be?
>
> Thanks,
> Om
>
> On Tue, May 1, 2018 at 9:44 PM, Alex Harui 
> wrote:
>
> > OK, but what file would contain that string such that it shows up
> then?
> >
> > Thanks,
> > -Alex
> >
> > On 5/1/18, 9:32 PM, "OmPrakash Muppirala" 
> wrote:
> >
> > On Tue, May 1, 2018, 8:13 PM Alex Harui  >
> > wrote:
> >
> > > That's my windows machine that I used for 0.9.2.
> > >
> > > Where did it say 0.9.3?
> >
> >
> > It shows up after the npm install completes.
> >
> >
> > I'm trying to remember if I published the package to NPM or if
> you did.
> > > Maybe the scripts are running or were run after some versions
> got
> > updated
> > > in the repos.  I have not run a build on my windows machine
> since the
> > > release.
> >
> >
> > >
> > >
> > >
> > >
> > > -Alex
> > >
> > > On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala"
> > >  wrote:
> > >
> > > On Tue, May 1, 2018 at 1:36 PM, Alex Harui
> > 
> > > wrote:
> > >
> > > > Om,
> > > >
> > > > I got the warnings when we released 0.9.2 but it
> appeared to
> > leave a
> > > > functional SDK.  Now it is hanging for me and Dany.
> > > >
> > > > I don't think I've run a publish and I don't think the CI
> > server is
> > > > either, but you never know.  Try grabbing one of the
> SWCs.
> > Unzip it
> > > and
> > > > swfdump the library.swf.  There should be debugfile
> bytecodes
> > with
> > > paths to
> > > > the source that give us a clue.
> > > >
> > > >
> > > Good idea.  Here is what I see in swfdump:
> > >
> > > 2) + 0:1 debugfile
> > >
> > > "C:\temp\rc\royale-asjs\frameworks\projects\
> > Collections\src\main\royale;org\apache\royale\collections;
> > FlattenedList.as"
> > >
> > > Any idea whose machine this could have been?
> > >
> > > Thanks,
> > > Om
> > >
> > >
> > > > -Alex
> > > >
> > > > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of
> OmPrakash
> > > > Muppirala"  > bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> > > 
> > > > wrote:
> > > >
> > > > > Hi Dany,
> > > > >
> > > > > The link is 

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[Dany Dhondt]

Hi Alex,

package.json which is the default file npm picks up

-Dany



Op 2 mei 2018 om 06:45 uur uur schreef Alex Harui :

OK, but what file would contain that string such that it shows up then?

Thanks,
-Alex

On 5/1/18, 9:32 PM, "OmPrakash Muppirala"  wrote:

On Tue, May 1, 2018, 8:13 PM Alex Harui  wrote:


That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3?



It shows up after the npm install completes.


I'm trying to remember if I published the package to NPM or if you did.

Maybe the scripts are running or were run after some versions got updated
in the repos. I have not run a build on my windows machine since the
release.








-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
wrote:

> Om,
>
> I got the warnings when we released 0.9.2 but it appeared to leave a
> functional SDK. Now it is hanging for me and Dany.
>
> I don't think I've run a publish and I don't think the CI server is
> either, but you never know. Try grabbing one of the SWCs. Unzip it
and
> swfdump the library.swf. There should be debugfile bytecodes with
paths to
> the source that give us a clue.
>
>
Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile

"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om


> -Alex
>
> On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" 
wrote:
>
> On Tue, May 1, 2018 at 8:57 AM, Alex Harui

> wrote:
>
> > Hi Dany,
> >
> > The link is directly to a tar.gz built by our CI server. No
humans
> > involved, and no special packaging for NPM. NPM says it can
install
> any
> > tar.gz file. Try downloading the file at that link and using
Mac
> Finder to
> > expand it into a folder. For me it expands without errors.
This is
> why I
> > believe it is some incompatibility with NPM.
> >
> > If the tar.gz expands for you on Mac, you can try to "npm
install"
> the
> > folder. Running:
> >
> > sudo npm install -g 
> >
> > seemed to work for me.
> >
> > -Alex
> >
>
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
>
> Although, I notice that @apache-royale/royale-js@0.9.3 was
> installed. It
> should have installed 0.9.2. Did we publish 0.9.3 to npm by
mistake?
> Could that be related?
>
> Thanks,
> Om
>
>
> >
> > On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
> >
> > Hi Alex,
> >
> > I tried the direct link you provided: same result
(hundreds of
> > ‘invalid entry’ messages)
> >
> > My version of npm is 6.0.0
> >
> > downgrading to a lower npm version is not an option at this
> moment
> > because I’m on a production mac with crucial projects on it.
> >
> > Amids all the invalid entry messages, now and then is a
somewhat
> > longer message like
> >
> > WARN⸨ ░░░⸩ ⠸ extract:@apache-royale
/royale-js:
> verb
> > lock using /Users/ tar invalid entry
> >
> >
> >
> >
> > Is it Om that created this package? This might give him an
idea
> of
> > what’s going on?
> >
> > -Dany
> >
> >
> >
> > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
>  > > het volgende geschreven:
> > >
> > > Hmm. I'm getting that too on my Mac. It used to
complete
> anyway
> > and work, but now it appears to be hanging.
> > >
> > > The internet hints that it might have to do with the
version
> of NPM
> > used to create the package vs the NPM we are using to
install. Om,
> did
> > you create the packages for publishing to NPM? If so, what
version
> did you
> > use?
> > >
> > > On the other hand, just installing the nightly build also
> gives a
> > ton of those warnings but seems to complete and produce a
runnable
> compiler.
> > >
> > > sudo npm install -g
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608060969636900=sgZBuZoOmRwla%2Bti%2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D=0
.
> protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com
%7C00079fd32a194a4caf1b08d5af8bd09e%
>
7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%
> 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> > protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> > westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> > jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> > royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> >
7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> >

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[Alex Harui]

I think that's a bug in releasecandidate.xml.  When you run the release target, 
it calls the update.versions target before reminding you to run the release.npm 
target.  It did not occur to me that the publishing grabbed files other than 
the tar.gz (which should have the right version in its files).  So I suppose 
you could try running release.npm before update.versions.

HTH,
-Alex

On 5/1/18, 11:10 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" 
 wrote:

 As per git history, this file was updated from 0.9.2 to 0.9.3 on 3/16/2018
at around 10:40AM :

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F2e6923440655c2c2314a9f3e2e1d91fa745cd6e2%23diff-6515d4243f4018bb4527c9184823da7f=02%7C01%7Caharui%40adobe.com%7Ca1f8ef5c36e84b2ce18508d5aff364ab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608382274076486=xcQE%2BsDRTUvsyE8t3eUTPHRg9ojfQleqCVx7aP9vFCs%3D=0

According to 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Forg%2Fapache-royale=02%7C01%7Caharui%40adobe.com%7Ca1f8ef5c36e84b2ce18508d5aff364ab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608382274076486=%2FCSPJkc%2B6CctGw4btT%2BoX5rUSS2CAq7aE36SNop0e0g%3D=0,
 the 0.9.3 release was
made on at around 11:00 AM on the same day.

I am guessing that the npm publish script was run accidentally that caused
a 0.9.3 release to be pushed.

Is it possible that this can happen again? i.e. are some scripts getting
called when they should not be?

Thanks,
Om

On Tue, May 1, 2018 at 9:44 PM, Alex Harui  wrote:

> OK, but what file would contain that string such that it shows up then?
>
> Thanks,
> -Alex
>
> On 5/1/18, 9:32 PM, "OmPrakash Muppirala"  wrote:
>
> On Tue, May 1, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > That's my windows machine that I used for 0.9.2.
> >
> > Where did it say 0.9.3?
>
>
> It shows up after the npm install completes.
>
>
> I'm trying to remember if I published the package to NPM or if you 
did.
> > Maybe the scripts are running or were run after some versions got
> updated
> > in the repos.  I have not run a build on my windows machine since 
the
> > release.
>
>
> >
> >
> >
> >
> > -Alex
> >
> > On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"
> >  wrote:
> >
> > On Tue, May 1, 2018 at 1:36 PM, Alex Harui
> 
> > wrote:
> >
> > > Om,
> > >
> > > I got the warnings when we released 0.9.2 but it appeared to
> leave a
> > > functional SDK.  Now it is hanging for me and Dany.
> > >
> > > I don't think I've run a publish and I don't think the CI
> server is
> > > either, but you never know.  Try grabbing one of the SWCs.
> Unzip it
> > and
> > > swfdump the library.swf.  There should be debugfile bytecodes
> with
> > paths to
> > > the source that give us a clue.
> > >
> > >
> > Good idea.  Here is what I see in swfdump:
> >
> > 2) + 0:1 debugfile
> >
> > "C:\temp\rc\royale-asjs\frameworks\projects\
> Collections\src\main\royale;org\apache\royale\collections;
> FlattenedList.as"
> >
> > Any idea whose machine this could have been?
> >
> > Thanks,
> > Om
> >
> >
> > > -Alex
> > >
> > > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > > Muppirala"  bigosma...@gmail.com>
> > wrote:
> > >
> > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> > 
> > > wrote:
> > >
> > > > Hi Dany,
> > > >
> > > > The link is directly to a tar.gz built by our CI
> server.  No
> > humans
> > > > involved, and no special packaging for NPM.  NPM says it
> can
> > install
> > > any
> > > > tar.gz file.  Try downloading the file at that link and
> using
> > Mac
> > > Finder to
> > > > expand it into a folder.  For me it expands without
> errors.
> > This is
> > > why I
> > > > believe it is some incompatibility with NPM.
> > > >

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[OmPrakash Muppirala]

 As per git history, this file was updated from 0.9.2 to 0.9.3 on 3/16/2018
at around 10:40AM :
https://github.com/apache/royale-asjs/commit/2e6923440655c2c2314a9f3e2e1d91fa745cd6e2#diff-6515d4243f4018bb4527c9184823da7f

According to https://www.npmjs.com/org/apache-royale, the 0.9.3 release was
made on at around 11:00 AM on the same day.

I am guessing that the npm publish script was run accidentally that caused
a 0.9.3 release to be pushed.

Is it possible that this can happen again? i.e. are some scripts getting
called when they should not be?

Thanks,
Om

On Tue, May 1, 2018 at 9:44 PM, Alex Harui  wrote:

> OK, but what file would contain that string such that it shows up then?
>
> Thanks,
> -Alex
>
> On 5/1/18, 9:32 PM, "OmPrakash Muppirala"  wrote:
>
> On Tue, May 1, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > That's my windows machine that I used for 0.9.2.
> >
> > Where did it say 0.9.3?
>
>
> It shows up after the npm install completes.
>
>
> I'm trying to remember if I published the package to NPM or if you did.
> > Maybe the scripts are running or were run after some versions got
> updated
> > in the repos.  I have not run a build on my windows machine since the
> > release.
>
>
> >
> >
> >
> >
> > -Alex
> >
> > On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"
> >  wrote:
> >
> > On Tue, May 1, 2018 at 1:36 PM, Alex Harui
> 
> > wrote:
> >
> > > Om,
> > >
> > > I got the warnings when we released 0.9.2 but it appeared to
> leave a
> > > functional SDK.  Now it is hanging for me and Dany.
> > >
> > > I don't think I've run a publish and I don't think the CI
> server is
> > > either, but you never know.  Try grabbing one of the SWCs.
> Unzip it
> > and
> > > swfdump the library.swf.  There should be debugfile bytecodes
> with
> > paths to
> > > the source that give us a clue.
> > >
> > >
> > Good idea.  Here is what I see in swfdump:
> >
> > 2) + 0:1 debugfile
> >
> > "C:\temp\rc\royale-asjs\frameworks\projects\
> Collections\src\main\royale;org\apache\royale\collections;
> FlattenedList.as"
> >
> > Any idea whose machine this could have been?
> >
> > Thanks,
> > Om
> >
> >
> > > -Alex
> > >
> > > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > > Muppirala"  bigosma...@gmail.com>
> > wrote:
> > >
> > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> > 
> > > wrote:
> > >
> > > > Hi Dany,
> > > >
> > > > The link is directly to a tar.gz built by our CI
> server.  No
> > humans
> > > > involved, and no special packaging for NPM.  NPM says it
> can
> > install
> > > any
> > > > tar.gz file.  Try downloading the file at that link and
> using
> > Mac
> > > Finder to
> > > > expand it into a folder.  For me it expands without
> errors.
> > This is
> > > why I
> > > > believe it is some incompatibility with NPM.
> > > >
> > > > If the tar.gz expands for you on Mac, you can try to "npm
> > install"
> > > the
> > > > folder.  Running:
> > > >
> > > > sudo npm install -g 
> > > >
> > > > seemed to work for me.
> > > >
> > > > -Alex
> > > >
> > >
> > > I just tried
> > > npm install @apache-royale/royale-js -g
> > > on windwos and it installed just fine.
> > >
> > > Although, I notice that  @apache-royale/royale-js@0.9.3
> was
> > > installed.  It
> > > should have installed 0.9.2.  Did we publish 0.9.3 to npm
> by
> > mistake?
> > > Could that be related?
> > >
> > > Thanks,
> > > Om
> > >
> > >
> > > >
> > > > On 5/1/18, 1:51 AM, "Dany Dhondt" 
> wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > I tried the direct link you provided: same result
> > (hundreds of
> > > > ‘invalid entry’ messages)
> > > >
> > > > My version of npm is 6.0.0
> > > >
> > > > downgrading to a lower npm version is not an option
> at this
> > > moment
> > > > because I’m on a production mac with crucial projects on
> it.
> > > >
> > > >

NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[Alex Harui]

OK, but what file would contain that string such that it shows up then?

Thanks,
-Alex

On 5/1/18, 9:32 PM, "OmPrakash Muppirala"  wrote:

On Tue, May 1, 2018, 8:13 PM Alex Harui  wrote:

> That's my windows machine that I used for 0.9.2.
>
> Where did it say 0.9.3?


It shows up after the npm install completes.


I'm trying to remember if I published the package to NPM or if you did.
> Maybe the scripts are running or were run after some versions got updated
> in the repos.  I have not run a build on my windows machine since the
> release.


>
>
>
>
> -Alex
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
>  wrote:
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
> wrote:
>
> > Om,
> >
> > I got the warnings when we released 0.9.2 but it appeared to leave a
> > functional SDK.  Now it is hanging for me and Dany.
> >
> > I don't think I've run a publish and I don't think the CI server is
> > either, but you never know.  Try grabbing one of the SWCs.  Unzip it
> and
> > swfdump the library.swf.  There should be debugfile bytecodes with
> paths to
> > the source that give us a clue.
> >
> >
> Good idea.  Here is what I see in swfdump:
>
> 2) + 0:1 debugfile
>
> 
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"
>
> Any idea whose machine this could have been?
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala" 
> wrote:
> >
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> 
> > wrote:
> >
> > > Hi Dany,
> > >
> > > The link is directly to a tar.gz built by our CI server.  No
> humans
> > > involved, and no special packaging for NPM.  NPM says it can
> install
> > any
> > > tar.gz file.  Try downloading the file at that link and using
> Mac
> > Finder to
> > > expand it into a folder.  For me it expands without errors.
> This is
> > why I
> > > believe it is some incompatibility with NPM.
> > >
> > > If the tar.gz expands for you on Mac, you can try to "npm
> install"
> > the
> > > folder.  Running:
> > >
> > > sudo npm install -g 
> > >
> > > seemed to work for me.
> > >
> > > -Alex
> > >
> >
> > I just tried
> > npm install @apache-royale/royale-js -g
> > on windwos and it installed just fine.
> >
> > Although, I notice that  @apache-royale/royale-js@0.9.3 was
> > installed.  It
> > should have installed 0.9.2.  Did we publish 0.9.3 to npm by
> mistake?
> > Could that be related?
> >
> > Thanks,
> > Om
> >
> >
> > >
> > > On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
> > >
> > > Hi Alex,
> > >
> > > I tried the direct link you provided: same result
> (hundreds of
> > > ‘invalid entry’ messages)
> > >
> > > My version of npm is 6.0.0
> > >
> > > downgrading to a lower npm version is not an option at 
this
> > moment
> > > because I’m on a production mac with crucial projects on it.
> > >
> > > Amids all the invalid entry messages, now and then is a
> somewhat
> > > longer message like
> > >
> > > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale
> /royale-js:
> > verb
> > > lock using /Users/ tar invalid entry
> > >
> > >
> > >
> > >
> > > Is it Om that created this package? This might give him an
> idea
> > of
> > > what’s going on?
> > >
> > > -Dany
> > >
> > >
> > >
> > > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
> >  > > > het volgende geschreven:
> > > >
> > > > Hmm.  I'm getting that too on my Mac.  It used to
>