angular-templates 1.0.9 does not install>

[maiardm]

Hi! I'm trying to install Meteor w/angular flavor, excluding blaze-templates was OK, but when i try to install angular templates, processing 'stalls' in loop like:

### H:\Radar>meteor add angular-templates
Extracting [email protected]... / (for ever).

System / Environment documentation:

OpSys: Win10 / 64 bits

H:\Radar>node -v
v6.7.0

H:\Radar>npm -v
3.10.8

H:\Radar>meteor -v
[[[[[ ~\H\Radar ]]]]]

=> Started proxy.
=> Started MongoDB.
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]
Local package version is up-to-date: [email protected]_1
Local package version is up-to-date: [email protected]
Doing HTTP request: POST
https://www.meteor.com/oauth2/authorize?...
Doing HTTP request: GET
https://activity.meteor.com/_oauth/meteor-developer?...
=> Started your app.

=> App running at: ...
Type Control-C twice to stop.

[maiardm]

I tried as Normal User and also as Administrator.

Tried too, to install version 1.0.7 from angular-templates with same result.

The problem seems to be in meteor add function (perhaps in update too).

[maiardm]

Hi! I did a new try:

I uninstalled and reinstalled Meteor (obviously running as Administrator).

Then, again following Meteor Tutorial steps for simple-todos app (but changing the app name to "radar", and home-drive to H:), this time i got a different error:

after submitting the steps:

---

H:
meteor create radar

cd radar
meteor npm install
meteor

meteor remove blaze-html-templates

meteor add angular-templates

---

This time i got:

H:\radar>meteor add angular-templates

events.js:141
throw er; // Unhandled 'error' event
^

Error: write EOF
at exports.errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:785:14)

[Urigo]

@maiardm why did you close this? did it work for you?

[maiardm]

Hi Mr Urigo !

Sorry! I didn´t wanted to close it.
I don´t even know how to close an item.
Perhaps i've done something wrong, but it wasn't intentional.
Can you reopen it ? Or must i open a new (equal) one?
Again sorry by my newbie mistake.
And thanks for your care.

[maiardm]

Now I know what i've done (I hit "Close issue").
But i wanted only to close my comment (not the topic).
It will not happen again.

[maiardm]

By the way ...
Is there something i can do to help on debugging / solving this problem ? If so, i'm at your service.
Thank You.

[DAB0mB]

@maiardm What happens if you try to run an older version of Meteor? Does it work?

[maiardm]

@
Tried too, to install version 1.0.7 from angular-templates with same result.

The problem seems to be in meteor add function (perhaps in update too).

[maiardm]

@DAB0mB

Tried too, to install version 1.0.7 from angular-templates with same result.

The problem seems to be in meteor add function (perhaps in update too).

[DAB0mB]

@maiardm I can't seem to reproduce this problem I will try to help you anyway and tell me which method worked for you. It seems like you have problems extracting the package. Try to follow the solution in the following issue:

meteor/meteor#7689

Meteor uses tar.exe to extract its packages and this guy had a very old version of it. Try to uninstall it or install a newer version of it.

[maiardm]

@DAB0mB You are correct ! I have/had an old version of tar.exe on my path:

 Pasta de C:\msys\bin

21/04/2010  00:44           308.736 tar.exe     (this one was on the active path)
               1 arquivo(s)        308.736 bytes

 Pasta de C:\Tesseract

31/08/2016  10:31           352.256 tar.exe    (this was not in use, but available in another directory)
               1 arquivo(s)        352.256 bytes

I "replaced" the first one by second an tried again (all over).

This time it was (if i could say) worse, in the sense that the install processing stalled at a point BEFORE the preceding ones:

C:\>meteor create teste
   Extracting [email protected]...  -   (endless loop here).

Since i'm now using a much newer version of "tar.exe" this was a big surprise for me.

Is there some way of start a processing trace or something like that, to register / list some information an flow of processing steps ?

Something like that that could be very useful to help debug this problem.

[maiardm]

Well, i searched a bit more and found an old gzip.exe too, replacing it solved this last problem and send me back to stalling on:

C:\test5>meteor add angular-templates
Extracting [email protected]... / (for ever).

So, we are back at the first step.

[maiardm]

Hi! report from my last try:

1. Reinstalled W10

2. Installed last version of MSys / MinGW found af Source Forge:
   mingw-msys-core-6.1.0-x86

3. Tried again with same results.

I´m sure that now the last versions of each program from MSys / MinGW is at use, but the problem still occurs.

Does somebody has some idea for any new test ?

[maiardm]

Hi Friends,

is there some other way to add angular-templates to meteor environment?

if so, please, where can i find some documentation about that ?

i'm needing to start a small web project, and want(ed) to develop it under meteor/angular/... stack.

but this simple (an very basic) problem, is getting away my best hopes on these packages.

[Urigo]

just to make sure, is there anyone else who experiences this issue?

