Process completed with exit code 1.

Argument type mismatch for argument #2 of `vsprintf`: expected `array<array-key, Stringable|null|scalar>`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>` or adjust the parameter type.

Invalid type for property `$profiles`: expected `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`, but got `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>`. >This expression has type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` >This property `$profiles` is declared with type `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>` --- original +++ modified @@ -1,10 +1,10 @@ -array< +non-empty-array< array-key, array{ 'elapse': float | null, 'end': float | null, 'parameters': PhpDb\Adapter\ParameterContainer | null, - 'sql': string, + 'sql': null | string, 'start': float, }, > The type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` is not compatible with and cannot be assigned to `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`. Help: Change the assigned value to match the property's type, or update the property's type declaration.

Returned type `array{'spec': string, 'values': list<mixed>}` is less specific than the declared return type `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` for function `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` due to nested 'mixed'. >Returned value's type is too general here due to nested mixed The analysis detected 'mixed' within the structure of the returned value, making the overall type less specific than what the function declared. --- original +++ modified @@ -1,4 +1,4 @@ array{ 'spec': string, - 'values': array<array-key, PhpDb\Sql\ArgumentInterface>, + 'values': list<mixed>, } Help: Ensure the structure returned by `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` strictly adheres to the types specified in the `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` return type declaration.

Argument type mismatch for argument #2 of `implode`: expected `array<array-key, Stringable|null|scalar>|null`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>|null` or adjust the parameter type.

Process completed with exit code 1.

Process completed with exit code 1.

Argument type mismatch for argument #2 of `vsprintf`: expected `array<array-key, Stringable|null|scalar>`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>` or adjust the parameter type.

Invalid type for property `$profiles`: expected `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`, but got `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>`. >This expression has type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` >This property `$profiles` is declared with type `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>` --- original +++ modified @@ -1,10 +1,10 @@ -array< +non-empty-array< array-key, array{ 'elapse': float | null, 'end': float | null, 'parameters': PhpDb\Adapter\ParameterContainer | null, - 'sql': string, + 'sql': null | string, 'start': float, }, > The type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` is not compatible with and cannot be assigned to `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`. Help: Change the assigned value to match the property's type, or update the property's type declaration.

Returned type `array{'spec': string, 'values': list<mixed>}` is less specific than the declared return type `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` for function `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` due to nested 'mixed'. >Returned value's type is too general here due to nested mixed The analysis detected 'mixed' within the structure of the returned value, making the overall type less specific than what the function declared. --- original +++ modified @@ -1,4 +1,4 @@ array{ 'spec': string, - 'values': array<array-key, PhpDb\Sql\ArgumentInterface>, + 'values': list<mixed>, } Help: Ensure the structure returned by `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` strictly adheres to the types specified in the `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` return type declaration.

Argument type mismatch for argument #2 of `implode`: expected `array<array-key, Stringable|null|scalar>|null`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>|null` or adjust the parameter type.

Process completed with exit code 1.

Process completed with exit code 1.

Argument type mismatch for argument #2 of `vsprintf`: expected `array<array-key, Stringable|null|scalar>`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>` or adjust the parameter type.

Invalid type for property `$profiles`: expected `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`, but got `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>`. >This expression has type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` >This property `$profiles` is declared with type `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>` --- original +++ modified @@ -1,10 +1,10 @@ -array< +non-empty-array< array-key, array{ 'elapse': float | null, 'end': float | null, 'parameters': PhpDb\Adapter\ParameterContainer | null, - 'sql': string, + 'sql': null | string, 'start': float, }, > The type `non-empty-array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': null|string, 'start': float}>` is not compatible with and cannot be assigned to `array<array-key, array{'elapse': float|null, 'end': float|null, 'parameters': PhpDb\Adapter\ParameterContainer|null, 'sql': string, 'start': float}>`. Help: Change the assigned value to match the property's type, or update the property's type declaration.

Returned type `array{'spec': string, 'values': list<mixed>}` is less specific than the declared return type `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` for function `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` due to nested 'mixed'. >Returned value's type is too general here due to nested mixed The analysis detected 'mixed' within the structure of the returned value, making the overall type less specific than what the function declared. --- original +++ modified @@ -1,4 +1,4 @@ array{ 'spec': string, - 'values': array<array-key, PhpDb\Sql\ArgumentInterface>, + 'values': list<mixed>, } Help: Ensure the structure returned by `PhpDb\Sql\Predicate\PredicateSet::getExpressionData` strictly adheres to the types specified in the `array{'spec': string, 'values': array<array-key, PhpDb\Sql\ArgumentInterface>}` return type declaration.

Argument type mismatch for argument #2 of `implode`: expected `array<array-key, Stringable|null|scalar>|null`, but provided type `list<mixed>` is less specific. >Provided type `list<mixed>` is too general due to nested `mixed`. >Arguments to this function are incorrect The structure contains `mixed`, making it incompatible. Help: Provide a value that more precisely matches `array<array-key, Stringable|null|scalar>|null` or adjust the parameter type.

Process completed with exit code 1.

Process completed with exit code 1.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, string>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, array<array-key, mixed>>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

This member selector uses a non-literal string type (`string`); its specific value cannot be statically determined. >This expression (type `string`) provides the member name While this may work at runtime, its existence and type cannot be checked statically.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, string>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, array<array-key, mixed>>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

This member selector uses a non-literal string type (`string`); its specific value cannot be statically determined. >This expression (type `string`) provides the member name While this may work at runtime, its existence and type cannot be checked statically.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, string>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('combinedBy')` accessed on `array<array-key, array<array-key, mixed>>`. >Key `string('combinedBy')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('combinedBy') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

This member selector uses a non-literal string type (`string`); its specific value cannot be statically determined. >This expression (type `string`) provides the member name While this may work at runtime, its existence and type cannot be checked statically.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

This pragma was not used and may be removed. >This expect pragma was not fulfilled. >...for this code >...within this comment.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Property `$magicSpecifications` is never used. >Property `$magicSpecifications` is declared here. This property is declared but never read or written within the class. Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Property `$magicSpecifications` is never used. >Property `$magicSpecifications` is declared here. This property is declared but never read or written within the class. Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Property `$magicSpecifications` is never used. >Property `$magicSpecifications` is declared here. This property is declared but never read or written within the class. Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"