java.lang.NullPointerException On Commit With Deleted Files To Be Removed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Commit Project
2. Delete File
3. Recommit with commit action for deleted file set to 'Remove'

What is the expected output? What do you see instead?
I expect the deleted file to be committed as deleted.
Instead I get a message box 'Unexpected Exception':
A java.lang.NullPointerException exception has occurred.
Please report this at http://www.netbeans.org/issues.html, including a 
copy of your messages.log file.
The messages.log file is located in your /home/arm/.netbeans/6.5/system 
folder

What versions of NbGit, NetBeans and Java are you using?
On what operating system?
NbGit: 0.1.1
Product Version: NetBeans IDE 6.5 (Build 200811100001)
Java: 1.6.0_0; OpenJDK 64-Bit Server VM 14.0-b08
System: Linux version 2.6.28-13-generic running on amd64; UTF-8; en_US (nb)
Userdir: /home/arm/.netbeans/6.5

Please provide any additional information below.
By changing the commit action to 'Exclude From Commit', things are fine. 
Deleted files build up in the project file tree, grayed out.

Original issue reported on code.google.com by armw...@gmail.com on 15 Jun 2009 at 5:05

[GoogleCodeExporter]

It would be nice to have the actual stack trace of the exception.
At least the saying where in the nbgit code the error occurs.

Original comment by jonas.fonseca on 8 Aug 2009 at 6:59

• Added labels: NetBeans-6.5, Java-1.6, OpSys-Linux, Component-Commit

[GoogleCodeExporter]

Not able to reproduce this with the current code on NetBeans 6.7.

Original comment by jonas.fonseca on 17 Aug 2009 at 11:05

• Changed state: NeedMoreInfo

[GoogleCodeExporter]

still getting this. how can i get the stack trace?

NbGit: 0.3
Product Version: NetBeans IDE 6.7 (Build 200906241340)
Java: 1.6.0_0; OpenJDK 64-Bit Server VM 14.0-b16
System: Linux version 2.6.31-16-generic running on amd64; UTF-8; en_US (nb)
Userdir: /home/arm/.netbeans/6.7

Original comment by armw...@gmail.com on 21 Jan 2010 at 2:58

[GoogleCodeExporter]

NetBeans tells you where you can get the log file. You initial report said:
{{{
The messages.log file is located in your /home/arm/.netbeans/6.5/system 
folder
}}}
So look in /home/arm/.netbeans/6.5/system/messages.log and try to dig
out the relevant part.

Original comment by jonas.fonseca on 21 Jan 2010 at 1:46

• Added labels: NetBeans-6.7

[GoogleCodeExporter]

i'm not looking to turn this into a tech support issue, so don't read this in 
that 
manner. i'm hoping these details will mean something helpful.
~/.netbeans/6.5/system   and   ~/.netbeans/6.7/system  do not exist.
found it in ~/.netbeans/6.7/var/log/
i cleared the log file after launching netbeans but before running the commit.

Original comment by armw...@gmail.com on 21 Jan 2010 at 3:40

Attachments:

• messages.log

[GoogleCodeExporter]

alright, after some poking around it was a problem with my git repo.
terribly sorry to waste your time like that.

Original comment by armw...@gmail.com on 21 Jan 2010 at 4:37

[GoogleCodeExporter]

OK, thanks for digging further into this. First, I completely
forgot about var/log/messages.log. It is still strange that
nbgit crashes in a corrupt repository.

Original comment by jonas.fonseca on 23 Jan 2010 at 4:30

[GoogleCodeExporter]

Without thinking I replied to the notification email I received with your 
message and 
I'm not sure what will happen to it but it hasn't appeared on here yet, so I've 
pasted it below.

If it helps, I can provide a few more details on what I experienced.
If anything it'll be nice to have this on record, and here is a good spot for 
it.

I'm pretty sure my git repo got messed up from moving the project folder 
around. I recall some (paraphrasing) 'error copying/moving file' message about 
a few files (long hash filenames) within the .git folder. I ignored it at the 
time, assuming a new commit would create at least a working commit to go from. 
This did not work, and the problems carried from one commit to the next.

Certain files which I knew to still exist and in fact be a crucial project 
file were displayed in NetBeans in a grey color. Files listed in grey I took 
to mean were removed files, as those were the files listed in the commit 
dialog that were in the (again, paraphrasing) 'Commit Type' column as 
'Remove'. If I changed all those as 'Remove' to 'Ignore' the commit would run 
just fine, and of course wouldn't be committed.
At the time I thought that to be a different issue, but it was also corrected 
after I recreated the git repo. This is where I believe nbgit ties into the 
the git repo corruption and crashes with a null reference error, probably 
looking for the git file that doesn't exist (ie: didn't get copied/moved).

I hope this helps you with a House-like "you vacationed in Tahiti last year 
and laid on the beach, got a parasite and that's why you're dying" moment.

Original comment by armw...@gmail.com on 23 Jan 2010 at 11:06