Problem/Motivation

I was doing the individual follow up from https://www.drupal.org/project/drupal/issues/2951715#comment-12559059 then find out that we cannot add or log the message on MigrateSkipProcessException

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

rakesh.gectcr created an issue. See original summary.

jofitz’s picture

Assigned: Unassigned » jofitz

Aha, I think I see what's going on here, patch coming...

rakesh.gectcr’s picture

Status: Active » Needs review
StatusFileSize
new1.97 KB
rakesh.gectcr’s picture

Sorry Jo, Didn't refreshed the page...

rakesh.gectcr’s picture

StatusFileSize
new1.3 KB
new2.58 KB
rakesh.gectcr’s picture

jofitz’s picture

Assigned: jofitz » Unassigned

The last submitted patch, 3: 2959125-1.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

heddn’s picture

Status: Needs review » Needs work
Issue tags: +Needs tests

Can we add a test to see what is going on here? Also some nits.

+++ b/core/modules/migrate/src/MigrateSkipProcessException.php
@@ -6,5 +6,36 @@
+  ¶
...
+  ¶
...
+  ¶

Whitespace.

rakesh.gectcr’s picture

Its my bad, Some reasom My php Storm done this to me very regulardly.... :(

rakesh.gectcr’s picture

Issue tags: +Nwdug_may18
jofitz’s picture

Status: Needs work » Closed (cannot reproduce)

I cannot see the problem here (despite my comment in #2!)

I have been able to add MigrateSkipProcessException messages in both of the child tickets that this is apparently blocking.

Setting to Closed, but happy to look again if someone can provide me with more details of the problem.