Modify

Opened 3 years ago

Last modified 23 months ago

#5619 new defect

"update data" does not find conflicts

Reported by: skyper Owned by: team
Priority: normal Component: Core
Version: Keywords:
Cc:

Description

I canceled an upload. (It was near the end as later all changes where uploaded already).

There existed only on data layer and validator at that moment.
I updated data and no conflict was reported.
I added one more node and dried to upload but then I got several conflicts, all because of duplicated ways/nodes and there relations.
I ended up with just my singled node left to upload after resolving all errors and conflicts.

All these conflicts should have been reported by "update data"
(By the way, conflicts which are already solved are still shown)

r3652

Attachments (0)

Change History (2)

comment:1 follow-up: Changed 23 months ago by stoecker

The problem is very likely that JOSM silently removes the "created_by". This results in conflicts on data update.

comment:2 in reply to: ↑ 1 Changed 23 months ago by skyper

Replying to stoecker:

The problem is very likely that JOSM silently removes the "created_by". This results in conflicts on data update.

All the duplicates were my own new adds, which had been uploaded but I canceled during the server response. There should be no conflict of created_by because all data involed had been created by me using JOSM.

The problem was that JOSM did fail on the update right after a canceled upload. Sadly I do not have any data-file anymore. Try to keep them the next time.

Wonder how you can reach that state again (cancel upload during server responce for completion).

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team. Next status will be 'new'.
Next status will be 'needinfo'.The owner will change to skyper
as duplicate The resolution will be set to duplicate. Next status will be 'closed'.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'.
Author


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

 
Note: See TracTickets for help on using tickets.