-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update fails (invalid signature) #12
Comments
That's a weird one. Also happened to me, then went away on its own. Could it be due to failed downloads, and we try to Otherwise, there are mentions of the unzip module failing if the archive contains files with "store"-level compression. We could try https://www.npmjs.com/package/unzip2. |
I get the same error. Is there a quickfix to get it working again? |
It should actually already be fixed in the master branch. Try pulling that If that doesn't work I've seriously overlooked something. On Mon, Apr 20, 2015, 00:26 Adrian Sieber notifications@github.com wrote:
|
…and why don't you publish it on npm? ^^ |
Good point, @rprieto let's update, the current release op npm is seriously broken 😄. |
I've got the same problem. Please, publish on npm. |
@rprieto publish 👍 |
Done, as |
~/P/_/project ❯❯❯ npm install -g tldr ⏎ ⬆
/Users/kud/.nvm/versions/node/v0.12.4/bin/tldr -> /Users/kud/.nvm/versions/node/v0.12.4/lib/node_modules/tldr/bin/tldr
tldr@1.0.1 /Users/kud/.nvm/versions/node/v0.12.4/lib/node_modules/tldr
├── commander@2.3.0
├── deep-extend@0.2.11
├── ms@0.6.2
├── rimraf@2.2.8
├── wrench@1.5.8
├── async@0.9.2
├── marked@0.3.3
├── colors@1.0.3
├── cpr@0.3.3 (graceful-fs@3.0.8)
├── unhtml@0.1.0 (quotemeta@0.0.0, html5-entities@0.5.1)
├── mkdirp@0.5.1 (minimist@0.0.8)
├── lodash@2.4.2
├── request@2.44.0 (caseless@0.6.0, aws-sign2@0.5.0, forever-agent@0.5.2, stringstream@0.0.4, oauth-sign@0.4.0, tunnel-agent@0.4.0, json-stringify-safe@5.0.1, qs@1.2.2, node-uuid@1.4.3, mime-types@1.0.2, form-data@0.1.4, bl@0.9.4, http-signature@0.10.1, tough-cookie@2.0.0, hawk@1.1.1)
└── unzip2@0.2.5 (setimmediate@1.0.2, pullstream@0.4.1, readable-stream@1.0.33, match-stream@0.0.2, fstream@0.1.31, binary@0.3.0)
~/P/_/project ❯❯❯ tldr ✱
15 Jun 16:37:26 - Usage: tldr <command>
~/P/_/project ❯❯❯ tldr open ⏎ ✱
Page not found
Try updating with "tldr --update", or submit a pull request to:
http://github.com/tldr-pages/tldr
~/P/_/project ❯❯❯ tldr --update ⏎ ✱
Updating...
Error: invalid signature: 0x97ad4b50
at /Users/kud/.nvm/versions/node/v0.12.4/lib/node_modules/tldr/node_modules/unzip2/lib/parse.js:63:13
at processImmediate [as _immediateCallback] (timers.js:358:17) normal? |
It isn't working for me either 😢 |
Ouch. Definitely looks like it's running the latest code with tldr --update
Updating...
Done The ZIP archive from GitHub looks valid, so I don't have any leads yet. curl -I --silent https://github.com/tldr-pages/tldr/archive/master.zip | grep Location
# Location: https://codeload.github.com/tldr-pages/tldr/zip/master
wget https://codeload.github.com/tldr-pages/tldr/zip/master
unzip -t master
# No errors detected in compressed data of master. |
Just came across this as well:
Adding info about my environment, in case it helps debugging/reproducing the problem:
Funny thing. I noticed I had still tldr v. 1.0.0, so I ran
(note the "Done" despite the error) Then I ran tldr --update again and this time it worked without a problem:
No idea what happened here, but hope it helps somehow. |
@waldyrious I guess upgrading node and npm first of all wouldn't be too bad ;-) |
@adius are the instructions here the recommended way to update nodejs in Ubuntu 12.04 (elementaryOS 0.2 Luna)? I mean, it feels a litthe hackish -- shouldn't
(rather than explicitly |
The ubuntu package manager is always a little behind. |
I understand about the official Ubuntu package manager, but as I said, I had previously installed using nodesource's ppa, which is why I expected |
Hmmm... I wonder if there is some kind of PATH issue going on here, specific to our own set ups? Attempting a pristine install of tldr several times, I had similar weird problems, e.g. invalid sig. attempting update, but also got a stream error (noted below). Then, after several --update tries (4 of them) - from different path locations - oddly got a similar, unexpected automagic fix. npm and node are globally installed, of course, so tldr --update failing in a subdir, but then finally working at "/" should be coincidence... hmmm... and then it worked in a subdir! OS: OSX (older version 10.7.5 [because Yosemite sux]). Successfully updated node.js, and npm a day ago : Installed tldr as instructed - and because I'm ironic - I tried /some/arbitrary/place $ tldr --version Tried again from / / $ tldr --update And then magically, it just worked fine - and with satisfactory irony: tldr |
Update from #19: as a temporary workaround, this seems to help: tldr --clear-cache
tldr --update |
…r-pages.github.io static site instead of Github API
Please update tldr-node-client to 1.1.0:
And then run pages update again
|
Just copying the issue from tldr-pages/tldr#263.
Related error:
A lot of people are getting them it seems, including a friend I introduced to the client. It may also be the cause of #11 because the cache got filled improperly.
The text was updated successfully, but these errors were encountered: