Object can't be deleted if already deleted on the server

[Gubaer]

• start two instance of JOSM, JOSM_1 and JOSM_2
• in JOSM_1, create a node and upload
• in JOSM_2, download the node
• in JOSM_1, delete the node and upload
• in JOSM_2, delete the node and upload

Leads to 410 Gone with the message "The node with the id 178848 has already been deleted" in JOSM_2. This can't be resolved in JOSM. The dataset in JOSM_2 can't be uploaded to the server anymore.

BTW: 410 Gone isn't defined as error code the context of a PUT changset, see ​API. Perhaps it has to be fixed on the server.

[framm]

The described procedure is not supposed to work. The server is *never* going to merge changes for you; if you simultaneously make a change in two JOSM instances and upload, one of the uploads is *always* going to fail unless you do a new download before you upload and resolve the conflict locally.

However, doing a local download would not help in this specific instance because JOSM does not detect that a node is missing from the download. We will have to employ one of the solutions discussed in this thread to solve the problem:

​http://lists.openstreetmap.org/pipermail/josm-dev/2009-April/002925.html

[anonymous]

Replying to framm:

The described procedure is not supposed to work. The server is *never* going to merge changes for you; if you simultaneously make a change in two JOSM instances and upload, one of the uploads is *always* going to fail unless you do a new download before you upload and resolve the conflict locally.

I know

However, doing a local download would not help in this specific instance because JOSM does not detect that a node is missing from the download. We will have to employ one of the solutions discussed in this thread to solve the problem:

That's why I filed the ticket.

​http://lists.openstreetmap.org/pipermail/josm-dev/2009-April/002925.html

Glad to see the problem has already been discussed and analyzed.

[stoecker]

Closed as duplicate of #2609.

[Speight]

I'm reopening here, because the marked-as-duplicate-of bug describes a broader scenario which has apparently been fixed for most cases.

The case of trying to upload the action of deleting a node once it has already been deleted on the server now (still?) breaks things, even if the area is re-downloaded, with an error message like the following.

Caused by: org.openstreetmap.josm.io.OsmApiException: ResponseCode=410, Error Header=<The node with the id 429965312 has already been deleted>,Error Body=<The node with the id 429965312 has already been deleted

Steps to reproduce:

create a POI in Potlatch in live edit mode.
Open up JOSM, delete the POI (but don't upload yet).
Delete the point in Potlatch.
Try to save in JOSM.
Even if JOSM updates the server, it can't be saved; it never realizes that the point no longer exists on the server and should not be uploaded.

[stoecker]

What JOSM version? There have been a lot of changes in latest regarding this topic.

[Gubaer]

Replying to stoecker:

What JOSM version? There have been a lot of changes in latest regarding this topic.

I think so too. This should be fixed since r1690.

@Speight: what if you try the latest version (~ 1710 or so)? Can you still reproduce it?