On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt <[email protected]> wrote:
> Alex, > > The version number here came from package.json so it should have been > updated by someone. > > I reinstalled from the link you provided with no problem. > But running the royale server:debug [1] command gives me the same errors > as before. > > I noticed that when running: royale new my-royale-app, only an app folder > is created with a src folder in it.In this src folder, there is a main.mxml > file. So no other files or folders whatsoever are created by the 'new' > command. > Yes, that is the expected behavior. Currently, we ship a very simple `Hello World` app with the royale-cli tool. We can make it fancier app once we iron out all the issues. > > This explains the error: > > Error: ENOENT: no such file or directory, open '/Volumes/Macintosh > HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html' > > Hmm, the path does not seem correct. it should be .../my-royale-app/bin/js-debug/index.html instead of what is shown here. It appears that you are running the royale serve:debug command from the .../my-royale-app/src directory instead of from the .../my-royale-app directory. Thanks, Om > -Dany > > [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli > > Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui <[email protected] > >: > > That's my windows machine that I used for 0.9.2. > > Where did it say 0.9.3? 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, "[email protected] on behalf of OmPrakash Muppirala" < > [email protected] on behalf of [email protected]> wrote: > > On Tue, May 1, 2018 at 1:36 PM, Alex Harui <[email protected]> > 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, "[email protected] on behalf of OmPrakash > > Muppirala" <[email protected] on behalf of [email protected]> wrote: > > > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui <[email protected]> > > 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/[email protected] 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" <[email protected]> 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 > > <[email protected] > > > <mailto:[email protected]>> 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% > 7Cfa7b1b5a7b34438794aed2c178decee1%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% > > 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%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% > 7Cfa7b1b5a7b34438794aed2c178decee1%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% > > 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%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" <[email protected] > > <mailto: > > > [email protected]>> 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 < > > > [email protected] <mailto:[email protected]>> 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 < > > [email protected] > > > <mailto:[email protected]>> 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/[email protected] > > > >>> 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 > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
