ProgressException when uploading osmChange file

[iandees]

1. Open a large osmChange file (one attached)
2. Click upload
3. Enter change comment and one changeset tag (source="National Hydrography Database")
4. Click Upload
5. Receive error alert: "Expected states are [IN_TASK] but current state is INIT"

Version: 2060

Stack trace:
org.openstreetmap.josm.gui.progress.ProgressException: Expected states are [IN_TASK] but current state is INIT

at org.openstreetmap.josm.gui.progress.AbstractProgressMonitor.checkState(AbstractProgressMonitor.java:66)
at org.openstreetmap.josm.gui.progress.AbstractProgressMonitor.finishTask(AbstractProgressMonitor.java:92)
at org.openstreetmap.josm.io.OsmServerWriter.uploadOsm(OsmServerWriter.java:194)
at org.openstreetmap.josm.actions.UploadAction$UploadDiffTask.realRun(UploadAction.java:534)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:62)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:116)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

[iandees]

Compressed osmChange file is too big, can't attach it. Send me an e-mail if you'd like to see it.

[iandees]

Just tried with the latest version with the same result: 2066.

[Gubaer]

Yes, I'd like to see it. Can't reproduce with small test files.

[anonymous]

Replying to Gubaer:

Yes, I'd like to see it. Can't reproduce with small test files.

Posted the file here: ​http://mapki.com/nhd070300.waterbody0.osm

[Gubaer]

(In [2078]) fixed #3413: ProgressException when uploading osmChange file

[Gubaer]

Uploading large dataset should work now.

Your file is a osmChange change file, not an osm file. Even if you didn't run into the problem you reported uploading would have failed because of missing API version. That's fixed too but I nevertheless disabled reading osmChange file as data file. That's because an upcoming feature in JOSM will read osmChange files as changesets, not as datasets.