Geth setup-raku: 4e0927a1a4 | dependabot[bot]++ (committed using GitHub Web editor) | package-lock.json
Bump @octokit/plugin-paginate-rest from 9.2.1 to 9.2.2

Bumps [@octokit/plugin-paginate-rest](github.com/octokit/plugin-paginate-rest.js) from 9.2.1 to 9.2.2.
  - [Release notes](github.com/octokit/plugin-paginate.../releases)
  - [Commits](github.com/octokit/plugin-paginate......v9.2.2)
  ---
... (6 more lines)		 00:17
setup-raku: 9fda08fa91 | (Shoichi Kaji)++ (committed using GitHub Web editor) | package-lock.json
Merge pull request #38 from Raku/dependabot/npm_and_yarn/octokit/plugin-paginate-rest-9.2.2

Bump @octokit/plugin-paginate-rest from 9.2.1 to 9.2.2
nqp: MasterDuke17++ created pull request #840:
Use a local variable for a class member access...		 02:09
setup-raku/dependabot/npm_and_yarn/octokit/request-8.4.1: 9c0b456bf2 | dependabot[bot]++ (committed using GitHub Web editor) | package-lock.json
Bump @octokit/request from 8.4.0 to 8.4.1

Bumps [@octokit/request](github.com/octokit/request.js) from 8.4.0 to 8.4.1.
  - [Release notes](github.com/octokit/request.js/releases)
  - [Commits](github.com/octokit/request.js/comp......v8.4.1)
  ---
... (6 more lines)		 03:42
setup-raku: 9c0b456bf2 | dependabot[bot]++ (committed using GitHub Web editor) | package-lock.json
Bump @octokit/request from 8.4.0 to 8.4.1

Bumps [@octokit/request](github.com/octokit/request.js) from 8.4.0 to 8.4.1.
  - [Release notes](github.com/octokit/request.js/releases)
  - [Commits](github.com/octokit/request.js/comp......v8.4.1)
  ---
... (6 more lines)		 03:44
setup-raku: 27c455fbe1 | (Shoichi Kaji)++ (committed using GitHub Web editor) | package-lock.json
Merge pull request #39 from Raku/dependabot/npm_and_yarn/octokit/request-8.4.1

Bump @octokit/request from 8.4.0 to 8.4.1
nine bartolin: I see no comment on that commit 08:07
bartolin Hmm, for me there are small icons on the right side of lines 174 and 176. By clicking on the icon they can be expanded. I had hoped they would be more visible for you. Is there a better way to add a comment to a commit? (I'm not that familiar with the features of GitHub.) 08:17
Ah, these could be direct links: github.com/rakudo/rakudo/commit/c0...r152716887 and github.com/rakudo/rakudo/commit/c0...r152717048 08:18
Geth rakudo/main: a0579b9bb1 | (Stefan Seifert)++ | 6 files
RakuAST: name's colonpairs method should return a HLL List for consistency
 09:12
rakudo/main: 65b2056e93 | (Stefan Seifert)++ | src/Raku/ast/regex.rakumod
RakuAST: support non-identifier rule calls

E.g. m/<.Foo::foo>/
nine This brings us to 1177 :) 09:13
bartolin: nice catch! That brings us down to 24 spec tests failing 09:39
bartolin: That loop is arguably even too conservative as labels always seem to get added to the end of the node list 09:40
releasable6 Next release in ≈3 days and ≈7 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 11:00
Geth rakudo/main: 2ab1e918f6 | (Elizabeth Mattijsen)++ | src/core.c/Rakudo/Iterator.rakumod
Add support for 0 in .rotor

As reported missing in #3588.
Also re-imagined the innards of .pull-one of the iterator, making the "eat all" case faster, and generally using fewer attribute calls and more locals. Also de-nqpified a lot to improve readability		 12:47
roast: ee1968ba2a | (Elizabeth Mattijsen)++ | S32-list/rotor.t
Add test for #3588
 12:51
lizmat [Coke] jdv that concludes my work on the core until the 2025.02 release, unless you find bugs that need to be fixed before the release 12:54
Geth rakudo/main: 60a2d44b8c | (Stefan Seifert)++ | src/Raku/ast/regex.rakumod
RakuAST: fix trailing separators getting put into wrong capture group

Fixes: "a,b," ~~ m/(<.alpha>) +%% (<.punct>)/ # to have only 2 capture groups		 14:33
nine 1179
[Coke] Do we want one more blin run, just in case? 15:58
timo 58 16:53
sorry, cat.
Geth rakudo/main: 1aa763f066 | (Stefan Seifert)++ | 2 files
RakuAST: wrap exceptions thrown by CHECK phasers in X::Comp::BeginTime

We also add file/line information to the wrapper.		 16:55
nine 1180
timo not to open yet another meta file discussion, but should we specify the "supports" stuff a bit more? a distinction between "this url can be fed directly into a version control tool's CLI" and "this url can be opened in a browser for a web view of the repository" would be the first thing i can think of immediately 17:44
Geth rakudo/main: 8ead62065c | (Stefan Seifert)++ | 2 files
RakuAST: fix compiler bug on <sym> outside a proto-regex
 17:53
rakudo/main: 7daa644a24 | (Stefan Seifert)++ | src/Raku/Actions.nqp
RakuAST: throw error when encountering <sym> outside a proto regex
nine 1181 17:54
timo nine's on a roll :)
Geth rakudo/main: 10040b9807 | (Stefan Seifert)++ | src/Raku/ast/regex.rakumod
RakuAST: fix name of capture groups for fully qualified calls

Apparently we need to use the full name, e.g. <Foo::foo> will be found in $<Foo::foo>		 18:14
nine And 1182
[Coke] is glad jdv is taking this one, since I just got diagnosed with the flu 21:21
timo aw crap. i hope you don't have it too rough :( 21:22
[Coke] little tired, some coughing. I'll be OK, thanks.

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!