Error running with numeric environment variable name

[desmana]

Bug report

Having variables with numeric names being present in the environment results in the following error:

$ env 1=1 ./phpstan
The key of item 'parameters › env › 1' expects to be string, 1 given.

I'm using PHPStan version 1.11.x-dev@a72400b from this repository.

Code snippet that reproduces the problem

No response

Expected output

Program should run normally:

$ env 1=1 ./phpstan
At least one path must be specified to analyse.

Did PHPStan help you today? Did it make you happy in any way?

No response

[mergeable]

This bug report is missing a link to reproduction at phpstan.org/try.

It will most likely be closed after manual review.

[ondrejmirtes]

Reproduced: phpstan/phpstan-src@24d990b
Fixed: phpstan/phpstan-src@e606fbe

[staabm]

@desmana interessting, I never needed a numeric env var. could you give a bit more detail when/how you need that? I am just curious.

[desmana]

@staabm CI stack I'm running uses execline script from s6 supervision suite. If you're not familiar, think of execline as a specialized bash alternative for scripting. By default execline sets environment variables 1 2 ... 9 to positional arguments $1 $2 ... $9

I did some research before submitting the report. It's not recommended by POSIX to use such variables:

Other applications may have difficulty dealing with environment variable names that start with a digit. For this reason, use of such names is not recommended anywhere.

They're not trivial to set either. For example bash refuses to accept this:

$ export 1=1
bash: export: `1=1': not a valid identifier

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.