Modify

Opened 12 years ago

Closed 9 years ago

#7416 closed defect (irreproducible)

conflicts all over the place

Reported by: dieterdreist Owned by: dieterdreist
Priority: blocker Milestone:
Component: Core Version: latest
Keywords: Cc:

Description

Current latest seems somehow broken, I get conflicts every time I upload. Also the error message seems strange (version 0):

Failed to delete way 61,395,668. It is still referred to by relations [{Relation id=388574 version=0 IV]}, {Relation id=1675796 version=0 IV]}]. Please load the relations, remove the reference to the way, and upload again.

Attachments (2)

conflict364555092.png (46.4 KB ) - added by dieterdreist 12 years ago.
conflict management for node, why aren't there coordinates for the node on the server?
123.osm (952.2 KB ) - added by dieterdreist 12 years ago.
this is the file that created the conflict

Download all attachments as: .zip

Change History (13)

comment:1 by dieterdreist, 12 years ago

I resolved the conflict but it is popping up again on next upload:

Failed to delete way 61,395,668. It is still referred to by relations [{Relation id=388574 version=0 IV]}, {Relation id=1675796 version=0 IV]}]. Please load the relations, remove the reference to the way, and upload again.

comment:2 by dieterdreist, 12 years ago

The first time there was only a conflict for the way (deleted locally, not deleted and referenced by 2 relations on the server). The next time there were 6 conflicts on the tags as well (the second time I decided to keep the version on the server, even if it was a way with 0 members): all tags were removed on the server version, my version (deleted) had still the 6 tags. I decided to keep the tags for the way with 0 nodes.

Now I got a problem with the nodes:

Failed to delete node 1,088,122,207. It is still referred to by way 48605334. Please load the way, remove the reference to the node, and upload again.

comment:3 by dieterdreist, 12 years ago

I also don't understand the conflicts on the nodes: why does my (deleted) version have coordinates, but the server one (not deleted) doesn't? See attached screenshot

by dieterdreist, 12 years ago

Attachment: conflict364555092.png added

conflict management for node, why aren't there coordinates for the node on the server?

comment:4 by dieterdreist, 12 years ago

I keep getting strange conflicts:

Failed to delete node 1,149,167,982. It is still referred to by ways [{Way id=99350587 version=0 IV (incomplete)}, {Way id=103212791 version=0 IV (incomplete)}]. Please load the ways, remove the reference to the node, and upload again.

in reply to:  4 comment:5 by dieterdreist, 12 years ago

Replying to dieterdreist:

I keep getting strange conflicts:

Failed to delete node 1,149,167,982. It is still referred to by ways [{Way id=99350587 version=0 IV (incomplete)}, {Way id=103212791 version=0 IV (incomplete)}]. Please load the ways, remove the reference to the node, and upload again.

After clicking on "resolve" now I get 16 node conflicts (at the beginning there were only 10).

I'll stop resolving conflicts now and will drop my modifications and mapping, as there seems to be something seriously broken.

by dieterdreist, 12 years ago

Attachment: 123.osm added

this is the file that created the conflict

comment:6 by skyper, 12 years ago

  1. open file
  2. update data -> four conflicts (2 rel/1 way/1 node)
  3. solved all conflicts choosing local
  4. update data -> two conflicts (1 way/1 node)

There is a problem with the conflict on node id:224808522.

deleting the node in conflict resolution raises another conflict, as you delete a node of way id:61395668 which only consists of two nodes. E.g. this way gets deleted and raises another conflict.

  1. solved all conflicts
  2. update data -> two conflicts reappear.

I did not try to upload, but as there gets one long boundary way with nodes outside downloaded area deleted you probably gonna run into some conflicts on delete nodes.

Replying to dieterdreist:

I also don't understand the conflicts on the nodes: why does my (deleted) version have coordinates, but the server one (not deleted) doesn't? See attached screenshot

Looks like the problems I have with known elements of relations which are known on local side but shown as incomplete on theirs.

comment:7 by skyper, 12 years ago

#5783 seems to be related.

comment:8 by verdy_p, 11 years ago

There are similar conflicts when trying to restore a deleted object : new objects are restored but cannot be uploaded because they will be uploaded BEFORE other objects they depend on, and that have also been undeleted (but will be uploaded AFTER). When there are then conflicts when sending only some objects in our wanted order (submitting restored relation members, then submitting the restored relation separately), if a conflict occurs in the first uploads, everything is mixed up in the dependancy checks !
Restoring a deleted relation with its members, or a deleted way with its nodes, is now a nightmare because dependencies are not properly checked in the correct order.

comment:9 by stoecker, 9 years ago

Owner: changed from team to dieterdreist
Status: newneedinfo

Still an issue?

comment:10 by dieterdreist, 9 years ago

obviously not, this is 3 yrs ago ;-)
Can't reproduce currently, suggest to close

comment:11 by stoecker, 9 years ago

Resolution: irreproducible
Status: needinfoclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain dieterdreist.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.