| 23 Sep 2025 | |||
| ab5tract | lizmat: thanks! | 07:58 | |
| The issue I'm having with the EVAL stuff is that when the EVAL CU visits its doc vars, I get re-declaration errors | 08:00 | ||
| I've got to run now but I'll get the output you mentioned in your comment this afternoon hopefully | |||
| Geth | rakudo/r5855-finish-shenanigans: d69369f8f3 | ab5tract++ | 2 files Broken :( |
08:04 | |
| rakudo/r5855-finish-shenanigans: 912e74ebdc | ab5tract++ | 2 files Only two test still failing |
|||
| rakudo/r5855-finish-shenanigans: a3a12e753d | ab5tract++ | src/Raku/ast/code.rakumod Still doc-declarator |
|||
| ab5tract | hmm, I thought it would have pushed to the open PR, I guess I made another branch | ||
| afk& | |||
| [Coke] ponders where to post a small update about getting us onboarded with Snyk, and guesses bluesky is fine? | 12:59 | ||
| lizmat | dev.to ? | 13:02 | |
| releasable6 | Next release in ≈4 days and ≈3 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft | 15:00 | |
| [Coke] | That is not true. | 16:03 | |
| Might need to update the "next release date" in the release guide. | 16:07 | ||
| Geth | rakudo/main: 86d216d3fa | Coke++ | docs/release_guide.pod No release this month |
16:22 | |
| [Coke] | releasable6: next | ||
| releasable6 | [Coke], Next release in ≈4 days and ≈2 hours. There are no known blockers. 0 out of 6 commits logged | 16:23 | |
| [Coke], Details: gist.github.com/371113f6b9647665b2...e5ebaac110 | |||
| [Coke] | let's see if that updates in the next hour or so | ||
| releasable6: next | 16:30 | ||
| releasable6 | [Coke], Next release in ≈25 days and ≈2 hours. There are no known blockers. 0 out of 7 commits logged | ||
| [Coke], Details: gist.github.com/e02c2766f608ba18db...7e35bb28c3 | |||
| [Coke] | github.com/rakudo/docker/blob/mast...Dockerfile - why do we rename the dockerfile every release? | 23:37 | |
| if we kept the historic ones it might make sense, but it looks like we create a new one and delete the old one. | 23:40 | ||
| (makes it slightly harder to deal with repository scanning - I just had to rescan to get the new ones, and then manually delete the old ones that had already been id'd by Snyk) | 23:43 | ||
| 24 Sep 2025 | |||
| releasable6 | Next release in ≈24 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 | |
| [Coke] | releasable6: next | 11:56 | |
| releasable6 | [Coke], Next release in ≈24 days and ≈7 hours. There are no known blockers. 4 out of 7 commits logged | ||
| [Coke], Details: gist.github.com/ce63e2acfe50360423...76b5ffb2ed | |||
| [Coke] sads. | 15:59 | ||
| Geth | ¦ rakudo: patrickbkr self-assigned Deference of a NULL Pointer github.com/rakudo/rakudo/issues/5957 | 19:33 | |
| [Coke] | patrickb: there are more where that came from. | 19:46 | |
| Do you want direct access to Snyk? | |||
| patrickb | I'd prefer GH issues, but if that annoys you too much, then Snyk it is. | 19:47 | |
| [Coke] | Nope, I can get them over into GH | ||
| Added all the null pointer issues from rakudo/rakudo to gh issues | 19:57 | ||
| I'll rescan in Snyk as needed to close them out | 19:58 | ||
| there's also "path traversal", "use after free", "missing release of memory", "integer overflow" and one "user controlled pointer" | 19:59 | ||
| I'll eventually get them all in as GH issues, but if there's anything that sounds "fun", lemme know | 20:01 | ||
| .seen geth | |||
| tellable6 | [Coke], I saw geth 2025-09-24T19:33:41Z in #raku-dev: <Geth> ¦ rakudo: patrickbkr self-assigned ␂Deference of a NULL Pointer github.com/rakudo/rakudo/issues/5957 | ||
| [Coke] | ... oh, right. Oops | ||
| patrickb: You might also be the right person for github.com/rakudo/rakudo/pull/5956 ? | 20:03 | ||
| patrickb | I am. The PR needs to be rejected. We explicitly want an as old as possible OS when building Rakudo. This is what allows Rakudo to run on such old OSes (that's the fun of glibc forward, but not backward compatibility). | 20:07 | |
| [Coke] | there are 0 Critical, 1 High, 32 Medium, and 64 Low issues in the existing docker image. | 20:25 | |
| 22.04 has 3M, 14L. | |||
| Is it just being used to build? | 20:26 | ||
| I can silence the alerts in Snyk about the dockerfile if needed. | 20:27 | ||
| huh. one of the mediums is perl/perl-base Improper Certificate Validation | |||
| (sadly, I think I can only put in an ignore message at an issue level; for a "project" like a dockerfile, I can just deactivate it. | 20:29 | ||
| patrickb | Coke: It's exclusively being used to build the pre built rakudo release files. | 21:08 | |
| [Coke] | Cool. | 21:23 | |
| deactivated that dockerfile project. | 21:30 | ||
| patrickb: do you know anything about the dockerfiles in rakudo/star? Can those be upgraded? | |||
| patrickb | I have near to no knowledge about star. Sorry. | 21:35 | |
| [Coke] | no worries, thanks for helping me close some of these out! | 21:43 | |
| [Coke] opens github.com/rakudo/docker/issues/74 | 22:00 | ||