js-cookie: bug: error github with bower install: transfer closed with outstanding read data remaining

It just cloned for me too! Maybe Github fixed it!

I’m having this problem. It’s happening with the old jquery-cookie repo as well.

+1 our builds are failing 😃

The jquery-cookie repository (https://github.com/carhartl/jquery-cookie/) is showing the exact same symptoms. Are these issues related?

If anybody knows what happened, please shout out!

I did a github research and it seems to have happened only for a couple of repositories. You can imagine how paranoid I was starting to be when sh1t started blowing out of the blue.

It’s 2AM in Australia right now… oh boy. I am going to sleep, happy everything is fine now, @addyosmani sorry for bothering.

I am having the same error when cloning via SSH:

git clone git@github.com:js-cookie/js-cookie.git js-cookie2
Cloning into 'js-cookie2'...
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Hey I have made no changes in the repository, this is definitely an external thing!

+1

I think it’s fixed? Just cloned for me.

Would really like a fix because unfortunately the suggested workaround is not suitable when the build is automated on different servers 😢

This was nice opportunity to update development tools.

I managed to add this in my bower.json file: "js-cookie": "https://github.com/js-cookie/js-cookie/releases/download/v1.5.1/js.cookie-1.5.1.min.js"

Then I get a index.js file containing the things, not ideal, but I don’t have to fork the repo.

just pinged Github Support on Twitter about this, do you guys know a better way to inform github ? https://twitter.com/VEBERArnaud/status/724616121148661761

temp solution for this is 1- forking the repo 2- download the zip 3- extract and rename folder to js-cookie 4- past the folder in your bower_components folder

Response from Github:

Re: Mayday mayday. Sh1t is blowing.

Hi Fagner,

Sorry for the trouble. We were investigating reports earlier today of cloning and pushing problems in some repositories.

Confirmed as a temporary glitch. Closing since everything was fixed.

@FagnerMartinsBrack @bdaenen You’re both right, sorry for the confusion.

@anolson Web requests to a github repository endpoint always seem to get redirected to the github page.

temporary fix: fork the repo and: bower install https://github.com/[repo]/js-cookie.git#v[version] --save

I just sent to Github support in the contact page.

@panthony you can fork and change the entry in your bower.json to your fork’s url instead of having to add the package to your project/bower_components folder.

This is terrible. Causing Production deploy issues. Gonna have to create a hacky workaround until this is fixed. We don’t commit our bower_components directory and it gets installed fresh on each deploy, so can’t just download the zip and extract it. I guess one option is to put it in the vendor/assets directory for now

+1 Seeing this too. Going to need a fix ASAP.

Same here

It’s not just bower I can’t clone

❯ git clone https://github.com/js-cookie/js-cookie.git
Cloning into 'js-cookie'...
fatal: unable to access 'https://github.com/js-cookie/js-cookie.git/': transfer closed with outstanding read data remaining