Newly downloaded ways/segmets not properly connected

[anonymous]

1. Download the data from an area with a long way that stretches out of your view
2. Go to the end of the long way
3. Download data again from server
4. Move connecting node between the two (or more) ways
5. Only the "old" way will move, the "new" way doesn't although it should as it is connected to the node

[framm]

I was able to reproduce this by loading two OSM files in sequence:

<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.4' generator='JOSM'>
  <node id='1' lat='1' lon='1' />
  <node id='2' lat='2' lon='2' />
  <segment id='1' from='1' to='2' />
</osm>

and

<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.4' generator='JOSM'>
  <node id='3' lat='3' lon='3' />
  <node id='2' lat='2' lon='2' />
  <segment id='2' from='2' to='3' />
</osm>

For some reason, node "2" got duplicated on import (the MergeVisitor did detect that it is the same node already present but did not add it to the list of merged nodes, so that a later "fixReferences" step did not modify the new segment to point to the old node). I have fixed that now but a little doubt remains as to why this was not spotted earlier - it seems that problem has been there all along.

Thank you for reporting the bug.