Yarn install Invalid protocol error #1625

lambertkuang · 2016-11-02T23:34:23Z

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Running yarn on a new system gives me this error:

Error: Invalid protocol: git+https:
      at Request.init (/usr/local/lib/node_modules/yarn/node_modules/request/request.js:459:31)
      at new Request (/usr/local/lib/node_modules/yarn/node_modules/request/request.js:128:8)
      at request (/usr/local/lib/node_modules/yarn/node_modules/request/index.js:54:10)
      at RequestManager.execute (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:327:17)
      at RequestManager.shiftQueue (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:353:10)
      at Promise (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:150:12)
      at RequestManager.request (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:148:21)
      at NpmRegistry.request (/usr/local/lib/node_modules/yarn/lib/registries/npm-registry.js:97:32)
      at TarballFetcher.fetchFromExternal (/usr/local/lib/node_modules/yarn/lib/fetchers/tarball-fetcher.js:176:21)
      at TarballFetcher._fetch (/usr/local/lib/node_modules/yarn/lib/fetchers/tarball-fetcher.js:218:19)

If the current behavior is a bug, please provide the steps to reproduce.
Running yarn on a new system
What is the expected behavior?
Install successfully
Please mention your node.js, yarn and operating system version.
Node: 6.9.1
Yarn: 0.16.0
OS: CentOS 6.8

The text was updated successfully, but these errors were encountered:

sebmck · 2016-11-03T11:05:40Z

Need more information to reproduce this like the package.json you're using.

lambertkuang · 2016-11-03T15:43:26Z

{
  "name": "web",
  "version": "1.0.0",
  "description": "",
  "main": "app.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node-dev app.js"
  },
  "repository": {
    "type": "git",
    "url": ""
  },
  "author": "",
  "bugs": {
    "url": ""
  },
  "homepage": "",
  "private": true,
  "dependencies": {
    "co": "^4.6.0",
    "cookie-parser": "^1.4.3",
    "lodash": "^4.15.0",
    "lokka": "^1.7.0",
    "lokka-transport-http": "^1.6.1",
    "moment": "^2.15.1",
    "parse-cache-control": "^1.0.1",
    "request": "^2.74.0",
    "sand": "^1.7.2",
    "sand-clients": "^1.0.0",
    "sand-eventsd": "1.2.0",
    "sand-grain": "^1.2.1",
    "sand-graphql": "1.1.0",
    "sand-http": "^2.8.4",
    "sand-mysql": "^2.2.2"
  }
}

What's weird is that it worked when I ran yarn in another project on the same machine, then came back and ran yarn again on this project and it worked. It's happened twice, both on fresh GCE instances.

KidkArolis · 2016-11-20T12:54:39Z

I couldn't reproduce, works fine with yarn@0.17.6. @lambertkuang can you try again with the latest yarn? I appreciate you're saying it only doesn't work the first time you run it. If you can still reproduce that, I will get a CentOS VM and try as well.

nadia318 · 2016-11-25T10:15:56Z

It still reproduce for me.

Error: Invalid protocol: git: at Request.init (/usr/local/lib/node_modules/yarn/node_modules/request/request.js:459:31) at new Request (/usr/local/lib/node_modules/yarn/node_modules/request/request.js:128:8) at request (/usr/local/lib/node_modules/yarn/node_modules/request/index.js:54:10) at RequestManager.execute (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:348:17) at RequestManager.shiftQueue (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:374:10) at data (/usr/local/lib/node_modules/yarn/lib/util/request-manager.js:264:12) at Extract.extractorStream.pipe.on.on (/usr/local/lib/node_modules/yarn/lib/fetchers/tarball-fetcher.js:128:9) at emitNone (events.js:91:20) at Extract.emit (events.js:185:7) at DirWriter.<anonymous> (/usr/local/lib/node_modules/yarn/node_modules/tar/lib/extract.js:82:8)

Node: 6.9.1
Yarn: 0.17.8
linux x64

ianmurrays · 2016-12-06T20:21:09Z

I also get this same error, on a debian jessie docker container. Doesn't happen on macOS El Capitan for some reason.

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

Error: Invalid protocol: git+https:
    at Request.init (/root/.yarn/node_modules/request/request.js:459:31)
    at new Request (/root/.yarn/node_modules/request/request.js:128:8)
    at request (/root/.yarn/node_modules/request/index.js:54:10)
    at RequestManager.execute (/root/.yarn/lib-legacy/util/request-manager.js:362:17)
    at RequestManager.shiftQueue (/root/.yarn/lib-legacy/util/request-manager.js:389:10)
    at /root/.yarn/lib-legacy/util/request-manager.js:276:12
    at Extract.<anonymous> (/root/.yarn/lib-legacy/fetchers/tarball-fetcher.js:146:9)
    at emitNone (events.js:72:20)
    at Extract.emit (events.js:166:7)
    at DirWriter.<anonymous> (/root/.yarn/node_modules/tar/lib/extract.js:82:8)

yarn 0.18.0

ryanwe · 2016-12-15T13:33:25Z

In case this helps anyone, I ran into this when testing a migration from npm to yarn and running CI on travis. I was able to work around the problem by changing our dependency references in package.json from the form
"dependency-name": "Company/dependency-name",
to
"dependency-name": "git://github.com/Company/dependency-name",

node 6.3.0
yarn 0.17.10

ianmurrays · 2016-12-15T15:56:26Z

I guess the problem is more troublesome when one does not have control over that, say, when a package has a dependency written as "dependency-name": "Company/dependency-name"

shkfnly · 2016-12-15T19:46:22Z

I found a temporary fix. Delete the yarn.lock file when trying to run on a new machine. Yarn will generate another one.

ianmurrays · 2016-12-15T19:54:29Z

@shkfnly kinda defeats the purpose though. The idea of using a lock file is to make sure you always have the same dependencies ☹️

cyprusglobe · 2016-12-16T04:00:30Z

I'm noticing this as well

drewpc · 2017-01-21T23:40:13Z

Same issue. Running yarn 0.19.1 and node 7.4.0 on macOS and Ubuntu Linux. Deleting yarn.lock is not an acceptable solution. Error message:

yarn install v0.19.1
[1/5] Resolving packages...
[2/5] Fetching packages...
error An unexpected error occurred: "Invalid protocol: git:".
info If you think this is a bug, please open a bug report with the information provided in "/opt/atlassian/pipelines/agent/build/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

yarn.lock.txt

pnispel · 2017-02-08T06:44:38Z

finally got repro steps for this:

empty dependencies in package.json

yarn cache clean
yarn add grunt-jsdoc@0.5.7
yarn add jsdoc@3.4.3
rm -rf node_modules/
yarn cache clean
yarn

that produces a yarn.lock entry like

taffydb@2.6.2, "taffydb@git+https://github.com/hegemonic/taffydb.git":
  version "2.6.2"
  resolved "git+https://github.com/hegemonic/taffydb.git#e41b5e179e197bb85c5fb887b707672b1e5ca079"

which for whatever reason produces the error.
adding "taffydb": "2.6.2" to our package.json gives the working entry of

taffydb@2.6.2:
  version "2.6.2"
  resolved "https://registry.yarnpkg.com/taffydb/-/taffydb-2.6.2.tgz#7cbcb64b5a141b6a2efc2c5d2c67b4e150b2a268"

"taffydb@git+https://github.com/hegemonic/taffydb.git":
  version "2.6.2"
  resolved "git+https://github.com/hegemonic/taffydb.git#e41b5e179e197bb85c5fb887b707672b1e5ca079"

/shrug

DCKT · 2017-06-15T06:54:29Z

Hi,

I got this error too on yarn v0.24.6. Any idea about this ?

larserikfinholt · 2017-06-15T08:43:18Z

Hi, got the same issue on v0.23.. I upgraded to v0.24.6 but got same issue. I'm unsure of what info I should provide, but this is the last lines of yarn-error.log

  yargs@~3.10.0:
    version "3.10.0"
    resolved "https://registry.yarnpkg.com/yargs/-/yargs-3.10.0.tgz#f7ee7bd857dd7c1d2d38c0e74efbd681d1431fd1"
    dependencies:
      camelcase "^1.0.2"
      cliui "^2.1.0"
      decamelize "^1.0.0"
      window-size "0.1.0"
  
  yn@^1.2.0:
    version "1.2.0"
    resolved "https://registry.yarnpkg.com/yn/-/yn-1.2.0.tgz#d237a4c533f279b2b89d3acac2db4b8c795e4a63"

Trace: 
  Error: Invalid protocol: git:
      at Request.init (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:108126:31)
      at new Request (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:107796:8)
      at request (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:106394:10)
      at RequestManager.execute (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:56300:17)
      at RequestManager.shiftQueue (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:56327:10)
      at promise.default (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:56104:12)
      at Promise.F (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:29142:28)
      at RequestManager.request (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:56102:21)
      at NpmRegistry.request (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:30492:32)
      at TarballFetcher.fetchFromExternal (C:\Program Files (x86)\Yarn\lib\yarn-cli.js:54425:21)

larserikfinholt · 2017-06-15T08:53:02Z

Deleted yarn.lock and everything works fine.

nynexman4464 · 2017-06-29T18:16:32Z

Keep running into this setting up new devs. Deleting yarn.lock is not a good solution as it defeats the purpose of having the file in the same place (eg everyone installs the same versions of dependencies). It also is only temporary - once the yarn.lock is generated it can't be used by anyone else due to this issue.

Has anyone else found a different workaround?

keegan-lillo · 2017-07-12T01:09:41Z

One thing that worked for us was to:

look through your yarn.lock for anything using:

resolved "git+https://github.com/foo/bar.git#1234"

Comment out the entire block
Figure out which of your dependencies are using it and yarn upgrade the package to any new version. hopefully commenting out the block allows you to run the upgrade
yarn upgrade back to the version you were using before. The changes to the lock file should be minimal.

…/yarn#1625

benjaminkohl · 2017-09-25T18:59:07Z

We just inherited a project that uses Yarn so I installed it today and we are seeing this error. I agree that deleting the lock file is not an acceptable solution. I see a commit was merged on July 13th. Was that supposed to fix the issue?

pyramation · 2017-10-19T22:20:37Z

If it helps find this bug, I ran into this when using a git submodule and trying to run yarn install inside of the submodule.

I was able to copy the package.json into a clean folder and it ran just fine. However, any time, even after deleting yarn cache (manually and with yarn cache clean), it always failed to install properly inside of the submodule.

Currently my workaround is ok for me, but ideally would be great if there's a solution to this bug. Cheers!

**Summary** Yarn can not handle the `git+https://` dependency format correctly, as described for various versions in #1625. The problem is present in Yarn 1.2.1. A related problem for `git+ssh://` has been described in #573 and fixed in #3425. This PR extends the solution from #3425 to use the Git fetcher for any [Git-over-protocol](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) URLs. **Test plan** Extended the `package-request` unit tests to verify that the correct remote type (git) is used for `git+https://`, while the tarball remote type continues to be used for regular HTTP(S) URLs.

…g#4759) **Summary** Yarn can not handle the `git+https://` dependency format correctly, as described for various versions in yarnpkg#1625. The problem is present in Yarn 1.2.1. A related problem for `git+ssh://` has been described in yarnpkg#573 and fixed in yarnpkg#3425. This PR extends the solution from yarnpkg#3425 to use the Git fetcher for any [Git-over-protocol](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) URLs. **Test plan** Extended the `package-request` unit tests to verify that the correct remote type (git) is used for `git+https://`, while the tarball remote type continues to be used for regular HTTP(S) URLs.

charleylla · 2017-11-18T09:12:01Z

this worked for me:

npm uninstall yarn -g
npm install yarn -g
yarn install

perezpz · 2018-04-28T11:14:50Z

