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
As part of the work in #6565, event logging in the parse task was removed. This ticket captures the work to reintroduce it to ManifestLoader.get_full_manifest, likely behind an optional flag. I believe the best method to achieve this is to pass in the fire_event function to the method, defaulting to a noop function.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Reintroduce logging to manifest generation
[CT-1890] Reintroduce logging to manifest generation
Jan 24, 2023
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
As part of the work in #6565, event logging in the
parse
task was removed. This ticket captures the work to reintroduce it toManifestLoader.get_full_manifest
, likely behind an optional flag. I believe the best method to achieve this is to pass in thefire_event
function to the method, defaulting to a noop function.The text was updated successfully, but these errors were encountered: