BUG: Import QA System throws an exception

[mlinkert]

Steps to reproduce:

1. Start importer and log in to server (gretzky)
2. Select "mike1_R3d.dv" from the test_images_bad directory
3. Click "+"
4. Choose any project/dataset
5. Choose "partial path" with 0 leading directories for the image name
6. Click "Add"
7. Click "Import"
8. Click the "Import Errors" tab
9. Click the "Send Feedback" button.
10. Enter an email address and comment, and check the first checkbox (only send the actual data files, not the log file).
11. Click "Send Comment"
12. Repeat (1)-(9).
13. Enter an email address and comment, and leave both boxes unchecked.
14. The QA is not submitted; its status is "pending". No error message is visible to the user, but on the console the following stack trace is displayed:

java.lang.ArrayIndexOutOfBoundsException: 1 >= 1
	at java.util.Vector.elementAt(Vector.java:447)
	at javax.swing.table.DefaultTableModel.getValueAt(DefaultTableModel.java:649)
	at ome.formats.importer.gui.ErrorHandler$MyErrorHandler.isSend(ErrorHandler.java:170)
	at ome.formats.importer.util.ErrorHandler.sendErrors(ErrorHandler.java:252)
	at ome.formats.importer.gui.ErrorHandler$MyErrorHandler.sendErrors(ErrorHandler.java:162)
	at ome.formats.importer.gui.ErrorHandler$MyErrorHandler$1.run(ErrorHandler.java:115)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)

[jburel]

Moved from sprint 2011-05-19 (12)

[bwzloranger]

Hi M,

I was not able to reproduce this bug (despite the excellent level of detail - much thanks). Is this a linux bug perhaps (or were you testing in some other way that caused it)?

[mlinkert]

Sorry, it looks like I missed a step in the description. If you click the "Clear Done" button after sending the first feedback (but before starting the second import), then the exception should appear. I couldn't reproduce the exception without clicking "Clear Done" either, so it must be something to do with that button.

[jburel]

Moved from sprint 2011-06-02 (13)

[bwzloranger <bwzloranger@…>]

(In [23b7a57ea564b07b5b0318ffcfdbb84649265b21/ome.git] on branch develop) Fixes #5250

[bwzloranger <bwzloranger@…>]

(In [26dfa694528d6a8b1a045d37f2df7bce128eb654/ome.git] on branch develop) Fixes #5250