Christian Bartolomäus

Why are 403 response codes sent while ROR plugin isn't initiated?

3

After upgrading to ROR 1.37.0 I saw some issues with clients that got back a ```403``` response code for requests to a freshly restarted elasticsearch node. At that point the...

When doing some experiments with encoding different strings with utf16 I've stumbled upon cases where a trailing character was missing from the buffer (that holds the encoded string): ``` $...

[JVM] Sometimes last character of stdout is reported as stderr in procasync test

2

## The Problem I've seen random test failures on the JVM backend for [a test from S17-procasync/basic.t](https://github.com/Raku/roast/blob/b26901106d/S17-procasync/basic.t#L167-L178). ``` S17-procasync/basic.rakudo.jvm..................... # Failed test 'stdout is good' # at t/spec/S17-procasync/basic.rakudo.jvm line 177...

[JVM] Error when trying to assign to variable typed as native int and use the result of the expression directly as key for nqp::hash

11

## The Problem Starting with https://github.com/rakudo/rakudo/commit/369093c837 a new error surfaced on the JVM backend: ``` $ ./rakudo-j --ll-exception -e 'my @arr := array[int].new(42); say @arr.repeated' This container does not reference...

[JVM] nqp::attrinited does not work for natives

2

The nqp::attrinited op always returns 1 for native attributes on the JVM backend. ``` r: use nqp; class Foo { has int $.foo }; my $a := Foo.new( ); say...

Starting from the bug reported in https://github.com/Raku/nqp/issues/250 it turned out that the old implementation gave different results than MoarVM for all buffer types (at least in some cases). The new...

[JVM] Java limit for method code size can be hit by defining large hashes

1

In https://github.com/rakudo/rakudo/pull/4397 an unexpected error showed up: Java's limit of 65535 bytes for the code length of methods is hit, if a hash with many entries is defined. * [Limitations...

Different implementation for nqp::substr for Moar and [JVM] (negative offset)

1

The implementation of nqp::substr differs between Moar and JVM with regard to negative offsets: ``` bartolin r: use nqp; say nqp::substr("bar", -1, 1) camelia rakudo-moar 054aca: OUTPUT«r␤» camelia ..rakudo-jvm 76b061:...

This is the current behaviour of nqp::substr on the different backends with regard to negative values for ```$position``` and ```$length```: ```my $s := 'foobar'``` | Code | Result on MoarVM...