[maiardm]

@Urigo This one seems to me same problem:

[(https://forums.meteor.com/t/unable-to-add-angular-tempates/30142)]

I registered my case there first and only after some time registered here too.

[maiardm]

New adventures on installing meteor:

i tried to install meteor on two other cpus (with exactly the same results).

One of them (a desktop), is running W10-Home/32Bits

The other is a notebook, running W10-Home/64Bits

Nothing changed, the install process stalls at the same point, at

C:\test5>meteor add angular-templates
Extracting [email protected]... / (for ever).

So, i'm now absolutely sure that meteor install function(s) have a problem.

[maiardm]

Hi!

The install loop of node/meteor install process occurs on the first instance of tar.exe (PID 8456): node´s direct child.

During loop, i ended manually, first gzip.exe (PID 2624) and then the second instance of tar.exe (PID 8576), but the message "Extracting...." still remained showing (blinking).

Only when I killed the first instance of tar.exe (PID 8456) the exibition of loop messages stopped. Then occured an exception (as expected), on node processing.

[maiardm]

Hi! good news ! ... (?)

i tried to install older versions from angular-templates package, in a backward search, and finally, at 1.0.3 it worked !!!

C:\test1>meteor add angular-templates@=1.0.3

Changes to your project's package version selections:

angular-templates          added, version 1.0.3
angular-templates-runtime  added, version 0.0.1

angular-templates: Compile angular templates into the template cache

So the problem (for me), started at 1.0.5 and exists until now.

But i'm now very glad because i got to confirm without any questions: the problem is outside, not in my cpus / oses / envs and so.

Well, lets start to work with 1.0.3 and wait for this problem's solution.

[maiardm]

It doesn't works !

Running [email protected] with tutorial code adjusted to 1.0.9 doesn't works.

All i get is a nice blank page on browser.

No errors, no warning messages on either side, just a blank page on browser.

So ... i'm back to 1.0.9 install problem.

[DAB0mB]

@maiardm Unfortunately I can't seem to reproduce the issue, you can contact me in the email address listed in my Github account and we can do a video chat where you can show me the issue. Hopefully it'll help :-)

[maiardm]

@DAB0mB Perhaps i got a light at the end of this dark tunnel !

I removed / reinstalled node (7.0.0 now), and meteor.

By chance i tried to install meteor without admin privileges. Then the meteor install process tried to create/install modules on a directory with my OLD userid (i reinstalled windows a few days ago), not under the actual userid.

My old userid WAS "Ricardo Maia" (with a space between names), and my present userid IS "RicardoMaia" (without space).

Well, since i didn't copy anything from my previous system (W10 was installed on the same HD and it was formatted with full format option), and also didn't create any other user, only "RicardoMaia", FROM WHERE my old user name is coming? Does Node / Meteor download sites stores this information anywhere?

Well, i runned Meteor install steps again (now with Admin privileges), and at this time the "new" dir: "Ricardo Maia" was created (???), under C:\Users (only a work dir, not a real user).

I copied then (by hand) the AppData subdir created under "Ricardo Maia" to "RicardoMaia" overlapping any existent files.

After this when i tried to install angular-templates, IT WORKED !!

C:\test>meteor add angular-templates

Changes to your project's package version selections:

angular-templates           added, version 1.0.9
caching-compiler            added, version 1.0.6
urigo:static-html-compiler  added, version 0.1.8


angular-templates: Compile angular templates into the template cache

Now i got some new questions:

1. FROM WHERE my old userid is coming?

2. I had angular-templates installation problems BEFORE reinstalling W10. So the userid change may not be this problem originator. What is/was the real origin of my problem?

3. Did Node 7.0.0 corrected the install problem ?

4. How / where can i correct the wrong userid? What must i do ?

[maiardm]

Let me tell one more thing:

When I was "Ricardo Maia" at my former W10 installation, i remember that i saw a "paralel" directory under C:\Users

It was "Ricardo%Maia". At that time i didn't understand what it was and from where it did came. Back then i didn't care about that. But now it is very clear: something (Node/Meteor install process) has created it (instead of using "Ricardo Maia").

This now explains (to me) why i got problems since my first installation tries: The target directory (and subs), for update modules download / expanded was not the real one, it should be "Ricardo Maia" at the first case but Node/Meteor install process was creating and "updating": "Ricardo%Maia". And after my win reinstall the (wrong) target was been "Ricardo Maia" instead of "RicardoMaia" how it should be.

So it seems that Node/Meteor installation process is not handling acurately userids with space character(s) inside, (this is perhaps the same with other special characters too), probably due to html special chars handling.

Next i'll run some tests on Meteor installation under "unconventional" userids, to see what happens.

[Urigo]

I hope you ended up solving your problem...

[GrandNewbien]

Would you mind explaining how you solved your problem more in-depth? I've been having this same problem for quite some time now, and feel it's the same issue.