Fix reset-failed command

Created on 19 January 2023, over 2 years ago

Problem/Motivation

The most recent change in the smart-migrate:reset-failed command was wrong: it was built on the assumption that all failed rows have a migrate message, but this assumption is wrong.

Steps to reproduce

  1. Migrate something which causes a fatal error while the destination plugin's import method is running.
  2. Try to reset the migration's failed rows with drush smart-migrate:reset-failed
  3. The failed row remains in the migrate map table, so you won't be able to re-import it one more time.

Proposed resolution

Change the reset approach back to the state (or equivalent) we had before b89452ba.

Remaining tasks

Create test coverage.

User interface changes

Nothing.

API changes

Nothing.

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡­πŸ‡ΊHungary huzooka Hungary πŸ‡­πŸ‡ΊπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Status changed to Needs review over 2 years ago
  • Status changed to Fixed over 2 years ago
  • Issue was unassigned.
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024