Opened 10 years ago
Closed 10 years ago
#11021 closed defect (irreproducible)
Bug when deleting 0-node-ways in relation editor
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Load Relation 38430 (but the version of mentzdv_NR without members)
- Use Reverter (selected only) for changeset 27376643
- Try to delete the Ways without Nodes in the relation editor
What is the expected result?
Deletion of the 0-Node-Ways
What happens instead?
"This is a bug"-Message
Please provide any additional information below. Attach a screenshot if possible.
Upon request of another mapper I've reverted several relations having complete member deletions. Two cases remained with the bug. In the case described above I've saved the contents to file tram101.osm. After reloading the file, the 0-Node-Ways were gone. Saving the contents again resulted in file tram101_saved_again.osm.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2014-12-29 00:11:17 Last Changed Author: Don-vip Revision: 7906 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2014-12-29 00:13:58 +0100 (Mon, 29 Dec 2014) Last Changed Rev: 7906 Identification: JOSM/1.5 (7906 de) Linux openSUSE 13.2 (Harlequin) (x86_64) Memory Usage: 187 MB / 3641 MB (33 MB allocated, but free) Java version: 1.7.0_71, Oracle Corporation, OpenJDK 64-Bit Server VM Java package: java-1_7_0-openjdk:x86_64-1.7.0.71 Plugins: - PicLayer (30892) - editgpx (30892) - imagery_offset_db (30892) - openvisible (30892) - photo_geotagging (30892) - poly (30892) - reverter (30892) - turnrestrictions (30892) - undelete (30892) - utilsplugin2 (30892)
Attachments (2)
Change History (5)
by , 10 years ago
Attachment: | tram101.osm added |
---|
by , 10 years ago
Attachment: | tram101_saved_again.osm added |
---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
I'm sorry, I didn't save any additional information at that time. There were about 16 changesets and an update in meantime and I don't think I can reproduce it. I propose to close the ticket.
comment:3 by , 10 years ago
Resolution: | → irreproducible |
---|---|
Status: | new → closed |
OK. You can reopen it if you reproduce it again :)
I can't reproduce, can you please copy and paste the full error message including the stacktrace?