| 5 | | Another thing, how did you see which way was the way with the faulty way nodes? Maybe if I delete that specific way the changeset might work regularly. |
| | 5 | 1. The error message and the validator tool: |
| | 6 | I apparently isolated what causes the error message ( "An unexpected exception occured. This is always a coding error. If you are running the latest version of JOSM, please consider being kind and file a bug report."). It is an issue with the validator tool, where it can't handle nodes which do not have coordinates. There are around 10 nodes without coordinates in my changeset. Once you delete those nodes the validator tool works normally and the error message doesn't show up anymore. |
| | 7 | |
| | 8 | 2. The reverter plugin bug(s): |
| | 9 | i) I assume the reverter plugin creates/retrieves: |
| | 10 | a) nodes without coordinates as mentioned above, and |
| | 11 | b) "phantom" ways, which have 0 nodes and are not visible on the map, even if you search for them by their id numbers, yet remain as members in relations, causing the server to detect the issue. Once you remove these phantom ways from the relations the problem is solved. Since the nodes neither the ways are directly visible, I couldn't find a link between them (maybe the nodes were part of the ways). |
| | 12 | |
| | 13 | There also happened repeatedly conflicts, but I believe that is expected since I deleted these faulty objects. |
| | 14 | |
