Bug #64942: Racecondition in Extractor Registry for Indexing FAL files - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (2)

Markus Hölzle
Stefan L

Actions

Copy link

Bug #64942

closed

Racecondition in Extractor Registry for Indexing FAL files

Added by Stefan L about 9 years ago. Updated over 3 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

File Abstraction Layer (FAL)

Target version:

Start date:

2015-02-09

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

Hi,

there seems to be a bug where two or more Extractors of a FAL driver can not share the same priority.
They overwrite each other

typo3/sysext/core/Classes/Resource/Index/ExtractorRegistry.php
Function getExtractorsWithDriverSupport
Line 99 (and duplicated) 101

i would expect two extractors with the same priority to work in random order

The same occurs in typo3/sysext/core/Classes/Resource/Index/Indexer.php:105

bye

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #56727: ExtractorRegistry can not handle Extractors with same ExecutionPriority

Closed

2014-03-10

Actions

Related to TYPO3 Core - Bug #92643: Fix FAL meta data extraction priorities

Closed

2020-10-21

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Riccardo De Contardi over 7 years ago

Category set to File Abstraction Layer (FAL)

Actions

Copy link

Updated by Gerrit Code Review about 5 years ago

Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Gerrit Code Review almost 5 years ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/59894

Actions

Copy link

Updated by Anonymous over 4 years ago

Status changed from Under Review to Resolved
% Done changed from 0 to 100

Applied in changeset 3092154eef62c1d7e96576577896fb0523605bde.

Actions

Copy link

#10

Updated by Benni Mack over 4 years ago

Status changed from Resolved to Closed

Actions

Copy link

#11

Updated by Helmut Hummel over 3 years ago

Status changed from Closed to Accepted
TYPO3 Version changed from 6.2 to 9

This issue isn't resolved yet. Extractors can have same priority, but the extracted meta data of extractors with same priority will still be overwritten.

Actions

Copy link

#12