Modify

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#4411 closed defect (fixed)

Can't upload due to conflicts, but conflict list is empty

Reported by: augustus.kling@… Owned by: team
Priority: major Milestone:
Component: Core Version: latest
Keywords: conflict, upload fail Cc:

Description

When I try to upload I get a message box stating “There are unresolved conflicts in layer 'Data Layer 1'. You have to resolve them first”. Before this I synchronized the entire dataset when requested to do so on failed upload.

However opening the conflict list (sidebar panel) does not show any conflicts. Right-clicking the data layer and selecting “Dataset consistency test” gives the following message:
{Way id=48343709 version=2 MVDd nodes=[]} not found using Dataset.searchWays()
{Way id=48343710 version=1 MVDd nodes=[]} not found using Dataset.searchWays()

When trying to save to a file for further investigation JOSM tells that it would not save conflicts and reject them instead. After rejecting the conflicts this way uploading is still not possible (and the conflict list remains empty).

After reopening the file (conflicts rejected on save) and syncing again, I received an other conflict (probably unrelated to the ones described above). This time the conflict was listed in the conflict list and could be resolved and the data could be uploaded.

This leaves some issues:

  • Why does JOSM complain about conflicts while presenting an empty conflict list?
  • I there a way to provide debugging information? Possibly listing stack traces of exceptions in “Status Report” window in help menu or a log file. Usually I don't start JOSM from a console and thus cannot see its error output.
  • The wording “reject” when trying to save may be not clear to the user. I guess ignoring servers version and using own version would be clearer.

Some system information (in case they are needed). These information were gathered after successful upload as described. I guess it would make sense to also include the operating system in the following output. Mine is Ubuntu 9.10.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2010-01-19 02:32:36
Last Changed Author: mjulius
Revision: 2877
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2010-01-18 22:28:36 +0100 (Mon, 18 Jan 2010)
Last Changed Rev: 2877

Memory Usage: 225 MB / 254 MB (74 MB allocated, but free)
Java version: 1.6.0_16

Dataset consistency test:
No problems found


Plugins: wmsplugin,remotecontrol,validator
Plugin wmsplugin Version: 19507
Plugin remotecontrol Version: 19471
Plugin validator Version: 19485

Attachments (0)

Change History (5)

comment:1 in reply to:  description Changed 10 years ago by skyper

Replying to augustus.kling@…:

When I try to upload I get a message box stating “There are unresolved conflicts in layer 'Data Layer 1'. You have to resolve them first”. Before this I synchronized the entire dataset when requested to do so on failed upload.

However opening the conflict list (sidebar panel) does not show any conflicts.

Have a look at #4406. First open the conflict-list (sidebar) and then merge/update. Maybe it works this way (did it for me)

comment:2 Changed 10 years ago by augustus.kling@…

These bugs seem to be unrelated.

In my case the problem was that the ConflictListDialog was empty although a conflict existed. Therefore I could not open the ConflictDialog to resolve the conflict.

I could resolve conflicts at other times so I guess the bug has something to do with the loaded data. Unfortunately it is not possible in JOSM to save files containing conflicts to examine further. I should also have mentioned that I made heavy use of the WMS and validator plugin (do they affect JOSM's internal storage of data?).

comment:3 Changed 10 years ago by jttt

Resolution: fixed
Status: newclosed

(In [2880]) Fixed #4411 Can't upload due to conflicts, but conflict list is empty

comment:4 Changed 10 years ago by jttt

Problem was that the conflict list dialog wasn't updated if it was shown after conflicts were created. The dataset consistency test warning was false alarm (fixed in r2879).

comment:5 Changed 10 years ago by augustus.kling@…

Thanks for fixing this.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
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.