{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":21663285,"defaultBranch":"main","name":"chapel","ownerLogin":"chapel-lang","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-07-09T18:15:54.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/7597261?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715695447.0","currentOid":""},"activityList":{"items":[{"before":"5197efa19c3a76afd016f51c9a14a87465d5a4d9","after":"e8181cd4bf104d76bd680fd19a5fe58450c3138b","ref":"refs/heads/main","pushedAt":"2024-05-31T20:13:45.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"bradcray","name":"Brad Chamberlain","path":"/bradcray","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7536222?s=80&v=4"},"commit":{"message":"Fix leak in new GMP-related test added in #25124 (#25146)\n\n[trivial, not reviewed—thanks to @lydia-duncan for pointing it out]\r\n\r\nI caught all the manual frees that my new GMP tests needed apart from\r\none... :'(","shortMessageHtmlLink":"Fix leak in new GMP-related test added in #25124 (#25146)"}},{"before":"8d03631cf3b56d140548be9a84e8d8c5ade965d9","after":"5197efa19c3a76afd016f51c9a14a87465d5a4d9","ref":"refs/heads/main","pushedAt":"2024-05-31T04:55:43.000Z","pushType":"pr_merge","commitsCount":5,"pusher":{"login":"e-kayrakli","name":"Engin Kayraklioglu","path":"/e-kayrakli","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4141670?s=80&v=4"},"commit":{"message":"Small fixes in GPU runtime (#25144)\n\nWhile preparing for my talk, I bumped into two issues:\r\n\r\n- `unordered` get/put weren't defined for device. This caused\r\ncompilation issues. Note that we never call those similar to base\r\nget/put, but we just need definitions to compile with.\r\n- `chpl_gpu_mem_realloc` was causing trouble in cpu-as-device mode, I\r\nbelieve this might be the first time we tried to create a rank-change\r\nview in this mode. The issue was a misplaced assertion. This PR moves it\r\naround.\r\n\r\n[Reviewed by @DanilaFe]\r\n\r\nTest:\r\n- [x] nvidia\r\n- [x] amd\r\n- [x] cpu\r\n- [x] nvidia+ofi on new tests","shortMessageHtmlLink":"Small fixes in GPU runtime (#25144)"}},{"before":"a1d82103ac8540601e08f5186efe56449a82f120","after":"8d03631cf3b56d140548be9a84e8d8c5ade965d9","ref":"refs/heads/main","pushedAt":"2024-05-29T23:51:53.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"e-kayrakli","name":"Engin Kayraklioglu","path":"/e-kayrakli","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4141670?s=80&v=4"},"commit":{"message":"Add a sub_test filter for known failures on OFI testbed (#25100)\n\nThis is a long-standing sporadic. It is long overdue we add this filter.\r\n\r\n[OK'ed by @jhh67 offline]\r\n\r\nTest:\r\n- [x] `start_test` h","shortMessageHtmlLink":"Add a sub_test filter for known failures on OFI testbed (#25100)"}},{"before":"77ac1b6340e26ceeaf6e7047ef24c0244fdaef3d","after":"a1d82103ac8540601e08f5186efe56449a82f120","ref":"refs/heads/main","pushedAt":"2024-05-29T23:22:43.000Z","pushType":"pr_merge","commitsCount":4,"pusher":{"login":"bradcray","name":"Brad Chamberlain","path":"/bradcray","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7536222?s=80&v=4"},"commit":{"message":"Add mpf_get_str() and mp_exp_t (#25124)\n\n[reviewed by @lydia-duncan]\r\n\r\nThis adds a prototype of the mpf_get_str() routine and a few tests of\r\nit.\r\n\r\nThis routine uses the 'mp_exp_t' type which we have not previously\r\ndefined in GMP.chpl, and which does not seem to have a well-defined size\r\nin the GMP documentation. Here, I've defined it to be `c_long`, which is\r\nwhat it looks like it is in virtually all cases. To make sure we weren't\r\nsetting the user up for trouble, I added an initialization-time check to\r\nmake sure we weren't running on a platform that uses `c_int` instead.\r\nThis feels a little unfortunate, but much easier than dynamically\r\ngenerating the definition of the type as we do for things like `c_int`\r\nor `c_size_t`. If we run into portability problems, we can beef up the\r\nlogic then, and I'm hoping the fact that the module is unstable will\r\nmake this acceptable for now.\r\n\r\nResolves #25082","shortMessageHtmlLink":"Add mpf_get_str() and mp_exp_t (#25124)"}},{"before":"c43a4ab7ed957ab7ae8c3e2dd00b121bb8e00670","after":"77ac1b6340e26ceeaf6e7047ef24c0244fdaef3d","ref":"refs/heads/main","pushedAt":"2024-05-29T23:10:53.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"bradcray","name":"Brad Chamberlain","path":"/bradcray","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7536222?s=80&v=4"},"commit":{"message":"Switch GMP extern varargs procedures to use 'in' intent (#25127)\n\n[reviewed by @mppf]\r\n\r\nThis changes the varargs routines within GMP.chpl to use 'in' intent\r\nrather than default intent. This is motivated by #25089, which noted\r\nthat, without this, our compiler would complain that an argument intent\r\nis required for such vararg arguments (albeit not very clearly) when a\r\nGMP type was passed in. It seems that our only other outstanding test of\r\nthis feature is one that passes in a pointer to a GMP type, which\r\nseemingly doesn't trigger the warning unless the `c_ptrTo()` is removed.\r\nHere, I removed it, as it seemed to be added as a workaround for this\r\nsort of issue to begin with.\r\n\r\nAdded a test to lock in the behavior for the three varargs GMP\r\nprocedures we currently support.\r\n\r\nResolves #25089","shortMessageHtmlLink":"Switch GMP extern varargs procedures to use 'in' intent (#25127)"}},{"before":"61193494463ae0af6ed3fcd4400f611a6bc45302","after":"c43a4ab7ed957ab7ae8c3e2dd00b121bb8e00670","ref":"refs/heads/main","pushedAt":"2024-05-29T21:57:30.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"bmcdonald3","name":"Ben McDonald","path":"/bmcdonald3","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/46734217?s=80&v=4"},"commit":{"message":"Add proto testing for Arkouda nightly (#25136)\n\n[ reviewed by @jeremiah-corrado - thanks ]\r\n\r\nThe Arkouda devs are planning to switch to a new set of unit tests, so\r\nwe are starting to run those in nightly now before officially making\r\nthat change on the Arkouda side of things.","shortMessageHtmlLink":"Add proto testing for Arkouda nightly (#25136)"}},{"before":"36f169eeba496edf14ad4f9065fbe6662fbddda5","after":"61193494463ae0af6ed3fcd4400f611a6bc45302","ref":"refs/heads/main","pushedAt":"2024-05-29T20:49:40.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"jhh67","name":"John H. Hartman","path":"/jhh67","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3190372?s=80&v=4"},"commit":{"message":"Added more Cray CS GASNet-EX tests (#25123)\n\nAdded more GASNet-EX tests in preparation to making the `gasnet-ex` shim\r\nthe default.\r\n\r\n[Reviewed by @tzinsky and @bonachea, thank you.]","shortMessageHtmlLink":"Added more Cray CS GASNet-EX tests (#25123)"}},{"before":"58588dcebe4ddce620c04784cfcef5d530210358","after":"36f169eeba496edf14ad4f9065fbe6662fbddda5","ref":"refs/heads/main","pushedAt":"2024-05-29T18:25:23.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"e-kayrakli","name":"Engin Kayraklioglu","path":"/e-kayrakli","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4141670?s=80&v=4"},"commit":{"message":"Add the missing reduce helper decl in AMD runtime, too (#25138)\n\nThis is a small patch symmetric to the one I added here:\r\nhttps://github.com/chapel-lang/chapel/pull/25108/files#diff-fd9cac0eea147dc210859903e7107766edc1abaeb335360064f415f1ba1f0571.\r\nI missed the AMD side as our typical manual test system doesn't have the\r\ncorrect ROCm version and the reduction tests are skipped.\r\n\r\n[Trivial, not reviewed]\r\n\r\nTest:\r\n- [x] `gpu/native/reductions/basic` on AMD","shortMessageHtmlLink":"Add the missing reduce helper decl in AMD runtime, too (#25138)"}},{"before":"21d316f91f5863cfa149a62baaabdbfe04d1e2cc","after":"58588dcebe4ddce620c04784cfcef5d530210358","ref":"refs/heads/main","pushedAt":"2024-05-29T17:55:06.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Only run future with ASAN (#25139)\n\nSwitches a future test to only run with ASAN, as its not guaranteed to\r\nfail otherwise\r\n\r\nTested that test does not fail as a future with ASAN and that test is\r\nskipped without asan\r\n\r\n[Not reviewed - trivial]","shortMessageHtmlLink":"Only run future with ASAN (#25139)"}},{"before":"e1c9c317355f92d95e577c2376f28f44d8142e4e","after":"21d316f91f5863cfa149a62baaabdbfe04d1e2cc","ref":"refs/heads/main","pushedAt":"2024-05-29T17:54:40.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Add skipif for valgrind for gitErrors test (#25131)\n\nSkip this test for valgrind testing only, as valgrind interacts\r\nstrangely with subprocesses that capture stdout/stderr\r\n(https://github.com/chapel-lang/chapel/issues/25130).\r\n\r\n[Not reviewed - trivial]","shortMessageHtmlLink":"Add skipif for valgrind for gitErrors test (#25131)"}},{"before":"c9acf0c43c322581b33dd17e7763e7059972f662","after":"e1c9c317355f92d95e577c2376f28f44d8142e4e","ref":"refs/heads/main","pushedAt":"2024-05-29T17:41:56.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Cleanup old .bad files (#25137)\n\nRemove two .bad files for futures that have previously been resolved.\r\n\r\nPRs that resolved these futures\r\n- https://github.com/chapel-lang/chapel/pull/24540\r\n- https://github.com/chapel-lang/chapel/pull/13549\r\n\r\n[Reviewed by @e-kayrakli]","shortMessageHtmlLink":"Cleanup old .bad files (#25137)"}},{"before":"2e747c34ecb56033d567eb87edfcb02f1d84b550","after":"c9acf0c43c322581b33dd17e7763e7059972f662","ref":"refs/heads/main","pushedAt":"2024-05-29T16:58:51.000Z","pushType":"pr_merge","commitsCount":5,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Add clenshaw.chpl as a performance test (#25133)\n\nAdd clenshaw.chpl as a nightly performance test. This is an interesting\r\ntest for Chapel's vectorization performance.\r\n\r\nTested locally as a correctness test and a performance test.\r\n\r\n[Reviewed by @e-kayrakli]","shortMessageHtmlLink":"Add clenshaw.chpl as a performance test (#25133)"}},{"before":"a71a453618e4062041cf663f00690ce3b6fbaf22","after":"2e747c34ecb56033d567eb87edfcb02f1d84b550","ref":"refs/heads/main","pushedAt":"2024-05-29T16:51:53.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"arezaii","name":null,"path":"/arezaii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2806014?s=80&v=4"},"commit":{"message":"update mason test .good file to match help output after removing 'new' (#25135)\n\nFixes a mason test `.good` file to match the output from `--help` since\r\nthe documentation was updated in\r\nhttps://github.com/chapel-lang/chapel/pull/25099\r\n\r\nTESTING:\r\n\r\n- [x] `mason/mason-help-tests/masonHelpTests` passes\r\n\r\n\r\n[trivial change to test `.good` file only, not reviewed]","shortMessageHtmlLink":"update mason test .good file to match help output after removing 'new' ("}},{"before":"0d9c94e2072db4c96ecd7b70ddd06c8f8ca697b7","after":"a71a453618e4062041cf663f00690ce3b6fbaf22","ref":"refs/heads/main","pushedAt":"2024-05-28T23:03:37.000Z","pushType":"pr_merge","commitsCount":5,"pusher":{"login":"e-kayrakli","name":"Engin Kayraklioglu","path":"/e-kayrakli","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4141670?s=80&v=4"},"commit":{"message":"Fixes for Arkouda following GPU-based reduction (#25108)\n\nArkouda+GPU compilation testing suffered as fallout from\r\nhttps://github.com/chapel-lang/chapel/pull/24787. The issues were\r\ntwofold:\r\n\r\n- Compiler segfault: In Arkouda, some order-independent loops are\r\nsubject to what we call \"late gpuization failure\". In such cases, we\r\ngenerate a kernel, but then remove it from the AST. Removing a function\r\nfrom AST doesn't remove it from `gFnSymbols`. Scrubbing `gFnSymbols` et\r\nal. happens in between passes and removes such functions. However,\r\n`gpuTransforms` are technically part of LICM. After `gpuTransfroms`\r\nthere are some LICM operations (that also seem unrelated to LICM,\r\nunfortunately) that iterate over `gFnSymbols`. One such operation would\r\nget the removed function from the AST that would cause segfaults down\r\nthe road. As a solution, this PR uses `for_alive_in_Vec` in the\r\nproblematic section of the code to avoid the issue. Note that I couldn't\r\nreproduce this issue outside of Arkouda.\r\n\r\n- Linkage issues: fixing that exposed other linkage issues b/c Arkouda\r\nuses reductions on bools. It felt safe to just support those. So, this\r\nPR adds the ability to do reduction on bools.\r\n\r\n[Reviewed by @DanilaFe]\r\n\r\n#### Test:\r\n- [x] arkouda compiles locally (well, there is another issue, but that\r\nneeds to be fixed on Arkouda side. See\r\nhttps://github.com/Bears-R-Us/arkouda/pull/3236)\r\n- [x] nvidia\r\n- [x] amd\r\n- [x] standard linux64","shortMessageHtmlLink":"Fixes for Arkouda following GPU-based reduction (#25108)"}},{"before":"4c7de0a85dfedf1d1fa0b4f2bf52ca26b05d458e","after":"0d9c94e2072db4c96ecd7b70ddd06c8f8ca697b7","ref":"refs/heads/main","pushedAt":"2024-05-28T19:10:32.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Skip future for ARCH=x86 (#25129)\n\nSkip a future for all x86 architectures (64 bit and 32 bit). This future\r\npasses on x86, but continues to fail on ARM\r\n\r\n[Reviewed by @stonea]","shortMessageHtmlLink":"Skip future for ARCH=x86 (#25129)"}},{"before":"568a431f436c875a6fa8b6b7467d6e3fa7b02858","after":"4c7de0a85dfedf1d1fa0b4f2bf52ca26b05d458e","ref":"refs/heads/main","pushedAt":"2024-05-28T15:59:56.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Fix incorrect warning with chapel-py tools and CHPL_LLVM=none (#25121)\n\nFixes an issue where users would get a misconfiguration warning\r\nerroneously.\r\n\r\nWith CHPL_LLVM=none, users would receive the following warning. This was\r\na configuration issue with how chapel-py was being built.\r\n```\r\nMisconfiguration of the C++ Chapel compiler library\r\n headers in use with HAVE_LLVM defined\r\n .cpp files compiled without HAVE_LLVM defined\r\n```\r\n\r\n[Reviewed by @mppf]","shortMessageHtmlLink":"Fix incorrect warning with chapel-py tools and CHPL_LLVM=none (#25121)"}},{"before":"5c5cd18f25c52c205f1c774245da48f86eaea772","after":"568a431f436c875a6fa8b6b7467d6e3fa7b02858","ref":"refs/heads/main","pushedAt":"2024-05-28T15:59:46.000Z","pushType":"pr_merge","commitsCount":6,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Add scripts to test Chapel apt/rpm packages (#25066)\n\nAdds a few scripts and Docker templates to test chapel packages built\r\nfor various OSes in apt/rpm formats\r\n\r\nFollowup to https://github.com/chapel-lang/chapel/pull/25051\r\n\r\n[Reviewed by @arezaii]","shortMessageHtmlLink":"Add scripts to test Chapel apt/rpm packages (#25066)"}},{"before":"733961b9e7c145d76b772cf46ea7f02c41f60216","after":"5c5cd18f25c52c205f1c774245da48f86eaea772","ref":"refs/heads/main","pushedAt":"2024-05-28T15:33:47.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jhh67","name":"John H. Hartman","path":"/jhh67","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3190372?s=80&v=4"},"commit":{"message":"Look for sinfo error message anywhere in its output (#25128)\n\nIt appears that sometimes the sinfo error message about an invalid\r\nformat specification is not in the first line of output. Change to use\r\nstrstr so we find it anywhere in the output.\r\n\r\n[Reviewed by @jabraham17, thank you.]","shortMessageHtmlLink":"Look for sinfo error message anywhere in its output (#25128)"}},{"before":"4869e841de79ba4f4419ccdbbc3b35f79a97f02f","after":"733961b9e7c145d76b772cf46ea7f02c41f60216","ref":"refs/heads/main","pushedAt":"2024-05-28T14:49:12.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"lydia-duncan","name":"Lydia Duncan","path":"/lydia-duncan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2454710?s=80&v=4"},"commit":{"message":"Add notes about other ways to solve the Optimizers library argument problem (#25119)\n\n[reviewed by @jabraham17]\r\n\r\nIn talking to Jade and David during the user support/stabilization\r\nsubteam meeting today, I remembered a way Arkouda handles the \"support\r\nmultiple argument types leading to genericness when I want to store\r\nthings in the same data structure\" issue that this library will\r\nencounter when it extends the argument types it supports. Jade also\r\nreminded me of the existence of unions. Note both of these possible\r\nsolutions for the future so we don't forget again by the time we get\r\nback to this library\r\n\r\nChecked the tests of the draft library locally, but didn't run testing\r\notherwise - it's a comment update, it shouldn't impact anything else.","shortMessageHtmlLink":"Add notes about other ways to solve the Optimizers library argument p…"}},{"before":"7ca57b66f2d011fa1d8341efdb3ee89f60f4cf5a","after":"4869e841de79ba4f4419ccdbbc3b35f79a97f02f","ref":"refs/heads/main","pushedAt":"2024-05-24T16:15:45.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"stonea","name":"Andy Stone","path":"/stonea","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2591890?s=80&v=4"},"commit":{"message":"annotations for 5/23/24 (#25111)\n\nAnnotations for perf triage week of 5/23/24:\r\n\r\n- we've seen some pretty big changes to our dataframe indexing tests as\r\na result of this PR: Bears-R-Us/arkouda#3109\r\n\r\n[Reviewed by nobody; annotations update]","shortMessageHtmlLink":"annotations for 5/23/24 (#25111)"}},{"before":"0854a2d2fab9e3fe91da07508c0ef5463a7ef0d7","after":"7ca57b66f2d011fa1d8341efdb3ee89f60f4cf5a","ref":"refs/heads/main","pushedAt":"2024-05-24T02:57:02.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"arezaii","name":null,"path":"/arezaii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2806014?s=80&v=4"},"commit":{"message":"fix nightly script for parallel blog tests, remove hello flag (#24826)\n\nFixes a problem when the nightly `test-linux64-blog-only` is ran when\r\nsetup for paratest. Also adds better error output to differentiate\r\nbetween `blogdir` not found and `blogdir` not set.\r\n\r\nPreviously the `blogonly` testing did not play well with paratest\r\nbecause it placed the `testdirs` after the paratest args instead of in\r\nthe `DIRFILE`. This changes that by checking for a paratest file and\r\nthen writing our test directories to it in `blogonly` mode, similar to\r\nhow `examples` tests do. In normal `blog` mode, the test dirs should be\r\nincluded by way of being located within the `test` directory.\r\n\r\nWhile here, noticed that the `hello` flag is an outlier in this script,\r\nand was not being used by any of our testing. After some discussion with\r\n@DanilaFe and the dev-ops subteam, we decided to remove this flag.","shortMessageHtmlLink":"fix nightly script for parallel blog tests, remove hello flag (#24826)"}},{"before":"6a1a83fd8cf3e37a699539614dbb2b92add05e37","after":"0854a2d2fab9e3fe91da07508c0ef5463a7ef0d7","ref":"refs/heads/main","pushedAt":"2024-05-23T20:49:36.000Z","pushType":"pr_merge","commitsCount":12,"pusher":{"login":"benharsh","name":"Ben Harshbarger","path":"/benharsh","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1883119?s=80&v=4"},"commit":{"message":"Dyno: Improvements to tuple-grouped formals (#25102)\n\nThis PR makes several improvements to the resolution of tuple-grouped\r\nformals in the frontend. After this PR, the following cases are now\r\nfunctional:\r\n- tuple-grouped formal with a star-tuple type expression\r\n- generic tuple-grouped formals (flat and nested)\r\n\r\nThis PR also adds an error for tuple-grouped formals with a non-default\r\nformal intent. This matches the production compiler's behavior.\r\n\r\nTechnical details:\r\n- ``resolveTupleUnpackDecl`` is improved to better handle unknown or\r\nerroneous types\r\n- ``TupleDecl::isTupleDeclFormal()`` has been added to aid in\r\ndistinguishing such formals from variable declarations\r\n- To allow generics, substitutions and star-tuples of ``AnyType`` were\r\nrequired\r\n\r\n[reviewed-by @riftEmber]","shortMessageHtmlLink":"Dyno: Improvements to tuple-grouped formals (#25102)"}},{"before":"10247fd0eb8b3778df1b0ebdc666cb4b2a857ba2","after":"6a1a83fd8cf3e37a699539614dbb2b92add05e37","ref":"refs/heads/main","pushedAt":"2024-05-23T20:37:42.000Z","pushType":"pr_merge","commitsCount":20,"pusher":{"login":"lydia-duncan","name":"Lydia Duncan","path":"/lydia-duncan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2454710?s=80&v=4"},"commit":{"message":"Add a draft Optimizer library to the test hierarchy (#25096)\n\n[reviewed by @jabraham17]\r\n\r\nAt the end of the HPO deep dive, we decided that we wanted to try to\r\npull some of the optimization algorithms it uses into an Optimizer\r\nlibrary. This PR makes a start at that library, with the random\r\noptimizer as a proof of concept.\r\n\r\nResolves Cray/chapel-private#6301\r\n\r\nIt makes a number of interface decisions which would need broader\r\ndiscussion before promoting the library out of the drafts folder. Some\r\nof these were motivated by looking at the interface provided by\r\n[dlib](http://dlib.net/optimization.html) and\r\n[scipy](https://docs.scipy.org/doc/scipy/reference/optimize.html). I did\r\nnot examine their implementation.\r\n\r\nUser-facing contents:\r\n- `config param numIters` - used to specify the number of iterations to\r\ntry before returning the best result\r\n- `record optimizableArg` - users will wrap any arguments they wish to\r\noptimize in this type, enabling them to specify important information\r\nabout the argument all at once\r\n- `proc randomOptimize` - the interface into the random optimizer.\r\nAccepts a first class procedure, list of optimizable arguments, and\r\noptional tuple of remaining arguments to provide\r\n- `config param seed` - used to specify a seed if want consistent\r\nresults (mostly useful for writing tests that don't fail sporadically)\r\n\r\nLimitations:\r\n- only supports the random optimizer, not the bayesian, genetic, or grid\r\noptimizer (HPO supports these)\r\n- only supports optimizing arguments of type int\r\n - HPO only supported `int`, `real`, and `string`. The optimizableArg\r\n wrapper follows a similar implementation strategy for supporting the\r\n types, but that approach has limitations and results in increased record\r\n size\r\n- Does not recover from improper calls to the first class procedure\r\nbeing optimized (HPO does this, albeit optimizing a program rather than\r\na function call)\r\n- only supports up to 5 optimizable arguments (HPO supports any number -\r\nthe limitation is due to optimizing a function call rather than a\r\nprogram)\r\n- doesn't recover from and log failed or timed out attempts (HPO does\r\nthis, and the enum I copied can, I just didn't get to adding that\r\nsupport and am not sure I can)\r\n- does not support conditions (e.g. \"if x has this value, also provide\r\ny\". HPO does this, but supporting it required extensive amounts of code)\r\n\r\nAdds 5 tests:\r\n- optimizing a single argument within a set range of possible values\r\n- optimizing a single argument, without specifying a range of possible\r\nvalues\r\n- optimizing a single argument, specifying a discrete set list of\r\npossible values\r\n- optimizing two arguments\r\n- optimizing a single argument for a function that takes two (using a\r\nset value for the other argument)\r\n\r\nPassed a full paratest with futures","shortMessageHtmlLink":"Add a draft Optimizer library to the test hierarchy (#25096)"}},{"before":"79f78661fbc5ed4edf67ca7225329f58e4738f02","after":"10247fd0eb8b3778df1b0ebdc666cb4b2a857ba2","ref":"refs/heads/main","pushedAt":"2024-05-23T18:35:43.000Z","pushType":"pr_merge","commitsCount":6,"pusher":{"login":"arezaii","name":null,"path":"/arezaii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2806014?s=80&v=4"},"commit":{"message":"Fix mason license source (#25062)\n\nIn Mason, updates the source list of valid license names to the proper\r\nspdx repository. Also adds a new option to `mason publish`,\r\n`--refresh-licences` that will force delete and make a new clone of the\r\nlicense repository that is stored in the `.mason` folder.\r\n\r\nThe feature is implemented in such a way that if it's passed, it will be\r\nthe only option executed. This felt OK to me since it should be a very\r\nrarely if ever used option and it seemed like a distinct operation from\r\nthe publishing actions.\r\n\r\nIncludes some testing for the refresh-licenses feature, while there,\r\nupdated some tests that had malformed arguments to the corresponding\r\n`mason` sub-function, and fixed some linter warnings for unused names\r\nand indentation.\r\n\r\nTESTING:\r\n\r\n- [x] paratest `[Summary: #Successes = 17229 | #Failures = 0 | #Futures\r\n= 926]`\r\n\r\n[reviewed by @benharsh - thanks!]","shortMessageHtmlLink":"Fix mason license source (#25062)"}},{"before":"908becdffc3dd97d22e68727115bc5da088daff3","after":"79f78661fbc5ed4edf67ca7225329f58e4738f02","ref":"refs/heads/main","pushedAt":"2024-05-23T18:18:36.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"bmcdonald3","name":"Ben McDonald","path":"/bmcdonald3","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/46734217?s=80&v=4"},"commit":{"message":"remove unused proc and mention of interactive session (#25099)\n\nFixes https://github.com/chapel-lang/chapel/issues/25071\r\n\r\n[ contributed by @lucaferranti, merged + reviewed by me ]","shortMessageHtmlLink":"remove unused proc and mention of interactive session (#25099)"}},{"before":"75a070ab51fdb7a33a54be235a619b53ed51d19e","after":"908becdffc3dd97d22e68727115bc5da088daff3","ref":"refs/heads/main","pushedAt":"2024-05-23T16:17:26.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"lydia-duncan","name":"Lydia Duncan","path":"/lydia-duncan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2454710?s=80&v=4"},"commit":{"message":"Clarify the issue templates w.r.t. workarounds and if the issue is blocking (#25104)\n\n[reviewed by @bradcray]\r\n\r\nWe had a user recently seem confused whether calling the issue\r\n\"blocking\" was talking about the state of the project or their personal\r\nexperience. In response, it seemed like a good idea to adjust the\r\nrequest a bit.\r\n\r\nBased on the structure of the feature request template, make the other\r\ntwo templates talk about potential work-arounds in the \"Description\"\r\nsection, and make the request say \"if any\", so the user doesn't feel\r\nlike they have to have looked into work-arounds themselves.\r\n\r\nTransform the question about if it is blocking to not mention\r\nwork-arounds and be more explicit about who is being blocked (\"you\", the\r\nperson filing the request, though I would expect Chapel developers\r\nfiling such issues to use their \"user hat\" and answer based on if they\r\ncan accomplish what they are trying to do when they encountered the\r\nissue)","shortMessageHtmlLink":"Clarify the issue templates w.r.t. workarounds and if the issue is bl…"}},{"before":"1c2bb864715eb71801846908e38dc56e55cf67e6","after":"75a070ab51fdb7a33a54be235a619b53ed51d19e","ref":"refs/heads/main","pushedAt":"2024-05-23T02:20:44.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"bradcray","name":"Brad Chamberlain","path":"/bradcray","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7536222?s=80&v=4"},"commit":{"message":"Touch up text around require statements w.r.t. -I / -L flags (#25072)\n\n[based on feedback and suggestions by @psath, reviewed by @lydia-duncan]\r\n\r\nBased on feedback in #24963, this PR strives to improve the\r\ndocumentation of the ``require`` statement to clarify that it doesn't\r\naccept general `chpl` command-line flags and refactors the description\r\nof the -I and -L flags to try and clarify their role in common to\r\nlisting files on the command-line or `require` statements. While here, I\r\nalso did some wordsmithing and formatting adjustments.\r\n\r\nResolves #24963.","shortMessageHtmlLink":"Touch up text around require statements w.r.t. -I / -L flags (#25072)"}},{"before":"4f8552dd84c266ca438f968aae964fb0a6de2c32","after":"1c2bb864715eb71801846908e38dc56e55cf67e6","ref":"refs/heads/main","pushedAt":"2024-05-22T21:07:05.000Z","pushType":"pr_merge","commitsCount":4,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Add test script for nightly runs of Chapel packages (#25077)\n\nAdds a script that will serve as the driver for a nightly test job to\r\nbuild Chapel apt and rpm packages.\r\n\r\n[Reviewed by @arezaii]","shortMessageHtmlLink":"Add test script for nightly runs of Chapel packages (#25077)"}},{"before":"b089929672ff9d3293728fb02be9c71da0fd8ab6","after":"4f8552dd84c266ca438f968aae964fb0a6de2c32","ref":"refs/heads/main","pushedAt":"2024-05-22T21:06:41.000Z","pushType":"pr_merge","commitsCount":23,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Add scripts to build Chapel apt/rpm packages (#25051)\n\nThis PR adds various build scripts to create distributable Chapel\r\npackages for various OSes. These packages are built in the default\r\nCOMM=none configuration. Each package can be built for x86 and Arm in a\r\nsingle command from the same system, using docker buildkit.\r\n\r\nThese packages can be extended in follow-up PRs to support more OSes and\r\nother configurations\r\n\r\nOSes supported by this PR\r\n- Ubuntu 20, 22\r\n- Debian 11, 12\r\n- Fedora 37, 38, 39\r\n- EL9\r\n - supports rhel, rocky, and alma, built with rocky\r\n\r\nNote: Fedora 40 and Ubuntu 24 can be easily added with Chapel 2.1,\r\nrequires LLVM 18\r\n\r\nThe RPMs currently require a hotfix to build 2.0, merging\r\nhttps://github.com/chapel-lang/chapel/pull/25058 will fix that for 2.1\r\n\r\n[Reviewed by @jhh67]","shortMessageHtmlLink":"Add scripts to build Chapel apt/rpm packages (#25051)"}},{"before":"7566fbfd18118e748d75564e6652c8becd121186","after":"b089929672ff9d3293728fb02be9c71da0fd8ab6","ref":"refs/heads/main","pushedAt":"2024-05-22T21:05:56.000Z","pushType":"pr_merge","commitsCount":6,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Make mason missing command errors more portable (#25101)\n\nThis PR expands on the work in\r\nhttps://github.com/chapel-lang/chapel/pull/25069 to improve mason errors\r\nwhen dependencies (specifically git) are missing. This PR adds\r\nadditional logic to account for portability issues exposed by nightly\r\ntesting\r\n\r\nTesting\r\n- Tested the two tests added in #25069 pass on a Mac\r\n- Tested `start_test test/mason` passes on linux x86\r\n- Tested `start_test test/mason` passes on the nightly test machine (a\r\nslightly different linux x86)\r\n\r\n[Reviewed by @benharsh]","shortMessageHtmlLink":"Make mason missing command errors more portable (#25101)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEWV3WAAA","startCursor":null,"endCursor":null}},"title":"Activity · chapel-lang/chapel"}