On 01.11.2012 06:30, Toby Murray wrote:
Yeah, it seems like something is causing JOSM to send two changeset
close requests to the server in rapid succession and then only paying
attention to the second response which is an error so it thinks the
changeset is still open. Next time it goes to upload data to the
changeset it gets an error back because it is actually closed.
It started after upgrade from josm-snapshot-5485.jar to
josm-snapshot-5531.jar including an update of the plugings + enabling
the wikipedia plugin.
I did a quick check:
* after a downgrade to 5485 (leaving the new plugings and the wikipedia
plugin) the problem was gone.
* then another upgrade to 5531 and it didn't reoccure.
Strange because...
I haven't seen this myself or reproduced it (probably because I
typically leave my changesets open) but I think I saw 3 different
reports of it on #osm today.
...tonight it was 100% reporducible for me. Hmmm, really strange.
Maybe the changeset needs certain size or so? The changesets used for
the tests this afternoon had all been only of one new/removed way with
only 3/4 nodes.
After one of them, Tom Hughes checked the
server log and saw two calls to close the changeset, one right after
the other.
I'll keep an eye on this issue. If it reoccures, I will show up again.
Thanks,
Michael.
_______________________________________________
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev
