Modify

Opened 8 years ago

Closed 6 years ago

#6373 closed defect (fixed)

Uploading deleted nodes that are still referenced by relations leads to unfixable editor state

Reported by: asciiphil Owned by: Don-vip
Priority: normal Milestone: 14.02
Component: Core Version:
Keywords: Cc:

Description (last modified by malenki)

If you delete a node that is a member of a relation and JOSM doesn't know about the relation, when you upload the changeset containing the deleted node, the API responds with an error code (451) which interrupts the upload. When the deleted node is referenced by a way, JOSM creates a conflict which can be resolved, but when the node is referenced by a relation, no conflict is created. Since the node cannot be recreated either, the changeset is now stuck in a partially-uploaded state.

JOSM should handle node-still-referenced-by-a-relation the same way it handles node-still-referenced-by-a-way and create a conflict to be resolved.

Attachments (0)

Change History (5)

comment:1 Changed 6 years ago by malenki

Description: modified (diff)

See also: #7157 and #9624

comment:2 Changed 6 years ago by simon04

Milestone: 14.02

comment:3 Changed 6 years ago by Don-vip

is this problem fixed with recent changes?

comment:4 Changed 6 years ago by Don-vip

Owner: changed from team to Don-vip
Status: newassigned

not fixed completely, work in progress

comment:5 Changed 6 years ago by Don-vip

Resolution: fixed
Status: assignedclosed

In 6886/josm:

fix #6373 - proper conflict resolution after failed attempt to delete an object referenced by an unknown one

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Don-vip.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.