Modify ↓
Opened 12 months ago
Last modified 12 months ago
#22965 new defect
Conflicts in areas downloaded by overpass are limited to 1 object on upload, leading to multiple upload attempts with a single conflict each
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
I keep getting conflicts even though I am refreshing my dataset:
-Upload changes
-Uploading failed - conflicts detected. I click 'synchronize entire dataset' and wait for the 30s -download and process.
-Upload changes
-Same thing
Also happens if i just synch the one conflicting way. Also happens if I cancel the upload attempt, and select File - Update Data.
Each conflict is different, so it is only detecting the conflict one at a time during upload, and not pulling in all of the relevant changes during a full dataset refresh.
Possibly relevant, each of the conflicts is with myself - changes I made via RapidEditor but have not synchronized to JOSM yet
Attachments (1)
Change History (3)
by , 12 months ago
| Attachment: | osm_conflict_loop.osm.zip added |
|---|
comment:2 by , 12 months ago
| Summary: | Repeated individual conflicts on upload attempt even after a dataset refresh → Conflicts in areas downloaded by overpass are limited to 1 object on upload, leading to multiple upload attempts with a single conflict each |
|---|
Note:
See TracTickets
for help on using tickets.
On IRC, the user mentioned that they were using r18721.
From IRC, steps to reproduce:
way 922993940is one way that has issues, apparently.It looks like this is due to objects outside of the full download areas having conflicts.
I've advised the user to download the area via overpass again, but I don't see a good way to do that automatically.