{"action":"created","issue":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/151","labels_url":"https://api.github.com/repos/flux-framework/flux-core/issues/151/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/flux-core/issues/151/comments","events_url":"https://api.github.com/repos/flux-framework/flux-core/issues/151/events","html_url":"https://github.com/flux-framework/flux-core/issues/151","id":61110396,"number":151,"title":"kvs watch callbacks called when sibling object changes","user":{"login":"garlick","id":169947,"avatar_url":"https://avatars.githubusercontent.com/u/169947?v=3","gravatar_id":"","url":"https://api.github.com/users/garlick","html_url":"https://github.com/garlick","followers_url":"https://api.github.com/users/garlick/followers","following_url":"https://api.github.com/users/garlick/following{/other_user}","gists_url":"https://api.github.com/users/garlick/gists{/gist_id}","starred_url":"https://api.github.com/users/garlick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garlick/subscriptions","organizations_url":"https://api.github.com/users/garlick/orgs","repos_url":"https://api.github.com/users/garlick/repos","events_url":"https://api.github.com/users/garlick/events{/privacy}","received_events_url":"https://api.github.com/users/garlick/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-13T15:54:04Z","updated_at":"2015-03-13T17:15:48Z","closed_at":null,"body":"From @lipari \r\n> The sched comms module registers two callbacks, one for changes to` lwj.next-id`.\r\n\r\n> The other callback is the state value registered for every job: `lwj.1.state`,` lwj.2.state`, etc.\r\n\r\n> In my simple test, I only submit one job, and expect callbacks whenever `lwj.1.state` changes.\r\n\r\n> What I'm finding is that both callbacks are called, whenever `lwj.1.state` changes.  The value of the `lwj.next-id` (at every callback) never changes; it's always 2.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/comments/79149685","html_url":"https://github.com/flux-framework/flux-core/issues/151#issuecomment-79149685","issue_url":"https://api.github.com/repos/flux-framework/flux-core/issues/151","id":79149685,"user":{"login":"grondo","id":741970,"avatar_url":"https://avatars.githubusercontent.com/u/741970?v=3","gravatar_id":"","url":"https://api.github.com/users/grondo","html_url":"https://github.com/grondo","followers_url":"https://api.github.com/users/grondo/followers","following_url":"https://api.github.com/users/grondo/following{/other_user}","gists_url":"https://api.github.com/users/grondo/gists{/gist_id}","starred_url":"https://api.github.com/users/grondo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grondo/subscriptions","organizations_url":"https://api.github.com/users/grondo/orgs","repos_url":"https://api.github.com/users/grondo/repos","events_url":"https://api.github.com/users/grondo/events{/privacy}","received_events_url":"https://api.github.com/users/grondo/received_events","type":"User","site_admin":false},"created_at":"2015-03-13T17:15:48Z","updated_at":"2015-03-13T17:15:48Z","body":"I wonder if something I'm seeing is related. \r\n\r\nLately when running `wreck` jobs, I see multiple callbacks for the `running` state. As with scheduler, `flux-wreckrun` watches `lwj.<id>.state` and reports state changes until `state == \"completed\"` then exits. Each state change should only be reported once, and only rank 0 of the LWJ should update the state (though not inconceivable there could be a bug here).\r\n\r\nI tried to update the lua tests recently with a test that ensures an update to a key in the kvs only invokes the callback once, but I didn't try anything with sibling objects..."}}