{"action":"opened","issue":{"url":"https://api.github.com/repos/private-octopus/picoquic/issues/120","repository_url":"https://api.github.com/repos/private-octopus/picoquic","labels_url":"https://api.github.com/repos/private-octopus/picoquic/issues/120/labels{/name}","comments_url":"https://api.github.com/repos/private-octopus/picoquic/issues/120/comments","events_url":"https://api.github.com/repos/private-octopus/picoquic/issues/120/events","html_url":"https://github.com/private-octopus/picoquic/issues/120","id":305697237,"number":120,"title":"Segmentation faults not caught by existing tests","user":{"login":"huitema","id":7464128,"avatar_url":"https://avatars0.githubusercontent.com/u/7464128?v=4","gravatar_id":"","url":"https://api.github.com/users/huitema","html_url":"https://github.com/huitema","followers_url":"https://api.github.com/users/huitema/followers","following_url":"https://api.github.com/users/huitema/following{/other_user}","gists_url":"https://api.github.com/users/huitema/gists{/gist_id}","starred_url":"https://api.github.com/users/huitema/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/huitema/subscriptions","organizations_url":"https://api.github.com/users/huitema/orgs","repos_url":"https://api.github.com/users/huitema/repos","events_url":"https://api.github.com/users/huitema/events{/privacy}","received_events_url":"https://api.github.com/users/huitema/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-15T19:54:06Z","updated_at":"2018-03-15T19:54:06Z","closed_at":null,"author_association":"COLLABORATOR","body":"PR #118 fixes a segmentation fault in the decryption of packets. Such issues should have been caught by the test framework, but were not. There seems to be at least three types of missing tests:\r\n\r\n1) Code analysis should have flagged the potential for null pointer execution.\r\n2) Test coverage analysis should have pointed lack of coverage of specific code branches\r\n3) Stress tests should try variations of connection scenarios such as bad certificate, 0-RTT failures, varied parameters, etc."}}
{"actor":{"display_login":"huitema"}}