Closed greenfork closed 5 months ago
reproduced... :(
I'll try to find the reason.
Thanks for finding it.
It seems it's something wrong with rakudo itself and @lizmat is going to investigate (https://irclogs.raku.org/raku-dev/2024-04-11.html#01:20)
Yeah we shouldn't be seeing an NQPRoutine in user code at all (unless you explicitly wanted one.)
https://github.com/rakudo/rakudo/commit/f329c52d29 has fixed this, afaik.
The problem was not the NQPRoutine
leaking into Raku HLL Land, but the default build logic only accepting HLL code. By using a low level check for invokability, this problem has gone away.
The error message was caused by the fact that since it was not recognized as executable code, it was assumed to be an nqp::list
, which caused the error observed.
It seems it brings this issue beck: https://github.com/FCO/Red/issues/573
For now I have released this: https://github.com/FCO/Red/commit/2bce11b7b1e1a6e76d5a121e81da9c4a05111b35
It seems to be fixed now! Thanks @greenfork for opening the issue and @lizmat for fixing it!
totally caught me as I have an application the runs in docker with the image based on rakudo-star:latest
(and I forgot about this issue in the interim.) :boom: :rofl:
I'm wondering whether it would be possible to set up a GitHub action that's triggered by commits on the master of rakudo (so Red@HEAD is also tested against rakudo@HEAD,) Red is a good canary for weirdness in the HOW level.
is it possible to do it on red's side? i'm not very fluent on github actions... but if people wanted to do that on rakudo side it would also be great! but I thought that was the intent for blib...
At one point I had a local Jenkins instance that did this for all of my modules, but I stopped it because I was turning into a bit of time sink (and the machine I was running it on was a bit puny for a hulking great Java application to be running nearly continuously,) but that was before Actions.
But you can either trigger a workflow on a cron-like schedule (e.g. daily) or via a web hook from another repo, obviously the latter would require some support within the rakudo repo, and both would require building rakudo from scratch (as far as I know there is no nightly build.)
I was wrong about the nightly build https://hub.docker.com/r/tonyodell/rakudo-nightly/, never noticed it before.
After doing
zef install Red
Failing tests log