NoSuchElementException in DuplicatedWayNodes

[anonymous]

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2013-06-22 01:35:22
Last Changed Author: Don-vip
Revision: 6016
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2013-06-21 09:43:29 +0200 (Fri, 21 Jun 2013)
Last Changed Rev: 6016

Identification: JOSM/1.5 (6016 en) Linux Ubuntu 12.10
Memory Usage: 455 MB / 455 MB (207 MB allocated, but free)
Java version: 1.7.0_21, Oracle Corporation, OpenJDK Server VM
Dataset consistency test: No problems found

Plugin: ElevationProfile (29611)
Plugin: ImportImagePlugin (29531)
Plugin: PicLayer (29601)
Plugin: geotools (29435)
Plugin: jts (29613)
Plugin: log4j (29435)
Plugin: opendata (29686)
Plugin: utilsplugin2 (29672)

java.util.NoSuchElementException
	at java.util.Collections$EmptyIterator.next(Collections.java:3006)
	at org.openstreetmap.josm.data.validation.tests.DuplicatedWayNodes.fixError(DuplicatedWayNodes.java:45)
	at org.openstreetmap.josm.data.validation.TestError.getFix(TestError.java:249)
	at org.openstreetmap.josm.gui.dialogs.ValidatorDialog$FixTask.fixError(ValidatorDialog.java:590)
	at org.openstreetmap.josm.gui.dialogs.ValidatorDialog$FixTask.realRun(ValidatorDialog.java:624)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:82)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:145)
	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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:722)

[Don-vip]

Can you please attach your .osm file leading to this error ?

[Don-vip]

Ok understood, likely a side effect of r5911 that sets the primitives collection of a test error to an empty colleciton when all the primitives are gone (after a purge for example).

Tests cannot assume the error still contain any of the initially affected primitives.

[Don-vip]

In 6030/josm:

fix #8822 - Don't try to fix empty errors