You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if an add, delete or update link fails, the failure is called out in the print log, but only at the time of the error. As a result, if a failure occurs during a sync_links or delete_orphans call to the PLM the failures will often be buried within the long print log output. These failure can easily be missed.
As a solution, the errors should be gathered and displayed at the end of the batch process similar to how they are displayed for scan_all_links. Some of the foundational logic for this already exists for sync links, the failure call back just needs to be passed down through the subroutine calls.
Delete_Orphans does not contain any logic for this and would need to be supplemented.
The text was updated successfully, but these errors were encountered:
krkeegan
added a commit
to krkeegan/misterhouse
that referenced
this issue
Oct 23, 2013
This enables the same feature that has been available in the scan_all_links function. If an error occurs while attempting to sync_all_links, MH now recovers from the error, and continues to process the remainin objects in Sync_All. At the conclusion of the Sync_All routine a message is displayed identifying the failed objects.
Partial Fixhollie#73
krkeegan
added a commit
to krkeegan/misterhouse
that referenced
this issue
Oct 23, 2013
Adds a similar functionality to what has been in scan all links. If a failure occurs on a device while running delte orphans, MH now recovers and continues to process the rest of the delete queue. At the conclusion of the queue, the failed object is reported.
Fixeshollie#82hollie#73
Currently if an add, delete or update link fails, the failure is called out in the print log, but only at the time of the error. As a result, if a failure occurs during a sync_links or delete_orphans call to the PLM the failures will often be buried within the long print log output. These failure can easily be missed.
As a solution, the errors should be gathered and displayed at the end of the batch process similar to how they are displayed for scan_all_links. Some of the foundational logic for this already exists for sync links, the failure call back just needs to be passed down through the subroutine calls.
Delete_Orphans does not contain any logic for this and would need to be supplemented.
The text was updated successfully, but these errors were encountered: