search

nschum / Gitifier

Git commit notifier for MacOSX
http://psionides.github.com/Gitifier/
Eclipse Public License 1.0
314 stars 15 forks source link

Constant Notifications #14

Closed holtkampw closed 13 years ago

holtkampw commented 13 years ago

I use gitosis for my self-hosted git repos.

After upgrading to the latest version (1.1.1) it shows a growl notification every 5 minutes (my update interval) for the last push (not necessarily a new commit/push).

It has only done this for any repo that has been through the commit/push cycle while using the new version.

Any ideas?

holtkampw commented 13 years ago

Correction: it shows every push made to the repo (every update interval).

I have 2 commit/pushes since I started using 1.1.1 so it shows 2 growl notifications (always the same) on every update.

mackuba commented 13 years ago

That's strange, I haven't seen this kind of behavior anywhere...

Do you remember which version you were using before? was it 1.0 or 1.1? (1.0 didn't have the commit window that appears after clicking a growl)

Also, can you check the logs in Console.app and see if you can find something there that's coming from Gitifier and looks suspicious?

holtkampw commented 13 years ago

I believe 1.0 but I'm not 100% sure. I actually moved from a HDD to an SDD so this was a fresh install. I just remember Gitifier was amazing on the HDD before I moved over.

There's absolutely nothing in Console.app that I can find.

I deleted the gitifier cache directory and the app, then reverted to 1.0. Then I added the repos (they cloned successfully, etc). Oddly enough, it still gives me multiple (every) commit notifications for the same repo.

Any ideas/debugging I can do?

mackuba commented 13 years ago

Hm, funny... maybe it's something with you repo...

Try finding the repo's directory inside the cache, where the .git directory is, and calling git fetch from there. The way Gitifier works is that it calls git fetch in that directory, and if fetch prints any commit ranges, it runs git log on those.

holtkampw commented 13 years ago

I did git fetch and got:

And a 3rd/4th time repeats the cycle. Is that standard behavior? I'm not familiar with fetching.

mackuba commented 13 years ago

Hm, that's definitely not standard behavior... Fetch is basically what git pull does before the merge. It asks the server if there are any new commits after the current local copies of remote branches, and if there are any, it updates those copies. Git pull does a git fetch first, and then if the local copy of origin/master was updated, it merges the latest version into master.

So in brief, if there are no new commits in the repo, fetch shouldn't do anything, just like pull doesn't.

Check what happens if you go to a new directory, do a clone from your repo there, and then start calling git fetch or git pull in the new copy. If the same thing happens, you've got something messed up in your repo. If it doesn't, then maybe this has something to do with the way Gitifier makes the clone...

The remote repo, is this a new repo that you've created recently or is it something that you've already worked on for some time?

holtkampw commented 13 years ago

Its a relatively new ( ~2 week old) repo.

I did a full clone, and fetch gives me the same results. Pull, however, does the same thing:

and

mackuba commented 13 years ago

Have you perhaps created the repo on the remote server without --bare? A remote repo should be created as bare, i.e. without the "working copy", there should just be a .git subdirectory in its directory and nothing else (after all, no one needs to work on the repo directly on the server). I remember that some crazy things like this can happen if your remote repo isn't bare (I think I wasn't even able to push to such repo, or maybe it printed some ugly warnings, I don't remember exactly - maybe what you have is what happens when you ignore those warnings...).

holtkampw commented 13 years ago

I use Redmine/Gitosis to manage the repo. I assume Gitosis creates bare repos.

I can do some investigating. I just never had any problems with push/pull/branching so I figured there was a small bug in Gitifier.

Great app! Thanks for the help, even though it had nothing to do with your application.

mackuba commented 13 years ago

No problem, I'm glad you like the app :)