IBX-8418: Remove draft when trashing its parent or ancestor location #2043
ci.yaml
on: pull_request
Matrix: Unit tests & SQLite integration tests
Matrix: Run code style check
Matrix: Solr integration tests
Matrix: MySQL integration tests
Matrix: PostgreSQL integration tests
Annotations
30 errors and 35 warnings
Unit tests & SQLite integration tests (8.1):
src/lib/FieldType/Image/ImageStorage.php#L1
Ignored error pattern #^Cannot access offset 0 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/FieldType/Image/ImageStorage.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/FieldType/Image/ImageStorage.php#L1
Ignored error pattern #^Cannot access offset 1 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/FieldType/Image/ImageStorage.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/FieldType/Image/ImageStorage.php#L110
Cannot access offset 0 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.1):
src/lib/FieldType/Image/ImageStorage.php#L111
Cannot access offset 1 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 'mime' on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 0 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 1 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L21
Cannot access offset 0 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L22
Cannot access offset 1 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.1):
src/lib/IO/MetadataHandler/ImageSize.php#L24
Cannot access offset 'mime' on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L451
Syntax error, unexpected T_DOUBLE_ARROW on line 451
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L458
Syntax error, unexpected ')' on line 458
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L483
Syntax error, unexpected T_PROTECTED on line 483
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L500
Syntax error, unexpected T_PROTECTED on line 500
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L517
Syntax error, unexpected T_PROTECTED on line 517
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L534
Syntax error, unexpected T_PROTECTED on line 534
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L555
Syntax error, unexpected T_PROTECTED on line 555
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L574
Syntax error, unexpected T_PROTECTED on line 574
|
Unit tests & SQLite integration tests (7.4):
tests/lib/Persistence/Legacy/Content/TreeHandlerTest.php#L584
Syntax error, unexpected '}', expecting EOF on line 584
|
Unit tests & SQLite integration tests (7.4)
Process completed with exit code 1.
|
Unit tests & SQLite integration tests (8.0):
src/lib/FieldType/Image/ImageStorage.php#L1
Ignored error pattern #^Cannot access offset 0 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/FieldType/Image/ImageStorage.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/FieldType/Image/ImageStorage.php#L1
Ignored error pattern #^Cannot access offset 1 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/FieldType/Image/ImageStorage.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/FieldType/Image/ImageStorage.php#L110
Cannot access offset 0 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.0):
src/lib/FieldType/Image/ImageStorage.php#L111
Cannot access offset 1 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 'mime' on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 0 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L1
Ignored error pattern #^Cannot access offset 1 on array\{0\: int\<1, max\>, 1\: int\<1, max\>, 2\: int, 3\: string, mime\: string, channels\?\: int, bits\?\: int\}\|false\.$# in path /home/runner/work/core/core/src/lib/IO/MetadataHandler/ImageSize.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L21
Cannot access offset 0 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L22
Cannot access offset 1 on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.0):
src/lib/IO/MetadataHandler/ImageSize.php#L24
Cannot access offset 'mime' on array{0: int<0, max>, 1: int<0, max>, 2: int, 3: string, mime: string, channels?: int, bits?: int}|false.
|
Unit tests & SQLite integration tests (8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit tests & SQLite integration tests (8.1)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit tests & SQLite integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit tests & SQLite integration tests (7.4)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit tests & SQLite integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (7.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit tests & SQLite integration tests (8.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit tests & SQLite integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Unit tests & SQLite integration tests (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run code style check (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Run code style check (8.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Run code style check (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run code style check (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run code style check (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Solr integration tests (8.1)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Solr integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Solr integration tests (8.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Solr integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Solr integration tests (7.4)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Solr integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Solr integration tests (7.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|