TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-23T06:28:58ZTYPO3 Forge
Redmine TYPO3 Core - Task #103473 (Resolved): Account for double click pagetree timeout in acceptance testshttp://forge.typo3.org/issues/1034732024-03-23T06:28:58ZBenjamin Franzkeben@bnf.devTYPO3 Core - Feature #103439 (Under Review): Site TypoScripthttp://forge.typo3.org/issues/1034392024-03-20T14:35:14ZBenjamin Franzkeben@bnf.dev
<p>Allow TypoScript without requiring sys_template records.</p>
<p>Idea: A site can define TypoScript and include other dependencies via profiles (<a class="issue tracker-2 status-8 priority-4 priority-default child" title="Feature: Site Profiles that ship Settings, TypoScript, TSConfig, Templates and enabled Content Elements (Under Review)" href="http://forge.typo3.org/issues/103437">#103437</a>)</p> TYPO3 Core - Task #103297 (Resolved): Add composer-mode to our acceptance test matrixhttp://forge.typo3.org/issues/1032972024-03-06T10:42:13ZBenjamin Franzkeben@bnf.dev
<p>All applicable acceptance tests should also executed<br />in composer mode in order to cover possible regressions for this mode.</p> TYPO3 Core - Task #103086 (Resolved): Allow execution of acceptance tests with local chromedriver...http://forge.typo3.org/issues/1030862024-02-09T05:57:26ZBenjamin Franzkeben@bnf.dev
<p>A local instance can sometimes be better debugged and odd behaviour easier introspected, when acceptance tests are possible to be run on the host instead of in containers only.</p>
<p>The testing setup should be adapted to allow that using codeception <code>--env</code> parameter</p> TYPO3 Core - Task #103081 (Resolved): Failing nightlies due to incorrect window sizehttp://forge.typo3.org/issues/1030812024-02-08T10:54:12ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://git.typo3.org/typo3/CI/cms/-/pipelines/52871">https://git.typo3.org/typo3/CI/cms/-/pipelines/52871</a></p>
<pre>
1) PageTreeFilterCest: Clear filter reloads page tree without filter applied
Test Acceptance/Application/PageTree/PageTreeFilterCest.php:clearFilterReloadsPageTreeWithoutFilterApplied
Step Can see "inline mngroup","#typo3-pagetree-tree .nodes-list"
Fail Failed asserting that any element by '#typo3-pagetree-tree .nodes-list' on page /typo3/module/web/list?id=51
Elements:
+ <div> New TYPO3 site
Root
styleguide TCA demo
staticdata
ctrl common
ctrl minimal
displaycond
elements basic
elements folder
elements group
elements imagemanipulation
elements rte
elements select
elements slugs
elements t3editor
file
flex
inline 11
inline 1n
inline 1n1n
inline 1nnol10n
inline 1nreusabletable
inline expand
inline expandsingle
inline foreignrecorddefaults
contains text 'inline mngroup'
Scenario Steps:
19. $I->canSee("inline mngroup","#typo3-pagetree-tree ...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:83
18. $I->canSee("elements group","#typo3-pagetree-tree ...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:82
17. $I->waitForElementVisible("//*[text()='inline expa...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:81
16. $I->waitForElementNotVisible("#typo3-pagetree ....",10) at Acceptance/Application/PageTree/PageTreeFilterCest.php:116
15. $I->waitForElement("#typo3-pagetree-tree .nodes...",10) at Acceptance/Application/PageTree/PageTreeFilterCest.php:115
14. $I->pressKey("#typo3-pagetree #typo3-pagetree-...","") at Acceptance/Application/PageTree/PageTreeFilterCest.php:78
Artifacts:
</pre>
<p><img src="http://forge.typo3.org/attachments/download/38243/TYPO3.CMS.Core.Tests.Acceptance.Application.PageTree.PageTreeFilterCest.clearFilterReloadsPageTreeWithoutFilterApplied.headless.fail.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #102502 (Closed): Fix support for bash v3 in runTests.shhttp://forge.typo3.org/issues/1025022023-11-24T09:06:20ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #102450 (Closed): Refer to minor versions for our images in runTestshttp://forge.typo3.org/issues/1024502023-11-22T13:54:56ZBenjamin Franzkeben@bnf.dev
<p>Allows to auto-update local images for feature-updates<br />simply by raising them in runTests.sh (like we do for<br />external images as well).</p>
<p>That means <code>runTests.sh -u</code> is only needed in case<br />patch updates are desired or needed.</p> TYPO3 Core - Task #102449 (Closed): Automatically remove containers in runTests.shhttp://forge.typo3.org/issues/1024492023-11-22T13:45:17ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #102132 (Closed): CI Composer max failure: phpstan: Ignored error pattern in T...http://forge.typo3.org/issues/1021322023-10-10T04:43:13ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://git.typo3.org/typo3/CI/cms/-/jobs/2632464">https://git.typo3.org/typo3/CI/cms/-/jobs/2632464</a></p>
<pre>
- Upgrading phpstan/phpdoc-parser (1.20.0 => 1.24.2)
- Upgrading phpstan/phpstan-phpunit (1.3.14 => 1.3.15)
</pre>
<pre>
$ Build/Scripts/runTests.sh -s phpstan -p 8.1
06:14
------ -----------------------------------------------------------------------------------------------
Line core/Tests/Unit/Database/Schema/Parser/TableBuilderTest.php
------ -----------------------------------------------------------------------------------------------
Ignored error pattern #^Call to static method
PHPUnit\\Framework\\Assert\:\:assertSame\(\) with 0 and string\|null
will always evaluate to false\.$# in path
/builds/typo3/CI/cms/typo3/sysext/core/Tests/Unit/Database/Schema/Parser/TableBuilderTest.php
was not matched in reported errors.
</pre> TYPO3 Core - Bug #101885 (Resolved): runTests.sh -u does not update imageshttp://forge.typo3.org/issues/1018852023-09-09T05:03:10ZBenjamin Franzkeben@bnf.dev
<p>Update does nothing:<br /><pre>
Build/Scripts/runTests.sh -u
> prune unused, dangling local volumes
> pull ghcr.io/core-testing-*:latest versions of those ones that exist locally
> remove "dangling" ghcr.io/core-testing-* images (those tagged as <none>)
###########################################################################
Result of update
Environment: local
PHP: 8.1
SUCCESS
###########################################################################
</pre></p>
<p>Although the images are outdated<br /><pre>
[typo3-clean] (main) $ docker images | grep core-testing-php
ghcr.io/typo3/core-testing-php83 latest 184e88ecc62c 2 weeks ago 206MB
ghcr.io/typo3/core-testing-php82 latest 10292ff1a2dd 7 weeks ago 224MB
ghcr.io/typo3/core-testing-php81 latest d5e5c603d5b4 3 months ago 230MB
ghcr.io/typo3/core-testing-php74 latest 46fc907a5d1c 3 months ago 217MB
ghcr.io/typo3/core-testing-php72 latest 9fb67a3524b5 3 months ago 184MB
</pre></p> TYPO3 Core - Task #101615 (Under Review): Remove implicit wait timeout from acceptance testshttp://forge.typo3.org/issues/1016152023-08-08T08:09:17ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #101278 (Resolved): Fix incorrect DateTimeTest method nameshttp://forge.typo3.org/issues/1012782023-07-06T21:16:34ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #98270 (Closed): Drop unneeded .cache/.npmrchttp://forge.typo3.org/issues/982702022-09-06T20:15:27ZBenjamin Franzkeben@bnf.dev
<p><code>unsafe-perm = true</code> is not available in npm v8 documentation, and TYPO3 core requires npm v8, so the setting should not be needed.</p> TYPO3 Core - Task #89280 (Closed): TypoScript Template Constant Editor flushes to many caches, re...http://forge.typo3.org/issues/892802019-09-25T21:26:07ZBenjamin Franzkeben@bnf.dev
<p>Reported by Simon Schaufelberger via Slack channel #psr11-initiative:</p>
<pre>
Sunday, August 4th 3:21 pm
The problem also is that the DI cache gets flushed way too often.
I just saved a typoscript constant in the template module and the whole cache was empty again afterwards.
Wondering why the DI cache needs to get flushed in such a case
</pre>
<p>The reason is the usage of clear_cacheCmd('all') which flushes all core caches like ext_localconf and DI cache.<br />Also opcache is flushed. These caches are unaffected by TypoScript Template change.s</p> TYPO3 Core - Bug #87997 (Rejected): Links to workspace overlays should not be generated without b...http://forge.typo3.org/issues/879972019-03-25T11:49:57ZBenjamin Franzkeben@bnf.dev
<p>If an editor links to a versioned page id (let's say 1011) directly (e.g. by specifying that id in header_link),<br />that link is currently generated as /index.php?id=1011 when the frontend is visited as a regular visitor (e.g. without backend/workspace context).</p>
<p>Visiting that page will fail with "page not found" (which is fine).</p>
<p>It would be expected that links wouldn't be generated at all (that means: link is empty), as for hidden/deleted pages.</p>