upgrade yarn to latest version and everything works fine.

cbrownbridge · 2018-05-27T22:00:48Z

Tried deleting yarn.lock file, it now requires a yarn install, cannot yarn install as it hits the same error.... error An unexpected error occurred: "Invalid protocol: localhost:".

olingern · 2020-01-28T10:27:27Z

Closing this. If this is is still an issue on 1.21.1, please comment and I'll reopen.

Daniel15 added the needs triage label Nov 4, 2016

bestander removed the needs triage label May 23, 2017

yuki24 mentioned this issue Jul 13, 2017

Fix deployment failure due to "An unexpected error occurred: "Invalid protocol: git:"." artsy/force#1639

Merged

gkovacs added a commit to habitlab/habitlab that referenced this issue Aug 23, 2017

make yarn happy on osx, to work around invalid protocol error yarnpkg…

d33bfeb

…/yarn#1625

This was referenced Oct 9, 2017

The dependency git+https://github.com/meteor/readable-stream.git causes problems with yarn meteor/node-stubs#10

Closed

yarn upgrade-interactive does not update package.json #4390

Closed

knuton mentioned this issue Oct 23, 2017

fix(resolver): Add general support for git-over-protocol URLs #4759

Merged

olingern closed this as completed Jan 28, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Yarn install Invalid protocol error #1625

Yarn install Invalid protocol error #1625

lambertkuang commented Nov 2, 2016

sebmck commented Nov 3, 2016

lambertkuang commented Nov 3, 2016

KidkArolis commented Nov 20, 2016

nadia318 commented Nov 25, 2016 •

edited

Loading

ianmurrays commented Dec 6, 2016 •

edited

Loading

ryanwe commented Dec 15, 2016

ianmurrays commented Dec 15, 2016

shkfnly commented Dec 15, 2016

ianmurrays commented Dec 15, 2016

cyprusglobe commented Dec 16, 2016

drewpc commented Jan 21, 2017 •

edited

Loading

pnispel commented Feb 8, 2017 •

edited

Loading

DCKT commented Jun 15, 2017

larserikfinholt commented Jun 15, 2017

larserikfinholt commented Jun 15, 2017

nynexman4464 commented Jun 29, 2017

keegan-lillo commented Jul 12, 2017

benjaminkohl commented Sep 25, 2017

pyramation commented Oct 19, 2017

charleylla commented Nov 18, 2017

perezpz commented Apr 28, 2018

cbrownbridge commented May 27, 2018

olingern commented Jan 28, 2020

Yarn install Invalid protocol error #1625

Yarn install Invalid protocol error #1625

Comments

lambertkuang commented Nov 2, 2016

sebmck commented Nov 3, 2016

lambertkuang commented Nov 3, 2016

KidkArolis commented Nov 20, 2016

nadia318 commented Nov 25, 2016 • edited Loading

ianmurrays commented Dec 6, 2016 • edited Loading

ryanwe commented Dec 15, 2016

ianmurrays commented Dec 15, 2016

shkfnly commented Dec 15, 2016

ianmurrays commented Dec 15, 2016

cyprusglobe commented Dec 16, 2016

drewpc commented Jan 21, 2017 • edited Loading

pnispel commented Feb 8, 2017 • edited Loading

DCKT commented Jun 15, 2017

larserikfinholt commented Jun 15, 2017

larserikfinholt commented Jun 15, 2017

nynexman4464 commented Jun 29, 2017

keegan-lillo commented Jul 12, 2017

benjaminkohl commented Sep 25, 2017

pyramation commented Oct 19, 2017

charleylla commented Nov 18, 2017

perezpz commented Apr 28, 2018

cbrownbridge commented May 27, 2018

olingern commented Jan 28, 2020

nadia318 commented Nov 25, 2016 •

edited

Loading

ianmurrays commented Dec 6, 2016 •

edited

Loading

drewpc commented Jan 21, 2017 •

edited

Loading

pnispel commented Feb 8, 2017 •

edited

Loading