Correcting a Git corruption problem

Git — Tags: — dc.rec1 @ 7:07 pm

Sometimes when we work with submodules the wrong way we end corrupting the repository and after trying to pull the server we get:

error: git-upload-pack: git-pack-objects died with error.
fatal: git-upload-pack: aborting due to possible repository corruption on the remote side.
remote: Generating pack…
remote: Done counting 39 objects.
remote: Result has 28 objects.
remote: error: unable to find b490fa1a6d81e39d3a8d99f9cce8b57c3397b7d7
remote: fatal: unable toremote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header

I’m not sure if this is the best solution but pulling from the public URL and then pushing to the server solves the problem.

Remarkable plugins for ActsAsTaggableOn, Paperclip and ThinkingSphinx

rails, remarkable — Tags: , , , , , , , , — dc.rec1 @ 4:49 pm

I created this three Remarkable plugins so they could help me in a project I’m working on:

Basically they let you write code like this:

describe User do
  should_act_as_taggable_on :categories
 
  should_have_attached_file :logo
 
  should_index 'addresses.city', :as => :address
  should_have_index_attribute :priority
end

If this plugins helps you, please consider to recommend me at Working With Rails.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
(c) 2010 Diego Carrion | powered by WordPress with Barecity