You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: amm [Submitted to the original trac issue database at 11.22pm, Friday, 14th May 2010]
Hello,
I was realligning an existing way. Then I split it at a cross junction node and after I accidentally reverted one of the ways, I suddenly had a copy of the old way and the new realligned way, with some odd interconnects between them. (I also did a bunch of other stuff in between)
I did not save the way to not cause potentially "corrupt" data, so I can't say what exactly happened. Also trying to reproduce the test case on api06 did not result in the same behaviour, where it worked correctly.
So I can't currently reproduce the issue, but I thought it was worth reporting it never the less, in case you get similar problem reports and it may help you find a potential bug.
The text was updated successfully, but these errors were encountered:
Reporter: amm
[Submitted to the original trac issue database at 11.22pm, Friday, 14th May 2010]
Hello,
I was realligning an existing way. Then I split it at a cross junction node and after I accidentally reverted one of the ways, I suddenly had a copy of the old way and the new realligned way, with some odd interconnects between them. (I also did a bunch of other stuff in between)
I did not save the way to not cause potentially "corrupt" data, so I can't say what exactly happened. Also trying to reproduce the test case on api06 did not result in the same behaviour, where it worked correctly.
So I can't currently reproduce the issue, but I thought it was worth reporting it never the less, in case you get similar problem reports and it may help you find a potential bug.
The text was updated successfully, but these errors were encountered: