{"action":"opened","issue":{"url":"https://api.github.com/repos/mpiwg-ft/ft-issues/issues/1","labels_url":"https://api.github.com/repos/mpiwg-ft/ft-issues/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/mpiwg-ft/ft-issues/issues/1/comments","events_url":"https://api.github.com/repos/mpiwg-ft/ft-issues/issues/1/events","html_url":"https://github.com/mpiwg-ft/ft-issues/issues/1","id":108937314,"number":1,"title":"Check whether a communicator/window/file is revoked","user":{"login":"wesbland","id":1561207,"avatar_url":"https://avatars.githubusercontent.com/u/1561207?v=3","gravatar_id":"","url":"https://api.github.com/users/wesbland","html_url":"https://github.com/wesbland","followers_url":"https://api.github.com/users/wesbland/followers","following_url":"https://api.github.com/users/wesbland/following{/other_user}","gists_url":"https://api.github.com/users/wesbland/gists{/gist_id}","starred_url":"https://api.github.com/users/wesbland/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wesbland/subscriptions","organizations_url":"https://api.github.com/users/wesbland/orgs","repos_url":"https://api.github.com/users/wesbland/repos","events_url":"https://api.github.com/users/wesbland/events{/privacy}","received_events_url":"https://api.github.com/users/wesbland/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-29T19:01:17Z","updated_at":"2015-09-29T19:01:17Z","closed_at":null,"body":"There have been multiple requests to have some new functions in ULFM that would look like:\r\n\r\n    MPI_COMM_IS_REVOKED(MPI_Comm comm, int *bool);\r\n    MPI_WIN_IS_REVOKED(MPI_Win win, int *bool);\r\n    MPI_FILE_IS_REVOKED(MPI_File file, int *bool);\r\n\r\nThere has been discussion in the past about thread safety issues that arise from this. Specifically, that a user might have received `MPI_ERR_REVOKED` in one thread but not another. Aurelien suggested that users could set an attribute on the communication object to track this.\r\n\r\nHowever, given the number of times this has come up, this convenience function might be worth adding the extra APIs. I think the thread safety issue is ok as long as we're clear that these functions will never return true until some thread has returned `MPI_ERR_REVOKED` to the user."}}