{"action":"opened","issue":{"url":"https://api.github.com/repos/leo-editor/leo-editor/issues/1369","repository_url":"https://api.github.com/repos/leo-editor/leo-editor","labels_url":"https://api.github.com/repos/leo-editor/leo-editor/issues/1369/labels{/name}","comments_url":"https://api.github.com/repos/leo-editor/leo-editor/issues/1369/comments","events_url":"https://api.github.com/repos/leo-editor/leo-editor/issues/1369/events","html_url":"https://github.com/leo-editor/leo-editor/issues/1369","id":503018775,"node_id":"MDU6SXNzdWU1MDMwMTg3NzU=","number":1369,"title":"A clone with a subtree is sometimes displayed as a leaf","user":{"login":"SegundoBob","id":1161057,"node_id":"MDQ6VXNlcjExNjEwNTc=","avatar_url":"https://avatars2.githubusercontent.com/u/1161057?v=4","gravatar_id":"","url":"https://api.github.com/users/SegundoBob","html_url":"https://github.com/SegundoBob","followers_url":"https://api.github.com/users/SegundoBob/followers","following_url":"https://api.github.com/users/SegundoBob/following{/other_user}","gists_url":"https://api.github.com/users/SegundoBob/gists{/gist_id}","starred_url":"https://api.github.com/users/SegundoBob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SegundoBob/subscriptions","organizations_url":"https://api.github.com/users/SegundoBob/orgs","repos_url":"https://api.github.com/users/SegundoBob/repos","events_url":"https://api.github.com/users/SegundoBob/events{/privacy}","received_events_url":"https://api.github.com/users/SegundoBob/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-10-05T21:33:15Z","updated_at":"2019-10-05T21:33:15Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"### I can't intentionally produce this bug symptom\r\nI have seen it three or four times, and I panicked every time thinking that I had lost important information.  The first time or two I went about trying to recover the lost information before discovering that the information was still in my .leo file.\r\n\r\nI'm reporting this problem, even though I can't reproduce it, because I think it is a very serious bug in the sense that when a user encounters it, the user will be very upset.\r\n\r\n### All but the last observed occurrence\r\n All I'm sure about for all the occurrences of this symptom is that a clone that should have had a subtree was displayed as a leaf and there was no way to expand the clone to see the subtree.\r\n### My last observed occurrence\r\nThe following is based on the last time I saw this symptom.\r\n\r\nWhen I opened the .leo file, the currently selected node was the clone.  The clone should have had a subtree, but it was shown as a leaf node.  Clicking on the clone, once, twice, many times did not show the subtree.  Selecting another node and then selecting the clone, did not show the subtree.  Scrolling the clone off the screen and back on the screen did not show the subtree.\r\n\r\nAlt+N (next clone) moved the focus to an occurrence of the node much earlier in the outline.  This occurrence was shown with its subtree!\r\n\r\nAlt+N (next clone) moved the focus back to where the node had been shown as a leaf, but now it was correctly shown with its subtree!\r\n\r\n### This occurred with Leo-Editor version\r\n ('devel', 'dc72b05e5609')  running under Ubuntu 18.04"}}
{"actor":{"display_login":"SegundoBob"}}