Skip to content
Snippets Groups Projects
  1. Apr 16, 2023
    • Stefan Bürk's avatar
      [TASK] Use `ghcr.io` core-testing images in non-ci context · 61579079
      Stefan Bürk authored
      The docker container image hub is slowly becoming more
      and more problematic for open source organisations, it's
      time to move to another container registry for core-testing
      images. Images are now build and published to both Docker
      HUB and GitHub Container Registry (`ghcr.io`).
      
      To test the ghcr.io images, the patch changes runTests.sh
      to use them them for local (non CI) execution already.
      
      We can not fully switch to ghcr.io yet, since CI uses the
      docker registry container as mirror for images to heavily
      reduce network load and increase performance. The registry
      container however can only mirror hub.docker.io images, so
      we need a different solution for CI first. When this is
      done, we'll stop uploading images to docker hub later.
      
      Resolves: #100617
      Releases: main, 11.5, 10.4
      Change-Id: Ia309826618696dc25b15527b73fa704235285479
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78668
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      61579079
  2. Apr 15, 2023
  3. Apr 14, 2023
  4. Apr 13, 2023
  5. Apr 12, 2023
  6. Apr 11, 2023
  7. Apr 10, 2023
  8. Apr 06, 2023
    • Oliver Bartsch's avatar
      [BUGFIX] Prevent undefined array key in TypolinkSoftReferenceParser · 4c6f1abc
      Oliver Bartsch authored
      Due to an invalid page link, e.g. "t3://page?type=123",
      the "pageuid" key might not be set by PageLinkHandler.
      
      This is now properly handled in the parser.
      
      Resolves: #100510
      Releases: main, 11.5
      Change-Id: I0bc35cc1e3c0f5128ea52e3645faeaa5c600faaf
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78530
      
      
      Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      4c6f1abc
    • Stefan Bürk's avatar
      [TASK] Adjust possible dbms versions in `Build/Scripts/runTests.sh` · a6a1e8bd
      Stefan Bürk authored
      This changed adjusts the `Build/Scripts/runTests.sh` support for the
      different database types and versions. That means, which version for
      which types can be selected for functional and/or acceptance tests.
      
      Additionally, the help text output is enhanced to list information
      about the support of database versions provided by the vendors, on
      actual published release informations:
      
      * https://mariadb.com/kb/en/mariadb-server-release-dates/
      * https://www.postgresql.org/support/versioning/
      * https://endoflife.software/applications/databases/mysql
      
      Available versions are choosen for supported versions of the TYPO3
      core version, see following matrix as generic overview.
      
      **NOTE** Be aware, that this does not mean that tests are green
               with all version. This only enables execution through
               `Build/Scripts/runTests.sh` for now. `CI` adjustments
               are done afterwards in a dedicated shuffle change.
      
      mysql
      -----
      
      * 5.5 unmaintained since 2018-12    (11.5, 10.4)
      * 5.6 unmaintained since 2021-02    (11.5, 10.4)
      * 5.7 maintained until 2023-10      (11.5, 10.4)
      * 8.0 maintained until 2026-04      (main, 11.5)
      
      mariadb
      -------
      
      * 10.1  short-term, no longer maintained        (11.5, 10.4)
      * 10.2  short-term, no longer maintained        (11.5, 10.4)
      * 10.3  short-term, maintained until 2023-05-25 (main, 11.5, 10.4)
      * 10.4  short-term, maintained until 2024-06-18 (main, 11.5, 10.4)
      * 10.5  short-term, maintained until 2025-06-24 (main, 11.5, 10.4)
      * 10.6  long-term, maintained until 2026-06     (main, 11.5, 10.4)
      * 10.7  short-term, no longer maintained        (main, 11.5, 10.4)
      * 10.8  short-term, maintained until 2023-05    (main, 11.5, 10.4)
      * 10.9  short-term, maintained until 2023-08    (main, 11.5, 10.4)
      * 10.10 short-term, maintained until 2023-11    (main, 11.5, 10.4)
      * 10.11 long-term, maintained until 2028-02     (main, 11.5, 10.4)
      * 11.0  development series                      (main) [not working]
      * 11.1  short-term development series           (main) [not working]
      
      postgres
      --------
      
      * 9.6 unmaintained since 2021-11-11 (11.5, 10.4)
      * 10  unmaintained since 2022-11-10 (main, 11.5, 10.4)
      * 11  maintained until 2023-11-09   (main, 11.5, 10.4)
      * 12  maintained until 2024-11-14   (main, 11.5, 10.4)
      * 13  maintained until 2025-11-13   (main, 11.5, 10.4)
      * 14  maintained until 2026-11-12   (main, 11.5, 10.4)
      * 15  maintained until 2027-11-11   (main, 11.5, 10.4)
      
      Resolves: #100492
      Releases: main, 11.5, 10.4
      Change-Id: Iac5d4f799fd05ed7b766d1a9db95481caea2f898
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78499
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      a6a1e8bd
  9. Apr 05, 2023
  10. Apr 04, 2023
  11. Apr 02, 2023
  12. Mar 30, 2023
  13. Mar 29, 2023
  14. Mar 28, 2023
  15. Mar 27, 2023
  16. Mar 26, 2023
  17. Mar 24, 2023
    • Alexander Nitsche's avatar
      [BUGFIX] Support parsing of XML files larger than 10 MB · b59986fc
      Alexander Nitsche authored
      EXT:impexp may run into memory limits when converting XML to PHP
      arrays, even before all PHP memory is used up, because libxml has a
      specific limit of 10 MB. This limit can be turned off by using the
      `XML_PARSE_HUGE` (libxml) or `LIBXML_PARSEHUGE` (PHP) option, but
      only for the DOMDocument implementation of libxml, and not for the
      current XmlParser implementation.
      
      By replacing the XmlParser implementation with a DOMDocument
      implementation, larger XML files can be parsed with lower peak memory
      consumption as a side effect. For example, parsing a 4 MB dummy XML
      file consumes
      
      56.03 MB (memory) / 168.72 MB (memory peak)
      
      with the XmlParser, while using DOMDocument reduces the consumption to
      
      56.15 MB (memory) / 60.08 MB (memory peak).
      
      Besides the replacing of the implementation, XML parsing has been moved
      to separate classes (Typo3XmlSerializer / Typo3XmlParser), fully covered
      by tests, and restructured to reduce the number of required parameters to
      a minimum. The functional scope was not reduced in any way.
      
      Resolves: #83580
      Releases: main, 11.5
      Change-Id: Ic3345d539f028d766b49d01096ec34a6190a6dfe
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78249
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarAndreas Fernandez <a.fernandez@scripting-base.de>
      Reviewed-by: default avatarAndreas Fernandez <a.fernandez@scripting-base.de>
      b59986fc
  18. Mar 22, 2023
  19. Mar 20, 2023