{"action":"opened","issue":{"url":"https://api.github.com/repos/aowen87/TicketTester/issues/2272","repository_url":"https://api.github.com/repos/aowen87/TicketTester","labels_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2272/labels{/name}","comments_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2272/comments","events_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2272/events","html_url":"https://github.com/aowen87/TicketTester/issues/2272","id":388601187,"node_id":"MDU6SXNzdWUzODg2MDExODc=","number":2272,"title":"VisIt not reading multi-block/multi-file Silo objects specified with absolute paths","user":{"login":"aowen87","id":11658578,"node_id":"MDQ6VXNlcjExNjU4NTc4","avatar_url":"https://avatars0.githubusercontent.com/u/11658578?v=4","gravatar_id":"","url":"https://api.github.com/users/aowen87","html_url":"https://github.com/aowen87","followers_url":"https://api.github.com/users/aowen87/followers","following_url":"https://api.github.com/users/aowen87/following{/other_user}","gists_url":"https://api.github.com/users/aowen87/gists{/gist_id}","starred_url":"https://api.github.com/users/aowen87/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aowen87/subscriptions","organizations_url":"https://api.github.com/users/aowen87/orgs","repos_url":"https://api.github.com/users/aowen87/repos","events_url":"https://api.github.com/users/aowen87/events{/privacy}","received_events_url":"https://api.github.com/users/aowen87/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/aowen87/TicketTester/milestones/24","html_url":"https://github.com/aowen87/TicketTester/milestone/24","labels_url":"https://api.github.com/repos/aowen87/TicketTester/milestones/24/labels","id":3878233,"node_id":"MDk6TWlsZXN0b25lMzg3ODIzMw==","number":24,"title":"2.5.2","description":null,"creator":{"login":"aowen87","id":11658578,"node_id":"MDQ6VXNlcjExNjU4NTc4","avatar_url":"https://avatars0.githubusercontent.com/u/11658578?v=4","gravatar_id":"","url":"https://api.github.com/users/aowen87","html_url":"https://github.com/aowen87","followers_url":"https://api.github.com/users/aowen87/followers","following_url":"https://api.github.com/users/aowen87/following{/other_user}","gists_url":"https://api.github.com/users/aowen87/gists{/gist_id}","starred_url":"https://api.github.com/users/aowen87/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aowen87/subscriptions","organizations_url":"https://api.github.com/users/aowen87/orgs","repos_url":"https://api.github.com/users/aowen87/repos","events_url":"https://api.github.com/users/aowen87/events{/privacy}","received_events_url":"https://api.github.com/users/aowen87/received_events","type":"User","site_admin":false},"open_issues":1,"closed_issues":32,"state":"open","created_at":"2018-12-06T23:49:50Z","updated_at":"2018-12-07T10:47:13Z","due_on":null,"closed_at":null},"comments":0,"created_at":"2018-12-07T10:47:12Z","updated_at":"2018-12-07T10:47:12Z","closed_at":null,"author_association":"OWNER","body":"This was reported by Katie Lewis.\r\n\r\nOverlink has an option to use absolute paths for various file operations. When this option is used, the multi-block/multi-file objects it creates in Silo have absolute paths for the filename parts of the block names. That means the file is not easily moved but Overlink indeed has tools to move it if need be. Nonetheless, VisIt at least ought to be able to visualize those files when they are indeed at the absolute paths specified. And, Katie tells me this is not working.\r\n\r\nThere is a small chance the problem could be in Silo library itself but I don't think so. Silo does attempt to perform some interpretation of file pathname parts of block object names to hand windows/linux slash swapping. So, its concievable that logic isn't handling absolute paths correctly and causing problems. However, more than likely, I think the problem is in the Silo plugin in VisIt where there is a lot of work going on to interpret the file pathname parts of block names.\r\n\r\nI did not request data to re-produce because I think we can adjust out test clients to produce test data to tickle this bug.\n\n\n\n\n\n-----------------------REDMINE MIGRATION-----------------------\nThis ticket was migrated from Redmine. As such, not all \ninformation was able to be captured in the transition. Below is\na complete record of the original redmine ticket.\n\nTicket number: 852\nStatus: Resolved\nProject: VisIt\nTracker: Bug\nPriority: Normal\nSubject: VisIt not reading multi-block/multi-file Silo objects specified with absolute paths\nAssigned to: Mark Miller\nCategory: \nTarget version: 2.5.2\nAuthor: Mark Miller\nStart: 09/20/2011\nDue date: \n% Done: 0\nEstimated time: 1.0\nCreated: 09/20/2011 01:08 pm\nUpdated: 07/17/2012 11:07 pm\nLikelihood: 2 - Rare\nSeverity: 3 - Major Irritation\nFound in version: 2.3.0\nImpact: \nExpected Use: \nOS: All\nSupport Group: Any\nDescription:\n This was reported by Katie Lewis.\r\n\r\nOverlink has an option to use absolute paths for various file operations. When this option is used, the multi-block/multi-file objects it creates in Silo have absolute paths for the filename parts of the block names. That means the file is not easily moved but Overlink indeed has tools to move it if need be. Nonetheless, VisIt at least ought to be able to visualize those files when they are indeed at the absolute paths specified. And, Katie tells me this is not working.\r\n\r\nThere is a small chance the problem could be in Silo library itself but I don't think so. Silo does attempt to perform some interpretation of file pathname parts of block object names to hand windows/linux slash swapping. So, its concievable that logic isn't handling absolute paths correctly and causing problems. However, more than likely, I think the problem is in the Silo plugin in VisIt where there is a lot of work going on to interpret the file pathname parts of block names.\r\n\r\nI did not request data to re-produce because I think we can adjust out test clients to produce test data to tickle this bug.\n\nComments:\nyeah, this is fixable in the Silo plugin I think. There is an assumption that file paths it reads from MB objects are always relative to the root file. I have a quick fix for this I think. I may not commit until after I return from vacation though.\nI fixed this in SVN trunk update 18769.\n\n"}}
{"actor":{"display_login":"aowen87"}}