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)
Attachments (0)
Change History (2)
comment:1 follow-up: ↓ 2 Changed 23 months ago by stoecker
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).



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