{"push_id":652286634,"size":2,"distinct_size":2,"ref":"refs/heads/2.11.x","head":"1374f114a3b5e781361294891538f5b3e0df48ac","before":"f1d7423ed41f516f9db8abd2364b764109150b6f","commits":[{"sha":"3ecbe596faf9f7b103856d3298eb0325bd5dc294","author":{"email":"8287c3bf2f3045ed7dda958850d2b0fdb9e67898@gmail.com","name":"Jason Zaugg"},"message":"SI-9282 Avoid obscuring an exception during classfile parsing\n\nBased on analysis of a stack trace in this bug report, I identified\na code path in `ClassfileParser` that can lead to an NPE in its\nexception handling code. If `val in = new AbstractFileReader(file)`\nthrows (e.g during its construction in which it eagerly reads the\nfile `val buf: Array[Byte] = file.toByteArray`), the call to\n`in.file` in `handleError` will NPE.\n\nThis commit stores the active file directly a field in ClassfileParser\nand uses this in the error reporting.","distinct":true,"url":"https://api.github.com/repos/scala/scala/commits/3ecbe596faf9f7b103856d3298eb0325bd5dc294"},{"sha":"1374f114a3b5e781361294891538f5b3e0df48ac","author":{"email":"c4c4cd0781e8a49d848921386970d334ffda1135@typesafe.com","name":"Lukas Rytz"},"message":"Merge pull request #4469 from retronym/ticket/9282\n\nSI-9282 Avoid obscuring an exception during classfile parsing","distinct":true,"url":"https://api.github.com/repos/scala/scala/commits/1374f114a3b5e781361294891538f5b3e0df48ac"}]}