class FailureMarkerExistsException

Exception thrown if a stage can't be created due to an earlier failed commit.

If this exception is thrown it indicates that an earlier commit operation had failed. If this happens the site code is in an indeterminate state. Package Manager does not provide a method for recovering from this state. The site code should be restored from a backup.

We are extending RuntimeException rather than StageException which makes it clear that it's unrelated to the stage life cycle.

This exception is different from ApplyFailedException as it focuses on the failure marker being detected outside the stage lifecycle.

Hierarchy

Expanded class hierarchy of FailureMarkerExistsException

6 files declare their use of FailureMarkerExistsException
FailureMarker.php in core/modules/package_manager/src/FailureMarker.php
FailureMarkerTest.php in core/modules/package_manager/tests/src/Kernel/FailureMarkerTest.php
PackageManagerRequirements.php in core/modules/package_manager/src/Install/Requirements/PackageManagerRequirements.php
PackageManagerRequirementsHooks.php in core/modules/package_manager/src/Hook/PackageManagerRequirementsHooks.php
package_manager.install in core/modules/package_manager/package_manager.install

... See full list

File

core/modules/package_manager/src/Exception/FailureMarkerExistsException.php, line 21

Namespace

Drupal\package_manager\Exception
View source
final class FailureMarkerExistsException extends \RuntimeException {

}

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.