{"action":"created","issue":{"url":"https://api.github.com/repos/go-qml/qml/issues/170","repository_url":"https://api.github.com/repos/go-qml/qml","labels_url":"https://api.github.com/repos/go-qml/qml/issues/170/labels{/name}","comments_url":"https://api.github.com/repos/go-qml/qml/issues/170/comments","events_url":"https://api.github.com/repos/go-qml/qml/issues/170/events","html_url":"https://github.com/go-qml/qml/issues/170","id":134750772,"number":170,"title":"go-qml is broken under Go 1.6","user":{"login":"vially","id":433598,"avatar_url":"https://avatars.githubusercontent.com/u/433598?v=3","gravatar_id":"","url":"https://api.github.com/users/vially","html_url":"https://github.com/vially","followers_url":"https://api.github.com/users/vially/followers","following_url":"https://api.github.com/users/vially/following{/other_user}","gists_url":"https://api.github.com/users/vially/gists{/gist_id}","starred_url":"https://api.github.com/users/vially/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vially/subscriptions","organizations_url":"https://api.github.com/users/vially/orgs","repos_url":"https://api.github.com/users/vially/repos","events_url":"https://api.github.com/users/vially/events{/privacy}","received_events_url":"https://api.github.com/users/vially/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2016-02-19T02:03:00Z","updated_at":"2016-06-17T19:16:24Z","closed_at":null,"body":"Running the gopher example fails with: `panic: runtime error: cgo argument has Go pointer to Go pointer`.\r\n\r\nMost probably this has to do with the [cgo changes](https://golang.org/doc/go1.6#cgo) present in Go 1.6"},"comment":{"url":"https://api.github.com/repos/go-qml/qml/issues/comments/226857512","html_url":"https://github.com/go-qml/qml/issues/170#issuecomment-226857512","issue_url":"https://api.github.com/repos/go-qml/qml/issues/170","id":226857512,"user":{"login":"binary132","id":936243,"avatar_url":"https://avatars.githubusercontent.com/u/936243?v=3","gravatar_id":"","url":"https://api.github.com/users/binary132","html_url":"https://github.com/binary132","followers_url":"https://api.github.com/users/binary132/followers","following_url":"https://api.github.com/users/binary132/following{/other_user}","gists_url":"https://api.github.com/users/binary132/gists{/gist_id}","starred_url":"https://api.github.com/users/binary132/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/binary132/subscriptions","organizations_url":"https://api.github.com/users/binary132/orgs","repos_url":"https://api.github.com/users/binary132/repos","events_url":"https://api.github.com/users/binary132/events{/privacy}","received_events_url":"https://api.github.com/users/binary132/received_events","type":"User","site_admin":false},"created_at":"2016-06-17T19:16:24Z","updated_at":"2016-06-17T19:16:24Z","body":"Or, you could open the PR against @SjB's fork containing your breaking test.  That way he can fix the breakage in his branch before opening the PR."}}
{"actor":{"display_login":"binary132"}}