{"push_id":1044398008,"size":17,"distinct_size":1,"ref":"refs/heads/unpack_tuple_memleak","head":"a67a5341168a825879206358fad5aa38ea94319c","before":"6d3ec073f5d8cb0dba308e6edb957963c4b86b9a","commits":[{"sha":"b1966bd54639af1a557564764ca5526a959d0222","author":{"email":"2e1153ecd6addcd932bf8cdd29c11fb7dd39bbb6@gmail.com","name":"Ben Harshbarger"},"message":"Adding future for incorrect semantics where ref-return logic always invokes 'ref' case when returning an array, even if the array is only read","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/b1966bd54639af1a557564764ca5526a959d0222"},{"sha":"fd92f27d6c8de230a94ca636815fd5230f98250e","author":{"email":"2e1153ecd6addcd932bf8cdd29c11fb7dd39bbb6@gmail.com","name":"Ben Harshbarger"},"message":"Adding future against bug where indexing into an associative array of arrays always adds an index/element to the outer array, meaning the 'ref' case is always triggered.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/fd92f27d6c8de230a94ca636815fd5230f98250e"},{"sha":"d623830c048233a861e1de7f9ff085acb04113dc","author":{"email":"2e1153ecd6addcd932bf8cdd29c11fb7dd39bbb6@gmail.com","name":"Ben Harshbarger"},"message":"Add future for ref-return issue with sparse array-of-arrays","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/d623830c048233a861e1de7f9ff085acb04113dc"},{"sha":"edc29f1a69d6ea5ebfa4999f9e60d9468e20c375","author":{"email":"9efea9f3e732de9799f8e0cd6a4854f20f095f82@users.noreply.github.com","name":"Michael Ferguson"},"message":"Add some tests for tuples that return arrays","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/edc29f1a69d6ea5ebfa4999f9e60d9468e20c375"},{"sha":"4395ca6dbe133c1c7754a926065df025a4d259fa","author":{"email":"9efea9f3e732de9799f8e0cd6a4854f20f095f82@users.noreply.github.com","name":"Michael Ferguson"},"message":"Merge pull request #3653 from mppf/add-tuple-return-arrays-tests\n\nAdd some tests for returning tuple of arrays\r\n\r\nThese tests are inspired by a bug report from Nikhil, but these\r\nparticular ones pass.\r\n\r\nThe failing case must uses globals, but the test/types/records/ferguson\r\nleak checking doesn't handle globals. However, I think it's a useful\r\naddition to our array/record leak coverage.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/4395ca6dbe133c1c7754a926065df025a4d259fa"},{"sha":"b1c9cf1fb411baa6f81baf6b9afba8ca555b4052","author":{"email":"a739c4f8e636da25cffcf7ae77a3ad0067722ef5@cray.com","name":"Brad Chamberlain"},"message":"Fixing a few things that I caught too late to fix for the release","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/b1c9cf1fb411baa6f81baf6b9afba8ca555b4052"},{"sha":"6141184d918f657f2731124413fd60ba924a2f74","author":{"email":"a739c4f8e636da25cffcf7ae77a3ad0067722ef5@cray.com","name":"Brad Chamberlain"},"message":"Add a 'make checkdocs' rule at top level for developers\n\nThis avoids having to 'cd' to doc/sphinx and do make check and also\nhelps ensure that sphinx is available, as in the top-level 'make docs'\nrule.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/6141184d918f657f2731124413fd60ba924a2f74"},{"sha":"215a394d242ec03da23b99f49292eeabe604d898","author":{"email":"b3066f53d7a0fd3eaa1b657a44ad0856312d2203@users.noreply.github.com","name":"Greg Titus"},"message":"Add an item about defining real-->int conversion details.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/215a394d242ec03da23b99f49292eeabe604d898"},{"sha":"f80dd531a144a76a7adde1b4e770c7a552b97981","author":{"email":"b3066f53d7a0fd3eaa1b657a44ad0856312d2203@users.noreply.github.com","name":"Greg Titus"},"message":"Merge pull request #3656 from gbtitus/spec-TODO-real-int-convert\n\nAdd an item about defining real-->int conversion details.\r\n\r\n(Not reviewed.)","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/f80dd531a144a76a7adde1b4e770c7a552b97981"},{"sha":"441d246132f0a2abfca975207fac634ad698c92b","author":{"email":"a739c4f8e636da25cffcf7ae77a3ad0067722ef5@cray.com","name":"Brad Chamberlain"},"message":"Change this link so that 'make checkdocs' won't complain about it","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/441d246132f0a2abfca975207fac634ad698c92b"},{"sha":"63994b4729ff6f508c19df272351a17f9211e7e6","author":{"email":"2e1153ecd6addcd932bf8cdd29c11fb7dd39bbb6@gmail.com","name":"Ben Harshbarger"},"message":"Simplify arr-ref-return future to just read the first element","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/63994b4729ff6f508c19df272351a17f9211e7e6"},{"sha":"033722ae2506c6e7780083c05560509c4cd5694c","author":{"email":"351a3856f7929dea8d335db7030a747c4f0632e1@users.noreply.github.com","name":"Ben Harshbarger"},"message":"Merge pull request #3661 from benharsh/arr-ref-return-future\n\nFutures for ref-returning arrays\r\n\r\nAdds a few futures that expose bugs with the ref-return logic for arrays, where reading an array always enters the 'ref' case. Associative and Sparse arrays of arrays exhibit incorrect behavior because of this issue, as they formerly relied on the now-deprecated 'setter' feature.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/033722ae2506c6e7780083c05560509c4cd5694c"},{"sha":"4f4b996f9e5e8e59082f2fa9b424abcde5d79ba7","author":{"email":"76b11d3d92bad7a642f7c1b15d8a810ff35b7019@users.noreply.github.com","name":"Brad Chamberlain"},"message":"Merge pull request #3654 from bradcray/post-release-doc-tweaks\n\nFixing a few things that I caught too late to fix for the release\r\n\r\n[reviewed by @ronawho ]\r\n\r\n* I caught the weird wording of the \"can be viewed without a free account\" too late to bother fixing it.\r\n\r\n* I only noticed the duplicate entry on reduction performance after the release, and forgot that I'd optimistically put in a placeholder for the module usage information that I'd meant to remove if it didn't get in.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/4f4b996f9e5e8e59082f2fa9b424abcde5d79ba7"},{"sha":"5b8ffd08625829c7f1e43b463b973e83b48fcb25","author":{"email":"76b11d3d92bad7a642f7c1b15d8a810ff35b7019@users.noreply.github.com","name":"Brad Chamberlain"},"message":"Merge pull request #3658 from bradcray/fix-futures-anchor\n\nChange this link so that 'make checkdocs' won't complain about it\r\n\r\n[reviewed by @ben-albrecht ]\r\n\r\nI'm not entirely sure why, but even though this anchor seems to work, our docs checks don't seem to be happy about it. Examining the way GitHub renders .rst as html, it seems to insert a \"user-content\" string in the \"<a name =\" tag and putting that in makes the link checker happy. Who am I to question...?","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/5b8ffd08625829c7f1e43b463b973e83b48fcb25"},{"sha":"2ab9da890f4004cb4f38c02096f73eb4fd6cfba9","author":{"email":"a739c4f8e636da25cffcf7ae77a3ad0067722ef5@cray.com","name":"Brad Chamberlain"},"message":"At BenA's request, made Makefile targets in doc/sphinx self-hosted\n\nPrior to this commit, top-level sphinx-related Makefile targets\ninvoked the run-in-venv script when building targets in the doc/sphinx\ndirectory, but making targets in doc/sphinx did not.  For convenience,\nthis commit uses run-in-venv within doc/sphinx/Makefile as well.  It\nalso adds a 'checkdocs' target to that Makefile to better mirror the\ntop-level target.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/2ab9da890f4004cb4f38c02096f73eb4fd6cfba9"},{"sha":"197b21ebaac7106df0c8653bbb95bd9015110e70","author":{"email":"76b11d3d92bad7a642f7c1b15d8a810ff35b7019@users.noreply.github.com","name":"Brad Chamberlain"},"message":"Merge pull request #3655 from bradcray/make-checkdocs-top-level\n\nadd 'checkdocs' make targets\r\n\r\n[reviewed by @ben-albrecht ]\r\n\r\nPrior to this commit, it was necessary to run 'make check' on the\r\nsphinx-generated docs from within the docs/sphinx/ directory, and\r\nto have sphinx available in your environment.  This commit adds a\r\ntop-level 'checkdocs' target for developers that is symmetrical to\r\nthe 'docs' target in that it uses run-in-venv to ensure that sphinx is\r\nloaded.\r\n\r\nOn BenA's request, this change also pushes the 'run-in-venv'\r\ninvocations down to the doc/sphinx/Makefile so that 'make docs'\r\ncan be run there without having sphinx in your environment, and\r\nintroduces a 'checkdocs' target to that Makefile for symmetry with\r\nthe top-level Makefile targets.","distinct":false,"url":"https://api.github.com/repos/npadmana/chapel/commits/197b21ebaac7106df0c8653bbb95bd9015110e70"},{"sha":"a67a5341168a825879206358fad5aa38ea94319c","author":{"email":"53aae9c67699e2796b87e992c00a8ee42d1c431a@gmail.com","name":"Nikhil Padmanabhan"},"message":"Merge branch 'master' into unpack_tuple_memleak","distinct":true,"url":"https://api.github.com/repos/npadmana/chapel/commits/a67a5341168a825879206358fad5aa38ea94319c"}]}