[josm-dev] Is the "should upload" logic a little too eager?

[Dirk Stöcker]

On Tue, 1 Jan 2013, Greg Troxel wrote:

> A while ago, I made edits to an area (in JOSM, entirely normally, not
> very large, 20 minutes worth of hand editing), and went to upload them.
> My memory is fuzzy, but I think the upload had trouble, and when I went
> to exit, I got the "should upload" prompt.  So I did (since I knew all
> the changes were my recent edits).   It turns out that the upload
> happened twice, or at least the db had many objects added by me twice.
> (I noticed this running the validator over my whole town.)
>
> Specific suggestions to avoid this kind of trouble:
>
> ** Somehow, when opening a file with un-uploaded changes, show in the
>    command stack at least a representation of what's not yet uploaded.
>    I find that after saving and restarting, that's empty.
>
> ** After an upload which does not complete normally, set a flag that
>    requires an "update modified" operation before another upload can
>    happen (and this needs to persist in the file).

Unfinished uploads are a known problematic issue, which is not easy to 
solve. You will find some tickets regarding that in Trac including 
descriptions why it is not easy. As others already said - bug reporting is 
better in trac tickets than in this list.

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)