{"action":"created","issue":{"url":"https://api.github.com/repos/nextflow-io/nextflow/issues/211","repository_url":"https://api.github.com/repos/nextflow-io/nextflow","labels_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/211/labels{/name}","comments_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/211/comments","events_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/211/events","html_url":"https://github.com/nextflow-io/nextflow/issues/211","id":169698184,"number":211,"title":"Add caching hashes to new log command","user":{"login":"mes5k","id":492641,"avatar_url":"https://avatars.githubusercontent.com/u/492641?v=3","gravatar_id":"","url":"https://api.github.com/users/mes5k","html_url":"https://github.com/mes5k","followers_url":"https://api.github.com/users/mes5k/followers","following_url":"https://api.github.com/users/mes5k/following{/other_user}","gists_url":"https://api.github.com/users/mes5k/gists{/gist_id}","starred_url":"https://api.github.com/users/mes5k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mes5k/subscriptions","organizations_url":"https://api.github.com/users/mes5k/orgs","repos_url":"https://api.github.com/users/mes5k/repos","events_url":"https://api.github.com/users/mes5k/events{/privacy}","received_events_url":"https://api.github.com/users/mes5k/received_events","type":"User","site_admin":false},"labels":[{"id":33572982,"url":"https://api.github.com/repos/nextflow-io/nextflow/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-08-05T21:16:51Z","updated_at":"2016-11-14T23:13:36Z","closed_at":null,"body":"It would be great if we could add a 'verbose' mode to the new log command that will print the hash values and data that was hashed for each task cache to help debug which changes are triggering a task to either use the cache or re-run.  One idea is print things in a such a way that we can simply diff the logs of different runs to see what's changed.\r\n\r\nThis feature request comes to mind because I'm currently struggling with a pipeline where a very long running process keeps re-running, even though as far as I can tell nothing before it changes. I've stared at `-trace nextflow.processor.TaskProcessor` logs quite a bit, but with only limited success.\r\n"},"comment":{"url":"https://api.github.com/repos/nextflow-io/nextflow/issues/comments/260494853","html_url":"https://github.com/nextflow-io/nextflow/issues/211#issuecomment-260494853","issue_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/211","id":260494853,"user":{"login":"mes5k","id":492641,"avatar_url":"https://avatars.githubusercontent.com/u/492641?v=3","gravatar_id":"","url":"https://api.github.com/users/mes5k","html_url":"https://github.com/mes5k","followers_url":"https://api.github.com/users/mes5k/followers","following_url":"https://api.github.com/users/mes5k/following{/other_user}","gists_url":"https://api.github.com/users/mes5k/gists{/gist_id}","starred_url":"https://api.github.com/users/mes5k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mes5k/subscriptions","organizations_url":"https://api.github.com/users/mes5k/orgs","repos_url":"https://api.github.com/users/mes5k/repos","events_url":"https://api.github.com/users/mes5k/events{/privacy}","received_events_url":"https://api.github.com/users/mes5k/received_events","type":"User","site_admin":false},"created_at":"2016-11-14T23:13:36Z","updated_at":"2016-11-14T23:13:36Z","body":"Hi Paolo, here's a preliminary patch that logs the hashes to a file using SLF4J/Logback markers:  https://github.com/mes5k/nextflow/tree/log_hashes\r\n\r\nThe main problem is that it currently always creates a \"hashes\" file, even if -dump-hashes isn't set.   I don't see an immediately obvious way of getting the -dump-hashes flag from CmdRun into LoggerHelper apart from adding it to CliOptions, which doesn't seem right.  If you can provide me some pointers I'll see what I can do.\r\n\r\nOtherwise, I'd say that if you want to add additional markers then some additional refactoring will probably also be useful.  \r\n\r\nAnd tests.  :)"}}
{"actor":{"display_login":"mes5k"}}