[josm-dev] how does the transition to tested work ?

[Ævar Arnfjörð Bjarmason]

On Mon, Mar 8, 2010 at 16:21, Sebastian Klein <bastikln at googlemail.com> wrote:
> Ævar Arnfjörð Bjarmason wrote:
>>> #4401 (JOSM does not remember what has been uploaded) It's more
>>> like an enhancement. Too complicated, will be fixed after release.
>>
>> I've used JOSM a lot recently to upload objects in the "one object at
>>  a time" mode, if it fails with a conflict it will start the whole
>> thing over again (even if it doesn't need to).
>
> This is news to me. Just tried the little "test script" from Karl in
> "one object at a time" mode and it worked well. (I.e. it created a
> conflict and the objects that had been uploaded before, where not marked
> as "modified" anymore.

This is how I've been running into this:

  1. Download data from the OSM server, say 20 ways
  2. While I edit 10 of those 2 have been changed already, so 2/10 conflict
  3. Press "upload" in single-object mode, will upload 1/10, 2/10...
  4. It conflicts at say the 5th object out of 10 and stops the entire
upload process
  6. If I try again it'll still start from 1/10 instead of 1/5

As I said I haven't tracked this down in any detail but it seems that
in some situations JOSM doesn't track the stuff it has uploaded
already when it runs into conflicts during uploads.