Databases
StackOverflow2013
Postsdbo
POGit push fails to github: failed to read object
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit push fails to github: failed to read object
    primarykey
    data
    text
    <p>The story:</p> <p>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 &amp; merge on other.</p> <p>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 &amp; 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.</p> <p>Until now. I tried to push from my laptop to github, which gives the following output: </p> <pre><code> 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' </code></pre> <p>So, the question is, what exactly took place here?</p> <p>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</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMichael Durrant
    1. USTeemu Vainio
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGit push fails to github: failed to read object
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGit push fails to github: failed to read object
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGit push fails to github: failed to read object
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat does `git fsck` report?
      singulars
      1. POGit push fails to github: failed to read object
      1. USGreg Hewgill
    2. COMaybe this one helps: http://stackoverflow.com/questions/801577/how-to-recover-git-objects-damaged-by-hard-disk-failure
      singulars
      1. POGit push fails to github: failed to read object
      1. UStobiasbayer
    3. COWhat do you mean "revert"? "Reverting" in the sense of `git revert` is making a *new* commit that undoes some other commit(s), but leaves the complete history intact. If you want specific help with this, provide the actual sequence of commands that you executed at both sites. If you screwed with history that you had already pushed to your github repo, there's your oops. See http://progit.org/book/ch3-6.html#the_perils_of_rebasing .
      singulars
      1. POGit push fails to github: failed to read object
      1. USrlibby
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload