{"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":"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)"}},{"before":"0cb8ace9d472ec84f0bfd3dca024b8abcf8f7843","after":"7566fbfd18118e748d75564e6652c8becd121186","ref":"refs/heads/main","pushedAt":"2024-05-22T18:13:46.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"jeremiah-corrado","name":null,"path":"/jeremiah-corrado","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/62707311?s=80&v=4"},"commit":{"message":"make moduleCheck more robust (#25098)\n\nFollow-up of https://github.com/chapel-lang/chapel/pull/25084, make sure\r\nthat `moduleCheck` only considers `.chpl` files, otherwise the following\r\ncase\r\n\r\n```\r\nmyPkg/\r\n src/\r\n myPkg.chpl\r\n notes.txt\r\n```\r\n\r\nwould lead the check to fail\r\n\r\n[ reviewed by @jeremiah-corrado ]\r\n[ merged on behalf of @lucaferranti ]","shortMessageHtmlLink":"make moduleCheck more robust (#25098)"}},{"before":"3ab03fbc754837137c028589dc73243f4c5327ef","after":"0cb8ace9d472ec84f0bfd3dca024b8abcf8f7843","ref":"refs/heads/main","pushedAt":"2024-05-21T23:01:58.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Prediff out LLDB test line for `--memLeaks` being set (#25092)\n\nThe test `test/execflags/lldbddash/declint.chpl` has been failing in\r\n`memleaks` configuration since LLDB became available to it and the test\r\nwas no longer `skipif`'d. This is because LLDB prints out a line about\r\narguments to the executable being set (`--memLeaks` and `--memLeaksLog`)\r\nwhich doesn't apply otherwise. Prediff out these lines so the test can\r\npass.\r\n\r\n[reviewed by @jabraham17 , thanks!]\r\n\r\nTesting:\r\n- [x] test now passes in reproducer configuration\r\n- [x] test still passes in non-memleaks configuration","shortMessageHtmlLink":"Prediff out LLDB test line for --memLeaks being set (#25092)"}},{"before":"e18a8d9ee25144a43ef5ac6e3c3cb2daf553eda7","after":"3ab03fbc754837137c028589dc73243f4c5327ef","ref":"refs/heads/main","pushedAt":"2024-05-21T22:30:48.000Z","pushType":"pr_merge","commitsCount":8,"pusher":{"login":"DanilaFe","name":"Daniel","path":"/DanilaFe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4361282?s=80&v=4"},"commit":{"message":"LSP: Ensure redefinition errors are issued even if no identifiers are present. (#25095)\n\nCloses https://github.com/chapel-lang/chapel/issues/25093.\r\n\r\nWe need to make sure modules are scope resolved to ensure that\r\nredefinition errors are issued. This PR makes this happen. Prior to this\r\nPR, it was not possible to trigger the scope resolution of a particular\r\nAST node -- only `Identifier` and `Dot` nodes had `to_id`s. This PR adds\r\na general purpose `scope_resolve` function to match `resolve`, which\r\nworks on an arbitrary AST, and returns a `ResolvedExpression` (also to\r\nmatch `resolve). Using this function we can trigger scope resolution of\r\narbitrary modules.\r\n\r\nThen, making use of this, this PR adds a new `visit` call for Modules,\r\nand calls `scope_resolve`.\r\n\r\nAlso adds a test to lock down this behavior.\r\n\r\nReviewed by @jabraham17 \r\n\r\n## Testing\r\n\r\n- [x] `make test-cls`","shortMessageHtmlLink":"LSP: Ensure redefinition errors are issued even if no identifiers are…"}},{"before":"2cecbad91af105ba29b44a91edf5ea817dba0738","after":"e18a8d9ee25144a43ef5ac6e3c3cb2daf553eda7","ref":"refs/heads/main","pushedAt":"2024-05-21T22:19:08.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"ShreyasKhandekar","name":"Shreyas Khandekar","path":"/ShreyasKhandekar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60454060?s=80&v=4"},"commit":{"message":"Update QUICKSTART.rst (#25091)\n\nUpdate QUICKSTART.rst to include memory requirement for installation.\r\nInstall fails on a machine with < 4GB of memory.\r\n\r\nContributed by @bhurwitz33, reviewed and merged by @ShreyasKhandekar","shortMessageHtmlLink":"Update QUICKSTART.rst (#25091)"}},{"before":"056e0ed2439fe3763e0006b68492ee3bcc0324b7","after":"2cecbad91af105ba29b44a91edf5ea817dba0738","ref":"refs/heads/main","pushedAt":"2024-05-21T21:41:10.000Z","pushType":"pr_merge","commitsCount":9,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Improve Mason error when git is missing (#25069)\n\nImproves the error thrown by Mason when git is missing. Prior to this\r\nPR, all that would be thrown was `\"Internal mason error\"`, which is not\r\nhelpful.\r\n\r\nPR also includes a bonus typo fix in the docs for Subprocess\r\n\r\nChecked that the test for this error message passes\r\n\r\n[Reviewed by @benharsh]","shortMessageHtmlLink":"Improve Mason error when git is missing (#25069)"}},{"before":"714f9c2bdf7c6ada62b7c2365f28f39dcb3bf77a","after":"056e0ed2439fe3763e0006b68492ee3bcc0324b7","ref":"refs/heads/main","pushedAt":"2024-05-21T19:14:02.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Switch to using default LLVM version in valgrind tests (#25094)\n\nRemove workaround setting use of LLVM 13 in Valgrind nightly test\r\nconfigs, as it is no longer needed and causing [other\r\nproblems](https://chapel.discourse.group/t/test-chapcs-correctness-test-valgrindexe/33620/3).\r\n\r\nResolves https://github.com/Cray/chapel-private/issues/3373.\r\n\r\n[merging without review for expediency as the test is broken now\r\nanyways)","shortMessageHtmlLink":"Switch to using default LLVM version in valgrind tests (#25094)"}},{"before":"da8805a5e99eba01188eacf6b47ad85b04d27bbb","after":"714f9c2bdf7c6ada62b7c2365f28f39dcb3bf77a","ref":"refs/heads/main","pushedAt":"2024-05-21T18:56:51.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"mppf","name":"Michael Ferguson","path":"/mppf","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3653132?s=80&v=4"},"commit":{"message":"Improve search behavior for specific keywords (#25037)\n\nThis PR improves the documentation search results for specific searches:\r\n * new\r\n * with\r\n * by\r\n * zip\r\n * local\r\n\r\nIn order to do so, it adds `.. index::` entries to the forallLoops.chpl\r\nand taskParallel.chpl primers. I added index entries for other sections\r\npresent there, while there. To get these `.. index::` entries to work, I\r\nneeded to update `literate_chapel.py` because it was de-indenting the\r\nlines following `.. index::` which lead to invalid RST.\r\n\r\nThis PR also has a minor impact on the Chapel blog rendering (since the\r\nblog uses `chpl2rst.py` which this PR modifies to support `.. index::`).\r\nNow whitespace is more accurately respected within the .rst comments.\r\n\r\nReviewed by @DanilaFe - thanks!\r\n\r\n- [x] full comm=none testing","shortMessageHtmlLink":"Improve search behavior for specific keywords (#25037)"}},{"before":"6108ccd62d1420aa4e7bd658606205ca1437781f","after":"da8805a5e99eba01188eacf6b47ad85b04d27bbb","ref":"refs/heads/main","pushedAt":"2024-05-21T16:49:45.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"jeremiah-corrado","name":null,"path":"/jeremiah-corrado","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/62707311?s=80&v=4"},"commit":{"message":"Fix mason CI check that was failing for packages with sub-modules (#25084)\n\nFix the bug in Mason's main-module check, outlined in [this\r\nissue](https://github.com/chapel-lang/chapel/issues/25064), that\r\nprevents packages that use sub-modules from being accepted in the mason\r\nregistry.\r\n\r\n[reviewed by @bmcdonald3 ] - thanks!","shortMessageHtmlLink":"Fix mason CI check that was failing for packages with sub-modules (#2…"}},{"before":"336dfc66e1f1651c979796be0930f986807206c4","after":"6108ccd62d1420aa4e7bd658606205ca1437781f","ref":"refs/heads/main","pushedAt":"2024-05-21T02:26:43.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Suppress readHDF5Df.chpl test always (#25085)\n\nSuppress this newly-running failing test pending further discussion, to\r\nend a few days of noise in multiple configs.\r\n\r\nSee https://github.com/Cray/chapel-private/issues/6322 for explanation\r\nand discussion.\r\n\r\n[reviewed by @bradcray , thanks!]","shortMessageHtmlLink":"Suppress readHDF5Df.chpl test always (#25085)"}},{"before":"b43a7a14a59de9a28b2c6736c06480a185356c49","after":"336dfc66e1f1651c979796be0930f986807206c4","ref":"refs/heads/main","pushedAt":"2024-05-21T00:04:19.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Switch LLVM setup script used in Valgrind test configs (#25080)\n\nSwitch the LLVM dependency setup script used in Valgrind nightly test\r\nconfigs.\r\n\r\nWe use LLVM 13 for our Valgrind testing due to\r\nhttps://github.com/Cray/chapel-private/issues/3373. These tests run on\r\nchapcs/chapvm systems which I recently switched to use a new Spack\r\ninstall, and as part of this I switched all LLVM dependencies to come\r\nfrom a Spack install. I adjusted the script\r\n`/data/cf/chapel/setup_system_llvm.bash` to load LLVMs from\r\n`/data/cf/chapel/chpl-deps/spack/`. However, the Valgrind test scripts\r\napparently use a copy of this script at\r\n`/cray/css/users/chapelu/setup_system_llvm.bash`, which loads from\r\nmanual LLVM installs and does not have a corresponding Spack install to\r\nuse AFAIK.\r\n\r\nSince I think this is the only remaining case in which we need to load\r\nan old LLVM, and we have a working way to do that, just go for the easy\r\nsolution of sourcing the updated\r\n`/data/cf/chapel/setup_system_llvm.bash` script instead.\r\n\r\nI tested and this alone does not resolve the issue, as the new Spack\r\ninstall comes with a new GCC install, and Valgrind complains about dwarf\r\n5 symbols in debuginfo for its libstdc++. However, I think it's a step\r\nin the right direction, and combined with a newer Valgrind it works in\r\nmy testing.","shortMessageHtmlLink":"Switch LLVM setup script used in Valgrind test configs (#25080)"}},{"before":"0afff8725c5dbce57a8879f4e89b288863a52174","after":"b43a7a14a59de9a28b2c6736c06480a185356c49","ref":"refs/heads/main","pushedAt":"2024-05-20T18:50:41.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":"Produce the correct output when the sinfo command fails (#24992)\n\nThe strsep function modifies the buffer it is given, so make a copy of\r\nthe buffer before calling strsep so that we can include the output in\r\nan error message if the buffer cannot be parsed.\r\n\r\n[Reviewed by @jabraham17, thank you.]","shortMessageHtmlLink":"Produce the correct output when the sinfo command fails (#24992)"}},{"before":"271d8e4787d334fbdcd42c924be1dfbcedff4af7","after":"0afff8725c5dbce57a8879f4e89b288863a52174","ref":"refs/heads/main","pushedAt":"2024-05-20T17:10:26.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Update C++ standard specified for protobuf build (#25049)\n\nRecent versions of protobuf [depend on\r\nabseil-cpp](https://protobuf.dev/news/2022-08-03/#abseil-dep), and\r\nabseil requires at least C++14. However, we specify the use of C++11 in\r\nthe compile flags for our `protoc-gen-chpl` target. Update it to C++17\r\nsince that's what Chapel in general requires.\r\n\r\n[`d1a649a`\r\n(#16817)](https://github.com/chapel-lang/chapel/pull/16817/commits/d1a649afd0308f55dba09bf71841a176ec62a63b)\r\nasserts the `-std` argument is required for building on Mac, which holds\r\nup on my Mac with Clang 15; however, it works with `-std=c++17` instead\r\nof 11.\r\n\r\n[reviewed by @mppf , thanks!]\r\n\r\nTesting:\r\n- [x] `make protoc-gen-chpl` succeeds with a protobuf requiring abseil,\r\non Mac and Linux\r\n- not on the latest protobuf however, due to\r\nhttps://github.com/Cray/chapel-private/issues/6313, but that's a\r\nseparate issue","shortMessageHtmlLink":"Update C++ standard specified for protobuf build (#25049)"}},{"before":"0244e85efa83dce13acc833bd05b4f740bfa044b","after":"271d8e4787d334fbdcd42c924be1dfbcedff4af7","ref":"refs/heads/main","pushedAt":"2024-05-20T17:02:51.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"riftEmber","name":"Anna Rift","path":"/riftEmber","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14242898?s=80&v=4"},"commit":{"message":"Remove spack dep loading on horizon (#25079)\n\nWe don't want to load deps from Spack on Horizon as that's where we do\r\nmodule builds.\r\n\r\nI thought that\r\nhttps://github.hpe.com/hpe/hpc-chapel-ci-config/commit/9db0ae56a63de443f6c58658e7817808d6564e25\r\nmade it so no Horizon tests used Spack deps anymore, but some apparently\r\ndo, such as\r\nhttps://chapel-ci.us.cray.com/job/cray-xc-correctness-test-cray-xc-arkouda.release/200/consoleFull.\r\nThis PR removes the code responsible.","shortMessageHtmlLink":"Remove spack dep loading on horizon (#25079)"}},{"before":"48446185882643c445a878b59e198a9e8d1f9664","after":"0244e85efa83dce13acc833bd05b4f740bfa044b","ref":"refs/heads/main","pushedAt":"2024-05-20T15:24:03.000Z","pushType":"pr_merge","commitsCount":47,"pusher":{"login":"jabraham17","name":"Jade Abraham","path":"/jabraham17","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15747900?s=80&v=4"},"commit":{"message":"Expand CLS testing (#25025)\n\nExpands the work of @DanilaFe in\r\nhttps://github.com/chapel-lang/chapel/pull/25011 to add more tests of\r\nCLS, Chapels language server implementation.\r\n\r\nInfrastructure changes\r\n- Moved test-only python dependencies into their own venv\r\n- Refactored and split up the monolithic `test_server.py`\r\n- all top level python files are considered test files, helper files can\r\nbe hidden in sub directories\r\n- this also allows for tests to be defined in multiple files to\r\nlogically group them\r\n\r\nAdded tests for the following features\r\n- Resolving nested directories\r\n- resolution tests\r\n- call inlays\r\n- type inlays\r\n- diagnostics\r\n- param inlays\r\n- document symbols\r\n- end markers\r\n- code lenses (show generic, show instantiation)\r\n\r\nBugs fixed as a result of writing tests\r\n- goto-type-def should use `name_location` when possible\r\n- fix type inlay bug with implicit this\r\n- fix document symbols inconsistencies\r\n- fix off-by-one location error\r\n- fix end marker inlays rendering incorrectly\r\n- fix type variable locations\r\n\r\n[Reviewed by @DanilaFe]","shortMessageHtmlLink":"Expand CLS testing (#25025)"}},{"before":"bab2356c54144aa5f121ff7fb0a0a5ace5c637d5","after":"48446185882643c445a878b59e198a9e8d1f9664","ref":"refs/heads/main","pushedAt":"2024-05-20T14:58:26.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":"Always use `python3` in bash env shebang (#25058)\n\nRemoves `#!usr/bin/env python` from `compileline.py`, as this causes\r\nissues when building RPMs.\r\n\r\nNow that we no longer support python2, it can just always be\r\n`#!usr/bin/env python3`\r\n\r\n[Reviewed by @mppf and @riftEmber]","shortMessageHtmlLink":"Always use python3 in bash env shebang (#25058)"}},{"before":"2948b49f00137130b8457e834cd3a13742f726ec","after":"bab2356c54144aa5f121ff7fb0a0a5ace5c637d5","ref":"refs/heads/main","pushedAt":"2024-05-17T00:25:47.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":"Add future for bug when applying `forwarding` to badly formatted variable declaration (#25068)\n\n[trivial, not reviewed]\r\n\r\nAdding a future for #25067","shortMessageHtmlLink":"Add future for bug when applying forwarding to badly formatted vari…"}},{"before":"2a2849cfd5f9d27c9981e585fe83e1a5869e1ba8","after":"2948b49f00137130b8457e834cd3a13742f726ec","ref":"refs/heads/main","pushedAt":"2024-05-16T21:57:59.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 week of 5/16/24 (#25065)\n\n- Improve mandelbrot complex performance for LLVM 17 with (#25019)\r\n- Improve Arkouda argsort performance with (Bears-R-Us/arkouda#3163)\r\n\r\n[Reviewed by nobody; annotations update]","shortMessageHtmlLink":"annotations for week of 5/16/24 (#25065)"}},{"before":"2ba4b4267dcfe80f15d31abfb5c4390dd418ffcc","after":"2a2849cfd5f9d27c9981e585fe83e1a5869e1ba8","ref":"refs/heads/main","pushedAt":"2024-05-16T21:10:26.000Z","pushType":"pr_merge","commitsCount":7,"pusher":{"login":"arezaii","name":null,"path":"/arezaii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2806014?s=80&v=4"},"commit":{"message":"update homebrew formula for main (#25044)\n\nMakes small updates to homebrew formula that we keep up to date so that\r\nit can build the latest main. Fixes a problem in homebrew builds where\r\nwe were having to reset the cmake cache between calls to make, or we'd\r\nsee an error during the build about how the cmake variables for\r\n`CMAKE_C_COMPILER` and `CMAKE_CXX_COMPILER` were being reset. In this\r\nand other packages, we just want to use the CC and CXX values that the\r\npackager is providing, so by setting `CHPL_CMAKE_USE_CC_CXX` we avoid\r\nproblems.\r\n\r\nPreviously, the `brew install` was failing and moving the new builds of\r\nthe `chapel-language-server` and `chplcheck` in with `chpldoc` fixes it.\r\nWhile here, remove code that was temporarily introduced to work around\r\nbugs with python 3.12 and also code to add a `clean-cmakecache` target\r\non the fly, since it is no longer needed.\r\n\r\nTESTING:\r\n\r\n- [x] can run `util/cron/test-homebrew.bash`\r\n- [x] manually updating chapel formula with `brew edit chapel` installs\r\nall built targets (e.g., `chpl`, `chpldoc`, `chplcheck`, etc.)\r\n\r\n[reviewed by @jabraham17 - thanks!]","shortMessageHtmlLink":"update homebrew formula for main (#25044)"}},{"before":"a518c881f2c2b4487c268edff764c4c59af1eb1b","after":"2ba4b4267dcfe80f15d31abfb5c4390dd418ffcc","ref":"refs/heads/main","pushedAt":"2024-05-16T20:32:56.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"benharsh","name":"Ben Harshbarger","path":"/benharsh","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1883119?s=80&v=4"},"commit":{"message":"Dyno: Generate concrete initializers on classes that inherit (#25055)\n\nThis PR adds some basic support for compiler-generating initializer\r\nsignatures on classes that inherit. This currently only works for\r\nconcrete types, as we have some other pre-existing issues for\r\ninstantiating generic classes with inheritance.\r\n\r\nVarious test cases are added to lock in relevant behaviors:\r\n- named arguments working correctly with defaults\r\n- presence of a user-defined initializer on a parent or grandparent\r\nclass\r\n- invoking a compiler-generated initializer with super.init\r\n\r\n[reviewed by @DanilaFe]","shortMessageHtmlLink":"Dyno: Generate concrete initializers on classes that inherit (#25055)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEUzhGwQA","startCursor":null,"endCursor":null}},"title":"Activity · chapel-lang/chapel"}