{"action":"created","issue":{"url":"https://api.github.com/repos/mavlink/mavlink/issues/743","repository_url":"https://api.github.com/repos/mavlink/mavlink","labels_url":"https://api.github.com/repos/mavlink/mavlink/issues/743/labels{/name}","comments_url":"https://api.github.com/repos/mavlink/mavlink/issues/743/comments","events_url":"https://api.github.com/repos/mavlink/mavlink/issues/743/events","html_url":"https://github.com/mavlink/mavlink/issues/743","id":238799361,"number":743,"title":"[c-library] encode message without modifying  global state","user":{"login":"MikeGitb","id":13987901,"avatar_url":"https://avatars2.githubusercontent.com/u/13987901?v=4","gravatar_id":"","url":"https://api.github.com/users/MikeGitb","html_url":"https://github.com/MikeGitb","followers_url":"https://api.github.com/users/MikeGitb/followers","following_url":"https://api.github.com/users/MikeGitb/following{/other_user}","gists_url":"https://api.github.com/users/MikeGitb/gists{/gist_id}","starred_url":"https://api.github.com/users/MikeGitb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MikeGitb/subscriptions","organizations_url":"https://api.github.com/users/MikeGitb/orgs","repos_url":"https://api.github.com/users/MikeGitb/repos","events_url":"https://api.github.com/users/MikeGitb/events{/privacy}","received_events_url":"https://api.github.com/users/MikeGitb/received_events","type":"User","site_admin":false},"labels":[{"id":843236766,"url":"https://api.github.com/repos/mavlink/mavlink/labels/Upstream","name":"Upstream","color":"d6ed7d","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-06-27T10:03:57Z","updated_at":"2018-02-21T21:40:35Z","closed_at":"2018-02-21T13:38:49Z","author_association":"NONE","body":"Correct me if I'm wrong, but it seems to me as if the c library doesn't provide any way to pack the data of a mavlink message into a `mavlink_message_t` without accessing some global data (namely one of the predefined channels).\r\nThis can be problematic in a multithreaded scenario and/or if the library is used in different parts of the program and the author doesn't make sure they are using different channels.\r\n\r\nHave you considered extending the API, such that a user can simply create and pass a local channel variable to the respective functions"},"comment":{"url":"https://api.github.com/repos/mavlink/mavlink/issues/comments/367482687","html_url":"https://github.com/mavlink/mavlink/issues/743#issuecomment-367482687","issue_url":"https://api.github.com/repos/mavlink/mavlink/issues/743","id":367482687,"user":{"login":"hamishwillee","id":5368500,"avatar_url":"https://avatars2.githubusercontent.com/u/5368500?v=4","gravatar_id":"","url":"https://api.github.com/users/hamishwillee","html_url":"https://github.com/hamishwillee","followers_url":"https://api.github.com/users/hamishwillee/followers","following_url":"https://api.github.com/users/hamishwillee/following{/other_user}","gists_url":"https://api.github.com/users/hamishwillee/gists{/gist_id}","starred_url":"https://api.github.com/users/hamishwillee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hamishwillee/subscriptions","organizations_url":"https://api.github.com/users/hamishwillee/orgs","repos_url":"https://api.github.com/users/hamishwillee/repos","events_url":"https://api.github.com/users/hamishwillee/events{/privacy}","received_events_url":"https://api.github.com/users/hamishwillee/received_events","type":"User","site_admin":false},"created_at":"2018-02-21T21:40:35Z","updated_at":"2018-02-21T21:40:35Z","author_association":"CONTRIBUTOR","body":"@LorenzMeier Perhaps you could give @amilcarlucas access to close these issues? \r\n\r\n@amilcarlucas Not really - I'm just cautious closing issues because I don't have responsibility for MAVLink or a clear policy to work against (I only have \"rights\" because I'm handling some documentation and tooling work). I've closed where obvious mostly because I didn't want your review work to go to waste. \r\n"}}
{"actor":{"display_login":"hamishwillee"}}