I am getting the following error when I try to push my app to heroku. I saw a similar thread on here, but the issues seemed related to OSX. I am running windows 7
$ git push heroku master
Counting objects: 1652, done.
Delta compression using up to 4 threads.
fatal: object 91f5d3ee9e2edcd42e961ed2eb254d5181cbc734 inconsistent object lengt
h (476 vs 8985)
error: pack-objects died with strange error
error: failed to push some refs to 'git#heroku.com:floating-stone-94.git
I'm not sure what this means. I can't find any consistent answers on the internet. I tried re-creating my ssh public key but still the same.
You need to recover the corrupted files.
How to recover Git objects damaged by hard disk failure?
Related
I downloaded urbit and am attempting to boot my ship for the first time. In following the instructions online, I ran the following command:
./urbit -w sampel-palnet -k path/to/my-planet.key
The script progressed until this line:
boot: downloading pill https://bootstrap.urbit.org/urbit-v0.10.4.pill
After some time, I received the error in the title of this question.
Does anyone know what the error means and what I can do to resolve it?
Have you tried checking this issue on Github. It's not exactly the same error as yours, but it's similar, so maybe it could be related.
Did you also check the Urbit Docs.
If none of this works I would recommend you create an issue in Urbit's Github page.
I've been searching around the heroku docs, heroku community, stack overflow, google and can't figure out an issue I'm having with the heroku command line interface. Any time I try to run the heroku command I get the same error:
Error parsing /Users/lee/.local/share/heroku/client/6.15.26-5726b6f/node_modules/#cli-engine/engine/package.json: Unexpected token � in JSON at position 0
Here's the full error:
https://gist.github.com/leemcalilly/21f28769c0d1a96127be1fdb2b63f236
The only things that have changed recently on my system is that I changed my heroku password and also installed docker. Otherwise nothing has changed and I'm still able to deploy changes via git.
I installed heroku's command line tools on my Mac with Homebrew and have already tried uninstalling and reinstalling. Still getting the same error.
Any help pointing me in the right direction on this would be helpful.
EDIT:
Here's how the file that it's getting stuck on looks (package.json):
https://gist.github.com/leemcalilly/35fb919b490bf02c6779811448da5f02
Very crazy. Not even sure how that happened, but I would have thought that uninstalling through homebrew and reinstalling would work.
Got an answer on this from Heroku support that fixed this issue for anyone else that runs into this:
Hey Lee, looks like you may have had a bad download/install but rather than re-install with brew I'd like you try something else. Let's remove your heroku client directory and then run heroku update with will fetch a new one. Try rm -fr /Users/lee/.local/share/heroku, then heroku update and it should fetch an updated CLI. Note: any plugins you have installed will have to be re-installed after this.
Let me know how it goes!
I recently pushed a new and empty app with gemfile added up to heroku and it was added successfully. The folder size locally is 488kb but on heroku its slugsize is 6mb of 100mb. I did this after trying to push my real application that kept showing this error: fatal: sha1 file '' write error invalid argument. The size of this app locally is 3mb. Could this really be the problem why it isn't bing pushed. How on earth do i reduce this size even after adding .gitignore and .slugignore files. Thanks
Details on the slug size can be found here:
https://devcenter.heroku.com/articles/slug-compiler
The key part you might be interested in is:
You can roughly estimate slug size locally by doing a fresh checkout
of your app, deleting the .git directory, and running du -hsc.
$ du -hsc | grep total
You get 200mb maximum though, so I wouldn't worry about it.
Please help. I have absoluty no idea what's wrong. The rails app works on my local machine.
If I do this:
git push heroku master
I get this:
Counting objects: 4195, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3944/3944), done.
Writing objects: 72% (3009/4178), 9.99 MiB | 73 KiB/s
Compressing objects: 100% (3944/3944), done.
**Connection to 10.46.xxx.xxx closed by remote host.KiB/s
error: pack-objects died of signal 13
error: failed to push some refs to 'git#heroku.com:gentle-rain-xxxx.git**
I just dealt with 24 hours of this hell. I re-cloned repos, destroyed apps, repacked, pruned... the whole 9 yards.
It turned out that I had a .txt file which was ~250MB in size that, even though I had removed it from my master branch, was still present in my local (as well as github) cache.
I checked out this page and inadvertently found my answer here:
https://help.github.com/articles/remove-sensitive-data
The .txt file had previously been in the doc/ folder, so I pointed this command at where the file would have been in any commits and ran it.
git filter-branch --index-filter 'git rm --cached --ignore-unmatch doc/US.txt'
This is very useful if you realize you have static assets of some sort that don't have to be in your repo and are causing you to get the signal 13 error.
I was having problems with a repository as small as 130MB. I don't really want to prune my repository, nor do I feel it is necessary.
I can't help but feel this is a problem with git and/or Heroku, I believe a big push should succeed, even over a "slow" or less than ideal connection.
How I solved/worked-around this issue was to spin up an EC2 instance, checkout my repo there, and push to github. In that way, my deploy speed was 4MiB/s (faster than my own 80KiB/s!). Furthermore, in the cases where the push would fail due to some configuration issues, I could quickly tweak and try again.
For more information on this technique, I've written up the full steps on how to spin up an EC2 instance for this purpose here: http://omegadelta.net/2013/06/16/pushing-large-repositories-to-heroku/
Hi I had the same problem trying push to cedar stack. I contacted heroku support and they fixed it. Here is what they said:
It appears to be due to a change in our git server on our end. I'll be
following up with our engineers to make sure we get a permanent fix
rolled out for this.
-Chris
This appears to just be a timeout from your push being too large.
I got around this by doing a git reset to a SHA that was around 500 commits back, pushing that, and then pushing the rest of my repo.
The story:
I've been developing a RoR-app in both my desktop and laptop. It was quite handy to commit changes made on another, push them to github and fetch & merge on other.
The starting point is this: I committed latest changes on my desktop, pushed them to github and then fetched and merged them into my laptop. Then, I made some commits on laptop and pushed to github. Took the changes, merged to my desktop (with --no-ff). THEN, happened the probable source of all mischiefs: I reverted the desktop to commit where it was before the latest fetch & merge. Made some development work with it, committed, pushed to github. In the laptop, I did the revert as well, though I reverted it to a commit which was made somewhere between the latest fetch from github, fetched again and merged those. Some error messages came after reverting desktop and laptop both, but things worked still fairly well and I kept working on both machines.
Until now. I tried to push from my laptop to github, which gives the following output:
Counting objects: 106, done.
error: unable to find 5a2a4ac...
error: unable to find bc36923...
error: unable to find ecb0d86...
error: unable to find f76d194...
error: unable to find f899df7...
Compressing objects: 100% (64/64), done.
fatal: failed to read object 5a2a4ac... : Invalid argument
error: failed to push some refs to 'git#github:username/repo.git'
So, the question is, what exactly took place here?
EDIT: It seems that because of suspending my laptop and moving it from place to place in that state screwed up the hard drive somehow. The fsck output is unavailable because we worked around the problem and kept on working, but IIRC some branches and commits were dangling, including that commit which git failed to read. - Teemu
I have run into these kinds of issues.
Rather than spending hours trying to resolve and fix these issues, my 'solution' is usually to take the code I want, copy it into a new directory, delete the .git files and then create a new github for it and then connect the two as usual.
Although this may not be a specific answer to the details you raise, I find that there can be a number of ways that git/github issues can happen and rather than wishing I was a 'git expert' now (it's happening but it takes time), I do the above and continue with my actual application development.
The problem you have is that you are trying to read objects that are not part of your 'tree'. They exist but they have been orphaned. However, git allows you to merge one project to another so this is one way you can keep your commits without starting again, something like the following:
git remote add -f somename git://somegitplace.com/user/some.git
git merge -s ours --no-commit somename/master
git read-tree --prefix=ext/somename -u somename/master
git commit -m 'external merge'
git pull -s subtree somename master
Hope that helps. Let me know if not and we can attack it again