Git Product home page Git Product logo

Comments (18)

ryyppy avatar ryyppy commented on May 22, 2024 2

I am totally with you! Maybe it would be a good idea to create a new issue, which will ask for HTTPS support, which doesn't require a configured SSH-Key configuration? I think this would solve many problems in the future. Not sure if the used library supports this? @jeffmo

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

Hmm, not sure if this subcommand is already in npm, but try the following:

flow-typed update-cache --debug

(EDIT: just checked, it's not yet available in 2.0.0-beta.5)

Maybe we get more information about the error then... I guess it's a git-config problem with github and not a direct problem with flow-typed itself...

from flow-typed.

tunerex avatar tunerex commented on May 22, 2024

+1. Having same problem here.

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

There is apparently some problem (at least usability wise), I will try to find some time on the weekend to look into that.

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

@MoOx Do you still have the problem? If so, the newest version on NPM includes the update-cache command I mentioned a while ago... could you run it and post the output? :-)

(because I couldn't find the issue in the code when I was checking)

from flow-typed.

MoOx avatar MoOx commented on May 22, 2024

Seems ok now. But wowww. 16min to install !

❯ npm install -g flow-typed

> [email protected] preinstall /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/.staging/nodegit-4f29389c
> node lifecycleScripts/preinstall

[nodegit] Running pre-install script
[nodegit] Configuring libssh2.
/Users/MoOx/.nvm/versions/node/v5.11.0/bin/flow-typed -> /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/dist/cli.js

> [email protected] install /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit
> node lifecycleScripts/install

[nodegit] Running install script
[nodegit] Success: "/Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit/build/Release/nodegit.node" is installed via remote
[nodegit] Completed installation successfully.

> [email protected] postinstall /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit
> node lifecycleScripts/postinstall

- [email protected] node_modules/flow-typed/node_modules/ansi
- [email protected] node_modules/flow-typed/node_modules/lodash._baseslice
- [email protected] node_modules/flow-typed/node_modules/lodash._basetostring
- [email protected] node_modules/flow-typed/node_modules/lodash.tostring
- [email protected] node_modules/flow-typed/node_modules/lodash.padstart
- [email protected] node_modules/flow-typed/node_modules/lodash.padend
- [email protected] node_modules/flow-typed/node_modules/lodash.pad
- [email protected] node_modules/flow-typed/node_modules/nodegit/node_modules/node-pre-gyp
- [email protected] node_modules/flow-typed/node_modules/tar-pack/node_modules/readable-stream
/Users/MoOx/.nvm/versions/node/v5.11.0/lib
└─┬ [email protected] 
  ├─┬ [email protected] 
  │ ├─┬ [email protected]
  │ │ └── [email protected] 
  │ ├── [email protected] 
  │ ├─┬ [email protected] 
  │ │ ├── [email protected] 
  │ │ ├─┬ [email protected] 
  │ │ │ └── [email protected] 
  │ │ ├─┬ [email protected] 
  │ │ │ └── [email protected] 
  │ │ ├─┬ [email protected]
  │ │ │ └── [email protected] 
  │ │ ├─┬ [email protected] 
  │ │ │ ├── [email protected] 
  │ │ │ ├─┬ [email protected] 
  │ │ │ │ ├── [email protected] 
  │ │ │ │ ├── [email protected] 
  │ │ │ │ ├── [email protected] 
  │ │ │ │ ├── [email protected] 
  │ │ │ │ └── [email protected] 
  │ │ │ └── [email protected] 
  │ │ ├─┬ [email protected] 
  │ │ │ ├── [email protected] 
  │ │ │ └── [email protected] 
  │ │ ├─┬ [email protected] 
  │ │ │ └─┬ [email protected] 
  │ │ │   └─┬ [email protected] 
  │ │ │     ├── [email protected] 
  │ │ │     └─┬ [email protected] 
  │ │ │       └── [email protected] 
  │ │ └─┬ [email protected] 
  │ │   └── [email protected] 
  │ └─┬ [email protected] 
  │   └── [email protected] 
  ├─┬ [email protected]
  │ └─┬ [email protected]
  │   └── [email protected] 
  ├── [email protected] 
  ├─┬ [email protected]
  │ └── [email protected] 
  └─┬ [email protected]
    └── [email protected] 


~/Sync/Development master* 16m 3s

from flow-typed.

jeffmo avatar jeffmo commented on May 22, 2024

Ugh, yea npm install is so slow :(

Would you mind opening an issue for install speed? (I'm on my phone and afraid I'll forget before I get back to my computer). I noticed this the other day and I think it's something we should dig into

Sent from my iPhone

On Jul 6, 2016, at 9:26 AM, Maxime Thirouin [email protected] wrote:

Seems ok now. But wowww. 16min to install !

❯ npm install -g flow-typed

[email protected] preinstall /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/.staging/nodegit-4f29389c
node lifecycleScripts/preinstall

[nodegit] Running pre-install script
[nodegit] Configuring libssh2.
/Users/MoOx/.nvm/versions/node/v5.11.0/bin/flow-typed -> /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/dist/cli.js

[email protected] install /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit
node lifecycleScripts/install

[nodegit] Running install script
[nodegit] Success: "/Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit/build/Release/nodegit.node" is installed via remote
[nodegit] Completed installation successfully.

[email protected] postinstall /Users/MoOx/.nvm/versions/node/v5.11.0/lib/node_modules/flow-typed/node_modules/nodegit
node lifecycleScripts/postinstall

~/Sync/Development master* 16m 3s

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from flow-typed.

jeffmo avatar jeffmo commented on May 22, 2024

Oh, haha -- I'd already filed an issue for this :p #107

from flow-typed.

jeffmo avatar jeffmo commented on May 22, 2024

Ok, so sounds like the OP issue is resolved with the latest release

from flow-typed.

tunerex avatar tunerex commented on May 22, 2024

Still having same issue on [email protected], [email protected], and [email protected]

flow-typed update-cache --debug
Updating flow-typed definitions...
 * flow-typed cache not found, fetching from GitHub...ERROR: Unable to clone the local cache repo.
Update failed: authentication required but no callback set
Error: authentication required but no callback set
    at Error (native)

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

I am 62% sure that you might not have configured your github cli / registered a public ssh key for your github account... did you do that?

from flow-typed.

rricard avatar rricard commented on May 22, 2024

@ryyppy - the issue is sometimes we may want to run flow-typed in an environment where the git cli is not configured (CI for instance).

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

@rricard I think you would be better off, if you would track your flow-typed folder in your git project, after you installed it. In that way, nobody using the project is actually reliant on the flow-typed cli tool.

At least, that is what we are doing in our production code right now ;-)

from flow-typed.

rricard avatar rricard commented on May 22, 2024

@ryyppy: I have found a workaround and I agree with that but I think it's worth reopening the issue to at least track it. You clearly state in the README that feedback on the cli is welcome: this is some feedback 😉

from flow-typed.

jamiebuilds avatar jamiebuilds commented on May 22, 2024

Can everything just fall back to downloading a zip file from GitHub? Just to keep things working 100% of the time?

from flow-typed.

jeffmo avatar jeffmo commented on May 22, 2024

I didn't realize github requires auth to simply clone a repo, but if so it would be good to understand if there's a way around this. If not, then some kind of periodic zipped release seems like a good fallback.

We should look into the auth thing and see if we can find the root of the issue first, though. Adding machinery to deal with non-git-repos for updating could get hairy since this system is fairly broadly based around the notion of github/history/PRs/etc.

from flow-typed.

ryyppy avatar ryyppy commented on May 22, 2024

@jeffmo we always had problems when we had a package.json pointing to a git+ssh:// reference... all our devs without a properly configured github keychain got auth error messages. As soon as we switched to the https:// clone urls everything worked.

I recently got errors as well when I tried to get my cache downloaded and I actually had to go into the ~/.flow-typed/repo directory and manually configure the remote master (which apparently was unknown?) ... node-git seem to make some troubles in various ways.

from flow-typed.

mithuns avatar mithuns commented on May 22, 2024

Still does not work and I just checked I have ssh setup on my windows device.

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----         2/4/2018  11:53 PM           1675 id_rsa
-a----         2/4/2018  11:53 PM            420 id_rsa.pub
-a----         7/6/2018  10:36 AM           3326 id_rsa1
-a----         7/6/2018  10:36 AM            747 id_rsa1.pub
-a----       11/13/2017  11:57 AM            792 known_hosts

This just hangs for hours

PS C:\Users\mithuns\git\electron-react-boilerplate> flow-typed update-cache --debug
Updating flow-typed definitions...
• flow-typed cache not found, fetching from GitHub...

So, I decided to follow the steps listed on readme.

PS C:\Users\mithuns\git\electron-react-boilerplate> yarn global add flow-typed
yarn global v1.12.3
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...

success Installed "[email protected]" with binaries:
      - flow-typed
Done in 6.81s.
PS C:\Users\mithuns\git\electron-react-boilerplate> yarn install
yarn install v1.12.3
$ node ./internals/scripts/CheckYarn.js
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
success Already up-to-date.
$ yarn flow-typed && electron-builder install-app-deps package.json && yarn build-dll && opencollective-postinstall
yarn run v1.12.3
$ rimraf flow-typed/npm && flow-typed install --overwrite || true
• Found 108 dependencies in package.json to install libdefs for. Searching...
• flow-typed cache not found, fetching from GitHub...

And still the same issue.
Whats the solution for this ? Sorry, if I am a bit late to this thread. seems like there was a identified solution for this.

from flow-typed.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.