{"action":"created","issue":{"url":"https://api.github.com/repos/ndmitchell/shake/issues/287","labels_url":"https://api.github.com/repos/ndmitchell/shake/issues/287/labels{/name}","comments_url":"https://api.github.com/repos/ndmitchell/shake/issues/287/comments","events_url":"https://api.github.com/repos/ndmitchell/shake/issues/287/events","html_url":"https://github.com/ndmitchell/shake/issues/287","id":100947626,"number":287,"title":"Avoid --keep-going message","user":{"login":"nomeata","id":148037,"avatar_url":"https://avatars.githubusercontent.com/u/148037?v=3","gravatar_id":"","url":"https://api.github.com/users/nomeata","html_url":"https://github.com/nomeata","followers_url":"https://api.github.com/users/nomeata/followers","following_url":"https://api.github.com/users/nomeata/following{/other_user}","gists_url":"https://api.github.com/users/nomeata/gists{/gist_id}","starred_url":"https://api.github.com/users/nomeata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nomeata/subscriptions","organizations_url":"https://api.github.com/users/nomeata/orgs","repos_url":"https://api.github.com/users/nomeata/repos","events_url":"https://api.github.com/users/nomeata/events{/privacy}","received_events_url":"https://api.github.com/users/nomeata/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-08-14T06:49:17Z","updated_at":"2015-08-18T20:20:08Z","closed_at":null,"body":"Hi Neil,\r\n\r\nmy build system usually uses --keep-going, because I expect there to be a number of build failures (finding and fixing them is the main purpose of the tool).\r\n\r\nThe message printed upon the first error is confusing to the user. Can it somehow be disabled?\r\n\r\nHere is an example:\r\n```\r\nimport Development.Shake\r\nmain = shakeArgs shakeOptions $ do\r\n    want [\"foo1\",\"foo2\"]\r\n    \"foo1\" %> \\out -> do\r\n        need [\"bar1\"]\r\n        putNormal out\r\n    \"foo2\" %> \\out -> do\r\n        need [\"bar2\"]\r\n        putNormal out\r\n    \"bar1\" %> \\out -> do\r\n        writeFileLines out []\r\n        putNormal out\r\n    \"bar2\" %> \\out -> do\r\n        writeFileLines out []\r\n        putNormal out\r\n```\r\nCurrently, it prints:\r\n```\r\n$ ./staunch-bug --keep-going\r\nbar2\r\nfoo2\r\nError when running Shake build system:\r\n* foo2\r\nError, rule \"foo2\" failed to build file:\r\n  foo2\r\nContinuing due to staunch mode, this error will be repeated later\r\nbar1\r\nfoo1\r\nError when running Shake build system:\r\n* foo2\r\nError, rule \"foo2\" failed to build file:\r\n  foo2\r\n```\r\nNote that the error on foo2 is reported twice, but no other error is.\r\n\r\nI would rather like to see either\r\n```\r\n$ ./staunch-bug --keep-going\r\nbar2\r\nfoo2\r\nbar1\r\nfoo1\r\n```\r\n(and I would extend my rules to give better error messages), or\r\n```\r\n$ ./staunch-bug --keep-going\r\nbar2\r\nfoo2\r\nError when running Shake build system:\r\n* foo2\r\nError, rule \"foo2\" failed to build file:\r\n  foo2\r\nbar1\r\nfoo1\r\nError when running Shake build system:\r\n* foo1\r\nError, rule \"foo1\" failed to build file:\r\n  foo1\r\n```"},"comment":{"url":"https://api.github.com/repos/ndmitchell/shake/issues/comments/132338666","html_url":"https://github.com/ndmitchell/shake/issues/287#issuecomment-132338666","issue_url":"https://api.github.com/repos/ndmitchell/shake/issues/287","id":132338666,"user":{"login":"ndmitchell","id":1651197,"avatar_url":"https://avatars.githubusercontent.com/u/1651197?v=3","gravatar_id":"","url":"https://api.github.com/users/ndmitchell","html_url":"https://github.com/ndmitchell","followers_url":"https://api.github.com/users/ndmitchell/followers","following_url":"https://api.github.com/users/ndmitchell/following{/other_user}","gists_url":"https://api.github.com/users/ndmitchell/gists{/gist_id}","starred_url":"https://api.github.com/users/ndmitchell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ndmitchell/subscriptions","organizations_url":"https://api.github.com/users/ndmitchell/orgs","repos_url":"https://api.github.com/users/ndmitchell/repos","events_url":"https://api.github.com/users/ndmitchell/events{/privacy}","received_events_url":"https://api.github.com/users/ndmitchell/received_events","type":"User","site_admin":false},"created_at":"2015-08-18T20:20:08Z","updated_at":"2015-08-18T20:20:08Z","body":"The idea behind giving the first error message is that you want to see it as soon as you can. The idea behind giving it again at the end is because you might have missed it if you have done a lot of things since then. So is showing the same error twice problematic on its own? I could certainly imagine that when building in staunch I show all error messages, that seems consistent and useful, but you'd still get the first error twice - is that a problem?"}}