Skip to content

mcardle-features-runners - #42

Open
rtmcardle wants to merge 3 commits into
ampsczfrom
mcardle-features-runners
Open

mcardle-features-runners#42
rtmcardle wants to merge 3 commits into
ampsczfrom
mcardle-features-runners

Conversation

@rtmcardle

Copy link
Copy Markdown
Collaborator

Additional features developed in July 2026, recording pipeline failures to a ledger, respecting audio qc overrides, and respecting manual date selection (for runsheet linking malnamed files).

* Prevent double-progress-bars from swallowing query executions

* Increased logging verbosity for tracking dropped/errored files

* Introduce persistent error ledger into db

* Wire error ledger into pipeline

* Additional comments/concerns for discussion

* Separated failure ledger schema and additional logging in crawlers

* Check for active subjects and record genuine failures

* Config update

* Improved failure ledger schema

* Introduce batch crawler

* Config for data dictionary

* Add OH timezone and timezone fail logging

* Deletes stale records for audio_journals on insert (avoids collision when journal upload is delayed compared to timestamp)

* DB connection optimizations
Introduces audio qc override to backend runners
* Introduce datetime_overrides table to db

* Utilize datetime_overrides on file parse failure

* Remove override_consumed check for subsequent crawler runs
@rtmcardle
rtmcardle requested a review from dheshanm July 21, 2026 18:33
@dheshanm

Copy link
Copy Markdown
Member

Posting @rtmcardle 's comments here for the record on #41:

/v1/issues/unresolved/pipeline-failures/datetime-override/route.ts POST method, which calls:

DashboardActions.recordAction to write to public.dashboard_actions, and
DatetimeOverrides.create to write to pipeline_ledger.datetime_overrides

I think you might be intending to link to the .../pipeline-failures/resolve/route.ts change near it, which does call:

DashboardActions.recordAction to write to public.dashboard_actions, and
PipelineFailures.resolve to write to pipeline_ledger.pipeline_failures.

This endpoint is called in ./src/app/issues/pipelineFailures/page.tsx , the resolveFailure function. This is a feature to mark a failure as resolved with an optional note. There is not a lot of functionality here at this time, just a basic 'mark this failure so we can ignore it as "resolved"'.

@dheshanm dheshanm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds multiple fixes:

  • Adds the missing timezone to OH
  • Much improved error handling and persistence in DB via. pipeline_ledger

And features:

  • AudioQC overrides

These are all great additions to the pipeline. One observation for future consideration: the pipeline is becoming more tightly coupled with its companion repository, dptools/dpinterview-web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants