{"action":"created","issue":{"url":"https://api.github.com/repos/Soostone/katip/issues/34","repository_url":"https://api.github.com/repos/Soostone/katip","labels_url":"https://api.github.com/repos/Soostone/katip/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/Soostone/katip/issues/34/comments","events_url":"https://api.github.com/repos/Soostone/katip/issues/34/events","html_url":"https://github.com/Soostone/katip/issues/34","id":164894104,"number":34,"title":"Handle scribe interleaves concurrent logs","user":{"login":"MichaelXavier","id":15840,"avatar_url":"https://avatars.githubusercontent.com/u/15840?v=3","gravatar_id":"","url":"https://api.github.com/users/MichaelXavier","html_url":"https://github.com/MichaelXavier","followers_url":"https://api.github.com/users/MichaelXavier/followers","following_url":"https://api.github.com/users/MichaelXavier/following{/other_user}","gists_url":"https://api.github.com/users/MichaelXavier/gists{/gist_id}","starred_url":"https://api.github.com/users/MichaelXavier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MichaelXavier/subscriptions","organizations_url":"https://api.github.com/users/MichaelXavier/orgs","repos_url":"https://api.github.com/users/MichaelXavier/repos","events_url":"https://api.github.com/users/MichaelXavier/events{/privacy}","received_events_url":"https://api.github.com/users/MichaelXavier/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Soostone/katip/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-07-11T17:44:27Z","updated_at":"2016-08-05T22:47:53Z","closed_at":null,"body":"If you have concurrent logs going to a handle scribe, they get interleaved in the file. I'm not sure if we can get away with setting the handle buffering to line buffering or if we'll need to set up a write queue like we have in `katip-elasticsearch` to linearize the logs."},"comment":{"url":"https://api.github.com/repos/Soostone/katip/issues/comments/237983555","html_url":"https://github.com/Soostone/katip/issues/34#issuecomment-237983555","issue_url":"https://api.github.com/repos/Soostone/katip/issues/34","id":237983555,"user":{"login":"MichaelXavier","id":15840,"avatar_url":"https://avatars.githubusercontent.com/u/15840?v=3","gravatar_id":"","url":"https://api.github.com/users/MichaelXavier","html_url":"https://github.com/MichaelXavier","followers_url":"https://api.github.com/users/MichaelXavier/followers","following_url":"https://api.github.com/users/MichaelXavier/following{/other_user}","gists_url":"https://api.github.com/users/MichaelXavier/gists{/gist_id}","starred_url":"https://api.github.com/users/MichaelXavier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MichaelXavier/subscriptions","organizations_url":"https://api.github.com/users/MichaelXavier/orgs","repos_url":"https://api.github.com/users/MichaelXavier/repos","events_url":"https://api.github.com/users/MichaelXavier/events{/privacy}","received_events_url":"https://api.github.com/users/MichaelXavier/received_events","type":"User","site_admin":false},"created_at":"2016-08-05T22:47:53Z","updated_at":"2016-08-05T22:47:53Z","body":"@sopvop I did some benchmarking (not included in commit) and was pretty happy with the simplest thing I could think of, just an mvar lock. As you can expect, this has minimal overhead that scales up as more concurrent writes are added. Do you think this is good enough for a v1 effort? I didn't want to get into managing a worker thread with channels if a simple mvar would do."}}
{"actor":{"display_login":"MichaelXavier"}}