{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":368305582,"defaultBranch":"main","name":"chapel","ownerLogin":"ShreyasKhandekar","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-05-17T19:51:21.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/60454060?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1726619920.0","currentOid":""},"activityList":{"items":[{"before":"0f76fb91d2b807a4cd8848bcd9355377457cc1bd","after":"b301fa0753984dec7e533787a4cfd897c9fb6298","ref":"refs/heads/main","pushedAt":"2024-09-20T18:10:45.000Z","pushType":"push","commitsCount":72,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"CHANGES.md for Chapel 2.2 (#25879)\n\n[reviewed by @DanilaFe and @mppf — thanks!]\r\n\r\nThis is the (reasonably complete) list of CHANGES for Chapel 2.2. Thanks\r\nto everyone for all the hard work!","shortMessageHtmlLink":"CHANGES.md for Chapel 2.2 (chapel-lang#25879)"}},{"before":"852cf0a2b75402eaaabf9267290dc35bdfd6bf6f","after":"28641b9a05c4244c84976149fef38b783427cf6c","ref":"refs/heads/sortModuleDocsUpdate","pushedAt":"2024-09-18T18:57:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Feedback from review\n\nPart 2\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Feedback from review"}},{"before":"d2b2efa5f0983dedffdfa3143ffd721a208449ba","after":"852cf0a2b75402eaaabf9267290dc35bdfd6bf6f","ref":"refs/heads/sortModuleDocsUpdate","pushedAt":"2024-09-18T17:34:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Changes based on review\n\nPart 1\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Changes based on review"}},{"before":null,"after":"d2b2efa5f0983dedffdfa3143ffd721a208449ba","ref":"refs/heads/sortModuleDocsUpdate","pushedAt":"2024-09-18T00:38:40.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Update Sort module documentation\n\nUpdate the sort module documentation based on the work done in the sort module stabilization subteam.\n\nOn a high level\n- Added a short intro with a few examples of using `proc sort`, before this change it was a bit wierd to just see Comparators as the first thing in the sort module docs.\n- Edited the comparators section to mention the new prescribed way to create and use custom comparators using the newly created interfaces.\n- Went over the rest of the doc to update other things that have changed like argument names\n\nThis includes work done in the following PRs:\n\n chapel-lang/chapel#25863\n chapel-lang/chapel#25852\n chapel-lang/chapel#25821\n chapel-lang/chapel#25817\n chapel-lang/chapel#25813\n chapel-lang/chapel#25807\n chapel-lang/chapel#25705\n chapel-lang/chapel#25703\n chapel-lang/chapel#25699\n chapel-lang/chapel#25698\n chapel-lang/chapel#25586\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Update Sort module documentation"}},{"before":"9c0f91cee4ffe4ae50d2be3e0a19ded4a535bdb6","after":"0f76fb91d2b807a4cd8848bcd9355377457cc1bd","ref":"refs/heads/main","pushedAt":"2024-09-17T21:05:27.000Z","pushType":"push","commitsCount":12,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"annotations for release-over-release 2.2 triage (#25953)\n\n- moved qthreads update/patch annotations to apply to all chapcs graphs\r\n(since they seem to impact a slew of graphs and not just the 2 I\r\npreviously had annotated).\r\n- annotation for \"Avoid array allocation for moving to equal domain\" to\r\n\"array return performance\" graph\r\n- annotation for AVE to apply to miniMD graph\r\n- annotation for AVE on \"2D Heat Solver\" graph\r\n- annotation for \"Stencil Distribution performance improvements\" to NPB\r\nMG Time Size B","shortMessageHtmlLink":"annotations for release-over-release 2.2 triage (chapel-lang#25953)"}},{"before":"64b8a6d12cbd564be0a504231b9b5f051454be1b","after":"9c0f91cee4ffe4ae50d2be3e0a19ded4a535bdb6","ref":"refs/heads/main","pushedAt":"2024-09-12T21:42:08.000Z","pushType":"push","commitsCount":73,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Add support for qualified interface access (#25924)\n\nCloses https://github.com/chapel-lang/chapel/issues/25829.\r\n\r\nStrangely, even though we have an `isym` when building the class\r\nhierarchy, I chose to use the symbol's name to construct an `implements`\r\nstatement. This works when the name is available in scope without\r\nqualification, but not when qualified access is used. The principled\r\nsolution is to allow interface statements to be constructed using a\r\nknown interface symbol. This PR does that, and switches the class\r\nhierarchy logic to avoid using a name.\r\n\r\nReviewed by @jabraham17 -- thanks!\r\n\r\n## Testing\r\n- [x] paratest","shortMessageHtmlLink":"Add support for qualified interface access (chapel-lang#25924)"}},{"before":"3284b94298461acb1ef0bd7c712243d0d86125c5","after":"64b8a6d12cbd564be0a504231b9b5f051454be1b","ref":"refs/heads/main","pushedAt":"2024-09-10T17:13:10.000Z","pushType":"push","commitsCount":43,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Remove FI_DELIVERY_COMPLETE in message-order-fence mode (#25921)\n\nThe Cassini-1 NIC does not support FI_DELIVERY_COMPLETE and specifying\r\nit can cause hangs. See Cray/chapel-private#1661 and\r\nCray/chapel-private#6677 for details.\r\n\r\n[Reviewed by @jabraham17, thank you.]","shortMessageHtmlLink":"Remove FI_DELIVERY_COMPLETE in message-order-fence mode (chapel-lang#…"}},{"before":"8b9cfac749c6ec04cf80fc3c77afe4de7b9baebf","after":"3284b94298461acb1ef0bd7c712243d0d86125c5","ref":"refs/heads/main","pushedAt":"2024-09-06T18:02:19.000Z","pushType":"push","commitsCount":33,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Add a test for @gpu.itersPerThread (#25895)\n\nAdd a test for the @gpu.itersPerThread feature added in #25855.\r\n\r\nWhile there, minor fixes to ensure that itersPerThread-attributed kernels\r\nrun on GPUs:\r\n\r\n* Instead of adding a CForLoop, add a WhileDoLoop, to avoid calls to chpl_error\r\n that would be inserted incleanupForeachLoopsGuaranteedToRunOnCpu().\r\n\r\n* Instead of PRIM_ASSIGN use PRIM_MOVE, as normalizing the former\r\n introduces new temps.\r\n\r\nTrivial, not reviewed.","shortMessageHtmlLink":"Add a test for @gpu.itersPerThread (chapel-lang#25895)"}},{"before":null,"after":"e068ead6b6a2db60f4e91f3c707c25990f6c7e4e","ref":"refs/heads/update-unstable-anon-script-22","pushedAt":"2024-09-05T23:32:49.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Unstable anon script special case \n\nThis adds a few things to the unstable warning anonymizer script in\norder to update it for the 2.2 release.\n\n- Add handling for a warning starting with the word ``:\n previously, we were assuming that a warning either starts with a\nChapel file name (like `foo.chpl`) or with `` but a\nnew unstable warning was added this release which starts with `` and it also doesn't have a number following it (the other two\nhave numbers following them which indicate a line number of argument\nnumber)\n- Add special case handling for the ambiguous modules warning (which is\n what also required the change from the 1st bullet) since it exposes\nimplementation details (module names), we scrub these names now.\n- Add testing for the special case\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Unstable anon script special case <command line>"}},{"before":"382fdc9dc46ed0a51741b9c1df69341bd6c83bc9","after":"8b9cfac749c6ec04cf80fc3c77afe4de7b9baebf","ref":"refs/heads/main","pushedAt":"2024-09-05T20:54:47.000Z","pushType":"push","commitsCount":56,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Fix incorrect resolution of outer variable when method exists with the same name (#25878)\n\nResolves #25551\r\nResolves #22918\r\n\r\nThis PR adjusts the way the new scope resolver handles looking for\r\nmatches for methods in order to resolve problems with incorrect matches\r\nto methods interfering with finding an outer variable, which is the\r\nproblem that occurs in #25551.\r\n\r\nWhat is going wrong in #25551 is that the new scope resolver is 1)\r\nlooking for the innermost match (for an identifier) and 2) searching\r\nfirst for methods from the definition point of myComparator and its\r\nparents. The result is to find the unrelated `text` method instead of\r\nthe outer variable.\r\n\r\nThis PR resolves the problem by adjusting the scope resolution process\r\nto only consider methods that could be called when considering method\r\nreceiver scopes.\r\n\r\nInstead of pre-computing the receiver scopes and then checking these for\r\nmethods, the lookup process now works with helper objects to call back\r\ninto the scope resolution or full resolution process. There are two\r\ndifferent helper objects for different purposes:\r\n1. a `MethodLookupHelper` provides a way to access the scopes that\r\nshould be checked for methods/fields and also provides a way to check if\r\nthe receiver is applicable\r\n2. a `ReceiverScopeHelper` provides a way to get a `MethodLookupHelper`\r\nthat corresponds to the receiver type for a particular method ID (and at\r\nthat point, the scopes from the `MethodLookupHelper` should be checked\r\nfor applicable methods)\r\n\r\nThere are two implementations of each of these -- one that uses\r\nsimplified rules and works without types (for use with the new scope\r\nresolution, which is currently enabled in production) -- and one that\r\nuses the full type system.\r\n\r\nReviewed by @benharsh - thanks!\r\n\r\n- [x] full comm=none testing","shortMessageHtmlLink":"Fix incorrect resolution of outer variable when method exists with th…"}},{"before":"fa322272acf6de2e301e343cf816b3fb871dec0e","after":"382fdc9dc46ed0a51741b9c1df69341bd6c83bc9","ref":"refs/heads/main","pushedAt":"2024-09-04T22:25:45.000Z","pushType":"push","commitsCount":322,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Improve errors for missue of `Sort` with arrays and domains (#25863)\n\nImproves the errors thrown by the Sort module (and .sorted() method)\r\nwhen it is used incorrectly by passing unsupported array.domain types.\r\n\r\nThis PR also adds a warning to `assocDomain.sorted()`, but it does not\r\ndeprecate it to maintain backwards compatibility.\r\n\r\n- [x] tested with a full paratest with/without comm\r\n- [x] checked that docs build and render properly\r\n\r\nResolves https://github.com/chapel-lang/chapel/issues/25109\r\n\r\n[Reviewed by @ShreyasKhandekar]","shortMessageHtmlLink":"Improve errors for missue of Sort with arrays and domains (chapel-l…"}},{"before":"0448cc2f6cf08969d2924493fc7777826379a869","after":"fa322272acf6de2e301e343cf816b3fb871dec0e","ref":"refs/heads/main","pushedAt":"2024-08-27T23:21:48.000Z","pushType":"push","commitsCount":125,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Dyno: Clean up usage of postOrderId numbers (#25822)\n\nDo not compare postOrderIds to specific integer values. Instead, use the\r\nmethod ``ID::isSymbolDefiningScope()``.\r\n\r\n[reviewed-by @DanilaFe]","shortMessageHtmlLink":"Dyno: Clean up usage of postOrderId numbers (chapel-lang#25822)"}},{"before":"07ef5b8a7a6a0c98d6a7b1294de36a8c64efa8a2","after":"0448cc2f6cf08969d2924493fc7777826379a869","ref":"refs/heads/main","pushedAt":"2024-08-23T18:33:43.000Z","pushType":"push","commitsCount":38,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Support for reading zarr stores with a custom locale distribution (#25803)\n\nThis PR adds support for customizing the distribution of Zarr stores\r\nacross locales with an `targetLocale` argument. This will help with\r\ngetting reasonable distributions for stores that have small sizes in the\r\nfirst dimension.\r\n\r\nTested locally and on chapdl with none and gasnet comms\r\n\r\nReviewed by: @benharsh","shortMessageHtmlLink":"Support for reading zarr stores with a custom locale distribution (ch…"}},{"before":"b0ae760ff0d10f2b26ae7a0b20eab6fc860d4509","after":"07ef5b8a7a6a0c98d6a7b1294de36a8c64efa8a2","ref":"refs/heads/main","pushedAt":"2024-08-22T21:39:16.000Z","pushType":"push","commitsCount":34,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Fix typo in hip memcpy call (#25784)\n\nFixes a typo introduced in\r\nhttps://github.com/chapel-lang/chapel/pull/24706, where\r\n`chpl_gpu_impl_copy_host_to_device` was replaced with `hipMemcpyDtoD`,\r\nwhen it should have been replaced with `hipMemcpyHtoD`\r\n\r\n- [x] Ran `start_test test/gpu/native` with rocm 5.4.3\r\n- [x] Ran `start_test test/gpu/native` with rocm 6.2\r\n\r\n[Reviewed by @DanilaFe]","shortMessageHtmlLink":"Fix typo in hip memcpy call (chapel-lang#25784)"}},{"before":"f1d49225dd3df95467361b727db001d936096bea","after":"b0ae760ff0d10f2b26ae7a0b20eab6fc860d4509","ref":"refs/heads/main","pushedAt":"2024-08-20T23:03:38.000Z","pushType":"push","commitsCount":102,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Expand Image support to PNG and JPG (#25687)\n\nExpands the Image module support to also work with PNG and JPG. With\r\nthis effort, I have also added the ability to read images with Chapel\r\ncode as well. This allows users to read, write, and manipulate several\r\npopular image formats.\r\n\r\nThe following code will read and write a PNG image.\r\n```chapel\r\nuse Image;\r\n\r\nvar pixels = readImage(\"input.png\", imageType.png);\r\nvar colors = pixelToColor(pixels); // 2D array of RGB values as (int,int,int)\r\n// manipulate the image as needed\r\n\r\nwriteImage(\"output.jpg\", imageType.jpg, colorToPixel(colors));\r\n```\r\n\r\nSummary of Changes\r\n- Bundled `stb_image.h` and `stb_image_write.h`, which are portable,\r\nheader-only C libraries for reading/writing images\r\n- Added PNG and JPG implementations based on `stb_image`, with a\r\nframework to use other implementions in the future if desired.\r\n- Refactored the native BMP implementation to cleanup the code\r\n- Added `pixelToColor`, which does the reverse of `colorToPixel`\r\n\r\n[Reviewed by @DanilaFe]","shortMessageHtmlLink":"Expand Image support to PNG and JPG (chapel-lang#25687)"}},{"before":"6996cf4668b073251f403bd83a3eb7855ea6843b","after":"f1d49225dd3df95467361b727db001d936096bea","ref":"refs/heads/main","pushedAt":"2024-08-15T18:20:21.000Z","pushType":"push","commitsCount":33,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Switch from test proto to test for Arkouda testing (#25767)\n\n[ testing, not reviewed ]\r\n\r\nThe Arkouda testing framework has been consolidated to a single testing\r\nlibrary and with that consolidation there was a change in naming of how\r\nto run the unit tests from `make test-proto` to `make test-python`.","shortMessageHtmlLink":"Switch from test proto to test for Arkouda testing (chapel-lang#25767)"}},{"before":"77f1be30c26a4400b887fa8b7431240346575c92","after":"6996cf4668b073251f403bd83a3eb7855ea6843b","ref":"refs/heads/main","pushedAt":"2024-08-14T20:41:28.000Z","pushType":"push","commitsCount":54,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"More accurately match the other benchmarks in the submitted shootout README (#25759)\n\nBrad pointed out that the other ones used `|` to keep all the versions\r\non the same line. Do that instead of having the separate `-` entries\r\n\r\nTrivial, not reviewed. Looked at the `view file` result to see that it\r\nnow matches","shortMessageHtmlLink":"More accurately match the other benchmarks in the submitted shootout …"}},{"before":"beca35e87d490e3f72f981589c65dfd503a74f99","after":"77f1be30c26a4400b887fa8b7431240346575c92","ref":"refs/heads/main","pushedAt":"2024-08-13T16:55:47.000Z","pushType":"push","commitsCount":82,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Fix module index text for Image, Debugger, OS, and POSIX (#25744)\n\nFixes the module index for the Image, Debugger, OS, and POSIX modules.\r\n\r\nThese were identified in\r\nhttps://github.com/chapel-lang/chapel/issues/25667\r\n\r\nPrior to this they were not rendered correctly because an extra line\r\nexisted after `/*` for the doc strings\r\n\r\n- [x] build docs and validated formatting and that the module index was\r\ncorrect\r\n\r\n[Reviewed by @jeremiah-corrado]","shortMessageHtmlLink":"Fix module index text for Image, Debugger, OS, and POSIX (chapel-lang…"}},{"before":"dcc7b5dc64d6dd65a06d3cf0e604cb0cfcba4cdb","after":"beca35e87d490e3f72f981589c65dfd503a74f99","ref":"refs/heads/main","pushedAt":"2024-08-06T20:03:06.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Allow distributed arrays to be passed to c_addrOf (#25718)\n\n`c_addrOf` returns the address of the array record when an array is\r\npassed. This is a safe operation for distributed arrays and as such it\r\nshould be supported. This PR makes that change.\r\n\r\nContrast this with `c_ptrTo` which returns the array's buffer, which\r\nwould be an unsafe operation for distributed arrays, as you can't really\r\nuse that pointer to access array's elements. I believe the current\r\nlimitation on `c_addrOf` is inherited from `c_ptrTo` out of abundance of\r\ncaution.\r\n\r\nContext for this is the need for expanding array view elision (AVE) to\r\ndistributed arrays. AVE uses C pointers in lieu of `ref` fields. To\r\nsupport AVE for distributed arrays, we want to be able to get the\r\naddress of the array records.\r\n\r\n[Reviewed by @riftEmber]\r\n\r\nTest\r\n- [x] standard linux64\r\n- [x] gasnet","shortMessageHtmlLink":"Allow distributed arrays to be passed to c_addrOf (chapel-lang#25718)"}},{"before":"d71ff850b2b6bcc12727a2ba6c8fd81eb5b9ccde","after":"dcc7b5dc64d6dd65a06d3cf0e604cb0cfcba4cdb","ref":"refs/heads/main","pushedAt":"2024-08-06T17:00:52.000Z","pushType":"push","commitsCount":34,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"ZarrTest build configuration fixes for MacOS and Windows (#25715)\n\nShould resolve testing failures for correctness-test-darwin-m1,\r\ngasnet.darwin-m1, and correctness-test-cygwin64. The mac failures were\r\ndue to an issue with the deployment version and a missing rpath flag.\r\nThe windows failure was because the PRECOMP script wasn't copying the\r\nshared library because it has extension .dll instead of .so or .dlyd.\r\n\r\nTested ZarrTest locally, on windows testing machine, and m1 testing\r\nmachine, and chapdl.\r\n\r\nReviewed by: @ShreyasKhandekar","shortMessageHtmlLink":"ZarrTest build configuration fixes for MacOS and Windows (chapel-lang…"}},{"before":"3af213d5d40257ad3a65471ea8e5e3cdfc1e0bf0","after":"d71ff850b2b6bcc12727a2ba6c8fd81eb5b9ccde","ref":"refs/heads/main","pushedAt":"2024-08-05T23:44:59.000Z","pushType":"push","commitsCount":140,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Dyno: Fix erroneous error when resolving forwarded method on class value (#25714)\n\nPreviously, CallInitDeinit::handleInFormal would attempt to resolve an\r\nassignment function even if the receiver was a borrowed class. This\r\nresulted in a failure when trying to resolve a forwarded call when the\r\ncorresponding actual was not a class. For example, in the following\r\nprogram:\r\n\r\n```chpl\r\n\r\nclass C {\r\n var x : int;\r\n\r\n proc helper() {\r\n return x;\r\n }\r\n}\r\n\r\nrecord R {\r\n var c = new unmanaged C(5);\r\n\r\n forwarding c;\r\n\r\n proc wrapper() {\r\n return this.helper(); // HERE!\r\n }\r\n}\r\n\r\nproc main() {\r\n var r : R;\r\n var x = r.wrapper();\r\n}\r\n```\r\n\r\nWe would encounter the error:\r\n\r\n```\r\n─── error in bar.chpl:16 [NoMatchingCandidates] ───\r\n Unable to resolve call to '=': no matching candidates.\r\n |\r\n 16 | return this.helper();\r\n |\r\n```\r\n\r\nThis was because CallInitDeinit was incorrectly trying to resolve\r\nassignment between ``R`` and a ``borrowed C``.\r\n\r\n[reviewed-by @riftEmber]","shortMessageHtmlLink":"Dyno: Fix erroneous error when resolving forwarded method on class va…"}},{"before":"8ad46b8583fec729670816fee1c8aaee1d45ea80","after":"3af213d5d40257ad3a65471ea8e5e3cdfc1e0bf0","ref":"refs/heads/main","pushedAt":"2024-07-30T20:03:11.000Z","pushType":"push","commitsCount":40,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Remove source of `~/.bashrc` in `load-base-deps.bash` (#25673)\n\nThis prevented users from sourcing `util/cron/load-base-deps.bash` in\r\ntheir `.bashrc` (directly or indirectly) on un-Spackified systems, due\r\nto an infinite loop.\r\n\r\nThanks @mppf for identifying this as the cause.\r\n\r\nThis source of `.bashrc` should no longer be necessary with\r\nSpackification; if anything breaks it should be replaced with a better\r\nsolution.\r\n\r\n[reviewed by @DanilaFe , thanks!]","shortMessageHtmlLink":"Remove source of ~/.bashrc in load-base-deps.bash (chapel-lang#25673"}},{"before":"06ed1025814448575540ac90e1c8d615e678434e","after":"8ad46b8583fec729670816fee1c8aaee1d45ea80","ref":"refs/heads/main","pushedAt":"2024-07-26T21:56:38.000Z","pushType":"push","commitsCount":162,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"update cpu-as-device mode for prior PR on ref intent scalars (#25651)\n\nThis should have been done as part of #25647 (which made updates so we\r\ncould have ref intents to scalars in gpuized loops work on AMD). Anyway,\r\nthat PR updated the signature of `chpl_gpu_impl_host_register` (to have\r\nit return the device pointer for the thing you're ref intent'ing) but I\r\nforgot to update it in the `cpu-as-device` implementation. This PR does\r\nthat update.This should have been done as part of #25647 (which made\r\nupdates so we could have ref intents to scalars in gpuized loops work on\r\nAMD). Anyway, that PR updated the signature of\r\n`chpl_gpu_impl_host_register` (to have it return the device pointer for\r\nthe thing you're ref intent'ing) but I forgot to update it in the\r\n`cpu-as-device` implementation. This PR does that update.\r\n\r\nWritten by @stonea. Merged by @jabraham17 late on Friday to prevent build errors","shortMessageHtmlLink":"update cpu-as-device mode for prior PR on ref intent scalars (chapel-…"}},{"before":"e3745ddf29fd67f686e8b59a74fac2be88d9b962","after":"06ed1025814448575540ac90e1c8d615e678434e","ref":"refs/heads/main","pushedAt":"2024-07-22T16:02:46.000Z","pushType":"push","commitsCount":69,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Make the Sort module an official standard module (#25586)\n\nMakes the Sort module an official standard module. This should not be a\r\nuser facing change as package modules and standard modules mostly differ\r\nin name only. However, there are changes to the online documentation.\r\nThis PR adds a blank Sort page to the old location so that there will be\r\nno dead doc links as a result of this change.\r\n\r\nDocs page:\r\n\r\n\r\nResolves https://github.com/chapel-lang/chapel/issues/25083\r\n\r\nTesting\r\n- [x] built and check docs\r\n- [x] paratest with/without comm\r\n\r\n[Reviewed by @ShreyasKhandekar]","shortMessageHtmlLink":"Make the Sort module an official standard module (chapel-lang#25586)"}},{"before":"9815ab5bbad548c2a80534a4c859c52e090bfce4","after":"e3745ddf29fd67f686e8b59a74fac2be88d9b962","ref":"refs/heads/main","pushedAt":"2024-07-15T21:32:08.000Z","pushType":"push","commitsCount":115,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Fix baseline bug for iteration over heterogeneous tuples (#25573)\n\nThis bug was caused by an incorrect usage of PRIM_GET_MEMBER for tuple\r\ncomponents that are references. Instead, use PRIM_GET_MEMBER_VALUE. We\r\ndon't see this in normal production configurations because optimizations\r\neliminated the tuple literal entirely.\r\n\r\n[reviewed-by @DanilaFe]","shortMessageHtmlLink":"Fix baseline bug for iteration over heterogeneous tuples (chapel-lang…"}},{"before":"b3fe06ec9b0efee28f510470285d1bfc078d4e6a","after":"6313b577f8d58da43910e74226137b0312df757e","ref":"refs/heads/gpuArrayInKernelFuture","pushedAt":"2024-07-14T19:11:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Use `kernel_lauch` argument instead of aod/um\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Use kernel_lauch argument instead of aod/um"}},{"before":"e4bb98b0f4a4cae7fa3f1b4a6e07f0f350790b73","after":"b3fe06ec9b0efee28f510470285d1bfc078d4e6a","ref":"refs/heads/gpuArrayInKernelFuture","pushedAt":"2024-07-12T21:38:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Add futures associated with Issue #20290\n\n are some hints as to wy we can't do this today in the `.bad` files\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Add futures associated with Issue chapel-lang#20290"}},{"before":null,"after":"e4bb98b0f4a4cae7fa3f1b4a6e07f0f350790b73","ref":"refs/heads/gpuArrayInKernelFuture","pushedAt":"2024-07-12T21:34:23.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Add futures associated with Issue #20290\n\n are some hints as to wy we can't do this today in the `.bad` files\n\nSigned-off-by: Shreyas Khandekar <60454060+ShreyasKhandekar@users.noreply.github.com>","shortMessageHtmlLink":"Add futures associated with Issue chapel-lang#20290"}},{"before":"4f7a6c305c5b31abb1bd882588cdde5816707fdb","after":"9815ab5bbad548c2a80534a4c859c52e090bfce4","ref":"refs/heads/main","pushedAt":"2024-07-12T21:17:33.000Z","pushType":"push","commitsCount":841,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Re-futurize test using runtime types for type fields (#25542)\n\nIn #22616 I retired this future because it had been relying on some very\r\nold syntax for domain literals. This test happened to pass on my mac,\r\nbut fails in other configurations due to memory issues, so it needs to\r\nbecome a .future again.\r\n\r\n[reviewed-by @DanilaFe]","shortMessageHtmlLink":"Re-futurize test using runtime types for type fields (chapel-lang#25542)"}},{"before":"7b77daaf0e8959d7d090f6bb0dff758bd74b01bb","after":"4f7a6c305c5b31abb1bd882588cdde5816707fdb","ref":"refs/heads/main","pushedAt":"2024-06-27T19:00:10.000Z","pushType":"push","commitsCount":49,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Performance graph updates for 2.1.0 (#25371)\n\nThis is similar to PRs done in previous releases such as:\r\nhttps://github.com/chapel-lang/chapel/pull/24647.","shortMessageHtmlLink":"Performance graph updates for 2.1.0 (chapel-lang#25371)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMFQxODoxMDo0NS4wMDAwMDBazwAAAAS8P9wK","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMFQxODoxMDo0NS4wMDAwMDBazwAAAAS8P9wK","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNi0yN1QxOTowMDoxMC4wMDAwMDBazwAAAARxLCJe"}},"title":"Activity · ShreyasKhandekar/chapel"}