On Tue, May 1, 2018 at 11:16 PM, Alex Harui <aha...@adobe.com.invalid> 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" <omup...@gmail.com on behalf of bigosma...@gmail.com> 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&data=02%7C01%7Caharui%40adobe.com% > 7Ca1f8ef5c36e84b2ce18508d5aff364ab%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C636608382274076486&sdata=xcQE% > 2BsDRTUvsyE8t3eUTPHRg9ojfQleqCVx7aP9vFCs%3D&reserved=0 > > According to https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.npmjs.com%2Forg%2Fapache-royale&data=02% > 7C01%7Caharui%40adobe.com%7Ca1f8ef5c36e84b2ce18508d5aff364ab% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608382274076486&sdata=% > 2FCSPJkc%2B6CctGw4btT%2BoX5rUSS2CAq7aE36SNop0e0g%3D&reserved=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 <aha...@adobe.com.invalid> > 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" <bigosma...@gmail.com> > wrote: > > > > On Tue, May 1, 2018, 8:13 PM Alex Harui <aha...@adobe.com.invalid > > > > 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" > > > <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > > > > > > On Tue, May 1, 2018 at 1:36 PM, Alex Harui > > <aha...@adobe.com.invalid> > > > 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: > > > > > > 00002) + 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" <omup...@gmail.com on behalf of > > bigosma...@gmail.com> > > > wrote: > > > > > > > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui > > > <aha...@adobe.com.invalid> > > > > 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 <path-to-folder> > > > > > > > > > > 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" < > archeme...@mac.com> > > 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 > > > > <aha...@adobe.com.INVALID > > > > > <mailto:aha...@adobe.com.INVALID>> 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&data=02%7C01%7Caharui%40adobe.com% > > 7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178de > > cee1%7C0%7C0%7C636608060969636900&sdata=sgZBuZoOmRwla%2Bti% > > 2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D&reserved=0 > > > . > > > > protection.outlook.com/?url= > https%3A%2F%2Fna01.safelinks& > > > > data=02%7C01%7Caharui%40adobe.com > > > %7C00079fd32a194a4caf1b08d5af8bd09e% > > > > > > > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > > 7C636607937396983186&sdata=D% > > > > 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R4 > 3uCdchzXoECD0%3D&reserved=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&data=02%7C01%7Caharui% > > 40adobe.com% > > > > > > > > 7C0c405d2ff9134638451608d5af40c2f1% > 7Cfa7b1b5a7b34438794aed2c178de > > > > > > > > cee1%7C0%7C0%7C636607615050264364&sdata= > zKrYmme3fourKgDPSyULPEiiR5% > > > > > 2FfXBUXmGQ49qdY0aM%3D&reserved=0 < > > > https://na01.safelinks.protection.outlook.com/?url= > > https%3A%2F%2Fna01.safelinks&data=02%7C01%7Caharui%40adobe.com% > > 7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178de > > cee1%7C0%7C0%7C636608060969636900&sdata=sgZBuZoOmRwla%2Bti% > > 2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D&reserved=0 > > > . > > > > protection.outlook.com/?url= > https%3A%2F%2Fna01.safelinks& > > > > data=02%7C01%7Caharui%40adobe.com > > > %7C00079fd32a194a4caf1b08d5af8bd09e% > > > > > > > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > > 7C636607937396983186&sdata=D% > > > > 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R4 > 3uCdchzXoECD0%3D&reserved=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&data=02%7C01%7Caharui% > > 40adobe.com% > > > > > > > > 7C0c405d2ff9134638451608d5af40c2f1% > 7Cfa7b1b5a7b34438794aed2c178de > > > > > > > > cee1%7C0%7C0%7C636607615050264364&sdata= > zKrYmme3fourKgDPSyULPEiiR5% > > > > > 2FfXBUXmGQ49qdY0aM%3D&reserved=0> > > > > > > > > > > > > I haven't tried downgrading or upgrading my > > version of > > > NPM > > > > (5.6). > > > > > Dany which version are you running? Can you try > > different > > > versions > > > > of NPM? > > > > > > > > > > > > HTH, > > > > > > -Alex > > > > > > > > > > > > On 4/30/18, 1:11 AM, "Dany Dhondt" < > > archeme...@mac.com > > > > <mailto: > > > > > archeme...@mac.com>> wrote: > > > > > > > > > > > > Hi Om, > > > > > > > > > > > > I did that! > > > > > > > > > > > > In the mean time I tried all sorts of > things: > > > > > > install 0.9.1 instead of 0.9.3 > > > > > > reinstalled npm > > > > > > > > > > > > nothing works > > > > > > > > > > > > -Dany > > > > > > > > > > > > > > > > > >> Op 30 apr. 2018, om 09:59 heeft OmPrakash > > Muppirala < > > > > > bigosma...@gmail.com <mailto:bigosma...@gmail.com>> > het > > > volgende > > > > > geschreven: > > > > > >> > > > > > >> Dany, > > > > > >> > > > > > >> I haven't tested this on a Mac. I am told > that > > Mac > > > users > > > > need to > > > > > use "sudo > > > > > >> install npm <package-name> " depending on > how they > > > installed > > > > npm. > > > > > Perhaps > > > > > >> you can try that out? > > > > > >> > > > > > >> Thanks, > > > > > >> Om > > > > > >> > > > > > >> On Mon, Apr 30, 2018 at 12:54 AM, Dany > Dhondt < > > > > archeme...@mac.com > > > > > <mailto:archeme...@mac.com>> wrote: > > > > > >> > > > > > >>> Hi Om, > > > > > >>> > > > > > >>> Thanks for pointing that out. > > > > > >>> > > > > > >>> I’ll have a go with that scenario. > > > > > >>> > > > > > >>> 1. (re) installing royale > > > > > >>> npm install @apache-royale/royale-js -g > > > > > >>> WARN tar invalid entry > extract:@apache-royale > > > /royale-js: > > > > verb > > > > > lock using > > > > > >>> /Users/dany/.npm/_locks/ > > staging-3a08f0df5026584d.lock > > > for > > > > > >>> /usr/local/lib/node_modules/.staging > > > > > >>> WARN tar invalid entry > > > > > >>> > > > > > >>> Then hundreds of ‘invalid entry’ lines in > the > > terminal. > > > > > >>> > > > > > >>> And finally > > > > > >>> > > > > > >>> … > > > > > >>> > > > > > >>> WARN tar invalid entry > > > > > >>> /usr/local/bin/asjscompc -> > > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > royale-asjs/js/bin/ > > asjscompcnpm > > > > > >>> /usr/local/bin/asjsc -> > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > > royale-asjs/js/bin/asjscnpm > > > > > >>> /usr/local/bin/compc -> > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > > royale-asjs/js/bin/compcnpm > > > > > >>> /usr/local/bin/externc -> > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > > royale-asjs/js/bin/externcnpm > > > > > >>> /usr/local/bin/asnodec -> > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > > royale-asjs/js/bin/asnodecnpm > > > > > >>> /usr/local/bin/mxmlc -> > > /usr/local/lib/node_modules/@ > > > > > >>> apache-royale/royale-js/ > > royale-asjs/js/bin/mxmlcnpm > > > > > >>> + @apache-royale/royale-js@0.9.3 > > > > > >>> updated 1 package in 17.395s > > > > > >>> > > > > > >>> > > > > > >>> What are those invalid entries?? > > > > > >>> > > > > > >>> 2. install cli tool > > > > > >>> > > > > > >>> npm install @apache-royale/cli@alpha -g > > > > > >>> no problem here > > > > > >>> > > > > > >>> 3. create royale app > > > > > >>> > > > > > >>> royale new helloWorld > > > > > >>> cd helloWorld > > > > > >>> > > > > > >>>>> no problem > > > > > >>> > > > > > >>> 4. running the app > > > > > >>> > > > > > >>> royale serve:debug > > > > > >>> > > > > > >>> Didn’t work: > > > > > >>> > > > > > >>> helloWorld dany$ > royale serve:debug > > > > > >>> Compiling... > > > > > >>> WARNING: An illegal reflective access > operation > > has > > > occurred > > > > > >>> WARNING: Illegal reflective access by > > > com.google.common.base. > > > > > internal.Finalizer > > > > > >>> > > > (file:/usr/local/lib/node_modules/@apache-royale/royale- > > > > > >>> js/royale-asjs/js/lib/guava.jar) to field > > > java.lang.Thread. > > > > > >>> inheritableThreadLocals > > > > > >>> WARNING: Please consider reporting this to > the > > > maintainers of > > > > > >>> com.google.common.base.internal.Finalizer > > > > > >>> WARNING: Use --illegal-access=warn to > enable > > warnings > > > of > > > > further > > > > > illegal > > > > > >>> reflective access operations > > > > > >>> WARNING: All illegal access operations > will be > > denied > > > in a > > > > future > > > > > release > > > > > >>> Error: unable to open > 'HD/Documents/ARCHEMEDIA/ > > > > > ROYALE/helloWorld/src/Main. > > > > > >>> mxml'. > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> Command failed: mxmlc /Volumes/Macintosh > > > > HD/Documents/ARCHEMEDIA/ > > > > > >>> ROYALE/helloWorld/src/Main.mxml > -debug=true > > > > > >>> WARNING: An illegal reflective access > operation > > has > > > occurred > > > > > >>> WARNING: Illegal reflective access by > > > com.google.common.base. > > > > > internal.Finalizer > > > > > >>> > > > (file:/usr/local/lib/node_modules/@apache-royale/royale- > > > > > >>> js/royale-asjs/js/lib/guava.jar) to field > > > java.lang.Thread. > > > > > >>> inheritableThreadLocals > > > > > >>> WARNING: Please consider reporting this to > the > > > maintainers of > > > > > >>> com.google.common.base.internal.Finalizer > > > > > >>> WARNING: Use --illegal-access=warn to > enable > > warnings > > > of > > > > further > > > > > illegal > > > > > >>> reflective access operations > > > > > >>> WARNING: All illegal access operations > will be > > denied > > > in a > > > > future > > > > > release > > > > > >>> Error: unable to open > 'HD/Documents/ARCHEMEDIA/ > > > > > ROYALE/helloWorld/src/Main. > > > > > >>> mxml'. > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> fs.js:646 > > > > > >>> return binding.open(pathModule._ > makeLong(path), > > > > > stringToFlags(flags), > > > > > >>> mode); > > > > > >>> ^ > > > > > >>> > > > > > >>> Error: ENOENT: no such file or directory, > open > > > > '/Volumes/Macintosh > > > > > >>> HD/Documents/ARCHEMEDIA/ > > ROYALE/helloWorld/bin/js- > > > > debug/index.html' > > > > > >>> at Object.fs.openSync (fs.js:646:18) > > > > > >>> at Object.fs.readFileSync (fs.js:551:33) > > > > > >>> at updateIndex > (/usr/local/lib/node_modules/@ > > > > > >>> apache-royale/cli/index.js:125:24) > > > > > >>> at compileDebug > (/usr/local/lib/node_modules/@ > > > > > >>> apache-royale/cli/index.js:106:9) > > > > > >>> at serveDebug > (/usr/local/lib/node_modules/@ > > > > > >>> apache-royale/cli/index.js:88:5) > > > > > >>> at Object.<anonymous> > > (/usr/local/lib/node_modules/@ > > > > > >>> apache-royale/cli/index.js:59:13) > > > > > >>> at Module._compile (module.js:652:30) > > > > > >>> at Object.Module._extensions..js > > (module.js:663:10) > > > > > >>> at Module.load (module.js:565:32) > > > > > >>> at tryModuleLoad (module.js:505:12) > > > > > >>> helloWorld dany$ > > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> Any ideas? > > > > > >>> > > > > > >>> -Dany > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
