{"action":"created","issue":{"url":"https://api.github.com/repos/osicat/osicat/issues/15","repository_url":"https://api.github.com/repos/osicat/osicat","labels_url":"https://api.github.com/repos/osicat/osicat/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/osicat/osicat/issues/15/comments","events_url":"https://api.github.com/repos/osicat/osicat/issues/15/events","html_url":"https://github.com/osicat/osicat/issues/15","id":171526510,"number":15,"title":"walk-directory fails because of a single invalid link","user":{"login":"chalaev","id":15344017,"avatar_url":"https://avatars.githubusercontent.com/u/15344017?v=3","gravatar_id":"","url":"https://api.github.com/users/chalaev","html_url":"https://github.com/chalaev","followers_url":"https://api.github.com/users/chalaev/followers","following_url":"https://api.github.com/users/chalaev/following{/other_user}","gists_url":"https://api.github.com/users/chalaev/gists{/gist_id}","starred_url":"https://api.github.com/users/chalaev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chalaev/subscriptions","organizations_url":"https://api.github.com/users/chalaev/orgs","repos_url":"https://api.github.com/users/chalaev/repos","events_url":"https://api.github.com/users/chalaev/events{/privacy}","received_events_url":"https://api.github.com/users/chalaev/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-08-16T21:49:41Z","updated_at":"2016-08-17T16:53:37Z","closed_at":null,"body":"When I recursively scan a directory using osicat:walk-directory\r\n(e.g., in https://github.com/chalaev/esy/blob/master/main.lisp)\r\nthe whole scan procedure fails because of a single invalid\r\nsoft link somewhere in the subdirectory tree.\r\nI suggest a quick (and probably not the best one) patch fixing the problem, see\r\nhttps://github.com/chalaev/esy/tree/master/osicat"},"comment":{"url":"https://api.github.com/repos/osicat/osicat/issues/comments/240475066","html_url":"https://github.com/osicat/osicat/issues/15#issuecomment-240475066","issue_url":"https://api.github.com/repos/osicat/osicat/issues/15","id":240475066,"user":{"login":"Ferada","id":13713,"avatar_url":"https://avatars.githubusercontent.com/u/13713?v=3","gravatar_id":"","url":"https://api.github.com/users/Ferada","html_url":"https://github.com/Ferada","followers_url":"https://api.github.com/users/Ferada/followers","following_url":"https://api.github.com/users/Ferada/following{/other_user}","gists_url":"https://api.github.com/users/Ferada/gists{/gist_id}","starred_url":"https://api.github.com/users/Ferada/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ferada/subscriptions","organizations_url":"https://api.github.com/users/Ferada/orgs","repos_url":"https://api.github.com/users/Ferada/repos","events_url":"https://api.github.com/users/Ferada/events{/privacy}","received_events_url":"https://api.github.com/users/Ferada/received_events","type":"User","site_admin":false},"created_at":"2016-08-17T16:53:37Z","updated_at":"2016-08-17T16:53:37Z","body":"@chalaev I agree with your reasoning. I haven't checked the rest of osicat for matter, but perhaps another flag like `:if-does-not-exists` (so `:if-cannot-access`) would match the current functions a bit more? Possibly also reraising with `cerror` so it can be caught by user code."}}
{"actor":{"display_login":"Ferada"}}