Problem/Motivation

Follow-up to #3354099: Add functional test that proves there is reasonable UX whenever Composer Stager operations have a hard failure to solve the problem in automatic_updates_extensions

Steps to reproduce

Proposed resolution

Right now \Drupal\automatic_updates_extensions\BatchProcessor::commit will try to delete the stage 2x if there is exception. We should copy the logic from \Drupal\automatic_updates\BatchProcessor::stage

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

tedbow created an issue. See original summary.

tedbow’s picture

Status: Active » Needs review
tedbow’s picture

tedbow’s picture

Title: Ensure exceptions are show if updating extensions and there is composer stager error » Ensure exceptions are shown if updating extensions and there is composer stager error
tedbow’s picture

Assigned: Unassigned » phenaproxima
phenaproxima’s picture

Assigned: phenaproxima » tedbow
Status: Needs review » Reviewed & tested by the community

One tiny thing but otherwise this is just a copy-and-paste from Automatic Updates, so I'm not concerned.

  • tedbow committed 0bd78fc9 on 3.0.x
    Issue #3436993: Ensure exceptions are shown if updating extensions and...

  • tedbow authored 64f925e7 on 3.1.x
    Issue #3436993: Ensure exceptions are shown if updating extensions and...
tedbow’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.