{"action":"created","issue":{"url":"https://api.github.com/repos/haliphax/rodario/issues/14","repository_url":"https://api.github.com/repos/haliphax/rodario","labels_url":"https://api.github.com/repos/haliphax/rodario/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/haliphax/rodario/issues/14/comments","events_url":"https://api.github.com/repos/haliphax/rodario/issues/14/events","html_url":"https://github.com/haliphax/rodario/issues/14","id":190550367,"number":14,"title":"unique proxy function call signatures","user":{"login":"haliphax","id":745888,"avatar_url":"https://avatars.githubusercontent.com/u/745888?v=3","gravatar_id":"","url":"https://api.github.com/users/haliphax","html_url":"https://github.com/haliphax","followers_url":"https://api.github.com/users/haliphax/followers","following_url":"https://api.github.com/users/haliphax/following{/other_user}","gists_url":"https://api.github.com/users/haliphax/gists{/gist_id}","starred_url":"https://api.github.com/users/haliphax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haliphax/subscriptions","organizations_url":"https://api.github.com/users/haliphax/orgs","repos_url":"https://api.github.com/users/haliphax/repos","events_url":"https://api.github.com/users/haliphax/events{/privacy}","received_events_url":"https://api.github.com/users/haliphax/received_events","type":"User","site_admin":false},"labels":[{"id":302354240,"url":"https://api.github.com/repos/haliphax/rodario/labels/daydream","name":"daydream","color":"c7def8","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-11-20T10:24:26Z","updated_at":"2016-12-14T05:10:49Z","closed_at":null,"body":"In order for a lock to work in a multi-node scenario (perhaps with redis clusters, too), a lock context needs to be completely unique for the `@singular` function call. Two call requests should never have the same lock key, or else the lock may be deleted by the after-hook clean-up function before another node's actors have attempted to acquire it.\r\n\r\nEach `Proxy` and `ClusterProxy` needs to track every method call as it is made, and somehow pass a unique identifier for each to the decorators. Not entirely sure how this is going to work out. Maybe each time it is called, it's actually passing through `__attr__` and being wrapped."},"comment":{"url":"https://api.github.com/repos/haliphax/rodario/issues/comments/266944404","html_url":"https://github.com/haliphax/rodario/issues/14#issuecomment-266944404","issue_url":"https://api.github.com/repos/haliphax/rodario/issues/14","id":266944404,"user":{"login":"haliphax","id":745888,"avatar_url":"https://avatars.githubusercontent.com/u/745888?v=3","gravatar_id":"","url":"https://api.github.com/users/haliphax","html_url":"https://github.com/haliphax","followers_url":"https://api.github.com/users/haliphax/followers","following_url":"https://api.github.com/users/haliphax/following{/other_user}","gists_url":"https://api.github.com/users/haliphax/gists{/gist_id}","starred_url":"https://api.github.com/users/haliphax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haliphax/subscriptions","organizations_url":"https://api.github.com/users/haliphax/orgs","repos_url":"https://api.github.com/users/haliphax/repos","events_url":"https://api.github.com/users/haliphax/events{/privacy}","received_events_url":"https://api.github.com/users/haliphax/received_events","type":"User","site_admin":false},"created_at":"2016-12-14T05:10:49Z","updated_at":"2016-12-14T05:10:49Z","body":"This can be initiated by the `_proxy` method in `ClusterProxy` and by the receiving `@singular` method on the `Actor` instance."}}
{"actor":{"display_login":"haliphax"}}