Process completed with exit code 1.

The strategy configuration was canceled because "run.ubuntu-latest_8_4" failed

The operation was canceled.

The strategy configuration was canceled because "run.ubuntu-latest_8_4" failed

The operation was canceled.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

Casting `mixed` to `bool`. >This expression has type `mixed` The truthiness of `mixed` cannot be determined statically. The result will be a general `bool`. Help: Consider adding type assertions or checks if a more specific boolean outcome is expected.

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.

Redundant null coalesce: left-hand side can never be `null` or undefined. >This expression (type `array{}|list<array{'answer': string, 'category_id': int(0), 'content_type': string('page'), 'id': int, 'keywords': string(''), 'lang': string, 'question': string, 'slug': string}|array{'index': array{'_id': truthy-string, '_index': string}}>`) is never `null` or undefined >This right-hand side will never be evaluated The null coalesce operator `??` only evaluates the right-hand side if the left-hand side is `null` or not set. Help: Consider removing the `??` operator and the right-hand side expression.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant condition: variable `$info->response` is already known to be `has-property<'clientDataJSON'>`. >This condition always evaluates to true The type of variable `$info->response` already satisfies the condition that it is `has-property<'clientDataJSON'>`. This check is redundant. Help: This condition is always true and the associated code block will always execute if reached. Consider simplifying.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Redundant null coalesce: left-hand side can never be `null` or undefined. >This expression (type `array{}|list<array{'answer': string, 'category_id': int(0), 'content_type': string('page'), 'id': int, 'keywords': string(''), 'lang': string, 'question': string, 'slug': string}|array{'index': array{'_id': truthy-string, '_index': string}}>`) is never `null` or undefined >This right-hand side will never be evaluated The null coalesce operator `??` only evaluates the right-hand side if the left-hand side is `null` or not set. Help: Consider removing the `??` operator and the right-hand side expression.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant condition: variable `$info->response` is already known to be `has-property<'clientDataJSON'>`. >This condition always evaluates to true The type of variable `$info->response` already satisfies the condition that it is `has-property<'clientDataJSON'>`. This check is redundant. Help: This condition is always true and the associated code block will always execute if reached. Consider simplifying.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Redundant null coalesce: left-hand side can never be `null` or undefined. >This expression (type `array{}|list<array{'answer': string, 'category_id': int(0), 'content_type': string('page'), 'id': int, 'keywords': string(''), 'lang': string, 'question': string, 'slug': string}|array{'index': array{'_id': truthy-string, '_index': string}}>`) is never `null` or undefined >This right-hand side will never be evaluated The null coalesce operator `??` only evaluates the right-hand side if the left-hand side is `null` or not set. Help: Consider removing the `??` operator and the right-hand side expression.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant cast to `(string)`: the expression already has this type. >This expression already has type `string`. Casting a value to a type it already possesses has no effect. Help: Remove the redundant `(string)` cast.

Redundant condition: variable `$info->response` is already known to be `has-property<'clientDataJSON'>`. >This condition always evaluates to true The type of variable `$info->response` already satisfies the condition that it is `has-property<'clientDataJSON'>`. This check is redundant. Help: This condition is always true and the associated code block will always execute if reached. Consider simplifying.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.