[00:08] *** reportable6 left [00:09] *** reportable6 joined [00:38] *** [Coke] left [00:42] *** [Coke] joined [01:53] ¦ rakudo: vrurg++ created pull request #5003: Fix some cases of coercion over containerized values [01:53] ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/5003 [01:56] jdv: what kind of issue was it? I remember no details on this. [02:21] *** evalable6 left [02:21] *** linkable6 left [02:23] *** linkable6 joined [02:24] *** evalable6 joined [02:47] iirc it was related to your changes [02:53] the reason for this: https://github.com/FCO/Red/commit/bdd5bbdf8f8c4255bc9c74f0021886b9a726fb2a [02:53] vrurg: ^ [02:54] SmokeMachine: do you know if thats fixed yet? [02:56] I'm afraid, more input would be needed. Vaguely recall that there was an issue opened, wasn't it? [02:57] ¦ rakudo: fbe3acd007 | (Vadim Belman)++ | 2 files [02:57] ¦ rakudo: Fix some cases of coercion over containerized values [02:57] ¦ rakudo: [02:57] ¦ rakudo: - The dispatcher itself never expects a containerized coercer, but it [02:57] ¦ rakudo: was possible for the metamodel to bypass a container [02:57] ¦ rakudo: - The scalar case of value was considerd, but `Proxy` has been [02:57] ¦ rakudo: overlooked; if there be any other kind of container it should be [02:57] ¦ rakudo: handled appropriately too [02:57] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/fbe3acd007 [02:57] ¦ rakudo: 02f32d510b | (Vadim Belman)++ | src/vm/moar/dispatchers.nqp [02:57] ¦ rakudo: Remove now unused 'raku-coerce' dispatcher [02:57] ¦ rakudo: [02:57] ¦ rakudo: It was part of the old return value coercion implementation. [02:57] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/02f32d510b [02:57] ¦ rakudo: aa5e680052 | (Vadim Belman)++ (committed using GitHub Web editor) | 2 files [02:58] ¦ rakudo: Merge pull request #5003 from vrurg/rakudo-5002 [02:58] ¦ rakudo: [02:58] ¦ rakudo: Fix some cases of coercion over containerized values [02:58] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/aa5e680052 [03:24] *** linkable6 left [03:24] *** evalable6 left [03:27] *** linkable6 joined [03:27] *** evalable6 joined [04:16] *** vrurg left [04:17] *** vrurg joined [05:04] *** jjatria left [05:04] *** jjatria joined [05:07] *** tailgate left [05:07] *** bartolin_ left [05:07] *** JRaspass left [05:07] *** bartolin joined [05:08] *** JRaspass joined [05:09] *** tailgate joined [06:07] *** reportable6 left [06:09] *** reportable6 joined [07:08] vrurg: Confirmed that gives a clean build, Getopt::Long too. :-) [07:09] *** evalable6 left [07:09] *** linkable6 left [07:11] *** evalable6 joined [07:12] *** linkable6 joined [07:51] *** sena_kun joined [07:54] *** ab5tract joined [07:56] *** sena_kun left [07:57] *** sena_kun joined [07:58] jdv: yes, I think lizmat has fixed that: https://irclogs.raku.org/raku-dev/2022-06-08.html#13:39 [08:18] *** jdv left [08:24] *** jdv joined [08:26] ¦ JSON-Unmarshal/main: b500bfa329 | (Elizabeth Mattijsen)++ | 2 files [08:26] ¦ JSON-Unmarshal/main: 0.11 [08:26] ¦ JSON-Unmarshal/main: review: https://github.com/raku-community-modules/JSON-Unmarshal/commit/b500bfa329 [08:58] *** ab5tract left [09:17] *** sena_kun left [10:01] *** sena_kun joined [10:05] *** Kaiepi left [10:07] *** Kaiepi joined [11:07] *** evalable6 left [11:07] *** linkable6 left [11:09] *** evalable6 joined [11:10] *** linkable6 joined [12:06] *** reportable6 left [12:07] *** [Coke] left [12:09] *** reportable6 joined [12:11] *** Xliff left [12:27] *** [Coke] joined [13:20] <[Coke]> patrickb: (rakuw) not in particular no. I'm a windows user, but not a power user. [13:27] *** evalable6 left [13:27] *** linkable6 left [13:28] ¦ JSON-Unmarshal/main: 4 commits pushed by (Jonathan Stowe)++, (Elizabeth Mattijsen)++, (Vadim Belman)++ [13:28] ¦ JSON-Unmarshal/main: 4248213b3b | Add an opt-in option to unmarshal [13:28] ¦ JSON-Unmarshal/main: c28340a4e4 | Undo up version [13:28] ¦ JSON-Unmarshal/main: 860db75a4b | Merge branch 'main' into opt-in [13:28] ¦ JSON-Unmarshal/main: ec2b22590d | Merge pull request #1 from jonathanstowe/opt-in [13:28] ¦ JSON-Unmarshal/main: review: https://github.com/raku-community-modules/JSON-Unmarshal/compare/b500bfa32963...ec2b22590d47 [13:30] *** linkable6 joined [13:30] *** evalable6 joined [13:47] [Coke]: So you can't reproduce either? [13:54] *** Xliff joined [14:01] and yet another Rakudo Weekly News hits the Net: https://rakudoweekly.blog/2022/07/25/2022-30-what/ [14:28] *** sena_kun left [14:28] *** Altai-man joined [14:51] SmokeMachine: ok. just to confirm - you're good on HEAD now? [14:57] *** melezhik joined [15:00] Next release in ≈4 days and ≈3 hours. 1 blocker. Please log your changes in the ChangeLog: https://github.com/rakudo/rakudo/wiki/ChangeLog-Draft [15:08] <[Coke]> patrickb: if it was the behavior I reported, nothing has changed. [15:11] [Coke]: How do you run `rakuw -e 'say 3'`? [15:12] Typing that into a Windows Terminal Window on my end outputs nothing. [15:20] *** melezhik left [16:22] *** patrickb left [16:27] *** patrickb joined [16:34] *** patrickb left [16:36] *** patrickb joined [17:06] *** Altai-man left [17:21] *** patrickb left [17:22] *** patrickb joined [17:27] <[Coke]> patrickb: ah. different behavior in git bash vs. cmd [17:27] <[Coke]> makes sense, I probably had git bash open by default. [17:34] [Coke]: I guess all is fine then. :) [17:42] *** sena_kun joined [17:51] *** lizmat_ joined [17:52] *** discord-raku-bot left [17:53] *** gfldex left [17:55] *** lizmat left [17:55] *** Xliff left [18:00] *** lizmat_ is now known as lizmat [18:03] ¦ rakudo/lizmat-died-naturally: eb731f7355 | (Elizabeth Mattijsen)++ | src/main.nqp [18:03] ¦ rakudo/lizmat-died-naturally: s/DIED-NATURALLY/DIED/ [18:03] ¦ rakudo/lizmat-died-naturally: [18:03] ¦ rakudo/lizmat-died-naturally: Indeed. Any other way to finish a program, is by not die-ing :-) [18:03] ¦ rakudo/lizmat-died-naturally: review: https://github.com/rakudo/rakudo/commit/eb731f7355 [18:06] *** reportable6 left [18:09] *** reportable6 joined [18:55] *** sena_kun left [18:56] *** sena_kun joined [19:05] Other way to finish a program is to inject exit syscall to it [19:06] > gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont' [19:06] (copied from https://gist.github.com/moyix/95ca9a7a26a639b2322c36c7411dc3be ) [19:27] apparently this is how you fence in java? https://openjdk.org/jeps/171 [19:27] atomic ints are ok, but fencing is Unsafe (???) [19:49] *** sena_kun left [19:50] *** sena_kun joined [20:25] *** vrurg left [21:00] lizmat: so you know. changes are probably for the best. [21:14] *** discord-raku-bot joined [21:20] *** discord-raku-bot left [21:20] *** discord-raku-bot joined [21:27] *** gfldex joined [21:28] *** discord-raku-bot left [21:29] *** discord-raku-bot joined [21:38] *** kjp joined [21:41] *** sena_kun left [21:49] jdv? [22:11] bisectable6: old=2019.11 say http://Date.new('2015-11-24').last-date-in-month; [22:11] lizmat, On both starting points (old=2019.11 new=aa5e680) the exit code is 1 and the output is identical as well [22:11] lizmat, Output on both points: «4===SORRY!4=== Error while compiling /tmp/XZJSQJxlY6␤Confused␤at /tmp/XZJSQJxlY6:1␤------> 3say http:8⏏4//Date.new('2015-11-24').last-date-in-mo␤ expecting any of:␤ colon pair␤» [22:12] bisectable6: old=2019.11 say Date.new('2015-11-24').last-date-in-month; [22:12] lizmat, Bisecting by exit code (old=2019.11 new=aa5e680). Old exit code: 1 [22:12] *** vrurg joined [22:14] lizmat, and I oop! Backtrace: https://gist.github.com/f2a65e8dcce52c87749b7a0cfbe51aaf [22:15] meh [22:15] first in 2020.05 I believe [22:15] sleep& [22:33] *** discord-raku-bot left [22:33] *** discord-raku-bot joined [22:39] *** melezhik joined [22:56] *** melezhik left [23:12] *** maettu left [23:38] *** maettu joined [23:48] LAPTOP-7I9RCT0C% nqp-j -e 'nqp::barrierfull()' [23:48] LAPTOP-7I9RCT0C% [23:48] partway there... [23:48] there's a way to do this without dumping more warnings in logs