Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow \Harvest\Harvester to log errors for users and devs #3811

Open
paul-m opened this issue Jul 29, 2022 · 0 comments
Open

Allow \Harvest\Harvester to log errors for users and devs #3811

paul-m opened this issue Jul 29, 2022 · 0 comments

Comments

@paul-m
Copy link
Contributor

paul-m commented Jul 29, 2022

User Story

This issue supports WCMS-10613.

This issue is almost a bug report, but the code currently works. It's just not easy to determine what went wrong in a failed content import.

Trying to perform the Drush commands for import from sample_content module, I get a status like this:

% ddev drush dkan:sample-content:create
+----------------+-----------+---------+---------+--------+
| run_id         | processed | created | updated | errors |
+----------------+-----------+---------+---------+--------+
| sample_content | 10        | 0       | 0       | 10     |
+----------------+-----------+---------+---------+--------+

Unfortunately the errors are only counted and not logged, so there is no path forward.

This effort should probably focus on \Harvest\Harvester::extract(), ::transform(), and ::load(), which catch exceptions and store their error outputs in an array, which is subsequently discarded.

Acceptance Criteria

Attempting to perform a harvest results in error logs for errors that occur.

@github-actions github-actions bot added this to Incoming/Triage in DKAN 2 Issue Triage Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
DKAN 2 Issue Triage
  
Incoming/Triage
Development

No branches or pull requests

1 participant