A non-numeric value encountered in Stacktrace.php

[Deifinger]

I get string $index and observe "A non-numeric value encountered" error

Please, take a look at my solution. I'm not sure that this is correct fix and the root of the problem

[ste93cry]

It would be cool if you could share a little script reproducing the problem of if you can debug and tell us what's the value of the $index variable.

[Deifinger]

@ste93cry That's my state before exception:

$argument = "???"
$index = "container"
$maxValueLength = 1024
$frame = Array
(
    [function] => "Illuminate\Container\{closure}"
    [type] => "->"
    [class] => "Illuminate\Foundation\Application"
    [file] => "/var/www/app/vendor/laravel/framework/src/Illuminate/Container/Container.php"
    [line] => 776
    [args] => Array
        (
            [container] => "???"
            [parameters] => "???"
        )

)

That happends when I make some Fatal error. See my example:

PHP Fatal error: Declaration of App\Utils\Sitemap\Generators\IndexGenerator::setAlias(string $alias) must be compatible with App\Utils\Sitemap\Contracts\Generator::setAlias(string $alias): App\Utils\Sitemap\Contracts\Generator in /var/www/app/app/Utils/Sitemap/Generators/IndexGenerator.php on line 9

[ste93cry]

Are you using XDebug or some other debug extension? If so, can you try disabling it and retrying?

[Deifinger]

@ste93cry Yeah, I have XDebug in my project. When I disabled it, the error disappeared.

[ste93cry]

So, the culprit of the problem as we found out is XDebug. The error occurs because it changes how the arguments of a stacktrace frame are reported by using the argument name as key of each value of the $args variable instead of its 0-based position in the function signature. Blindly casting $index to an integer then would result in some indesiderate results (e.g. foo would be converted to 0). The best fix we can do is to check whether the $index variable is a string or an integer and act accordingly. However, this exact same issue should have been fixed in #761 which is the reason why there is an if/else statement wrapping the loop, so I don't get why it happens and it would be cool if you could debug a bit more in depth to see what's happening

[sztyup]

The screenshot you provided does not contain the fix by #763, could you make sure you are using the latest version of the library and see if the issue is still there?

[ste93cry]

The screenshot you provided does not contain the fix by #763

Good catch, I didn’t even noticed it!

[Deifinger]

I'm going to update dependency on Monday and check the result

[Deifinger]

@ste93cry Sorry for delay. I updated dependencies and now all works fine. I have the next versions:
sentry/sdk 2.0.2
sentry/sentry 2.0.1

Ticket going to be closed.