[Coke] clean run through 5ccfdc2370 00:03
linkable6 (2026-10-27) github.com/rakudo/rakudo/commit/5ccfdc2370 (At least) preliminary fix for #6879 (#6889)
00:15 guifa left 00:17 finanalyst_ left
[Coke] raku doc test is dying with "# Cannot find method 'language_revision' on object of type NQPMu" 02:32
golfing
bisectable6: use nqp; nqp::getcomp('Raku') || nqp::getcomp('perl6'); 02:36
bisectable6 [Coke], Will bisect the whole range automagically because no endpoints were provided, hang tight
[Coke], ¦6c (105 commits): «» 02:37
[Coke], Nothing to bisect!
[Coke] bisectable6: use nqp; my $parser = nqp::getcomp('Raku') || nqp::getcomp('perl6'); $parser.parse('say 3'); 02:38
bisectable6 [Coke], Will bisect the whole range automagically because no endpoints were provided, hang tight
[Coke], Output on all releases: gist.github.com/6e2cb6853c50431c71...b57c6e37a8 02:39
[Coke], Bisecting by output (old=2026.09 new=5ccfdc2) because on both starting points the exit code is 1
[Coke], bisect log: gist.github.com/af2d085da2aa81e600...5810cd0411
[Coke], (2026-09-27) github.com/rakudo/rakudo/commit/60...c8c869b39b
[Coke], Bisecting by exit code (old=2026.08 new=2026.09). Old exit code: 0
[Coke], bisect log: gist.github.com/24f6ff3583cc3ed964...ed00ef6d6a
[Coke], (2026-09-22) github.com/rakudo/rakudo/commit/f0...b3348dbcb0
[Coke], ⚠ New output detected, please review the results manually
[Coke], Output on all releases and bisected commits: gist.github.com/157862798d55e8f357...1a00d7f033
Geth ¦ rakudo: coke assigned to ugexe Issue nqp::getcomp('Raku') issues in RakuAST github.com/rakudo/rakudo/issues/6890 02:44
¦ rakudo: coke assigned to lizmat Issue nqp::getcomp('Raku') issues in RakuAST github.com/rakudo/rakudo/issues/6890
03:18 apogee_ntv left 03:20 apogee_ntv joined 05:39 [Coke] left 07:34 [Coke] joined 08:03 vrurg joined, vrurg_ left
Geth ¦ rakudo: lizmat unassigned from ugexe Issue nqp::getcomp('Raku') issues in RakuAST github.com/rakudo/rakudo/issues/6890 09:51
lizmat m: sub syntax-ok($string) { CATCH { return False }; EVAL($string, :check); True }; say syntax-ok("say 34"); say syntax-ok("zay 34") 09:56
camelia ===SORRY!=== Error while compiling <tmp>
EVAL is a very dangerous function!!! (use the MONKEY-SEE-NO-EVAL pragma
to override this error but only if you're VERY sure your data contains
no injection attacks).
at <tmp>:1
------> { return False…
lizmat m: sub syntax-ok($string) { CATCH { return False }; $string.EVAL(:check); True }; say syntax-ok("say 34"); say syntax-ok("zay 34")
camelia True
False
Geth rakudo/lizmat-103: b6e13cf3d5 | (Elizabeth Mattijsen)++ | src/Raku/ast/rakuast-prologue.nqp
Add a "note" sub to the RakuAST bootstrap

Debugging precomp issues in the RakuAST bootstrap is extremely difficult because NQP doesn't provide an easy way to "note" things on STDERR (as saying things on STDOUT will interfere with dependency recording when precomping).
This commit adds a "note" sub in the RakuAST bootstrap, allowing for the same ease of use we know in Raku.		 11:45
rakudo: lizmat++ created pull request #6891:
Add a "note" sub to the RakuAST bootstrap
lizmat [Coke]: I intend to merge ^^ if CI is green, as it will make it easier for me to look at fixing #6857 11:47
[Coke]: unless you really do not want me to do that (as the CI turned green) 12:29
12:44 djinni` left, djinni` joined
[Coke] lizmat: seems reasonable. 12:54
Geth rakudo/main: bba73cdd7b | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/Raku/ast/rakuast-prologue.nqp
Add a "note" sub to the RakuAST bootstrap (#6891)

Debugging precomp issues in the RakuAST bootstrap is extremely difficult because NQP doesn't provide an easy way to "note" things on STDERR (as saying things on STDOUT will interfere with dependency recording when precomping).
This commit adds a "note" sub in the RakuAST bootstrap, allowing for the same ease of use we know in Raku.		 13:00
rakudo/lizmat-104: d6c5d06aa2 | (Elizabeth Mattijsen)++ | 5 files
Replace RakuAST::IMPL::VarLowering.IMPL-NOTE with note()

The new note() sub is better optimized as it doesn't need to create new types everytime it is being called. Also it accepts multiple arguments which it will concatenate, so that that doesn't need to be done at the callsite anymore.		 13:16
rakudo: lizmat++ created pull request #6892:
Replace RakuAST::IMPL::VarLowering.IMPL-NOTE with note()
[Coke] bisectable6: ::("Error") 13:38
bisectable6 [Coke], Will bisect the whole range automagically because no endpoints were provided, hang tight
[Coke], Output on all releases: gist.github.com/45fb52867ffbe49b2f...871b5dcdf1 13:39
[Coke], Bisecting by output (old=2017.05 new=2017.06) because on both starting points the exit code is 1
[Coke], bisect log: gist.github.com/58e88bc995274c7b50...5cb367afff
[Coke], (2017-06-07) github.com/rakudo/rakudo/commit/e5...30bd74d765
[Coke], Output on all releases and bisected commits: gist.github.com/92975cf6cba96109f0...8641427ccb
[Coke] ok, so the thing I'm testing in raku-doc - the actual behavior of ::('foo') hasn't changed. 13:46
Geth rakudo/lizmat-105: a329f480ed | (Elizabeth Mattijsen)++ | src/Raku/ast/var-lowering.rakumod
RakuAST: use lowered lexical in hot loops during optimization

The variable lowering optimization logic contains a lot of hot loops going through frames. This commit replaces these accesses from a getattr into a lowered lexical.
Makes optimize stage by about 10% faster (roughly from 5.9 seconds to 5.4 seconds for the core.c setting optimization on my MBP).		 14:21
14:22 Geth left, Geth joined
Geth rakudo: lizmat++ created pull request #6893:
RakuAST: use lowered lexical in hot loops during optimization		 14:22
rakudo/lizmat-106: 645fb00d2d | (Elizabeth Mattijsen)++ | src/core.e/Fixups.rakumod
Add Code.syntax-ok($code-to-check) method

Inspired by github.com/rakudo/rakudo/issues/6890 it indeed felt there should be an easily usable method for checking the legality of a piece of Raku code.
The Code.syntax-ok method takes a string and returns True/False on whether it is legal Raku code.
Since this is a new feature, it is only available in 6.e.		 14:40
rakudo: lizmat++ created pull request #6894:
Add Code.syntax-ok($code-to-check) method
roast: dcd97b9f6b | (Elizabeth Mattijsen)++ | S05-modifier/ratchet.t
Add test for github.com/rakudo/rakudo/issues/6879
 14:46
rakudo/lizmat-106: 8c8f86f8c2 | (Elizabeth Mattijsen)++ | src/core.e/Fixups.rakumod
Use uppercase letters in name: SYNTAX-OK

Because call the method *could* be dangerous in the sense that any BEGIN blocks *will* get executed. So mark it by using uppercase, just as the Str.EVAL method and the EVAL sub.		 15:11
[Coke] bisectable6: my $a = ::("asdfasdf"); dd $a 15:27
bisectable6 [Coke], Will bisect the whole range automagically because no endpoints were provided, hang tight
[Coke], Output on all releases: gist.github.com/fd0b71722d56821a55...5c61b05736
[Coke], Bisecting by output (old=2024.04 new=2024.05) because on both starting points the exit code is 0
[Coke], bisect log: gist.github.com/10c9684b04a8aec856...aadeef8976 15:28
[Coke], (2024-05-18) github.com/rakudo/rakudo/commit/0a...0683b6afac
[Coke], Output on all releases and bisected commits: gist.github.com/e648b130be73706747...1bad9c1496
ab5tract ugexe: ever pointed Claude at the dual-JIT situation as a cleanup operation? 15:29
tellable6 ab5tract, I'll pass your message to ugexe
[Coke] c: my $a = "Backtrace"; say ::($a); 15:41
committable6 [Coke], ¦my: «Cannot find this revision (did you mean “nom”?)»
[Coke] c: HEAD my $a = "Backtrace"; say ::($a);
committable6 [Coke], ¦HEAD(bba73cd): «(Backtrace)␤»
[Coke] c: HEAD my $a = "Backtrace"; say ?::($a); 15:43
committable6 [Coke], ¦HEAD(bba73cd): «False␤»
[Coke] c: HEAD my $a = "Backtrace"; say ::($a).DEFINITE;
committable6 [Coke], ¦HEAD(bba73cd): «False␤»
[Coke] c: HEAD my $a = "Backtraceadoo"; dd ::($a) 15:46
committable6 [Coke], ¦HEAD(bba73cd): «Failure.new(exception => X::NoSuchSymbol.new(symbol => "Backtraceadoo"))␤»
patrickb ab5tract: The ExprJIT has been disabled for a long time now. Cleanup basically means ripping out ExprJIT in it's entirety.
[Coke] c: HEAD my $a = "RakuAST::Name"; dd ::($a) 15:48
committable6 [Coke], ¦HEAD(bba73cd): «RakuAST::Name␤»
16:18 zostay left, disbot left, disbot joined 16:19 zostay joined
[Coke] c: HEAD dd "asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+) (\s || $) / 16:43
committable6 [Coke], gist.github.com/2da2d78f6aca2ac6d0...004897e297
[Coke] c: HEAD dd ("asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+) (\s || $) /).map(*<word>) 16:44
committable6 [Coke], ¦HEAD(bba73cd): «(Match.new(:orig("asdf Signature"), :from(0), :pos(4)),).Seq␤»
[Coke] c: HEAD dd ("asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+) (\s || $) /).map(*<word>).flat
committable6 [Coke], ¦HEAD(bba73cd): «(Match.new(:orig("asdf Signature"), :from(0), :pos(4)),).Seq␤»
[Coke] c: HEAD dd ("asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+) (\s || $) /).map(*<word>.Str)
committable6 [Coke], ¦HEAD(bba73cd): «("asdf",).Seq␤»
[Coke] why doesn't that include Signature?
I'm assuming I've done something horrible dumb.
c: HEAD dd ("asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+)? /).map(*<word>.Str) 16:50
committable6 [Coke], ¦HEAD(bba73cd): «("asdf", "Signature").Seq␤»
[Coke] that feels like cheating, but fine. :)
c: HEAD dd ("asdf Signature" ~~ m:g/ (\s || ^ ) $<word>=( \S+) /).map(*<word>.Str) 16:51
committable6 [Coke], ¦HEAD(bba73cd): «("asdf", "Signature").Seq␤»
[Coke] c: HEAD use experimental :macros 17:16
committable6 [Coke], gist.github.com/4594a9b0209046e3da...eba6b55bf0
[Coke] ok, there's a bunch of current doc failures.
Geth setup-raku/dependabot/npm_and_yarn/multi-456d42d8d4: fc3c95bdff | dependabot[bot]++ (committed using GitHub Web editor) | 2 files
Bump @vitest/mocker and vitest

Bumps [@vitest/mocker](github.com/vitest-dev/vitest/tree/...es/mocker) to 4.1.12 and updates ancestor dependency [vitest](github.com/vitest-dev/vitest/tree/...s/vitest). These dependencies need to be updated together.
Updates `@vitest/mocker` from 4.1.11 to 4.1.12
  - [Release notes](github.com/vitest-dev/vitest/releases)
... (19 more lines)		 17:34
setup-raku: dependabot[bot]++ created pull request #66:
Bump @vitest/mocker and vitest
setup-raku: 802acf072c | dependabot[bot]++ (committed using GitHub Web editor) | 2 files
Bump @vitest/mocker and vitest (#66)

Bumps [@vitest/mocker](github.com/vitest-dev/vitest/tree/...es/mocker) to 4.1.12 and updates ancestor dependency [vitest](github.com/vitest-dev/vitest/tree/...s/vitest). These dependencies need to be updated together.
Updates `@vitest/mocker` from 4.1.11 to 4.1.12
  - [Release notes](github.com/vitest-dev/vitest/releases)
... (20 more lines)		 18:05
setup-raku/dependabot/npm_and_yarn/undici-6.29.1: 82a914afce | dependabot[bot]++ (committed using GitHub Web editor) | package-lock.json
Bump undici from 6.29.0 to 6.29.1

Bumps [undici](github.com/nodejs/undici) from 6.29.0 to 6.29.1.
  - [Release notes](github.com/nodejs/undici/releases)
  - [Commits](github.com/nodejs/undici/compare/v.....v6.29.1)
  ---
... (7 more lines)		 18:06
setup-raku: dependabot[bot]++ created pull request #67:
Bump undici from 6.29.0 to 6.29.1
ab5tract patrickb: I assumed it must be some obstacle as it hadn’t been ripped out yet 18:20
s/it/there/ 18:21
evalable6 Use of uninitialized value $_ of type Any in string context.
Methods .^name, .raku, .gist, or .say can be used to stringify it to something meaningful.
in block <unit> at /tmp/4QfPAqlRm9 line 1
18:47 hurufu joined
Geth setup-raku: 82a4382a9b | dependabot[bot]++ (committed using GitHub Web editor) | package-lock.json
Bump undici from 6.29.0 to 6.29.1 (#67)

Bumps [undici](github.com/nodejs/undici) from 6.29.0 to 6.29.1.
  - [Release notes](github.com/nodejs/undici/releases)
  - [Commits](github.com/nodejs/undici/compare/v.....v6.29.1)
  ---
... (8 more lines)		 19:25
setup-raku/codex/update-all-dependencies: f278302219 | (Shoichi Kaji)++ | 3 files
Update development dependencies and rebuild action

Co-authored-by: Codex <267193182+codex@users.noreply.github.com>		 19:37
setup-raku: f278302219 | (Shoichi Kaji)++ | 3 files
Update development dependencies and rebuild action

Co-authored-by: Codex <267193182+codex@users.noreply.github.com>		 19:40
setup-raku: 8602b35728 | (Shoichi Kaji)++ | CHANGELOG.md
v1.15.0
patrickb ab5tract: Not as far as I know. We wanted to keep it in for a bit after disabling just to be safe. And since then nobody cared enough to actually do it. I'm pretty sure it will be a fair bit of work, but not insurmountable. One will need to build up a fair bit of knowledge to confidently remove all the things all over the code base, but I guess one will be naturally guided to all the places 19:55
that need touching.
19:57 hurufu left
patrickb If I had one wish for the person doing this: Do keep a log of all the relevant touch points and document how the pieces fit together. That will make the job of someone in the future that wants to add a jit back in a lot easier. 19:57
19:59 hurufu joined 20:18 hurufu left 20:19 hurufu joined 22:40 hurufu left
[Coke] failure from the doc examples: 22:55
c: HEAD my $counter = 0; my $result = sink for ^5 { $counter++ };
committable6 [Coke], ¦HEAD(bba73cd): «===SORRY!===␤Do not use this statement prefix on a RakuAST::Statement::For; instead, set the mode on that node␤ «exit code = 1»»
[Coke] bisectable6: my $counter = 0; my $result = sink for ^5 { $counter++ }; 22:58
bisectable6 [Coke], Will bisect the whole range automagically because no endpoints were provided, hang tight
[Coke], Output on all releases: gist.github.com/2d8e9de94cab94ef4a...d35625362d 22:59
[Coke], Bisecting by exit code (old=2026.08 new=2026.09). Old exit code: 0
[Coke], bisect log: gist.github.com/784c926c1dcad59a12...aa825bd9a7
[Coke], (2026-09-22) github.com/rakudo/rakudo/commit/f0...b3348dbcb0
[Coke], Output on all releases and bisected commits: gist.github.com/2429c772f697504f6d...5c0159db46
[Coke] looks like taht changed just in 2026.09 - need a bug for that? 23:05
lizmat yes please 23:23
23:30 iwuvmika joined

Powered by Cro and the Raku® Programming Language.

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

Thank you!