{"action":"created","issue":{"url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/47","labels_url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/47/comments","events_url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/47/events","html_url":"https://github.com/LeanKit-Labs/wascally/issues/47","id":59091236,"number":47,"title":"use of `batchAck`, and clearing out some messages while other still run?","user":{"login":"derickbailey","id":75190,"avatar_url":"https://avatars.githubusercontent.com/u/75190?v=3","gravatar_id":"","url":"https://api.github.com/users/derickbailey","html_url":"https://github.com/derickbailey","followers_url":"https://api.github.com/users/derickbailey/followers","following_url":"https://api.github.com/users/derickbailey/following{/other_user}","gists_url":"https://api.github.com/users/derickbailey/gists{/gist_id}","starred_url":"https://api.github.com/users/derickbailey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/derickbailey/subscriptions","organizations_url":"https://api.github.com/users/derickbailey/orgs","repos_url":"https://api.github.com/users/derickbailey/repos","events_url":"https://api.github.com/users/derickbailey/events{/privacy}","received_events_url":"https://api.github.com/users/derickbailey/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/LeanKit-Labs/wascally/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":19,"created_at":"2015-02-26T15:47:00Z","updated_at":"2015-02-27T19:18:46Z","closed_at":null,"body":"Regarding the fixes for #24 - it looks like there is a `wascally.batchAck()` method available now. Is that the correct method to use when I want to force acknowledgements to process?\r\n\r\nI'm currently running in to a scenario where I have a very very very long (20+ minute) job running, with 5 other jobs that have completed. The other 5 jobs are sitting in unacked mode in rabbitmq, in spite of the work having been completed already.\r\n\r\nIn my scenario, it looks like Wascally is not processing the `ack` on those 5 messages, due to the 1 message that remains unack'd. Is that correct?\r\n\r\nAssuming that is correct, will a call to `wascally.batchAck()` force the ack of those 5 messages to process, while the last one still runs?\r\n\r\nalso - there's not any documentation for the batchAck method that I can see."},"comment":{"url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/comments/76454331","html_url":"https://github.com/LeanKit-Labs/wascally/issues/47#issuecomment-76454331","issue_url":"https://api.github.com/repos/LeanKit-Labs/wascally/issues/47","id":76454331,"user":{"login":"derickbailey","id":75190,"avatar_url":"https://avatars.githubusercontent.com/u/75190?v=3","gravatar_id":"","url":"https://api.github.com/users/derickbailey","html_url":"https://github.com/derickbailey","followers_url":"https://api.github.com/users/derickbailey/followers","following_url":"https://api.github.com/users/derickbailey/following{/other_user}","gists_url":"https://api.github.com/users/derickbailey/gists{/gist_id}","starred_url":"https://api.github.com/users/derickbailey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/derickbailey/subscriptions","organizations_url":"https://api.github.com/users/derickbailey/orgs","repos_url":"https://api.github.com/users/derickbailey/repos","events_url":"https://api.github.com/users/derickbailey/events{/privacy}","received_events_url":"https://api.github.com/users/derickbailey/received_events","type":"User","site_admin":false},"created_at":"2015-02-27T19:18:46Z","updated_at":"2015-02-27T19:18:46Z","body":"I'd like to move this conversation over to PR #49 to start code reviewing and cleaning up anything I did wrong, handle any missing work (like documentation), etc. If that sounds good to you, @arobson, go ahead and close this ticket."}}