#4059 closed defect (fixed)
Relation history window does not show up
Reported by: | Nakor | Owned by: | Nakor |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description (last modified by )
If I select a relation and ask for its history, the history is downloaded from OSM but the history window never shows up afterwards.
Closing as worksforme.
Attachments (1)
Change History (8)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from team to Nakor |
---|---|
Status: | new → needinfo |
I can not reproduce that in r2554. What exactly are you doing (step-by-step)?
comment:3 follow-up: 4 Changed 14 years ago by
I cannot reproduce it any more. I do not know if this can be on any help, but this was on an out-dated relation (i.e. a modification that has been modified on OSM in the meantime).
comment:4 Changed 14 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → worksforme |
Status: | needinfo → closed |
Replying to Nakor:
I cannot reproduce it any more. I do not know if this can be on any help, but this was on an out-dated relation (i.e. a modification that has been modified on OSM in the meantime).
comment:5 Changed 14 years ago by
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
I was able to narrow down the issue using the data attached to #4060.
The issue comes up when one tries to show the history of a modified relation that has a new way added. In this case JOSM wants to add the current data to the history as "latest" and RelationMember throws an IllegalArgumentException when the new way (with negative ID) is to be added. And because this is happening in a sub-thread this exception is ignored. (This is probably a bug on its own.)
The attached patch simply gets rid of the exception.
Changed 14 years ago by
Attachment: | HistoryRelationMemberException.patch added |
---|
comment:6 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Ticket #4058 has been marked as a duplicate of this ticket.